# Xibo problem carbon

**URL:** https://community.xibo.org.uk/t/xibo-problem-carbon/38377
**Category:** CMS Features and Functionality
**Created:** [August 27, 2026, 8:18am UTC](https://community.xibo.org.uk/t/xibo-problem-carbon/38377 "2026-08-27T08:18:06Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Essam000000](https://community.xibo.org.uk/letter_avatar_proxy/v4/letter/e/90db22/32.png) [@Essam000000](https://community.xibo.org.uk/u/Essam000000)
#### Post date: [August 27, 2026, 8:18am UTC](https://community.xibo.org.uk/t/xibo-problem-carbon/38377/1 "2026-08-27T08:18:06Z")

</div>

Carbon\Carbon::createFromTimestamp(): Argument #1 ($timestamp) must be of type string|int|float, null given, called in /sites/deploy/4.5.1\_revanjordan/lib/Xmds/Soap.php on line 1377

---

<div class="post-metadata">

### Author: ![MrStefan](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/mrstefan/32/17330_2.png) [@MrStefan](https://community.xibo.org.uk/u/MrStefan)
#### Post date: [August 27, 2026, 9:38am UTC](https://community.xibo.org.uk/t/xibo-problem-carbon/38377/2 "2026-08-27T09:38:20Z")

</div>

Head to Administration → Settings → Defaults →  
**Disable** the following setting: “Should Layouts be automatically Published?”

It’s a bug in version 4.5.1

> <https://github.com/xibosignage/xibo/issues/3924>
>
> With DEFAULT\_LAYOUT\_AUTO\_PUBLISH\_CHECKB set to 1 in settings, we attempt to set… publishedDate on a draft Layout
> When adding a new Layout or editing a layout without \`publishedDate\` set on it this will cause an error when creating a timestamp from the \`$parent-\>publishedDate\` as it runs unconditionally with this setting enabled.
> 
> This will then cause lock issues and eventually timeout leaving user unable to publish any Layout. 
> 
> Temporary workaround in current 4.5.1 CMS version would be to set this setting to 0.

---

<div class="post-metadata">

### Author: ![Romolo\_Manfredini](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/romolo_manfredini/32/19662_2.png) [@Romolo\_Manfredini](https://community.xibo.org.uk/u/Romolo_Manfredini)
#### Post date: [August 28, 2026, 8:31am UTC](https://community.xibo.org.uk/t/xibo-problem-carbon/38377/3 "2026-08-28T08:31:51Z")

</div>

> [@Essam000000](#):
>
> createFromTimestamp()

It’s not the only one related to null values passed to createFromTimestamp(), another big one is in lib/Helper/DateFormatHelper.php  
replace around line 55

```auto
public static function createFromTimestamp($timestamp): Carbon
{
    return Carbon::createFromTimestamp($timestamp, date_default_timezone_get());
}

with:
public static function createFromTimestamp($timestamp): Carbon
{
   if (!is_null($timestamp)) {
       return Carbon::createFromTimestamp($timestamp,date_default_timezone_get());
   } else {
       return Carbon::createFromTimestamp(0, date_default_timezone_get());
   }
}

```

This one fix issues with soap when commands are scheduled

---

<div class="post-metadata">

### Author: ![natasha](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/natasha/32/18270_2.png) [@natasha](https://community.xibo.org.uk/u/natasha)
#### Post date: [September 2, 2026, 12:14pm UTC](https://community.xibo.org.uk/t/xibo-problem-carbon/38377/4 "2026-09-02T12:14:41Z")

</div>

An issue has been logged for this here: [4.5.1: a \*\*repeating\*\* Command event stops every player on that display getting its schedule · Issue #3931 · xibosignage/xibo · GitHub](https://github.com/xibosignage/xibo/issues/3931)

Thank you

---

<div class="post-metadata">

### Author: ![Ieuan\_Leigh](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/ieuan_leigh/32/19601_2.png) [@Ieuan\_Leigh](https://community.xibo.org.uk/u/Ieuan_Leigh)
#### Post date: [September 3, 2026, 12:10pm UTC](https://community.xibo.org.uk/t/xibo-problem-carbon/38377/5 "2026-09-03T12:10:43Z")

</div>

Hey,

This has been fixed in v4.5.2 which has just been released. You can find the release notes [here](https://docs.xibosignage.com/changelog#cms-v4.5.2).

Thanks 😀