-
Notifications
You must be signed in to change notification settings - Fork 17
Theme Upgrade Proofing
When creating a theme for the first time you can duplicate an existing theme and rename it with a unique name. By creating a custom name (directory) for your theme it will ensure that it cannot be overwritten by the default themes accidentally when upgrading, preserving your design customizations.
Compartmentalize hacks by adding them within your custom theme(s). By extending (or replacing) core functions & functionality with custom hacks within your theme it will ensure these modified files are not overwritten when upgrading.
When creating custom data storage within the Helios Calendar database for your themes/hacks it is recommended to create new tables to store custom data. Modifying the core database schema can have unintended impact on the database upgrade script. By preserving the default schema, and supplementing it with custom tables, the upgrade script will be able to apply future updates in a uniform manner.
Events
- Adding Events
- Editing Events
- Recycling Events
- Deleting Events
- Pending Events
- Billboard Events
- Orphan Events
- Event Search
- Event Series
- Category Management
Locations
Administration
- Adding Admin Users
- Editing Admin Users
- Change Admin Password
- Manage Users
- Manage Database
- Reports
- Event Import
- Event Export
- Export Templates
Newsletters
- Newsletter Overview
- Sending Newsletters
- Newsletter Templates
- Compose Draft
- Create Newsletter
- Newsletter Queue
- Manage Subscribers
- Subscriber Groups
- Email Guildelines
Publishing
Customization
- Integration
- Weather/Map Links
- Calendar Digest
- Preferences
- API Settings
- API Registration
- Translation
- Localization
- Meta Settings & SEO
Themes
- Themes Overview
- Themes Settings
- Custom Theme Functions
- Creating Themes
- Creating Hacks
- Upgrade-proofing
API
Technical
- Setup
- Upgrading
- Upgrading from 1.x
- Server Requirements
- Browser Compatibility
- Search Engines & SEO
- CAPTCHA
About