PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

1.6.rc4 Bug Error in Selecting Columns in the Entries Backend Panel.

  1. No entries have been made, but this should not affect the selection of fields to be displayed should it? Here is a snapshot of the error pop up message:

    I also tested this across all current forms which worked on this feature with previous releases of GF. The above pop up error box occurs on all of them. Please advise, thank you.

    Posted 12 years ago on Sunday October 2, 2011 | Permalink
  2. This is a server related issue specific to changes made to this release to be compatible with WordPress installs where the wp-content folder may exist somewhere other than than the default location.

    We can't replicate this issue. If you send me a WordPress admin login and an FTP login for this site we can take a look and see what needs to be changed to make it work with your server configuration. You can email me this information to

    Posted 12 years ago on Monday October 3, 2011 | Permalink
  3. Email sent with logon credentials. So you're telling me I would have ran in to this anyways down the road, with your new release coming up?

    Posted 12 years ago on Tuesday October 4, 2011 | Permalink
  4. Yes, you would have run into this if you had not brought it up. It's not something most users are going to encounter. Our lead developer has the information and is going to take a look and see what we can do to prevent it from happening so that it is resolved in the next release.

    Posted 12 years ago on Tuesday October 4, 2011 | Permalink
  5. Check! I just created and tested a new ftp account for your GF Team and sent ftp credentials to Alex. Your root will be /public_html , where the WP install resides for the domain in question Carl. I'll keep it intact, should you require it in the future Carl. Thanks.

    Posted 12 years ago on Wednesday October 5, 2011 | Permalink
  6. Thanks Robert, this issue has been resolved. It was an issue involving changing made to handle different server setups. We have refined the code and it resolved the issue. This change will be in the next release and has already been applied to your site as you are aware.

    Posted 12 years ago on Wednesday October 5, 2011 | Permalink

This topic has been resolved and has been closed to new replies.