My problems with XML sitemap begun when I changed the path for the XML file. The reason for the change was that the robots text file was not allowing access to anything in this site path. I relocated to site/all/files/ . I then changed the robot text file so that only restricted access to the default directory.

I was unable to change the XML Path to the new location. So I uninstalled XML site map. At the same time I noticed that there was an update to 6x.2 so I installed it, and ran the update.php. The update failed.

Tried uninstalling XML sitemap, deleting the module, removed all reference to XML sitemap in sys database table. Still cannot run update. This is the error I receive

The update process was aborted prematurely while running update #6001 in nodereference.module. All errors have been logged. You may need to check the watchdog database table manually.

I may have installed the update over the old version.

Great Model! Any help I can get or pointers of where to look next will be appreciated

Comments

dave reid’s picture

Project: XML sitemap » Content Construction Kit (CCK)
Version: 6.x-2.0-unstable1 » 6.x-2.x-dev
Component: xmlsitemap.module » nodereference.module

The problem you're reporting is actually a problem with nodereference.module. Which version of CCK are you using? There is probably an existing report for this bug, but I'm moving this issue to CCK.

markus_petrux’s picture

Could you please take a look at the following? #550252: content_db_index_exists produces SQL errors when creating node reference fields for MySQL 4.

The fix for that is already in CVS. You would have to get the latest development snapshot of CCK (the -dev package related to the version of CCK installed in your system).

ron_mahon’s picture

Thanks For the very fast reply
Install the dev dated aug 18 same error message?
I have removed all traces of xmlsitemap and it still has this error?
Ran the cron and flushed all the chache's

ron_mahon’s picture

Version: 6.x-2.x-dev » 6.x-3.x-dev

Installed 6.3x-dev Same error but differen referannce #
An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page

An HTTP error 0 occurred. http://inmrc.com/update.php?id=30&op=do

translector’s picture

Subscribing.

markus_petrux’s picture

Status: Active » Postponed (maintainer needs more info)

If not related to the above mentioned issue, then I'm lost on ideas. Maybe something else has been stored in the logs?

Side note: this update function is basically equal as the previous update step. The only difference is that each update function does a different thing for each field, but the logic to use batch api is the same. So the only difference I can see is that use of content_db_index_exists() mentioned in #2.

markus_petrux’s picture

Version: 6.x-3.x-dev » 6.x-2.x-dev

It would be nice to know from which version to which version of CCK the update was related.

Also, I wanted to mention update 6001 in nodereference module can be executed as many times as you wish. To do so, visit update.php, find the updates for nodereference module and choose 6001.

The aim of this update step was to create indexes for nodereference fields, but only if those indexes do not exist already.

And... please note the userreference field also had an update step to do the same for userreference fields. This update function is the same as the one implemented by nodereference. That is, nodereference_update_6001() and userreference_update_6001() look the same. One deals with userreference fields, and the other with nodereference fields.

ron_mahon’s picture

Version: 6.x-2.x-dev » 6.x-3.x-dev

Ok I uninstalled CCK completely and removed it from all/files/modules. cleared cache and ran cron.

Tried update Got this The update process was aborted prematurely while running update #6004 in print_mail.module. All errors have been logged. You may need to check the watchdog database table manually.

Did the same thing with print module and got a new error message
HTTP POST is required.
warning: array_pop() [function.array-pop]: The argument should be an array in /home/inmrcc/public_html/update.php on line 314.
The update process was aborted prematurely while running update # in .module. All errors have been logged. You may need to check the watchdog database table manually.

I did up date CCK, Print, mollom, share this, taxmanager. all at the same time yesterday.

Hope this sheds some light!
Thanks
Ron

markus_petrux’s picture

To update CCK, all you need to do is visit update.php and follow the instructions. You don't need to disable/uninstall anything else.

I would suggest restoring backups, make sure everything is ok, and then updating one module at a time following provided instructions for each one. Probably, all you need is update the module files and visit update.php, unless instructed otherwise from a particular module.

ron_mahon’s picture

Ok I cheated but I fixed it

I install ed a new Acquia update. Then just to test the gods I installed cck 6.x-3.x-dev and run update.

Updates were attempted. If you see no failures below, you may proceed happily to the administration pages. Otherwise, you may need to update your database manually. All errors have been logged.

* Main page
* Administration pages

The following queries were executed
nodereference module
Update #6001

* No queries

userreference module
Update #6001

* No queries

Update #6002

* No queries

Every thing runs fine Now and it look like the latest CCK update is fine too!

Many thanks
Ron

ron_mahon’s picture

Except that update aborted before it finished. Thats how this whole thing started.
Ron

markus_petrux’s picture

Status: Postponed (maintainer needs more info) » Fixed

As per your comment in #10, it seems you got it fixed. If this is not the case, then please post the exact error that you're seeing. Without an error which is related to CCK, nodereference, it is not possible to guess what really failed. It could simply be something not really related to CCK.

ron_mahon’s picture

That is my feeling also! That is was not related to CCK. It's working fine now. I installed the latest update to make shore that it works.

Thanks
For the help
Ron

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.