Thanks, that worked. Added it to the CSS of the plugin using the font, Performance score on the site is now 99 for Desktop… :-)

I decided to alter the default Medium size (300 x 300) using the function because I use Portfolio, which works. Medium is now 600 x 450 px.

But the issue remains that when setting a Featured Image in the Post there is no selection available to choose the Medium size – Add A New Post / Featured Image only allows the full sized image to be chosen, nothing else.

How do I set the altered Medium size as the FI?

I’ll try this out tomorrow in another editor and report.

I personally think it should be fixed as I’d have thought you’d want to maintain compatibility with all browsers. You can close it.

Brilliant, thanks – works a treat!

Out of interest – what’s the reason why
if ($query['category_name'] = 'events';)
doesn’t work?

Thanks. Your fix only affects part of the blog text, namely the

• … section at the bottom.

  This

  #top .all_colors p {
      font-size: 16px;
  }

  is over-riding the 18.4px declaration, and adding !important to .entry-content-wrapper doesn’t work either.

  I didn’t realise the smaller font size would narrow the blog container. I’ll have a re-think about the size and layout. Case closed!

I didn’t realise before posting that the site is running 4.8.6.1, so if the code has been updated since that version it might be fixed.

No I cannot reproduce it, in part because the site does not use a Tab Section anywhere that I’m aware of on its Pages (it does have the Combo widget on every page and post, which is tabbed) so it seems strange to me that tabs.php should throw an error. Having said that, the site has 12,800 Posts dating back nearly 10 years, so it’s possible a Tab section was used in the past – but the site Editor cannot remember doing so… Does that code get called by something else?

Also, at the time the error was logged, middle of a Sunday evening, no admin folks were working on the site so however the error was invoked it would have to be by a normal user (unless of course there’s a system process that might cause it).

Sorry can’t offer more insight (but if there’s anything I can do further, please advise).

Got it, thanks. Closed!

Hi Yigit,

The site was down. Appearance > Themes said “The active theme is broken. Reverting to the default theme.” It says Enfold Child is Active but then below it says:

Broken Themes
The following themes are installed but incomplete.
Name	Description			
enfold	Stylesheet is missing.		Delete

I’ve renamed ‘enfold’ to ‘enfold-4-9’, uploaded 4.8.6.1 and it’s live again.

Options > Theme Update is also now showing there is a new version (4.9) available.

Debugging is active plus define( ‘WP_DEBUG_LOG’, true );

I have hopefully fixed the FTP problem. The hosting provider said that whilst permissions looked OK to you, their system sometimes overrides this after I’d set you up as a new user (he didn’t say why) but he has reset it so you should be fine now.

Sorry, been busy elsewhere…

Updating the live site via Updates > Themes, because 4.9 was showing as available, and using the old, original token that validated in Theme Update, crashed the site with the “critical error”. I had to FTP version 4.8.6.1 back up to /themes to get the site back online.

After this, back on 4.8.6.1, I could validate this original token in Enfold Child > Theme Update – but the Manual Update check there failed to find 4.9 and Envato Market also fails that token with:

Incorrect token permissions, please generate another token or fix the permissions on the existing token.
Please ensure only the following permissions are enabled:
View and search Envato sites
Download your purchased items
List purchases you've made
Dismiss this notice.
Additional Error Details:
Found too many permissions on token..
sale:verify
[]

So I tried the new token I generated a few days ago. Theme Update again validates the token but Envato Market fails it as above.

I then created another new token today. This again validates in Theme Update but again no Manual Update shows up. When I go into Envato Market and add this newest token, Save Changes, I get the error again as above (Incorrect token permissions). But if I go to the Themes tab, it lists Enfold Version 4.9 as available. I have not tried clicking Activate on this for fear of crashing the site again.

One last try: I did the FTP upload of 4.9 into /themes, did the directory re-name as I’ve always previously done – and the site crashed with ‘critical error’. So reverted back to 4.8.6.1.

