index.php is not a valid MVC template

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.

@mvctemplate – There have been a great deal of changes to the plugin since the version you are referencing as your starting point. Also to note, we are only the author of NextGEN Gallery from your referenced list (some of which I am not familiar with and others are no longer supported to the best of our knowledge which may be contributing to the issues you are seeing).

Also, migrating to AWS may be creating other issues although as it is, we do support current releases of our plugins and as such you may need to be updated to the latest release before we can offer much in the way of suggestions to look at for additional troubleshooting.

Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?

If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.

Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.

If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.

Thanks!

– Cais.

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.

@mvctemplate – Thanks for the follow-up!

– Cais.