So there have been two occasions I’ve run into this error on a page – and it’s very ambiguous and hard to track down both times I’ve experienced it. Fortunately, both times have also involved a very easy solution once I looked through the page for the 40th time. The first time I encountered this, the previous form designer had named both cfforms on the page the same thing. While this worked, it’s never advisable. By doing this, the cfcalendar script could not locate the item because it couldn’t track down the form properly.
The second time I ran into this – just a few moments ago – was the same problem surfacing because the declaration for the form had been placed inside the declaration for the table.
1 2 3 | <table>
<form></form>
</table> |
This just did not sit well with the browser, being invalid and all. Once I moved them outside of that formation and made it this:
1 2 3 | <form>
<table></table>
</form> |
it worked like a champ. Hopefully this helps someone out there with this error in the future!
Thank you so much! I was having this issue for hours and couldn’t figure it out why. People like you make our job easier
You are a hero, you just saved my life
Thanks for the tip
you rock!
Hey man… you are great… you saved several hours of mine to find about this issue.
Thank you! Thank you! Thank you! Great solution…it works!
Thanks for the tip! One Google search took me right to your page and I was back in business.
Thank you! Very helpful
Another subtle way this error can occur is if you inadvertently name two datefields the same. For example, if you have have a FROM date and a TO date in a date range search and you do what I did and simply copy and paste the date fields and forget to rename the second one.
Great!
Thanks for the fix. Totally saved me hours of recoding!
Thanks! Saved my day