Folks: I'm having a huge problem with XMLsitemap in Drupal 7.
When I enable the xmlSitemap module, I am no longer able to log into the site with my password. It says "Access Denied". I ran update.php and got the following errors: Notice: Undefined index: update_success in update_results_page() (line 177 of /Applications/MAMP/htdocs/update.php). Warning: reset() expects parameter 1 to be array, null given in update_results_page() (line 181 of /Applications/MAMP/htdocs/update.php). Warning: array_pop() expects parameter 1 to be array, null given in update_results_page() (line 181 of /Applications/MAMP/htdocs/update.php). The update process was aborted prematurely while running update # in .module. All errors have been logged.
This is part of an update from Drupal 6 to 7. Previously, I tried deleting all of the xmlSitemap… tables in the database, but that didn't help. There seemed to be someplace else where xmlsitemap data was stored. When I deleted those tables, then re-installed xmlsitemap, they didn't re-appear, so something was out of whack.
I'm lost. Can someone give me a strategy to pursue? If I could figure out how to permanently, manually uninstall the module, I might be able to pt it back in and get the database updated correctly. I've searched through the db tables and don't see how I could uninstall the module, except to remove tables beginning with xmlsitemap.
Thanks, Bill
Prothero William waprothero@gmail.com
Folks:
I finally figured out how to solve this. I installed siteMap on a virgin D7 site that didn't have any of the xmlsitemap tables. I invoked the module, and saw that it created two tables, much different from the D6 versions. I deleted the old D6 site map tables, and copied the new ones to my site. Then, it worked. I no longer get errors when I do update.php and the problems disappeared.
Boy, some of these modules are finicky!!
Best, Bill
Prothero William waprothero@gmail.com
On Apr 25, 2013, at 10:27 AM, Prothero William waprothero@gmail.com wrote:
Folks: I'm having a huge problem with XMLsitemap in Drupal 7.
When I enable the xmlSitemap module, I am no longer able to log into the site with my password. It says "Access Denied". I ran update.php and got the following errors: Notice: Undefined index: update_success in update_results_page() (line 177 of /Applications/MAMP/htdocs/update.php). Warning: reset() expects parameter 1 to be array, null given in update_results_page() (line 181 of /Applications/MAMP/htdocs/update.php). Warning: array_pop() expects parameter 1 to be array, null given in update_results_page() (line 181 of /Applications/MAMP/htdocs/update.php). The update process was aborted prematurely while running update # in .module. All errors have been logged.
This is part of an update from Drupal 6 to 7. Previously, I tried deleting all of the xmlSitemap… tables in the database, but that didn't help. There seemed to be someplace else where xmlsitemap data was stored. When I deleted those tables, then re-installed xmlsitemap, they didn't re-appear, so something was out of whack.
I'm lost. Can someone give me a strategy to pursue? If I could figure out how to permanently, manually uninstall the module, I might be able to pt it back in and get the database updated correctly. I've searched through the db tables and don't see how I could uninstall the module, except to remove tables beginning with xmlsitemap.
Thanks, Bill
Prothero William waprothero@gmail.com
On Thu, Apr 25, 2013 at 2:03 PM, Prothero William wrote:
Folks:
I finally figured out how to solve this. I installed siteMap on a virgin D7 site that didn't have any of the xmlsitemap tables. I invoked the module, and saw that it created two tables, much different from the D6 versions. I deleted the old D6 site map tables, and copied the new ones to my site. Then, it worked. I no longer get errors when I do update.php and the problems disappeared.
Boy, some of these modules are finicky!!
When upgrading to a major release make sure that all the modules in the current release are at their most current release. For xmlsitemap you should have upgraded from the latest 1.x series to the latest 2.x series before upgrading to the major release.
If you are removing a module, first disable the module, then use the Delete tab and delete it. This removes the tables, any associated data and marks the system table as uninstalled; you should never remove the tables manually. You can then remove the module from your modules folder on the disk.
Ernie, Thanks for the info on the correct procedures. Since I had no update notification for xmlsitemap, I thought I was at the latest version in D6. So, once I upgraded, it wasn't until I decided to activate xmlsitemap that I started getting into trouble. For someone who only occasionally needs to do Drupal work, the system does seem pretty finicky and there are so many ways to do things that a load of time can be wasted. But, I know that's the strength of drupal, to be able to do so many things.
I do appreciate the help I get from the community.
Best, Bill
William Prothero http://es.earthednet.org
On Apr 26, 2013, at 4:56 AM, Earnie Boyd earnie@users.sourceforge.net wrote:
On Thu, Apr 25, 2013 at 2:03 PM, Prothero William wrote:
Folks:
I finally figured out how to solve this. I installed siteMap on a virgin D7 site that didn't have any of the xmlsitemap tables. I invoked the module, and saw that it created two tables, much different from the D6 versions. I deleted the old D6 site map tables, and copied the new ones to my site. Then, it worked. I no longer get errors when I do update.php and the problems disappeared.
Boy, some of these modules are finicky!!
When upgrading to a major release make sure that all the modules in the current release are at their most current release. For xmlsitemap you should have upgraded from the latest 1.x series to the latest 2.x series before upgrading to the major release.
If you are removing a module, first disable the module, then use the Delete tab and delete it. This removes the tables, any associated data and marks the system table as uninstalled; you should never remove the tables manually. You can then remove the module from your modules folder on the disk.
-- Earnie
-- https://sites.google.com/site/earnieboyd
[ Drupal support list | http://lists.drupal.org/ ]
-
Earnie Boyd -
Prothero William -
Waprothero＠gmail.com