Jose Castaneda

Hi there,

That’s a new one I haven’t seen. From taking a look at the markup I do see it’s a text widget which does add to the oddness of this. What happens if you deactivate plugins? Does that go away?

You could deactivate all plugins to see if that gets things back to working as well, if you haven’t already tried that.

Hi there,

I suggest looking at the error logs if you know where those reside, if not, you can reach out to your hosting company and ask them where they can be found. That will at least give you some idea of what could be happening and maybe crashing.

Ah ok. Disregard that. I, for some reason, thought it was a site network/multi-site installation. Those have super admin which is where my brain went when reading keymaster which is not the same thing.

Was there a recent update done to a plugin?

Are you able to search all plugins using the command line? Quick thing you might be able to do is see if there is a plugin that is potentially adding the current_user_can() or filtering that somehow with user_has_cap. Could maybe run something like:

grep -nr 'current_user_can' wp-content/plugins
grep -nr 'user_has_cap' wp-content/plugins

If a plugin is using either one of those it will be listed with the path and line number of the file it is on.

It sounds like it’s a multi site installation, correct? If that’s the case does that also happen across all the sites or just one?

If not, when did that first appear or first notice that? After an update?

Hi there,

Had to look this up for myself because curiosity and I do see they have some discussions: https://github.com/jeffreyvr/tailpress/discussions

I think the repo (https://github.com/jeffreyvr/tailpress) might be a slightly better read for me. I do see that you can run a npm run production script that will give you what you need to push to the live site.

Hopefully that helps a little bit.

Awesome. Happy to hear that

Ah, ok. So you’re using a local installation at the moment. Got it.

So, one thing that comes to mind would be adding a random .git or a .svn folder at the root of the install (where you have those wp files) so it doesn’t update it. WordPress does check if it is being version controlled from what I can recall and won’t run those if it is using version control. The other might be to change the folder/file permissions so it doesn’t run an update for core files. That I can’t recall how to do on a local Windows installation since it’s been many, many years since I had to do that.

There are 3 that are being passed. The docs page I linked shows what they are as well. The inline docs also let you know what ones are passes:https://github.com/WordPress/wordpress-develop/blob/6.2/src/wp-login.php#L1277-L1277

Ah gotcha. Sounds like you are trying to do this on a live site, correct? Not a staging or testing site?

One thing that comes to mind would be an auto update PHP constant that could be doing that but hard to say since it was just a simple, clean installation of WordPress, right? No other plugins?

Hi there,

There are several 4xx error messages available but all of those are client related. Are they all the same errors or is there a majority of one than others?

Hi there!

What tutorial were you following?

Also, what have you tried to resolve this so far so we don’t suggest things you have tried and didn’t work.

Hi there,

What have you tried so far to resolve this? If you haven’t already try deactivating all plugins to see if that resolves things. If that doesn’t resolve it, you can switch the theme to rule that out as well.

Hi there,

My first question is why are you looking to run on an older version of WordPress?

What does the error message say?