Skip to content
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

Aliases shouldn’t use the CMS standard template in preview/edit mode #255

Open
MacLake opened this issue Nov 20, 2024 · 2 comments
Open

Comments

@MacLake
Copy link

MacLake commented Nov 20, 2024

When editing e. g a small footer it is confusing to see header and footer of the CMS standard table, which might belong to another section site of the CMS, and it might even be hard t find the section you want to edit, see screenshot.
Bildschirmfoto vom 2024-11-20 18-12-12

@MacLake MacLake changed the title Aliases shouldn’t use teh CMS standar template in preview/edit mode Aliases shouldn’t use teh CMS standard template in preview/edit mode Nov 20, 2024
@MacLake MacLake changed the title Aliases shouldn’t use teh CMS standard template in preview/edit mode Aliases shouldn’t use the CMS standard template in preview/edit mode Nov 20, 2024
@fsbraun
Copy link
Member

fsbraun commented Nov 20, 2024

@MacLake You can customize the template by providing your own alias/base.html. The one provided extends base.html, yours does not have to. Just make sure the required CSS and JS is present.

@MacLake
Copy link
Author

MacLake commented Nov 20, 2024

Good to know, @fsbraun, actually it’s djangocms_alias/base.html (in your template folder). If you look at the code, it’s
obvious Nevertheless we should mention it in the documentation. I can do it when I have some time.

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

No branches or pull requests

2 participants