Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider splitting the plugin into a legacy and modern edition #365

Open
Clorith opened this issue Dec 11, 2019 · 3 comments
Open

Consider splitting the plugin into a legacy and modern edition #365

Clorith opened this issue Dec 11, 2019 · 3 comments

Comments

@Clorith
Copy link
Member

@Clorith Clorith commented Dec 11, 2019

This is more a discussion point, but one that would help move things forward.

Currently the plugin supports WordPress 4.0 and onwards. As seen in various tickets, this is beneficial for users looking to upgrade from older version, but does limit us a fair bit in relation to improvements ahead of, and along with, WordPress core.

Would it make sense to fork the plugin, essentially making Legacy Health Check with the tools as they are now, that only receives bugfixes and security enhancements?

This would allow the main plugin to much more closely couple with core, remove backwards compatibility code, and basically make it easier to maintain with regards to porting code to and from core.

This of course has both pros and cons, and I want to hear the wider thoughts on it, and not just the voices in my head :)

@joyously

This comment has been minimized.

Copy link

@joyously joyously commented Dec 11, 2019

Actually, I wondered about this, because of a forum topic. I was going to recommend Health Check, but didn't know if it had the part that moved to core, so I couldn't tell if it would work on the older WP.
I think it would be nice to have only one to recommend, regardless of WP version. But I can see how that would be high-maintenance.
On the other hand, if all the code that is currently in core is moved to a file, that file could be required according to WP version.

@joyously

This comment has been minimized.

Copy link

@joyously joyously commented Dec 12, 2019

If there are two plugins, a user can install both at the same time. Would there be PHP name clashes with that?

@joyously

This comment has been minimized.

Copy link

@joyously joyously commented Dec 12, 2019

I'm thinking that Health Check should remain the same, and any further explorations should be done in a new Beta plugin with "Site Health" in the name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.