Cannot add new redirects, delete logs or change configuration

Are any error messages shown?

No, the only message I get says that chnages have been saved.

It seems wp rest api URL gets cached some where and it is the cause of the problem. I can work with plugin now.

It is happening again. It is strange; I think it started when I had open two tabs with the admin dashboard of the plugin. I had to log out and log in to see changes and to work again with the plugin.

It is definitely something in the JavaScript. It is crazy. Even reloading the page by clicking the “reload” button of the browser gives you different results in the admin screen of the plugin.

For example, I click on the menu item pointing to wp-admin/tools.php?page=redirection.php. I get the plugin admin screen with 119 elements. Without touching anything, I click on “reload” button of the browser, now I have 122 elements.

This issue happens also by repeatedly clicking on the plugin menu. I get different items each time I click on it.

Now, I’m not sure what I’m editing. Frustrating.

It still sounds like it is being cached

Yes, but where, why, when?

That very much depends on your server and your setup, so it’s not something I could comfortably answer. If your API is being cached then it’s something outside of Redirection, and something that will affect anything that uses the API. I would investigate any caching software you are using (both on the server and in WordPress).

I’m actually investigating it. I’m using LiteSpeed with private caching activated (it caches privately for each logged in user). I can see X-LiteSpeed-Cache: hit,private in the Redirection API endpoint. Let’s me check what happens if I deactivate that option in LiteSpeed.

Litespeed is caching the REST API responses from your plugin (privately; I have it configured to do so, and it is awesome for logged in users and wp-admin), but it seems that your plugin does not trigger any of the action hooks used by LiteSpeed to clean up the cache.

It seems both plugins need to support each other specifically.

Ok, so it sounds like you’ll need to configure Litespeed caching not to cache the REST API (or anything else in WordPress where data is changed). This is not something a plugin should do itself.

Caching REST API is a must for me, as I’m using an app and the performance is really much better when the REST API is cached.

I could configured LiteSpeed to not cache privately, so the admin backend of your plugin would not be affected, but I would lost the performance gains for logged in users in all other areas (including back and frontend parts of the site).

I really don’t like none of the those options.

So, I’m thinking about integrating both plugins. Your plugin provides some actions hooks where LiteSpeed Cache API can be integrated. I think I can do it.

I see that your plugin does not use any core object to store information, and so, when it changes, it does not trigger any core action hook used by LiteSpeed. For now, I’ve excluded /wp-json/redirection/ path from LiteSpeed cache until I have time to investigate further.