Admin logs-inspection bug fix

[Gagan-Ram]

Fixes: #800

Before:
Error page: " Not found I'm afraid we could not find the the resource you requested."

After:

Summary by Sourcery

Bug Fixes:

• Update JavaScript log detail URL from '/control/logdetail/' to '/tickets/control/logdetail/' to resolve 404 errors

[sourcery-ai]

Reviewer's Guide

The PR fixes a 404 error by adjusting the base path for the admin log detail AJAX endpoint in the main UI script.

Sequence diagram for admin log detail AJAX request (before and after fix)

sequenceDiagram
    actor AdminUser
    participant Browser
    participant Server
    Note over AdminUser,Browser: Before Fix
    AdminUser->>Browser: Clicks 'View Log Detail'
    Browser->>Server: GET /control/logdetail/:id
    Server-->>Browser: 404 Not Found
    Browser-->>AdminUser: Shows error page
    Note over AdminUser,Browser: After Fix
    AdminUser->>Browser: Clicks 'View Log Detail'
    Browser->>Server: GET /tickets/control/logdetail/:id
    Server-->>Browser: Log detail data
    Browser-->>AdminUser: Shows log detail modal

Loading

File-Level Changes

Change	Details	Files
Correct AJAX URL for log detail requests	Updated URL prefix from '/control/logdetail/' to '/tickets/control/logdetail/'	src/pretix/static/pretixcontrol/js/ui/main.js

Possibly linked issues

• Admin logs inspection causes partial system crash. #800: PR fixes admin logs inspection crash by correcting the log detail URL.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Gagan-Ram - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (code-quality): Use const or let instead of var. (avoid-using-var)

Explanation

`const` is preferred as it ensures you cannot reassign references (which can lead to buggy and confusing code). `let` may be used if you need to reassign references - it's preferred to `var` because it is block- rather than function-scoped.

From the Airbnb JavaScript Style Guide