I would like to create a second form on my ExpressionEngine 2.5.2 site using Freeform. We have been using the Freeform module for about a year and a half, but I have recently been experiencing 2 different problems. I'm not sure if the issues are related or not:

Problem 1 - Disallowed Characters

When I go in to my ExpressionEngine control panel and try to add information to a blank field of an entry, when submitting the change, I always receive a message that says "Disallowed Key Characters." Nothing is wrong with the fields I am entering the data into, and there are no unusual characters in the data that I'm entering.

I am able to enter data into a form when pulling up an old form page on our site in my browser [not in my ExpressionEngine control panel].

Problem 2 - Unauthorized Action on New Forms

I created a simple new form where I am only entering a first name and a last name, then clicking submit. On the webpage in a browser, when I fill those two fields then click submit, I get taken to a new page that says "You are not authorized to perform this action". This doesn't make any sense to me and I'm out of troubleshooting ideas.

Here is the very simple form I am using in my html page, and I have created each of the fields in the Freeform module within EE that are listed in my code -

<form class="application-form" action="#">
    {exp:freeform:form collection="Entry Form" return="home/index"}         
        <div class="heading">
            <h2>APPLY TO COMPETE</h2>
        <div class="row">
            <div class="col">
                <label for="first_name">First Name</label>
                <input type="text" dir="ltr" id="first_name" name="first_name" value="" />
            <div class="col">
                <label for="last_name">Last Name</label>
                <input type="text" dir="ltr" id="last_name" name="last_name" value="" />
        <div class="row">
            <input type="submit" value="submit" />
  • I put my comment in an answer below.
    – GDmac
    Feb 22, 2013 at 8:07

1 Answer 1

  1. is usually disallowed character in the url. e.g. in a get parameter, or in a form input name.
  2. i don't think you should add the <form> tag yourself, it will be set by freeform, no?
  • just found it - i was using 'google+' as one of the field names and the '+' was disallowed. I also removed <form> because it was redundant. Never quite discovered what was going on with the 'Unauthorized Action on New Forms'. But I'm sure that cleaning up those two things contributed to the fix. Thanks! Mar 5, 2013 at 18:15
  • I had a typo as name="{freeform_field_name}" on my input, so it wasn't being parsed ({ and } were disallowed). Updated it to name="{freeform:field_name}" (colon, not underscore) and that fixed it. Sep 9, 2016 at 19:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.