Can I activate for all sites in Mu setup?

Hi Drdamour,

It’s indeed possible : please see
https://www.ads-software.com/plugins/wp-ses/faq/
for the defines.

Thanks,

Sylvain

This is not resolved, i performed those steps but every site in the network still says that the ses plugin is not active. I want to activate it for every site..not just configure it. Is that possible?

Got it, see the other thread.
Will add the feature.

Done V0.3.4 :
add
define(‘WP_SES_AUTOACTIVATE’,true);

within the wp-config.php file.

Please note that this will force the activation, thus probably broking email if any setting is not correct. Use Auto activate only for WPMU installs, when you’re positively sure that all your settings are ok and tested.
Set other defines, test on a single blog of the wpmu install, then define autoactivate.

Waiting for your answer before resolving the thread.

ok, it’s a corporate blog so i’ll try it on monday and report back.

one other side issue i’ve encountered. On my first attempt i was doing stuff locally before putting it in production. First, i used the UI to set the SES keys and test everything out, then after success i switched to the defines. When i did that the ses section of the the config UI told me these values were set by the administrator. it did not display them or let me edit them.

On my second attempt in production (different WPMU instance) i just updated the wp-config with the defines right off the bat. Generally this worked, but now the SES API keys section shows the keys in the config UI for every blog. The user can edit them and save them, although the UI doesn’t show the updated values, instead using the defined values from wp-config.

Any ideas? Is there a missing entry in the DB? the emails function fine, i just wanted it to act like it was in the first set up, with a message indicating that the setting was defined in the UI.

this worked. RE: my issue, i found that if i moved my define statements up above the security defines in my wp-config my error went away. Is this a known issue?

thanks! this issue is now resolved.

Nice to know it’s solved.

I wasn’t aware of the issue about the location of the define within the config file. Good to know.