Deprixa Pro — Integrated Courier & Logistics System · Development Guidelines
- 🔒 Always backup files and database before making any code changes.
- 🧱 Structure: Business logic lives in PHP entry points and helpers. Views are in views/. Shared config is in config/. Avoid modifying core helper files; use separate override files where possible.
- 🗄️ Database changes: New tables or columns should match the existing naming conventions and types. Test all migrations on a copy of the database before applying to production.
- 🔑 Roles & permissions: When adding new pages or actions, implement the same permission checks used throughout the system (check helpers/permissions.php or helpers/check_permission.php) so the menu and access stay consistent.
- 🎨 CSS overrides: Add custom styles in a separate CSS file loaded after the main stylesheet (e.g. assets/css/custom.css). This way your overrides survive theme updates.
- 🔄 Updates: When upgrading, compare your modified files with the new package using a diff tool. Re-apply your changes on top of the new code and retest all affected modules.
- 📝 JavaScript: Page-specific JS lives in dataJs/. Add new scripts there rather than modifying existing files.