Anonymous | Login | Signup for a new account | 2024-04-19 20:38 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
View Revisions: Issue #1153 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0001153: Minimizing In-Portal CORE | ||
Revision | 2011-12-23 11:36:54 by Dmitry | ||
Additional Information | ========== Info from 0000268: Code Cleanup in 5.2.x branch === 1. Somehow divide In-Portal into layers, that can be easily turned on/off. 2. Maybe modularize core itself, e.g. "form submissions", "permission system", "various logs", "visits", "site domains". 3. Maybe some parts (within the main module) can be downloaded separately. ============ Interesting code in WordPress and I got this idea: Have system-level events, that modules can hook to so it will be easier for us to from module. For example OnGetTheme event could retrieve theme_id from url and hook to it from SiteDomain module can override that theme with the one, that matches current site domain. |
||
Revision | 2011-11-01 12:28:36 by Dmitry | ||
Additional Information | Interesting code in WordPress and I got this idea: Have system-level events, that modules can hook to so it will be easier for us to from module. For example OnGetTheme event could retrieve theme_id from url and hook to it from SiteDomain module can override that theme with the one, that matches current site domain. |
||
Revision | 2011-11-01 12:27:00 by Dmitry | ||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |