[thecolumbian]

Thank you for your response, Jaime. Unfortunately, none of that worked so I went ahead and created a new dev site doing only the following:

– I installed WordPress added nothing to it.
– I installed The Events Calendar, Events Calendar Pro, Community Events, and Query Monitor.
– I changed the WP default setting in Settings > Permalinks so that the calendar would work properly.

I did install or change the default theme or install or activate any other plugins.

I went to http://mysite.com/events/community/add/ and http://mysite.com/events/community/list/ and Query Monitor still throws the exact same error. The source of this issue is clearly the events calendar plugin, possibly in either the-events-calendar/src/deprecated/Tribe__Events__Asset__Ecp_Plugins.php or the-events-calendar/src/Tribe/Assets.php.

[thecolumbian]

I did this on both my dev site on my localhost server and my live production site with no avail.

[thecolumbian]

Thanks for response, Jaime.

I deleted the Events Calendar, Events Calendar Pro, and Community Events plugins then threw the filesets of each after downloading fresh copies into my plugins folder then activated them. The issue still persists in the same way it did before.

I have a separate sandbox dev site on a local VM and I just installed the three plugins and visited the “Add New Event” Community Events page and I got the same “Missing Dependencies” error produced by Query Monitor, saying it’s missing “ecp-plugins”.

[thecolumbian]

I appreciate it, Cliff. I’ll stay tuned.

[thecolumbian]

If this helps anyone while this fix is still pending, here’s a quick solution to temporarily redirect traffic from your site’s home page to the properly working first page of events (place in your active theme’s functions.php):

// temporarily redirect front page to currently better working version of events list first page
add_action( 'template_redirect', 'redirect_home_page' );
function redirect_home_page(){
	if( is_home() ){
		wp_redirect( '/events/list/', 302 );
	}
}

[thecolumbian]

Just for reference, I went ahead and tried downgrading my version of ElasticSearch from 6.3.2 down to 6.2.0 because of the warning that ElasticPress was giving, saying that my version was above the maximum required Elasticsearch version of 6.2. I reindexed and unfortunately the problem still remained.

[thecolumbian]

In addition, I also get the same behavior when using the tribe_get_events() function.

[thecolumbian]

That actually seemed to be do the trick. Thanks for your help!

[thecolumbian]

Thanks for your response, Cliff.

After turning on WP_DEBUG_LOG, I noticed it did not record any errors. I threw a bad line of code in my theme’s functions.php file and it did record that error to my debug.log file, so it does look like it’s logging properly.

One thing I just discovered is that when trying to pull up the Community Events front end pages, it’s actually throwing a 404.

I’m running Elasticsearch 6.3.2, which at the time of this writing is above ElasticPress’s required maximum version of 6.2, so that may or may not be a/the culprit. I can try downgrading my version somehow if you think that might make a difference.

[thecolumbian]

It’s been a couple weeks; any updates? Thanks! 🙂

[thecolumbian]

I appreciate it! I look forward to hearing back from you with a solution. 🙂

[thecolumbian]

Went through those instructions with no avail. I did a file comparison between a fresh copy of wp-login.php downloaded from wordpress.org and the copy on the server and they were exactly the same.

[thecolumbian]

I fixed the PHP error in themes/blankslate/tribe-events/modules/meta/details.php, which was minor and I really don’t think it was causing the login page issue.

I temporarily removed my login page customizations and it didn’t appear to work any differently.

[thecolumbian]

This reply is private.

[thecolumbian]

I’ll send you some temporary login creds in a separate reply. I did just try to login via the community events plugin’s login page and it would not let me in and also didn’t even throw an error message. Again, like I said, this is happening really intermittently.

I have turned on the WP_DEBUG and WP_DEBUG_LOG constants as you requested.

[Author]

Posts