symphonycms/symphony-2 — Issue #874: Breadcrumbs inside /blueprints/pages/
Author: eKoeS
Created: 2011-10-29 10:52:23+00:00
State: open

Some strange behaviours I noticed:

* When creating a new page, the breadcrumbs shows the following path: `Pages››Untitled` I suppose it's a bug.
* Depending on the page (e.g. pages listing or single page editor), the parent page links becomes either a link to `?parent` or a link to the editor. I can't find a logic for that, moreover `?parent` is only available when `pages_table_nest_children` is true, but no checks are done on that.

I think the 2nd is the biggest issue. The same link to the same parent page means different things based on where we are, which is dangerous in my opinion because makes the whole "clicking" action a surprise. I'd suggest to stick to one single behaviour for every `/blueprints/pages/*` page. My take is: let's use `?parent`, as every other breadcrumbs in the backend uses links to take the user to a table view page. If `?parent` is not available (which in turns means that `pages_table_nest_children` is off), let's just display link-less text.

Question: when `pages_table_nest_children` was first introduced, which was the reason for making it a setting? I'm asking this because I'm not sure I like having it as a choice. If we could just make it mandatory, we could make breadcrumbs more intuitive.