Wagtail CMS: Adding a banner and banner fields - Templates and Frontend Framework (Part 2)

[@wappyn]

Watching you jumping between dark mode editor, and completly white website at night on TV was a bit of pain. You made me find about night life at fedora :)

[@ArjitRaj]

The moment he says "Oh baby!" :-) 5:48

[@CodingForEverybody]

"Oh baby! Look at this" :)

[@Shasras]

Firstly, love the series and I'm slowly falling for Wagtail 😉 Secondly, yes, that is a bad CSS. As far as I know, a CSS rule with "!important" always takes precedence (even if it's located in external CSS file), so adding it to the "style" tag simply does not make sense.

[@marquesjohnson870]

My image is not currently showing. I'm listening more closely to the tutorial and looking around the code, and I don't see an issue, unless it has to do where my pics are stored.

[@CodingForEverybody]

It could be. But if you started your site with `wagtail start yoursitename` then it shouldn't be a problem. Make sure you take a look at the git repo (github.com/CodingForEverybody/learn-wagtail/) you can see all the code Im writing in this repo. And browse through the commits, too.

[@quickwell8030]

@@CodingForEverybody Hello. I have the same problem. As you wrote early, i started my site with "wagtail start mysite". So, how can I fix this problem?

[@benlamptey5208]

Hi there, thanks for these videos. I wanted to know what software do you use to record your screen ?

[@leondaz7380]

Hey kalob, What's the difference between using |richtext and |safe from django, I mean, wagtail automatically puts the needed HTML tags around the text when using a RichTextField() and we can just escape the tags with |safe and it should work the same

[@CodingForEverybody]

A RichTextField has custom HTML elements in it that map the images, pages, and documents. So a link to another page is not saved in the database with . The |richtext filter takes the custom html Draftail uses and converts it to proper HTML. This richtext can always keep track of other objects its linking to. You don't need |richtext if you aren't linking to pages, images or documents. If its just standard HTML like bold, italic, hr, lists, or headings you can avoid using |richtext.

[@leondaz7380]

@@CodingForEverybody Yea I expected this, Thanks for replying, Great content

[@faithbaghan9204]

Thanks for uploading the tutorial. I am getting an error (Invalid block tag on line 12: 'endif', expected 'endblock'. Did you forget to register or load this tag?) after adding the {% extends "base.html" %} line to home_page.html. 5:30

[@fredyorlandosiguantay7808]

i got a project in advanced develop on django and my chiefs want to incorporate wagtail to this project with existing models full with data, how can i use the existing models for wagtail model's and avoid make new models for wagtail

[@kevinjay62]

I just completed the second Banner and Banner Fields video and noticed that there are 144 database queries when I open a page for editing in the admin panel. Using the debug toolbar, I see many entries like this ( 58 similar queries. Duplicated 58 times. ). This seems excessive. My guess is that it's due to the way we've built the models. Is this something that we'll get to clean up later in the series?

[@CodingForEverybody]

Nope, this is somewhat normal with Django and Django Debug Toolbar. Duplicated queries are typically cached in Django, if I recall correctly as to not hit the database too many times. Having streamfields on your page adds queries as well and having links in your RichText will also create queries.

[@kevinjay62]

Ck, it will be interesting to see what the performance will be like with and without the debug toolbar installed. So far the performance issues are only seen in the admin panel.

[@CodingForEverybody]

@@kevinjay62 That's also pretty standard for the admin panel to have more overhead; it needs to access a lot more data, generally. This would be common for every CMS. But the debug toolbar isn't just a debugging tool, it's a profiler. So if you ever find a really slow loading page, try disabling DDT (django debug toolbar) and the lag will instantly go away. It takes quite a bit of power to profile a system.

[@sailendrachettri966]

Thanks..!!

[@votelearn1244]

thank U