smallstar67

THere is no way for me to send your zipped plugin files via email. You surely must know of the Yoast SEO plugin, it’s the most used SEO plugin on the planet.

unfortunately this is not what we were asking for. We don’t need images for the variations, thats built into woocommerce.

We were asking for images displayed for the “terms” in the standard drop down format.

Oh my gosh, we are so excited, thank you!

We are using the version from this mornings updates. I’m simply asking you a question about a feature we have been asking for , for about a year. I have no idea how my question pertains to any of these posting violations in your link.

It’s just a question about a feature that honestly is fundamental.

any progress on adding a selection dropdown terms thumbnail shown as well as the term’s text.

meh… I wouldn’t call this resolved…

Oh that’s too bad. You should reall y consider it. It’s literally the most basic way to display product options and there are zero plugins that do it on any platform.

5.4 doesn’t work with caching. gotta go back to 5.3.2 For some reason they are in no hurry to fix it on any level.

The 5.4 latest release doesn’t work well or at all with any caching plugin such as WP-rocket, Total Cache, ect….
Why they don’t just come out and say it to take care of 90% of these issues in the last two weeks I have no idea. Instead like so many plugins they first pretend to assume it’s one of the other plugins you may be using.

Simple fix, roll back to the 3.32 version until you see something other than the 5.4

Contact form 7 version 5.4 does not work if you are running a cache program like WP rocket and all others.
roll back to 5.32 and make your life easier until they address this.

version 5.4 does not work with caching like WP rocket and others. The user solution currently is to roll back to 5.32

I don’t have reCaptcha errors, mine just plan doesn’t work correctly anymore. Judging from the other threads this is a new common thing.

At what point do you think the plugin version 5.4 will be corrected, or should we go back to the previous version?

After the WordPress update last night to 5.5.3 All these Google search console errors disappeared in a matter of hours with no interaction on our part what so ever.

This proves that wordpress doesn’t check to see how new changes will be viewed by the all mighty omnipotent Google search console algorithm until after the damage has been done. ??

and every time they do that it wastes hours upon hours of my time.

Since this started we have started up a fresh Apache server 1 day old with CentOS7 and PHP 7.4 We loaded a fresh WordPress install with zero plugins. All the same errors show up on the new server. The original server has had no indexing enabled for a number of years. We tried indexing enabled and disabled on the new server, in either state it has no effect on the PHP errors.
Of the 60 server 500 PHP errors these missing class functions are the same in all three instances on both servers.

Class ‘Text_Diff_Renderer’
Class ‘SimplePie_Sanitize’
Class ‘WP_Session_Tokens’
Class ‘Walker’
Class ‘Text_Diff_Renderer_inline’
Class ‘WP_HTTP_Response’
Class ‘IXR_Server’
Class ‘WP_Image_Editor’
Class ‘SimplePie_File’
Class ‘WP_Dependencies’
Class ‘SimplePie_Cache’
Class ‘Requests_Hooks’
Class ‘WP_Image_Editor’
Class ‘WP_Dependencies’

So in conclusion, either these pages will inherently throw errors when being viewed out of context as a stand alone page in a browser or wordpress itself has something wrong with it. There is no known way in google search console to understand why it is indexing these files, or to tell it not to. These PHP files are not are not part of any submitted site map that we have produced.

• This reply was modified 4 years, 5 months ago by smallstar67.

We just got the message from Google search console this morning. 60 files affected in the wp-includes directory:

wp-includes/class-wp-text-diff-renderer-table.php
wp-includes/template-loader.php
wp-includes/class-wp-simplepie-sanitize-kses.php
wp-includes/class-wp-user-meta-session-tokens.php
wp-includes/class-walker-category-dropdown.php
wp-includes/class-wp-text-diff-renderer-inline.php
wp-includes/class-wp-http-requests-response.php
wp-includes/class-oembed.php
wp-includes/rss-functions.php
wp-includes/ms-default-filters.php
wp-includes/feed-atom-comments.php
wp-includes/nav-menu-template.php
wp-includes/update.php
wp-includes/class-http.php
wp-includes/class-feed.php
wp-includes/feed-rdf.php
wp-includes/spl-autoload-compat.php
wp-includes/class-walker-nav-menu.php
wp-includes/class-wp-http-ixr-client.php
wp-includes/class-walker-category.php
wp-includes/registration-functions.php
wp-includes/class-walker-page.php
wp-includes/class-wp-xmlrpc-server.php
wp-includes/class-wp-image-editor-imagick.php
wp-includes/class-wp-simplepie-file.php
wp-includes/class.wp-scripts.php
wp-includes/class-wp-customize-setting.php
wp-includes/ms-settings.php
wp-includes/ms-blogs.php
wp-includes/registration.php
wp-includes/class-wp-feed-cache.php
wp-includes/rss.php
wp-includes/session.php
wp-includes/class-wp-customize-control.php
wp-includes/default-widgets.php
wp-includes/media.php
wp-includes/vars.php
wp-includes/feed-atom.php
wp-includes/default-filters.php
wp-includes/class-wp-customize-section.php
wp-includes/feed-rss2.php
wp-includes/locale.php
wp-includes/wp-diff.php
/wp-includes/functions.php
wp-includes/class-json.php
wp-includes/class-wp-http-requests-hooks.php
wp-includes/date.php
wp-includes/class-walker-page-dropdown.php
wp-includes/class-walker-comment.php
wp-includes/class-wp-image-editor-gd.php
wp-includes/feed-rss.php
wp-includes/script-loader.php
wp-includes/class-IXR.php
wp-includes/class-simplepie.php
wp-includes/class.wp-styles.php
wp-includes/class-wp-customize-panel.php
wp-includes/compat.php
wp-includes/embed-template.php
wp-includes/feed-rss2-comments.php
wp-includes/class-snoopy.php