@billsmithem – We do not see this issue when testing with WordPress installed in sub-directories … or are you referring to the WordPress URL and Site URL addresses being different (an issue we are still working on)?
– Cais.
@billsmithem – Yes, in some instances NextGEN Gallery just will not work under those conditions (and as I noted, we are still trying to sort those out). Is it possible for you to set those addresses to use the same URL?
– Cais.
LOL… I’m not going to move 20+ websites because you can’t figure out the correct path to the WP install. If I have to go through that much work I’ll just ditch NG and look for something more stable.
@billsmithem – I wasn’t asking you to change all of your sites, just one you are having the issue with as a test for your instance(s).
If that is too much work, I can fully appreciate you not wanting to do it … or to try it … I’ll note this report of different URL addresses without any additional details.
Thanks!
– Cais.
Since we always use subdirectory installs, Thickbox has stopped working on every site that uses NextGen. The issue is the same on every one – NG is using the Site Address instead of the WordPress Address to locate the thickbox.js script.
I have copied the thickbox folder, /wp-includes/js/thickbox/, to the root and it works just fine, but I really would prefer not to have to do this on all the sites. The only thing wrong is that your code has started looking for it in the wrong place.
and by copy to the root, I mean I’ve duplicated the entire path where it would be located were WP installed in the root directory.
@billsmithem – Thank you very much for that troubleshooting and the specific example of an issue (with Thickbox). I will pass this along to our developers so they can review it against their current corrections to address the issue with paths as may be related to this differing URL address issue.
– Cais.
