The bare issue is that when "Add content" is selected on the "Content" admin page no response is forthcoming. On one occassion, and I have been unable to recreate this, Chrome reported "too many redirects".
The URL displayed in the browser (Chrome) is /#overlay=node/add and on selecting this it simply leaves the "Loading ...." cycling. Earlier add content worked as expected, giving a choice of the available content types. I can still add content, but do so by changing the URL to for example /#overlay=node/add/basic to create a basic page. Between working as expected, and the current behaviour, Add content went to a behaviour of immediately going the page to construct one of the available content types that I had created. That content type was new with no instances on the site, so I deleted that content type ... and the current behaviour ensured. This may have been a mistake ...
Caches have been cleared, permissions rebuilt. Hosting service is ipage, OS reported as Debian. Any replies please include the obvious mistakes, I've been using Drupal for about one week only, site is www.deesidecameraclub.org
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | add-content-1185838-7.patch | 2.08 KB | bramvdkroef |
| #5 | add-content-1185838-5.patch | 901 bytes | bramvdkroef |
Comments
Comment #1
captaingeek commentedwhat about disabling overlay?
Comment #2
captaingeek commentedfixed my issue by http://drupal.org/node/613292 not sure of cause
Comment #3
shyamala commented- Disable Add content links within the Navigation menu at: #overlay=admin/structure/menu/manage/navigation
- though the #overlay=node/add/page, #overlay=node/add/poll all works the message displayed at: #overlay=node/add is:
"You have not created any content types yet. Go to the content type creation page to add a new content type."
This is a BUG. The node/add page links must not be based on the status of the Navigation menu links. They must be based on the content permissions.
The function node_add_page() assigns $content = system_admin_menu_block($item); which is based on the Navigation menu and not the content type permissions.
Comment #4
rpmskret commentedI have changed the issue settings from Vers. 7.2 to 7.8 as that is now current and what I have a bug in.
Also from Component:node system to Component:menu system
Does seem to involve the menu system and particularly the Nav menu. I had made panicky changes
there after getting another problem (see. http://drupal.org/node/1018614 - Undefined index: localized_options in menu_navigation_links())
Fixed that issue by using post#5.
Now get "You have not created any content types yet..." when trying to use the Add content link.
Work-around is to go to #overlay=admin/structure/menu/manage/navigation and select a
content to create there.
This is inconvenient and a little unsettling, but sure am glad for a secondary method to add content.
Comment #5
bramvdkroef commentedThis patch updates node_add_page() in node/node.pages.inc so it uses node_type_get_types() to get the content types and creates links for the ones the user has access to.
Comment #6
Everett Zufelt commentedIf I understand correctly, node_add_page() is currently checking the access perms on the menu items (node/add/content-type) and not on the add content-type perms. Whereas this might not normally be a problem, there are cases where the perms are not the same.
Agreed that this is a bug that needs to be fixed. A quick peak at node_add_page() for 8.x shows that it will need to be fixed there too.
Bumping to 8.x-dev as issues are resolved there first and then backported where appropriate.
Comment #7
bramvdkroef commentedI see your point. Here's a patch that uses the system_admin_menu_block() code, but includes hidden menu items.
Comment #8
Everett Zufelt commentedComment #9
kscheirer#7: add-content-1185838-7.patch queued for re-testing.
Comment #19
catchOverlay is no longer in core.