WP 5.7 update issue

Same issue here. Any plans to update the plugin?

Same here and I notice that the company behind this plugin is closing threads with similar issues without replying – so I assume this is an abandoned project by a scam company. DONT USE THIS PLUGIN with 5.5+

To all with the same problem, use “core rollback” to downgrade wordpress to 6.X or before version and use this plugin, later you can update your wordpress to the last version and that’s all.

• This reply was modified 3 years, 7 months ago by Richzendy.

To fix the issue just replace line 15 in the file bulk-block-converter/js/scripts.js, witch is:

wp.editPost.initializeEditor(‘bbconv-editor’);

with:

wp.editPost.initializeEditor(‘bbconv-editor’, ”, 0, {styles: []});

`To fix the issue just replace line 15 in the file bulk-block-converter/js/scripts.js, witch is:

wp.editPost.initializeEditor(‘bbconv-editor’);

with:

wp.editPost.initializeEditor(‘bbconv-editor’, ”, 0, {styles: []});`

Not working anyway. Is there any other way to resolve it? thanks ((

Hi everyone! Yes, i found the solution, but its requires make some changes in scripts.js file in plugin`s folder. So:

CHANGE THIS:

	$('<div />').attr('id', 'bbconv-editor').attr('style', 'display: none').appendTo('body');
	wp.editPost.initializeEditor('bbconv-editor', 'post', 1, settings);

WITH THIS:

const settings = {
		editorMode: 'visual',
		panels: {
			'post-status': {
				opened: true
			}
		},
		features: {
			fixedToolbar: false,
			welcomeGuide: true,
			fullscreenMode: true,
			showIconLabels: false,
			themeStyles: true,
			showBlockBreadcrumbs: true,
			welcomeGuideTemplate: true
		},
		hiddenBlockTypes: [],
		preferredStyleVariations: {},
		localAutosaveInterval: 15
	};

	$('<div />').attr('id', 'bbconv-editor').attr('style', 'display: none').appendTo('body');
	wp.editPost.initializeEditor('bbconv-editor', 'post', 1, settings);

• This reply was modified 3 years ago by mironezes.
• This reply was modified 3 years ago by mironezes.

But beware, this plugin has crucial dependence from WordPress core scripts, and next time when WP team will change them, you might have to find another solution. Anyway, besides my gratitude to plugin’s developers i wonder why so simple solution still wasn’t implemented

• This reply was modified 3 years ago by mironezes.
• This reply was modified 3 years ago by mironezes.