vincentjflorio

anyakaats,

I’m not the plug-in author, but I did make that snippet above to target some things but not others.

Does the page in question have its own class? “Home” is built into most themes, as is “blog” and “single,” and most Genesis themes allow for you to very easily add one on a per-post or per-page basis.

Otherwise, you might want to lean on the container for the specific content, which may be something like “#gallery-1” if it’s a default WordPress gallery.

Either way, I am reasonably sure you can adapt what I wrote above to have a “not” selector in jQuery to deliberately avoid certain parts of the page, like this:

jQuery("body.home * img").attr("nopin", "nopin");

turning into this

jQuery("body.home * img:not(#gallery-1 dl dt a img)").attr("nopin", "nopin");

or

jQuery("body:not(.gallery-page) * img").attr("nopin", "nopin");

I may have a chance to test this tomorrow when I get back to work, otherwise it may be worth a try unless someone comes around to correct it, if need be.

There’s likely way cleaner ways of going about this than adding it to the head without a priority number (like queuing an external file) but for the quick and dirty, this worked for me:

add_action('wp_head', 'no_pin_outside_of_content');

function no_pin_outside_of_content() { ?>

     <script type="text/javascript">

     jQuery(document).ready(function() {

          jQuery("body.home * img").attr("nopin", "nopin");
     });

    </script>
}

Note: This was a site where the homepage was the main blog index; single post pages aren’t covered by body.home so they don’t receive the “nopin” attribute and still receive a button.

It looks more like a documented change than a problem:

https://www.ads-software.com/plugins/wordpress-seo/changelog/

It appears that feature piggybacked on a Google service, and they had to disable it once Google said people couldn’t anymore.

I am not personally attached to either, because I don’t have a ton of experience with either. They both seem like they have a lot of hard work behind them, and offer interesting and useful features.

I had a client who had an enormous list of stores, and he liked the default layout for WPSL, because it’s a scrollable list on the side instead of a huge list beneath the map, especially when it comes to being economical on smaller screen sizes. SLPlus is capable of that, but at the time (don’t know if it’s still like this) you had to pay to theme it out that way, or to add infinite scroll, or to paginate the 30-odd results.

Some of his non-dev team members also felt like the back end was just a little bit leaner/cleaner/less overhead.

I was looking in the wrong place for profile information. That’s what the issue was. In reality, the offending images were ProPhoto RGB.

I didn’t run into an error, I just happened to need that one particular part to work and had my eye on all the attributes.

I was using the Developer Tools in Chrome that come up when you hit F12, and inspecting the elements of the area I had chosen to place the plugin.

All the text is color-coded, and I noticed that one attribute was all red, instead of red then blue for the attribute and then its value.

From there, it was a matter of hunting down which file contained that logic.

For what it’s worth, I’m not trying to blow sunshine up your butt, and it’s not coming out of pure emotional charge. I’d be objective if it gave me any issues. But I literally just install it and the problems either go away or never arise in the first place. It’s actually -less- complicated than a Band-Aid because there’s nothing to peel.

I don’t doubt that you, knowing the inner workings, are likely its biggest critic. It’s also entirely possible that I haven’t really pushed its limits or been to too spammy or unsafe places. But we’ve had over fifty contracts and it’s been put in place on at least the last 2/3rds (I didn’t know about it before then).

I actually came here looking for some “premium” version so I could a.) find out what could be fancier about it than what it does stock and b.) make sure you got compensated for contributing something so darned solid and effective to the community.

Making sites can be so…well…variable. Just when you think you can rely on things, they act different or explode or undermine what you tell people. There are maybe four or five plug-ins tops in all of WordPress-dom where I know I can consistently rely on how they’re built and if they’re any good at their job.

This one, albeit far simpler in scope than some others (at least the view from the outside), is the -most- reliable. I have total confidence it’ll work in any situation I put it in. I’m not naive; I know that’s not necessarily the case or that it could change. But so far it hasn’t even received a dent, even when two people were on terrible hosts and getting hacked.

Out of curiosity, what do you mean by effect? Like a different default style? Or did you want them to use graphics instead of an icon font?

You sweet glorious person. I just lost four days of my life trying to diagnose this, and I suspected it might have come down to different references made in the database as I bounced around when I broke something testing out compatibilities with different versions of WooCommerce.

In my case I am using this contraption : https://www.ads-software.com/plugins/bulk-photo-to-product-importer-extension-for-woocommerce/

so I had to edit the point at which it creates variations and turns them into downloadable versions.

For yours, it sounds more generic but I came across this page in my travels; hopefully it helps you as much as you’ve helped me:
https://wedevs.com/support/topic/woo_files-not-updating-showing-in-back-end/