[David]

Hi Barry, I will definitely provide some info in a private post soon. as I mentioned, I was under a deadline (actually several, but only one involving EC), so it wasn’t possible for me to immediately provide you private feedback. I’ll be making a private update to this likely within 24 – 48 hours with the requested info, as I need a chance to prepare some screenshots and also try to document the changes I made.

[David]

PS – just a side thought / realization – as a host I’m growing concerned about growing number of “developers” who tell their customers that they’re using “third-party” software, when in fact that is exactly what they are as well, but moreover it’s disconcerting to see the growing number of developers that tell every user with a problem to change / blame their host. Thankfully Tribe hasn’t done that latter part, as far as I can tell, and I hope you never do. I love the quality of your products and I am in no way saying anything negative about you, I guess I’m just expressing my utter disgust of having to be the web host who wastes time for no pay to explain to customers why their 10+ plugins don’t get along. In the end us hosts almost always get blamed. It’s ridiculous the number of developers who won’t take responsibility for their either A) crappy outdated code or B) their lack of continuity and harmony with the popular plugin community. Please don’t think that I’m slagging anything toward Tribe products – clearly you guys are quality stuff. I’m just seriously having to consider telling hosting clients that “all third-party plugins are not supported” over these kinds of situations, and that’s something no hosting customer wants to hear. Kind of a bummer for all of us I guess.

[David]

That is understandable, but also unfortunate. Hopefully in two years it won’t be EC that is the bad boy like NGG is now after so many years of their plugin being reliable. This situation does leave me in a quandary and re-thinking whether I should spend the $250 on a license for something that is (at no fault of yours) not compatible with one of the most widely used plugins in WordPress history. I truly understand and appreciate your situation, as hopefully you do mine. I really don’t want to resort to a crappy free calendar, but I’ve tested a couple that don’t argue with NGG and I’m now caught in the middle of a decision that nobody would ever want to make 🙁

[David]

For Barry – you mentioned in a previous reply “we are still waiting for more information to come in since we haven’t been able to replicate it”

I can tell you how to replicate it if you have the means. Here’s what you’d need for a test bed:

Server Environment – RHEL 5 64bit, cPanel 11.38.2.x, PHP 5.4.x, mySQL 5.5x, suPHP

Software – WP 3.6x, EC 3x, NGG 2x

This would be a “current” or “modern” updated environment. As for hosts running deprecated versions of any of the above, I can’t say. I keep my servers current (but not bleeding-edge or beta).

[David]

One last tidbit, which might already be assumed – the errors are only generated in two cases:

1. When the Event Calendar pages / features are accessed by a site visitor

2. When the Even Calendar controls are accessed in the admin Dashboard

No errors are generated when visitors or admins access the NextGEN plugin controls or pages with galleries.

[David]

Correction per above – where “EX Pro” I meant “EC Pro” as in Event Calendar.

[David]

If I knew how to edit the post above, I’d also provide the short version – when NGG v2 or higher is running alongside EX Pro 3, the PHP error logs are filled with EC errors (not NGG errors). Disabling NGG appears to stop the EC Pro errors.

[David]

Guys, some troubleshooting progress:
While I cannot say 100% for certain, I believe that this problem stems from an incompatibility with NextGEN gallery version 2.0 and forward. (basically since the update Photocrati pushed out around July 30th).

On the specific site in question where I’m doing my testing, both EC Pro and NGG have been running side-by-side without issue for about a year or so, just until the last couple months (going through my error logs).

But here’s the thing – while I’m very inclined to say that the “fault” lay with NextGEN in light of the fact that their v2 update has caused a LOT of issues for many users (ones who don’t even use EC), the timing does present a *tiny* bit of doubt / hesitation to say so, because it’s also around the same time that EC Pro 3 update was pushed as well.

I’m not looking to place “blame” and I’m not hating on either product. I’m just trying to get to the bottom of the issue just like you.

So while it definitely seems to be an incompatibility with NextGEN and I’m leaning toward that plugin as the source of the problem, but NGG and EC 3 produced updates in July that coincide with the timing of this issue cropping up.

For those of us who work for clients that depend on both plugins, this is a dilemma 🙁

I can’t exactly tell my client to stop using NGG (nor would that be practical), and at the same time I would lose face by saying that EC 3 Pro doesn’t play well alongside it.

So, that’s the best I have so far… with NGG 2.x enabled EC Pro definitely generates PHP errors in the main folder and admin folder error_log files (eg: /public_html/error_log and /public_html/wp-admin/error_log) on servers that are set to generate those logs into the hosting account.

