I've been through the docs and I've been through the tutorial and I'm still not happy with what I've come up with for one of my pages, and I'm hoping there's a better way.
I have a News page which lists news items - you could think of them as the same as blog items if you like. I want to give editors the ability to add and edit these news items. But they're only ever displayed in a list on this page - i.e., there's no single page version for each of them. What I've done so far is to create a clonable template, news-item.php, containing the editable regions. This allows users to enter and edit news items via the admin page. Meanwhile in my news.php page, I have a cms:pages tag with news-item.php as the masterpage, displaying the news items fields as I wish, in a list. I am also able to display a subset of the items in a different format on the home page, which is helpful.
This system works but it seems slightly unsatisfactory to me because of the way the editor interacts with the page. Having entered the details, they can click a View button to see the result (and similarly they can click the view icon while looking a listing of existing pages). But there is in fact nothing to view as such, as there is no single page view for this page. What I've done so far is to test 'k_is_page' for the news-item.php and if true, redirect to 'news.php' where the items are displayed in a list. This seems pretty kludgy to me, although I can live with it.
What I would like to know is:
a) is there a better way of doing this whole thing?
b) if not, is there a way of hiding the View buttons for this page?
I have a News page which lists news items - you could think of them as the same as blog items if you like. I want to give editors the ability to add and edit these news items. But they're only ever displayed in a list on this page - i.e., there's no single page version for each of them. What I've done so far is to create a clonable template, news-item.php, containing the editable regions. This allows users to enter and edit news items via the admin page. Meanwhile in my news.php page, I have a cms:pages tag with news-item.php as the masterpage, displaying the news items fields as I wish, in a list. I am also able to display a subset of the items in a different format on the home page, which is helpful.
This system works but it seems slightly unsatisfactory to me because of the way the editor interacts with the page. Having entered the details, they can click a View button to see the result (and similarly they can click the view icon while looking a listing of existing pages). But there is in fact nothing to view as such, as there is no single page view for this page. What I've done so far is to test 'k_is_page' for the news-item.php and if true, redirect to 'news.php' where the items are displayed in a list. This seems pretty kludgy to me, although I can live with it.
What I would like to know is:
a) is there a better way of doing this whole thing?
b) if not, is there a way of hiding the View buttons for this page?