Absolute disaster of an update

  • The big banner on the page I manage proclaimed something along the lines of “this won’t change anything on the front end, only the back end” yet you changed HUGE amounts of CSS IDs and class names and changed how several of the widgets worked. There was no way this wasn’t going to break hundreds/thousands of sites that did even some basic CSS customization. Why did you change those?

    On top of just a huge amount of changes that were clearly going to change the look of anyone’s site even from a standard upgrade, making it so everyone with a child theme needed to go in and play code detective to over the weekend because they were getting angry clients wondering why their sites at best, look weird and at worst, completely stopped working.

    Did you even test the new update on any sites other than your own internal developments sites? Any beta testing with outside users? There might be thousands of users with different setups but with these sweeping changes, you needed to have to have tried it with at least a few dozen/hundred test scenarios…

    So if you are reading this looking for tips to fix the site, you will need to open up inspector and find the CSS IDs / class names and swap them to the new IDs and classes and then go from there.

Viewing 4 replies - 1 through 4 (of 4 total)

  • I totally agree with you. They changed class names and CSS IDs and that changed the display of all websites that was using a child theme with CSS changes.

    They should publish a list of class names and IDs that have been modified so that we can identify them more easily and not have to do detective work as you said.

    I found a short-term solution to downgrade the theme’s version to 2.1.8 until I figure out what changes are needed for the website to work with the new 3.0.0.6 update.

    Among other things it is said that it should have no impact except with respect to some customizations perhaps made to the child theme, but it is not so.

    As far as I’m concerned, I had customized only one thing and added two mu-plugins, which I proceeded to delete before the update.
    I also tried to switch to the parent theme on which no hand had been made before updating (thus losing any default option, even minimally modified, such as colors, background, layout…) and by doing so also in the Home are added sections in wrong places, the pages made with Elementor appear randomly paginated and with all wrong alignments and seem to have completely “lost” the responsive capabilities set in Elementor, and above all the pages created by WP Customer Area completely block the browser and do not are able to be executed (by performing a rollback everything works again).

    This is therefore proof that the problems do not derive from customizations and third-party plugins, but from the theme itself.

    I hope they rethink everything otherwise there is no other solution than not updating and in the meantime changing the theme in staging, also because this is not an update but a real “new theme”

    Where can I download version 2.1.8 of colormag ?

    Hi @tamerax, @hemartin54, @mominet, @chrismb78,

    We deeply apologize for any inconvenience caused by the recent update to our theme. We understand that this update has caused significant issues for users with child themes, including yourself, and we sincerely regret any negative impact it may have had on your website.

    Our intention behind the update was to incorporate the latest technology and enhance compatibility with other resources. However, we acknowledge that it has affected the customization of your site through the child theme. If you have not customized the theme using the child theme and have relied on the default features, you would greatly benefit from the theme update.

    Please provide us with an example of the customization you made on your site so we can offer you appropriate references. If you require customization assistance from our support team, we are here to help.

    Regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Absolute disaster of an update’ is closed to new replies.