Hi,
I'm redirecting and trying to capture a checkbox group. I'm setting the capture as:
&plan={Admob setup $27.50 AUD :11.7}
But the query string is passing ...&plan=Array
Please advise.
Thanks.
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.
Checkboxes passing "Array"
-
mobisenz
Memberentry export of the checkbox group:
"Entry plan (up to 20 pages) $324.50 AUD ","Map powertool (free) $0.00 AUD ","Contact powertool (free) $0.00 AUD ","Search powertool $55.00 AUD ","News powertool $27.50 AUD ",".mobi domain $55.00 AUD ","Admob setup $27.50 AUD "
Posted 14 years ago on Wednesday September 15, 2010 | Permalink -
This is a bug in 1.4 and will be fixed in an upcoming release. If you contact us via our Contact Us form and request the current development build we can send it over so you can fix this now. We will also be making it available on the Downloads page later today.
Posted 14 years ago on Wednesday September 15, 2010 | Permalink -
Morten Knudsen
MemberIf you have priority support, check in a request for the 1.4.1 (beta) version - I have received one and that resolved the ARRAY issue.
But I can't understand why 1.4.1 officially is not released, this must be a bug that many people are having and they knew about it at least since friday last week- and why gravityforms.com does not have a "Known Bugs" area in the forum/FAQ somewhere I really don't understand:-(
Well, the plugin is top-notch - and support is rather good normally, so not everything is bad, I really do like this pluin and the people behind it :-)
EDIT: just saw that Carl did infact immidiately tell you that option - to contact them and have a development version mailed.....so I don't understand why you didn't accept that ?
Posted 14 years ago on Friday September 17, 2010 | Permalink -
mobisenz
MemberBecause I am not going to waste more time, and I had already implemented a workaround.
Also I do not think it is wise to put not production ready code into production. If it was ready it would have been released.
Thirdly, this really is an unacceptable bug to have to endure from a paid up version of a tool that was supposed to save me time when in fact I ended up spending hours on a workaround. And the impression I got from you was that I should pay for a support license to get prompt attention. But this was your problem, not mine.
The software failed me, I purchased something that did not work, you need to accept that fact, and not shrug it off. It appears this bug has been known for a while. Why has it not been patched into the stable release?
If you're willing to take money for a product then you should be willing to accept criticism.
And if you suggest for a second that I should have paid for the support license, then you need to get off the drugs. I did not need support, I know how to use the product, but it failed to do its job.
It is a good product, but it could be better. And in one particular way it failed me completely. That is a fact.
Posted 14 years ago on Friday September 17, 2010 | Permalink -
@mobisenz, if you didn't notice, @solsikkehaven is just another member on the forum, not an admin or one of the plugin developers.
It looks like from your rant that you're confusing his comments with some sort of statement from the development team and that's not the case. Still, the fact is that Carl offered you the development version with the fix right away. If you chose not to use it, that's totally your decision.
In regards to support, we try to answer all of the requests on the forum as promptly as possible, usually within just a few hours. Priority support is reserved for the developer license holders - that just means they get pushed to the top of the support list, not that other support doesn't get taken care of as quickly as possible.
Posted 14 years ago on Friday September 17, 2010 | Permalink -
Because I am not going to waste more time, and I had already implemented a workaround.
If you had simply waited a few hours you could have simply received the 1.4.1 development release and patched the problem. You were the one that took the initiative to fix it yourself despite the fact a fix already exists and would have been supplied to you.
Judging by your code you are in Australia and we are in the United States so you need to be a little more patient with your response time expectations given the time difference between us.
Also I do not think it is wise to put not production ready code into production. If it was ready it would have been released.
All software has bugs. It's a fact of life and anyone that tells you otherwise wrong. The code was production ready, it contained a bug with the checkbox field that didn't come up during the weeks of beta testing by hundreds of users. I apologize that this bug impacted you but we immediately offered you a fix.
Thirdly, this really is an unacceptable bug to have to endure from a paid up version of a tool that was supposed to save me time when in fact I ended up spending hours on a workaround. And the impression I got from you was that I should pay for a support license to get prompt attention. But this was your problem, not mine.
You are the one that took the initiative to implement your own workaround rather than waiting on our response which included a fix for the issue. Support is provided to all users and I responded promptly to your request with a fix.
Was it our problem? Yes. Did we offer a solution in a prompt manner? Yes.
The software failed me, I purchased something that did not work, you need to accept that fact, and not shrug it off. It appears this bug has been known for a while. Why has it not been patched into the stable release?
You purchased something that had a bug that we offered a fix for in a prompt fashion. Why hasn't this been patched in the production release? Because we are making sure there is nothing else that needs to be added or tweaked before releasing. We prefer not to release single fix releases as people get annoyed by upgrades as it is.
We offer single fix patches on an as needed basis until we have a few items to release via automatic upgrade so we don't annoy users with updating too frequently. Or until it appears there is nothing else to include, at which time we will release it via automatic upgrade.
It is a good product, but it could be better. And in one particular way it failed me completely. That is a fact.
If our software failed you and our support is so horrible we would be glad to offer you a refund and you can use CForms or Contact Form 7 instead.
Posted 14 years ago on Friday September 17, 2010 | Permalink -
Morten Knudsen
Memberwell, my comments about the 1.4 patch (I call it 1.4.1 because that's what Carl mailed me, I know it's 1.4 + patch to fix ARRAY issue):
1) That you can just contact the developers and have the patch send is a HUGE advantage, in stead of a development team that just says "you gotta wait till next release". I thought and still think that was great that Carl did that (for me, and for you if you had just put in a request to Carl and the Gravity team).....
2) I still think there should be a menu on the gravityhelp.com site where all known bugs are listed - not just for us, the customers, but it should also releave the support a little bit, because they don't have to answer to the same bug reports over and over again. So it would be a win-win situation to have such info on the website.
I won't be involved in this forum thread anymore, because I really don't won't to get into some sort of heated debate about Mobisenz's issues with gravityforms. Especially after the "get of the drugs" remark, it seems not to be worth the trouble.
btw: I like drugs, especially the kind called "love". Let's spread some love instead, also to you, Mobisenz.
Posted 14 years ago on Friday September 17, 2010 | Permalink
This topic has been resolved and has been closed to new replies.