Andrea Sciamanna

> The time to check discovery would be just before sending that URL

I like the idea: I’ll use this approach!

As for the “reentrant”, I ended up by checking if REST_REQUEST is defined (which should be enough) and if it’s set to true (probably redundant).

Checking against the constant seems to be enough to avoid the problem and also makes the code more readable. Checking with is_admin, even if it may work, may look a bit out of context.

I’ve seen some discussions (I lost the URLs) where users were asking for a way to detect a REST request (as you wrote, pretty much like DOING_AJAX).
It looks like there is not much will to do so, which makes me wonder if that constant is there to stay ??

> you don’t need an active API to add a routes, only to make use of them

The reason for this whatn’s explained in my post.

This is the workflow:
– The plugin creates some “jobs” and send data to an external service, together with an URL (something like /my/endpoint/:jobid)
– When that job is completed by the external service, it will send a request to the provided URL

However, if REST API is not active, I need to inform the external service about it, so it won’t try to send these calls (which, instead, will need to be handled manually by the user).

I hope this explains why I need to run this check.

So, it looks like there was nothing wrong in there, except the fact I needed to add some checks to run the code only on back-end pages.

I was planning to do that after having confirmed that this works, but apparently, the fact that the code was always running on every request was somehow causing the timeout (though I’ve checked and saw no recursions or anything similar).

Clear: thanks!

Why is this marked as resolved? Is not.

I see that when you register the events taxonomies, you even define the ‘update_count_callback’ property: wouldn’t help to use a custom function that counts taxonomy events based on the ‘showpast’ option?

As I wrote above: I want to show a list of event categories with the number of (active/future) events for each category.

I’m sorry, but your answer doesn’t address my question.

The installer is stating that the system requirements check has failed because the root folder has writing permission?

I’ve checked the FAQ before posting my question and I don’t see this error message explained.

Could you please explain why a folder with writing permissions would be an issue?

Also, when I run the installer.cleanup.php on the other server (the one that has no issues), I get this notice:
Notice: Undefined offset: 1 in /home/sciamann/public_html/bitmap/wp-includes/vars.php on line 28

Indeed, the table is empty, for who know what reason.

But what puzzles me even more is the fact that I see one event in the events list page.

I can recreate the records in _eo_events table, but I’m worried about this visible event.

I never used other events plugin in this site and is a fresh site installation (only the DB is a copy of the old version): no plugins and the theme is the default one.

Done.

Thank you!

No problem.

Where can I send your credentials?

Hello Tobias,

Working in a local environment, I’ve eventually found out that is a theme issue, but I can’t figure out what is causing it.

If your offer is still valid, I can give you admin access or, even better, a snapshot copy of the site that you can run locally.

Hi Tobias,

Thank you for the quick answer.

It can’t be something that block uploading, as this happens with manual input as well.

Unfortunately I can’t disable plugins or switch theme, as I’m working in a team and other people must be able to keep working without me messing on the site.

I’ll try to make a local copy of the site so I can freely test.

I’ll keep you updated.