Shocking new ! The widget "Responsive text block" is now deprecated ? :o

I’m not using the Gutenberg blocks. I’m using the Classic Editor and very happy about it just like 5 other millions of WordPress users.

I’m working with WPBakery and Elementor. While working with WPBakery, I WANT and I NEED a responsive text block.

I demand that you revert this decision and do not deprecate this text block.

Thanks

I see it nowhere. See screenshots below.

Indeed, I raised a separate ticket about the woodmart core plugin.

Now I checked the new Text Block plugin and it seems (on the frontend at least) exactly identical as the old Responsive Text Block.

Is it really impossible to simply migrate the old text block to the next one? The settings are exactly the same… it’s just not worth it spending hours and hours just migrating those old identical text to new text blocks and recopy pasting each setting.

Alright, it just took me 3 hours to replace all the deprecated “Repsonsive Text Block” by the new “Text Block” for just ONE website only.

Let me inform you that I simply don’t accept this. I’m a webmaster building lots of websites. I can’t spend my time on such kind of maintenance.

I request from you to find a solution so you transfer the code of your new Text Block into the Responsive Text Block automatically, or any other alternative solution.

You said that I don’t need to transfer but I disagree. If you deprecate something, of course I need to transfer at some point because it’s “deprecated” so one day it will disappear at some point in later releases. You will obviously not keep deprecated things in the theme forever.

Therefore, I demand :

1) that in future releases, you please think twice about the choices you make. Many your users (agents) buy your theme with the expectations to use it in long-term, and don’t want to redo their work because of this kind of decisions.

2) that you provide a system/query that performs the transfert of widgets between the old and new one byitself. I can’t spend hours and hours just to transfert that, taking screenshot of all the settings of the old widget and reselecting them all 1 by 1 in the new widget.

Thanks for your understanding
Simon

Hi Artem,

I understand your answer. However, please understand my point of view as well.

I like my work and I like to do it well. When you take a decision to deprecate something, this word has a meaning. Deprecating something means that :

1) it won’t be (actively) maintained anymore => it could still be maintained for critical or security issues, but there won’t be real maintenance on it anymore

2) may be subject to suppression in the future even if you say now that you’ll not remove it

3) it is never recommended to keep deprecated elements alive in a website.But still, I do not like using elements that are deprecated, not now and not in the future.

Please undertand the consequences of your choices. Your choice to deprecate this widget has the inevitable consequence that anytime in the future, one day (even if it is in few years later) I will have to do this job of migrating those old widgets to the new one. You say the contrary but it is obviously not true. Of course you’ll not keep deprecated things in a theme forever.

Therefore, I kindly write again my demand for you to provide a way to automatically migrate the old widgets to the new widget. Settings are “identical” across the old/new text block, therefore I am sure that something can be found to try to migrate them automatically.

Thank you for your understanding
Simon

Hello,

Alright, then in this case the flag “deprecated” should be removed because :

1) you will keep maintaing this widget
2) you will never remove this widget

Based on these two points, the situation doesn’t answer to a case of depreciation.

Thanks
Simon

You also removed the word “responsive” in the next widget although it’s confusing.. the new one is also responsive. So I’d rather call them :

Responsive Text Block v1

Responsive Text Block v2 (recommended)

with no use of depreciation

Then remove the word responsive as well from the old one, because for users who search “text” in the list of widgets. They’ll end up with both of them. They’ll see an old one “responsive” and a new now where there is no responsive in the title. Yes I know they are both responsive, but at first sights for users it may appear confusing. So better align both titles as below I think:

Text Block

Text Block (old)

I think that would be better agreement than the current situation

Would it be possible to get something like a query that would list all the “posts” where the deprecated text block has been added?