Best practice to Upgrade an existing CB Site from CB 1.91 and Joomla 2.5.24 to CB 2.0 and Joomla 3.3

I am looking into upgrading each and everything for my current (progress in work) CB page consisting of various CB and Joomla Plugins, based on Joomla 2.5.24 and CB 1.91.

I made a testcopy and uploaded RC2, to find the following:

Conditional fields plugin won't work, not compatible. My Registrationforms heavily rely on conditional fields. Wasn't it, that this plugin should have been incorporated into 2.0? What next here?

When i login into frontend, i will get a 1064 error, but where to find the details of this error?

I will now unpublish all incompatible plugins, but this will break, of course the website

Any page to inform about compatibility on behalf of CB plugins, may they be incubator like conditional fields or 3rd party? This would help a lot in planning the upgrade. (Perhaps a sticky?)

Also, what is the best practice to upgrade? First upgrading everything in 2.5.24 to the latest versions and then unpublish everything and upgrade the core? Some plugins work in 2.5 and 3.x environments, some have different versions for 2.5 and 3.x like UddeIM and my template, so any insight is truly appreciated.

And, what about doing a separate download section for CB 2.0 and the according files? It is a pain, looking for something in current download directory.


Thanks and best

Please note there is no guarantee of functionality for incompatible plugins. We're doing our best to maintain a legacy layer to ensure the plugins can still function, but there maybe some that are unfixable in CB it self. Incubator projects will be receiving new releases shortly after CB 2.0 goes stable to fix the compatibility issues.

Wasn't it, that this plugin should have been incorporated into 2.0?

No, not in CB 2.0. Conditionals will be built into the core in a later 2.x release or even 3.x if necessary.

When i login into frontend, i will get a 1064 error, but where to find the details of this error?

Enable debug mode and maximum error reporting in Joomla global configuration then retesting should expose the error.

Any page to inform about compatibility on behalf of CB plugins, may they be incubator like conditional fields or 3rd party?

Please see the below topic.

www.joomlapolis.com/forum/6-news-and-publicity/226118-cb-20-plugin-compatibility-issues

Also, what is the best practice to upgrade? First upgrading everything in 2.5.24 to the latest versions and then unpublish everything and upgrade the core? Some plugins work in 2.5 and 3.x environments, some have different versions for 2.5 and 3.x like UddeIM and my template, so any insight is truly appreciated.

For CB you typically just update CB then update your plugins to latest.

And, what about doing a separate download section for CB 2.0 and the according files? It is a pain, looking for something in current download directory.

Our package builder below lets you build a single installer for any number of plugins you'd like to include in the install.

www.joomlapolis.com/downloads/cb-package-builder

We'll also be improving our download section further with a future update to JP it self.

Hi Kyle,

thanks for your reply. Unfortunately i am stuck between two things.

I need the conditional fields AND i need this:


Re: feature # 4246: I understood it that way, that i can (multiselect) the (searchable) fields, which should apply to that specific userlist. So i can have different userlists (and searches) with common and different fields to search in, right?
Once 1.10.0 is released you'll edit your userlist and select "Specific searchable fields" for "Searchable fields:". Once you do it'll display directly below it the new parameter "Fields to search:". This parameter is a multi-select with all your CB fields that are marked searchable. You select exactly what fields you want to be displayed as search criteria for your userlist. Yes, this will provide exactly as requested.



This has been a year ago, where you said, this feature would be in 1.10, but it wasn't but slated for 2.0 release. Now i am either stuck to 1.9.1, without this feature or 2.0 without conditional fields.

So what to do now? Or is there another solution in order to present profilefields based on usergroups or other fields?

Concerning Downloadpage: It is hard to find anything, i am not talking about the package builder but to find the latest version of software. I would like to have a list, where i can see, which plugin has been updated when, so i can figure out, which one to update, which i could then put into the package builder.

Thanks and best

Re: feature # 4246: I understood it that way, that i can (multiselect) the (searchable) fields, which should apply to that specific userlist. So i can have different userlists (and searches) with common and different fields to search in, right?

Yes, you'll be able to select specifically what searchable fields to show on your userlist.

This has been a year ago, where you said, this feature would be in 1.10, but it wasn't but slated for 2.0 release. Now i am either stuck to 1.9.1, without this feature

CB 1.10 and CB 2.0 development branches merged into just CB 2.0.

2.0 without conditional fields.

CB Conditionals will work fine in its next release after CB 2.0 goes stable. Right now the focus is on getting core CB done and ready. Once it is I'll be upgrading all of our plugins.

So what to do now?

Don't upgrade a live site to CB 2.0 until the plugins you need are also ready.

Concerning Downloadpage: It is hard to find anything, i am not talking about the package builder but to find the latest version of software. I would like to have a list, where i can see, which plugin has been updated when, so i can figure out, which one to update, which i could then put into the package builder.

CB 2.0 Plugin Management in backend will let you know when a plugin is out of date. CB 2.0 also includes our new admin module with an update feed that will also inform you of plugin updates on the backend control panel of Joomla.

My problem is:

I was last year under the impression there would be a 1.10 with #4246; that would have been that solution for me, because i need this feature.

When you said, there won't be a 1.10, this was a real drawback for me. So i can go for 2.0, without conditional fields or stay with 1.91 without #4246, neither very appealing.

Do you have some sort of roadmap, when you will have 2.0 stable and furtheron conditional fields? This is a showstopper for me, because i couldn't go live for about one year now, without having a clue, when it would work out in the end. As i said before: 1.10 released and i would have had all the time in the world to wait for 2.0 and could have been live. Now i am still in beta and will have to wait. So we are not talking about a live site at all ... <sigh>

But anyway, thank you for getting back.

Best

Do you have some sort of roadmap, when you will have 2.0 stable

What's on our ticket list below is all that remains. We're expecting an RC3 followed by Stable depending on how RC3 testing goes. How long these stages take is subjective to what issues we find during testing.

forge.joomlapolis.com/projects/cb/issues

furtheron conditional fields?

Incubator projects won't receive new releases until CB 2.0 Stable has been reached. I'll be starting with the smallest/simplest plugins first and working up to the more complicated (GJ being last). CB Conditional is probably somewhere in the middle. So I suspect within a week or two after CB 2.0 Stable has released, but that's just a guesstimate at best.

This is a showstopper for me

All the feature does is let you specifically select what fields you want to be searchable on your list. There's a couple workarounds you can do to accomplish this now. You can add all searchable fields to your userlist then use CSS to hide the ones you don't want searchable or you can have only the fields shown on the list be searchable then add other fields that you want searchable, but not displayed to a column then hide them in that column using CSS. I really can't imagine this feature being a complete showstopper, but if you want help setting up either of the two then prepare the userlists and I can write the CSS to hide them as needed if you'd like.