wornways

Figured it out purely through trial and error. Jetpack 12.5 is the latest version compatible with WordPress 6.1.

Nothing? Anyone? I see that none of the posts here get responded to now that I think about it…

Hi Support People,

Sorry! I should have been more clear. I’m taking about the list of share links that shows when you click the orange plus symbol at the right/bottom of the list of share links that have been set as visible. I would show a screen snippet, but for some reason that’s not possible to do here, at least not with the type of account I have.

For clarification, the social sharing floating icons has the plus symbol at the end, and when you click/tap on that an in-browser window is displayed that you can scroll through with loads and loads of social share links, some of which seem a little edgy, like “Hacker News” (kind of wish I could remove that option honestly as I can’t say I want my blog shared with a hacker’s discussion forum).

Let me know if I need to try to clarify further. ?? There are a few dead or improperly functioning links on account of sites going offline or changing the way URLs are passed to them.

All the best!

EAT

Hi Heateor Support lifeforms,

I really appreciate your taking the time to respond to the query. I trust that you’ll get around to enabling this capability as time and resources permit, at which point I will be happy to test it out for you. ??

You’ve created a great tool. If readers ever start using the Facebook comment tool, I’ll definitely drop some dough to use the Facebook moderation tool you’ve got.

One suggestion–go through the social links in the list a little more frequently. As I explored to see where they all went and what kind of sites they were associated with I hit a few 404s and similar. A couple of sites also didn’t capture the URL and just landed you on their home page.

??

Appreciate the follow-up, WFG.

Be well,

EAT

This issue self-resolved.

Upon further investigation, I discovered that WordFence needs a little time to reindex the blog and its core files after an upgrade.

So I jumped the gun by running a scan just after upgrading WordPress to 5.2.2.

Thanks for listening,

EAT

I installed Yaost SEO not long after starting my blog. I have noticed lag all along when editing my posts, but most of my posts were short, so it was bearable. However, presently I’m building some much longer posts–lists that organize a bunch of the smaller posts–and as the posts grow in length, the lag has become increasingly unbearable.

Upon reading this post, I tried disabling Yaost SEO’s “Readability analysis,” and all the lag I’ve been experiencing went away. Having seen the analyses presented over the course of more than 400 posts moved from my old blog, I can assure you it’s not an entirely useful feature to have anyway. It flags a lot of posts as green (good readability) when they’re really not and require further editing and it flags a lot of beautifully written posts as red (poor readability). So it’s good to know that all I had to do to get rid of the lag was to disable a completely useless feature.

Thanks to the creator of this post for drawing attention to the problem and figuring out how to solve it.

Ah I see. You used the code I posted to make your own changes. Be sure to install the Easy Updates Manager plugin so you can prevent the changes from being overwritten next time there’s an update. Hopefully the plugin developers will incorporate the changes and make us all very happy.

Having looked through the internals of the code and having made my own modifications to it to suit my own needs, I can tell you that what you’re wanting to do won’t be possible.

There are two reasons for this.

1) The plugin only modifies the OG tags for a post when it is added or updated from within the “new post” or “update” page. Otherwise, it doesn’t do anything except give you access to a few settings from the admin pages. This is actually the ideal way for the plugin to work, as this means there is zero overhead anywhere else on your WP site.

2) The plugin uses the default description and image for a post unless you change it manually. If you are wanting to go through and edit the description of every post the way you want it, then this is another reason you’ll need to go through the motions manually.

I don’t know what platform you’re using, but if you’re in Windows, and you don’t mind horsing around with a new app that may sometimes get you into trouble, there’s a fantastic tool I use to manage repetitive tasks called Pulover’s Macro Creator. It lets you create macros out of mouse and keyboard use. For instance, if the changes you want to make are purely automatic, I’d open however many tabs my system could handle at a time, then create a macro to click on the “Update” button, wait 15 or so seconds, then close the tab (cntrl+w), then repeat for however many tabs I’ve opened. It’s real hands-on, and sometimes incredibly frustrating to work with, but once you get the hang of it, you’ll find it’s really a useful tool.

• This reply was modified 6 years, 9 months ago by wornways.

This is really good to hear, George. Let me know when you publish the update and I’ll test it all out (since every single one of my posts uses a customized og:title that’s different from the SEO title) and report back to you.

Solved the disable updates question. There’s a plugin called “Easy Updates Manager” that lets me disable updates for a specific plugin.

Please respond to this post if you do an update that incorporates the ability to create custom og:titles as I’ve done. It’s also kind of important that you use the same “_webdados_fb_open_graph_specific_title” key if you do–which I’ve modeled after the key names already in use–so all my hard work won’t be undone.

Back in bid’ness. This is part of the reason why I shared the code I used to create custom titles with you. I wanted to be able to come back here and get it again if you did an update that didn’t include it. Please consider using the code. It works perfectly.

If not, please at least tell me how to disable automatic updating of a specific plugin.

Arrghhhh you killed my changes with your update. Now I have to put them back again. How do I prevent automatic update of a specific plugin? At least I have the code right here so I can just copy it back in.

Sorry about the indentation. It’s using the indentation set at that particular point in the files.

PS: I’ve changed all occurrences of “EAT_fb_open_graph_specific_title” and “EAT_fb_open_graph_specific_title” to “webdados_fb_open_graph_specific_title” and “_webdados_fb_open_graph_specific_title” in anticipation of remaining compatible with your next update.

The addition of this one feature makes all the difference.