On 26/02/2008, Grietinus Koops grietinus@gmail.com wrote:
stupid question perhaps... But what were you doing? I didn't understand the question and neither the answer... But ir looked interesting
2008/2/19, Herta Van den Eynde herta.vandeneynde@gmail.com:
On 19/02/2008, Dan Bolser dan.bolser@gmail.com wrote:
What about the 'noresultsheader' dpl option?
Exactly what I need. Thanks, Dan!
Kind regards,
Herta
We're using the dpl extension to create dynamic pages (cf. http://semeb.com/dpldemo/ if you don't know it yet).
We're creating a customer -> services -> servers structure in our wiki (one to many relationships). We have a "data" article for each customer, service, and server, which simply defines a number of variables for that customer, service, and server. We have a dpl template for customers, another for services and a third for servers, which read the data from the "data" articles and formats it so that we have a uniform layout at each level. We then create one article per customer, service, and server, which calls the corresponding template to create the part that needs to be uniform, and allows room to add information specific to that customer, service, and server.
We created semi-templates for both "data" and the actual customer, service, and server articles, which people responsible for a new project can copy. All they have to do then is fill in the blanks.
The current data is extracted from a number of customer database type systems, and sometimes data is missing. I was looking for a way to stop dpl from throwing a warning.
The nice thing about this setup is that we can start out with a limited amount of data. Later on, we can simply replace the data articles with more elaborate ones (adding more variables), adjust the templates, and we're done.
Hope this clarifies it.
Kind regards,
Herta