There was a task to submit form with ajax, with server side validation of course. Obvious solution is to do validation and return json with erros.
I didn't like idea of writing separate view for validation and then inserting errors in form html on client side. Especially since I already had a generic template for django form with errors display.
Task
User will see process like this:
- User clicks 'edit' near article block
- article is replaced with form
- in case there are validation errors - they are shown above the form fields
- in case there are no errors - form is replaced by article html
Solution
Server will return piece of html that will replace part of page with article or form (with errors if needed). Actually this sentence is the most important part of this blog post. Implementation is very simple and straightforward.
Well actually the fact that you can return parts of html from server is also not new idea at all. It's just only now I finally understood that using this technique you can create more complicated things than modal window or tabs.
Implementation
views.py
def edit_new(request, new_id):
new = get_object_or_404(MyModel, pk=new_id)
if request.method == 'POST':
form = NewsForm(request.POST, instance=new)
if form.is_valid():
new = form.save()
return render_to_response('include/new.html', dict(new=new))
else:
form = NewsForm(instance=new)
return render_to_response('include/form.html', dict(form=form, new=new))form.html
This html will replace article block on 'edit' button click. Javascript should be moved to separate file of course.
<script type="text/javascript">
function submitAndLoad(input) {
$.ajax({
url: "{% url edit_new new.id %}",
data: $(input).parent().serialize(), // форма
type: "post",
dataType: "html",
success: function(data) {
$(input).parent().parent().html(data); // article block
}
});
return false;
};
</script>
<form>
{{ form }}
<input type="submit" value="Save" onclick="return submitAndLoad(this);"/>
</form>news_list.html
<script type="text/javascript">
function editNew(id) {
$("#new-" + id).load("{% url edit_new new.id %}");
return false;
}
</script>
<!-- ... -->
<div id="new-{{ new.id }}">
{% include "news/new.html" %}
</div>
<a onclick="return editNew({{ new.id }});" href="#">Edit</a>Code can be cleaned up of course, I just wanted to show the idea.
Update
I'm translating this article almost five years after it was originally written and of course now it seems very childish :) Now we have angular and ajax forms are implemented a little differently. Still this old solution is not all that bad. I'd still replace one thing here - it's better to return json with html from server instead of just html.
Subscribe for the news and updates
This article explores Figma’s Dev Mode, a tool that streamlines design-to-code translation by enabling precise inspection, automated code generation, and seamless integration with design systems.
This article demonstrates how to use Python to automate yield calculations in decentralized finance (DeFi), focusing on the Renzo and Pendle platforms. It guides readers through estimating potential rewards based on factors like token prices, liquidity, and reward distribution rules, emphasizing the importance of regular data updates and informed decision-making in DeFi investments.
Earlier in our previous article "Improve efficiency of your SELECT queries" we discussed ways to profile and optimize the performance of SELECT queries. However, to write complex yet efficient SQL queries, there is a thing to remember about.
We have reviewed the top web frameworks for server and client-side development and compared their pros and cons. Find out which one can be a great fit for your next project.
In this article I will describe how to integrate geolocation HTML5 function to a web app so you can then easily implement it in your apps or websites. As an example we are going to create small web app which will be able to calculate the shortest route between detected user’s location and predefined destination using Google Maps API.
In my current project I had a task to use twitter API. Twitter uses OAuth for authentication, which is pretty dreary. To avoid fiddling with it all the time, I've moved authentication to decorator. If key is available - nothing happens, just view is launched as usual. It's convenient that there's no need for additional twitter settings in user profile. Code is in article.