SGURYGF

….anyone?

I have excluded wp-json from the redirection and now it’s working fine!

Thank you ??

Hi Maybellyne,

That is correct.

Requesting /wp-json/yoast/v1/indexation/prepare redirects (301) to /wp-json/yoast/v1/indexation/prepare/

I see, thanks. Will take your advice and check with the debugger/tester.

Sorry for the delay, thanks for the explanation!

Some features have been removed but not all of them. Have you been prompted to a wizard after the installation? I assume you won’t see the menu unless you go through the initial setup.

@barteknguyen I was facing the same issue. After uninstalling the plugin the browser would still try to load js files from the site. I had to clear all the storage and cache data of the browser for that site to make it go away. If you use Chrome hit F12 and navigate to the Application Tab. On the left hand pane click the third option which is “Clear storage”. Uncheck “Cookies” and click “Clear site data”. This should solve your problem.

But what is the problem? As far as HTML validity, they are both correct. “http” is not needed anyway in a link. “//” represents the current scheme of your website be that http or https.

Thanks for your reply. It’s indeed safer but it affects performance which what the plugin is about ??

Maybe it has cached files from a previous version and compares to (or wrong tag). If the files on your server are the same as the ones included in the official ZIP then you are OK.

After a plugin is updated, WordFence always show the modified files. I believe that is normal.

Try disabling caching completely to see if it fixes the problem. If yes then you know what is wrong. Also please make sure you are running the latest version of this plugin.

Btw my opinion is that you should never enable caching for logged in users, no matter if they are admins or normal users and especially their sessions.

It is bad practice and will cause only problems in most cases. (not to comment on privacy issues exposing others’ personal details)

I suggest to find another solution for the server crashing problem. Maybe you should consider changing host. WordPress is a very resource hungry system. You can leverage caching in multiple layers, just not in the way you currently are.

my 2c.

That sounds odd. It shouldn’t under any circumstances show another user’s name.

Is it only the name wrong or the chat messages too?
Are you using the on-premise or cloud server mode?
Do you use any sort of caching?
Is it reproducible or random?
What version of the plugin are you using?

If you go to Settings -> Advanced Features which mode is selected? On-Premise or Cloud?

Which chat mode are you using?

There are a few other temporary solutions:

1) remove yourself from being an agent
or
b) set chat to offline from settings but this will disable chat for all agents