This looks like the same issue which was present in SPPB3 in the frontend editor.
But this time in the backendeditor.

The Emoji is supported, if the Customer saves the text in the frontend Editor.
As soon as he tries to save the Text within the Backend, it throws the error.

I have tested this with Version 5.0.8.
Frontend works as intended and in the backend it throws the reported error.

https://www.joomshaper.com/forum/question/21791?order=newest#qa-answer-106014

To fix this issue, The backend editor needs to transfer the icon correctly encoded. SPPB4: "title":"\ud83d\udd25 The Best Web Hosting" SPPB5: "title":"🔥 The Best Web Hosting"

@Ofi Khan please forward this to the developers.

@Micheline Potvin

Workaround for you, so you can use emojis in front and backend.

• open the file "administrator/components/com_sppagebuilder/editor/traits/PageTrait.php"
• scroll down to this line "public function savePage()"
• now scroll down a little bit more until you see this line "$model->savePage($data);"
• before the "try{" you can add the following line

$data->content = json_encode(json_decode($data->content));

It should look like this.

                if (!$canEditState) {
                        unset($data->published);
                }
                $data->content = json_encode(json_decode($data->content));
                try
                {
                        $model->savePage($data);
                }
                catch (\Exception $e)
                {
                        $this->sendResponse(['message' => $e->getMessage()], 500);
                }

Save the file and you are now able to save the page in front and backend editor.

Have a nice day.

@Ofi Kahn and @Ahmed sakr This is indeed a problem within the backend of SPPB3. When creating a new article and adding a emoji "🔥" joomla will throw an error regarding SPPB.

Speichern fehlgeschlagen. Fehler: Incorrect string value: '\xF0\x9F\x94\xA5te...' for column `xyz-joomla`.`xyz_sppagebuilder`.`title` at row 1

Tested with Joomla 4.4.5 and SPPB 3.8.10.

Since SPPB 3.x is EOL, it is possible you wont get an update/fix.

@Ofi If no update/fix is possible let me know, I will provide him a workaround to fix the issue. If he can not switch to 5.x for some reason.

@Ahmed sakr You only need to change the encoding of the column from utf8mb3_general_ci to utf8mb4_general_ci.

ALTER TABLE `osf5f_sppagebuilder` CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;

You need to replace the prefix “osf5f” with yours :)
If you encounter a similar issue, then you have to change more tables and columns to utf8mb4_general_ci.