<p>The possible reason for no errors being shown is that you re-define your <code>entry</code> variable before displaying the errors. Make sure you have</p>

<pre><code>{% if entry is not defined %}
    {% set entry = craft.entries.id(craft.request.segment(4)).first() %}
{% endif %}
</code></pre>

<p>and not just</p>

<pre><code>{% set entry = craft.entries.id(craft.request.segment(4)).first() %}
</code></pre>

CC BY-SA 3.0
2017-02-16T13:36:53.787Z
2017-02-16T13:36:53.787Z
Yuri Salimovskiy
<p>I run into the same issue and I found out, that the problem was with one of the fields I have added into the Entry Type.</p>
<p>The field was not required, but it had set Min Relations to 1. Craft was testing the Min Relations on the save and since I was not using this field in the Entry Form at all, I didn't get the error message.</p>

CC BY-SA 4.0
2023-10-12T11:55:22.097Z
2023-10-12T11:55:22.097Z
Michal Bulla
<p>I've run into this situation in various scenarios as well where a front-end entry form fails to save anything and just seems to be reloading the page. Almost always it has had to do with overlooking a required field or some other small detail, as Douglas mentions in his comment.</p>

<p>If all of your fields are not required, make sure you are still setting fields like the <code>Title</code> field, which are necessary for your Entry to save properly.</p>

<p>One way to help troubleshoot is to take a look at all of the errors you are getting back. If you are just trying to output errors for the fields you are submitting you may be missing seeing an error for another field that is giving you an error but that you are not outputting.</p>

<p>When a front-end entry form fails to submit, Craft will add any errors to the <code>EntryModel</code> and return it to the page. If you have <code>devMode</code> enabled, you can dump all of the errors from your submission with the following line of code to help troubleshoot:</p>

<pre><code>&lt;pre&gt;{{ dump(entry.getErrors()) }}&lt;/pre&gt;
</code></pre>

CC BY-SA 3.0
2015-08-23T05:06:28.290Z
2015-08-23T05:06:28.290Z
Ben Parizek
<p>I am trying to make entries editable from the front end and pretty much follwed <a href="http://buildwithcraft.com/docs/templating/entry-form" rel="noreferrer">the docs</a>.</p>

<p>When i visit my edit view, the entry-from is filled with their respective values but unfortunately no changes are being saved back when i update those and submit. A redirect is also not happening. The old form just loads again.</p>

<p>Not errors too. The site is localized so could this be a problem? Should i add the locale to my inputs?</p>

CC BY-SA 3.0
2014-09-29T16:14:24.153Z
Your entry is likely failing due to a missing required field, incorrect formatting, or other not-critical error. Have a look at the answer [to this post](http://craftcms.stackexchange.com/questions/641/how-to-deal-with-client-input-your-site/2778#2778).
Douglas McDonald
CC BY-SA 3.0
2014-09-30T08:32:20.403Z
Thanks Douglas. Had a look into most of them. There are no required fields.

Interestingly enough, updating an entry now works, just like that. With the exception of assets. Assets for new entries are working fine but updating an existing asset results in the deletion but not updating to the new one. It doesn’t get uploaded either. However, the redirect works. Investigating.
Marcus Scheller
<entries><form>
Front end edit: entry doesn’t get saved
# Front end edit: entry doesn’t get saved

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

I am trying to make entries editable from the front end and pretty much follwed [the docs](http://buildwithcraft.com/docs/templating/entry-form).

When i visit my edit view, the entry-from is filled with their respective values but unfortunately no changes are being saved back when i update those and submit. A redirect is also not happening. The old form just loads again.

Not errors too. The site is localized so could this be a problem? Should i add the locale to my inputs?

**Tags:** entries, form

> **Comments:**
> **username_1**: Your entry is likely failing due to a missing required field, incorrect formatting, or other not-critical error. Have a look at the answer [to this post](http://craftcms.stackexchange.com/questions/641/how-to-deal-with-client-input-your-site/2778#2778).  
> **username_0**: Thanks Douglas. Had a look into most of them. There are no required fields.  Interestingly enough, updating an entry now works, just like that. With the exception of assets. Assets for new entries are working fine but updating an existing asset results in the deletion but not updating to the new one. It doesn’t get uploaded either. However, the redirect works. Investigating.  

---

## 3 answers

### Answer by username_4 on 2015-08-23. Score: 10 | Accepted answer

I've run into this situation in various scenarios as well where a front-end entry form fails to save anything and just seems to be reloading the page. Almost always it has had to do with overlooking a required field or some other small detail, as Douglas mentions in his comment.
If all of your fields are not required, make sure you are still setting fields like the Title field, which are necessary for your Entry to save properly.
One way to help troubleshoot is to take a look at all of the errors you are getting back. If you are just trying to output errors for the fields you are submitting you may be missing seeing an error for another field that is giving you an error but that you are not outputting.
When a front-end entry form fails to submit, Craft will add any errors to the EntryModel and return it to the page. If you have devMode enabled, you can dump all of the errors from your submission with the following line of code to help troubleshoot:
{{ dump(entry.getErrors()) }}


---

### Answer by username_2 on 2017-02-16. Score: 6

The possible reason for no errors being shown is that you re-define your entry variable before displaying the errors. Make sure you have
{% if entry is not defined %}
    {% set entry = craft.entries.id(craft.request.segment(4)).first() %}
{% endif %}

and not just
{% set entry = craft.entries.id(craft.request.segment(4)).first() %}


---

### Answer by username_3 on 2023-10-12. Score: 1

I run into the same issue and I found out, that the problem was with one of the fields I have added into the Entry Type.

The field was not required, but it had set Min Relations to 1. Craft was testing the Min Relations on the save and since I was not using this field in the Entry Form at all, I didn't get the error message.


---

