I reckon the 1st

hx-swap

should rather be

hx-trigger

I.e. you're telling htmx on what event it should do the hx-post. Also note, if you're putting something in the trigger event filter (i.e. the stuff in square brackets after

click

in this case), it should return a boolean. So perhaps add a

return true

at the end of your testing function

html
 <button hx-get="{% url 'detail' product.pk %}"
         hx-trigger="click[testing]"
         hx-swap="outerHTML">
            test
</button>

JS
var testing = function () {console.log("test");return true}

I tried it like this (there was a mistake in the hx events in the first post) and with the hx-trigger in it, the hx-get stops working

without the hx-trigger it works

with the hx-trigger neither the trigger nor the get works

Try taking out the

[testing]

and confirm that it works without the filter?

yes, works

html
 <button hx-get="{% url 'detail' product.pk %}"
         hx-trigger="click"
         hx-swap="outerHTML">
            test
</button>

Ok, so then the next step - is the

testing

function variable available in the global scope?

🤔

I can't spot anything wrong with that, sorry. Maybe someone else has an idea

oh!

Yes I can

I think you need

[testing()]

Yup, pretty sure you need to include the brackets with the function call in the filter

i.e.

html
<button hx-get="{% url 'detail' product.pk %}"
         hx-trigger="click[testing()]"
         hx-swap="outerHTML">
            test
</button>

You can see it explained here: https://htmx.org/attributes/hx-trigger/ in the 'Conditions can also refer to global functions or state' example

@User ☝️

haha yes that was it!

i did not think of that.

I should have spotted it sooner, sorry! That particular detail has bitten me too in the past... I can't believe I'd forgotten about it 🤦‍♂️ 😅

I'm new to HTMX but loving it so far: going through and replacing a lot of JS with it. In one case, I have a form that when submitted, the view returns an X-Accel-Redirect to a file so that nginx serves up the file. At the moment, HTMX is replacing the inside of my submit button with the byte code of the file (which makes sense). I'm using django-htmx, and I sort of know about HttpResponseClientRedirect, but I'm not sure if this is right since the POST request is already doing an X-Accel-Redirect. I suppose there's also 204 - No Content, but that also doesn't feel right either, since there is content being returned, I just don't want it swaped into the DOM anywhere. Should I just not be using HTMX here? I was hoping to use it to submit the form (and show an indicator spinner) without redirecting the page.

If you use

HX-Redirect

to the file URL, it should download properly

hmm, so instead of the X-Accel i can just add an HX-Redirec6t?

(sorry, crying baby in one hand!)

Hmm, so

self.filepath

in the image above is the actual location of the file on my server: there's no view or URLConf entry that serves up this file, so I'm not sure HX-Redirect will work, since I think it expects a URL

correct, is there a way to generate a URL for it?

Well, I was using X-Accel-Redirect because I didn't want the file to be exposed to the public, only available for certain logged in users. It might be that I don't really need HTMX in this situation, since the form submission will be returning the desired response anyways

Ah, got it. I am not familiar w/ that header, but it sounds like you are on the right track.

Looking forward to contributing a bit around here, really enjoying what I've learned about HTMX so far

Worked like magic. Thanks allot.