mirror of
https://github.com/e107inc/e107.git
synced 2025-08-07 15:16:30 +02:00
Updated Preparing your v1.x plugin(s) for v2.x (markdown)
@@ -2,11 +2,21 @@ Plugins developed for v1.x of e107 will continue to work on v2.x.
|
||||
However, to get the most out of v2.x, we suggest the following changes be made to bring your plugin up to the new v2.x standards.
|
||||
|
||||
## Front-end
|
||||
### CSS
|
||||
e107 v2.x follows the [bootstrap standard](http://twitter.github.com/bootstrap/base-css.html) for css.
|
||||
As a quick reference:
|
||||
|
||||
**class='button'** should become **class='btn button'**
|
||||
**<table class='fborder'** should become **<table class='table fborder'**
|
||||
### Templates
|
||||
e107 v2.x uses a new template loading system.
|
||||
Plugin templates should be stored in **e107_plugins/yourplugin/templates/** by default.
|
||||
The template file should contain a variable with the same name as your template file.
|
||||
|
||||
eg. If your file is called **myplugin_template.php** , within this file you might see something like this:
|
||||
|
||||
$MYPLUGIN_TEMPLATE['start'] = "<div>";
|
||||
$MYPLUGIN_TEMPLATE['end'] = "</div>";
|
||||
|
||||
## Admin-Area
|
||||
The admin area of v2.x uses a special new admin handler (admin-ui).
|
||||
@@ -19,7 +29,7 @@ The advantages of using the new admin system are numerous - including, but not l
|
||||
* Consistent interface with the rest of admin
|
||||
* Users can select which fields from your db table they wish to view - based on your predefined list.
|
||||
* Media-Manager is integrated into the system.
|
||||
* Easily add drag and drop sorting/re-odering to your plugin.
|
||||
* Easily add drag and drop sorting/re-ordering to your plugin.
|
||||
* Easily add batch delete, copy, featurebox creation, sitelink creation, userclass modification, etc. etc.
|
||||
* Easily add inline editing to your data.
|
||||
* Easily add tabs to keep your plugin's admin-area well organized.
|
||||
|
Reference in New Issue
Block a user