For some reason, this is occurring only when the form is submitted with errors while using AJAX. The disabled attribute is being stripped when the form is submitted. I’ll have to do some research to find out why this would happen. However, if you use the form without AJAX, the attribute will be preserved.
I too am experiencing this issue.
Did you find any resolution other than not using AJAX? Sometimes we must use ajax for other purposes.
Thanks,
Nicole
I have also tried it without ajax and then it messes with the actual validation of the fields that were at one time disabled.
Eg. I have checked a checkbox that was originally disabled using your plugin and which I had then I had enabled myself with jQuery when a condition was met. This checkbox is required and has now been checked. I then hit submit and that checkbox reverts to disabled and it gives me a validation error for that field even though it was actually checked and the form should have submitted.
Basically without AJAX it is forcing the disabled property even on submit so there is not ability for me to remove the disabled property at all and hence the field is actually useless.
Any ideas or resolution to the original issue?
Without AJAX enabled it works perfectly – so thank you for this plugin.
However, with AJAX enabled I am having the problem as nicole2292 is above.
Would you be able to make the plugin work with AJAX? This would be greatly appreciated.
Cheers
Next time I update the plugin, I’ll include something to prevent the attributes from being stripped when using AJAX.
@nicole2292: Based on what you’re describing with the validation issue, it sounds like you should be using the readonly attribute, not the disabled.
Sounds great, thank you! 😉
Cheers
