I only actually render the body tag in the situations where I expect the page to be fully swapped out

so treat the body tag always as an oob swap targeting the body

since I render fragments elsewise

I didn't try that though

that would be more generalizeable though because I'd define once in base.html and never need to alter for a given view

Hi everyone, I am trying to do the following:

html
<form id="frmUpdate" method="POST" enctype="multipart/form-data"
  hx-post="{% url 'products:update' product.id %}" 
  hx-target="#viewport"
  hx-swap="innerHTML"
  hx-push-url="true"
  hx-indicator="#content-loader"
  >
  {% csrf_token %}
  {% crispy form form.helper %}
  <div class="flex justify-end gap-3">
    <a hx-get="{{ product.get_list_url }}" 
      hx-target="#viewport"
      hx-swap="innerHTML"
      hx-push-url="true"
      hx-indicator="#content-loader"
      class="intro-x px-3 py-2 cursor-pointer">
      Cancel
    </a>
    <button class="intro-x text-white bg-blue-500 hover:bt-blue-600 px-3 py-2 rounded-md"
      type="submit"
      form="frmUpdate">
      Save
    </button>
  </div>
</form>

However, when ever I try to update the form....it validates as though it were empty...

I can see in the

clean

function on my ProductForm class that it is as well. What has me scratching my head is that I can see the POST in the Network tab in the debugger and it shows the data properly.....

Am I missing something?

is it expecting the

multipart/form-data

encoding?

It is set as show above....

feels like an encoding issue to me (sorry, not a django expert)

Yeah, it is strange. I noticed I only had the FORM

enctype

set so I added

hx-enctype="multipart/form-data"

but it still fails.....

@User I saw another post that stated they were running into the same issue. Once I switched to

1.5.0

of htmx, it started working...

Okay, I read further down....you need to change the

hx-enctype

to

hx-enctype="text/x-www-form-urlencoded"

and it works fine.

In Django, for regular forms, it is expecting:

enctype="multipart/form-data"

So this can be confusing...

Thanks for helping...Really love power of htmx!!!

👍 sorry for the confusion

it's strange that django is generating forms that are encoding using a format it doesn't like

nice

used the header - it does exactly what it says it should

it is a definite improvement over what I was doing before w/ the client side redirect

but I can forsee an issue where I have a view and care about the referring url to make a determination on where to target

I guess I'll just have to deal with that when it happens

sorry if that seems negative

The header is a major improvement and now I can keep global state on the client between form submits and that's really awesome

not at all, we are all figuring it out. What do you mean "the referring url"?

I have a mixin I've been using that looks at the incoming request and figures out of it's got htmx headers, and if so uses a different template