Firstly, thanks for this module. I have a client who is currently dependant on a hacked version of Premium, but you've provided a much better future option.

So, some time soon, I'll need to migrate this client over to Node Option Premium. Will premium nodes marked by the Premium module continue to be recognised by Node Option Premium? Or are the modules entirely separate?

If they are entirely different modules, I guess I may try to do something with Views Bulk Update to manage the migration....

Comments

anrikun’s picture

anrikun commented

This is something I have never tried yet.
Modules are completely separate.
Views Bulk Update might work but *please be very careful* and try this on a dev site first.
And backup your database before attempting the real migration.
Feedback about this would be greatly appreciated.

Mark Nielsen’s picture

Mark Nielsen commented
Status: Active » Closed (works as designed)

Thanks, anrikun. I'll try the Views approach. I'm thinking that I might create a transitional taxonomy term or flag to hold the premium/not-premium data. That way I can disable and uninstall Premium (as advised) before enabling Node Option Premium.

I'll post back with more feedback after I've done this (may be a few weeks in the future). Closing this issue for now.

anrikun’s picture

anrikun commented

Nice approach! Please reopen when done.

anrikun’s picture

anrikun commented

Finally, I'm opening this issue again as other users might want to share their experiences about the same subject.

anrikun’s picture

anrikun commented
Status: Closed (works as designed) » Active