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
* https://github.com/tinymce/tinymce-docs-4x/blob/develop/CONTRIBUTING.md#contributing-to-the-tinymce-developer-documentation[GitHub - Contributing to the TinyMCE developer documentation].
Copy file name to clipboardExpand all lines: modules/ROOT/pages/advanced/configuring-comments-callbacks.adoc
+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
@@ -9,7 +9,7 @@
9
9
[[introduction]]
10
10
== Introduction
11
11
12
-
*Callback mode* is the default mode for link:{baseurl}/plugins/comments/comments_2.0/[Comments 2.0]. In the callback mode, the user needs to configure storage to be able to save comments on the server. The Comments functions (create, reply, edit, delete comment, delete all conversations, and lookup) are configured differently depending upon the server-side storage configuration.
12
+
*Callback mode* is the default mode for link:{baseurl}/plugins/comments/comments_2.0.html[Comments 2.0]. In the callback mode, the user needs to configure storage to be able to save comments on the server. The Comments functions (create, reply, edit, delete comment, delete all conversations, and lookup) are configured differently depending upon the server-side storage configuration.
13
13
14
14
[[required-settings]]
15
15
=== Required settings
@@ -211,4 +211,4 @@ The done callback needs to take an object of the form:
211
211
}
212
212
----
213
213
214
-
For more information on Comments commercial feature, visit our link:{baseurl}/enterprise/tiny-comments/[Premium Features] page.
214
+
For more information on Comments commercial feature, visit our link:{baseurl}/enterprise/tiny-comments.html[Premium Features] page.
If you would like to contribute to TinyMCE's documentation, please see our link:../contributing-docs/[contrib page and style guide].
33
+
If you would like to contribute to TinyMCE's documentation, please see our link:{baseurl}/advanced/contributing-docs.html[contrib page and style guide].
Copy file name to clipboardExpand all lines: modules/ROOT/pages/advanced/creating-a-custom-button.adoc
+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
@@ -32,7 +32,7 @@ In fact, the `identifier` is the only required argument, but if you want to be
32
32
33
33
But let's do something more useful than merely alerting a message. Let's insert something into the editor - a current date, for example.
34
34
35
-
NOTE: TinyMCE already ships with *nice* link:{baseurl}/plugins/insertdatetime/[Insert date/time plugin] (it is hard to find a text editing feature that is not implemented in TinyMCE), but it does a whole lot of complimentary things - adds some commands and shortcuts, inserts *"Insert date/time"* menu, adds support for fancy date formats, i18n, and some more. We won't go into all of that in this tutorial and make our button much simpler. However, `insertdatetime` plugin is a good read if mentioned stuff is something that you would like to familiarise yourself with. Its source code can be found on https://github.com/tinymce/tinymce/blob/master/js/tinymce/plugins/insertdatetime/plugin.js[github].
35
+
NOTE: TinyMCE already ships with *nice* link:{baseurl}/plugins/insertdatetime.html[Insert date/time plugin] (it is hard to find a text editing feature that is not implemented in TinyMCE), but it does a whole lot of complimentary things - adds some commands and shortcuts, inserts *"Insert date/time"* menu, adds support for fancy date formats, i18n, and some more. We won't go into all of that in this tutorial and make our button much simpler. However, `insertdatetime` plugin is a good read if mentioned stuff is something that you would like to familiarise yourself with. Its source code can be found on https://github.com/tinymce/tinymce/blob/master/js/tinymce/plugins/insertdatetime/plugin.js[github].
36
36
37
37
For our purpose, we will use https://developer.mozilla.org/en-US/docs/Web/HTML/Element/time[`<time>`] tag. `<time>` tag should have an attribute `datetime` - valid date with an optional time string. And as https://developer.mozilla.org/en-US/docs/Web/HTML/Element/time[MDN] states:
38
38
@@ -156,7 +156,7 @@ Here's updated demo. Try to click inside and outside the date string:
156
156
157
157
NOTE: In reality, it would have been more practical to simply set `contenteditable` attribute to *false* on the `time` tag. But I wanted to demonstrate how you can toggle the button state, depending on various logical conditions.
158
158
159
-
By the way, notice how the code for our example gets bigger and bigger. It has almost reached the boundaries of simplicity already. This is the moment when you should ask yourself whether it's better to link:{baseurl}/advanced/creating-a-plugin/[bundle this feature as a plugin] instead.
159
+
By the way, notice how the code for our example gets bigger and bigger. It has almost reached the boundaries of simplicity already. This is the moment when you should ask yourself whether it's better to link:{baseurl}/advanced/creating-a-plugin.html[bundle this feature as a plugin] instead.
Creating plugins in TinyMCE is pretty simple - especially if you use the link:{baseurl}/advanced/yeoman-generator/[Yeoman generator]! - but if you would rather do it all by yourself, keep reading.
10
+
Creating plugins in TinyMCE is pretty simple - especially if you use the link:{baseurl}/advanced/yeoman-generator.html[Yeoman generator]! - but if you would rather do it all by yourself, keep reading.
11
11
12
12
This tutorial tries to outline some of the basic concepts of creating a plugin. For more details consult the API documentation and check the existing plugins we ship with the core.
13
13
@@ -127,7 +127,7 @@ tinymce.init({
127
127
== Exposing metadata
128
128
anchor:exposingmetadata[historical anchor]
129
129
130
-
You can expose metadata from your plugin by returning an object with the property `getMetadata` with a function that returns an object with a `name` and `url` property. This metadata will then be used by the link:{baseurl}/plugins/help/[Help Plugin] to show the correct name and link for your plugin in the Plugins installed tab. See the `test` plugin above for example.
130
+
You can expose metadata from your plugin by returning an object with the property `getMetadata` with a function that returns an object with a `name` and `url` property. This metadata will then be used by the link:{baseurl}/plugins/help.html[Help Plugin] to show the correct name and link for your plugin in the Plugins installed tab. See the `test` plugin above for example.
0 commit comments