Every time I try to install this plugin I get:
Warning: include(/home2/maindirectory/site/wp-content/plugins/frontrom/vendor/composer/../../includes/Upgrades/Upgrade.php): failed to open stream: No such file or directory in /home2//maindirectory/site/wp-content/plugins/google-calendar-events/vendor/composer/ClassLoader.php on line 444
Warning: include(/home2//maindirectory/site/wp-content/plugins/frontrom/vendor/composer/../../includes/Upgrades/Upgrade.php): failed to open stream: No such file or directory in /home2//maindirectory/site/wp-content/plugins/google-calendar-events/vendor/composer/ClassLoader.php on line 444
Warning: include(): Failed opening ‘/home2/maindirectory/site/wp-content/plugins/frontrom/vendor/composer/../../includes/Upgrades/Upgrade.php’ for inclusion (include_path=’.:/opt/cpanel/ea-php73/root/usr/share/pear’) in /home2/maindirectory/site/wp-content/plugins/google-calendar-events/vendor/composer/ClassLoader.php on line 444
I have deleted and reinstalled it, but I still get the same error.
]]>Great idea and effort to have plugin that would enable Gutenberg editor to function in the way it does Elementor Pro at commercial product level, covering complete templating structure with WYSIWYG/Gutenberg blocks editor.
During testing I’ve found some incompatibilities and errors, firstly to mention is current version 0.7 that has disfunctional Composer classes in install files and totally non-functional.
Version 0.6 is working okay yet some Gutenberg specific plugins are conflicting and this plugin’ theme could get disabled.
From my personal perspective during testing there are several advantages of this plugin over other Gutenberg template/page builders, most prominent are numerous content widgets and also option to rename page, header and entire theme. Still on the other side template structure is functioning differently than Elementor and other builders, here with this plugin users are supposed to include template page as content sections into their newly creating pages, differently than assigning in before mentioned.
So, this was to extend introduction of this plugin to interested WP members and to give some hints and thanks to the author(s), regards.
Any idea how to make it work with the “allowed_block_types” filter? It works in the backend but not frontend.
]]>Nice idea, but the plugin doesn’t do anything in the front end.
]]>Thanks for working on this plugin.
I have a clean local install (no other plugins) with busy multisite. The plugin is not working.
When editing in front, does not load. When returning to the back it is inside the iframe.
]]>