Merge tag 'vDX-733' into develop
Fixed links
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
## images_upload_base_path
|
||||
|
||||
This option lets you specify a `basepath` to prepend to URLs returned from the configured [`images_upload_url`](images-uploads-url.md) page.
|
||||
This option lets you specify a `basepath` to prepend to URLs returned from the configured [`images_upload_url`](#images_upload_url) page.
|
||||
|
||||
**Type:** `String`
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
## images_upload_credentials
|
||||
|
||||
|
||||
The **images_upload_credentials** option lets you specify if calls to the configured [`images_upload_url`](images-upload-url) should pass along credentials like cookies etc. cross domain.
|
||||
The **images_upload_credentials** option lets you specify if calls to the configured [`images_upload_url`](#images_upload_url) should pass along credentials like cookies etc. cross domain.
|
||||
|
||||
**Type:** `Boolean`
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ If you wish to use a language other than English, please follow these steps:
|
||||
|
||||
1. Download the language pack you wish to use [from here](https://www.tinymce.com/download/language-packages/).
|
||||
2. Unpack the language file into your `tinymce/langs` folder.
|
||||
3. Set the [`language`](/configure/localization/#language) option in your TinyMCE configuration to the language code in the list below (which you'll also find on the language pack [download page](https://www.tinymce.com/download/language-packages/).
|
||||
3. Set the [`language`]({{ site.baseurl }}/configure/localization/#language) option in your TinyMCE configuration to the language code in the list below (which you'll also find on the language pack [download page](https://www.tinymce.com/download/language-packages/).
|
||||
4. Confirm that the language has been set successfully by loading TinyMCE.
|
||||
|
||||
Please note, the language code you set in your TinyMCE configuration must match the filename of the language file. If the language file is not found, TinyMCE will not load.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
This option allows you to set the maximum height that a user can stretch the entire TinyMCE interface (by grabbing the dragable area in the bottom right of the editor interface) when using the modern theme.
|
||||
|
||||
> Note that this behavior is different than the [`autoresize`](/plugins/autoresize) plugin, which controls the resizing of the editable area only, not the entire editor.
|
||||
> Note that this behavior is different than the [`autoresize`]({{ site.baseurl }}/plugins/autoresize) plugin, which controls the resizing of the editable area only, not the entire editor.
|
||||
|
||||
**Type:** `Number`
|
||||
|
||||
|
||||
@@ -43,4 +43,4 @@ tinymce.init({
|
||||
});
|
||||
```
|
||||
|
||||
For more information on the differences between regular and inline editing modes please see this page [here]({{ site.baseurl }}/get-started/use-tinymce-inline/).
|
||||
For more information on the differences between regular and inline editing modes please see this page [here]({{ site.baseurl }}/general-configuration-guide/use-tinymce-inline/).
|
||||
|
||||
@@ -9,7 +9,7 @@ The format of the converter function is: `URLConverter(url, node, on_save)`, whe
|
||||
* on_save is always set to true.
|
||||
* name = the attribute name that is being set.
|
||||
|
||||
This function should return the converted URL as a string. This option is set to an internal TinyMCE function <editor>.[convertURL()]({{ site.baseurl }}/api/class/tinymce.editor/) by default. You may call this function from your extension in order to use the built-in convert options.
|
||||
This function should return the converted URL as a string. This option is set to an internal TinyMCE function <editor>.[convertURL()]({{ site.baseurl }}/api/tinymce/tinymce.editor/) by default. You may call this function from your extension in order to use the built-in convert options.
|
||||
|
||||
**Type:** `Javascript Function`
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ The new "modern" theme was introduced in 4.0. More themes will be added in the f
|
||||
|
||||
## Event handling
|
||||
|
||||
TinyMCE 4.0 has a new way of binding events. Instead of the old dispatcher method, it uses the more common "on" and "off" like for example jQuery. It also allows you to bind multiple events and cancel events using the more common preventDefault and stopPropagation. Check the [API documentation]({{ site.baseurl }}/api/class/tinymce.editor/) for a full list of events.
|
||||
TinyMCE 4.0 has a new way of binding events. Instead of the old dispatcher method, it uses the more common "on" and "off" like for example jQuery. It also allows you to bind multiple events and cancel events using the more common preventDefault and stopPropagation. Check the [API documentation]({{ site.baseurl }}/api/tinymce/tinymce.editor/) for a full list of events.
|
||||
|
||||
```js
|
||||
// Old event
|
||||
|
||||
+1
-1
@@ -9,6 +9,6 @@ keywords: example demo custom common standard normal typical
|
||||
|
||||
## Live example
|
||||
|
||||
In this example we highlight new features in our latest release, including the image caption option, media embeds and code snippets. For more information on the latest updates to TinyMCE, see the [changelog](/changelog).
|
||||
In this example we highlight new features in our latest release, including the image caption option, media embeds and code snippets. For more information on the latest updates to TinyMCE, see the [changelog]({{ site.baseurl }}/changelog).
|
||||
|
||||
{% include codepen.html id="gGRYKN" height="900" %}
|
||||
|
||||
@@ -15,7 +15,7 @@ Your have two deployment options. One is super easy with TinyMCE Cloud, the othe
|
||||
|
||||
## Link Checker Cloud Quick Setup
|
||||
|
||||
[TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/) makes setting up Link Checker a breeze. Simply include the `linkchecker` parameter in your `tinymce.init` and have our Cloud services do the work for you.
|
||||
[TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/) makes setting up Link Checker a breeze. Simply include the `linkchecker` parameter in your `tinymce.init` and have our Cloud services do the work for you.
|
||||
|
||||
## Link Checker Self-hosted Quick Setup
|
||||
|
||||
@@ -41,6 +41,6 @@ ephox {
|
||||
}
|
||||
```
|
||||
|
||||
You will also find more Self-hosted setup information on the [Link Checker plugin page](/plugins/linkchecker/).
|
||||
You will also find more Self-hosted setup information on the [Link Checker plugin page]({{ site.baseurl }}/plugins/linkchecker/).
|
||||
|
||||
> **Important note:** The Link Checker server currently does not support integration with IBM WebSphere Application Server.
|
||||
|
||||
@@ -15,7 +15,7 @@ Your have two deployment options. One is super easy with TinyMCE Cloud, the othe
|
||||
|
||||
## Enhanced Media Embed Cloud Quick Setup
|
||||
|
||||
[TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/) makes setting up Enhanced Media Embed a breeze. Simply include the `mediaembed` parameter in your `tinymce.init` and have our Cloud services do the work for you.
|
||||
[TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/) makes setting up Enhanced Media Embed a breeze. Simply include the `mediaembed` parameter in your `tinymce.init` and have our Cloud services do the work for you.
|
||||
|
||||
## Enhanced Media Embed Self-hosted Quick Setup
|
||||
|
||||
|
||||
@@ -113,10 +113,10 @@ The other option for developing a custom API endpoint is to return JSON in the [
|
||||
|
||||
#### HTTP response status codes
|
||||
|
||||
* HTTP 200 (OK): [`EphoxEmbedObj`]({{ site.baseurl }}/enterprise/check-links-and-embed-media/mediaembed-server-integration/#ephoxembedobj)
|
||||
* HTTP 400 (User Error): [`ErrorObj`]({{ site.baseurl }}/enterprise/check-links-and-embed-media/mediaembed-server-integration/#errorobj)
|
||||
* HTTP 503 (Upstream Error): [`ErrorObj`]({{ site.baseurl }}/enterprise/check-links-and-embed-media/mediaembed-server-integration/#errorobj)
|
||||
* HTTP 500 (Unexpected Error): [`ErrorObj`]({{ site.baseurl }}/enterprise/check-links-and-embed-media/mediaembed-server-integration/#errorobj)
|
||||
* HTTP 200 (OK): [`EphoxEmbedObj`]({{ site.baseurl }}/enterprise/embed-media/mediaembed-server-integration/#ephoxembedobj)
|
||||
* HTTP 400 (User Error): [`ErrorObj`]({{ site.baseurl }}/enterprise/embed-media/mediaembed-server-integration/#errorobj)
|
||||
* HTTP 503 (Upstream Error): [`ErrorObj`]({{ site.baseurl }}/enterprise/embed-media/mediaembed-server-integration/#errorobj)
|
||||
* HTTP 500 (Unexpected Error): [`ErrorObj`]({{ site.baseurl }}/enterprise/embed-media/mediaembed-server-integration/#errorobj)
|
||||
|
||||
#### JSON response objects
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ Before we move on to the table of format parameters below, we want to acknowledg
|
||||
| classes | Space-separated list of classes to apply the selected elements or the new inline/block element. |
|
||||
| styles | Name/value object with CSS style items to apply such as color and other attributes. |
|
||||
| attributes | Name/value object with attributes to apply to the selected elements or the new inline/block element. |
|
||||
| exact | Disables the [Style merging]({{ site.baseurl }}configure/content-formatting/#stylemerging) feature when used. `exact` is needed for some CSS inheritance issues such as text-decoration for underline/strikethrough. |
|
||||
| exact | Disables the [Style merging]({{ site.baseurl }}/configure/content-formatting/#stylemerging) feature when used. `exact` is needed for some CSS inheritance issues such as text-decoration for underline/strikethrough. |
|
||||
| wrapper | State that tells that the current format is a container format for block elements. For example a `div wrapper` or `blockquote`. |
|
||||
|
||||
### Example of usage of the formats option
|
||||
|
||||
@@ -96,7 +96,7 @@ tinymce.init({
|
||||
|
||||
### Q: Where are the advanced image options?
|
||||
|
||||
Use the [`Style Formats`](/configure/content-filtering/#style_formats) option instead, which is much more powerful.
|
||||
Use the [`Style Formats`]({{ site.baseurl }}/configure/content-filtering/#style_formats) option instead, which is much more powerful.
|
||||
|
||||
```js
|
||||
tinymce.init({
|
||||
|
||||
@@ -8,7 +8,7 @@ Nobody likes content with spelling errors. Our team at TinyMCE is motivated to h
|
||||
|
||||
## Browser-based spell checking
|
||||
|
||||
The first and easiest to implement option is to utilize the browser's native spell check functionality by assigning the [`browser_spellcheck`]({{ site.baseurl }}/configure/spelling/#browser_spellcheck) configuration option the value of `true`. Depending on the right click / context behavior you want, you *may* need to enable the [`contextmenu`]({{ site.baseurl }}/plugins/context-menu/) plugin.
|
||||
The first and easiest to implement option is to utilize the browser's native spell check functionality by assigning the [`browser_spellcheck`]({{ site.baseurl }}/configure/spelling/#browser_spellcheck) configuration option the value of `true`. Depending on the right click / context behavior you want, you *may* need to enable the [`contextmenu`]({{ site.baseurl }}/plugins/contextmenu/) plugin.
|
||||
|
||||
```js
|
||||
tinymce.init({
|
||||
|
||||
@@ -41,7 +41,7 @@ $ npm install --save @tinymce/tinymce-react
|
||||
|
||||
### 3.1 Loading TinyMCE
|
||||
#### Auto-loading from TinyMCE Cloud
|
||||
`@tinymce/tinymce-react` requires `tinymce` to be globally available to work, but to make it as easy as possible it will automatically load [TinyMCE Cloud](https://www.tinymce.com/docs/get-started-cloud/) if it can't find TinyMCE available when the component is mounting. To get rid of the `This domain is not registered...` warning, sign up for the cloud and enter the api key like this:
|
||||
`@tinymce/tinymce-react` requires `tinymce` to be globally available to work, but to make it as easy as possible it will automatically load [TinyMCE Cloud](https://www.tinymce.com/docs/cloud-deployment-guide/editor-and-features/) if it can't find TinyMCE available when the component is mounting. To get rid of the `This domain is not registered...` warning, sign up for the cloud and enter the api key like this:
|
||||
|
||||
```js
|
||||
<Editor apiKey='YOUR_API_KEY' init={% raw %}{{{% endraw %} /* your other settings */ {% raw %}}}{% endraw %} />
|
||||
@@ -58,7 +58,7 @@ So using the `dev` channel would look like this:
|
||||
<Editor apiKey='YOUR_API_KEY' cloudChannel='dev' init={% raw %}{{{% endraw %} /* your other settings */ {% raw %}}}{% endraw %} />
|
||||
```
|
||||
|
||||
For more info on the different channels see the [documentation](https://www.tinymce.com/docs/get-started-cloud/editor-plugin-version/#devtestingandstablereleases).
|
||||
For more info on the different channels see the [documentation](https://www.tinymce.com/docs/cloud-deployment-guide/editor-and-features/editor-plugin-version/#devtestingandstablereleases).
|
||||
|
||||
#### Loading TinyMCE by yourself
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ Image Tools (`imagetools`) plugin adds a contextual editing toolbar to the image
|
||||
*Warning:* This feature requires at least Internet Explorer 10, since it makes use of `HTML5 File API`.
|
||||
|
||||
## Cloud Installation
|
||||
The Image Tools plugin is provided with all subscriptions to [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/), including an automatically configured image proxy.
|
||||
The Image Tools plugin is provided with all subscriptions to [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/), including an automatically configured image proxy.
|
||||
Simply add `image` to the `toolbar` list and `image imagetools` to the `plugins` list.
|
||||
|
||||
##### Example
|
||||
@@ -53,7 +53,7 @@ An array of supported domains for the images (with CORS enabled on them) can be
|
||||
|
||||
**Note:** Each string in the array *must* be in the format of `mydomain.com`. Do not include protocols (`http://, https://`) or any trailing slashes in your domains.
|
||||
|
||||
**Note:** `imagetools_cors_hosts` is **not** required when enabling this plugin via [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/).
|
||||
**Note:** `imagetools_cors_hosts` is **not** required when enabling this plugin via [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/).
|
||||
|
||||
**Type:** `String[]`
|
||||
|
||||
@@ -92,7 +92,7 @@ Another way of getting images across domains is using local server-side proxy. P
|
||||
|
||||
[TinyMCE Enterprise](https://www.tinymce.com/pricing/) subscription also includes proxy service written in Java. Check [Install Server-side Components]({{ site.baseurl }}/enterprise/server/) guide for details.
|
||||
|
||||
**Note:** `imagetools_proxy` is **not** required when enabling this plugin via [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/)
|
||||
**Note:** `imagetools_proxy` is **not** required when enabling this plugin via [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/)
|
||||
|
||||
**Type:** `String`
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ The `linkchecker` does what it says – validates URLs, as you type them. UR
|
||||
|
||||
## Cloud Instructions
|
||||
|
||||
If you are using [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/), simply add `"linkchecker"` to your plugins list, and the service will be automatically configured.
|
||||
If you are using [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/), simply add `"linkchecker"` to your plugins list, and the service will be automatically configured.
|
||||
|
||||
##### Example
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ For the moment the **Enhanced Media Embed** plugin has to be used in conjunction
|
||||
2. Add the `mediaembed` plugin to the `plugins` list.
|
||||
|
||||
### Example Cloud Configuration
|
||||
The service URL is already configured with [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud).
|
||||
The service URL is already configured with [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/).
|
||||
Simply specify the `media` and `mediaembed` plugins, and optionally a `mediaembed_max_width`
|
||||
|
||||
```js
|
||||
@@ -48,7 +48,7 @@ The plugin can be used in two ways, either by simply entering a URL on an empty
|
||||
### `mediaembed_service_url`
|
||||
|
||||
This setting specifies the URL to the service that will handle your requests and return the embeddable snippets used by the **Media Embed** plugin. Please follow these [instructions]({{site.baseurl}}/enterprise/server/#step6setupeditorclientinstancestousetheserver-sidefunctionality) to configure the **WAR** file that you will get as a part of your [premium TinyMCE plugin](https://www.tinymce.com/pricing/) subscription.
|
||||
This option is not required for [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud).
|
||||
This option is not required for [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/).
|
||||
|
||||
### `mediaembed_max_width`
|
||||
|
||||
|
||||
+1
-1
@@ -168,7 +168,7 @@ tinymce.init({
|
||||
|
||||
This option enables you to configure the `valid_elements` specific to MS Office. Word produces a lot of junk HTML, so when users paste things from Word we do extra restrictive filtering on it to remove as much of this as possible. This option enables you to specify which elements and attributes you want to include when Word contents are intercepted.
|
||||
|
||||
>**Note:** To access this feature, you need to set the value of [paste_enable_default_filters]({{site.baseurl}}./#paste_enable_default_filters) to `"false"` in your configuration.
|
||||
>**Note:** To access this feature, you need to set the value of [paste_enable_default_filters]({{site.baseurl}}plugins/paste/#paste_enable_default_filters) to `"false"` in your configuration.
|
||||
|
||||
**Type:** `String`
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ https://www.tinymce.com/docs/advanced/handle-async-image-uploads/
|
||||
|
||||
|
||||
## Cloud Installation
|
||||
To enable the TinyMCE **PowerPaste** plugin with [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/):
|
||||
To enable the TinyMCE **PowerPaste** plugin with [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/):
|
||||
|
||||
1. If you are currently using the `paste` plugin provided with TinyMCE, disable it by removing it from the `plugins` list.
|
||||
2. Add `powerpaste` to the `plugins` list.
|
||||
|
||||
@@ -24,7 +24,7 @@ The following languages are supported:
|
||||
* Swedish
|
||||
|
||||
## Cloud Installation
|
||||
To enable the TinyMCE Enterprise Spellchecking plugin with [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud):
|
||||
To enable the TinyMCE Enterprise Spellchecking plugin with [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features):
|
||||
|
||||
1. If you are currently using the 'spellchecker' plugin provided with TinyMCE, disable it by removing it from the 'plugins' list.
|
||||
2. Add 'tinymcespellchecker' to the 'plugins' list.
|
||||
@@ -71,7 +71,7 @@ The TinyMCE Enterprise Spellchecking plugin activates automatically when users t
|
||||
### `spellchecker_rpc_url`
|
||||
This setting enables you to specify the URL to be used for the server side ephox-spelling service. Check the [server-side component installation guide]({{ site.baseurl }}/enterprise/server/) for details on how to setup your own spellchecker server.
|
||||
|
||||
**Note:** `spellchecker_rpc_url` is **not** required when enabling this plugin via [TinyMCE Cloud]({{ site.baseurl }}/get-started-cloud/)
|
||||
**Note:** `spellchecker_rpc_url` is **not** required when enabling this plugin via [TinyMCE Cloud]({{ site.baseurl }}/cloud-deployment-guide/editor-and-features/)
|
||||
|
||||
### `spellchecker_languages`
|
||||
This optional setting allows you to specify the languages that are available to the user, provided as a comma delimited string. The default value for this setting is:
|
||||
|
||||
+1
-1
@@ -83,7 +83,7 @@ tinymce.init({
|
||||
|
||||
### `toc_class`
|
||||
|
||||
With `toc_class` you can change the class name that gets assigned to the wrapper `div`. Please note that you will have to alter [Boilerplate Content CSS](({{ site.baseurl }}/advanced/boilerplate-content-css/)) accordingly.
|
||||
With `toc_class` you can change the class name that gets assigned to the wrapper `div`. Please note that you will have to alter [Boilerplate Content CSS]({{ site.baseurl }}/advanced/boilerplate-content-css/)) accordingly.
|
||||
|
||||
**Type:** `String`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user