zeno001

Joe

I think I can add one of my websites to the list of ones where the Toggle Font size doesn’t work: https://www.medico-legalsociety.org.uk/

It’s currently using 2.1.9 and I can leave it on that for a short while if it helps. The body text is 16pt but doesn’t increase when I click on Toggle Font size: it remains as 16pt.

I have another site and it works as expected (16pt becomes 24pt) with 2.1.9 but the template is completely different.

OK, on the other site (where it was showing with V2.1.2 but not V2.1.3), I deactivated, deleted, reinstalled and enabled the toolbar and it’s now showing on the site.

Thanks for you help, Joe!

Deactivated, deleted and reinstalled. Cleared the cache, enabled the toolbar – didn’t show. Reloaded the page and cleared again and it’s now showing!

That’s one one site – I’ll try the other site tomorrow and let you know.

Thanks, Joe.

I had cleared the cache but the toolbar is still not appearing. Don’t know whether it would make any difference but I’ve tried disabling then re-enabling the tool bar and also deactivating the plugin then re-activating it but still no toolbar!

Hmmm… V2.1.3 doesn’t work on either site now – the toolbar is not displayed – and I see someone else has also raised this issue!

The console shows this:

Uncaught ReferenceError: wpalt is not defined
at wpa-toolbar.min.js?ver=2.1.1:1:39
at wpa-toolbar.min.js?ver=2.1.1:1:978
at wpa-toolbar.min.js?ver=2.1.1:1:989
wp-accessibility.min.js?ver=2.1.1:1 Implicit label on Searchadded by WP Accessibility
wp-accessibility.min.js?ver=2.1.1:1 30 title attributes removed from links and buttons by WP Accessibility
wp-accessibility.min.js?ver=2.1.1:1 12 target attributes removed from links by WP Accessibility
wp-accessibility.min.js?ver=2.1.1:1 3 tabindex attributes added to anchor elements with the button role and no href value by WP Accessibility
admin-bar-v2.js?ver=12.8.1-202346-lite:1 Missing data from PHP (wpNotesArgs).
(anonymous) @ admin-bar-v2.js?ver=12.8.1-202346-lite:1
wp-accessibility.min.js?ver=2.1.1:1
Array(1)
0
:
“{\”0\”:[\”implicit-label\”,\”Search\”],\”1\”:[\”control-titles\”,\”30\”],\”2\”:[\”link-targets\”,\”12\”],\”3\”:[\”link-add-tabindex\”,\”3\”],\”timestamp\”:1700435038}”
length
:
1
Prototype
:
Array(0)

Great! Many thanks for the very quick response, Joe!

Keep up the good work.

Thanks, @loganstrike. I see the same error:

wpa-toolbar.min.js?ver=2.1.1:1 Uncaught ReferenceError: wpalt is not defined
at wpa-toolbar.min.js?ver=2.1.1:1:39
at wpa-toolbar.min.js?ver=2.1.1:1:978
at wpa-toolbar.min.js?ver=2.1.1:1:989

I am not using Elementor and the site seems to work OK otherwise.

Thanks, Tobias. I hope you’re able to provide that option soon but at least there’s a workaround for now!

Thanks, Andrew. I’ve been ill so unable to reply earlier but there was an issue with a page builder plugin that was installed and although not being used at present, it had the V3 reCAPTCHA built in. I had not entered any keys (because I wasn’t ready to use the page builder) and that was causing the error on the slide-in banner – I’d forgotten that was V3 only so it was confusing me!

All sorted now.

Odd. Even though I’ve deactivated the Bestwebsoft reCAPTCHA plugin (and purged caches) and the tick box has disappeared from the comment form, I still see the reCAPTCHA slide-in banner box with the same error message. I don’t think I have anything else that uses Google reCAPTCHA but I’ll investigate again.

Still would welcome an suggestions!

Hi @dajanas

I was able to resolve the issue by adding this CSS:

.nf-form-content input[type=radio].ninja-forms-field {
display: none;
}

But whether this works or not for you may depend on your template. I can make some simple CSS tweaks so not an expert but I can see basically what this is doing – hiding some of the form elements.

Perhaps give that a try?

And yes, it’s clearly something that has changed in the last or last-but-one version of Ninja Forms.

Thanks! Will do.

Peter

Finally worked what the issue is here!

I had helpfully added in a comment before the noabort code to say what it was doing and to link your page on it:

# Add fix to stop Litespeed aborting Wordfence scans and updates
# https://www.wordfence.com/help/advanced/system-requirements/litespeed/
# Insert just before # BEGIN WordPress

Unfortunately, when WordPress runs a core update it recreates the WordPress section in htaccess and to find the WordPress section, it does a simple string search for # BEGIN WordPress. Even though it’s in the middle of a comment line, WordPress find that in my comment and writes its new section from there, overwriting the noabort code! I’ve removed the # from the comment so WordPress will no longer find it in my comment. I’m sure that will fix the issue.

The function is in: \wp-admin\includes\misc.php

function insert_with_markers( $filename, $marker, $insertion )
...
$start_marker = "# BEGIN {$marker}";
$end_marker = "# END {$marker}";

Actually, I no longer need that plugin so I’ve now deleted it.

There is also a text change on Advanced Editor Tools (previously TinyMCE Advanced) (from Automattic) but this is just the tested up to WordPress version “Tested up to: 5.7”.

Peter

I had missed the file changes but they appear to simply be textual changes of spacing/tabs and not a code change, eg:

Original:
if (isset($_POST['option']) and $_POST['option'] == "ap_user_login") {

Modified:
if( isset($_POST['option']) and $_POST['option'] == "ap_user_login"){

I’ll investigate further but I doubt this is the cause of the issue.

I have tried the first suggestion for the htaccess file but that’s what’s being overwritten. Your page says:

Find the line that says “# BEGIN WordPress” and add this code above it:

Does the noabort code need to go above the WordPress section or can I put it below?