Is it possible to upgrade at all? Looks like advpoll_update_7000() doesn't perform upgrade from 6.x. And it assumes that fields have been created already. Is there any work on this task? Can we help with D6 to D7 upgrade code?

Comments

Michele Wickham’s picture

Michele Wickham commented
Assigned: Unassigned » Michele Wickham
Category: support » feature

I'll have a look at what it would take to make transition easier from d6 to d7. The underlying structure of the two modules is very different because it seemed the community was interested in a CCK compatible node structure.

I'll have a look at how other modules are allowing for an upgrade path and see what I can do. It just may take me a little time as my priority is getting the current build stable and ready for full release. If anyone has any suggestions feel free to comment.

As an FYI, the hook_update_n hook is typically used to make alterations to the database - each revision gets called during the update.php process.

Thanks,
Michele

Michele Wickham’s picture

Michele Wickham commented
Status: Active » Closed (won't fix)

Closing this issue as it is partly a feature request and partly a misunderstanding of the purpose of the update_n hook. At this point there is no direct path from 6 to 7.

dmitriy.trt’s picture

dmitriy.trt commented

Please, read hook_update_N() documentation, especially this part:

mymodule_update_7000(): This is the required update for mymodule to run with Drupal core API 7.x when upgrading from Drupal core API 6.x.

And your advpoll_update_7000() is for upgrade between minor versions, not for upgrade from 6.x.

So, there will be no upgrade path from 6.x in future? Even if someone will implement it as a patch?

vinoth.3v’s picture

vinoth.3v commented
Status: Closed (won't fix) » Needs work

content_migrate module from cck does the great Job doing/helping other module's fields to upgrade to D7. Does it help? May be we can integrate with that module or you can use the sample from there.

Sorry, I am reopening this.
I dont like this great module breaking continuvity or discouraging others from using in future.

mikhailkrainiuk’s picture

mikhailkrainiuk commented
Issue summary: View changes
Status: Needs work » Fixed

Hello!

Thank you for the comment.
Upgrading a website between 2 major versions of the platform needs a special separate module for moving data from the old website on a previous major version to the new website, built on a new major version of the platform. This is the task for the website owner, not for the current module.

mikhailkrainiuk’s picture

mikhailkrainiuk commented
Status: Fixed » Closed (won't fix)
mikhailkrainiuk’s picture

mikhailkrainiuk commented
Assigned: Michele Wickham » Unassigned
Status: Closed (won't fix) » Fixed

Status: Fixed » Closed (fixed)

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