Commenters entering emojis causing failure to save record

[johnegerton15]

I've got comments up and runnig ok but when a user is using their mobile phone to leave a comment, they're often using the emojis on their phone keyboard.

This cases Engage to send the email to admin (to say the comment has been entered) but the user gets an error saving that the record could not be saved.

Has anyone experienced this and found a workaround?

[nikosdion]

That's a database issue. Your database version, database driver, and PHP must support UTF8MB4 and Joomla must install database tables with the UTF8MB4 encoding (the default for more than 7 years now).

If you have Joomla 3.7 or later, PHP 7.0 or later, and MySQL 5.6 or later (assuming your host has not intentionally removed UTF8MB4 support, something I have never seen yet I must note) you can take a backup of your site with Akeeba Backup and restore it with both Force UTF-8 and Detect UTF8MB4 selected in the database restoration page to force the tables to use UTF8MB4.

[nikosdion]

Can you please give me the full path (after public_html) and the line number shown next to the item #0 under "Debug information"?

[johnegerton15]

Hopefull;y this is ok:

The error reported at the top of the screem is as follows - I've removed the parts that would disclose by DB name and prefix:

Save failed with the following error: Incorrect string value: '\xF0\x9F\x98\x89\xC2\xA0...' for column MYSQL_DBNAME.DBPREFIX_engage_comments.body at row 1

From the debugger, here's the 7 log entries:

akeeba.runpluginstrait - Event "onComEngageDispatcherBeforeDispatch" resolved to class Joomla\Event\Event -- called from Akeeba\Component\Engage\Administrator\Dispatcher\Dispatcher->triggerPluginEvent at [ROOT]/administrator/components/com_engage/src/Mixin/TriggerEventTrait.php line 79

infoakeeba.runpluginstrait - Event "onComEngageCommentsControllerBeforeExecute" resolved to class Joomla\Event\Event -- called from Akeeba\Component\Engage\Administrator\Controller\CommentsController->triggerPluginEvent at [ROOT]/administrator/components/com_engage/src/Mixin/TriggerEventTrait.php line 79

infoakeeba.runpluginstrait - Event "onComEngageCommentsControllerBeforeMain" resolved to class Joomla\Event\Event -- called from Akeeba\Component\Engage\Administrator\Controller\CommentsController->triggerPluginEvent at [ROOT]/administrator/components/com_engage/src/Mixin/TriggerEventTrait.php line 79

infoakeeba.runpluginstrait - Event "onAkeebaEngageGetAssetMeta" resolved to class Joomla\Event\Event -- called from Akeeba\Component\Engage\Site\Helper\Meta::getAssetAccessMeta at [ROOT]/components/com_engage/src/View/Comments/HtmlView.php line 222

infoakeeba.runpluginstrait - Event "onComEngageCommentsControllerAfterMain" resolved to class Joomla\Event\Event -- called from Akeeba\Component\Engage\Administrator\Controller\CommentsController->triggerPluginEvent at [ROOT]/administrator/components/com_engage/src/Mixin/TriggerEventTrait.php line 79

infoakeeba.runpluginstrait - Event "onComEngageCommentsControllerAfterExecute" resolved to class Joomla\Event\Event -- called from Akeeba\Component\Engage\Administrator\Controller\CommentsController->triggerPluginEvent at [ROOT]/administrator/components/com_engage/src/Mixin/TriggerEventTrait.php line 79

infoakeeba.runpluginstrait - Event "onComEngageDispatcherAfterDispatch" resolved to class Joomla\Event\Event -- called from Akeeba\Component\Engage\Administrator\Dispatcher\Dispatcher->triggerPluginEvent at [ROOT]/administrator/components/com_engage/src/Mixin/TriggerEventTrait.php line 79

[nikosdion]

No, that's not what I need. Reproduce the error on your site. You see the error page, the one you printed as PDF. Towards the top of the page there is a section called "Debug information". Right below the big text with the error there is a <pre> tag with items #0, #1, #2, etc. Next to each of these numbers there's a long path and a line number. I need this path and line number shown next to the item #0.

[johnegerton15]

I've tried multiple times again today, the site will only bring up the debug console at the bottom of the page rather than the full inline report I got yesterday! I've turned on DEBUG SYSTEM to YES, changed ERROR REPORTING to MAXIMUM and still, just the popup debugger at the bottom. I never log into the front end, always just the backend.

Any idea how I can trigger that full inline report again ? (and thanks so much for all the help... really appreciated).

[nikosdion]

You just need to be a Super User, and to have set Debug System to Yes.