Forum Replies Created
-
Posts
-
I installed the plugin. Existing token on the site yields:
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 Additional Error Details: Found too many permissions on token.. sale:verify []I created a new token as per plugin instructions, entered it into Envato Market, Save Changes and get:
Your OAuth Personal Token has been verified.When I then enter this new token into Theme Options and Revalidate, I get:
We checked the token on 2022/03/02 15:59 and we were able to connect to Envato and could access the following information: Your purchases Username could not be accessed (needed for your information only) E-Mail could not be accessed (needed for your information only) Following errors occurred: username Errorcode 403 returned by Envato: Forbidden: - code: not_authenticated email Errorcode 403 returned by Envato: Forbidden: - code: not_authenticatedThe old token in https://build.envato.com/my-apps#tokens had this:
This token has access to: View and search Envato sites View your Envato Account username View your email address Download your purchased items Verify purchases of your items List purchases you've madeI then found this page: https://kriesi.at/documentation/enfold/theme-registration/#toggle-id-5, which says the token also needs “View the user’s account profile details”. So I added the other 3 from above and this. The token then validates.
Before moving on, this raises an issue.
The default plugin setting states you only need 3 permissions (as did the error message after I’d first installed the plugin):
View and search Envato sites Download your purchased items List purchases you've madeThe existing tokens (and I have another licence/token as well as this site we are discussing) all have the 6 permissions above. But creating a new token with 3 or 6 doesn’t validate. I had to add “view account profile” as well. Why does the plugin say you only need 3, the old tokens have 6, but you actually (apparently) now need 7? Have Envato changed the rules/guidance? Whatever, if Enfold needs the 7 then maybe you might want to consider highlighting a link to that #toggle-id-5 page in a sticky post at the top of the forum?
All that aside, I now have a nice, shiny bright new token that validates on the test site. But the manual update check still fails to find 4.9, and when I do the FTP directory re-name to update, I get the critical error again and the site is dead.
Please note that the live site, which has the original token that failed on the test site, has found the 4.9 update (it is also on 4.8.6.1) and I have successfully re-validated that original token this afternoon. (The test site is set up as a sub-domain of the live site.)
I know you offered to update the theme for me but I’d like to get to the bottom of why this token & site update has suddenly stopped working after all these years. Next steps?
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#commentwith 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?
I agree the UL is there but shouldn’t you or the devs report this to Google as it’s clearly a bug in Lighthouse yet it’s coming across as an Enfold problem, when it’s not. I’m sure other users will flag this to you in future and I’d have thought you might want to get the issue fixed at source to prevent repeated questions on it.
“… 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.
I see now from other posts that you have changed your long standing policy of free lifetime support. I know all about Envato’s policy but back in 2015 this post explained the situation: https://kriesi.at/support/topic/envato-support-policy-2/#post-500677.
Are you now saying that Envato have forced @Kriesi to change his previous position of free lifetime support, even after Envato had changed their rules?
If so, do you not think it would be polite and a courtesy to long standing customers like me and many, many others to have posted a sticky post on the support forum explaining what has changed rather than letting everyone find out the hard way, and as a consequence have angry users post multiple questions in this forum, that you and other mods then have to waste time answering???
@Jan_FtFA : one of my sites suddenly started doing this today after I updated to WP 5.8.1. (Note for mods – it is still running Enfold 4.8.6.1)
I went into Chrome settings and deleted all the cookies for that site – and the problem went away.
I did not get the time delay issue you report. When the cookie bar was re-appearing on every page even after clicking ‘OK’, the bar re-appeared on every new page selected, all the time.
PS. I experienced the same problem on another Enfold site (which took a couple of attempts at deleting cookies, but eventually the problem went away) but did not get it on a 3rd. So who knows what’s going on…
Thank you @Guenni007
Thanks, I’ll give it a go!
One further question though – what does the number 10 signify in the add_action (or add_filter)?
I’ve seen different numbers in some functions (but not others) but never understood what it is, why the number varies or why some functions have one number, some have two, others none. Hope you can shed some light!
@Ismael – I have not considered hooks and have never created a PHP function from scratch, although I am quite adept at investigating & hacking PHP code modules to get what I want… :-)
The day and date is written into a custom widget area called ‘header’ that the theme assigns an id of ‘custom_html-7’, and I position it in the header via my child style.css, e.g.
#header #custom_html-7 { left: 50%; padding-top: 0px; etcAre there any code examples of using the two hooks you mention that might give me a head start in trying to figure something out? I can’t see anything in Enfold Documentation.
The validation process in Search Console fails on the errors I get. I found similar breadcrumb errors reported on other themes via a Google search and those theme authors acknowledged a problem in their themes and fixed them. But it “appears” Enfold does not know the cause of these errors.
So until the cause of the errors is fixed, we are stuck with. :-(
I know I shouldn’t jump in on someone else’s thread but @swisstraveler’s issue is the same as mine here: https://kriesi.at/support/topic/search-console-has-identified-that-your-site-is-affected-by-2-breadcrumbs-issues/ – which as you can see @Rikard had to leave unresolved.
My site is today reporting 4 pages with both ‘Either “name” or “item.name” should be specified’ and ‘Missing field “id”‘ errors.
There is something going on here…
Still no change after another 5 days. Page 319 still reported as being ‘in error’ but trying to validate a fix continues to fail. No other pages have been flagged up.
The SC history does show however that there were no breadcrumb errors found on April 10, but the error was back on April 11 and still there today.
Shall we close this down as it appears there’s no cause or resolution?
April 6th – page 872 is no longer reported as being in error (and I didn’t do or change anything, I just logged in to SC to see the latest status), but page 319 still is ‘bad’ (error as above). Quite bizarre…
I’ll keep checking for a few more days.
I’m leaning towards this being some quirk of Search Console. I got an email from it this morning claiming a post created in February was crawled 2 days ago and found as “marked noindex” and on checking of course it was no such thing!
Makes sense that if it was a system wide issue with the theme code that you’d expect all pages to be reported, but as stated that’s not the case and the pages giving errors change.
To which point… today, page 872 is still reported as a problem but SC is now reporting that page 319 has the same 2 errors of ‘Missing field “id”‘ and ‘Either “name” or “item.name” should be specified’. Go figure… :-)
I’ll keep an eye on it and advise.
https://imgur.com/vcdEdZN
https://imgur.com/SwNthzf
https://imgur.com/u2KIEdGPlease see screenshots from Search Console (SC) for the error as seen today.
The breadcrumbs error that SC reported on my last post #1290421 for page 385 has now “gone away” and SC is only reporting page 872 as having a problem.
So whatever is going on appears transient but SC is finding something ‘wrong’.
If you search for similar problems online, certain themes or plugins acknowledge a problem but others don’t.
Maybe this is just one of those SC annoyances like the ‘text too small’ and ‘content too wide’ errors that SC pumps out on a regular basis, which are “resolved” in SC by doing nothing other than starting a Validate Fix, whereupon the ‘error’ as reported by SC just goes away without changing anything on the page.
But reporting a breadcrumbs error in code seems different somehow to an ‘interpretation’ of how a page displays on a mobile?
Took a while… but updating to 4.8.1 does not fix the problem.
Doing a Validate Fix in Search Console returns:
Cannot continue validation process Affected pages were found. Fix the issue and run validation againBut the pages are different from my original post – Search Console now says the breadcrumb errors are on pages 872 and 385.
I received emails on 26/11/20 from Envato Market advising there was a new version of Enfold available to download.
There are 2 posts from mod Ismael telling users to “update/upgrade to 4.7.6.5” – https://kriesi.at/support/topic/shortcode-in-page/, https://kriesi.at/support/topic/enfold-remove-yoast-woocommerce-footer-schema-graph/ (and a user claiming to have just updated to 4.7.6.5 – https://kriesi.at/support/topic/enfold-update-not-working-5/).
I saw that the Changelog had not been updated to 4.7.6.5, but sometimes that doesn’t happen immediately and just assumed there was in fact a new version. Obviously not, but I shall await it with bated breath…
Hi,
I think the relevant section in my .htaccess file is:# Block the include-only files.
RewriteEngine On
RewriteBase /
RewriteRule ^wp-admin/includes/ – [F,L]
RewriteRule !^wp-includes/ – [S=3]
RewriteRule ^wp-includes/[^/]+\.php$ – [F,L]
RewriteRule ^wp-includes/js/tinymce/langs/.+\.php – [F,L]
RewriteRule ^wp-includes/theme-compat/ – [F,L]# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Options All -IndexesI added the blocking of includes files because I read somewhere else to explicitly block these. The last line ‘Options…’ was added as recommended in the link in this post: https://kriesi.at/support/topic/google-search-console-403-error-on-directory-wp-contentthemesenfoldframework-2/#post-1013166
If I type in http://yoursitename.com/wp-includes/ then I get a Forbidden message. If I do the same for /wp-content/ or /wp-content/themes/ I get a blank screen with no messages. This may indicate a problem because the wpsuperstars page says I should get a 403 or 404 page.
Ideas?
@Rikard – given the multiple different problems being reported, may I suggest you temporarily remove 4.6 from Envato/Themeforest & the changelog and/or post a sticky note at the top of the support page to advise users not to upgrade?
Can you absolutely confirm that Enfold does not create images of that size?
I don’t use Woocommerce. And as I asked, can anyone offer some helpful ideas as to how I might start to track down the culprit?
The website address is the first line of the original post.
I also stated “if you have a look at it (on the site), you will see the problem.”
I want the Subscribe button in the socket to display as it does in the header.
@Gunter – not sure which bright spark thought this was a good idea but it’s not. It’s a daft decision.
The “Don’t display image on single post” checkbox was/is clearly associated with a Featured Image so it should be in that select box and not with some generic page-wide Layout selections. Please ask the development team to undo this change and restore it as it was.
Screenshot from GTmetrix report.
Screenshot of the page in ALB where the images are specified.
Home page generating the GTmetrix report.
If you look at the page source in Dev Tools you will see the img code for the sponsor logos do not have any dimensions…
<img src="https://www.henleyherald.com/wp-content/uploads/2016/08/brakspear-2017-logo.jpg" alt="" />…whereas the first Top Story image does:
<img width="260" height="185" src="https://www.henleyherald.com/wp-content/uploads/2019/02/invesco-helen-douglas-cheque-260x185.jpg" alt="" />This is not a plugin issue. The home page has numerous plugins and elements and my original post mentioned that the date in the header was not being updated – this is just a line of PHP code – and that a recently published news story, served up by Enfold’s Blog Posts element, was not being displayed, but that the posts from the previous day were still being shown, along with the outdated weather, i.e. the browser was loading a cached page from the day before and not the latest content.
As I wrote in the original support request, and in a follow-up,
On the live site Chrome is showing up-to-date weather info, and today’s date in the header. If I open a new tab then load the test/dev site, it shows yesterday’s date and yesterday’s weather.
…and…
If I launch Firefox today (January 30) and load the live site, it is still showing me the page from January 23.Despite multiple re-starts of both PC and both browsers, that situation endured for over a week. Neither browser would refresh correctly on its own, as it should.
Over the weekend however, without doing a hard cache refresh, the latest content is being shown by both browsers on both live and test sites. I have not changed anything but something has finally caused ‘normal service’. But I guess we’ll never found out what, as no-one has been able to replicate it or offer any suggestions as to what might be the problem. I will continue to monitor and watch for any re-occurrence.
