Closed (fixed)
Project:
Services
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Aug 2011 at 15:48 UTC
Updated:
26 Jul 2013 at 14:55 UTC
Jump to comment: Most recent file
Comments
Comment #1
kylebrowning commentedCan you give me more information on how to reproduce this?
Comment #2
kylebrowning commentedComment #3
astutonetHi.
I'm updating a site from D6 to D7. I also have a problem with update #7301 that may be related to this issue.
Whem I running update.php, I receiving this message:
Comment #4
kylebrowning commentedThere is no upgrade path between 6 and 7 for services., and furthermore you shouldn't need to run update.php on old updates if you have the latest version of services, the updates are already applied to the schema.
Comment #5
astutonetOk.
@kylebrowning, I also have noticed this type of problem with other modules (examples: CKEditor; LinkIt, ; HTMLMail, etc).
The following messages also are assigned to the Services module while running of update.php:
7301 - Update 7301 adds debugging to each endopint to facilitate easier development
7302 - Update 7302 restores the usage of Chaos tools to check for enabledisable-status
7303 - Update 7303 adds the possibility to configure server settings on a per-endpoint basis. and sets upgrades all new servers to have at least services session enabled.
7399 - Update 7304 removes the title as it is no longer used
As this message is always displayed during execution of update.php, I think some instruction is missing in the services.install file.
With the other modules, a simple patch solves the issue.
You can help me?
Tks.
Comment #6
kylebrowning commentedThe updates are only needed if you used a previous version of services 3.x Why is your schema attempting to apply these updates?
Comment #7
astutonetHi @kylebrowning.
I'll try to explain to you why there is need for update.
The informations of Services module are related to version 6.x-3.0.
When the database was imported to the new version of Drupal, the module Services 6.x-3.0 weren't excluded (I don't find any information saying that it should be done before the upgrade) and the information remained in the database.
When the "update.php" is executed, it checks the old information in the database and does the updates according to the needs of new installed modules.
So if the old database (6.x-3.0 update 7304) table stores a title of a field and the new version (7.x-3.0) does not use this information, the update should treat this information (excluding or truncating the information) so that when update.php is run again, there is no mismatch of information.
As it stands, all the sites who have upgraded from D6 to D7 and have the Services module installed, when running "update.php" will receive the information in #5 (always).
Therefore, the version 7.x-3.0 of Services module should treat the information brought from version 6.x-3.0, even if only to exclude them from the database.
Perhaps you understand best by seeing this comment related to another module: http://drupal.org/node/1347682#comment-5272444.
I hope you understand "why" of the need.
Any questions, just ask.
Tks.
Comment #8
marcingy commentedInitial upgrade path path.
Comment #9
astutonet@marcingy,
The patch was applied to the services.install file. Then, the update.php was run. All operations of updating the database were implemented and the Drupal did not report any problems.
Thank you.
Comment #10
kylebrowning commentedComment #11
kylebrowning commentedComment #12
elBradford commentedThanks for that patch, it worked great! I was hoping it would make it into 7.10 but apparently it didn't. Great work though, allowed the updates to finish.
Comment #13
marcingy commentedThis has nothing to do with drupal core release what so ever.
Comment #14
Starminder commentedIs this getting rolled into a dev release?
Comment #15
kylebrowning commentedIts already in the dev build.
Comment #16
jeroenb commentedI'm having the same issue, upgrading from D6 to D7, had services installed (6.2.x). Just tried installing 6.3.x (the dev, to get the patch) and got:
Update #7301
Failed: DatabaseSchemaObjectDoesNotExistException: Cannot add field services_endpoint.debug: table doesn't exist. in DatabaseSchema_mysql->addField() (line 320 of /Volumes/data/Users/jeroenb/Projects/proximity-dashboard/trunk/includes/database/mysql/schema.inc).
Comment #17
marcingy commentedUpgrades from 2.x to 3.x are not supported and never will be.
Comment #19
crazyben21 commentedHi,
I'm still getting the error after using the latest development release. I'm upgrading my drupal website on my lab system from 6 to 7. The problem is I never was using the services module on drupal 6 and it's giving me this error.
The problem is in my case is, how can the table exist if this my first time using the service module and I'm not upgrading from any previous service module.
Any help will be greatly appreciated. In the mean time I will disable this module and delete the folder.
Comment #20
marcingy commented@crazyben21 services must have been installed at some point in time because if it hadn't been the update hook would not fire. You should uninstall the service module from the module uninstall screen (drupal core).
Comment #21
marcingy commentedComment #22
crazyben21 commentedWell I check the uninstall when I was drupal 6 and it's not there. When I remove it from drupal 7 I also did and uninstall. Is there any way to uninstall it manually on the mysql database?
Comment #23
marcingy commentedStrange, yes you can delete the services module manually from the system table.
Comment #24
marcingy commentedClosing as old support request