Posts by anonymous84327

3 posts
  • Has been a member for 1-2 years
anonymous84327 says

I would like to add that:

Deprecated: Assigning the return value of new by reference is deprecated in ...\option-tree\ot-loader.php on line 369

Deprecated: Assigning the return value of new by reference is deprecated in ...\option-tree\includes\ot-settings-api.php on line 843

Deprecated: Assigning the return value of new by reference is deprecated in ...\option-tree\includes\ot-meta-box-api.php on line 275

Running PHP 5 .3

As a side note, OptionTree didn’t trigger any deprecated warning.

3 posts
  • Has been a member for 1-2 years
anonymous84327 says

Sorry I meant OptionTree 1.1.8 and not 1.8 (which doesn’t exist) but you should have guessed that.

3 posts
  • Has been a member for 1-2 years
anonymous84327 says

This message is intended to Derek Herman (@valendesigns)

I’m speaking on the behalf of a few developers that used OptionTree 1.8

Today we’re upgrading our themes using OptionTree 1.8 to the new version OptionTree 2.0.9 — And we find it really cumbersome. Key features from previous version are missing. Please read on.

Before we had 2 files:

  • theme-options.xml for the options
  • theme-options.txt for the data

Now we have only one file:

  • theme-options.php for the options

We believe that you should really have released this new version under an entirely new plugin instead of an update to the previous OptionTree, because there is nothing to do with the previous version as it’s missing key features like theme-options.txt which I can’t understand how any theme developer is willing to release a theme without data prefilled in the backend!

We’re not saying OptionTree 2 is bad, all we’re saying is that it doesn’t respond to the same needs as the previous version did. Releasing this new plugin as an update to OptionTree 1.8 was a really big mistake in our opinion as it literally broke thousands of perfectly-working sites, and more than annoying both end-users, support-providers, developers and customers.

We actually tried to force keeping OptionTree 1.8 for our current themes by renaming the plugin so it wouldn’t get updated by WordPress, but we weren’t able to do so as there would be too much errors if another instance of OptionTree would have been installed in parallel, having to rename most functions names, a real mess! So we dropped this possibility.

The new “Theme mode” is definitely a good thing as this will prevent this same scenario to occur again in the future where plugin/theme update is forced, leaving no choice to both end-users and developers.

I believe without the “Theme mode” and after what happened with this invasive, unwanted update (as most sites were working perfectly well and nobody asked anything but to keep it that way, and now we’re all forced to provide irrational development work to restore previous working feature – if even possible!) we would have just dropped OptionTree for another framework or even our own custom solution.

Another serious regression is the obsolescence of get_option('option_tree');... can we ask why it isn’t possible anymore to retrieve all the data at once?

Anyway, good work but bad strategic choice: a new incompatible plugin should not replace a previous well-established and perfectly working plugin.

From one of us:
Imagine if each time there is a new version of jQuery, all previous version would get replaced with the new one instantly, on all servers, on all sites, leaving any script depending on it responsible for sudden incompatibility.
This is what happened with OptionTree. The way WordPress leaves no choice to end users to keep previous branches of plugins should have been considered before releasing it as an update, and with no warning, no indications whatsoever on how to keep the previous version for end-users, as the “uninstall” button wouldn’t work because OptionTree is “active”... so it’s a really cumbersome process to simply revert back to OptionTree 1.8 once the end-user accidentally upgraded to OptionTree 2:
  1. Step Fail: The end-user tries to hit the “uninstall” button next to “OptionTree 2” but it doesn’t work, they get an error returning that “OptionTree is active”
  2. Step Fail Bis: Trying to simply “delete” OptionTree returns the same error
  3. Step 3: They have to figure out that switching to another theme that is NOT using OptionTree would make OptionTree “inactive” – took me a few minutes, as an experimented developer.
  4. Step 4: Switch to any other theme that does NOT use OptionTree
  5. Step 5: Uninstall OptionTree 2
  6. Step 6: Install OptionTree 1.8
  7. Step 7: Re-activate the theme that uses OptionTree
  8. Step 8: Ignore the WordPress constant warning about plugin update

What a mess! and it’s not over yet!

Thanks Derek for the hours, days if not weeks of unpaid and unrewarding work we had to provide because of this absolutely unwanted plugin update. — from a few web developers who regret not having chosen another alternative back in time