Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning: Illegal offset type in isset or empty #57

Closed
lukemcdonald opened this issue Jul 19, 2011 · 11 comments
Closed

Warning: Illegal offset type in isset or empty #57

lukemcdonald opened this issue Jul 19, 2011 · 11 comments
Labels

Comments

@lukemcdonald
Copy link
Contributor

I've recently had two people come to me about an issue when using the Options Framework Plugin and my theme. Apparently, when they are getting the following warning on the theme options page:

Warning: Illegal offset type in isset or empty in /.../wp-includes/pomo/translations.php on line 59

Line 59 has something to do with the translate_entry() function. Both sites with these issues are in another language.

Any ideas?

@devinsays
Copy link
Owner

Have you been able to re-create the bug?

If so, perhaps e-mail me a copy of the theme and let me know what language it was in and I can take a shot at troubleshooting it. devin[at]wptheming.com

@lukemcdonald
Copy link
Contributor Author

Email sent...

@lukemcdonald
Copy link
Contributor Author

Any progress on this? I only ask because I just got another support questions regarding it... from a French user translating WP. Below is his comment and a link to his screenshot for reference.

"I've got this message when I "Save option" in "theme options" the options are changed but i've got that:"
http://d.pr/rPtC

@devinsays
Copy link
Owner

I installed a French version of WordPress and tested with Options Check. It runs fine.

Can you reproduce the bug locally? If so, can you e-mail me the files and steps to reproduce- otherwise there's not much I can do.

@lukemcdonald
Copy link
Contributor Author

I'll give a shot when I have some time. I know the plugin runs fine, I think they are just seeing the warnings. If error reporting is enabled on their hosting server or WordPress, I'm guessing that is why they are seeing the warnings. Not real sure right now...

@devinsays
Copy link
Owner

Any updates on this Luke? I'm probably going to release a new version in the next week or so.

@lukemcdonald
Copy link
Contributor Author

No, I haven't had a chance to try things out. So far, I've probably had a handful situations regarding this. I'm not sure what it could be, it could be anything. I think it can wait to be looked into or maybe just noted as it doesn't seem to affect anything as far as functionality goes. It's more of a warning that appears for users.

@lukemcdonald
Copy link
Contributor Author

Just got another one of these. I'll have to take a look into this for sure. Apparently, each time they try to update the options, they get the warning. In this case, it was after this latest update. v0.9.

@devinsays
Copy link
Owner

If you can recreate the steps to reproduce it, I'm sure we can tackle it.

@lukemcdonald
Copy link
Contributor Author

I think I have this figured out. The theme was trying to translate a variable that was an array.

@devinsays
Copy link
Owner

Ah, that makes sense. Thanks for closing the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants