simple question... how do i upgrade CB

Thank you.. getting there but hit fairly big snag... CSS.

It seems you changed the styling element names for many/most of the items in the new version. Is that correct?

We have spent quite some time CSS styling the way we want and as you can see in the two links below, the differences are quite large:

Old CB version: www.staging2.wodrocket.com/index.php/view-profile/userprofile/demo1

New CB version: www.staging3.wodrocket.com/index.php/view-profile/userprofile/demo1

Yes, we're using Bootstrap 3 and most elements will have boostrap 3 classes in addition to our own semantic classes where needed. Your CB 1.x custom styles are very unlikely to carry over to CB 2.x.

arrgh. Ok. I am getting knee deep in this. Here is the next items:

1. why (on the backend) does super user only see the tabs (public) for each user instead of the full data (phone, email, etc)?

2. when one user group logs in we get the following screenshot:

1. why (on the backend) does super user only see the tabs (public) for each user instead of the full data (phone, email, etc)?

I don't know, probably an access issue. Check that CB Core is public and published in CB > Plugin Management. Next ensure the tabs your fields are on are properly accessible in CB > Tab Management.

2. when one user group logs in we get the following screenshot:

Edit any existing CB menu items and correct their menu types. CB 1.x did not create valid internal menu links for Joomla 2.x and Joomla 3.x. These need to be manually corrected. Most likely login POST is submitting to the wrong URL.

I highly recommend searching around the forums if you should have any further issues. Most of your problems have already been addressed and are just standard pitfalls of a migration.

I have / had CB dialed in for our purposes. I want to upgrade but don't want to spend a ton of my time doing so. We have ~40,000 members and this is important but frustrating.

I LOVE this extension and appreciate all you do, but (just being honest here), I did not sign up to have a system that totally needs to be re-worked when improvements are made. You are asking we change links, CSS, custom scripts, etc, etc.

I have posted a job on Upwork to have somebody help us with this and want to know if there is a person / people you might recommend. I suspect, this is VERY easy for some.... just not for me.

CB 2.x is a migration. It's not a simple upgrade. We've made the process as simple as possible by migrating what we can during install. However, it's not foolproof like any migration. There will be issues as we can't account for the unlimited number of ways CB can be configured.

I LOVE this extension and appreciate all you do, but (just being honest here), I did not sign up to have a system that totally needs to be re-worked when improvements are made. You are asking we change links, CSS, custom scripts, etc, etc.

You should expect these kind of changes with any major version change. So for CB 3.0 expect another migration, etc.. I suspect however CB 3.0 will migrate much easier. Major releases are our chance to make the changes needed to move CB forward and also finally remove older APIs no longer used.

For example CB 3.0 will likely be Bootstrap 4 meaning additional style changes. However, with latest nightly we've moved all our custom classes out of bootstrap.css meaning you can turn CBs Bootstrap off and use your own customized Boostrap (of which there are many nice style generators). This effectively means styling CB is actually significantly easier now.

I have posted a job on Upwork to have somebody help us with this and want to know if there is a person / people you might recommend. I suspect, this is VERY easy for some.... just not for me.

It's not easy for anyone. You need to go through all of CB and ensure your configurations still make sense. To ensure view access levels and usergroups are setup fine still. To account for all the new parameters and changes to existing parameters. This all takes time.

I don't know what more to advise, sorry. I understand it's frustrating and it's certainly not something that should be done under a time crunch or anything of the sort. I highly suggest taking your time and carefully reviewing the changes on a clone site at your leisure to avoid becoming frustrated so you'll be better prepared for the live site migration.