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/cli/displaying-output.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Standard output can be created using `$this->output->outln`
8
8
9
9
### Displaying Error
10
10
11
-
Similar to the `info()` function, tou can use `$this->error()` for displaying errors that occure. The error call will die upon output, and no further code will be executed.
11
+
Similar to the `info()` function, you can use `$this->error()` for displaying errors that occurred. The error call will die upon output, and no further code will be executed.
12
12
13
13
### Formatting Output
14
14
@@ -53,4 +53,4 @@ dim dim in the current text and background colors
53
53
ul underline in the current text and background colors
54
54
blink blinking in the current text and background colors
55
55
reverse reverse the current text and background colors
Copy file name to clipboardExpand all lines: docs/control-panel/channels.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ NOTE: **Note:** We recommend using the default base URL variable `{base_url}` de
90
90
-**Channel** -- The full URL to the main page for this channel.
91
91
-**Comment form** -- The full URL to the "comments" page for this channel. The URL should include the Template Group and Template. For example: <https://example.com/channel/comments/>
92
92
-**Search results** -- The full URL where you would like search results from this channel to be pointed. The URL should include the Template Group and Template. For example: `{base_url}/index.php/channel/comments/`.
93
-
-**RSS feed** -- Thes URL where you can view the RSS feed for this channel. For example: <https://example.com/channel/rss_2.0>
93
+
-**RSS feed** -- The URL where you can view the RSS feed for this channel. For example: <https://example.com/channel/rss_2.0>
94
94
-**Preview URL** -- The template path, or route, to use for [Live Preview](control-panel/create.md#preview) in this Channel. You can use the variables `{entry_id}` and `{url_title}` which will be replaced with the entry's ID or URL Title when rendering your template. For example: `blog/entry/{url_title}`**Note:** If an Entry has a Page URI it will be used instead of the Preview URL for the channel.
95
95
-**Allow Preview** -- When set to yes, the entry preview will be allowed, don't forget to set the Preview URL too.
96
96
-**Generated title** -- When a new entry is created or previewed, this value will be inserted by default in the Title field. This is helpful if you wish every entry in a channel to have the titles follow a certain format. The automatic URL Title creating javascript for the Publish page will ignore this text during processing.
Copy file name to clipboardExpand all lines: docs/development/fieldtypes/enhanced.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,7 +114,7 @@ Custom fields can display their data inside the Entry Manager through 3 possible
114
114
115
115
## Entry cloning support
116
116
117
-
ExpressionEngine has the ability to [clone existing entries](/channels/entry_cloning.md) using the "Clone to New Entry" option on the entry editing page. Most fieldtypes do not need to do anything special to support this feature.
117
+
ExpressionEngine has the ability to [clone existing entries](/channels/entry_cloning.md) using the "Clone to New Entry" option on the entry editing page. Most fieldtypes do not need to do anything special to support this feature.
118
118
119
119
However, if the fieldtype you are developing saves data to its own database table, you might need to tell it to save the rows as a submission for the new entry and not for the existing one.
120
120
@@ -223,7 +223,7 @@ There are 3 available methods, and you are required to implement `evaluate` at t
Evaluates the rule by comparing the field value (`$fieldValue`) with the `$expectedValue` as entered in the conditional field settings.
226
+
Evaluates the rule by comparing the field value (`$fieldValue`) with the `$expectedValue` as entered in the conditional field settings.
227
227
`$fieldSettings` is available as array of field settings.
228
228
229
229
#### `getLanguageKey()`
@@ -248,23 +248,23 @@ To parse both cases correctly, please use the `ee()->file_field->parse_string()`
248
248
ee()->load->library('file_field');
249
249
$data = ee()->file_field->parse_string($data);
250
250
251
-
If the fieldtype is using custom JavaScript for manipulating the files, be sure to make the code aware of the [`EE.fileManagerCompatibilityMode`](development/control-panel-js/globals.md#filemanagercompatibilitymode) variable.
251
+
If the fieldtype is using custom JavaScript for manipulating the files, be sure to make the code aware of the [`EE.fileManagerCompatibilityMode`](development/control-panel-js/globals.md#filemanagercompatibilitymode) variable.
252
252
253
253
## Implementing Filepicker for Rich Text Editor
254
254
255
255
If your add-on is operating as File Manager, you might want to make it available as file picker for RTE fields.
256
256
257
257
In order to achieve that, create file prefixed with `rtefb.` in add-on's main directory, e.g. `rtefb.my_addon.php`. You can refer to the file in Filepicker add-on as an example.
258
258
259
-
The file's class needs to implement `ExpressionEngine\Library\Rte\RteFilebrowserInterface`. The easiest way to achive that is to extend `ExpressionEngine\Library\Rte\AbstractRteFilebrowser` abstract class and add code only for the functions that work differently from
259
+
The file's class needs to implement `ExpressionEngine\Library\Rte\RteFilebrowserInterface`. The easiest way to achieve that is to extend `ExpressionEngine\Library\Rte\AbstractRteFilebrowser` abstract class and add code only for the functions that work differently from
260
260
261
261
## Working with Front-End Editing
262
262
263
263
Most fieldtypes will work with [Front-end content management](/advanced-usage/front-end/frontend.md) out-of-the-box.
264
264
265
265
However there are some parameters that can be set in `ft.` to improve integration.
Copy file name to clipboardExpand all lines: docs/general/gdpr.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Add-ons may also have consent requests, and you can also make any Consent Reques
43
43
44
44
## Records, Auditing
45
45
46
-
ExpressionEngine records an audit log of all consents granted or withdrawn by a user. This is maintained indefinitely. If you ever need to prove or report an individual's granting or withdrawl of consent, just visit your [Consent Logs](control-panel/system-logs.md#consent-logs).
46
+
ExpressionEngine records an audit log of all consents granted or withdrawn by a user. This is maintained indefinitely. If you ever need to prove or report an individual's granting or withdrawal of consent, just visit your [Consent Logs](control-panel/system-logs.md#consent-logs).
0 commit comments