github/pelican
1
0
Fork 1
mirror of https://github.com/getpelican/pelican.git synced 2025-10-15 20:28:56 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #3462 from Kristinita/KiraValidPathMetadataValue

Browse source 
docs: Use raw string for the `PATH_METADATA` setting
This commit is contained in:
Justin Mayer 2025-04-19 12:28:16 +02:00 • committed by GitHub
commit f9711fa10a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/faq.rst
View file

@ -118,7 +118,7 @@ How do I make my output folder structure identical to my content hierarchy?
Try these settings::
USE_FOLDER_AS_CATEGORY = False
PATH_METADATA = "(?P<path_no_ext>.*)\..*"
PATH_METADATA = r"(?P<path_no_ext>.*)\..*"
ARTICLE_URL = ARTICLE_SAVE_AS = PAGE_URL = PAGE_SAVE_AS = "{path_no_ext}.html"
How do I assign custom templates on a per-page basis?

2
docs/settings.rst
View file

@ -458,7 +458,7 @@ If you don't want that flexibility and instead prefer that your generated
output paths mirror your source content's filesystem path hierarchy, try the
following settings::
PATH_METADATA = '(?P<path_no_ext>.*)\..*'
PATH_METADATA = r'(?P<path_no_ext>.*)\..*'
ARTICLE_URL = ARTICLE_SAVE_AS = PAGE_URL = PAGE_SAVE_AS = '{path_no_ext}.html'
Otherwise, you can use a variety of file metadata attributes within URL-related

2
pelican/settings.py
View file

@ -144,7 +144,7 @@ DEFAULT_CONFIG = {
"DEFAULT_ORPHANS": 0,
"DEFAULT_METADATA": {},
"FILENAME_METADATA": r"(?P<date>\d{4}-\d{2}-\d{2}).*",
"PATH_METADATA": "",
"PATH_METADATA": r"",
"EXTRA_PATH_METADATA": {},
"ARTICLE_PERMALINK_STRUCTURE": "",
"TYPOGRIFY": False,