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

Already on GitHub? Sign in to your account

Can't navigate back to admin homepage, /admin/content (or the other context homepages) #752

sourcejedi opened this Issue Mar 19, 2013 · 1 comment


None yet
2 participants

sourcejedi commented Mar 19, 2013

Sorry, this is a bit of a laundry list.

/admin redirects to /admin/content

/admin/content says "As of Bonfire v0.7-dev, this page has no default content. This is your playground. Make it home." Imagine you follow the instructions and put useful stuff there. The problem is the Bonfire admin interface doesn't seem to give you any links back to that page. You would have to re-enter the admin interface.

P.S. no 1: /admin/reports has the same text, but is completely unreachable.

P.S. no 2: If you hover over e.g. the "Content" or "Reports" text in the tobpar, it looks like a link to /admin/content / admin/reports, because that's what appears in your status bar. But clicking them doesn't do anything.

P.S. no 3: Hovering the "Developer" text in the topbar, the status bar shows /admin/developer. This URI does not exist, (and if you try to visit it, Bonfire will confusingly redirect you to admin/content without showing any error message).

Also config/route.php creates a URI alias, from admin/settings to settings/settings. URI aliases often considered undesirable (although it's mainly an issue with public web pages). For example, the * in firefox indicating that a URI has been bookmarked, will not be visible in alternate aliases of that URI. Similar issue with link color (:visited). Equally if people are having to apply per-page hacks for usability/a11y reasons.


mwhitneysdsu commented Mar 21, 2013

First, I'd like to say thanks for everything you've been doing on the codebase. I've been heavily bogged down with other work on my own site and still haven't managed to successfully move my environment from its current 0.6.hybrid to 0.7 (I get locked out of my test system when I try to migrate to 0.7).

This makes it difficult to determine whether things are settings-related or related to some change going forward to 0.7. That being said, /admin/reports works on my end if I go there directly, but as you mentioned there are no links to it. I could set a role's default context to Reports, which would cause the Control Panel links (/admin) on the front end to go there, but that would make it only as useful as the Content page.

I actually use the /admin/content/index view (in my admin theme) as a sort of running changelog for my site, with changes to modules displayed based on user permissions (though looking at it now I see I haven't been keeping up for the last couple of months), and a set of links to reference sites for developer/admin users. Since most of my users land there when they log in, it's useful for less important notifications and reminders.

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