You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/development/modernizing-existing-add-ons.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,21 +11,21 @@
11
11
12
12
13
13
14
-
The ExpressionEngine 7.2 release brough a new add-on developemnt approach, which generates the majority of the add-ons needed files and struture. It also bring additional organization to how add-ons are developed.
14
+
The ExpressionEngine 7.2 release brought a new add-on development approach, which generates the majority of the add-on's needed files and structure. It also brings additional organization to how add-ons are developed.
15
15
16
16
NOTE: These changes do NOT break existing add-ons. The old development methodologies will still work.
17
17
18
-
The idea of a plugin, module, extension, fieldtype, etc. no longer exist. Instead an add-on can have a template tag, or a field-type, or an extention.
18
+
The idea of a plugin, module, extension, fieldtype, etc. no longer exists. Instead, an add-on can have a template tag, a fieldtype, or an extension.
19
19
20
-
In order to harness the new add-on development methodology, you will have to do a few SMALL updates to your existing add-on's.
20
+
In order to harness the new add-on development methodology, you will have to do a few SMALL updates to your existing add-ons.
21
21
22
-
TIP: You don't have to migrate your add-on to the new development methodology. After making the following changes, you can leave your add-ons as is, and start new / additional development in the new method.
22
+
TIP: You don't have to migrate your add-on to the new development methodology. After making the following changes, you can leave your add-ons as is, and start new/additional development in the new method.
23
23
24
24
25
25
[TOC]
26
26
27
27
## Updating your mod.addon.php file
28
-
In order to use the new approach, you will have to have your mod file use and extend the module addon service
28
+
In order to use the new approach, you will have to have your mod file use and extend the module add-on service
29
29
30
30
31
31
```
@@ -37,7 +37,7 @@ class Addon extends Module
37
37
38
38
## Updating your mcp.addon.php file
39
39
40
-
In order to use the new approach, you will have to have your mcp file use and extend the Mcp addon service
40
+
In order to use the new approach, you will have to have your mcp file use and extend the Mcp add-on service
41
41
42
42
```
43
43
use ExpressionEngine\Service\Addon\Mcp;
@@ -47,7 +47,7 @@ class Addon_mcp extends Mcp
47
47
48
48
## Updating your ext.addon.php file
49
49
50
-
In order to use the new approach, you will have to have your mcp file use and extend the Extension addon service
50
+
In order to use the new approach, you will have to have your mcp file use and extend the Extension add-on service
51
51
52
52
```
53
53
use ExpressionEngine\Service\Addon\Extension;
@@ -57,12 +57,12 @@ class Addon_ext extends Extension
57
57
58
58
## Updating your upd.addon.php file
59
59
60
-
In order to use the new approach, you will have to have your mcp file use and extend the Instaler addon service
60
+
In order to use the new approach, you will have to have your mcp file use and extend the Installer add-on service
61
61
62
62
```
63
63
use ExpressionEngine\Service\Addon\Installer;
64
64
65
65
class Addon_upd extends Installer
66
66
```
67
67
## A Note on Plugins
68
-
If your add-on is currently a plugin and your looking to take advantage of the new add-on development methodologies, we recommend migrating your plugin methods (functions) to your mod file first. This can be done with a simple copy and paste.
68
+
If your add-on is currently a plugin and you are looking to take advantage of the new add-on development methodologies, we recommend migrating your plugin methods (functions) to your mod file first. This can be done with a simple copy and paste.
0 commit comments