Activating a plugin via a query - or how to update the cache?
 

Hello all,

I want to activate a plugin via a mySQL query, just to put up a message at a certain time, then turn it off again. I worked out how to activate/deactivate it via a query...

However, the page does't update - some sort of cache I suspect.

Anyone know how to trigger an update of the cache, or a way to achieve what I want?

Thanks.

All you are doing is single a single plugin one time via a query? Perhaps post your code and state the goal and we can see what is going on.

I just want to put up a message saying that we're closing for maintenance, then turn it off after maintenance.

The plugin is simply:

The $closemessage is placed in the template... then ideally I just want to turn that plugin on and off at the designated times.

Why are you not using the actual option to do this? vboptions > turn vb board on / off > reason for turning forum off

And why not just say:
No echo, no get_contents, just set the variable.

Because this isn't to turn the forum off, it's to give a warning that it will be turned off. So ten minutes before maintenance it lets people know and they can avoid starting to make long posts.

When the acp updates the active status of a plugin (in admincp/plugin/php) it calls vBulletinHook::build_datastore() which is in includes/class_hook.php. So you'd probably want something like:

Thanks for the response kh99.

Well, that half works! It works to turn the plugin off via command line... but doesn't work to turn it on. Any ideas?

Thanks

I don't know why that doesn't work. But I have an alternative suggestion: create a plugin (always active) using hook init_startup with code:

(all those quotes need to be there).

Then in your template use something like:

Then have your command line program write to the datastore table with title = "closemessage" and data = your message (I'm not sure if the message string needs to be serialized or not, so you'd either need to call serialize on it and write the resulting string to the db and set the unserialize field to 1, or not. I don't think it hurts to just do that even if it's not necessary).

To turn off the message you could either delete the record or set the message to a null string.

I haven't tried this myself but it seems like it should work, and I think it's less complicated than rebuilding the plugin datastore.

ETA: another idea would be to add a setting under vBulletin options (which you can do when the site is in debug mode), then figure out where to change the value in the database. That would have the advantage of letting you also set it from the acp if you wanted.