Need help with SQL in CB Queries

I want to set a dropdown field 'cb_logousage' to a certain value upon registration, depending on member's plan and if they check a checkbox 'cb_applylogo'.

I did a test using simple SQL as follows and it works:
The above code set the field 'cb_logousage' correctly. Then I add more condition to limit by plan ID and it doesn't work anymore:
Basically everytime I add condition from table jos_cbsubs_subscriptions the SQL stops working. I copy-paste the SQL to phpMyAdmin (supplying user_id manually) and it works.

Perhaps anyone can spot something I missed?

CB Queries is depreciated, please upgrade to CB Auto Actions. If you need this for CBSubs then you should add it directly to the plan that you want it applied to using CBSubs SQL Actions. Due to the order of execution it's likely the plan is not becoming active or inserted into database at the time you're executing your query.

I think you're right, the trigger was executed before subscription record was created. I'm moving the SQL to Integrations > SQL Actions now.

Another question, what triggers 'Deactivation' in CBSubs > Integration > SQL Actions? Must it be triggered from the front-end? I tried to set subscriptions to Inactive and Unsubscribed at backend but the deactivation SQL was not executed.

Does CB Auto Actions work with CBSubs 1.1.2 and CB 1.4? I know that ideally both should be upgraded but it's up to my client to decide.

Another question, what triggers 'Deactivation' in CBSubs > Integration > SQL Actions? Must it be triggered from the front-end? I tried to set subscriptions to Inactive and Unsubscribed at backend but the deactivation SQL was not executed.

Editing a subscription from CBSubs > Subscriptions won't fire triggers. It's a direct database edit. To have triggers you'll need to edit them from CB > User Management and expire them properly.

Does CB Auto Actions work with CBSubs 1.1.2 and CB 1.4? I know that ideally both should be upgraded but it's up to my client to decide.

Nope, you should upgrade both. I recommend stressing the importance of maintaining up to date releases to your client. At any rate I can't guarantee what will and will not work on your releases unfortunately as both are quite significantly out of date.

krileon wrote: Editing a subscription from CBSubs > Subscriptions won't fire triggers. It's a direct database edit. To have triggers you'll need to edit them from CB > User Management and expire them properly.

I tried that as well, setting the user to 'Unsubscribed' but the SQL didn't fire either. I'll try again. But I don't see option to expire the user in the User Management, only 'Unsubscribe' and 'Delete'. How do I manually expire a user?

Nope, you should upgrade both. I recommend stressing the importance of maintaining up to date releases to your client. At any rate I can't guarantee what will and will not work on your releases unfortunately as both are quite significantly out of date.

Yeah, I guess that's on their to-do list. We did talk about it before.

When we upgrade, will the current plugins still work? Otherwise we need to shut down the site until I'm done migrating whatever it is that needs to be migrated (like CB Queries to Auto Actions, etc).

I tried that as well, setting the user to 'Unsubscribed' but the SQL didn't fire either. I'll try again. But I don't see option to expire the user in the User Management, only 'Unsubscribe' and 'Delete'. How do I manually expire a user?

Unsubscribed should do the trick, but believe you'll need to setup your usages to use the Cancelled usage instead of just Expired. For example with SQL Actions you'll want to setup "Deactivation".

When we upgrade, will the current plugins still work? Otherwise we need to shut down the site until I'm done migrating whatever it is that needs to be migrated (like CB Queries to Auto Actions, etc).

Don't know what all you've installed, but they should still work; I can't make any guarantee for depreciated projects though as I didn't test them on CB 1.8.