CiviCRM Community Forums (archive)

I think this problem is occurring purely because a lot of text is being pasted in to fields that are used for an Activity.

I get "There is a validation error with your HTML input. Your activity is a bit suspicious, hence aborting"

But there is no HTML involved. Just lots of text being added to a bunch of NOTE fields.

After adding and saving a few fields, when I add some more text to other fields I get the above.

Debugging/backtrace doesn't spit out anything obviously helpful to me yet

/sites/fuzion7/sites/www.outdoorsnz.org.nz/modules/civicrm/CRM/Core/Error.php, backtrace, 296
/sites/fuzion7/sites/www.outdoorsnz.org.nz/modules/civicrm/CRM/Core/IDS.php, fatal, 231
/sites/fuzion7/sites/www.outdoorsnz.org.nz/modules/civicrm/CRM/Core/IDS.php, kick, 165
/sites/fuzion7/sites/www.outdoorsnz.org.nz/modules/civicrm/CRM/Core/IDS.php, react, 144
/sites/fuzion7/sites/www.outdoorsnz.org.nz/modules/civicrm/CRM/Core/Invoke.php, check, 88
/sites/fuzion7/sites/www.outdoorsnz.org.nz/modules/civicrm/drupal/civicrm.module, invoke, 447
, civicrm_invoke,
/sites/fuzion7/includes/menu.inc, call_user_func_array, 503
/sites/fuzion7/index.php, menu_execute_active_handler, 21
On dev site I have turned off IDS and succeeded in saving the Activity fine.

Not keen to have to leave IDS off.

Is this something to do with the sheer size of the POST request hitting a maximum number of characters for the form?

so trying to replicate on demo with Activity with lots of fields and lots of text and getting different error - unrelated?
Database Error Code: Got error 139 from storage engine, 1030
Additional Details:
Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => a515ac9c2796ca0e23adbe92c68fc9fc
    [message] => DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
    [mode] => 16
    [debug_info] => UPDATE civicrm_value_fuzion_activity_test_4  SET fuzion1_7 = 'Lorem ipsum dolor sit amet,snip
[type] => DB_Error
    [user_info] => UPDATE civicrm_value_fuzion_activity_test_4  SET fuzion1_7 = 'Lorem
SNIP
r\n',radio1_15 = 1,radio2_16 = 1,radio3_17 = 1,radio4_18 = 1,radio5_19 = 1,radio6_20 = 1,radio7_21 = 1,radio8_22 = 1,fuzion9_23 = 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum
SNIP
 vitae, justo. Nullam dictum felis eu pede mollis pretium. Integer tincidunt. Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifem nulla eros, ultricies sit amet, nonummy id, imperdiet feugiat, pede. Sed lectus. Donec mollis hendrerit risus. Phasellus nec sem in justo pellen. Maecenas vestibulum mollis\r\n',fuzion10_24 = 'Lorem
SNIP
  WHERE  id = 1 [nativecode=1030 ** Got error 139 from storage engine]"]
)

The error 139 appears to be due to us running up into mysql limit: we're exceeding the maximum row limit.

To quote two sources from mysql:

The maximum row length, except for variable-length columns (VARBINARY, VARCHAR, BLOB and TEXT), is slightly less than half of a database page. That is, the maximum row length is about 8000 bytes. LONGBLOB and LONGTEXT columns must be less than 4GB, and the total row length, including BLOB and TEXT columns, must be less than 4GB. (http://dev.mysql.com/doc/refman/5.0/en/innodb-restrictions.html)

And:

The maximum row length, except BLOB and TEXT columns, is slightly less than half of a
database page, that is, the maximum row length is about 8000 bytes. LONGBLOB and LONGTEXT
columns are allowed to be < 4 GB, and the total row length, including also BLOB and TEXT
columns, must be < 4 GB. Of a BLOB and TEXT column InnoDB stores the first 512 bytes in
the row, and the rest to separate pages. (http://bugs.mysql.com/bug.php?id=1611)

This suggests that if we were to have just 15 (or 16) text fields (let alone other fields), each which had at least 512bytes of data in, we'd exceed the maximum mysql row size. This is because, even though text fields are stored out of the database row, the first 512 bytes are stored in the row (presumably for indexing).  Given that this activity has 150 fields, it seems we'll easily come up against this limit.

Have other people come up against this limit? Should this limit of fields be made clearer in the documentation?