https://github.com/dhtmlx/scheduler-wordpress
Wordpress plugin for the dhtmlxScheduler
https://github.com/dhtmlx/scheduler-wordpress
Last synced: 9 months ago
JSON representation
Wordpress plugin for the dhtmlxScheduler
- Host: GitHub
- URL: https://github.com/dhtmlx/scheduler-wordpress
- Owner: DHTMLX
- Created: 2012-12-18T11:05:31.000Z (about 13 years ago)
- Default Branch: master
- Last Pushed: 2012-12-19T13:34:57.000Z (about 13 years ago)
- Last Synced: 2025-04-09T06:51:12.365Z (10 months ago)
- Language: PHP
- Size: 2.22 MB
- Stars: 8
- Watchers: 7
- Forks: 3
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# dhtmlxScheduler Wordpress plugin
##Component structure
* codebase/ - scheduler codebase
* mce_scheduler/ - mce button to add event in wordpress post/page editor
* admin.php - initializing admin panel
* scheduler.php - plugin code
* scheduler_include.html - additional html/js/css code which is included at page before scheduler.init()
All scheduler logic is located in codebase.
It includes scheduler codebase, scheduler configurator, code generator.
There are 3 main points in code:
* initializing admin panel:
+ wordpress/admin.php
* generating scheduler code:
+ wordpress/scheduler.php (function scheduler_init())
* processing loading/saving requests:
+ codebase/dhtmlxSchedulerConfiguratorLoad.php
##Database structure
* events_rec - stores scheduler events
+ event\_id - event id
+ start\_date - event start date/time
+ end\_date - event end date/time
+ text - event text
+ rec\_type - event recurring logic
+ event\_pid - parent event (for editing one event from recurring series)
+ event\_length - event length (required for recurring events)
+ user - event creator/editor id
+ lat - event latitude (for map view)
+ lng - event longuitude (for map view)
* scheduler options are located in wordpress options table.
Here is a list of options:
+ scheduler\_xml - scheduler xml configuration. Is used to load settings in admin panel
+ scheduler\_php - parsed xml configuration and serialized into more useful form
+ scheduler\_php_version - version of the last php configuration
+ scheduler\_xml\_version - version of the last xml configuration
+ scheduler\_stable\_config - last stable configuration (is used for restoring scheduler configuration after config xml error)
##Codebase details
Core provides universal control panel, API for generating scheduler and events data-feed.
Logic of parsing settings may be found in codebase/dhtmlxSchedulerConfigurator.php.
For saving/parsing configuration is used the follow logic:
when user saves configuration it is saved into database.
At the same time scheduler\_xml\_version (have a look database structure) is increased.
When user opens scheduler then configurators compare scheduler\_xml\_version and scheduler\_php\_version.
If scheduler\_xml\_version if bigger than scheduler\_php\_version then it parses xml configuration and serialize it into php (scheduler\_php in database).
At the same time configurator updates scheduler_php_version to actual.
If scheduler\_xml\_version equals scheduler\_php\_version than xml is already parsed and serialized php configuration may be used.
Read more about dhtmlxScheduler Joomla! component in [documentation](https://github.com/DHTMLX/scheduler-wordpress/wiki/dhtmlxScheduler-for-Wordpress).