I'll try, thank you so much.
Il giorno domenica 10 settembre 2017 21:54:06 UTC+2, Rainell Dilou Gómez ha
scritto:
>
> Hello,
> I am trying to create a content type extending Blog, the migration is
> completed successfully but in the admin panel the content type does not
> exist, it is not
Hello Rainell,
as BlogPost inherits from "Displayable" and not "Page" I am not sure whether
the PageAdmin is the correct Admin class. If your register your model in
admin.py with admin.site.register(Recipe) it should show up allright. If
you want a similar form as for the BlogPost admin
If you add something like "url("^search/$", mysearch, name="search")" in
the main urls.py of your app above "url("^", include("mezzanine.urls")),"
it should work. I just tried it and it addressed my custom "mysearch"
perfectly.
Am Dienstag, 12. September 2017 17:19:20 UTC+2 schrieb
Yes it will, because the template uses the {% url %} tag and will
respect your urlpatterns. Just make sure you set name="search" in your
overridden pattern.
On 2017-09-12 9:19 AM, si...@e5r.no wrote:
tirsdag 12. september 2017 14.14.13 UTC+2 skrev Christian Kuper følgende:
Just create a
tirsdag 12. september 2017 14.14.13 UTC+2 skrev Christian Kuper følgende:
>
> Just create a new empty template and put {% extends 'template_to_extend'
> %} at the top. Then you get a template with your custom name and the same
> content as the build in template.
>
Yes, but that doesn’t override
Just create a new empty template and put {% extends 'template_to_extend' %}
at the top. Then you get a template with your custom name and the same
content as the build in template.
Am 12.09.2017 1:05 nachm. schrieb :
> tirsdag 12. september 2017 13.50.33 UTC+2 skrev Christian Kuper
tirsdag 12. september 2017 13.50.33 UTC+2 skrev Christian Kuper følgende:
>
> Not sure why you consider creating a custom template as not optimal. IMHO
> templates are for customizing.
>
> Create a custom template which extends the build in template, and all
> updates of the core framework will
Hi,
Not sure why you consider creating a custom template as not optimal. IMHO
templates are for customizing.
Create a custom template which extends the build in template, and all
updates of the core framework will be implemented.
Regards
Chris
Am 12.09.2017 8:02 vorm. schrieb :
Hi Rainell.
That’s indeed the second approach I tried to describe. It works well,
but for such a small thing as changing the search URL part it doesn’t
feel optimal. When doing so you have to watch out for changes to
Mezzanine’s built-in `search_form.html` in future releases and
backport it to