What a dilemma. Clearly EC Pro is a beautiful product and very powerful, but likewise NGG is something a LOT of WP users have relied on for many years. Asking a client to give one plugin up to save the other is a conundrum.

Thanks for your attention to this, much appreciated. Any recommendations other than telling clients to give up their hard-earned/worked NGG galleries in favor of getting rid of EC Pro PHP errors?

[David]

Hi Barry, thanks for the responses. I haven’t had the chance to do all the troubleshooting / tests I’d planned on – I got busy with another client deadline job and a ton of support work to do. I DO plan to do a full session of testing asap and will report the results to you here as soon as I can. It is equally as important to me as I’m interested in upgrading my license from “Business” to “Professional” very soon.

[David]

Well after some searching it turns out that this seems to be the ONLY thread on the entire web (via Google) that contains all of these words – “WordPress database error Unknown column tribe_event_duration”
So considering that, and the fact that the message filling up the WP error_log file is *extremely* similar to the message zacheryh is getting, and the problem started for both of us just recently in August, I guess I should add to this discussion. (If not, then moderators please delete my posts and instruct me to start a separate thread if you wish).

So this is currently what is repeating over and over in my WP error_log file:
[12-Sep-2013 01:41:13 UTC] WordPress database error Unknown column ‘ids’ in ‘field list’ for query SELECT DISTINCT ids FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) INNER JOIN wp_term_relationships AS tt1 ON (wp_posts.ID = tt1.object_id) INNER JOIN wp_postmeta ON (wp_posts.ID = wp_postmeta.post_id) AND wp_postmeta.meta_key = ‘_EventStartDate’ LEFT JOIN wp_postmeta as tribe_event_end_date ON ( wp_posts.ID = tribe_event_end_date.post_id AND tribe_event_end_date.meta_key = ‘_EventEndDate’ ) LEFT JOIN wp_postmeta as tribe_event_duration ON ( wp_posts.ID = tribe_event_duration.post_id AND tribe_event_duration.meta_key = ‘_EventDuration’ ) WHERE 1=1 AND ( wp_term_relationships.term_taxonomy_id IN (8) AND tt1.term_taxonomy_id IN (8) ) AND wp_posts.post_type = ‘tribe_events’ AND (wp_posts.post_status = ‘publish’) AND (wp_postmeta.meta_key = ‘_EventStartDate’ ) AND ((wp_postmeta.meta_value >= ‘1119-12-01’ AND wp_postmeta.meta_value = ‘1119-12-01’ AND wp_postmeta.meta_value <= '1119-12-31' ) OR (wp_postmeta.meta_value = ‘1119-12-31’ )) ORDER BY DATE(wp_postmeta.meta_value) ASC, TIME(wp_postmeta.meta_value) ASC made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/MyTheme8/page.php’), get_template_part, locate_template, load_template, require(‘/themes/MyTheme8/content-page.php’), theme_get_content, apply_filters(‘the_content’), call_user_func_array, TribeEventsTemplates::load_ecp_into_page_template, tribe_get_view, do_action(‘tribe_events_before_view’), call_user_func_array, Tribe_Events_Month_Template->setup_view, Tribe_Events_Month_Template::get_daily_counts, TribeEventsQuery::getEventCounts, WP_Query->query, WP_Query->get_posts

(I changed the name /MyTheme8/ since the theme includes a client username that I’d like to keep private).

The only thing I’ve ruled out for sure so far is the server – I am only currently running two of my EC Pro licenses on two WP sites, both are on the same together and both are running basically the same themes and settings, so I’m a bit mystified at this point and preparing for some unexpected troubleshooting tonight.

[David]

My apologies – looks like my problem is VERY similar to zacheryh’s problem, but not exact…
Going to do some more searching and testing. Will look for existing thread or start a new one if I find the *exact* issue I’m hitting.

[David]

This reply is private.

[David]

I’m running into this same exact issue and it’s filling up the PHP error_log log file that PHP generates on the server (for example – /public_html/error_log) repeatedly, bloating the error_log to a whopping 3.5MB (yes, 3 megabytes) and it is just a simple text file.

I only run 6 other plugins, basic and common ones (Contact Form 7, Really Simple Captcha, NextGen Gallery, Akismet, Ultimate TinyMCE, WP Render Blogroll Links) on the particular WP site I’m seeing this on, so I’m about to go through and disable plugins one-by-one and changing to default WP themes as a start to troubleshooting.

Will respond back here with any findings.

[David]

I’ve run into the same exact problem and tried the solutions suggested in this thread but no luck. Exasperated and tired, I’ll try again tomorrow.

[David]

Barry – feel free to remove all of my posts from this thread to keep it clean for you and Doug. Sorry about that!

[Author]

Posts