Joe Streno

@malihu Ditto. Fixed the problem on both my sites. Thanks!

WordPress 6.1.1 on both WordPress sites.

@thomascloer … don’t I feel like the arrogant fool! D’oh!

Got up on the wrong side of the Mac this morning … I guess.

Thanks for the info … I’ve updated to 5.164.1 & you are correct. The notice is gone.

But the warning was kind of big, scary & in your face. lol I just thought tet my house ablaze … so to speak.

Thanks for the update, Thomas. I do appreciate it.

Case closed. : )

Hi …

That did the trick. Thanks!

Joe

Hi Michael …

Just updated to YARRP v5.10.1

I’m using Enable jQuery Migrate Helper v4.08

I’m still getting an error when I go to the YARRP settings page. Same error I got on v5.10.0.

Previously logged deprecation notices

The following are deprecations logged from the front-end of your site, or while the deprecation box was disabled.
Time : 2020-10-23 16:09:28

Notice: https://www.go2jo.com/wp-content/plugins/yet-another-related-posts-plugin/js/options_basic.js: jQuery.fn.attr(\’checked\’) might use property instead of attribute

Page: https://www.go2jo.com/wp-admin/options-general.php?page=yarpp

Here’s a screenshot of the warning too:

View post on imgur.com

Thanks … Joe

Sadly, nope … not fixing it for me.

2020-10-23 08:41:07 https://www.go2jo.com/wp-content/plugins/yet-another-related-posts-plugin/js/options_basic.js: jQuery.fn.attr(\’checked\’) might use property instead of attribute

And I am running v5.10.0 ˉ\_(ツ)_/ˉ

Hope that helps.

@isaumya Checked for error logs via FTP at domain root, public_html, and my theme level. I also checked for error logs on my cPanel page. No errors anywhere. ˉ\_(ツ)_/ˉ

The strange thing is, this was all working previous to the last 2 updates to your plugin.

Also … I’ll throw this in for good measure: I am also running Fast Velocity Minify. I see you have settings for use of other caching plugins, there’s nothing for this one. Though I guess it technically doesn’t cache. I also don’t have Cloudflare set to minify, because FVM is doing that job.

@isaumya Thanks for your reply.

I checked the main admin page & I do see the BYPASS status. But when I go to tools.php page for OPDADR by clicking on its WP admin menubar link/button (which should run the script/utility), this is what I see in Console: https://imgur.com/a/7ZdLr1s . The Console page is empty. Though the page itself draws correctly the Console is empty except for the tool page link for OPDADR.

If I click the OPDADR button a second time, or refresh the page, this is what I see: https://imgur.com/a/NNNo4WC . The Console updates & I see the BYPASS status for the page as you said I should.

I get no errors, no warnings — nothing.

BTW … this is still happening & I have updated WP Cloudflare Super Page Cache to v4.2.7 before running all these tests.

Any ideas? What’s next?

• This reply was modified 4 years, 8 months ago by Joe Streno.

This may be bad plugin, & or forum etiquette but … for sliders I use Smart Slider 3 (paid version).

https://smartslider3.com

It even has a free version. Build the sliders you want, pop the shortcode for each slider where you want in a post or a page … done. I use Smart Slider in my own & client’s WP websites. And their support is fantastic!

If not … the other thing you can try is the old … turn off all other WP plugins, then activate them one by one & check to see if there is a conflict with SU.

The problem may also be an incompatibility with your WP theme. Try viewing your site in the WP Appearance manager and try a standard WP theme like Twenty Nineteen. If it works there … the problem is with your theme.

Good luck!

The problem seems to be your original images are not the same size. The slider seems to be taking on the height dimension of the tallest photo. The photos—for whatever reason—are causing the slider to have so much white space.

Try resizing and or cropping the original images in an external editor like Photoshop. It seems the dimensions of the current slider are W:650 x H:390. So ALL photos used in the new slider must be that size—even if some of those images are in portrait sizing (H:650 x W:350) … all photos must be cropped to landscape sizing W:650 x H:390.

