mpp32

I have the same issue. How was this resolved?!

This isn’t helpful. Why is this post being mixed up with that of andromeda555?

I am obviously anxious to get this resolved quickly as I have an otherwise working site with NGG integrated that cannot go live on the web host and NGG is the only plugin in the way since I cannot even customize any theme as get this runtime error even on a fresh generic install.

Thinking more about this, the required modules are not loading because of the error which seems to result from looking up the full physical absolute path including full server name to the files at runtime. Why would this even be necessary? And if necessary, something goes wrong in picking up this path. With the proper knowledge, it seems like an easy fix – likely with respect to the module: /wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/mvc/package.module.mvc.php

If this is a similar issue to https://www.ads-software.com/support/topic/solutions-to-missing-leading-slash-in-urls then to clarify, I am not using the Roots theme and I also tried to role back to NGG version 2.1.23 with the code modification (Solution 2) given by rrhode in that post – but no difference.

By the way, I submitted my bug report yesterday including my Overview server settings and I did not receive any confirmation that the bug report was received. I only received confirmation of subscription to Imagely as a result. I’m not sure what the process is.

I would be happy with even a temporary workaround i.e. code substitution as I don’t really want to rework my site with a different image plugin. Thanks.

Thanks Cais,

@andromeda555 ????

I just submitted the bug report to expedite a solution. However to address your response: It appears that NGG does not load properly as the relevant files are not being loaded. Given that the runtime error shows the full absolute server path instead of the URL and that the leading slashes are missing from the server path in the message – I suspect the problem is similar to what rrhode reported here: https://www.ads-software.com/support/topic/solutions-to-missing-leading-slash-in-urls?replies=5. I guess I missed this post previously, but since you recently commented on this post – it seems like we’re on the right track. However the solution that rrhode offered – to modify the file: /wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/mvc/package.module.mvc.php and change the line: return $retval; to: return ($retval[0] != “/”) ? “/” . $retval : $retval;

…did not work for me as I just tried it. I don’t know enough of php to customise this further in a proper way. However, I believe the issue is in there somewhere.

Also to clarify:
As I point out in my original post, initially this was not a clean install but a migration of well running site on a custom theme and including the same version of NGG running on my windows pc. However, after dealing with this error for over a week and trying every suggestion offered online, I tried it with a clean install but still with the same result. It’s odd what you said that server issues arise on clean installs with default Twenty series themes. It would seem that if you take out complexity and limitless variables and remain with the simple default settings, this would have the highest probability of a successful install. I should assume that such a simple default scenario would have been tested and addressed long ago.

I hope this and the bug report can lead to a quick solution – thanks!

Further to my post above, I mentioned that in the error message the server name path – UNC name was missing the 2 leading backslashes. As such, that means that the entire link is invalid and cannot be found.

I have been working with my web hosting company support and the tech told me that he followed this so far up to the function find_template_abspath in file package.module.mvc.php.

This function calculates the absolute path to the template and seems to be stripping the leading slashes from the path.

Please advise – thanks!