shawfactor

Resolving as I’ve not been able to replicate

“LH Archived post status” has nothing to do with both the archive widget and the concept of WordPress archives.

WordPress archives are just collections of old posts by month with the publish status. They are viewable by everyone. The archive widget just displays months which have published posts

My plugin does something different in that it creates a whole new archived post status and some simple options on when posts with that status should be displayed. The similarity in names is unfortunate and if I was building the plugin again I’d probably find another name.

I’m not sure of what you exactly want for your site but I’m confident it would require a small bit of custom code to change the default behaviour of the widget and perhaps the WordPress archives to work with the plugins archived post status and settings you’ve made in the way you want. This would be custom paid work on my part and hence not appropriate for this support forum, the plugin faq has the next steps if that is your preferred approach.

I am resolving this post for now but if I’ve misunderstood your problem and there is a bug I’ll still be monitoring the thread and will reopen if appropriate.

Resolving this for good order as it’s likely that the problem lies with another plugin doing something non standard

I will however monitor the thread and reopen if appropriate.

Gwyneth,

you are conflating a few different but related problems

firstly WordPress support for registering custom post statuses. Yes this has been outstanding for 13 years. But it’s quite easy to work around this on the classic editor. My plugin did and still does this using vanilla JavaScript and jquery.

However the block editor is uses react. My plugin did not support the block editor at all until I integrated imaths wp-status library. However as you pointed out there are two issues which do not currently work on the block editor

The auto draft problem. According to imath this is an issue with the block editor itself (which is now part of core). There is no fix via the library atm until block editor specific changes are made in core.

The inability to set draft, pending etc statuses on posts with future publish dates. The only post status available being scheduled. Imath has yet to respond on whether there is a library specific fix possible for that. I first raised that issue in February and followed up last week. I suspect that issue is library specific but I’m only guessing.

I suggest you look annd/or follow up the issues I raised on GitHub for the wp-status library. You’ll see it all there and additional follow might help clarify the second issue further. I know imath is busy atm with buddypress (as I am). But “The squeaky wheel gets the grease” as they say!

I will immediately incorporate any library updates into the plugin but as Im a php and vanilla is guy so I’m not going to spend days pondering react as this plugin currently works for my purposes.

This is likely caused by another plugin.

Have you disabled all other plugins, cleared the browser cache, and regenerated permalinks? If so does the behaviour still occurr?

2 stars is unfair, the issues you outline are real but unnoticeable for most users. I use it on several multi author sites and neither issue has ever been raised.

I realise that the issue is major for you but giving poor reviews is not the way to get things fixed. One of the issues (auto draft) at least (perhaps both) is core related so all plugins are in the same boat (hopefully one day it will be fixed). The other (no choice of status on scheduled posts) I’m following ip

But canning plugins by authors like me for who do it for the community (there is no upsell here I publish and support it here to help people) is discouraging to perhaps not what you are trying to achieve.

Thankyou, understood and resolved

There are two issues

The first issue with ie “auto draft” is (according to imath) an unavoidable issue with the current state of the block editor.

The second is the lack of any other status than scheduled when a future post date is set on the block editor . I’m yet to hear back from imath on that one

Imath wp-status library is used for all UI in the block editor for my plugin. I don’t know enough react to look at the issue myself and so best for both of us to follow the issues on github (search wp-statuses Imath) but if you can find workarounds let me know and I’ll look at incorporating them

To simplify plugin is actually three parts

1. My original plugin which only supported the classic editor
2. a library I have integrated called wp statuses that enables the gui for custom post statuses in the block editor (Gutenberg). Written by @imath
3. Some other functionality I’ve added

The issues you’ve raised both relate to to the library (2). And I’ve raised both with the author

His response on the first was:

Unfortunately this is a downside of the lack of extensibility of the Block Editor, to be sure to get the update button, I need to use another field to save the status to use and force the WordPress status to be private. Otherwise you get the Publish button and you cannot customize the post status.

So basically the first issue can’t be fixed for now until core improves the the block editor (classic should work fine). I agree it’s annoying

Ive followed my previous post up on the second issue (ie the inability to set any other status than scheduled for publish dates in the future) on GitHub with the library author and see what he comes up with.

No the plugin does not do that and I doubt you will find any plugin that does as the media library is designed for files on your server

More broadly CDNs are not generally used to save hosting storage, if your host has poor storage get a better host or offload it to an external storage service. Storage is cheap. A cdn is used to redice server load and deliver a faster website experience for your visitors by hosting copies of your media (and other content) on separate specialised servers that are often closer to the visitor.

If the plugin is not bringing a copy onto your server then let me know a sample media url and I’ll trouble shoot the issue

Depends what you mean?

if you mean bring a copy of the media into your library then yes the plugin can do that.

if you mean manage items in your cdn, then no, those items are on a different server

Resolving this for good order, as I don’t believe the issue is with my plugin but I will monitor the thread and if appropriate reopen it

Subscribers are logged in right?

if so then there is no way the problem has anything to do with LH Private buddypress, as the plugin does absolutely nothing if the visitor is logged in.

the plugin also does not interfere with the registration. The only thing the plugin does is redirect non logged in visitors away from buddypress component pages

Have you tried deactivating all plugins or raising the issue with the chat plugin author (buddypress does not have a chat component although maybe you meant private messaging).

Thankyou all good enhancements/fixes much appreciated. Just need to set up a sub folder test environment to implement and test