Skip to toolbar

Find answers, ask questions, and connect with our
community around the world.

Forums Forums Bug Reports Error 500, Error log blocks/content-toggle/block.php Reply To: Error 500, Error log blocks/content-toggle/block.php

  • Alexis

    October 3, 2020 at 9:28 am

    Hi @MoinMollie ! There are two ways to directly access the plugin files: (1) through the plugin editor, which is the easier way, and (2) via FTP. Before doing any of them to edit the plugin files, please deactivate the plugin first and ensure that you have the replacement file ready.

    For the first one, you can go to WordPress’ built-in plugin editor by clicking on Plugins > Plugin Editor at the sidebar. You may see a popup warning about directly editing the plugin files if it’s your first time going there, but it should go away after clicking on “I understand”,. Then, you should be able to see a dropdown list containing the list of plugins you currently have. Pick “Ultimate Blocks” from the dropdown list and then click on “Select”. Afterwards, using the Plugin Files scroll list right below the plugin dropdown list, go to src > blocks > content-toggle > block.php. After clicking on it, you should be able to see the content toggle block’s PHP source code. Copy the original source code to a separate file, then paste on the original the contents of the replacement file. Finally, save it by clicking on update file.

    In case the first method doesn’t work, you’ll need to use an FTP client to use the second method. This guide shows how to access the WordPress theme folder in your current host through an FTP client, but, in our case, we have to go to the WordPress plugin folder instead. After reaching the plugin folder, go to ultimate-blocks/src/blocks/content-toggle. Then, rename the original block.php file before pasting the replacement file.

    After you’re able to save the replacement file in either method, you can reactivate the plugin. In pages where you didn’t turn on “Enable FAQ Schema” for the content toggle block, nothing should change at all. In pages where you turned it on, some changes in output are expected when the bug that causes your current issue comes up again (and, as soon as you take note of the changes that happen, you can hide them by turning the FAQ schema off). Either way, please let us know what would come up this time.