Support #20863
closedEvents Calendar plugin and Rest API
0%
Description
This is from Nate Cooper:
The plugin The Events Calendar is giving me an error. I've attached the screenshot. Here is the link to the errror
My developer that is helping me with this said:
I’ve switched themes (tried two different ones), disabled all plugins, saved the permalinks, changed them, and saved again—following all the debug recommendations from the Events Plugin’s FAQ. Despite all this, I’m still seeing the issue with ' Warning: The Events Calendar REST API endpoints are not accessible !'This is a bit challenging for me without access to edit the files. I think it might be caused by another plugin active at the network level. Do you know of another website that uses this same plugin?
If you have any example sites using this plugin on the commons or any tips as to why we're getting this error it would be much appreciated.
----------------------
I did see this - https://wp-eventmanager.com/product/rest-api/ Not sure if this helps
Files
Updated by scott voth 3 months ago
- File error-sep-2.png error-sep-2.png added
attached error message
Updated by Raymond Hoh 3 months ago
If I navigate to the REST API URL posted in the screenshot, it is browser-accessible.
The notice is a false positive. Other users have experienced the same issue over on the wordpress.org forums: https://wordpress.org/support/topic/rest-api-access-warning/.
It looks like there is a new version of The Events Calendar (v6.6.3) that will look to address this:
Fix – Update the logic that displays the “REST API blocked” banner to reduce false positives. [TEC-5105]
We will be updating to this version next week. In the meantime, they can safely ignore this notice.
Updated by Raymond Hoh 3 months ago
I did notice a 404 problem on the kccedevents site with The Events Calendar on single event pages.
The issue was The Events Calendar did not complete their database migration properly and was missing a few DB tables on the kccedevents site. I forced the database upgrade again using the code snippet from this thread and that appears to have fixed the 404 issue with events.