01364: Have a separate page for [[PmForm/]] templates.
This is already possible, simply set in local configuration something like:
$PmFormTemplatesFmt = array('Site.LocalPmFormTemplates', 'Site.PmFormTemplates');
True, but we didn't used to have Site.PmFormTemplates either, the summaries are fairly clear about thinking at the time, arguably Site.LocalTemplates was misnamed.
I wouldn't think it was misnamed, I'd suppose it was mis-summarized: (That page doesn't exist in a default installation. Both features - PageLists and PmForm - were designed to work with that name if such a page exists.) The page history is not long enough to show who added that summary. If only there was a way to fix the summary! :-) Petko April 13, 2015, at 01:27 PM
OK, you call the shots. My concern is simply that the page LocalTemplates can become large, and having different types of templates in it makes its meaning overloaded. Having clear guidance from the OOTB deliverables about a recommended structure (as defined in PmFormTemplatesFmt and wherever Site.LocalTemplates is defined) appeals to me. Appreciate your discussion
My understanding of Pm's intentions is that the software, settings and documentation OOTB should be as simple as practical (working) in order not to confuse and overload with information a person who would use the software OOTB. See my comment on the lack of
$FarmD in sample-config.php is a deliberate choice, not an omission. A person using so many templates that the page becomes overloaded is arguably an advanced user who can make his/her own choices. The software OOTB allows this change to be made, the feature you request exists, so to me this is a non-issue. But, if the community requires this change, I can make it in the core. --Petko April 14, 2015, at 12:25 PM