Pulling my hair out. Again.

A completely clean, bang-up-to-date (today) Drupal install, with all mods up to date and update.php / cron run fully.

Mods installed / enabled (the only mods in sites/all/modules):
- CCK/Link
- DHTML Menu
- Global Redirect
- Pathauto
- Token
- Views

Garland in use for admin and live site.

Several content types created, most pretty basic with nothing more than a few fields.

One content type includes a single taxonomy vocab which includes 6 terms. When I add a node of this content type, the add form is fine, however submiting it takes me to a page not found error! If I try to access the content it lists in admin/content man/content, however if I try to access it I get the page not found again.

I have worked out that something is bothering pathauto/global redirect as the auto alias is not being created in this content type. If I try to do a batch update from settings it still does not work - aliases remain blank.

If I remove the taxonomy from the content type then add a new node, it works!! (The broken ones stay broken).

I removed EVERYTHING and started from scratch - it did it again :oS !!!!

Lastly, and just to add to the odness, trying to get into the Garland configure page also gives me a 404 error also. What the...!

Comments

cheshireinatree’s picture

In Administer » Site building » URL aliases under "automated alias setting" tab what replacement patterns are you using to auto create the alias for that content type?

Try making it the simplest pattern possible, such [nid]. Does it still not create the aliases?

Also remember the check the "Bulk generate aliases for nodes that are not aliased box" for each setting group you want to affect. I know it sounds obvious but I had a bonehead moment with that once so I thought I'd mention it.

If none of that gives any hints, can you manually add an alias on the node's edit page, just to check that there's not a mod_rewrite issue with the server.

citrustree’s picture

Thank you.

No pattern works. Bulk generation does not work either.

I found another 404. If I go to Views, I can press Add, then set name and type, however when I submit that I get nother page not found.

Grramnkmmmkkk!

citrustree’s picture

My amazing host got to the bottom of this. It turns out that APC cache which was installed on the server was causing Drupal to panic and serve up the error. We don;t know why, just that it works with APC cache disabled. Shame, as it made the rest of Drupal just that little bit faster.

I can't really see much reference to any conflict when I search for it - does anyone know of any?