wagtail

How to set multiple ParentalKeys to Wagtail TaggedItemBase tag class

蹲街弑〆低调 提交于 2020-12-23 08:19:07
问题 I have two different page models (no subclassing, separate apps with only similar fields being common ones like "model name", "id", "parts") , let's say, cars and motorcycles. I'm making a separate page with a table of their parts (which also needs to contain columns like "id" which i assume can be a pk,"web store link", and "used by" which will show all Bike and Car models that use the part); Since they can share a few of the same parts, I want for them to be connected to the same Tag model

How to set multiple ParentalKeys to Wagtail TaggedItemBase tag class

自作多情 提交于 2020-12-23 08:18:12
问题 I have two different page models (no subclassing, separate apps with only similar fields being common ones like "model name", "id", "parts") , let's say, cars and motorcycles. I'm making a separate page with a table of their parts (which also needs to contain columns like "id" which i assume can be a pk,"web store link", and "used by" which will show all Bike and Car models that use the part); Since they can share a few of the same parts, I want for them to be connected to the same Tag model

How to set multiple ParentalKeys to Wagtail TaggedItemBase tag class

允我心安 提交于 2020-12-23 08:17:19
问题 I have two different page models (no subclassing, separate apps with only similar fields being common ones like "model name", "id", "parts") , let's say, cars and motorcycles. I'm making a separate page with a table of their parts (which also needs to contain columns like "id" which i assume can be a pk,"web store link", and "used by" which will show all Bike and Car models that use the part); Since they can share a few of the same parts, I want for them to be connected to the same Tag model

Wagtail raises ValidationError on page update

扶醉桌前 提交于 2020-12-15 06:10:27
问题 On publishing updates to an existing wagtail page it raises a ValidationError with the message below. ValidationError({'live_revision': ['page revision instance with id 33 does not exist.']}) All other actions such as drafting, submitting for moderation all work okay. Only publishing the page with new updates raises the ValidationError effectively limiting the ability to update existing pages. 回答1: Just faced a very similar issue. Make sure you are not using ParentalKey in a Page model. Use

Wagtail raises ValidationError on page update

独自空忆成欢 提交于 2020-12-15 06:09:34
问题 On publishing updates to an existing wagtail page it raises a ValidationError with the message below. ValidationError({'live_revision': ['page revision instance with id 33 does not exist.']}) All other actions such as drafting, submitting for moderation all work okay. Only publishing the page with new updates raises the ValidationError effectively limiting the ability to update existing pages. 回答1: Just faced a very similar issue. Make sure you are not using ParentalKey in a Page model. Use

Wagtail filter page-childs-elements on the basis of logged-in user's permissions

℡╲_俬逩灬. 提交于 2020-12-12 06:18:08
问题 I am working on a small site using Wagtail. This site is all about a "mainpage" and several "subpages". So far it is pretty simple! But, depending on what group the user (not admin) is in, the right subpages should show up! See the following setup (minimized), to get an idea of what I am talking about. If I set permissions on ToolKitPart (like requiring explicit user-login and group-membership), then the following is happening: when going to the page using the fully qualified path, the user

additional fields associated with wagtail tags?

試著忘記壹切 提交于 2020-11-29 11:12:08
问题 I'm creating wagtail website that copies and adds to the functionality of old django website: there is a blog-like "animal-listing" and "plant-listing" pages with post-detail-like "animal detail" and "plant detail" pages. They share a common "need" tag via simple ManyToManyField, because animals and plants have some of the same needs (like water or hay). Need tags are displayed on the "needs page" table, which has columns like "store link". This original solution weren't as smooth as

additional fields associated with wagtail tags?

♀尐吖头ヾ 提交于 2020-11-29 11:11:07
问题 I'm creating wagtail website that copies and adds to the functionality of old django website: there is a blog-like "animal-listing" and "plant-listing" pages with post-detail-like "animal detail" and "plant detail" pages. They share a common "need" tag via simple ManyToManyField, because animals and plants have some of the same needs (like water or hay). Need tags are displayed on the "needs page" table, which has columns like "store link". This original solution weren't as smooth as