Thesography 1.0.1 Support
This page is intended for feedback and questions for Thesography version 1.0.1.
Website of photography loving, mac-using, Christian molecular biology graduate working in web design.
This page is intended for feedback and questions for Thesography version 1.0.1.
{ 4 comments… read them below or add one }
Hi, Kristarella,
First some fan mail. I continue to really enjoy the mini skin, and have a link in the footer section of my blog as an attempt to continue to say thank you.
As for Thesography, I attempted to install it today, and it crashed my admin panel completely. Steps I took:
1) Uploaded thesography folder to wp-content/plugins/
2) Clicked “Activate” to activate the plugin.
The admin panel crashed at that point. The site was still up, but anything in wp-admin was unreachable. I deleted the thesography folder, and the wp-admin returned to being usable.
The error messages seemed to include some version of a username, so I’m editing the folder name rather than open myself to vulnerability from any internet thugs – but if you send me an e-mail I can return the specifics. The part I’m altering are bold italics.
Here’s the result of attempting to browse to anything in wp-admin:
Warning: Illegal offset type in isset or empty in /home/content/a/b/c/abc123/html/wp-includes/l10n.php on line 436
Warning: Illegal offset type in /home/content/a/b/c/abc123/html/wp-includes/l10n.php on line 437
Warning: Illegal offset type in /home/content/a/b/c/abc123/html/wp-includes/l10n.php on line 439
Fatal error: Call to a member function translate() on a non-object in /home/content/a/b/c/abc123/html/wp-includes/l10n.php on line 59
Any ideas?
James — re: Mini: Thanks! Much appreciated.
I have no idea why these errors are happening, but it’s not the first report of admin going awry and this plugin seeming to be the cause. I’ve also heard of these errors before, but I didn’t think they could be caused by Thesography because the current version of Thesography doesn’t use internationalisation. I will investigate as soon as I can and let you know when it’s fixed (if I can duplicate the problem). I haven’t even looked at WordPress 2.9 yet (shabby, I know, but I was without internet for a month and haven’t got around to it yet) and that’s when the issues started, although some people have no problems so I wasn’t convinced there was one. If you see an upgrade to the plugin in your dashboard it should be a fixed copy for 2.9.1.
James — There should be an update of the plugin coming through any time now and those errors should be fixed. Please let me know if they aren’t or if you come across any other errors.
Also, thanks for posting your question in the right place!
You bet! I’m off to try a fresh install. Thank you!