Can add this to the request and it should work

setattr(request, "session", "session")
   messages = FallbackStorage(request)
   setattr(request, "_messages", messages)

I created a simple package to simplify the usage of htmx with django, check it out if you have a chance and let me know if you think there could be improvements or if there are any bugs! Thanks! https://pypi.org/project/simple-django-htmx/

Hello all. I was in hyperscript room with my question earlier. But I think since my setup is django (pythonanywhere), perhaps I should ask around here. The problem is that in my setup HTMX is working quite fine except for hx-vals attribute. And if I try to use the same code in a standalone page, the get request is called just as expected. The code is this:

<div id="calendar"
  hx-get="/day/"
  hx-vals="js:{date: new Date()}"
  hx-target="this"
  hx-swap="outerHTML"
  hx-trigger="load">
</div>

The get requested is initiated on the client side but without the ``date``querystring parameter appended to it. The same code works on a standalone local page.

Solved! I was using an earlier version of HTMX library. Upon using the latest one, it works now.

is this ready for production?

Also how does this compare to django-htmx library? Can you share a brief overview?

It's brand new so can't be positive that it covers all edge cases, I am currently using it for a project of my own.

The only comparison to django-htmx is pretty much the name. There are really 2 main points to the library : 1) To avoid the messy views you get when you use htmx with django. With my library the htmx requests manage themselves meaning that you don't need to do

if htmx reuqet .... else render regular view

, see the documentation for more details on how that works. 2) To avoid all the extra urls! You don't need a new endpoint for every single request (edit, delete etc.) instead the htmx requests handle it themselves. (again see documentation for more details) It also has some built in htmx requests for basic functionality. If you want a delete button, there's a built in htmx request that all you do is pass in the object (to a template tag) that you want to delete and the built in htmx request will handle it for you! Please take a look at the repo and documentation. https://github.com/yaakovLowenstein/simple-django-htmx I am open to pull requests if there's anything you can think of adding/ or if any bugs are found! Thanks!

Thanks! I ll read up the docs

@astonishing-kilobyte-60820 In the name ``HtmxVIewMixin`` is capital I a deliberate choice?

nope , that's embarrassing 🙈 . Thanks for pointing it out. I will fix it shortly

What did you think. Any thoughts about it?

(I am not an advanced-level programmer so I won't be able to give very great insights). I like it. Yes. I like the idea of hitting just one view for detail/list as well as Post/Get requests. The code will be neater and I feel it will bring clarity to the whole design. I am going to definitely use it in my project.

@astonishing-kilobyte-60820 Can you show a full example of how this can be implemented?

Hello everyone, I wrote my first article on handling full page reloads with Django and htmx and would love some feedback! https://medium.com/@john1galiszewski/how-to-handle-full-page-reloads-with-django-and-htmx-a9a7ef2e4b1c

Django and htmx article

Hello, I am a new user of htmx. So I can't find how to do what I want. On a simple task list, when I create a new task collection, I want to redirect to the new collection list. If I do the redirect in my view, the html is loaded into the collection. In the screenshot below I have my default collection and when I create my test collection it is added but I would like to be directly redirected to this collection.

I use slug like this : http://127.0.0.1:8000/?collection=_default

Thanks in advance for your help 😉

html:

html
                <form method="POST" class="d-flex gap-2 mt-2">
                    {% csrf_token %}
                    <input type="text"
                           name="collection-name"
                           class="form-control"
                           placeholder="Enter a new collection ...">
                    <button class="btn btn-success"
                            hx-post="{% url 'add-collection' %}"
                            hx-target="#collections"
                            hx-swap="beforeend"
                            type="submit">Add
                    </button>
                </form>

views:

py

def add_collection(request):
    collection_name = escape(request.POST.get("collection-name"))
    collection, created = Collection.objects.get_or_create(name=collection_name, slug=slugify(collection_name))
    if not created:
        return HttpResponse("The collection already exists.", status=409)

    return render(request, 'tasks/collection.html', context={"collection": collection})

2 options: 1. HX-redirect header to send user to another page https://htmx.org/reference/#response_headers. 2. Use OOB swaps to update both "Collections" and "Tasks" in combination with HX-Push header

Thanks for your feedback, i have see these options but i haven't understand how they work. i will go read this part of the documentation again. 😉

Yeah i have understand the HX-redirect ! Thanks again ! Have a good day.

Hi everyone, Still trying to improve at this. I have an issue with loading a button that simply toggles the state of a post whether it is published or unpublished. My Django view function works well and edits the Post database item. The function call seems to trigger the function but for some reason, the button does not update appearance. Instead the button disappears. Once I reload the page, the button appearance is as it should be. Any ideas?

Does the

admin-posts-partial

have those buttons? You can always inspect using webtools the html that is rendered by the backend on response to the toggle

İt seems like my mistake was, I was trying to reload the section without using a partial at all. 🫢 Finally fixed. Thank you @silly-bear-76516

Can anyone explain why PUT requests need a csrf token added with hx-headers but POST requests don’t (from my experience so far)? I was under the impression that all htmx requests except GET required this to avoid 403 Forbidden

I think they do, unless you’re attaching the token to the form using {% csfr_token %}

Yeah, attaching the token in the tag like that works for POST but not for PUT. In PUT’s case, only adding the token to the htmx request (hx-headers or requestConfig) works. Just unsure why!

Ah i see, hadn’t realized that tbh!