Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ToDo for Manager 2.0 #973

Open
2 of 4 tasks
ChristianMayer opened this issue Nov 17, 2019 · 5 comments
Open
2 of 4 tasks

ToDo for Manager 2.0 #973

ChristianMayer opened this issue Nov 17, 2019 · 5 comments

Comments

@ChristianMayer
Copy link
Member

ChristianMayer commented Nov 17, 2019

  • Make Manager protected for big installations (e.g. hotel), like having an admin settable password in the hidden.php
  • Templates for hidden.php section settings (a bit like the XSD for the config) to give the admin hints about the valid keys
  • Icons should show all available icons (not only the SVG ones) and also show different sizes and colors of a selected one
  • It should be possible to restore a backup of the config with the manager (and probably also to delete too old backups)
@ChristianMayer
Copy link
Member Author

  • strictly enforce the file system structure:

    • /config/ - contains only config files (i.e. file format visu_config.xml and visu_config_*.xml) and the hidden.php
    • /config/media/ - can contain any file and subfolders, no restrictions
    • /config/backup/ - automatic backup files of config files, file name visu_config*-DATECODE.xml

    Any files/folders that don't follow should not be displayed in the normal mode. The expert mode might show them but the only possible interaction should be "passive" (i.e. download and perhaps read only text editor)

@peuter
Copy link
Member

peuter commented Mar 15, 2020

What abount Config-Include files in this structure, are they allowed in the config/ Folder?

@ChristianMayer
Copy link
Member Author

As of today "snippets" (files to be included in a config file) would only be allowed in the config/media/ folder as those (usually) don't fit to the file name structure and definitely don't fit the syntax of a normal config (e.g. as they must not contain a <pages></pages> element).

But I'm open to relax that requirement a bit when we would force a strict file name structure for them like visu_snipplet_*.xml.

The idea behind being strict here is two fold:

  1. A strict structure helps the user to make good decisions about where to put what content (avoid "Qual der Wahl")
  2. A strict structure also helps us to have a simple infrastructure for automated tasks, like backups.

@ChristianMayer
Copy link
Member Author

For the first point: see also #1090

@ChristianMayer
Copy link
Member Author

Moved to a later milestone as the current level of the editor is IMHO fine for 0.12.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants