You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Button - simultaneous use these options - causes "Your server returned a 500 error." when trying to save the page:
using a "Gradient Fill" ("Linear" or "Radial") as the background of the button, instead of "Solid"
using an "Outline=ON" for the button
If under "Your server returned a 500 error." I click on "SEE DETAILS" > "ERROR DETAILS" - more detailed information about the errors is displayed:
Breakdance\AJAX\BreakdanceAjaxHandlerException: An exception has been thrown during the rendering of a template ("Array to string conversion") in "177273b38164851f6acbf973d4cdc417e031ac40" at line 13. in C:\xampp\htdocs\shop-test.com\wp-content\plugins\breakdance\plugin\ajax\api.php on 116
throw new BreakdanceAjaxHandlerException($callback_exec_exception->getMessage(), 500, $callback_exec_exception);
This issue was already posted by another user here (Jul 8, 2024): #1120
But there in response other users could not confirm this issue, because the author did not specify that the issue occurs only under simultaneous using "Gradient Fill" and "Outline=ON" - he only specified that "customize it with a background gradient".
Platform: PC Windows 10 x64
WEB-Browser: CHROME 131.0.6778.86
Server: Localserver XAMPP 8.2.12
PHP: 8.2.12
Apache 2.4.58
MariaDB 10.4.32
I have the following software versions installed:
Wordpress 6.7.1
WooCommerce 9.4.2
Breakdance Pro 2.2.0-rc.1
> I have "Debug Mode" enabled in "WordPress"
(this helps me quickly detect critical glitches in the plugins) I have these lines in the "wp-config.php" file :
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
define( 'SCRIPT_DEBUG', false );
P.S.
I hope this problem will be fixed soon, because it is critical for the design of my website, for which I purchased the "Breakdance Pro" license, and I am pressed for time before the planned launch of the website.
The text was updated successfully, but these errors were encountered:
Button - simultaneous use these options - causes "Your server returned a 500 error." when trying to save the page:
If under "Your server returned a 500 error." I click on "SEE DETAILS" > "ERROR DETAILS" - more detailed information about the errors is displayed:
Breakdance\AJAX\BreakdanceAjaxHandlerException: An exception has been thrown during the rendering of a template ("Array to string conversion") in "177273b38164851f6acbf973d4cdc417e031ac40" at line 13. in C:\xampp\htdocs\shop-test.com\wp-content\plugins\breakdance\plugin\ajax\api.php on 116
throw new BreakdanceAjaxHandlerException($callback_exec_exception->getMessage(), 500, $callback_exec_exception);
This issue was already posted by another user here (Jul 8, 2024):
#1120
But there in response other users could not confirm this issue, because the author did not specify that the issue occurs only under simultaneous using "Gradient Fill" and "Outline=ON" - he only specified that "customize it with a background gradient".
> I am attaching a video screen recording of this problem as a small MP4 file (6Mb).
https://github.com/user-attachments/assets/ab2778f4-b9db-40c2-92b4-7e645facfa9e
My Software and Settings:
Platform: PC Windows 10 x64
WEB-Browser: CHROME 131.0.6778.86
Server: Localserver XAMPP 8.2.12
PHP: 8.2.12
Apache 2.4.58
MariaDB 10.4.32
I have the following software versions installed:
> I have "Debug Mode" enabled in "WordPress"
(this helps me quickly detect critical glitches in the plugins)
I have these lines in the "wp-config.php" file :
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
define( 'SCRIPT_DEBUG', false );
P.S.
I hope this problem will be fixed soon, because it is critical for the design of my website, for which I purchased the "Breakdance Pro" license, and I am pressed for time before the planned launch of the website.
The text was updated successfully, but these errors were encountered: