Page app listing output

Tony Perry asked on August 12, 2022 16:40

Hi,

A client has asked us to create a page, that is not for public viewing, to allow them to manage an element of the site all from one screen.

We have a load of locations in the system, and the client wants to be able to manage an alert for the location all from one place, without having to go into each of the page nodes within the CMS. This page in my head will look something like this:

Location Name Alert Message Date from Date to Location Name Alert Message Date from Date to Location Name Alert Message Date from Date to Location Name Alert Message Date from Date to Location Name Alert Message Date from Date to

and so on for each of the locations in the system which are pages in another part of the tree structure.

I've not seen anything in Kentico that allows for this to be done in the backend, other than a listing from a custom table, but I don't think that the custom table option is going to work, as I want to be able to provide date pickers for the date fields, and a WYSIWYG for the alert message

Any ideas?

kentic 12 mvc pages application

Recent Answers

Brenden Kehren answered on August 15, 2022 02:18

Use the content tree. Create an "Alert" page type with your necessary fields. From there tell your controllers when and where to get the specific alert from in your content tree.

Something like this is NOT a custom table or a custom module, it's content on a page.

0 votesVote for this answer Mark as a Correct answer

Tony Perry answered on August 17, 2022 17:18

Hi Brendan,

Thanks for your response firstly, have asked around the company and got nowhere.

So, if this forum actually allowed more formatting, it might have been clearer what I am trying to achieve.

We have a site tree along the lines of:

Home
--Locations
----Location1
----Location2
----Location3
----Location4
.
.
.
.
----Location200

What the ask from the client is, is to have a single page, sitting under the Locations node, that will list out all of the locations (200 or so of them), in the backend of the system only, and for each of the locations to have some additional field for them to enter.

This listing would need to look something like

<table>
<tr>
<td>Location 1</td>
<td><textarea name="locationContent"></td>
<td>Other field</td>
<td>Another field</td>
</tr>

<tr>
<td>Location 2</td>
<td><textarea name="locationContent"></td>
<td>Other field</td>
<td>Another field</td>
</tr>

Which then when I am building the location page for the frontend. I go off and look at this single page in the CMS, find the location and pull in the additional fields and do the rest of the clients request. As this is sort of a data structure, this is why I was looking at the custom table, but didn't really want to go down that route

Tony

0 votesVote for this answer Mark as a Correct answer