Aaron Jorbin

@seoservicesbristollimited If you encounter an issue, please open a new thread in the?Alpha/Beta area?of the support forums. If you are comfortable submitting a reproducible bug report, you can do so?via WordPress Trac. You can also check your issue against this list of?known bugs.

It looks like https://beaulebens.com/projects/wp-keyring/ is now the correct URL.

A Release Candidate for 6.6.1 was created today and is available for testing. 6.6.1 is currently being planned for Tuesday, July 23rd.

On recent WordPress version, I do not know if ts 6.4 or 6.5 you can add it directly from the settings / General / Site icon

This was added in 6.5. If you are running a version before 6.5 you should update but if that’s not possible right away, you can add this from the Cuztomizer by visiting yoursite.com /wp-admin/customize.php. You’ll find the option under Site Identy

It’s possible that your site had an incomplete update. Please try doing a manual update and seeing if that fixes the issue.

If that doesn’t fix it, some more info to be able to help narrow this down would be to understand if this is this on all wp-admin pages or only a subset of pages? For example, can you access yourdomain.com/wp-admin/edit.php or yourdomain.com/wp-admin/index.php or is this only on specific pages? Is your site a single install or a part of a multisite install? Is this for all user roles or only some roles?

Found the git repo and opened a PR https://github.com/WordPress/theme-check/pull/270

The ability to manually add deprecated notices is disabled, hence the error message you are seeing. I just released version 0.4.1 which hides the add new button since it does make a tempting target to click.

Thanks for the catch!

Unfortunately, I have no idea who maintains that sync, but it is by no means official.

@wido – What GitHub mirror are you referring to?

Fixed in 0.4

do_not_allow is a capability that is given to no user role and is even specifically denied to super admins.

• This reply was modified 8 years, 1 month ago by Aaron Jorbin.

Fixed in 0.4

The line listed is where the notice is triggered, not what is causing it. Take a look at https://www.ads-software.com/plugins/log-deprecated-notices/ to help you identify the plugin or theme that is causing the issue and then report the issue to the author.

I wouldn’t keep log-deprecated-notices activated after you use it, it can be a bit of a resource hog to do the backtrace to where the notice is caused.

> it works fine in PHP 5.3 and later

Are you sure? https://3v4l.org/tLT0d shows that it throws a parse error below 5.6. See also, https://php.net/manual/en/migration56.new-features.php#migration56.new-features.const-scalar-exprs

Hi @mulligan101

It looks like your theme has some javascript issues that could be causing this problem. I would encourage you to contact the author of theme and let them know that they need to update line 136 of enfold/js/avia.js to use a proper selector. As the jQuery documentation states for attribute selector “Attribute values in selector expressions must follow the rules for W3C CSS selectors; in general, that means anything other than a valid identifier should be surrounded by quotation marks.”