Disable Fields

Well that should be possible. We’ll need @siamkreative for that.

Thanks for the reply Julien.

Look forward to the solution – that’s the only piece of the puzzle remaining for me to get my site ready.

Could you target the field like this?

Edit: I’ve only just noticed the comment “if you work with a form , the disabled fields does not submit , so use a hidden field to store disabled dropdown value”. So I supposed that’s what’s causing the complication …and I can’t help with that so I’ll shut up ??

Edit 2: Could you not create a secondary custom field, then pre-populate it as part of your url variables? Then hide it with CSS.

Hi pipdig

Yes, I could. That’s relatively easy but I’ve got a few forms I’m using to submit different requests. It’s the way I’ve structured my site, to differentiate the different requests I’m looking to receive.

I would then need to be able to (somewhere on the page) list the type of request that is being submitted – like a label. In my head – it’s just so much easier but for some reason, I can’t seem to get the label added into the right place. It always appears at the top of the screen above the header.

I’ve tried different techniques and ultimately decided to just go with disabling the field – preventing users from changing it.

Because I’m using url parameters, I am displaying additional fields for different request/product types – does that make sense?

Hi anisjolly,

I’ve only just started using Awesome Support today, so I’m still setting up our site and I am by no means an expert. However, it sounds like we have almost identical requirements, so maybe the code I’ve made so far today could help ??

I haven’t fully tested this yet (Julien might point out some mistakes/issues) but this is an example function that makes up my ticket flow/form – https://pastebin.com/JupUMfH3.

It adds the CSS/jquery to the head when on the ticket submit page. Then checks if my special query argument is there: “?pipform=1”. I’ve stripped the code down just for this example, but in my actual site I’m planning to set different layouts/products based on this query argument. i.e. pipform=2, pipform=3 etc etc will turn the form into different things.

So the form has all custom fields present in the markup, but they are changed via jquery and css depending on how the user got to the page. I’m creating different entry points with the url queries and pre-fill variables etc.

Not sure if that helps, but thought I might as well post in case it does.

Incidentally, if you’ve approached this from a different angle I’d love to hear your thoughts.

Hi pipdig

Thanks for this. I’ll give this a shot later this evening. I’ll report back!