TEMPLATE_STRING_IF_INVALID setting throws error in traversing from page-list to page item #2676

Closed
ramandv opened this Issue Feb 20, 2014 · 4 comments

Comments

Projects
None yet
4 participants
@ramandv

ramandv commented Feb 20, 2014

Page list [http://localhost:8000/en/admin/cms/page/] url lists the items with invalid anchor url
[http://localhost:9000/en/admin/cms/page/INVALID%20EXPRESSION:%20url7/]

It is not critical, as it will be used only in development settings. But it might confuse the newbies, when they are trying out.

@digi604

This comment has been minimized.

Show comment
Hide comment
@digi604

digi604 Feb 20, 2014

Contributor

i don't understand the issue... could you explain more?

Contributor

digi604 commented Feb 20, 2014

i don't understand the issue... could you explain more?

@digi604 digi604 added this to the 3.0 milestone Feb 20, 2014

@ramandv

This comment has been minimized.

Show comment
Hide comment
@ramandv

ramandv Feb 21, 2014

Version: 2.4.3

How to reproduce the error:

In the settings.py, add the following config

TEMPLATE_STRING_IF_INVALID = 'INVALID EXPRESSION: %s'

Now, check the admin page for "pages" and click on a particular page_item

cursor_and_list_of_pages_and_site_administration___django_site_admin-14

ramandv commented Feb 21, 2014

Version: 2.4.3

How to reproduce the error:

In the settings.py, add the following config

TEMPLATE_STRING_IF_INVALID = 'INVALID EXPRESSION: %s'

Now, check the admin page for "pages" and click on a particular page_item

cursor_and_list_of_pages_and_site_administration___django_site_admin-14

@digi604 digi604 modified the milestones: 2.4.X, 3.0 Mar 6, 2014

@ggaughan

This comment has been minimized.

Show comment
Hide comment
@ggaughan

ggaughan Aug 22, 2014

This also breaks the 'Page' menu link in the front-end.

This also breaks the 'Page' menu link in the front-end.

@czpython

This comment has been minimized.

Show comment
Hide comment
@czpython

czpython May 26, 2016

Member

Looks like this is fixed on the latest CMS 3.2.x

Member

czpython commented May 26, 2016

Looks like this is fixed on the latest CMS 3.2.x

@czpython czpython closed this May 26, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment