<p>You won't need the <code>enctype="multipart/form-data"</code> part of the form, since you don't appear to be uploading any files when saving the user.</p>

<p>Other than that, I'd guess that maybe you've got an Asset field on your User's field layout that set to required and you're not taking that into account on the front-end?j</p>

CC BY-SA 3.0
2014-09-05T02:22:49.667Z
Brad thank you for prompt reply, my user field layout is empty no required fields there.Not really sure what is causing this error. If I find out I will post here.
Silvanus Matiku
CC BY-SA 3.0
2014-09-05T02:24:43.243Z
Can you enabled devMode (http://buildwithcraft.com/docs/config-settings#devMode) and post the full stack trace when the "Craft\WebApp.assetUpload" error occurs?
Brad Bell
CC BY-SA 3.0
2014-09-05T03:58:36.710Z
Hi Brad, I have found that when "Upload assets on the front-end 2.0" plugin by Bob Olde Hampsink is enabled...the error appears. I have disabled it since am not using it and now everything is working as expected!
Silvanus Matiku
CC BY-SA 3.0
2014-09-05T04:16:51.147Z
That plugin was written before front-end asset uploading was possible. Entirely not necessary now.
Brad Bell
CC BY-SA 3.0
2014-09-05T02:11:01.823Z
2014-09-05T02:11:01.823Z
Brad Bell
<p>I came across error Property "Craft\WebApp.assetUpload" is not defined, when registering users from front end. Is this a bug or missing config param?</p>

<p>I have used the example on craft website:
<a href="https://craftcms.com/docs/templating/user-registration-form" rel="nofollow noreferrer">https://craftcms.com/docs/templating/user-registration-form</a></p>

<p>The Actual template used is:</p>

<pre><code>&lt;h1&gt;Membership Registration&lt;/h1&gt;

&lt;form method="post" action="" enctype="multipart/form-data" accept-charset="UTF-8"&gt;

    &lt;input type="hidden" name="action" value="users/saveUser"&gt;
    &lt;input type="hidden" name="redirect" value=""&gt;

    {% macro errorList(errors) %}
        {% if errors %}
            &lt;ul class="errors"&gt;
                {% for error in errors %}
                    &lt;li&gt;{{ error }}&lt;/li&gt;
                {% endfor %}
            &lt;/ul&gt;
        {% endif %}
    {% endmacro %}

    {% from _self import errorList %}

    &lt;h3&gt;&lt;label for="username"&gt;Username&lt;/label&gt;&lt;/h3&gt;
    &lt;input id="username" type="text" name="username"
    {%- if account is defined %} value="{{ account.username }}"{% endif -%}&gt;

    {% if account is defined %}
        {{ errorList(account.getErrors('username')) }}
    {% endif %}

    &lt;h3&gt;&lt;label for="email"&gt;Email&lt;/label&gt;&lt;/h3&gt;
    &lt;input id="email" type="text" name="email"
        {%- if account is defined %} value="{{ account.email }}"{% endif %}&gt;

    {% if account is defined %}
        {{ errorList(account.getErrors('email')) }}
    {% endif %}

    &lt;h3&gt;&lt;label for="password"&gt;Password&lt;/label&gt;&lt;/h3&gt;
    &lt;input id="password" type="password" name="password"&gt;

    {% if account is defined %}
        {{ errorList(account.getErrors('password')) }}
    {% endif %}

    &lt;input type="submit" value="Register"&gt;
&lt;/form&gt;
</code></pre>

<p>Cheers,
Sil</p>

CC BY-SA 3.0
2014-09-05T00:57:19.947Z
Can you share the full template code you're using, Sil?
Brad Bell
<error-templates>
Property "Craft\WebApp.assetUpload" is not defined
# Property "Craft\WebApp.assetUpload" is not defined

(Asked by: username_0 on 2014-09-05)

I came across error Property "Craft\WebApp.assetUpload" is not defined, when registering users from front end. Is this a bug or missing config param?
I have used the example on craft website:
https://craftcms.com/docs/templating/user-registration-form
The Actual template used is:
Membership Registration



    
    

    {% macro errorList(errors) %}
        {% if errors %}
            
                {% for error in errors %}
                    {{ error }}
                {% endfor %}
            
        {% endif %}
    {% endmacro %}

    {% from _self import errorList %}

    Username
    

    {% if account is defined %}
        {{ errorList(account.getErrors('username')) }}
    {% endif %}

    Email
    

    {% if account is defined %}
        {{ errorList(account.getErrors('email')) }}
    {% endif %}

    Password
    

    {% if account is defined %}
        {{ errorList(account.getErrors('password')) }}
    {% endif %}

    


Cheers,
Sil

**Tags:** error-templates
> **Comments:**
> **username_1**: Can you share the full template code you're using, Sil?  

---

## 1 answers

### Answer by username_1 on 2014-09-05. Score: 1 | Accepted answer

You won't need the `enctype="multipart/form-data"` part of the form, since you don't appear to be uploading any files when saving the user.

Other than that, I'd guess that maybe you've got an Asset field on your User's field layout that set to required and you're not taking that into account on the front-end?j

> **Comments:**
> **username_0**: Brad thank you for prompt reply, my user field layout is empty no required fields there.Not really sure what is causing this error. If I find out I will post here.  
> **username_1**: Can you enabled devMode (http://buildwithcraft.com/docs/config-settings#devMode) and post the full stack trace when the "Craft\WebApp.assetUpload" error occurs?  
> **username_0**: Hi Brad, I have found that when "Upload assets on the front-end 2.0" plugin by Bob Olde Hampsink is enabled...the error appears. I have disabled it since am not using it and now everything is working as expected!  
> **username_1**: That plugin was written before front-end asset uploading was possible. Entirely not necessary now.  

---

