Saravanan666/pypi-org huggingface dataset:
Package: wagtail-cjk404
Managed 404 Pages with RedirectsDescriptionA Wagtail package which will give you ability to automatically log and create of redirects from within Wagtail admin panel.FeaturesAutomatic "404 Not Found" HTTP Error Detection Following the Non-Existent Page OpeningSupport for Redirects toWagtail PagesHow It WorksRegular Expression → Regular Expression[currently in development]Regular Expression → URLRegular Expression → Wagtail PageURL → URLURL → Wagtail PageRepository inspired by / based on a fork of:wagtail_managed404- abandoned in 2018django-regex-redirects.Both projects were similar (oneModelclass and fairly uncomplicatedMiddleware), so the easiest thing was simply to combine them, and work onwards from this base.
Below, you can see the classes comparison of those two.Django Regex RedirectsWagtail Managed 404 (Cjk404)class Redirect(models.Model)class PageNotFoundEntry(models.Model)•old_path•url•new_path•redirect_to_urlorredirect_to_page•regular_expression-•fallback_redirect-•nr_times_visited•hitsTestingUse either Django test runner (python manage.py test cjk404) or pytest.Dependencieswagtail.contrib.modeladmin (https://docs.wagtail.io/en/stable/reference/contrib/modeladmin/index.html)This package is used for the admin panel itself.Screenshots"All Redirects" in the Backend"Edit Redirect" in the BackendUsageFresh installGet the app from PyPI:pip install wagtail-cjk404Add 'cjk404' to the INSTALLED_APPS:INSTALLED_APPS=[...'wagtail.contrib.modeladmin',# required dependency'cjk404'...]Add the supplied middleware. You may also want to disable Wagtail's defaultRedirectMiddleware:MIDDLEWARE=['cjk404.middleware.PageNotFoundRedirectMiddleware',# "wagtail.contrib.redirects.middleware.RedirectMiddleware",]Run the migrations:pythonmanage.pymigrateVisit the Wagtail admin area. You should see any 404s recorded in the application, and you can add redirects to them. You can also add your own redirects, e.g. based on regexp.Upgrade from the old (dj-apps-cjk404) versionRemove folderapps/cjk404with all contentsChange 'apps.cjk404' to 'cjk404' in INSTALLED_APPS.Get the app from PyPI: ```pip install wagtail-cjk404``You're done!DevelopmentUtility scripts - testingAssuming you have Django>=4.0 and Wagtail>=3.0 pip-installed in your virtual environment, you do not need to set up a new Django/Wagtail project to develop/test the app.After yougit clonethe repository, useload_tests.pyto callboot_djangoand then to execute the unit tests.AuthorsGrzegorz KrólFilip WoźniakGithub URLOld URL:https://github.com/cjkpl/dj-apps-cjk404New URL:https://github.com/cjkpl/wagtail-cjk404Please migrate your local repositories to the new URL by executing:$ git remote set-url origin https://github.com/cjkpl/wagtail-cjk404
Package: wagtail-cjkcms
CMS system for Wagtail 5.x, Django 4.x and 5.x, with support for Bootstrap 5.x and MDBootstrap 5.x.SummaryOut of the box, CjkCMS provides your project with generic, reusable pages:[Project] ArticleIndex,[Project] Article,[Project] WebPagewhich you can use in your project, or easily extend with additional functionality by defining new blocks from scratch, or installing any Wagtail application that defines new blocks.CjkCMS pages provide you with an ultra-flexible, generic "body" section and, usingwagtail-seopackage, a basic SEO functionality.HomepageProject homepage, with demos, examples and documentation:https://cjkcms.com/DocumentationDirect link to the documentation:DocsBeginningsCjkCMS was forked from, and is based onWagtail CRX- an excellent CMS byCodeRed.Contact & supportPlease useGithub's Issue Trackerto report bugs, request features, or request support.
Package: wagtail-ckeditor
Wagtail CKEditor pluginThis is aWagtailplugin, which allowsCKEditorto be used as an internal editor
instead of hallo.js or draftail.RequirmentsWagtail 2+
Django 3+How to installIncludewagtail_ckeditorin yourINSTALLED_APPS.Ensure that you have this entry in yoursettings.pyfile.WAGTAILADMIN_RICH_TEXT_EDITORS = {
    'default': {
        'WIDGET': 'wagtail_ckeditor.widgets.CKEditor'
    }
}There are several options you can add to yoursettings.pyfile.WAGTAIL_CKEDITOR_CONFIG = {
    "language": "ru",
}Inspired by:Richard Mitchell (https://github.com/isotoma/wagtailtinymce.git)
mastnym (https://github.com/mastnym/wagtail-ckeditor)
Package: wagtail-cloudfront-invalidate
A Wagtail hook to invalidate a path when a page is updatedInstallationpip install wagtail-cloudfront-invalidateConfigurationINSTALLED_APPS = [
    'wagtail_cloudfront_invalidate'
]

AWS_ACCESS_KEY_ID = '<your access key id>'

AWS_SECRET_ACCESS_KEY = '<your secret key>'

CLOUDFRONT_DISTRIBUTION_ID = '<your distribution id>'

WAGTAIL_CLOUDFRONT_INVALIDATE_ENABLED = True #defaults to False
Package: wagtailcloudinary
Use cloudinary within wagtailThis project is still maintained, but I prefer this approach instead nowhttps://gitlab.com/thelabnyc/wagtail-cloudinary-imageAboutThis package adds Cloudinary support to Wagtail CMSInstallationpip install wagtailcloudinaryWagtail 2.4 and Django 2.1 are supported.ConfigurationAdd app wagtailcloudinary in your INSTALLED_APPS list. Also add cloudinary if not already done.INSTALLED_APPS = [
    ...
    'cloudinary',
    'wagtailcloudinary',
    ...
]in settings.py put your cloud_name, api_key and apy_secret into cloudinary configurationimport cloudinary

cloudinary.config(
    cloud_name=<YOUR_CLOUDINARY_CLOUD_NAME>,
    api_key=<YOUR_CLOUDINARY_API_KEY>,
    api_secret=<YOUR_CLOUDINARY_API_SECRET>,
)Next edit your urls.py like this:from wagtailcloudinary import site

urlpatterns = [
    ...
    url(r'^wagtailcloudinary', include(site.urls, namespace="wagtailcloudinary")),
    ...
]Usagein models.pyfrom wagtail.wagtailadmin.edit_handlers import FieldPanel
from wagtail.wagtailcore.models import Page
from wagtailcloudinary.fields import CloudinaryField
from wagtailcloudinary.widgets import AdminCloudinaryChooser

class SomePage(Page):
    image = CloudinaryField()

    content_panels = Page.content_panels + [
        FieldPanel('image', widget=AdminCloudinaryChooser),
    ]Or use in a streamfieldfrom wagtailcloudinary.blocks import CloudinaryImageBlock
Package: wagtail-collectionmodeladmin
Collection Model AdminInstallationpipinstallwagtail-collectionmodeladminDevelopmentCheckout this repo, create a local virtual environment and install dependencies:pipinstall-e.Create a newdemowagtail project:wagtailstartdemoWe will use thehomeapp as the base for our demo. Add a newModelindemo/home/models.py:fromdjango.dbimportmodelsfromwagtail.core.modelsimportCollectionMemberclassDemo(CollectionMember,models.Model):demo_field=models.CharField()Add thewagtail.contrib.modeladminto the demoINSTALLED_APPSatdemo/demo/settings/base.py:INSTALLED_APPS=[...'wagtail.contrib.modeladmin',]Create the wagtail hooks that will inject the model admin indemo/home/wagtail_hooks.py:fromwagtail.contrib.modeladmin.optionsimportmodeladmin_registerfromcollectionmodeladmin.baseimportCollectionModelAdminfromhome.modelsimportDemoclassDemoModelAdmin(CollectionModelAdmin):model=Demomodeladmin_register(DemoModelAdmin)Then as usual make migrations, apply them, create a superuser and start the Django server.cddemo
pythonmanage.pymakemigrations
pythonmanage.pymigrate
pythonmanage.pycreatesuperuser

pythonmanage.pyrunserver
Package: wagtail-color-panel
Wagtail-Color-PanelIntroduces panels for selecting colors in Wagtail.FeaturesNativeColorPanel that can be used in your edit handlerNativeColorBlock for usage in a StreamFieldBased on the native HTML5 color pickerA custom db field for improved validationPolyfillColorPanel for cases that require IE11 support (built onSpectrum)Examplefromwagtail.modelsimportPagefromwagtail_color_panel.fieldsimportColorFieldfromwagtail_color_panel.edit_handlersimportNativeColorPanelclassMyPage(Page):color=ColorField()content_panels=Page.content_panels+[NativeColorPanel('color'),]DocumentationGetting startedAdding panel to a PageAdding to a StreamFieldReferenceContributingWant to contribute? Awesome. Just send a pull request.LicenseWagtail-Color-Panel is released under theMIT License.
Package: wagtailcolourpicker
A colour picker for Wagtail’s DraftJS editor.InstallationpipinstallwagtailcolourpickerSetupAdd to installed app:INSTALLED_APPS=[...'wagtailcolourpicker',...]Settings# picker iconWAGTAILCOLOURPICKER_ICON=['...']# Add your coloursWAGTAILCOLOURPICKER_COLOURS={'black':'#000000','white':'#ffffff'}DocumentationCan be found onreadthedocs.ScreenshotsPickerSelected TextExample site with dockerClone the repo$gitclonehttps://github.com/AccentDesign/wagtailcolourpicker.gitRun the docker container$cdwagtailcolourpicker$docker-composeupCreate yourself a superuser$docker-composeexecappbash$pythonmanage.pycreatesuperuserGo tohttp://127.0.0.1:8000/cmsand add a new basic pageTestingTODO
Package: wagtailcolumnblocks
A generic, reusable column block for Wagtail's StreamField.Allows developers to create column layouts with a number of different layout
ratios that are supported in the admin in a visually appealing way.A basic frontend template is included, but no frontend CSS. Due to the
variations of responsive layouts and frontend layout frameworks,
frontend templates should be overridden by the developer.InstallationOnce you have set up Wagtail, you should just need to do the following:pip install wagtailcolumnblocksEdit INSTALLED_APPS in your settings.py to include 'wagtailcolumnblocks'.Usage ExampleAssuming you have set up Wagtail according tothese instructions(and those above), you can see wagtailcolumnblocks in action as follows.Edit home/models.py to look like this. HomePage is from the original templated code, and we've added SidebarPage and the *Blocks classes:fromdjango.dbimportmodelsfromwagtail.core.modelsimportPagefromwagtail.coreimportblocksfromwagtail.coreimportfieldsfromwagtail.embeds.blocksimportEmbedBlockfromwagtail.images.blocksimportImageChooserBlockfromwagtail.admin.edit_handlersimportFieldPanel,StreamFieldPanelfromwagtailcolumnblocks.blocksimportColumnsBlockclassMyContentBlocks(blocks.StreamBlock):"""The blocks you want to allow within each MyColumnBlocks column."""image=ImageChooserBlock()text=blocks.CharBlock()classMyColumnBlocks(blocks.StreamBlock):"""All the root level blocks you can use"""column_2_1=ColumnsBlock(# Blocks you want to allow within each columnMyContentBlocks,# Two columns in admin, first twice as wide as the secondratios=(2,1),# Used for grouping related fields in the streamfield field pickergroup="Columns",# 12 column frontend grid (this is the default, so can be omitted)grid_width=12,# Override the frontend templatetemplate='home/blocks/two_column_block.html',)classSidebarPage(Page):content=fields.StreamField(MyColumnBlocks)content_panels=[FieldPanel('title'),StreamFieldPanel('content')]classHomePage(Page):passEdithome/templates/home/sidebar_page.htmlto look like this:{% extends "base.html" %}
{% load static %}
{% load wagtailcore_tags %}

{% block content %}<divclass="row">{{page.content}}</div>{% endblock content %}Edithome/templates/home/blocks/two_column_block.htmlto look like this:{% load wagtailcore_tags %}<divclass="row">{% for column, width in columns %}<divclass="col-xs-12 col-md-6">Column width = {{ width }}
            {% include_block column %}</div>{% endfor %}</div>Runpython manage.py makemigrations && python manage.py migrateto add our SidebarPage migration and execute it.In the Wagtail admin you should now be able to create a Sidebar page which shows up in a two column layout. When you view or preview the page you should see the templated content.DeploymentDeployment to pypi should happen automatically via travis-ci.org once the commit on master is tagged appropriately.LicenseLicensed under the BSD 3-clause "New" or "Revised" License.(c) 2017-2024, Squareweave. All rights reserved.
Package: wagtailcommonblocks
# wagtailcommonblocks [![PyPI](https://img.shields.io/pypi/v/wagtailcommonblocks.svg)](https://pypi.python.org/pypi/wagtailcommonblocks)> Common StreamField blocks for Wagtail.*Check out [Awesome Wagtail](https://github.com/springload/awesome-wagtail) for more awesome packages and resources from the Wagtail community.*## QuickstartAssuming you have a [Wagtail](https://wagtail.io/) project up and running:```shpip install wagtailcommonblocks```Add commonblocks to your `settings.py` in the INSTALLED_APPS section, before the core wagtail packages:```python...'commonblocks','wagtail.contrib.wagtailsitemaps',...```# Available blocks* CommonPageChooserBlock* SimpleRichTextBlock* CommonImageBlock* CommonQuoteBlock* CommonHeadingBlock* CommonVideoBlock* CommonInternalLink* CommonExternalLink* CommonLinksBlockYou can override the headings of the `CommonHeadingBlock` block:```python...COMMONBLOCKS_HEADING = (('h1', 'h1'),('h2', 'h2'),)```## Development### Releases- Make a new branch for the release of the new version.- Update the [CHANGELOG](https://github.com/springload/wagtailcommonblocks/CHANGELOG.md).- Update the version number in `setup.py`, following semver.- Make a PR and squash merge it.- Back on master with the PR merged, use `make publish` (confirm, and enter your password).- Finally, go to GitHub and create a release and a tag for the new version.- Done!
Package: wagtail-commonmark
wagtail-commonmark: CommonMark fields and blocks for WagtailTired of annoying rich text editors getting in the way of your content
input?  Wish Wagtail worked more like a wiki?  Well, now it can.wagtail-commonmarkprovides CommonMark field support forWagtail.
Specifically, it provides:Awagtailcommonmark.blocks.CommonMarkBlockfor use in streamfields.Awagtailcommonmark.fields.CommonMarkFieldfor use in page models.Awagtailcommonmark.edit_handlers.CommonMarkPanelfor use in the editor interface.Awagtailcommonmark.jinja2tags.commonmarkextension for use in jinja2 templates.Acommonmarktemplate tag.InstallationAlpha release is available on Pypi -https://pypi.org/project/wagtail-commonmark/- installable viapip install wagtail-commonmark.Using itAdd it toINSTALLED_APPS:INSTALLED_APPS+=['wagtailcommonmark',]Use it as aStreamFieldblock:fromwagtailcommonmark.blocksimportCommonMarkBlockclassMyStreamBlock(StreamBlock):markdown=CommonMarkBlock(icon="code")Or use as a page field:fromwagtailcommonmark.edit_handlersimportCommonMarkPanelfromwagtailcommonmark.fieldsimportCommonMarkFieldclassMyPage(Page):body=CommonMarkField()content_panels=[FieldPanel("title",classname="full title"),CommonMarkPanel("body"),]And render the content in a template:{%loadwagtailcommonmark%}<article>{{self.body|commonmark}}</article>
Package: wagtail-condensedinlinepanel
Condensed InlinePanel for Wagtail CMSThis repository contains a drop-in replacement for Wagtail'sInlinePanel.
It's designed with a lighter interface that's suitable for cases where there
may be hundreds of items in the panel.FeaturesFast, react-based UI which hides away forms that aren't being usedDrag and drop reorderingAdd a new item at any pointInstallationFirstly, install the module with PIP:pipinstallwagtail-condensedinlinepanel==0.5.2Then, addcondensedinlinepanelto yourINSTALLED_APPS:# settings.pyINSTALLED_APPS=[...'condensedinlinepanel',...]Then, finally, import the edit handler and use it.CondensedInlinePanelcan be used as a drop-in replacement for Wagtail's built-inInlinePanel:# models.py...fromcondensedinlinepanel.edit_handlersimportCondensedInlinePanel...classMyPage(Page):...content_panels=[...CondensedInlinePanel('carousel_items',label="Carousel items",card_header_from_field="title"),]
Package: wagtail-constance
I know there iswagtail.contrib.settingsavailable, but I’m a big fan ofdjango-constancewith redis backend!InstallationMake sure you installeddjango-constancethen install wagtail-constance:pipinstallwagtail-constanceAnd then just addwagtailconstanceintoINSTALLED_APPS:INSTALLED_APPS=(...'wagtailconstance',...)NoteI’m not added wagtail or constance as requirements in setup.py.
I’m tested it out only with python 3.5.1CreditsReleased underMIT Licensewagtaildjango-constancethissnippet
Package: wagtail-contact-reply
Wagtail Contact ReplyReply to contact form submissions directly from the Wagtail adminInstallationpip install wagtail-contact-replyINSTALLED_APPS=[# ....'wagtail_contact_reply',# Must be before wagtail.contrib.forms'wagtail.contrib.forms',# ...]ContributingI'm always open to PR's to improve this code and I'm not too picky about how it gets done. If you can make a contribution, I invite you to open a pull request (or an issue).TodosThings I want to do with this package but may or may not get the time to do...Save replies to each contact submissionView replies from each contact submissionAllow BCC emailsOptionally email all other adminsAdd a hook after the reply email is sentCreate default settings to fallback onAdd JavaScript form validation (ie. If the form is trying to be submitted but is missing a required field, show an alert box above the button)A few standard tests for at leastsomecoverageContibutorsKalob TaulienYour name soon?
Package: wagtail-content-admin
wagtail-content-adminA Wagtail app for working with content-driven model instances in the admin interface. Please bear with us while we prepare more detailed documentation.Compatibilitywagtail-content-admin' major.minor version number indicates the Wagtail release it is compatible with. Currently this is Wagtail 4.1.xInstallationInstall usingpip:pipinstallwagtail-content-adminAddwagtail_content_adminto yourINSTALLED_APPSsetting:INSTALLED_APPS=[# ...'wagtail_content_admin'# ...]
Package: wagtail-content-block
wagtail-content-blockContent block primitives for Wagtail, used by wagtail-content-admin. Please bear with us while we prepare more detailed documentation.Compatibilitywagtail-content-block' major.minor version number indicates the Wagtail release it is compatible with. Currently this is Wagtail 4.1.xInstallationInstall usingpip:pipinstallwagtail-content-blockAddwagtail_content_blockto yourINSTALLED_APPSsetting:INSTALLED_APPS=[# ...'wagtail_content_block'# ...]
Package: wagtail-content-import
Wagtail Content Import is a module for importing page content into Wagtail from third-party sources.
Page content is imported into a StreamField, using a set of customisable mappings.
Currently supports:As sources:Google DocsOneDrive/SharePointAs files:Google Docs documents with:Rich textTablesImagesHeadingsDocx files with:Text with bold and italicsHeadingsRequirements:Django >= 3.2Wagtail >= 4.1For the full documentation, see:https://torchbox.github.io/wagtail-content-import/Note for Google ImportIf using Google Docs import, for users to authenticate with Google they must either allow third party cookies or addaccounts.google.comto their allowed domains (Settings/Privacy and Security/Cookies and other site data in ChromeorPreferences/Privacy & Security in Firefox).
Package: wagtailcontentstream
Wagtail Content StreamAn abstract Django model with a Wagtail StreamField namedbodywith multiple blocks I use on a regular basis. This is geared towards developers who need to write examples with code in them. It's opinionated: very little HTML is allowed in the text block, forcing authors to create structured data. The following blocks are included inContentStreamBlock:HeadingParagraphCaptioned ImageEmbedTableCode BlockA secondary StreamBlock,ContentStreamBlockWithRawCode, also provides an additional block for injecting HTML, JS, and CSS code. Use with care, as this can really blow up your markup and is a potential code injection point!Three pages types are provided out-of-the-box.Example UsageYou will need to addwagtailcodeblockto yourINSTALLED_APPSDjango setting.Basic Usage: a Title Field and Content StreamFirst, create a page type in yourmodels.py:fromwagtailcontentstream.modelsimportContentStreamPage,SectionContentStreamPage,ContentStreamPageWithRawCodeclassStandardPage(ContentStreamPage):passclassSectionStandardPage(SectionContentStreamPage):passclassStandardPageWithRawCode(ContentStreamPageWithRawCode):passThen in your template:{%loadwagtailcore_tags%}<h2>{{page.title}}</h2>{%include_blockpage.body%}Extended Usage: Adding More Fieldsfromdjango.confimportsettingsfromdjango.dbimportmodelsfromwagtail.admin.edit_handlersimportFieldPanelfromwagtailcontentstream.modelsimportContentStreamPageclassStandardPage(ContentStreamPage):date=models.DateField("Post Date")authors=models.ManyToManyField(settings.AUTH_USER_MODEL)content_panels=[FieldPanel('date'),FieldPanel('authors'),]+ContentStreamPage.content_panelsRelease Notes & ContributorsThank you to ourwonderful contributors!Release notes areavailable on GitHub.Project MaintainerTimothy Allen (https://github.com/FlipperPA)
Package: wagtail-copyablemodeladmin
Wagtail CopyableModelAdminCopyableModelAdmin is an extension of theWagtail ModelAdminthat allows for model instances to be copied in the user interface with a "Copy" button.DependenciesInstallationUsageGetting helpGetting involvedLicensingCredits and referencesDependenciesPython 3.6+Django 1.11+, 2.0+Wagtail 1.13+, 2.0+InstallationInstall wagtail-copyablemodeladmin:pipinstallwagtail-copyablemodeladminAddcopyablemodeladminas an installed app in your Djangosettings.py:INSTALLED_APPS=(...'copyablemodeladmin',...)UsagePlease see theWagtail ModelAdmin documentationfor getting started with ModelAdmin.When creating aModelAdminfor objects that should be copyable, instead of inheriting fromModelAdmin, inherit fromcopyablemodeladmin.options.CopyableModelAdmin:fromwagtail.contrib.modeladmin.optionsimportmodeladmin_registerfromcopyablemodeladmin.optionsimportCopyableModelAdminfrommyapp.modelsimportBook# Inherit from CopyableModelAdmin instead of ModelAdminclassBookAdmin(CopyableModelAdmin):model=Booklist_display=('title','author')list_filter=('author',)search_fields=('title','author')# Now you just need to register your customised ModelAdmin class with Wagtailmodeladmin_register(BookAdmin)In addition toCopyableModelAdmin, there are three mixin classes that can be added to other customModelAdminsubclasses:fromcopyablemodeladmin.helpersimportCopyButtonHelperMixinfromcopyablemodeladmin.optionsimportCopyableModelAdminMixinfromcopyablemodeladmin.viewsimportCopyViewMixinclassCustomCopyButtonHelper(CopyButtonHelperMixin,CustomButtonHelper):passclassCustomCopyInstanceView(CopyViewMixin,CustomInstanceSpecificView):passclassCustomCopyableModelAdmin(CopyableModelAdminMixin,ModelAdmin):button_helper_class=CustomCopyButtonHelpercopy_view_class=CustomCopyInstanceViewGetting helpPlease add issues to theissue tracker.Getting involvedGeneral instructions onhowto contribute can be found inCONTRIBUTING.LicensingTERMSLICENSECFPB Source Code PolicyCredits and referencesForked fromcfgov-refresh
Package: wagtaildependencies
Wagtail Dependencies====================This package for Wagtail makes it easy to manage front-end dependencies for admin plugins.#### The problemMultiple Wagtail plugins may require the same front-end dependency, ex. Font Awesome. But we don't want to require that dependency twice on the admin screen, so we need to detect that duplication and only include it only once.#### The solutionWe can use named dependencies to prevent duplication, as long as developers can agree to use the same name. For instance, if we name Font Awesome `fontawesome`, then multiple projects can enqueue the `fontawesome` CSS, and this app will be sure it's only imported once.Usage-----Add `wagtaildependencies` to your `INSTALLED_APPS`, then you can use the following hooks:* `enqueue_scripts`* `enqueue_styles`The system will automatically detect duplicates among enqueued media throughout apps and will only include the library once.Example-------```python@hooks.register('enqueue_scripts')def enqueue_jquery():return {'jquery': {'source': 'lib/js/jquery.js','version' '3.1.0',}}@hooks.register('enqueue_styles')def enqueue_fontawesome():return {'fontawesome': {'source': 'lib/css/fontawesome.css','version': '4.6.3',}}```