Closed (fixed)
Project:
Pathauto
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
28 Apr 2011 at 18:47 UTC
Updated:
24 May 2011 at 13:31 UTC
I didn't see a post about this anywhere. I just installed and enabled pathauto. I did a Bulk update and some of my exising content works but most does not. The old path for one content type works but not the new one. IE: node/34 works but entries/34 does not. The critical part though is that I can no longer create Content. When I go to the add content link it says "you have not created any content types." even though they are there when I go to list content types.
Comments
Comment #1
paulandrewmarchand@yahoo.com commentedComment #2
dave reidDo you have multiple languages on this site? What happens when you go to yoursite.com/node/add? I highly doubt Pathauto is at fault here. It does not mess with node access nor menu callbacks at all.
Comment #3
paulandrewmarchand@yahoo.com commentedI get the same error just not in the admin overlay. Path auto is the only thing that I changed today. It was working fine until I did the bulk update.
this is the exact text on the page:
You have not created any content types yet. Go to the content type creation page to add a new content type.
Comment #4
paulandrewmarchand@yahoo.com commentedand no there is not multiple languages.
Thanks
-paul
Comment #5
dave reidAgain, not sure how pathauto could remove your content type configuration. Can you reproduce this with a clean Drupal 7 install + Pathauto alone? Do you have any kind of node-related contributed modules enabled?
Comment #6
paulandrewmarchand@yahoo.com commentedSorry you are right it was this not Pathauto.
I am still having the issue with one content type not working though. The new path doesn't work but the old one does. I am getting a 403 Forbidden. Any idea why this would happen on one type but not the other? I checked the permissions but I couldn't find anything.
http://drupal.org/node/997444
Comment #7
gregglesGlad to hear that.
I suggest disabling modules one by one until the menu item works again.