girl_number_5

Don’t bother then … purchased a better plugin

I’m refering to the front-end setup forms provided via a dedicated page or shortcodes

https://melapress.com/support/kb/wp-2fa-configure-2fa-front-end-page-wordpress/?=

we are using the shortcodes option and it appears all vertical-padding has been removed so there’s a spacing issue. The xample css given on the page (referenced above) does not extend to spacing. Some notices adopt the themes styles others don’t.

I’ve got around some of the issues (like illegal css id names) by targeting them in jQuery rather than CSS rules.

(@catacaustic),

Thanks for that info – i found the problem shortly after creating this thread, it was a problem in my naming of pages. Marked [Solved].

thank you

Hi (@ironprogrammer)

Yes the login functionality (out-of-the-WP box) with or without 2FA works great using either Authenticator or Email based auth. The plugin I’m using , Paid Member Subscriptions gives us the option to use its own login page or the WP built in login page. Their login page completely ignores the 2FA form – so im left having to customise the look of the in-built Login form. But now i want to use a Login page from a html5 site i found to build my own WP theme.

I think the suggestion to use Email auth is probably the best way to go. I personally like Auth apps, but many users i think would appreciate not having reliance on a 3rd party app in favour of using their (already supplied) email-address. Maybe i was over thinking it; easier is definitely better were the end user is concerned.

@bcworkz – ill take a look at that link thanks – ill start by looking at plugins like Branda which give you ca completely customised login page. Currently im using a plugin called ‘Paid member subscriptions’ which gives us a Login/Register page with shortcodes attached but the problem i’m having with that is the login page doesn’t recognise the 2FA form that appears after successful submittal of email/username and password. 2FA is critial on the site i’m building. Ive also encountered a few other custom login page builders that don’t recognise the need to show the 2FA inputbox.

Hi Anton,,

i figured it out earlier this morning but wasn’t able to get onto these forums getting a ‘bad gateway too many requests error in Chrome’. But that’s what worked – initially i was using text.replace() and it only occurred to me later that we’re searching for and replacing html.

Thanks for your answer anyway.

Ok no problem – thanks for the update.

@blakmarkit,

Yeah, i think i did the same a few versions ago and i kept the old version for ages ignoring all new updates just to avoid another bunch of new surprise changes. Its a lot of fun dabbling with the editor and making cool customisations then you find they alter after the next update. I’ve used the export & import a few times and it works ok so long as your doing it within the same version. Hope he finds the fix soon.

Thanks for that, it appears the problem as far as i can see is, in general UIPress is designed to allow us to make pretty drastic changes to the UI and these changes can’t be accounted for when the plugin is updated – this is without the most problematic update so far. I’m leaving it uninstalled for now and ill revisit in the future since its not a critical element of the installation. As an indie dev myself i know the pressures when its one pair of hands to the wheel 24/7. I still rate this as one of the best WP plugins out there (a real gamechanger) but as i stated in my original thread it needs to be more consistent with the updates. I wont mark this as ‘solved’ since others seem to be adding updated issues.

Thanks

UPDATE:

In the staging site i just commented out those ‘Firewall’ lines at the end of .htaccess and the two lines they write to wp-config.php and the 500 error has gone. So you were spot on the issue. Ill leave the Firewall tab and wait for an update on the plugin which we like for the 2FA and other features

Thanks for your attention in diagnosing this issue.

Hi,

Are you referring to the staging site when you write ‘child’ i have a child-theme and that is all setup ok and is not the issue this problem occurred after setting up the staging site directly on my server hosting account; they have a single click option to allow creating a staging site so you don’t need to use a 3rd party plugin. Noted: there is a .htaccess file in both the parent(production) site files AND one in the staging sites files since the sites are carbon copies of one another. I noticed that the files are identical and there might be some conflict going on. Also the two lines which are injected to the top of wp-config.php, as you suggest, may be clashing since they appear in both sites; production and staging. Rather than messing with .htaccess, which i don’t like to do, would it be better to just turn Firewall option off in the plugin? I can do without it anyway as i have Firewall settings at the server hosting level.

Yes,

Forgot and later sent the password to you via your generic support email. I’ve removed the password now so please take a look.

I use Microsoft Authenticator and always have and it works with all other accounts i have setup in it. I’m using: 2FA with Backup codes and email-address methods in that order. I’ve tried the backup codes and also my email and no method is working. Today i tried removing 2FA and re-initialising it with my authenticator app and it won’t recognise the verification code Defender shows after we scan the QR code.

I’m having to leave my site unprotected while this issue persists but will soon uninstall if it can’t be fixed.

Hi,

thanks for the response. I’ve already cleared my PHP debug log and that original error went away after removing the erroneous extra ‘$’.

Other details asked for:

WordPress version 6.4.3
Site Language en_GB
PHP version 8.0.30 (Supports 64bit values)
Defender version 4.5.

Site health check paste is here

Hi,

Has a fix for this been issued yet, i have the same issue and the banner (as the thread starter says) is blocking the UI. It actually blocks important aspects of the UI menus – surely this is important enough to issue a minor update.

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

Wow what a difficult one!

I generally always do hard cache refreshes (ctrl+F5) so knew that was not the issue but it was cache related.
I suspected VScode since the images were showing as broken in the VSCode editor (as in the screenshots i provided).

For anyone experienceing this when using VScode:

1* Don’t move images from their locations on your PC directly into your VSCode project!
2* Move them instead into the VSCode project folder which contains all your VScode projects
by default VSCode installs it in your ‘user’ folder (in Windows); not sure about Mac (sorry)

1. Remove the broken images from your VSCode project they are permamantly corrupted! the cut-off parts display completely corrupted data like a fractal image.
2. Replace those images by adding good versions to the VSCode project folder as in point 2* above.
3. From within your VSCode project upload those images via ftp to your server (replacing corrupted ones).
4. Ok, this next bit fooled me for ages! After (hard)clearing my cache again and purging all cahes using my Caching plugin (Litespeed)
   expecting the new images to display – oops no! This may or may not be an issue for you but i had to take one more step.
5. All affected image need to have a version query-string update, i.e. ‘myimage.png?ver=1.0’ your images may or may not have this query-string explicitly added. If not there its assumed to be version 1.
   You, however need to add it if not there already and then bump up the version number by one, i.e. ‘myimage.png?ver=2.0’.
6. If, like me, one of the broken images is your screenshot.png of your theme then you can only affect the version number by bumping up the version from
   the themes ‘style.css’ comment meta data – i.e. ‘version : 1.0’ – bump the version up there. However note if its not your own theme then it may mess up future updates of the theme.
   So try using a WP Plugin like ‘Easy Replace Image’ which gets around the age-old WP issue of not being able to overwrite an unwanted image with a new image of the same name.

Hope this helps someone else. The issue is definately VSCode image paths on your local machine. Never happens when using NP++ as an editor!

Thanks