Beware of Short codes

I really wish I understood that this would have broken even more than short codes. All of my accordion implementations are broken. I wish I knew how to go back.

Hi,

When you upgrade a plugin you should always read the changelog and review what changes are coming – especially in a major version upgrade like this.

I specifically put a !WARNING! in the change log at the very top, in order to alert upgraders to the potential problems they would face:
https://www.ads-software.com/plugins/wordpress-bootstrap-css/changelog/

As to my shortcodes, they’ve been working fine for months and any time anyone has reported a problem I have worked quickly to fix them.

Version 3.0 of Bootstrap is hugely different and I spent a LONG time reworking much of this to try to ensure they work with Bootstrap 3.0. If you have a problem, or spot a bug, please, feel free to come on and report it to help fix. I welcome that feedback at any time as you’ll see through-out these support forums.

To see an example of how to politely ask for help, and for the answer I gave to downgrade the plugin, please check out this support question:
https://www.ads-software.com/support/topic/can-you-add-back-bootstrap-v2-as-an-option-in-the-new-plugin

The 1 star rating you gave also isn’t helpful… I’m sorry the plugin doesn’t work for you as you’d hoped, and if you’d like to offer some feedback as to what wasn’t working for you, I’d be happy to take that on and work in some fixes for the shortcodes for a future release.

Thank you.
Paul.

Your style is very invasive. This should have been a new plugin, not an update because you totally forced people to choose a major new fork on bootstrap. This would break nearly every blog and that is behavior that warrants 1 star. Not even an option to let users decide if they want the new or old fork. Nothing graceful, nor respectful that you could be throwing peoples sites into severe disarray. To quote you:

Version 3.0 of Bootstrap is hugely different and I spent a LONG time reworking much of this to try to ensure they work with Bootstrap 3.0.

A more considerate approach would have not forced what you yourself say is “hugely different” upon droves of people totally abandoning what was the only way to go just 10 days prior. I was on the Bootstrap site and it was all about the other fork 11 days ago. It seems uncontenable that you think any site would be ready to completely change so quickly. And to a brand new fork that you yourself admit is buggy. Bugs don’t belong in production code. You offer a dropdown selection to select other Bootstrap OPtions (all with version numbers) so it seems odd that you would not give the option to use the fork that all sites are depending on. This would have allowed us to test and see if bootstrap 3.0 was ready or going to be compatible.

I stand at 1 star, if I’m the only person that feels this way I might reconsider but I believe you have abandoned your users for the sake of novelty.

Hi,

Your opinions are noted.

Unfortunately they don’t take into account any of the development (on top of anything that has gone into it, and is on going) required to do what you’re suggesting.

Also, what you’re advocating is displacement of responsibility of site management from site owners/managers, and placing it wholly on plugin developers.

Thanks for your comments and feedback.
Paul.

I’m not asking for the displacement of any responsibility. I’m responsible. However, I don’t want to continuously be forced to change development forks based on your development cycle. So I reverted to my backup, I’m removing the short codes and implementing pure bootstrap and then figuring out how to install bootstrap 2.3.2 and then properly creating a copy of my site on my development bench to examine the path to 3+ should I want it. What was a convenient plugin, has become a ball and chain that when stuck on the original fork, without any updates, could become a security risk.

You are free do develop as you want. I found it odd that with a plugin populated with so much advertising on the Dashboard, that you wouldn’t have used that area to give some notice. And in the plugin area where you advertise iControl, you couln’t have said “Upgrades to new fork of Bootstrap, which may require significant changes to your coding especially if you are using the functionality of 2.3.2.”

Sure you have to make a buck, but a little care in cultivating your free user base, would seem a more wise approach. But even with notice in the WP plugin itself, I would had to have left anyway. Once I saw that you will be auto upgrading, in the future, the thought of losing control over backups and revisions was enough for me to want to stay far, far away.

Cool, then I wish you all the best going forward.