Error with GF v.1.9.1.2

  • Hi, I’m getting this error on forms that map post fields to a CPT:

    2/19/2015 5:59:50 AM - www: PHP Fatal error: Cannot use string offset as an array in /var/www/example.com/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddonbase.php on line 301

2/19/2015 5:58:49 AM - www: PHP Fatal error: Cannot use string offset as an array in /var/www/example.com/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddonbase.php on line 301

    This only began happening after upgrading to GF 1.9.1.x. Appreciate any insights on how to fix it please. Thanks

    https://www.ads-software.com/plugins/gravity-forms-custom-post-types/

Viewing 4 replies - 1 through 4 (of 4 total)

  • I am having the same error when trying to map tags to a custom taxonomy… Can’t load the form at all in the admin area now.

    Any suggestions?

    I am also having this issue.

    I’m having the same issue also

    Ditto.

    Here’s my specific error on one particular form: 

    Notice: Uninitialized string offset: 0 in /website/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddonbase.php on line 301

Fatal error: Cannot use string offset as an array in /website/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddonbase.php on line 301

    My forms won’t even show up, so I looked into that file and removed [0] as I understand this error points to trying to load arrays when one of them is just a string.

    Doing so “fixes” the problem, in that the forms will display, but the error changes to this on one particular form: 

    Notice: Undefined index: text in /website/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddonbase.php on line 301

Notice: Uninitialized string offset: 0 in /website/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddonbase.php on line 301

    And this on another form:

    Notice: Undefined index: text in /website/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddonbase.php on line 301

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error with GF v.1.9.1.2’ is closed to new replies.