Dear Peter,

I hope this email finds you well. I wanted to bring to your attention an issue I am experiencing on my website. I have uploaded some screen capture videos to the following URL: https://imgur.com/a/81H0mqz. The videos show that the Wayback Date is being displayed on the post list page, but when I click on the Wayback Date, it redirects me to the homepage of the Wayback. Additionally, when I manually enter the Post URL, it says “Not Archived”.

I would greatly appreciate it if you could take a look at the plugin and let me know if there is an issue. I have also provided some information about my website’s debug settings below:

• WordPress Version: 6.1.1
• PHP version: 7.4.13
• MySQL version: 5.7.32
• CURL version: 7.69.1
• Snoopy Installed
• Safe mode: Off
• open_basedir: Off
• Default PHP execution time limit: 120 seconds
• PHP Memory: 101.81 MB of 1024 MB (10% used)
• RAM: 14 GB of 31 GB (46% used)
• CPU Load: 5%

Please let me know if you need any additional information. Thank you for your assistance.

Best regards,
Occlu.

Just hopping in to see if there are any plans to update this plugin. It continues to work great but is now being flagged by WordFence since there have not been updates for so long. I recognize that it is a small personal project, so no worries if not.

Any posts I’ve written since May 2021 show in my WordPress dashboard as “queued”. The posts actually are archived, though whether that’s due to the plugin or the Wayback Machine’s usual spiders & bots is hard to say.

Is this plugin still functioning?

I saw https://www.ads-software.com/support/topic/private-posts-visiblity/ had mentioned that private posts are honored with this plugin.

However, what about if a site has “discourage search engines” checked under WordPress’ reading settings and/or if it’s marked as a “private” site via the WordPress Network/Multi-site site settings?

I could see people potentially wanting to install & prep this plugin on a site in development prior to launch, and they don’t want things being sent off until it’s ready (which then just has that one setting to change rather than doing that as well as needing to hold off on implementing this plugin until then also.)

I could see the page/post/etc. listing status column saying something like “Not Applicable on Non-Public / Robot-Disabled Sites” instead of the “Not Applicable” message shown for private content to help highlight the cause of the message/status.

What are your thoughts on this? Is this actually already being done (they’re just left as “Queued”; which makes me think they might not be getting explicitly blocked like they should be…?) & the status message just isn’t specifying it, or is it something to be implemented yet?

As an aside, is this plugin on GitHub or similar to help support community-based development? If so, I think it’d be good to have a link to it in your plugin description to help those that might want it (also helps with plugin selection to know there’s a good level of support/opportunity for growth out there for the plugin.)

I have a question about lines 327–329 in lh-wayback-machine.php:


$permalink = get_the_permalink($post_id);
$post_status = get_post_status( $ID );
$timestamp = get_post_meta( $post_id,


Should $ID be $post_id?

I was wondering, do snapshots created with this plugin respect post visibility? If I installed this and had posts published but set to private, would the wayback machine archive it? Ideally I’d hope it wouldn’t even send the URLs at all for private posts, but at minimum it’d be reassuring to know that at least the content wouldn’t be visible in the archive until the post is set to public.

Hi Shawfactor

Thanks for the plugin. Is it still working under 5.3+?
How can we actually monitor which pages have been saved when?

Have you meanwhile added the features mentioned in the other support thread so it would match the capabilities of archiver – the other Wayback machine plugin.

Thanks

• This topic was modified 5 years, 4 months ago by toremo. Reason: forgot a passage

Thank you so much for making this!

I am wondering if I can set it up so that it takes a snapshot of specific posts twice a day. I have an RSS feed embedded into a post, and I don’t believe it will trigger a screenshot because no changes will be made to the post itself. And IF it is taking screenshots for every change to the RSS feed embedded, then I feel bad and am wasting wayback machine bandwidth. (I’m sure you’re busy, do you have a link to an article explaining how to tweak your php file to achieve this?)

TL;DR Can you add the option to toggle this for only select posts? And can you allow for an automated daily screenshot?