Also change the name of the original photos by adding -2 to the end. I say this because it looks like you’re also using Jetpack’s photo cacheing. If you don’t change the names, Jetpack will deliver the old unedited photos.

Upload the edited photos to your WordPress blog. Then recreate the slider with the new images, making sure you set the new slider to the height/width dimensions of the edited photos—650 x 390. Plus if you don’t need arrows, or pagination, turn those off too. And for good measure make the slider responsive.

If this fixes the issue, and you edit all the other photos & recreated the other sliders, go back and delete the original multi-sized images you used in the previous slider(s) from you WordPress image library. Unless of course you use these images as single still images elsewhere.

I have a feeling this will fix the problem. If not … I tried. Good luck.

Seems this forum is not big on help. I posted a question over a week ago & have gotten no help from even the plugin author. ˉ\_(ツ)_/ˉ

Hi Nastia …

Was not able to get the popup to trigger from a menu item. I use the WP plugin ShiftNav for all my menus. For whatever reason none of the menu methods tried work. I gave up on that.

I ended up using HTML and the popup clickable shortcode and created my own html button & now the popup works in my ShiftNav configuration.

Thanks for your help … Joe

It’s a goner. I also realized it conflicts with SmartSlider Pro 3. Post Grid was causing 40-60 errors for SSP3 on each search. Yeah … buh-bye to Post Grid.

With AO & Hyper Cache my load times are 2 seconds or less … with Post Grid installed it kills my load and search times.

Later for that!

Thanks for all your help!

As soon as I remove the Post Grid plugin php code from my archive.php & search.php pages … all those searches return what they should & the pages draw as they should.

As much as I don’t want to … I need to dump the Post Grid plugin. Had a feeling that’s how t would end up. I wasted far too much time on this. Now if I can only get a refund. lol

Thanks for your input. ??

It’s the stock WP search. No 3rd party extension version or enhancement for searching, but the archive & search and index php pages are using a grid plugin to display the results.

What’s odd is not even the WP interface, Admin bar etc are drawn. Just nothingness.

But you’d think that if is was a search problem, it would happen for ALL searches not just arbitrary search words.

I’ll second the disaster sentiment!

I’ve used WordPress since starting my blog 13 years ago. I’ve used HTML & CSS in the text editor almost exclusively (read: 98% of the time). I really don’t want, nor need Gutenberg or blocks.

You’re not making my writing any easier or faster—especially when Gutenberg’s current release it’s unusable. The blocks editing area is tiny on a 27″ screen. Editing or blocks are not intuitive in any shape or form. Even something as simple as adding an image into a text block has become painful in Gutenberg.

Currently I create a new WordPress document, defaulted to the text editor, I write. I don’t need some new inferior method introduced that will also force 3rd party plugin writers to have to support 2 methods of editing: Gutenberg and the “Classic Editor” plugin…. and that’s even IF they support “classic”.

When Coke tried to change their product to New Coke & Classic Coke, the outcry was deafening. Have we leaned nothing?

Making the “old” editor a plugin has already caused ill effects in Safari Mac when trying to Web Inspect a WordPress page. The page is not drawn correctly, many plugins are rendering as text, when there should be a visual rendering—not text.

I’m ready to jump ship if Gutenberg becomes the default editor. You’ve created a HUGE problem where there was none. You’re inflicting pain where there needs to be none. You’re already causing HTML rendering errors where there were none before (just view a page in Safari Mac Web Inspector).

I never thought I’d say: maybe it’s time to look at Joomla or just recreate my blog as a stand alone HTML/CSS website. And I’ll also have to look at and rethink all the work I’ve done for other WordPress blogs I’ve built and manage for clients.

If upheaval is what you were shooting for, you’re right on target! Why couldn’t Gutenberg be the plugin & keep “classic” as the core.

I’m not impressed & I doubt I’ll ever be. If it ain’t broke, don’t fix it with an entirely new paradigm and backend.

I may need to download the previous non-Gutenberg version of WP, turn off auto updates & stay there until you all either come to your senses or I find an alternative. You’ve already made my life difficult enough. Thanks!