Cory Lamle

Seems like the isolated users fixes would be better served as induvial user patches, that are then rolled out into a consistent release pattern. Simply releasing a version because a user has a bug doesn’t indicate the plugin has a good SDLC. Unless the bug is critical in nature it shouldn’t be pushed out to the entire distribution chain. Imagine if WordPress rolled out its updates as often as this plugin did.

Seems like there are still issues the plugin needs to work on to help deliver more quality code with less risk to users. Releases come with risk and constantly have to monitor multiple updates weekly isn’t a good practice for companies and for users who would like to depend on your software.

Every time a release is pushed we have to run a series of regression tests to make sure that there’s no conflicts in the entire ecosystem . A weekly schedule is pretty aggressive and then intermittent releases indicates the plugin should consider looking at it’s full SDLC practices. Of all the plugins/themes we use this one is constantly needing updates at a ratio of 5/1 which indicates a poor SDLC. Hopefully things calm down for the plugin and things can settle down to a more reasonable release ratio…

Wishing you the best in your endeavors!

Hi Pial,

Thanks for the quick turn around! I have tested the latest version V.1.5.15 and the issue is now resolved on my end. Keep up the good work!

Cheers~

Hey Miles,

Based on my setup, I’m only seeing the headers that are messed up. I don’t have very many widgets but the ones I do have all look ok, I think its just the headers.

Quick question are you making sure to only wp_register_script and wp_enqueue_style the plugins scripts when needed or on the entire wp-admin?

BTW Nice plugin, its simple and well thought out…