Hi, I’m using the Trade Theme by ThemeTrust, which comes bundled with SO PB. Suddenly my SO pages’ revisions are simply reverting back to the previous versions, and sporadically reverting to text (keeping the SO widget code in place).
I am hosting with SiteGround, disabled all caching plugins, and run their master cache flush. I’ve been using SO for years and maybe this came up once before but it was so brief I didn’t consider it.
I reverted back to 2.4.19 from the latest 2.6.7 to no avail, and to Widgets Bundle 1.11.3 from 1.11.8 but it didn’t help.
Thanks for your continued support.
WordPress Environment
WordPress
Home URL https://peoplefirst.tech
Site URL https://peoplefirst.tech
WordPress Version 4.9.6
WordPress Multisite No
WordPress Memory Limit 128M
WordPress Debug Mode No
WordPress Debug Log No
WordPress Script Debug Mode No
WordPress Cron Yes
WordPress Alternate Cron No
Background tasks Yes
Active Theme
Trade Child by ThemeTrust.com – 1.0.5.1525923658
Trade (Parent) by ThemeTrust.com – 1.0.5
Active Plugins
Black Studio TinyMCE Widget by Black Studio – 2.6.2
Child Theme Configurator by Lilaea Media – 2.3.0.2
Duplicator Pro by Snap Creek – 3.7.0
Easy Smooth Scroll Links by pandasilk – 2.1.1
Google Analytics Dashboard for WP (GADWP) by ExactMetrics team – 5.3.3
Last Modified Timestamp by Evan Mattson – 1.0.4
Login Logo by Mark Jaquith – 0.9.0
Page Builder by SiteOrigin by SiteOrigin – 2.4.19
SiteOrigin CSS by SiteOrigin – 1.1.5
SiteOrigin Widgets Bundle by SiteOrigin – 1.11.3
Web Server
Software Apache
Port 443
Document Root [redacted]
PHP
Version 7.1.17
Memory Limit (memory_limit) 768M
Maximum Execution Time (max_execution_time) 120
Maximum File Upload Size (upload_max_filesize) 128M
Maximum File Uploads (max_file_uploads) 20
Maximum Post Size (post_max_size) 128M
Maximum Input Variables (max_input_vars) 3000
cURL Enabled Yes (version 7.59.0)
OpenSSL OpenSSL 1.0.2k 26 Jan 2017 (268443839)
Mcrypt Enabled Yes
Mbstring Enabled Yes
Loaded Extensions Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, bz2, calendar, ctype, curl, dba, dom, enchant, hash, fileinfo, filter, ftp, gd, gettext, gmp, SPL, iconv, session, intl, json, ldap, mbstring, mcrypt, standard, mysqli, pcntl, mysqlnd, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, Reflection, imap, shmop, SimpleXML, soap, sockets, exif, sysvmsg, sysvsem, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, cgi-fcgi, memcached, Zend OPcache
MySQL
Version 5.6.36
Database Character Set utf8
Database Collation utf8_general_ci
SOLVED!
Adding a goddamn emoji was the culprit. Removed the offending smiley and the issue goes away.
I can also confirm that this issue does not occur on non-SiteOrigin WP pages that contain an emoji. They update fine.
Hope this issue report is useful for future updates to your fine product.
Hi,
That’s odd! Can you please clarify which emoji caused this issue? Also, which widget was used to add it? I ask as we tried a few and I can’t seem to replicate this issue. To confirm, did this issue occur when all non-SiteOrigin plugins are activated?
Hi Alex,
I retested it this morning with nearly all plugins deactivated (the list is in the first frame of this screencast). Hope this helps…
https://www.dropbox.com/s/js1sc3t8l8o6l08/emojitest_sm.mp4?dl=0
Hi Healthconnection,
I’m unable to replicate this issue on a server without mod_security, but I am able to replicate this issue on a server that does. Is mod_security (or a similar security module) present on the server you’re using? If you’re not too sure, I would reach out to your hosting provider and ask if mod_security is installed and if it is, are there any records of you getting blocked with it?
Hi Alex,
I can confirm my host, Siteground, uses mod_security on all shared environments:
https://www.siteground.com/kb/how_does_siteground_protect_my_website/
Zach
Hi Zach,
Thanks. I’ve logged this as an issue with the development team – here’s the GitHub issue. I’m not 100% sure we’ll be able to fix this, but we’ll definitely take a look and see if this is something that can be avoided/fixed.
No problem, Alex. It’s not a big issue on our end. One thing I’m wondering is whether adding the characters as a hex code or something like being enclosed in a [raw] shortcode might help. I don’t have time right now to check but I just thought I’d throw it out there.