Problem with new update

[nothingtodo]

I updated the plugin today and it caused an error when I tried to log in ([an error occurred while processing this directive]). My host (bluehost) said it was because of the new version of the calendar and deactivated the plugin. I asked if there was some more information I could give to the developers and they pointed me towards the error log but said they didn’t actually see a problem there… Has anyone else had issues?
Sorry if this isn’t the right place to put this!

[Barry]

I’m sorry you’re hitting difficulties – no problem posting it on the forums, though I’m guessing it’s not actually an EDD Tickets issue as such?

It sounds like your host weren’t too forthcoming with information, here, but did they offer any insight into why they though our plugin was doing this, given nothing relevant shows in the error log?

Can I also ask if you had any recurring events in place prior to updating and approximately how many/what percentage of your events would have been accounted for by recurring events?

Thanks!

[nothingtodo]

Don’t get me started on the customer service I get from my hosts. They asked what happened before I was locked out of the admin panel and I said I had updated the plugin so they assumed that was the problem. They didn’t have any information but I did save the error log if that would help.
I have a lot of recurring events. Maybe 25 – 30% of my events are recurring. That’s what tipped me off to needing an update. I saw that my recurring events were posted multiple times.
I don’t know why I posted this in the EDD Tickets area! Oops.

[Barry]

No problem about posting here – normally we’d move it but we’re having a few issues with our support tools at the moment and really I just wanted to make sure there wasn’t a link with EDD Tickets.

Can I roll back a step to your original post? Your wrote:

I updated the plugin today and it caused an error when I tried to log in ([an error occurred while processing this directive]).

Do you mean that when you visited wp-login.php and tried to login, an error reading an error occurred while processing this directive displayed – or something else?

Thanks!

[nothingtodo]

Right, when I tried to log in to my admin panel after updating the plugin I got the [an error occurred while processing this directive] message. Bluehost deactivated the plugin and I could get back in but without a calendar my site is basically useless so I turned it back on. Now I can’t get into my site but at least any visitors will see something rather than nothing.

[Barry]

OK – puzzling.

[an error occurred while processing this directive]

This is an error message that the Apache web server produces – why it would be triggered here I’m not absolutely sure – and if I was to offer up a guess at this point, and it really is just a guess, it would be that some extra work which needs to be done to keep recurring events created using previous versions operational with our latest version is pushing your host’s server beyond what it is configured to allow.

It seems related to reports from other users and so I’ve attached this thread to the relevant issue (in our internal issue tracker).

We’ll update you as soon as we’ve had a chance to investigate in more detail – unfortunately right now I’m not sure what else to suggest, unless you can attempt to reactivate PRO and see if it works second time round?

[nothingtodo]

I had my host shut the plugin off but I can’t access my dashboard this time.
The support person I communicated with today was much more friendly and helpful and he gave me an actual error that seems to be causing the issues.
This is the exact error its throwing now:
[02-Apr-2014 08:30:31 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘) )
) coors’ at line 15 for query SELECT Max(lat) max_lat,
Max(lng) max_lng,
Min(lat) min_lat,
Min(lng) min_lng
FROM (SELECT post_id AS venue_id,
CASE
WHEN meta_key = ‘_VenueLat’ THEN meta_value
end AS LAT,
CASE
WHEN meta_key = ‘_VenueLng’ THEN meta_value
end AS LNG
FROM uxa_postmeta
WHERE ( meta_key = ‘_VenueLat’
OR meta_key = ‘_VenueLng’)
AND post_id IN (SELECT meta_value FROM uxa_postmeta WHERE meta_key=’_EventVenueID’ AND post_id IN () )
) coors
made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/plugins/the-events-calendar/views/default-template.php’), get_header, locate_template, load_template, require_once(‘/themes/genesis/header.php’), wp_head, do_action(‘wp_head’), call_user_func_array, wp_enqueue_scripts, do_action(‘wp_enqueue_scripts’), call_user_func_array, TribeEventsPro->enqueue_pro_scripts, TribeEventsGeoLoc->estimate_center_point

[Barry]

Awesome that we got some more info this time round 🙂

I’m very sorry you’re having these issues with the plugin, though, and we do actually have this very issue logged already and a fix is in the works. I am surprised that it would prevent you from logging in, though and I wonder if some other issue is causing that.

Regrettably, I think the best advice in this case if you continue to find you are being locked out and therefore cannot manage your site is going to be to temporarily downgrade to Events Calendar PRO 3.4 and The Events Calendar 3.4.1 until we can turn out another maintenance release (which hopefully will be very soon).

On the other hand, if you feel comfortable doing so you could explore the temporary fixes/workarounds described here (same issue as you just described above – an SQL error) and here (different issue, but I suspect it may be playing a part in this). Though, failing that, downgrading may be the best course of action unless you are happy to wait a few more days in case we can turn out another release in that time – which is possible, but I can’t really offer any guarantees.

Apologies once again for all the hassle.

[Author]

Posts