puput | A Django blog app implemented in Wagtail | Blog library

I have a custom image and rendition model, and have followed the wagtail v2.4 guide to implement them:

I use django-taggit 0.23.0 and wagtail 2.0.2 for a weblog app called puput 1.0.2.

Puput github repo

My preferred language is Persian (Farsi) in Wagtail's admin dashboard and one of my language letters is on the "comma" key of keyboard.
So, each time I want to use that letter, tag gets submitted and I cannot add tags properly. How can I customize ui-widget in adding/editing tags in admin's dashboard?
I also tried using these command lines in settings and overwriting its functions but yet didn't solve my problem:

TAGGIT_TAGS_FROM_STRING = 'utils.comma_joiner'
TAGGIT_TAGS_FROM_STRING = 'utils.comma_splitter'

Any solution would be a lot appreciated!!!

I´m trying to make a whatsapp button but I´m having problems with the trailing slash at the end on the href. Whatsapp renders wrongly with the trailing slash.

I´m using wagtail and puput. I´d like to do it on template only because wagtail and puput are addons on divio. If I install them separatedly, I would have to remake my website, so I can´t change models.py.

I´m using {% canonical_url entry %} for the href. What I´d like to have would be something like {% canonical_url|slice:":-1" entry %}

They provide full_url placeholder, but it doesn´t add date to link. It gives foo.com/slug instead of foo.com/2017/09/01/slug so everything gets rendered wrong too.

Any suggestions?

Thanks!

I am part editor and part developer and not utterly advanced at either career. But I am carrying out only a small-scale project. I'm thinking that in the blog that I recently added to my Django site (as yet only on the development server), with Wagtail and Puput, I might want to upload, say, two ~50KB images per week for five years, after which I'll be doing something else. There will never be a huge number of readers or a need for vast storage. Those being the circumstances, I specifically want to know if what I'm doing to overcome the problems that I encountered with uploaded images not resizing to small screens in the Puput blog, non-responsive design, looks feasible. Or, did I make some stupid mistake and, say, just use the Puput/Wagtail editor incorrectly?

When you click into the "body" textbox in the Puput editor to insert an image, it's quite simple. You just browse for your file, give the image a name, and select whether you want full-width or aligned on the left or right. And upon doing that your image will be uploaded into your previously established "media" folder and the database will simply be updated to contain the location of your image in the "media" folder. The tag in your text body will be given an ID attribute which is a link to the database entry.

Two troubling things then happen: (1) when you go into the browser's Responsive Design Mode the image is bigger than the small screen, no responsiveness; and, you actually don't now have an image stored in your media folder, you have three--- the original is in a subdirectory called "original_images" and there are two images in an "images" subdirectory. The two additional images may not have exactly the same pixel dimensions as the original, depending on your choice of full-width or not, the aspect ratio of the images perhaps, etc.

So this is rather intolerable, unless of course you can tell me what mistake I may have made. Otherwise, here's what I have done to get past this, and again, my question is would this work out in practice or do you have a better idea. I found this post on github, and in particular the comment by jerel concerning an insert_editor_js and wagtail_hooks.py hook. This overcomes the richtext limitations of standard hallo and permits opening a second editor window in which you can see and enter HTML.

But Wagtail has this Whitelister class that only permits certain attributes to be used with certain HTML tags. So the Wagtail people also have a hook for changing that, which is explained here. Here's my version of the wagtail_hooks.py file:

I've added a puput blog to an existing Django project. I followed all the steps for setting up a standalone blog app (https://puput.readthedocs.io/en/latest/setup.html).

It works fine in that I now have working blog at http://127.0.0.1:8000/blog/ and can edit the content and add new posts at http://127.0.0.1:8000/blog_admin/ . But where are all the files? Specifically the template file. I don't see any new folders or files in my Django project.

I would like to edit the html template in order to get a layout that fits with my project. But I can't find any files to edit.

I how someone can help. Thanks!