Has anyone tried to downgrade from EE 3.0 to 2.10? any tips?

Yeah, use the backup you made before you upgraded to 3.x. You did backup right? 😉

No 2.10 Backup… as I said… it’s a new site, but to clarify, I began with a 3.0.3 Installation.

Thanks. R

My apologies. I’d recommend a manual downgrade… copy the template files, etc… unless it’s something huge.

Sorry to hear the add-ons you are looking for aren’t yet available. I have a feeling that 3.1 will bring a flood of them. Pedro is correct though, there is no supported way to downgrade, but your template files could definitely be brought into a new v2 install.

It’s not even so much the plugins… I can work through that, but rather the number of annoying issues the keep making me stop & start development…

R

Sorry to hear the add-ons you are looking for aren’t yet available. I have a feeling that 3.1 will bring a flood of them. Pedro is correct though, there is no supported way to downgrade, but your template files could definitely be brought into a new v2 install.

It’s not even so much the plugins… I can work through that, but rather the number of annoying issues the keep making me stop & start development… R

I’ll admit the bugs are getting frustrating. Some are pretty obvious and you wonder how they are not caught in basic testing (constant modal issues for example). Some are less obvious and are forgivable. However, the promise was quicker, smaller iterations that would result, in addition to other things, less bugs introduced. I stay optimistic as 3 has a lot of new code to stabilize and hope this trend declines, but I am getting concerned.

Hey Jeremy, can you let me know what constant modal issues you are having? If you’ve reported elsewhere, just drop me a link. Thanks!

Hey Jeremy, can you let me know what constant modal issues you are having? If you’ve reported elsewhere, just drop me a link. Thanks!

Hi Derek,

In reference to the various filepicker and/or RTE issues that persisted a couple updates. Some fixed. Some pending. Examples below. Forgiveable at this stage, but most or all seem like they would be somewhat obvious in testing and would expect to be caught before release. They are pretty much all things that a client would encounter on a near daily basis, and thus prevent us from actually deploying ee3. Again, lots of new code with ee3 so understandable, but need these kind of small things ironed out to be viable.

https://support.ellislab.com/bugs/detail/21204/fatal-error-cant-use-method-return-value-in-write-context

https://support.ellislab.com/bugs/detail/21205/fatal-error-class-ellislabaddonsfilepickerfilepicker-not-found

https://support.ellislab.com/bugs/detail/21227/buggy-display-of-images-and-buttons-in-rte

https://support.ellislab.com/bugs/detail/21248/cannot-select-an-existing-image-in-thumbnail-view

https://support.ellislab.com/bugs/detail/21309/trying-to-display-member-custom-fields-in-a-template-fails-with-error

https://support.ellislab.com/bugs/detail/21315/ui-issue

https://support.ellislab.com/bugs/detail/21344/file-picker-modal-not-sticking-to-allowed-directory-when-swiching-between-l

Ah okay Jeremy, I thought you means with modals in general. Thanks for sharing those in any case. I don’t want to minimize your experience either, as if you were bitten by those bugs it was certainly annoying.

However, most of those were reported in 3.0.0, fixed quickly, and involved specific environments. We do manual and automated testing, but with a self-hosted product, there are some issues that we simply won’t encounter until it hits the wild. Hopefully we will retain your confidence in the speed at which we have been addressing these issues.

I still have overall confidence. I’m still a cheerleader in the EE camp and I appreciate your engagement in the forums.

However, I encountered half the bugs I posted, the others I selected are for what I feel a common thread. I couldn’t even upload an image to an entry properly until I upgraded to 3.0.2 because of the filepicker issues. That’s a basic need. That’s my point without beating a dead horse… more qc on basic functionality before a release. Our hosting environment is your partner/sponsor Nexcess, which I assume/believe is running an optimized ee config that EL would have had input on. Nothing out of the ordinary here in that regard.

Looking forward to 3.1 😉