Joshua David Nelson

Hey again! Just following up to see if your issue was resolved or if you need further support.

I’m closing this issue due to inactivity, but if you need further help please reach out!

Peter,

There’s always a risk with any software for issues, but this plugin is actively maintained. I’ve lately recommended checking out PluginTests when researching plugins, see Archived Post Status’ page. I hope you find the plugin helpful, feel free to reach out for support on this forum!

You can sponsor my work on this plugin at https://joshuadnelson.com/donate/ or https://github.com/sponsors/joshuadavidnelson

Thanks!

All that said, you should actively work to be on a newer, and supported, version of PHP. Version 8.3 or higher right now, version 8.2 will get security updates until next year.

Also, I would push back on the claim “mysqli extension for PHP 8.x is not well-supported” it’s a core extension to the PHP project and has been for years now.

Hey James!

Thanks for reaching out about this. My approach for PHP support has largely been guided by the what the PHP project supports instead of WordPress core, with the mindset that I don’t want to support versions of PHP that are beyond end-of-life.

However, you make a great callout in regards to WordPress support of 8.x “with exceptions.” I think those exceptions are all pretty minor, but that’s a little bias of me. According to the stats, about 31.7% of WordPress users are on 7.4 at the time of writing, which is a pretty large group.

We’re not doing anything in this plugin that requires 8.x, so I’m open to going back to 7.4 minimum PHP until WordPress core bumps it’s minimum or we want to use features only available in a new version. I’m working on an update that should roll out this month, I’ll consider this some more and likely change it in that release.

As a workaround for now, you could download the current version of the plugin and change the “Requires PHP” header in the readme.txt to version 7.4 to side-step the issue.

Hey there!

If you remove the plugin or turn it off, the archive post status will no longer exist. The content will remain in your database, but unless you register that post status via another means, or reactivate the plugin, you won’t see the content on the site (front end or back end).

If you want to remove the plugin and keep the content accessible you can either change all the archived posts to another status (like draft or private perhaps) or add some code to your own plugin or theme to register the archive post status.

• This reply was modified 1 month, 2 weeks ago by Joshua David Nelson.

Hey there!

Sorry for the delayed response!

Archived posts are viewable to admin users with the read_private_posts capability. Those users also can see them listed via the “Archived” filter above the post table within the admin, at a url like: yoursite.com/wp-admin/edit.php?post_status=archive&post_type=post

Do you want to view archived posts in a different or another context (e.g. list them on the front end, make them publicly viewable, etc)?

Let me know if I can help further.

• This reply was modified 1 month, 2 weeks ago by Joshua David Nelson.

Hey there! Apologies for my delayed response, I didn’t get any notification for your post…

With this plugin active, assuming that there are no other post types using the post_tag taxonomy (which is the default condition), you should not see tag archives in the sitemap.

If you’re using an SEO plugin like Yoast SEO, default WordPress sitemaps might be disabled and your SEO plugin may be creating a sitemap – in some cases you can disable the archive pages themselves using one of these plugins, too.

Hey there, thanks for reaching out! These errors appear to be entirely related to the other plugin, so I don’t think there is much I can do to assist here. Let me know if you have any questions.

Thanks, I’ve connected with Support via email.

Hey there! Just following up to confirm the plugin has been tested and works for PHP 8.2 and 8.3.

Hey there! Apologies for the delayed response.

You’re on the right path here, you can use the content filter or place some code directly in your template or functions file. The status is actually archive following the same naming convention as WordPress core (where it’s publish not published, and trash not trashed).

Just a word of caution on using that filter – a lot of things go through it, so that message might show up in things like an excerpt view or archives, depending on your theme. You may want to limit your context further, by adding an additional check. For instance, if you only want that message to show up on the Single Post view you could use is_singular() in the if statement:

if ( is_singular() && 'archive' === $post->post_status ) {

I hope that helps!

Joshua

Hey there, just checking in to see if you needed any further help or if the proposed solution worked for you?

Hey there, just checking in on this again.

Hey Mark!

I’ve manually tested the plugin with WP version 6.5.4 and didn’t see any regressions. I’m working on a plugin update that will include bumping the WP support, likely releasing in the next couple weeks.

Thanks,
Joshua