• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

mysql truncating fields?

michaellunsford

Regular Pleskian
I have a WYSIWYG HTML editor that allows users to edit their little page online. they edit the page and it's happy. it looks good. and it stays for a day or two.

but then, without warning, you go to their page one day, and the page's content has been truncated. I have had to pull database backups to fix this in the past, but I really want to know what is causing it?

typically the page is not edited anywhere, it just gets cut. Here's the table description:

keyfield int(11) PRI NULL auto_increment
page varchar(64)
content text

the part that's being truncated is the "content" field. The one that was truncated is 7,840 in length after being truncated, but probably no longer than 10,000 before. The longest `content` record is 65,542 in length (is there a limit? 65,536 or something?)

I have just yum updated mysql to 4.1.20 from 4.1.18 (in the hopes that mysql may have fixed something that caused this?)

Is plesk's cron scanning or messing with mysql at all? Could this be the root cause? Also, Is there a mysql log that can tell me when a database has been modified, scanned, or otherwise touched and by what login?
 
Back
Top