So it appears both sites are now well and truly messed up, and cannot be updated.

Why is Enfold Child > Theme Update validating all three tokens but Envato Market fails all three? This must be why the auto update is failing but doesn’t explain why the FTP upgrade is also failing.

What next?

Please close, thank you.

Hi Ismael,

1. The default comment field has a corresponding label above it.
<label for=”comment”>Comment <span class=”required” aria-hidden=”true”>*</span></label>
I know, I can see it – but this is the crux of the problem. We can both see the label code is present but Lighthouse says it isn’t, and is generating an error.

2. Please note that the comment field is a default WordPress element, it is not generated by the theme.
I did not realise this – please see my last comment below.

3. Are you sure that the textarea that the plugin generates has been removed from the page when you run the test again?
Yes, definitely gone, also checked in Firefox. See https://imgur.com/gallery/ZkOGgrv – this is Dev Tools Elements after I have clicked on the hyperlink from Failing Elements > textarea#comment, showing what Lighthouse thinks is the (shaded) line of code that generates the “Form elements do not have associated labels” error.

Now… given your reply to 2, whilst I appreciate your time and effort to assist with this, isn’t this something that I should (now) be raising on a WordPress forum? You having pointed out it’s a default WP element that is causing the error, and not an Enfold element. Or rather, I think it’s Lighthouse that has a bug here but it’s a WP element it’s failing on. Perhaps I should be getting them to address the issue with Google?

I use Antispam Bee on that site. If I deactivate it then the line
<textarea id="a941a68d79d5a981230e419af11a14d5" aria-hidden="true" name="comment" autocomplete="new-password" style="padding:0 !important;clip:rect(1px, 1px, 1px, 1px) !important;position:absolute !important;white-space:nowrap !important;height:1px !important;width:1px !important;overflow:hidden !important;" tabindex="-1"></textarea>
disappears from the page.

However… without that plugin active, and after a hard cache refresh, I still get the “Form elements do not have associated labels” error from Lighthouse, specifying this line:
<textarea id="comment" name="comment" cols="45" rows="8" maxlength="65525" required="required"></textarea>
which is the Enfold comment box.

If I re-enable the plugin the Antispam code re-appears. If I run Lighthouse again, I still get the ‘no label’ error. When Lighthouse highlights what’s causing the error, it states:

Failing Elements
textarea#comment

with a small thumbnail of the comment box. The ‘textarea#comment’ is a hyperlink to the code it thinks is a problem. If you click on that hyperlink, you get transferred to the Elements tab of Dev Tools, wherein the HTML code is displayed. It then automatically goes to the line of ‘problem’ code and highlights it in light blue. Guess what? It’s not the Antispam Bee line that’s highlighted, but the Enfold comment box, e.g.
<textarea autocomplete="new-password" id="comment" name="ac76510e77" cols="45" rows="8" maxlength="65525" required="required"></textarea>

So Lighthouse is saying it’s not Antispam Bee causing the error, but Enfold. When Lighthouse detects multiple errors on a page, e.g. ALT tags missing, it lists out all failing instances under Failing Elements. The only element ‘failing’ here is the Enfold textarea.

When you say “We have checked the comment form on a fresh installation without a plugin and we didn’t find the same hidden textare below the actual comment field“, yes the hidden textarea won’t be there – but did you run Lighthouse on that page? I suspect if you did, you’d get the ‘no label’ error.

Or you can try it yourself on the page (or any page on my site) that I referenced in the first post.

Given your last reply, I’m at a loss to understand what’s going on here. Another Lighthouse bug perhaps?

“… the lighthouse warning can be ignored.”

But it’s flagging this as a red triangle “high priority to fix” error and it is downgrading the Accessibility score.

Whilst you say the element doesn’t require a label, could one not be added so that the error goes away? It seems a simple fix for the devs to do and I assume it wouldn’t ‘hurt’ or cause a problem, with the benefit of helping the score improve.