I searched but didn't find this issue.

On pgSQL, the following line (128) in subscriptions.install fails.

  db_query("INSERT INTO {subscriptions_user} (uid, digest, send_interval, send_updates, send_comments) VALUES(-DRUPAL_AUTHENTICATED_RID, 0, 1, 0, 0)");

It's a typo (note the -). Should be :

  db_query("INSERT INTO {subscriptions_user} (uid, digest, send_interval, send_updates, send_comments) VALUES(DRUPAL_AUTHENTICATED_RID, 0, 1, 0, 0)");

Though I am not sure that the defined variable DRUPAL_AUTHENTICATED_RID gets interpreted when it is within a quoted string. So that needs checking as well.

Comments

agentrickard’s picture

Looking again, perhaps the - is by design. In which case this error note will help.

Query failed: ERROR: column "drupal_authenticated_rid" does not exist 

query: subscriptions_install INSERT INTO subscriptions_user (uid, digest, send_interval, send_updates, send_comments) VALUES(-DRUPAL_AUTHENTICATED_RID, 0, 1, 0, 0)

I suspect the fix is to evaluate -DRUPAL_AUTHENTICATED_RID outside of the query itself.

salvis’s picture

Thanks for the heads up... Unfortunately there are two issues with BETA7:

http://drupal.org/node/170571#comment-673363
http://drupal.org/node/204765

Apply the patches, uninstall Subscriptions (not just disable) and reinstall. Then it should be fine...

And, yes, the minus sign is intentional!

salvis’s picture

Status: Active » Closed (duplicate)

I'm thrilled to have someone exercise the pgsql code!

agentrickard’s picture

I've been running pgSQL simply to test MySite and Domain Access development, since no volunteers pitched in.

I have recently decided that I may do all my local testing against pgSQL for just this reason.

salvis’s picture

That's an interesting strategy, testing against pgsql and relying on testers to do the mysql part.

Then I assume that you were able to install after applying the patches. That's valuable information, thanks!

And sorry for the hassle -- we're trying not to go through beta versions too quickly...

You have quite a few beta releases in Domain Access, too -- is there a way to get rid of these after you've released?

agentrickard’s picture

I never did patch and install Subscriptions. I was doing a quick install to see what data it stored. Then I gave up -- but filed the bug report like a good Drupaler.

I did lots of beta because MySite is on release 5.x.2.15 -- that's two releases and 15 bugfixes, which means, in effect, that I didn't do enough testing.

I also tend to do point releases in batches. x.1 begets x.2, x.3, and x.4. In fact, DA rc2 has, I learned, two critical bugs in it which have already been patched and require an rc3.

Sadly, I do not think you can unpublish a release. But I suspect that is a feature request for Project module.