8000 docs: Explain how to route requests from an apphook back to the CMS by jrief · Pull Request #7878 · django-cms/django-cms · GitHub
[go: up one dir, main page]

Skip to content

docs: Explain how to route requests from an apphook back to the CMS #7878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 9, 2024

Conversation

jrief
Copy link
Contributor
@jrief jrief commented Apr 18, 2024

Description

This documentation patch explains how to route requests from an apphook back to the CMS. Currently it states that this is impossible, but actually it can be done with a small modification to get_urls()….

Adding CMS pages below an apphooked page was a request from my team btw.

  • I have opened this pull request against develop-4
  • I have added or modified the tests when changing logic
  • I have followed the conventional commits guidelines to add meaningful information into the changelog
  • I have read the contribution guidelines and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.

@jrief jrief force-pushed the docs/apphook-rerouting branch from 75e55c0 to 85a7c25 Compare April 18, 2024 12:19
@fsbraun
Copy link
Member
fsbraun commented Apr 18, 2024

Nice!

@marksweb marksweb changed the title Explain how to route requests from an apphook back to the CMS docs: Explain how to route requests from an apphook back to the CMS Apr 30, 2024
@marksweb marksweb force-pushed the docs/apphook-rerouting branch from 85a7c25 to 5603f72 Compare April 30, 2024 00:56
@fsbraun fsbraun merged commit 0b3ad4f into django-cms:develop-4 May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0