Tim Codex

Thank you Mohamed. Your code is what I am looking for. Thank you very much.

@linardsn Thank you for spending time writing the code. I will definitely test the code.

However, as I know, WordPress FSE has two back-end parts: the editor and the editor iframe (which actually has the blocks). The editorScript is for working with the editor only, not the blocks inside the editor iframe. We will use editorScript to add/remove features of the editor (like inspectors, and toolbars) but cannot access the editor iframe to modify its structure.

Thanks again.

Hello @linardsn

The .block-editor-inner-blocks contains all inner blocks so we can’t hide it.

The reason I want to remove them (unwrap them), so the whole structure of blocks in the editor will be similar to the front-end structure.

This is a must because many layouts are leaning on the Grid and Flex layouts that can be broken if there are any blocks that interfere between the parent wrapper and the children.

Thanks for the reply.

@alextintea

I replied. Thanks.

Although the plugin is free, it does not excuse the developer’s decision to add an extra step during the uninstallation process. The developer should still prioritize the user’s experience and respect their time, regardless of the financial aspect. By forcing users to complete an unnecessary step, the developer is showing a disregard for the user’s time and an unwillingness to prioritize their needs.

Additionally, while the feedback collected by the developer may bring benefits to other users in the future, it is not a valid reason to force users to complete an extra step during the uninstallation process. There are other polite ways to collect feedback, such as a separate link near the uninstall link on the plugin page, that do not inconvenience users during the uninstallation process. The fact that the feedback may bring benefits to other users does not justify the developer’s decision to put their own interests above the users’ needs and force them to complete an unnecessary step.

In summary, if the developers don’t respect users’ experience as well as time and put their interests above the users’ needs, it’s reasonable to call them “greedy developers”.

@threadi

Dear threadi,

Thank you so much for taking the time to respond to my question. Your advice is greatly appreciated and I will consider implementing the option for users to set custom widths for columns on mobile devices if requested.

Your suggestion to start with one option and then supplement it based on user feedback is very wise and I will keep it in mind during my plugin development.

Thank you again for your help, I truly appreciate it.

@bcworkz Thank you very much. It is still not working in Heading / Paragraph blocks (Full Site Editor) even with the 2023 theme.

Thanks for your reply.

@catacaustic Thank you. I set the fill and the size for the SVG in my scss file. Here is the screenshot of my inspector:

The problem is that if I right-click and choose Edit HTML on the SVG, then just enter (edit nothing) and the SVG will show. I think there is something else with the Browser DOM.

Do you have any ideas? Thanks a lot.

@faisalahammad Thank you very much for the reply.

I tried the method and I got another error:

“editor” is undefined

Could I know what is the reference that I need to import to use this object?

Sorry for late replying to you. It’s lunar new year in my country.

Thank you in advance.

Thank you. I followed.

Many plugins are using this impolite method doesn’t mean it’s right. Lots of developers chose not to have this kind of greedy development in their plugins due to the fact that they respect the others’ time and user experience.

You have all rights to show a feedback link near the de-active link so I have my own freedom in choosing what I want to do but when I click the de-active link, it should de-active the plugin immediately without any extra step.

Hello,

This support forum is for MagOne Lite theme, not for MagOne premium version (no matter from ThemeForest or Elements).

If you want request support for Premium Version, you need a license from ThemeForest at: https://themeforest.net/item/magone-responsive-magazine-news-wordpress-theme/14342350

Thanks for understanding.

@djennez Thank you.

Thank all you guy very much.

I removed W3 Total Cache which changed my wp-config.php and .htaccess file, then I restored back those file and everything works well again.

Appreciate!

• This reply was modified 4 years, 11 months ago by Tim Codex.

Happy to hear that.