I have made an upgrade to the latest version, to see if the problem with the textarea truncation of text still exist.
After the upgrade, I am unable to see the form entries in the backend. They are simply blank
The wp_rg_lead_details_long table has been truncated during the upgrade.
What do I do about that?
Neither 1.4.3 or 1.4.5 had truncation issues. If you had issues with the textarea being truncated then it was another plugin causing a conflict, which we have seen (a plugin called Newsletter plugin causes this issue because it is poorly coded). That being said, it sounds like something is wrong with your site in general, possibly another plugin causing issues. Upgrading from 1.4.3 to 1.4.5 should not blank out your entries. It sounds like your database tables have been corrupted.
@hgr All I can say is it interferes with the Gravity Forms admin. I haven't dug any deeper than that. It's the only plugin we have encountered that causes the truncation issue, so it is doing something with data manipulation in WordPress that it should not be doing.
Can someone please post a link to the Newsletter plugin? I'm curious what it's doing wrong. Thanks.
@illinoisharley It's actually a commercial plugin. You can find it here:
http://tribulant.com/plugins/view/1/wordpress-newsletter-plugin
We haven't had time to do more investigation on this. We've only encountered 2 users who are using it who ran into an issue.
I just upgraded from 1.4.5 to 1.5 RC2.2 and my forms don't show up in the editor, nor can I create a new form. The forms function on the front end. I don't use the newsletter plug-in. Everything WAS working with 1.4.5.
Update: I should mention I disabled EVERY other plug-in and this still occurs. Theme is Genesis
Nope, there is no special procedure and no issues have been reported upgrading from 1.4.5 to 1.5. So this is going to be something specific with your site. In order to debug this you would have to install and activate Gravity Forms v1.5 and then send us a WordPress admin login for this site via our Contact Us form so we can take a look and do some debugging.
There's not special procedure for upgrading. Most likely, the upgrade process didn't complete properly. WordPress drops the ball occasionally on upgrades.
I would try deleting the current plugin files, then uploading the new version via ftp and see if that works for you.
I just discovered this may be a browser issue (Chrome 10.0.612.1). Working in Safari 5.0.3 and FireFox 4.0b7.
Chrome (dev releases) just updated itself this morning, I may roll it back to 9 and see how it goes.
Confirmed on two separate machines running Chrome 10.0.612.1
The new form actually flashes on screen for a milisecond before it disappears. I'm guessing a JS bug (which I'm not able to debug) and it probably Chrome's fault)
I use Chrome as my primary browser and haven't encountered this issue.
Something else is going on. If you send us a WordPress admin login for this site via our Contact Us form we can debug and see what the issue is.
in case it helps anyone else... i'm also seeing this on 2 different websites... when working in Chrome 9.0.597.19 the new form/edit form show a blank form screen for GF 1.5 RC2.2 and Beta 3.
FF 3.6.13 is not having any problems with either release.
@biscuitstudios Chrome 9 is a beta release and not a public release. Try testing in the latest public release of Chrome 8 and see if you still encounter the issue. I'll do the same. Also let me know if this is Windows or MAC.
Carl, just tested Chrome 8.0.552.224 on Windows and GF 1.5 RC2.2 works great.
tested Chrome 9.0.597.19 on a MAC and it shows the blank edit form pages... not too concerned about it since the Chrome version is beta... was just posting a confirmation that the Chrome beta was indeed showing blank form edit pages in case someone else was having the same issue.
just a little side note in case it matters (i know this should probably be a different forum topic)... my WP plugins list shows GF being RC2.1... i downloaded RC2.2 two hours ago and didn't install any other GF prior to RC2.2 this morning.
Yea, it appears to be a Chrome 9/Chrome 10 browser bug. We are going to look into why it's happening, no guarantees it's a code issue we can fix... could be an issue they fix in subsequent development builds of Chrome.
No worries about the version issue, I just noticed that the meta data for the latest Gravity Forms build does say RC2.1 when it's really RC2.2. We'll fix it, but no need to re-install the updated build.
Carl, i appreciate the feedback on both the Chrome bug and build update... as always, i'm really impressed with GF's quality and incredible support... not sure how i survived my WP form building years without it... thanks!
contrid
Member
Good day,
@Carl, I think you are mistaken by making a statement saying our plugin was "poorly coded". If you haven't investigated further it means that you probably haven't purchased a license of our plugin and that you haven't seen the code. It is the best MVC code you will possibly see. You may want to re-consider being judgemental about the code of other developers.
Guys, these conflicts happen. In most cases it is because of a plugin not using WordPress conventions but in other cases like this there is a combination of plugins causing the problem.
We purchased a license of the Gravity Forms plugin recently and have started to investigate, not being able to duplicate the issue but we are still trying and are communicating with the users having the issue to see if we can spot the problem.
And please don't remove this comment, based on your attitude on your first comment of this threat, the easiest seems like the best way out.
All the best,
Antonie Potgieter
@contrid Gravity Forms uses WordPress best practices and doesn't interfere with other plugins. We didn't investigate further because I am aware of the code involved and there isn't anything Gravity Forms is doing that can be changed to "correct" whatever the Newsletter plugin is doing.
We don't have time to debug every single plugin conflict when the issue is caused by the other plugin and not our own. We encounter so many poorly coded plugins that cause so many hours of support time on our end that ultimately was not a Gravity Forms issue that I automatically assume the other plugin is poorly coded when it's causing an issue.
The functionality in question is simply displaying data from a database. It isn't complex. It's a select query. The issue only occurs with the Newsletter plugin activated. There is nothing the Newsletter plugin should be doing that should interfere with one of Gravity Fors queries, but it does. So obviously something is going on within the Newsletter plugin that is interfering with Gravity Forms ability to query and display entry data.
contrid
Member
@Carl, I added you on Skype to discuss this further with you and get some information from you so that we can check the code on our side.
I added you yesterday but no response yet. Can you please accept my contact request or add me on Skype as: contrid . It will be great if we can talk about the code for a moment.
All the best,
Antonie
@contrid I'm currently traveling and don't have reliable access to Skype and no set time i'd be available if I did. The best way to get in touch with me right now is via email at carl@rocketgenius.com
