Closed.php uneditable

closed.php uneditable

I have been noticing that the closed.php can't be edited.

Workflow

Support request

Status

Problem has been recorded

Submission on Feb. 7 2008 by Bernard

Owner

Anstey Stephan

Progress

I very much want to rework the language on this page, and put it in a simple template, however,wheneve ri update it gets over-written. It seems like maybe there should be an optional set of data text files

header-footer and body, if they exist load them, if not, then use the default. Obviously if the database is closed, so they shouldn't be stored there.

Comments

Bernard Paquesfrom nearby-an-airport Associate, 8408 posts	on Feb. 7 2008 That's correct. But instead of formulating this as a bug, the best way to go would be to offer a functional change of behavior in the area for new requirements. If we use text files, how to name them ? Where should they be placed ? Where in page should YACS use them ?
Anstey Stephan 305 posts	on Feb. 7 2008 I would propose a directory /closed which would have the index.php and the data files for header, footer, and message(s) [assuming multi-language] in the control panel, offer a link to edit the closed.php page. Header and footer could be simply a find image option for the masthead, perhaps an email address for the bottom, a title for the page. Possibly offer multi-language messages.
Bernard Paquesfrom nearby-an-airport Associate, 8408 posts	on Feb. 8 2008 I like the idea to edit the `closed.php` from the control panel, to generate a text file that would be included afterwards. This function already exists for the modification of .css files of a skin, we could transpose this to the closed page.