infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Schaefer (JIRA)" <>
Subject [jira] [Commented] (INFRA-9705) Remove elementid Markdown extension
Date Thu, 02 Jul 2015 01:56:04 GMT


Joe Schaefer commented on INFRA-9705:

I realize you guys are now of the mindset that randomly breaking shit and letting the projects
figure out how to cope after the fact is par for the course at Apache, but just because the
new attribute handling shipped with markdown has more features than doesn't
mean you can just drop it.   THE SYNTAX IS DIFFERENT!  The new stuff uses {: ... }, which
I have no idea what the Dotiac::DTL templates will do with when you use markdown as a filter
for included markdown template files or within markdown document source files themselves.
 That is why allows people to use [#...] and [. ...] instead of {# ... }
and {. ...} to avoid syntax conflicts.  If you really want to drop, you need
to communicate this change in the documentation IN ADVANCE OF MAKING THE SYSTEM CHANGE so
people can prepare for the fallout.  There won't be much fallout in terms of affected projects,
but there will be some, especially with

> Remove elementid Markdown extension
> -----------------------------------
>                 Key: INFRA-9705
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: CMS, Website
>         Environment:
>            Reporter: Sebb
>         Attachments: INFRA-9705.patch
> The elementid Markdown extension appears to have been originally intended to handle Special
Attributes as per PHP Markdown Extras [1]. However it was not a complete implementation.
> The elementid extension code was later extended to try to handle permalinks as per Subversion
[2]. However it turned out that this code interfered with TOC processing.
> It would of course be possible to fix both of these issues, however there seems little
point as the Python Markdown module includes atttribute lists [3] as well as permalinks [4].
> I think it therefore makes sense to disable elementid by removing it from
> Attribute lists and permalinks can then be enabled separately; see related JIRAs.
> [1]
> [2]
> [3]
> [4]

This message was sent by Atlassian JIRA

View raw message