mvctemplate

ended up using ‘WP Mail SMTP Plugin with Email Logs’ which meets all my needs

ended up using ‘WP Mail SMTP Plugin with Email Logs’ which meets all my needs.

Hi no one responded, but i got this plugin and some article i was reading that i cant find now says this does support multi site. I can see no way to do that, and after configuring one site, it simply asks me to configure the next one.

I mean i appreciate that you can have individual settings for each, but that is not what i want. Can you add a Q&A link with whether your plugin in multi site supported? and if you can answer this message as well.

really sucks because i spent an hour or two getting it working and then couldn’t make it work with multisite. This is about the 5th plugin I tried and the first one that i got successfully configured so sad it does not work multi site. let me know thanks.

All fixed. The problem was symlinking the wp-content directory out of document root.

I did an end run around this, by using vhosts in the apache config to just re map the whole website to the directory (on EFS storage) avoiding symlinks entirely, and thus the problem. Gallery now works, and is in the correct presentation.

And i can move another website to the cloud. yay.

Sorry i dont have more useful information for you guys, but it is an old version and i believe you did fix this “bug” with symlinks already, so i wouldn’t worry too much about it.

I left the half fix above in the code because hey, it works so i am not going to touch it anymore.

actually, doing what was suggested (although not explicitly, has fixed the problem somewhat. Unfortunately, it just makes a vertical stream of images as opposed to a “cloud” as what was on the live site. The (half fix) was to add:

$retval = $this->object->get_registry()->get_module_dir($module) . '/' . $settings->mvc_template_dirname . '/' . $path;

in place of lines 242-247 in the file “\wp-content\plugins\nextgen-gallery\products\photocrati_nextgen\modules\mvc\class.mvc_view.php”

Not ideal, but it does kind of work! not sure if that helps solve the problem though. The file does not exist in the updated plugins that broke the site (I kept a backup of the changed files and dont see a file at that path. So perhaps the entire structure of the plugin was changed in this component.