calebprenger85

nothing works in spectra as intended.

i feel this this should be part of it. What if I have a column I need to insert 4 icons next to each other?

Oh ok, i completely missed that drop down. Thank you.

Problem is, I’ve opened a support ticket. I told you guys what I did to try to remedy the situation, you suggested the same thing I already told you I did, asked for a login, did the same thing I already did, now don’t reply to my emails.

Come on Spectra support. I need a fix for this.

I don’t think that is an ok work around. I can’t be expected to go through dozens of sites and do that with every page

I still don’t think it’s the way to go. It makes me look really bad as a web dev

Yes, they messed everything up. My only hope is they bring back these blocks. They were not necessary to remove to begin with.

I hate to be a jerk and all, and it’s great that they worked hard and did an “extensive public beta” which most of us didn’t know about. But this does not change the fact I have a large number of websites using this that are now broken.

Again, take woocommerce for example. They don’t just randomly change the way the entire plugin works, and the things they do change, they automatically update via their scripting.

Removing and deprecating blocks is not the solution here. Deprecation means I need to go and replace all these websites because it could be removed in a few days, weeks or months. Most of my clients will likely think I will do this for free and when I won’t, they will be upset. I guess this is why I try to write most things myself and don’t use other plugins people make…

It’s deprecation. That’s literally what it said on the websites that use advanced columns. The problem isn’t that I don’t know how to use containers. I can use them. My problem is what happens to the websites I created with these for the past 2-3 years? What about all my websites I currently am working on that are almost done and I used advanced columns to design them?

This is the problem. Breaking functionality and changing the way things work are huge problems and a good way to lose customers.

@delanthear no, that’s not what they did. If you install it on a new website, it’s gone. The only time it appears is on an old website. It shouldn’t have been done.

It seems a better course of action would have been instead of deprecating advanced columns, make a different block called container and keep the advanced columns. I would suggest an update to the plugin that adds support back in for this without deprecating. It would be like woocommerce suddenly changing the product category taxonomy name randomly for no apparent reason.

Rolling back is not a solution. We have many active sites with the UAGB plugin. It looks super amateurish on my part to be using the functionality of a plugin that just suddenly breaks for my clients or has a large warning that the block has been deprecated.

Here is some things that currently don’t work on the columns:

• When trying to select a single column, it’s not clear you are selecting a column, it still says the container is selected.
• Sometimes I have a row that has a background color, then i insert another advanced column in order to add a background image and then another advanced row on top of that to insert the content. This functionality no longer works with your new container block. I can insert a container, but I can’t have more than one column for whatever reason.
• I created a 2 column container, when i change the responsive screen size to tablet to apply a min height to one of the columns, or at least try to, that specific column crashes and no longer works
• This is an advanced feature, but I was using your helper classes for UAGB that were built in, in order to parse some CSS for other pages. I updated a specific site and it completely broke that website.
• I used to be able to push down to select a advanced column row, then down again to select a column, and so on. This functionality is gone.

There are many other issues. A layout block should not be deprecated. I understand the need to move on to other things and improving code, but with a layout block, many people have used things like that and it’s not good to just pull the carpet from under people like this. Even with a deprecation warning.