By Aquilasfx on
I follow upgrade.txt and disable all module that are not in the core, and after save configuration, the site return me only page not found for whichever page.
Now???
I follow upgrade.txt and disable all module that are not in the core, and after save configuration, the site return me only page not found for whichever page.
Now???
Comments
If it is a minor update
If it is a minor update don't disable them -- go to ?q=admin/build/modules and enable them again. Just take your site offline (admin/settings/site-maintenance)
nothing if I point to
nothing if I point to /?q=admin/build/modules server returns "The requested page could not be found. " I install the site in my localhost...
drupal 6.2 to 6.3...
drupal 6.2 to 6.3...
Is "Page not found" a
Is "Page not found" a Drupal-themed page or a server page?
Do you have uploaded the 6.3 files already, or is it still 6.2?
If you have uploaded the 6.3 files, have you run update.php?
it's still 6.2.. I block my
it's still 6.2.. I block my upgrade as I see page not found...
Same problem
Hello all, I have the same problem!!
I followed the upgrade directions and disabled the non core modules after putting the site into maint. mode. I got page not found errors, but continued the update.
I have updated the site to 6.3 - and update.php ran without problems. I am unable to access the admin pages to re-enable my modules. I get 'page not found' errors
I have steped thru the forums and tried using the alternate URL ?q=admin/modules - this does not work.
I have tried disabling clean URL's in the database. this did not work.
I have replaced my settings.php file with the latest version and only updated the DB url.
Is there a way to manually re-enable the modules in the database?
Your help is much appreciated.
FYI:
I am using: Views(6.x-2.0-rc1), FCKEditor, Simplenews, Calandar(6.x-2.0-beta3), Date(6.x-2.0-beta3), & CCK(6.x-2.0-rc2) modules that all need to be re-enabled.
I also am using a views block to display upcoming events on each page.
I guess you mean that you
I guess you mean that you tried ?q=admin/build/modules
How didn't that work? A "page not found" again? Was the error page Drupal-themed?
You can enable the modules in the database, in the system table, by setting their status to 1.
thanks
Thank you.. After a little more digging and a leap of faith, I started disabling the modules with the SQL command:
UPDATE system SET status = 0 WHERE name = 'calendar';
as described in: http://drupal.org/node/270303
cog.rusty - thank you for your response.
it's still 6.2.. I block my
it's still 6.2.. I block my upgrade as I see page not found...
So,
So,
- your Drupal files are still 6.2
- your Drupal database is still 6.2 because you never ran update.php. Correct?
Now the problem is that you have disabled some modules. Correct?
If so, go to your database using phpmyadmin, browse the 'system' table, and enable those modules again by setting their 'status' to 1. Anyway it was not necessary to disable them.
Me too!
I have the same problem. As soon as I disabled the added modules I lost access to everything and have not been able to get back into the site since. I can't get to any of my pages at all.
I'm really new at this and don't know where to go from here. Is there anything I can do if I ftp into the files?
Try running update.php. Even
Try running update.php. Even if there are no updates to do, this often fixes a few things.
Were there any access control modules among the modules which you disabled, such as organic groups or taxonomy access?
If you can't access your site at all and can't go to the ?q=/admin/build/modules page, then the only thing you can do is to go into the database and try to fix it. Unfortunately to do this you need to know a few things about the database.
One thing you could try in the database is to enable your modules again in the system table, by setting their 'status' to 1. Also browse the 'node_access' table. Does it contain more than one row with realm='all'?
yes all correct... all is
yes all correct... all is still 6.2 I disable only all module excluse module of core system... now... you think is better to do a fresh installation of drupal 6.3? (I try in that version some module.. and delete other module after try their functionality... ) My question is... after install module and delete that.. in database what happens? (the majority of modules haven't remove functionality... I must fisically remove folders of that module... )
About your question, when
About your question, when you disable a module its data are not completely deleted, but they may become unavailable. If a module contains uninstall code, you can click on the 'Uninstall' tab of the admin/build/modules page and uninstall it, to remove its data completely.
If you delete a module's folder, the above won't work because the uninstall code won't exist, so you will only get errors. Before deleting a module's folder make sure that you have disabled it *and* uninstalled it.
and if uninstall doesn't
and if uninstall doesn't exhists? ...how I can delete this module without corrupt database?
If a disabled module is
If a disabled module is still in its folder and there is no uninstall entry for it, then probably there was nothing to uninstall and it is OK to delete it.
But sometimes (rarely) a module may be badly designed or buggy and doesn't clean after itself. In such cases you can't do anything except submit an issue with a support request or a bug report to the module's project page.