what does that error look like to you? It looks like a plugin issue to me.
Why?
Because WordPress doesnt install any directories named images and it also doesnt drop an index.php into any directory named images
disable that plugin you are using for your image gallery and I bet the error goes away.
After you’ve done that, you might want to contact the plugin author at his/her site ..and ask for some frther assistance, or maybe there’s even been an upgrade.
Like i said, this is content meant to be outside of WordPress. I manually created those directories, and created that index.php for other purposes. All plugins were disabled for the upgrade, and have not been re-enabled as of yet, and I only have a few to begin with like Akismet, WP-DB-backup, and ZenPress (not affiliated with the images directory).
Basically, the index.php is a file that does a real basic list of the files in that directory, in this case, images. It adds downloading functionality and some other stuff custom for the site. In no way is that page or index.php called to from WordPress.
The page mentioned uses a
function translate($string)
which seems to be interfering with the WordPress
function translate($text, $domain) {
global $l10n;
in the l10n.php file, but like I said, this shouldnt have anything to do with WordPress, and why they are even trying to do anything together is beyond me. It worked fine with 2.1.3, but not 2.2.
