VisioList aims to separate user customizations from the core skins files to allow for easier upgrades and maintenance. To this end, VisioList employs a few simple techniques to allow complete customization without hacking the core files.
3 simple rules
Any template edits you make ensure its in a child template (admin edits automatically do this)
Any CSS edits should be made in skins/default/user.css
Any PHP edits should be handled via a plugin
For these examples we assume your working with default skin.
Template Edits:Login to your admin panel, hover over settings tab, click on skins and categories.
Click "Edit Child" and click the template you want to customize from the list on the left. This will make a copy of the template file in default/child/ that you can edit. Child templates are never overwritten during an update, this again allows your customizations to be preserved after an update. You should still compare the new templates to your child templates to ensure you are not missing any new tags added to the core.
CSS edits: if you open skins/default/user.css you can add any CSS rules you like to this file to override the default styles. You can also add your own custom classes and ID's to this file. user.css is never overwritten during upgrades so your customizations are safe in this file.
PHP edits: You should never need to edit core files, all php edits must be handled via a plugin. If you cant figure out how to do it with a plugin, please start a topic in the forum and we will help you, we can add hook locations where needed in the core.
3 simple rules
Any template edits you make ensure its in a child template (admin edits automatically do this)
Any CSS edits should be made in skins/default/user.css
Any PHP edits should be handled via a plugin
For these examples we assume your working with default skin.
Template Edits:Login to your admin panel, hover over settings tab, click on skins and categories.
Click "Edit Child" and click the template you want to customize from the list on the left. This will make a copy of the template file in default/child/ that you can edit. Child templates are never overwritten during an update, this again allows your customizations to be preserved after an update. You should still compare the new templates to your child templates to ensure you are not missing any new tags added to the core.
CSS edits: if you open skins/default/user.css you can add any CSS rules you like to this file to override the default styles. You can also add your own custom classes and ID's to this file. user.css is never overwritten during upgrades so your customizations are safe in this file.
PHP edits: You should never need to edit core files, all php edits must be handled via a plugin. If you cant figure out how to do it with a plugin, please start a topic in the forum and we will help you, we can add hook locations where needed in the core.
Last edited:
