Ship to WordPress.org Plugins Repository?

[georgestephanis]

It feels like this would be a lot more useful, and automatically support upgrades when needed, if this was deployed to the WordPress.org plugins repository over a link to a zip on dropbox.

I've used this GitHub action in the past to handle automatic deploys to .org -- https://github.com/10up/action-wordpress-plugin-deploy -- and would be delighted to help out with a PR to manage it.

[otarhe]

Sure we can start preparing for this whenever you're ready.

[ned-bs]

Why not?
I didn't realize that there is some updates till I have issues.

[ned-bs]

So, any plan for that.
I put reminder to my phone and check every month if there is an update. It doesn't make sense :)

[otarhe]

Sorry for the inconveniences, we're still reviewing the best way we can use for deploying the plugin.

[Garconis]

This would be nice. Currently the plugin has no way of notifying you that an update exists, let alone being able to update it from the backend.

The only way to update is to add the new plugin file from GitHub, but that then wipes all the settings from the previous version.

[otarhe]

@Garconis

This would be nice. Currently the plugin has no way of notifying you that an update exists, let alone being able to update it from the backend.

The only way to update is to add the new plugin file from GitHub, but that then wipes all the settings from the previous version.

• We're still reviewing the plugin and may retire it in favor of another method that does not require you to install or manage it manually, as it would be manged/updated automatically from the WordPress install but there are no time line for the release date now.

• Currently, updating the an old version of the plugin does not wipe the data from the database. Data from the plugin is only removed when the plugin is uninstalled.

[runephilosof-abtion]

Since there is no time line for the perfect solution, could you deploy it to Wordpress.org plugins repository for now.

Perfection is the enemy of good.

[georgestephanis]

A couple possibile paths forward (and I'm not on the team or directly impacted by this any longer, so this is just outside context provided hoping that it's helpful) --

@austinginder wrote a great article on running updates through github here: https://anchor.host/using-github-to-self-host-updates-for-wordpress-plugins/ -- sometimes it can be easier to run things like this outside of the WordPress Plugins Repository as it's only useful to a limited subset of hosting setups.

There's also the "Update URI" header that can be added to point updates specifically elsewhere: https://make.wordpress.org/core/2021/06/29/introducing-update-uri-plugin-header-in-wordpress-5-8/ and a proof of concept on how to leverage it: https://gist.github.com/CruelDrool/4cc70b819a33793396456c5ddb81781d as well as a working implementation by @NickGreen here: a8cteam51/plugin-autoupdate-filter#10 (there are a couple subsequent PRs as well that merged into the file that does the bulk of the work)

[Garconis]

Please add to WordPress.org repo

[otarhe]

Please add to WordPress.org repo

Thanks for the feedback. We're discussing the best option to deliver the plugin easily to all users.