Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.web
beat.web
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.webbeat.web
  • Issues
  • #558

Closed
Open
Opened Sep 08, 2020 by Samuel GAIST@samuel.gaist3 of 3 tasks completed3/3 tasks
  • Report abuse
  • New issue
Report abuse New issue

Fix usage of URL_PREFIX

Currently the URL_PREFIX settings variable is used like a fully qualified URL in many parts of the website which is wrong. As the name suggests, this prefix shall essentially "move" all the URLs of the site behind it.

If a fully qualified address is needed it should be generated either using the request object associated with the method call or using Django's Sites framework.

This issue tracks the cleanup of the following:

  • Email generation
  • Template rendering
  • Other usages
Edited Sep 28, 2020 by Samuel GAIST
Assignee
Assign to
Django 3 migration
Milestone
Django 3 migration
Assign milestone
Time tracking
None
Due date
None
1
Labels
bug
Assign labels
  • View project labels
Reference: beat/beat.web#558