Forum Replies Created
-
Posts
-
Changing the slugs is not an option. This used to work flawlessly using the same slug. It makes no sense that it would just stop working. I’m also not the only one reporting this issue.
I didn’t find the source of the issue. I just found the source of the PHP error messages. I’m still getting the 404 page which is the main issues. I’ll address the issues with the agenda view once the 404 issue is resolved.
I deactivated all plugins, cleared the permalink cache and I’m still getting 404s. I have determined that the following PHP errors are coming from the “The Events Calendar: Agenda View” plugin. Deactivating that removes the errors. There is not update for that plugin. How do I resolve that?
Notice: /nas/content/staging/canalside/wp-content/plugins/the-events-calendar/src/deprecated/TribeEvents.php is deprecated since version 3.10! Use Tribe__Events__Main instead. in /nas/content/staging/canalside/wp-includes/functions.php on line 3966
Notice: /nas/content/staging/canalside/wp-content/plugins/the-events-calendar/src/deprecated/Tribe_Template_Factory.php is deprecated since version 3.10! Use Tribe__Events__Template_Factory instead. in /nas/content/staging/canalside/wp-includes/functions.php on line 3966
I’m concerned that this is still happening on a default theme without any plugin except for the tribe plugins (The Events Calendar, The Events Calendar Pro).
Would it be helpful if I package up the site and database so you can install on your end?
No changed to the plugin code. The “Week Starts On” is set to Sunday. Still getting a 404. I have also fully deleted The Events Calendar and The Events Calendar Pro plugins and replaced them with freshly downloaded versions and I’m still getting the same errors.
I’m also seeing these errors in the admin section
Notice: /nas/content/staging/canalside/wp-content/plugins/the-events-calendar/src/deprecated/TribeEvents.php is deprecated since version 3.10! Use Tribe__Events__Main instead. in /nas/content/staging/canalside/wp-includes/functions.php on line 3966
Notice: /nas/content/staging/canalside/wp-content/plugins/the-events-calendar/src/deprecated/Tribe_Template_Factory.php is deprecated since version 3.10! Use Tribe__Events__Template_Factory instead. in /nas/content/staging/canalside/wp-includes/functions.php on line 3966
Notice: /nas/content/staging/canalside/wp-content/plugins/the-events-calendar/src/deprecated/TribeEventsAPI.php is deprecated since version 3.10! Use Tribe__Events__API instead. in /nas/content/staging/canalside/wp-includes/functions.php on line 3966
This tells me that it’s not a theme issue.
I have updated all plugins and WordPress and I still have the same issue. I turned on WP_DEBUG AND WP_DEBUG_LOG. Turning on WP_DEBUG shows these two errors:
Notice: /nas/content/staging/canalside/wp-content/plugins/the-events-calendar/src/deprecated/TribeEvents.php is deprecated since version 3.10! Use Tribe__Events__Main instead. in /nas/content/staging/canalside/wp-includes/functions.php on line 3966
Notice: /nas/content/staging/canalside/wp-content/plugins/the-events-calendar/src/deprecated/Tribe_Template_Factory.php is deprecated since version 3.10! Use Tribe__Events__Template_Factory instead. in /nas/content/staging/canalside/wp-includes/functions.php on line 3966
I would like to point out that the theme that is currently being used while figuring this out is twentysixteen, so none f my custom code from my theme is being used. This also means all Tribe Event templates are being used from the plugin.
I have done all of this and stated this in a previous comment. As I have also stated, this worked before and there have been no changed on our end with the site. I am the theme developer and I followed the customization process that is outlined on your site. If I had to guess, something changed with how the plugin is creating re-writes.
As I stated before, when I reverted back to a bare bone WordPress theme, the week pagination worked, however it only worked with JavaScript. If I went directly to a URL with a specific starting date for a week, still using the bare bone (twentysixteen) theme, it did not work. I have followed all of the troubleshooting step that are outline on the tribe site and have stated that. To be honest, I’m getting frustrated that you are just recommending that I keep doing the things that I have already told you I have done.
If you would like, I can provide WordPress and FTP access to the staging site. Please advise.
But the issue is that it worked before and this site has been up for years. If I changed it, I would have to create bunch of 301 redirects. My issues is also not resolved becuase I want and need the slugs to be the same. How would it redirect to the same page? Can’t the plugin tell what is a single post vs an archive page? It’s just a CPT. I know the week view has /week, but but all of the single views should be able to use the same slug.
Changing the single slug allowed it to work, however I want both of them to be the same. This was never an issue before, why is it now?
I have gone through all these steps already. Flushing the permalinks was my first thought, didn’t do anything. THe permalink structure I’m using is post name.
I have changed the site to use the twentysixteen theme. As I stated in my original post, the ajax functionality works, even though I have that unchecked. It seems that that plugin JavaScript is changing the URL. When that happens, try reloading the page with the a future week starting date, it gives a page not found error.
That checkbox is already unchecked. As I said, this worked before. You can see it here http://canalside.staging.wpengine.com/things-to-do/week/.
The web server and database server are separated. When the DB server is being maxed out, the web server is fine. I only showed you one small sample set of the queries going on in this 15 min window. there are thousands more. There is no way that the traffic on the site is generated all these queries. Like I said before, I’m not blaming your plugin, but a lot of the queries seem to be related to the events plugin. I’m just going to disable the wp crons right before this normally happens, and test my theory that it is the crons. I’m going to close this issue, since I feel that I will have to dig deeper into my site to see whats going on. Thanks for the help!
