Plugin version 3.6.3 – Data from a single field not displaying in directory

I have the same problem, but it is a radio button field. The data is not being displayed. I am on 3.7.1.

– Scott

I should clarify, the data from my other fields is displaying. There is just one field that is not displaying. The header for that field displays, but the content of that field is all empty.

– Scott

FYI, I reverted all the way back to 3.6.2 and now the missing data is being displayed.

Surprised that this problem was identified months ago on a previous version, but still is not fixed.

– Scott

I also have this problem. If I include a radio button field in a directory, the heading shows, but no data for that field.

If it used to work, can you please update the latest version of the plugin to fix it or provide some code that I can put in to fix it?

I really need this to work asap.

Yes, it’s a real mess, and extremely disappointing that this author does not care about their plug-in. I would consider purchasing the pay-for version if they showed some support here, but it seems they do not care about bugs.

I had to roll back to 3.6.2 to get it to work, but it introduced a whole pile of errors on the Gravity Forms admin screens (very annoying, but seems to not break anything)

– Scott

Never was able to get this fixed, so I reluctantly opted for the paid version. I must say, I’m glad I did – much more stable than this free plugin, and their support staff is on point. I was able to build out the directory exactly as I’d wanted, complete with a Gravity Form to act as a search form for it. Very happy with the purchase after so much frustration with this free version

Unfortunately, the site I’m using this on is a non-profit with a very limited budget. Sad that this bug still hasn’t been addressed.

I had the same issue where for questions that had multiple responses… each response would appear in the table as it’s own column… as opposed to 1 column containing all of the responses. However as Sneader suggested, rolling back to version 3.6.2 appeared to resolve the issue. WAKap… with all of the references from the developer within the plugin itself and on his website, it appears he may have resolve this issue intentionally in the paid version…. which leads me to believe he will not fix the feature in the free plugin, hoping users will purchase gravityview.

“…which leads me to believe he will not fix the feature in the free plugin, hoping users will purchase gravityview.”

Which is why I would not buy the plug-in. The “freemium” model works, when you have a solid free version with limited features, and a solid paid-for version with premium features. A solid free version with happy users is the best advertising a developer could ever ask for. If a developer cares this little for the free version, I would expect it’s only a matter of time before the developer craps on his paid customers.

Well, look what I just stumbled upon.. could it be the developer had a change of heart..? Free Gravityview? https://wptavern.com/gravityview-is-now-public-on-github

Just because it is on Github doesn’t mean the paid-for version is now easily used for free. The last comment on the above links spells it out more:

“If GravityView is open to public then it should be in www.ads-software.com NOT Github. It cannot be used in live site. If we need to test this plugin, we need to download and install Git submodules. I just omit this kind of stuff.”