# WAIT: PHP fatal error; nestable slider custom options breaks and becomes stdClass

**URL:** <https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404>\
**Category:** Bugs\
**Tags:** v2-3-6\
**Created:** [June 8, 2026, 6:24pm UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404 "2026-06-08T18:24:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![vigilante](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/vigilante/32/3421_2.png) [@vigilante](https://forum.bricksbuilder.io/u/vigilante)\
**Post date:** [June 8, 2026, 6:24pm UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404/1 "2026-06-08T18:24:58Z")

</div>

**Browser** : Chrome 148  
**OS** : Windows

This is the third time we’ve seen the same page break on a website with PHP fatal error due to the corrupted custom options of a nestable slider.

The PHP error is:

```plaintext
PHP Fatal error: Uncaught TypeError: stripslashes(): Argument #1 ($string) must be of type string, stdClass given in /www/xxxxx/public/wp-content/themes/bricks/includes/elements/slider-nested.php:1190
Stack trace:
#0 /www/xxxx/public/wp-content/themes/bricks/includes/elements/slider-nested.php(1190): stripslashes(Object(stdClass))
#1 /www/xxxxx/public/wp-content/themes/bricks/includes/elements/base.php(2941): Bricks\Element_Slider_Nested->render()
#2 /www/xxxxxx/public/wp-content/themes/bricks/includes/frontend.php(748): Bricks\Element->init()
#3 /www/xxxxx/public/wp-content/themes/bricks/includes/elements/container.php(946): Bricks\Frontend::render_element(Array)
#4 /www/xxxxx/public/wp-content/themes/bricks/includes/elements/base.php(2941): Bricks\Element_Container->render()
#5 /www/xxxxx/public/wp-content/themes/bricks/includes/frontend.php(748): Bricks\Element->init()
#6 /www/xxxxxx/public/wp-content/themes/bricks/includes/elements/container.php(946): Bricks\Frontend::render_element(Array)
#7 /www/xxxxx/public/wp-content/themes/bricks/includes/elements/base.php(2941): Bricks\Element_Container->render()
#8 /www/xxxxx/public/wp-content/themes/bricks/includes/frontend.php(748): Bricks\Element->init()
#9 /www/xxxxx/public/wp-content/themes/bricks/includes/frontend.php(902): Bricks\Frontend::render_element(Array)
#10 /www/xxxxx/public/wp-content/themes/bricks/includes/builder.php(1395): Bricks\Frontend::render_data(Array, ‘content’)
#11 /www/xxxxxx/public/wp-content/themes/bricks/includes/builder.php(321): Bricks\Builder::builder_data(1183)
#12 /www/xxxxxx/public/wp-includes/class-wp-hook.php(341): Bricks\Builder->enqueue_scripts(‘’)
#13 /www/xxxxx/public/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)
#14 /www/xxxxx/public/wp-includes/plugin.php(522): WP_Hook->do_action(Array)
#15 /www/xxxxx/public/wp-includes/script-loader.php(2329): do_action(‘wp_enqueue_scri…’)
#16 /www/xxxxxx/public/wp-includes/class-wp-hook.php(341): wp_enqueue_scripts(‘’)
#17 /www/xxxxxx/public/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)
#18 /www/xxxxxx/public/wp-includes/plugin.php(522): WP_Hook->do_action(Array)
#19 /www/xxxxx/public/wp-includes/general-template.php(3208): do_action(‘wp_head’)
#20 /www/xxxxx/public/wp-content/themes/bricks/header.php(7): wp_head()
#21 /www/xxxx/public/wp-includes/template.php(814): require_once(‘/www/xxxxx…’)
#22 /www/xxxxx/public/wp-includes/template.php(749): load_template(‘/www/xxxxxx…’, true, Array)
#23 /www/xxxxx/public/wp-includes/general-template.php(48): locate_template(Array, true, true, Array)
#24 /www/xxxxxx/public/wp-content/themes/bricks/template-parts/builder.php(2): get_header()
#25 /www/xxxxx/public/wp-includes/template-loader.php(132): include(‘/www/xxxxx…’)
#26 /www/xxxxxxx/public/wp-blog-header.php(19): require_once(‘/www/xxxx…’)
#27 /www/xxxxxx/public/index.php(17): require(‘/www/xxxxx…’)
#28 {main}
thrown in /www/xxxxxx/public/wp-content/themes/bricks/includes/elements/slider-nested.php on line 1190

```

I cannot view the frontend of the page or the Bricks edit UX, both will throw the PHP fatal error and crash.

However, from WP backend I can duplicate the page and then the Bricks editor will open.

When I edit the duplicated page and look at the Slider (nestable) settings, I see this:

 ![nestable slider options](https://forum.bricksbuilder.io/uploads/default/original/3X/3/d/3d389b1c3553b65e0699955d8ee44af0056b9e6e.jpeg)

The custom options were always valid, it used to be this:

```json
{"type":"loop","autoWidth":true,"height":"35vh","direction":"ltr","keyboard":"global","rewind":false,"gap":0,"start":0,"easing":"linear","speed":9000,"interval":0,"autoplay":false,"pauseOnHover":false,"pauseOnFocus":false,"arrows":false,"pagination":false,"mediaQuery":"max","drag":"free","autoScroll":{"speed":1,"pauseOnHover":false}}

```

I know there are other posts that blame the Enable Media Replace plugin for this, but in our case, even though we have this plugin, it has not been used for the images on this particular page. The images have been the same since the original build.

In fact, there is another page with a slider (different images) that hasn’t corrupted once, but this page keeps breaking.

I don’t know why the JSON string keeps getting changed into an object type, or at least Bricks thinks it is? There is a data type conversion issue or a rendering problem or something.

In any case, this is not robust and the slider code needs to have some data/error checking to prevent this. The client is already hesitant to edit this page cause nobody knows when it’s going to randomly blow up with fatal crash again.

For more information, I went into the databasse directly and looked at the Bricks content in the `_bricks_page_content_2` option.

The broken slider looks like this:

```auto
s:12:"lbydf-slider";s:8:"interval";s:1:"0";s:7:"options";O:8:"stdClass":19:{s:4:"type";s:4:"loop";s:9:"autoWidth";b:1;s:6:"height"......

```

Notice the “sstdClass” reference.

When I duplicate the page and fix the custom options, it looks like this:

```auto
s:12:"lbydf-slider";s:8:"interval";s:1:"0";s:7:"options";s:335:"{"type":"loop","autoWidth":true,"height"...

```

Now it’s just a 335 char string.

Why in the world does it randomly switch to a stdClass? And why doesn’t the slider have some data type checking to avoid a fatal crash?

I don’t really know what to do to fix it or find the root cause of the corruption.

Hopefully this information helps someone!

In the meantime I’m going to have to find some other tool to make this slider.

---

<div class="post-metadata">

**Author:** ![itchycode](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/itchycode/32/4542_2.png) [@itchycode](https://forum.bricksbuilder.io/u/itchycode)\
**Post date:** [June 9, 2026, 6:52am UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404/4 "2026-06-09T06:52:50Z")

</div>

Hi @vigilante ,

Thanks for reporting the issue.

Does the corrupted data only happen on 1 specific page? Will this page be updated by other users without an admin role?

Possible to reproduce the issue + clone it as a staging site, and provide admin access to [help@bricksbuilder.io](mailto:help@bricksbuilder.io)?

Regards,  
Jenn

---

<div class="post-metadata">

**Author:** ![vigilante](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/vigilante/32/3421_2.png) [@vigilante](https://forum.bricksbuilder.io/u/vigilante)\
**Post date:** [June 9, 2026, 6:37pm UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404/5 "2026-06-09T18:37:40Z")

</div>

I can’t reproduce it, no idea what triggers it.

It broke again today right after I fixed it yesterday. I’m pretty sure the client didn’t touch anything because they emailed saying “it’s still down for us” like they didn’t even get a chance to see the fixed page.

That tells me nobody actually had to edit the page for it to corrupt the settings.

I only have this slider on two pages, and the other one hasn’t broken at all.

The interesting thing about this one is that the whole slider was copied from the other page. E.g. they selected the slider element, copied, then pasted in the builder on the ‘bad’ page. It worked for quite a while though.

Another interesting thing is when I click on the slider element and then click the “CONTENT” tab and then click the “OPTIONS” accordion, there is a brief half a second where the proper JSON string appears and then is immediately replaced with the broken `[object Object]` message. Almost like it’s breaking in real time only when the custom options are loaded - but that can’t be true because I can see the stdClass object directly in the database.

Here is a screen recording seeing the settings flash.  
[Watch Video](https://kommodo.ai/recordings/uJBEEn4SoWCxhYgX5i7I)

[![](https://api.prod.komododecks.com/redirector/recordings/uJBEEn4SoWCxhYgX5i7I/preview.gif)](https://kommodo.ai/recordings/uJBEEn4SoWCxhYgX5i7I)

It’s possible when I repaired this by copying settings directly in the database, that I didn’t have the PHP object perfectly correct.

I was more careful this time to make sure I copied it perfectly. And I’ve asked the client to mess around again and see if it breaks again.

I’m afraid there is not much more I can offer you except maybe a list of the plugin stack or access to the backend so you can poke around. But I can’t make the problem trigger.

---

<div class="post-metadata">

**Author:** ![itchycode](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/itchycode/32/4542_2.png) [@itchycode](https://forum.bricksbuilder.io/u/itchycode)\
**Post date:** [June 10, 2026, 12:31am UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404/6 "2026-06-10T00:31:01Z")

</div>

Hi @vigilante ,

Based on your video, it seems like certain JavaScript code is changing the content.

I can’t replicate this following your video steps.

Could it be a certain browser extension causing this?

When the issue occurs again, can you please try NOT to solve it first? Please clone it as a staging site and send admin credentials to [help@bricksbuilder.io](mailto:help@bricksbuilder.io) so we can check.

Regards,  
Jenn

---

<div class="post-metadata">

**Author:** ![vigilante](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/vigilante/32/3421_2.png) [@vigilante](https://forum.bricksbuilder.io/u/vigilante)\
**Post date:** [June 16, 2026, 2:51am UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404/7 "2026-06-16T02:51:47Z")

</div>

I can try to do that but it’s a client site and I would have to use a backup plugin and then clone it on my own server. I’m wondering if changing the environment that much would prevent proper testing.

We’ll see, it hasn’t broken yet in about a week so far.

---

<div class="post-metadata">

**Author:** ![vigilante](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/vigilante/32/3421_2.png) [@vigilante](https://forum.bricksbuilder.io/u/vigilante)\
**Post date:** [November 10, 2026, 6:51pm UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404/8 "2026-11-10T18:51:27Z")

</div>

Reporting that it has happened yet again.

The page hasn’t been edited in two months and suddenly out of the blue fatal crashinig when anyone visits the page. Once again it’s because of the slider:

```auto
PHP message: PHP Fatal error: Uncaught TypeError: stripslashes(): Argument #1 ($string) must be of type string, stdClass given in /www/xxxxxxx/public/wp-content/themes/bricks/includes/elements/slider-nested.php:1190

```

The custom options JSON string disappears and is replaced with some placeholder `[object Object]`

I can’t edit the page in Bricks since it fatal crashes there too.

The only way to fix is clone the page, which magically lets me edit the clone, remove the custom options broken string, change back to default options instead.

Then I open the DB and copy the Bricks content from the clone to the regular page and everything works again.

This time I didn’t put the custom options back again, I just left it at default options.

Honestly this is getting crazy, just add some code to detect the improper object or something, just so we don’t have to deal with a full fatal crash.

---

<div class="post-metadata">

**Author:** ![itchycode](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/itchycode/32/4542_2.png) [@itchycode](https://forum.bricksbuilder.io/u/itchycode)\
**Post date:** [November 11, 2026, 2:43am UTC](https://forum.bricksbuilder.io/t/wait-php-fatal-error-nestable-slider-custom-options-breaks-and-becomes-stdclass/39404/10 "2026-11-11T02:43:32Z")

</div>

Hi @vigilante

**To investigate this further, we need a staging copy where the affected page still produces the error.** Please preserve the broken state before repairing it, and send the staging URL, temporary admin access, affected page URL, and installed Bricks version to [help@bricksbuilder.io](mailto:help@bricksbuilder.io), including a link to this thread.

You do not need to know how to trigger the corruption again. A staging copy that already contains the broken data gives us something concrete to inspect. Please confirm that the error remains present after cloning.

Preventing the fatal error and identifying what changes the saved options are separate issues. **Without an affected staging site or repeatable steps, we cannot take the investigation into the recurring data conversion further.** The error message alone does not provide enough information to establish its cause.