I've been running my drupal site for about 9 months, and over the past few days pathauto has disappeared. It's no longer available in the admin pages, doesn't show up on the node edit pages and doesn't display in the Available Modules page. It almost looks like it's been deleted, except that it hasn't.

It's still in the same place, untouched. I started my investigation by visiting the admin url for pathauto (path/pathauto), and it wouldn't load, failing with 'Fatal Error: Call to undefined function _pathauto_include()'.

I've checked and it loads into the 'system' table of the database, disabled.

It was available as an uninstall option, which I completed. I then deleted the files, rebuilt the modules list, cleared cache, reinstalled the latest stable version and it still won't show up in the modules list for me to re-enable.

Are there any cases of this happening before? Are there any suggestions for a fix? Or any places to look where something might have been corrupted? The uninstall removed all the pathauto variables from the variable table and I've tried manually removing the file from the system table, but no luck.

Any help appreciated as I really need this module!

Cheers.

Comments

greggles’s picture

I'm not really sure. I suggest trying out 6.x-1.3 and then looking in the system table for the "filename" column to see where it thinks that Pathauto is installed. It may be in some directory where you don't expect it.

matt.nz’s picture

Version: 6.x-1.2 » 6.x-1.3
Priority: Critical » Normal
Status: Active » Closed (fixed)

Thanks for your help! I've managed to get it going again, but still not entirely sure what the problem is. The filename in the system table was where it was kept, so it should have been visible.

Anyway, I'll document what else I tried, in case it happens to anyone else or is part of some other issue/conflict:

In desperation to get this module to be recognised again, I tried copying it to the system modules directory, and it still didn't show up, so it wasn't just the one particular location wasn't working.

However, when I renamed the folder in the sites modules directory to 'path_auto', it was recognised again. All the permissions on the folder were unchanged, and the only references to pathauto in my entire database were in the system table and advanced help tables, but it looks like the directory with the name 'pathauto' was somehow blocked or conflicting or something with Drupal, but no idea why...

Probably not the most elegant solution (and hopefully the renaming doesn't create more issues), but I'm glad it's back up and running!

sp_key’s picture

Hi, the same thing has happened to me too.
I have a 'pathauto' folder in my modules directory which I renamed to path_auto however, this did not fix the problem like it did at your case.
Furthermore the URL /admin/pathauto comes back as Page not found.

Any suggestions / thoughts would be highly appreciated!

Many thanks

greggles’s picture

/admin/pathauto

If you are on Pathauto 6.x try admin/build/path/pathauto - it's the Automated Alias Settings tab under Administer > Site building > URL Aliases.

matt.nz’s picture

This has happened to me again and I can't figure it out. It's still in the system table, but status and bootstrap have been set to 0, and it doesn't show up in admin/build/modules. I've managed to get it to force load (add automatic alias settings to node edit page) by changing the values mentioned to 1, but visiting the modules page means it disappears again.

And it never recreates the pathauto tab in the alias settings. Hardlinking doesn't work - I guess the module rebuild removes the path.

It does, however, appear under uninstall. Going through that process doesn't cause it appear in the modules page again.

matt.nz’s picture

Category: support » bug
Status: Closed (fixed) » Active

There doesn't seem to be anything in the dblog, but is there any other way to debug where it's failing to load??

matt.nz’s picture

This one is bizarre, I've been looking at it for the last hour or so now. I've got back to the point where if i change the folder name to 'pathauto2' it works, but back to 'pathauto' and it disappears again. Loads into system table if i do a module rebuild with it named pathauto2, but not the other way.

Did dump of my entire drupal database - the only mentions of pathauto are in locales_source and the permission table, so I can't see what could be blocking it. Path redirect was enabled and had pathauto listed in the system table as an 'enhances' module, but I've removed that entry and the module - still no luck.

Dave Reid’s picture

Category: bug » support

Until there's an actual bug we can point to, moving this to a support request.

Elaine_k’s picture

Version: 6.x-1.3 » 6.x-1.5
Component: Code » Miscellaneous
Assigned: Unassigned » Elaine_k

I am having this same problem with pathauto. I fairly new to Drupal, but had been doing quite nicely, until I started translating content and menus into Spanish. Everything seemed to be working ok, then I realised some of my menu links were going to page not found.

I can´t get at a lot of my content, even though it is showing up in the content list as published, when I click on the link on the content page I get the error.

I tried, clean urls etc. but though perhaps it may be something to do with pathauto, after searching for solutions, I found a post that mentioned problem with pathauto and i8n module.

So then I have the same problem as above:

Path enable (say pathauto is enabled), yet pathauto is not showing on the module list.

Path auto file was missing on the server, I uploaded the latest version, and now the file is there, but still not showing in the modules list.

Any suggestions as to how to fix these problems is greatly appreciated.

marcopanichi’s picture

on Drupal 6.x you can reach pathauto here:
Administer > Site Building > URL aliases > Automated alias settings

or you can also create a Navigation menu item referring it to "admin/build/path/pathauto"

Dave Reid’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)

No longer able to provide help for support requests on 6.x which I cannot reproduce.