ac4lt

What I did was just a hack to avoid the error. According to the author, the includes of those files were a mistake and he uploaded a new version which should be fine. If you re-download the plugin, you should be ok now (though I haven’t had a chance to verify that myself).

If you create two empty files, filters.php and functions.php in the plugin directory, you can eliminate the warnings.

I posted a bug report on the author’s google code page for the plugin (https://code.google.com/p/wp-geo/issues/detail?id=72). Hopefully he can eliminate the warning in future versions but for now, it’s fairly easy to stop the warnings.

Looks like adding:
. ” ” . $sort_order
at the end of the query construction on line 106 does the trick.

I’m a native English speaker. Or at least what passes for English in America. ??

Our site isn’t live yet and we’ve decided to use the Event Calendar plugin for WP rather than import events from Google Calendar with RSS so this is much less of an issue for us, but I’m happy to help debug things.

In our test site, we currently have:
Akismet
Audio player
Automatic Timezone
Blogroll Links
Blubrry Powerpress
cforms
Event Calendar
Flickr Photo Album
Get Recent Comments
pageMash
Wordpress Automatic Upgrade
WordPress Database Backup
WP Geo

However, at the time the error happened it was almost certainly a different set as we’ve been trying different plugins to see what works best for us.

Looks like something similar is happening again:

Fatal error: Cannot use string offset as an array in /home/equality/public_html/wp/wp-content/plugins/advanced-rss/jp-advancedrss.php on line 113

I hadn’t changed anything and it had been running fine for the last week. I went to edit an article and was hit with this. Only way forward was to move the plugin directory out of the way.

I’m not sure what instigated the situation, but I think I can describe how it happened.

I changed an option in the widget. I think I cleared the title checkbox, but I’m not certain. After saving, wordpress wouldn’t display pages. I was too sleepy to capture the error so I deleted the plugin directory and wp was restored to normal function.

A day or two later, I tried reinstalling the plugin and this error resulted. I was able to work around by going into the database and delete the widget. Hopefully your fix will prevent it from happening in the future.

I’m going to investigate how I made it happen to see if I can reproduce the root cause, but you may want to take a look at what happens when you clear the title checkbox. I’m not certain that’s what I did, but I think it’s the most likely candidate.