Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Developers are asked to help improve documentation, but the input format allowed is a bit restrictive (Filtered HTML). Documentation style could benefit greatly from allowing simple (secure) markup like tables, for instance.
Specifically, I'm speaking of http://drupal.org/node/224333 which contains some tables that compare "before" and "after" functions in several places that look broken right now.
Comments
Comment #1
janusman commentedSecond reference to "broken" table should be this one : http://drupal.org/node/224333#unmanaged_files
Comment #2
webchickI don't want to change the input format on the update pages, because it's absolutely important that anyone and everyone can keep those up-to-date, since they're so crucial.
However, since we trust people to not use their power to commit code that installs a back-door in every single Drupal site on the planet, it seems like we could trust them with images. ;P
Comment #3
avpadernoAs there is already a role for users with CVS access, what should be done is to create an input format that is associated with that role.
Comment #4
avpadernoI am changing the title, as it's more correct to say that the input format should be associated to users who are project maintainers (which is not depended from the system used to commit files in the repository).
Comment #5
dave reidAnd that input format should only be used on 'project' nodes, not any other nodes.
Comment #6
avpaderno@Dave: I agree.
The problem is how to implement that feature, as input formats normally are not limited to a particular content type; the only solutions would be to use a third-party module thought to restrict an input format to a set of content types, or to implement custom code in drupalorg.module. In both the cases, it's required the decision taken from an administrator.
Comment #7
dave reidI think this is another reason we need http://drupal.org/project/better_formats on drupal.org
Comment #8
avpadernoTo deploy Better Formats is what #558512: Install Better formats to limit the input format to a specific content type suggests; so far, there have not been replies on that, and no users chimed in to report that they would like to be able to use more HTML tags, even if in specific content types. I get the feature doesn't interest so much users, even though there are some use cases for the module on d.o.
Comment #9
simeOn IRC discussion of better_formats, killes preferred a trial of allowing
If it turns out that abuse of table (breaking layouts etc) is a problem then better_formats would be the next thing to consider, but until that happens then it remains that the less modules (ie. contrib dependencies) on d.o the better.
Leaving issue open for the momo, but I reckon close it.
Comment #10
simeComment #11
avpadernoI take the correct status of this report is postponed, until we don't have any reason to allow only specific roles to use a specific input format (or to allow all users to use a specific input format in a specific content type).
Comment #12
dddave commentedClosing old, stale issues as part of the webmaster's clean-up spring of DrupalCon Prague.