Mak
Forum Replies Created
-
@emrevona I tried it out. It solves the problem. Thank you!
@emrevona The next/previous posts based on published date, not category.
Thank you!
Forum: Themes and Templates
In reply to: [GeneratePress] Add category links to bylineThank you, that’s perfect.
- This reply was modified 3 years, 4 months ago by Mak.
I tried it out locally and it works well. Perfect! Thanks for looking into this and providing that plugin.
I sent the information about what plugins I’m using and what site maintenance I’ve done in the last year.
I used multiple database backups to piece together the last known social image URL for each page. Here’s the info I could find:
May – 293 posts with social url / 325 total posts
Aug – 242 posts with social url / 350 total posts
Sept – 242 posts with social url / 375 total posts
Nov – 106 posts with social url / 400 total postsSo the number of posts with the originally selected social URLs has kept shrinking.
I’ve done a few bulk operations during this time:
1. Used WP Fastest Cache to clear out post revisions and comment spam, then shrunk the posts/comments tables.2. Bulk-edited every post to update a setting.
3. Bulk deleted all tags
4. Bulk-edited the categories for batches of posts
I went back to a DB backup from 6 months ago. It has most of the social image URLs. So what I’m going to do is re-insert the records into wp_postmeta, instead of doing the insanely tedious task of relinking manually.
It would be nice to know WHY these got unlinked in the first place. Going forward, I’m going to have to keep track of the metadata in a spreadsheet so I don’t have to try to repair this problem again. It would be nice if there were a feature that could help detect this problem in the first place.
I used the image uploader as you described (Post SEO Settings > Social > Social Image URL > Select Image) when I originally wrote the posts. All posts showed the correct social image when I originally shared them on social media.
Now 300 of my posts are unlinked from their social image URLs and are showing the site logo instead.
Here’s an example of one post with this problem: https://makolyte.com/csharp-sending-query-strings-with-httpclient/
I can see there’s one og:image tag, which is the site’s logo:
<meta property=”og:image” content=”https://makolyte.com/wp-content/uploads/2019/12/makolyte-icon-128-e1575419011285.png”/>When I originally wrote this post, I selected this image as the Social Image: https://makolyte.com/wp-content/uploads/2021/11/sending-query-strings-with-httpclient.png (it shows this as Attached to the post)
It cropped it and saved this image:
https://makolyte.com/wp-content/uploads/2021/11/cropped-sending-query-strings-with-httpclient.png (says Unattached)These images exist on disk and you see they exist if you navigate directly to them.
I did some digging through the code. It looks like _social_image_url in wp_postmeta data is used when you’ve selected an image. The following SQL shows which posts don’t have a social image URL:
SELECT * FROM wp_posts p LEFT JOIN wp_postmeta m ON p.ID = m.post_id AND m.meta_key='_social_image_url' WHERE p.post_status='publish' AND p.post_type = 'post' AND m.meta_id IS NULL;Well, that’s not cool. 75% of my posts no longer have a social image url. I’m not sure how that happened.
- This reply was modified 3 years, 6 months ago by Mak.
Forum: Plugins
In reply to: [Easy Table of Contents] Code changes for 2.0.18 and 2.0.19?What a strange response. It’s obvious you aren’t reading what I’m writing.
Sorry, but I’m going to have to leave a bad review.
- This reply was modified 4 years, 1 month ago by Mak.
Forum: Plugins
In reply to: [Easy Table of Contents] Code changes for 2.0.18 and 2.0.19?I haven’t tried the new releases yet.
Forum: Plugins
In reply to: [Easy Table of Contents] Code changes for 2.0.18 and 2.0.19?Thanks!
Figured it out. The proxy is passing in HTTP_X_MIDDLETON_IP for the real origin IP. I added this to the trusted origin IP list, and now it’s not blocking me.
Interesting problem
Forum: Themes and Templates
In reply to: [GeneratePress] Upgrading to > 3.0 without changing appearanceThanks Leo. I went ahead and updated.
I tried the build (1.3.1) and can confirm that it fixed the problems. Thanks!
