Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Working with Pages and Forms on the backend
hcg_themes 0.5 output:
themes
└── default-4.5.7
├── forms
│ ├── article.article_listing.txp
│ ├── article.comments_display.txp
│ ├── article.default.txp
│ ├── article.search_results.txp
│ ├── comment.comment_form.txp
│ ├── comment.comments.txp
│ ├── comment.popup_comments.txp
│ ├── file.files.txp
│ ├── link.plainlinks.txp
│ ├── misc.images.txp
│ └── misc.search_input.txp
├── pages
│ ├── archive.txp
│ ├── default.txp
│ └── error_default.txp
└── styles
└── default.css4 directories, 15 files
Type before Form name, still don’t get what type is good for?
As a grouping mechanism for the backend, so you can collapse and expand your forms, that is if you have 50+ forms, I get it, but in the grand scheme of things, it’s confusing for the new user.
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Re: Working with Pages and Forms on the backend
hcgtv wrote #291900:
As a grouping mechanism for the backend, so you can collapse and expand your forms, that is if you have 50+ forms, I get it, but in the grand scheme of things, it’s confusing for the new user.
Yeah the types do seem rather arbitrary. I mean, a Section form type? I’ve started using that group for broad-stroke layout code, like head-meta, head-css, head-js, page-header, page-footer and so forth. Anything article-related goes in the Article group (though I’ve never used the Preview thing), reusable gallery code in the Images group, and so forth, with any remaining bits and bobs in Misc.
But without any clear distinction between them, you’re right it might seem confusing to newcomers. Ruud has often campaigned for the removal of Forms entirely since (besides the dubious preview feature) they offer nothing that a Page couldn’t also offer, as long as there was a suitable tag like <txp:output_form /> to render them. There’s some merit in that. The loss of the stupid name would be the most welcome benefit! It’s only the backwards-compatibility card that stands in the way, really.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Working with Pages and Forms on the backend
I’ve long been against the name ‘Forms’ for these template pieces (favouring partials) but I do think they have a distinction from overall pages templates, so I think they need to stay in some form (sorry for the pun).
I would kill the preview ‘feature’ though, it’s utterly useless and makes things look like they are broke when they are not.
Offline
Offline
Re: Working with Pages and Forms on the backend
…. texted postive
Offline
Re: Working with Pages and Forms on the backend
Are we changing the name? This was about whether the snippets/forms are needed (which they are, I think). Unless you had another form type of ‘pages’ and lumped everything within a templates section.
It’s probably best to stay with what we have currently though – it’s too ingrained in the system to change easily (tag names would need to change, attribute names too).
Offline