Question Subscriptions lost in FB1.05RC2 to 1.08 Migration

I'm in the process of testing the migration from FB1.05RC2 to Kunena 1.0.8.
After uninstalling Fireboard and Installing Kunena - all seems fine apart from all subscriptions have been lost.
On further investigation, it seems the table jos_fb_subscriptions is empty.
If I drop jos_fb_subscriptions and recreate it from a backup then everything seems fine.

• Is there a reason that the subscriptions table is being emptied during upgrade? - Perhaps a problem with the data in the table?
• Is it safe to restore the table from a backup post install?

I have had a good look through the forum and the only reference I can find to a similar problem seems to be in German. Sorry I only understand english.

Has anyone else encountered this problem?
Thank you

Rob

Been digging a little deeper - it looks like the structure of the subscriptions table is changed during install. I think the problem is duplicates. I'm going to try editing the table to remove duplicates prior to install.
Strange though that there was no error generated during the install.

Please note- this is a solution I have devised myself - it might not be right and it might not work for you. If anyone can advise further please do.

Just for anyone else who might have this problem - I think Its fixed now.
Just before the upgrade export your ???_fb_subscriptions table remove any duplicate lines. Then truncate the table and upload your edited version.

You should now be able to uninstall fireboard and install Kunena and retain your subscriptions.

Well it worked on my test site.

Rob ( i dont normally talk to myself this much...) (oh yes you do)

Rob,

Thx a lot for posting this! Yes there was a security fix to remove duplicates. Somebody could have put 10,000s of subscriptions into, ultimately crashing somebody's email and server.

The upgrade performs exactly what you are describing as long as your MySQL user has create temp table permissions. The upgrade will create a temporary table to dedupe the data, truncate and update the subscriptions table and re-insert the clean data.

Only if the mySQL userid does not have create temp table permission, the existing subscriptions are dumped to allow the table changes to take place.

Hope this explains the logic behind the upgrade.

fxstein