#django

is there documentation on using the test client with Sites somewhere?

hopthrisC: Why – you just set the SITE_ID setting, won't that be enough?

renlo: Looks more like your problem is that Django doesn't support EXISTS subqueries...

removing the a__bs__isnull still results in an incorrect count

I'm at my wits end with it; going to do a query for each query I guess, and maybe switch to raw sql or sqlalchemy in the future

just for this / for complicated queries

renlo: In cases where you just need an EXISTS subquery, you might have to write raw SQL at this time...

koniiiik: uhm.. i wont to test the requests to two different sites running on the same project work correctly (simplified)

koniiiik: how would i do that with SITE_ID?

thought so

hopthrisC: Ah, so you want to test an application with a domain-based approach to sites?

yes

in essence

hopthrisC: In that case, you can just set the Host header in your requests.

koniiiik: how do you mean?

self.client(..., HOST='whatever')?

hopthrisC: self.client.get('/url/path/', HTTP_HOST='domain1.example')

tried both, didn't work

i'll go look for the bug

There are several possible reasons; one might be that you do have SITE_ID set.

If you do, then that Site instance will be used regardless of the request domain.

used by what?

_i_ only use get_current_site(request)

By get_current_site.

get_current_site checks if d.c.sites is installed, if so, then it checks if SITE_ID is set, and uses that Site instance, otherwise it tries to get an instance based on the request domain; if d.c.sites is not installed, it returns a RequestSite.

yeah, just read the docs

what's the use in that?

Umm, why?

Those are the different ways in which d.c.sites can be used.

how do i avoid django rendering a client side "required" html5 attribute for a textfield

If you want to have a separate application server process per site, you set the setting; if you want to dynamically choose based on the domain, you don't set the setting.

i would have thought of SITE_ID as the fallback

the textfield is using a WUSIWUG and messing it up

fission6: Have you tried setting attrs={'required': False} in your form widget?

that may be the play thanks koniiiik

fission6: Also, the commonly used acronym is WYSIWYG.

yes thank you

haha

hopthrisC: why should it try to be smarter than you if you explicitly set a SITE_ID?

just don't set it if you want it to guess :)

moldy: i already did acknowledge my stupidity. why do you have to rub it in?

eh, that was not my intention

ok :)

i was just replying to "what's the use in that? / i would have thought of SITE_ID as the fallback"

yeah, i'm going to test what happens when SITE_ID is not set and it can't find a site for the request

but i think i got it now

what could be giving this import issue? https://gist.github.com/anddam/8a06dda82ed6b91c...

koniiiik: is this self.fields['description'].required = False

different from this attrs={'required': False}

i still want the form to validate as being required just not render "required" in the textarea

fission6: Yes, it is different.

attrs={'required': False} is what i want correct?

fission6: One sets whether the field itself is required, the other just the attribute of the rendered widget.

gotchat

i want attrs={'required': False}