I'm running a test copy of a website with over 1000 users. I tried to upgrade form 1.9 to 2.0 beta 12 but it failed. Running update.php was very slow (taking more than 10 minutes). Somewhere in the end it failed. I tried again, but it would'nt update anymore and Subscriptions was broken.

I then tried to make a clean start. I disabled the module, deleted the files and deleted all database tables starting with subscriptions. After copying Subscriptions 2.0 beta 12 to my modules folder again and activating it, it wasn't creating any database tables. Logically status report said the database wasn't up to date.

What can I do to make a clean start with 2.0 beta 12? What do I have to delete or reset besides the things I described above?

Thanks in advance..

Comments

salvis’s picture

This is the first time I hear of such problem. Did you get a progress bar? Did it advance? Did you get any error messages, or how did it "fail"? Anything in the watchdog log?

You shouldn't have to delete database tables. Subscriptions 2.0 has an uninstall function on admin/build/modules/uninstall. After that, you should be able to do a clean install (you may as well get RC1, but it won't make a difference installation-wise).

However, I'm very concerned about this problem; please provide whatever additional information you can come up with. PHP version? MySQL version? Drupal version? ...

dries arnolds’s picture

I got a progress bar running update.php. It progressed very slowly with about 1% at a time. After ten minutes it said 'unspecified error' in red. In the details there was no text under 'update 7'. Just blank. Watchdog gives the following error multiple times (probably because I tried uninstalling and reïnstalling multiple times
Invalid argument supplied for foreach() in /home/vhosts/website.org/httpdocs/sites/all/modules/subscriptions/subscriptions.module on line 492.

Drupal: 5.7
MySQL: 5.0.45
PHP: 5.2.3

salvis’s picture

#245464: "Invalid argument supplied for foreach()" on line 492 during user self-registration is fixed in RC1.

We have some sizable sites running on Subscriptions 2.0 for quite a while already, for example introfini's (see http://drupal.org/node/210659), and he ran update_7() without commenting.

It's odd that it progresses so slowly, there's just not that much processing in update_7(). Could it be that you have something else that's eating up cycles when updating users?

But anyway, it was progressing, and with the foreach() bug fixed in RC1, it would be very interesting to see whether it goes through now. You wrote you were running it on a test copy of the site — could you do that again with a new copy and RC1?

dries arnolds’s picture

It might be another module, since I've got quite some modules installed. Nothing however that catches my eye as 'might interfere', but then again I'm no developer.

I want to try it again, but I started this test installation for other purposes, which are nearing a deadline. If I have some time left next week I'll try again.

Thanks for your help.

gigslist’s picture

ugrade to og 2 also failed on my site,

drupal 5.7

Would it be the problems with the subscriptions module affecting the og module? as I seem to be getting a lot of error messages related to subscriptions when something happens in the og module

also Group name 0 problem - I looked in og.module but could not find the lines they mentioned in the lines they quoted in the module

newbie to drupal but have worked on other cms - postnuke, dotnetnuke, mambo
(so far drupal and installing modules has been great, except for og and subscriptions)

thanks

Deborah

Drupal dev site Gigslist.org/gigslist

salvis’s picture

@gigslist: I have never heard of any interaction between Subscriptions and OG, and whatever problem may occur on your site with upgrading OG is certainly not related to upgrading Subscriptions from 1.9 to 2.0 BETA 12, which is the topic of this issue here.

Please open a new issue in the appropriate issues queue. If you have subscriptions_og installed, then you might try the issues queue there. Otherwise, go to the og issues queue.

There's very little we can do with "I seem to be getting a lot of error messages related to subscriptions when something happens in the og module". To have a chance to receive help, you need to say what your configuration was when your site still worked, what you upgraded (exact version numbers!), and what you're seeing now (exact error messages!).

Again, DO NOT REPLY in this issue here, but open a new one!

salvis’s picture

Version: 5.x-2.0-beta12 » 5.x-2.0-rc1
Status: Active » Fixed

chx has run the 1.9+ to 2.0-RC1 update on a large test database with "waaaaaaay more than 1000 users." It completed without a hitch in close to 50 minutes. Most of that time is spent in subscriptions_update_7(), which moves subscriptions flags from the {users} table to the {subscriptions_user} table, loading and saving every {users} row in the process.

As I mentioned in #3, RC1 did fix a bug in BETA12, and I'm confident now that Subscriptions is ready for release.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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