William Rettmann

The following link has a better general explanation of the issue and the math involved as it relates to utf8mb4 and WordPress Core.

https://make.www.ads-software.com/core/2015/04/02/the-utf8mb4-upgrade/

I also experienced this problem. Based on my findings, it depends on what encoding you are using in your database. If you are using some form of UTF8, then each character appears to be 4 bytes.

To resolve this for version 2.9.0, I changed the code in wplogin_redirect.php on line 1514 to the following (had to remove original backticks for comment):

UNIQUE KEY rul_type (rul_type,rul_value(180))

This only uses 180 of 255 characters for the rul_value column, and allowed me to install the plugin.

Once the plugin is installed with this change made, updates should continue to work as normal since the tables will not need to be recreated. I am not sure what, if any, other effects this may have on plugin functionality, though.

I also experienced this issue. The problem seems to be with the ver= query string that is added to the end of the jQuery Tools script, which causes a 404 error, and therefore causes things to break.

Besides this error, there seems to be a conflict with the version of jQuery and the version of jQuery Tools being used.

To fix this, in the plugin file /php_includes/housekeeping.php at line 311, change:

wp_enqueue_script('jquery-tooltip', 'https://cdn.jquerytools.org/1.2.5/jquery.tools.min.js', array('jquery'));

TO:

wp_enqueue_script('jquery-tooltip', 'https://cdn.jquerytools.org/1.2.7/full/jquery.tools.min.js', array('jquery'), null);

Notice the version change (1.2.5 to 1.2.7) as well as the added null to the wp_enqueue_script function to prevent WordPress from adding the version query string value.

I read & responded to the post on the Gravity Forms support site using the links provided above. At the time of my post, the OP merely stated the conflict between the jQuery version in WP 3.5 and the curCSS method. The GF developers replied that they were not able to reproduce the error.

I responded with the information that the AMTPV plugin causes a conflict, and disabling it resolves the issue. However, since disabling this plugin resolves the problem, but the error is in a GF script, I’m just passing along the info so both sides can investigate.

I fixed this problem by typecasting the array in the foreach statement. You can do this by placing (array) in front of the variable on the lines mentioned in the error.

foreach (<strong>(array)</strong>$groups as $group_id => $group) {
...
}