I think it'd be better for the project to just ship with a single version
if possible.
There shouldn't be anything stopping the developer from using whatever
version they like for the public site - if there is, then that's what
should be addressed.
On Wed, Dec 31, 2014 at 8:11 AM, Eduardo
Hello,
I had a quick question about the usage of the form_fields template. Is it
possible/viable to modify the fields_for tag to use a specific template
when rendering a given form? I have a form with rather specific formatting
requirements that just won't play nice with the rest of the forms,
PS: I was almost thinking about adding an extra argument to the fields_for
tag, which would be which template to use: defaults to
templates/includes/form_fields.html but can accept a different template. Is
that possible / a good idea? Or is there something I'm missing...
On Tuesday, 30
That sounds like a good enhancement - go for it.
On Wed, Dec 31, 2014 at 8:47 AM, Avery Laird laird.av...@gmail.com wrote:
PS: I was almost thinking about adding an extra argument to the fields_for
tag, which would be which template to use: defaults to
templates/includes/form_fields.html but
I'd be happy to! I was just unsure about whether or not my contribution
would be wanted -- I'm not very experienced in submitting code to large
projects. I'll make a pull request later today.
On Tuesday, 30 December 2014 14:44:07 UTC-8, Stephen McDonald wrote:
I don't think that's the right
Definitely welcome, thanks a lot.
To kick things off, I guess the current tag will need to change from an
inclusion tag to a regular template tag in order to make the template
optional.
Then as it's not longer an inclusion tag, the regular template tag would
return the result of rendering the
Hi there, thanks for getting back...
Indeed, it seems that something has changed in a new release of either
Django, Mezzanine, djangorestframework, or something else, that protects
the APIs - but I have no clue where to start digging.
If I copy a working session with Fiddler, coming from a
Can you roll back? That is where I would start.
On Tue, Dec 30, 2014 at 6:52 PM, Niels Jakob Buch njb...@gmail.com wrote:
Hi there, thanks for getting back...
Indeed, it seems that something has changed in a new release of either
Django, Mezzanine, djangorestframework, or something else,
Hi Stephen,
It actually involved very little change to the code. The new branch passed
all the tests, and there is a pull request up now. Your suggestion for the
return statement worked right off the bat!
Cheers,
Avery
On Tuesday, 30 December 2014 15:24:29 UTC-8, Stephen McDonald wrote:
