fogger

I had forgotten: Because of the cookie query, the Matomo code was stored in my privacy plugin. I deleted it there and the problem is solved. A stupid mistake on my part. Sorry for the alarm.

Hi @properlypurple as I wrote above, the effect occurs with all browsers on iPad. The iOS used is iPadOS 17 (meanwhile 17.0.2).

I have tested it with:
Firefox 118.0 (34465)
Google Chrome 117.0.5938.117
Microsoft Edge 117.0.2045.42
Safari (included in iOS 17)

PS. If the effect does not appear immediately on first load, refreshing the page (dragging down) is sufficient to trigger the rendering error.

Of course, it looks like this on the productive website:

And it’s the same with the bare Theme on https://wp-themes.com/twentyfourteen/ :

If it had been an issue or conflict that only affected my site, I probably wouldn’t have posted it here.

PS. Sometimes the effect occurs only after a reload of the page. But it is definitely reproducible.

• This reply was modified 1 year, 2 months ago by fogger.

I have now temporarily solved the problem with a permanent redirect from /wp-login/ to the start pages. However, I would like to know where this login under /wp-login/ comes from. I couldn’t find any references to it in all of my installations.

In some cases, disabling and re-enabling AIOWP seemed to solve the problem briefly. When asked:

?Would you like All In One WP Security & Firewall to restore the config settings and re-insert the security rules in your .htaccess file which were cleared when you deactivated the plugin?“

I added the rules back and enabled the php firewall when asked. After a short time the error was back.

Also a complete reset via the settings page of the plugin did not bring a permanent solution. The only thing I haven’t tried yet is to delete the plugin with all its database tables and then set it up again from scractch. I have shied away from this amount of work so far.

Let me summarize once again: There are multiple installations using different plugins and themes.

Standard themes like Twenty Fourteen, Twenty Twenty and Twenty Twenty-Three, but also a theme from Elmastudio and Hive Lite from Pixelgrade.

All of them have AIOWP (v 5.2.1) installed and run on WP 6.2.2. I have not made any entries in htaccess or functions.php myself that would redirect to /wp-login/.

Nevertheless, the wp login page renamed to AIOWP is additionally accessible under /wp-login/ The plugin seems to only prevent login via /wp-login.php with a 404 error.

• This reply was modified 1 year, 4 months ago by fogger.

ok. I have deleted the pastebin again. What do we do now?

I tried it anyway:

Link: https://pastebin.com/7hqnJC1D

PW: nmzA2XwBDW

I don’t have a developer, because I only use the standard tools, also concerning e.g. themes. And with the mentioned site there are no adjustments in the code in Twenty Twenty Three either. The .haccess looks like this:

# BEGIN WordPress
# Die Anweisungen (Zeilen) zwischen ?BEGIN WordPress“ und ?END WordPress“ sind
# dynamisch generiert und sollten nur über WordPress-Filter ge?ndert werden.
# Alle ?nderungen an den Anweisungen zwischen diesen Markierungen werden überschrieben.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Since I’m not really familiar with Pastebin, is there another way to securely exchange credentials?

Sorry, I’m not a programmer and this topic kept me busy for several hours last night.

As I said, the problem occurs with half a dozen websites, all using different WordPress default themes. And no, I have not put any corresponding custom code in functions.php. Certainly not on all sites. I would know.

If I disable or reset AIOS completely, the renaming is gone and only wp-login works. But that’s the expected behavior, right?

If you want to see for yourself: This site uses the default Twenty Twenty-Three theme and currently has only two plugins enabled

• All In One WP Security
• Coming Soon Page, Maintenance Mode, Landing Pages & WordPress Website Builder by SeedProd

The login page has been renamed and can now be reached in parallel at [deleted]

• This reply was modified 1 year, 4 months ago by fogger.

Here is another try:

For example, in one case (where I just tried disabling all plugins), these are installed:

• All In One WP Security (of course ?? )
• Conditionally display featured image on singular pages and posts
• Enable Media Replace
• Imagify
• Jetpack (just for the Custom Content Type ?Portfolio“, all other services like firewall login etc disabled. It’s also the only site with Jetpack where the problem occurs).
• Popup Maker
• Query Monitor
• Redirection (with only two redirects to renamed posts)
• Spectra
• Statify
• Statify – Extended Evaluation
• UpdraftPlus – Backup/Restore
• WP-Optimize – Clean, Compress, Cache
• Yoast Duplicate Post
• Yoast SEO (the free version without redirect function)

Unfortunately, my last answer is not published, it says:

Your post is being held for moderation by our automated system and will be manually reviewed by a volunteer as soon as possible.

No action is needed on your part at this time, and you do not need to resubmit your message.

For example, in one case (where I just tried disabling all plugins), these are installed:

• All In One WP Security (of course ?? )
• Conditionally display featured image on singular pages and posts
• Enable Media Replace
• Imagify
• Jetpack (just for the Custom Content Type ?Portfolio“, all other services like firewall login etc disabled. It’s also the only site with Jetpack where the problem occurs).
• Popup Maker
• Query Monitor
• Redirection (with only two redirects to renamed posts)
• Spectra
• Statify
• Statify – Extended Evaluation
• UpdraftPlus – Backup/Restore
• WP-Optimize – Clean, Compress, Cache
• Yoast Duplicate Post
• Yoast SEO (the free version without redirect function)

I have already tried that. Even if all plugins except AIOS are disabled, the behavior remains the same. The issue also occurs on different sites that use different compositions of plugins. All of them usiing different (standard WordPress)themes. And no, there is no other wordpress page called wp-login.

• This reply was modified 1 year, 4 months ago by fogger.