I suspect this has something to do with CSS. Here's my blog.css file:
body {
padding-left: 15px;
}
.page-header {
background-color: #C25100;
margin-top: 0;
padding: 20px 20px 20px 40px;
}
.page-header h1, .page-header h1 a, .page-header h1 a:visited, .page-header h1 a:active {
color: #ffffff;
font-size: 36pt;
text-decoration: none;
}
.content {
margin-left: 40px;
}
h1, h2, h3, h4 {
font-family: 'Lobster', cursive;
}
.date {
color: #000000;
}
.save {
float: right;
}
.post-form textarea, .post-form input {
width: 100%;
}
.top-menu, .top-menu:hover, .top-menu:visited, {
color: #ffffff;
float: right;
font-size: 26pt;
margin-right: 20px;
}
.post {
margin-bottom: 70px;
}
.post h2 a, .post h2 a:visited {
color: #000000;
}
this is my base.html file
{% load static %}
<html>
<head>
<title>Sinks Canyon Avalanche Center</title>
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css">
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap-theme.min.css">
<link href="//fonts.googleapis.com/css?family=Lobster&subset=latin,latin-ext" rel="stylesheet" type="text/css">
<link rel="stylesheet" href="{% static 'css/blog.css' %}">
</head>
<body>
<div class="page-header">
{% if user.is_authenticated %}
<a href="{% url 'post_new' %}" class="top-menu"><span class="glyphicon glyphicon-plus"></span></a>
{% endif %}
<h1><a href="/">Sinks Canyon Avalanche Center</a></h1>
</div>
<div class="content-container">
<div class="row">
<div class="col-md-8">
{% block content %}
{% endblock %}
</div>
</div>
</div>
</body>
</html>
and my post_detail.html file:
{% extends 'blog/base.html' %}
{% block content %}
<div class="post">
{% if post.publlished_date %}
<div class="date">
{{ post.published_date }}
</div>
{% endif %}
{% if user.is_authenticated %}
<a href="{% url 'post_edit' pk=post.pk %}" class="btn btn-default"><span class="glyphicon glyphicon pencil"></span></a>
{% endif %}
<h2>{{ post.title }}</h2>
<p>{{ post.text|linebreaksbr }}</p>
</div>
{% endblock %}
ice_bear69 Is this tutorial good?
ice_bear69 Its description says, "Django 3.0 crash course tutorials. Building a customer management app from start to finish covering all the basics of the django framework."
ice_bear69 But some of the first videos were released before December 2, 2019
$ workon <your-pythonanywhere-domain>.pythonanywhere.com
(ola.pythonanywhere.com)$ python manage.py collectstatic
[...]
ice_bear69 I think I get the basics
I have a new doubt. Any hints are appreciated. So I have a bunch of buttons(called as topics) and a drop-down. I want to basically map them to blog posts. For example:- if I click on a button that says "Horror" and then click on the week dropdown and select "Week 1", it should show only blog posts that have Horror and Week 1 mapped to it(this I already did and can be selected in the admin).
Any idea on how to approach this? I tried to Google before asking here obviously but can't find a specific answer to it.
@abhishekkoothur_twitter So if I understand you correctly, you essentially want to create a search view. First you have to create a url path that's something like posts/<str:catname>/<int:weeknum>/'. Then you need a view which has a customget_queryset` method, using techniques similar to what's described in the search tutorial you went through earlier. E. g.
def get_queryset(self):
return Post.objects.filter(category=self.catname).filter(week=self.week)Then you want a form that uses the correct widgets for collecting inputs, as you want them. You can read about widgets here. I would guess you want RadioSelect and Select. Once you've done that, you write a 'search input' view, which uses the form and forwards the user to the custom queryset view (using the HTML <form>'s action attribute).
Something like that anyway :)
Hello. I'm having some trouble when submitting a form that has several fields.
I have a 'Notes' model, which has a text field and other different fields, but the one I want to edit for now is the text field only. I created a ModelForm from the Notes model and I'm looping over all the table rows that have a note that is related to a specific project. What I want is to display all the notes at once and be able to edit whichever I want (one or more at once) and then submit them. However, when I hit the submit button after editing any of them, nothing happens, they are not changed; except when I edit the last one, which updates the database table, but puts that value in all of those rows.
save(commit=False) because I'm not doing anything with the data before saving it, but saving directly didn't change anything. I also tried to change where the submit button is, but nothing happened either. Why is this only submitting the last text field and putting that text value in all of the rows in my table?
name attribute (note_text, I would guess). When the user POST's their data, only the last form's note_text value is sent with the POST request, I think. It effectively "overwrites" all the other forms' note_text value. From your view's perspective, the view receives a POST dictionary that has a note_text key, paired with whatever value that was input for the last form on the page. So when you feed that dictionary of key-value pairs into the NoteForm class call, each time the same value is used.
When the user POST's their data, only the last form's note_text value is sent with the POST request, I think. It effectively "overwrites" all the other forms' note_text value. From your view's perspective, the view receives a POST dictionary that has a note_text key, paired with whatever value that was input for the last form on the page. So when you feed that dictionary of key-value pairs into the NoteForm class call, each time the same value is used.
@datalowe That's exactly what's happening, and I don't really know how to access a specific element's data from my view. When modifying an existing model instance, I thought I could access it's pk, but I haven't been able to find how to do that—or if it would actually work. Although, when adding a functionality to add a new note, there would be no pk before it's saved to the database.
I'll check the formsets and see what I can do. Thank you very much. Great as always.
@datalowe I was able to make my forms work with formsets, specifically with model formsets. This is because I am editing model instances. My current task is very simple, but I—and anyone else reading this—can build from here to more complex things.
I'm not updating anything on my forms.py file because, with this approach I ended up not using it.
Here is my view
project_id; this is why I'm not using the forms.py file and doing everything here in the view.
