Made by healthcare.gov's fired workers

Howdy,

Thanks for the feedback! I’d like to do what I can to resolve the issues you are seeing.

If there is two radio forms, it won’t mark a default answer for the second one

I just tried to replicate that and when I have two sets of radios, I am able to set a default answer for each one just fine.

The radios stretch the entire screen

There’s very little I can do as a plugin author to control how a theme might display the survey on the frontend. I use Twenty Fourteen for all local testing and it displays fine there.

Instead of a custom css form off and on, display the css form so people can add custom CSS

And then I get to support that too. No thanks.

The thank you page should redirect them to a page of our choosing or at least to the homepage

https://gist.github.com/WillBrubaker/57157ee587a9d580ddef

I just tried to replicate that and when I have two sets of radios, I am able to set a default answer for each one just fine.

It works in the backend but not on the front end. I’ll install the plugin and attempt to replicate it again as an example.

The radios stretch the entire screen

This statement I made was vague and stupid. The radio itself doesn’t stretch across the screen, just the ability to select the answer. If I click in the white space on the other side of the radio, it’ll select the answer. This caused accidental answer changees

And then I get to support that too. No thanks.

But :[

If I click in the white space on the other side of the radio, it’ll select the answer. This caused accidental answer changees

I see your point now. It’s actually the click on the ‘label’ element that the radio button is wrapped in that triggers the change. I’m not going to set a width for the label, as I have no earthly idea how long of a string of text might end up in that label. I don’t keep up with W3C standards, but I’m fairly certain that whether or not the radio is wrapped in the label, clicking on the label will do the same thing as clicking on the radio provided the label’s for and the input’s id attribute are the same. There are a lot of good arguments in favor of that behavior not least of all accessibility and touch-devices. That said, I’m pretty reluctant to do anything to alter that behavior – don’t want some ADA issue to become part of my life because I removed an accessibility feature.

Anyone who knows enough about CSS to make an attempt at customization doesn’t need a place in my plugin’s configuration to add that. Either their theme has a place or they will are already including their own custom stylesheets, the moment I provide a place for it, I start to get CSS questions, which if it isn’t already obvious is not on my list of strengths.

I looked I messed with the radio for a while myself. I’ll continue to do so and see if I can find a solution. This site figured it out:

https://www.surveygizmo.com/s3/1254087/hostmonster

————–

For a regular text form, I set the maximum character to 5. If I insert 8 and submit it denies the form. I then try to submit 5 and it says there is a 3 character limit.

I tried to edit the form but you can’t change the character limit once it’s created. So I recreated it, made sure I put 5 – same problem.

————–

The loading icon when you submit the form on the front end…how do I remove/change that to something standard?

I missed this:

The survey shouldn’t require a title. My page displays a title on my screen. If it is going to have a title, put it in something other than <p> tags. At least give it an <h> tag or a div so we can remove/customize it with css

That’s a really good point. issue created

maximum character to 5

Looks like I’ve completely broken that – the results on the dev version are even worse. Issue created

Alright, this has been fun but I have other things to do. Any more issues you’d like to add I’ll probably keep better track from the github repo.

Haha of course! Thank you for your time on the plugin. One last thing, I figured out the radio situation:

Simple radio solution:

Simple radio solution:

Set up like this
<ul>
<li><label class="radio></label></li>
<li><label class="radio></label></li>
<li><label class="radio></label></li>
</ul>

Extra CSS:
.answer-survey label.radio{display:inline-block}

This will make only the radio an its label clickable.

Thanks you for your time on this, seriously.

How to reproduce:

Start with your browser width as small as it can go and slowly get larger. There is a time when the text won’t drop to the next line but will instead go off the screen.

Caused by
form.answer-survey{width:100%;padding:1em}

I wouldn’t bring it up but it is effecting mobile devices. (regardless of their width)

The padding part only adds to a themes default padding. This creates pages without similar padding.

More problems:

1. Text area forcing required

Not sure what is causing this. I have a 10 radio required attribute above a text area. Text area is not required, it is forcing it to be required.

If you can’t replicate this, let me know. I’ll try to pin it down further.

2. Validation/authentication (none) recording improperly

When I set Validation/authentication to none and go to ‘Survey results by users’ tab, it only shows my first submission, not the 3-4 that I did. On top of that, it only shows the answers for radios. It isn’t posting textbox or text area answers.

‘Your Results’ tab properly recording all answers from all submissions.

[ No bumping please. ]

Hey there,

on the “maximum character to 5” I broke that pretty badly on the dev version an wouldn’t have noticed if I hadn’t been looking into the issue for you so thanks – but it’s not broken and works as expected on version 1.5.1

These issues also:

Text area forcing required
Validation/authentication (none) recording improperly
If there is two radio forms, it won’t mark a default answer for the second one

are not reproducable see screencast

and a test on mobile while I’m at it

Perhaps your not recorded issue refers to the fact that the results are hosed up in results by user tab – that fix would have probably already been rolled out if I hadn’t been chasing these other non-issues.

Can I ask you to open any other support requests in the support forum rather than here under reviews?