WordPress.org

New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Development Readme (trunk): English (New Zealand)

1 2 3 16
Filter ↓ Sort ↓ All (265) Untranslated (27) Waiting (0) Fuzzy (0) Warnings (0)
Prio Original string Translation
The visual editor widget for WordPress. The visual editor widget for WordPress. Details
The visual editor widget for WordPress.
Comment

Short description.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
high
Black Studio TinyMCE Widget Black Studio TinyMCE Widget Details
Black Studio TinyMCE Widget
Comment

Plugin name.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
high
This plugin gives you the ability to use the WordPress visual editor (TinyMCE) in widgets as you do in posts and pages, but it doesn't affect the editor behavior itself or its functionalities. If you are looking for additional editor features, take a look at plugins like <a href="https://wordpress.org/plugins/wp-edit/">WP Edit</a>, <a href="https://wordpress.org/plugins/tinymce-advanced/">TinyMCE Advanced</a> or any other feature specific plugin you may need. Any additional TinyMCE plugin written following WordPress guidelines should work fine with Black Studio TinyMCE Widget. This plugin gives you the ability to use the WordPress visual editor (TinyMCE) in widgets as you do in posts and pages, but it doesn't affect the editor behaviour itself or its functionalities. If you are looking for additional editor features, take a look at plugins like <a href="https://en-nz.wordpress.org/plugins/wp-edit/">WP Edit</a>, <a href="https://en-nz.wordpress.org/plugins/tinymce-advanced/">TinyMCE Advanced</a> or any other feature specific plugin you may need. Any additional TinyMCE plugin written following WordPress guidelines should work fine with Black Studio TinyMCE Widget. Details
This plugin gives you the ability to use the WordPress visual editor (TinyMCE) in widgets as you do in posts and pages, but it doesn't affect the editor behavior itself or its functionalities. If you are looking for additional editor features, take a look at plugins like <a href="https://wordpress.org/plugins/wp-edit/">WP Edit</a>, <a href="https://wordpress.org/plugins/tinymce-advanced/">TinyMCE Advanced</a> or any other feature specific plugin you may need. Any additional TinyMCE plugin written following WordPress guidelines should work fine with Black Studio TinyMCE Widget.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 23:05:15 GMT
Translated by:
webaware
Priority of the original:
normal
Support for Customizer with live preview and quick edit Support for Customiser with live preview and quick edit Details
Support for Customizer with live preview and quick edit
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 23:04:15 GMT
Translated by:
webaware
Priority of the original:
normal
<a href="https://wpml.org">WPML</a> is the leading commercial plugin for WordPress multi-language sites. If you're using WPML v3.8 or newer and you need to translate a widget, we recommend to create a separate widget for each language of your site and assign the language to each widget accordingly using the selector "Display on language" provided by WPML. This way you will be able to work with the visual editor also for translations. For older versions of WPML (up to 3.7.x), we recommend to install the 3rd party <a href="https://wordpress.org/plugins/wpml-widgets/">WPML Widgets</a> plugin, which provides the same feature described above, that was not available natively on WPML. In the past, we also suggested to translate the widgets using the official WPML String Translation plugin, but this method is now deprecated as it was not very friendly due to the inability of using the visual editor for translations. If you were using WPML String Translation, we recommend to switch to the aforementioned translation method and remove the entries in WPML String Translation list after you moved them to be real widgets. Starting from version 2.6.0 of Black Studio TinyMCE Widget, a warning will be displayed if any deprecated translation is detected. <a href="https://wpml.org">WPML</a> is the leading commercial plugin for WordPress multi-language sites. If you're using WPML v3.8 or newer and you need to translate a widget, we recommend to create a separate widget for each language of your site and assign the language to each widget accordingly using the selector "Display on language" provided by WPML. This way you will be able to work with the visual editor also for translations. For older versions of WPML (up to 3.7.x), we recommend to install the 3rd party <a href="https://wordpress.org/plugins/wpml-widgets/">WPML Widgets</a> plugin, which provides the same feature described above, that was not available natively on WPML. In the past, we also suggested to translate the widgets using the official WPML String Translation plugin, but this method is now deprecated as it was not very friendly due to the inability of using the visual editor for translations. If you were using WPML String Translation, we recommend to switch to the aforementioned translation method and remove the entries in WPML String Translation list after you moved them to be real widgets. Starting from version 2.6.0 of Black Studio TinyMCE Widget, a warning will be displayed if any deprecated translation is detected. Details
<a href="https://wpml.org">WPML</a> is the leading commercial plugin for WordPress multi-language sites. If you're using WPML v3.8 or newer and you need to translate a widget, we recommend to create a separate widget for each language of your site and assign the language to each widget accordingly using the selector "Display on language" provided by WPML. This way you will be able to work with the visual editor also for translations. For older versions of WPML (up to 3.7.x), we recommend to install the 3rd party <a href="https://wordpress.org/plugins/wpml-widgets/">WPML Widgets</a> plugin, which provides the same feature described above, that was not available natively on WPML. In the past, we also suggested to translate the widgets using the official WPML String Translation plugin, but this method is now deprecated as it was not very friendly due to the inability of using the visual editor for translations. If you were using WPML String Translation, we recommend to switch to the aforementioned translation method and remove the entries in WPML String Translation list after you moved them to be real widgets. Starting from version 2.6.0 of Black Studio TinyMCE Widget, a warning will be displayed if any deprecated translation is detected.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
The widgets data are stored in serialized format inside a record in the <code>wp_options</code> table having <code>option_name</code> = <code>'widget_black-studio-tinymce'</code>. Widget data storage is handled by WordPress and not directly by the plugin. The widgets data are intentionally kept in the database upon plugin deactivation/deletion to avoid content loss. Additionally, the plugin may save some user preferences in the <code>wp_usermeta</code> table, in particular, the records having s key with the prefix <code>_bstw</code>. If you want to totally remove the plugin including its data, just uninstall it and then remove the above records from the database. You may use the following SQL queries for removal (Note: adjust table prefix according to your database settings): The widgets data are stored in serialised format inside a record in the <code>wp_options</code> table having <code>option_name</code> = <code>'widget_black-studio-tinymce'</code>. Widget data storage is handled by WordPress and not directly by the plugin. The widgets data are intentionally kept in the database upon plugin deactivation/deletion to avoid content loss. Additionally, the plugin may save some user preferences in the <code>wp_usermeta</code> table, in particular, the records having a key with the prefix <code>_bstw</code>. If you want to totally remove the plugin including its data, just uninstall it and then remove the above records from the database. You may use the following SQL queries for removal (Note: adjust table prefix according to your database settings): Details
The widgets data are stored in serialized format inside a record in the <code>wp_options</code> table having <code>option_name</code> = <code>'widget_black-studio-tinymce'</code>. Widget data storage is handled by WordPress and not directly by the plugin. The widgets data are intentionally kept in the database upon plugin deactivation/deletion to avoid content loss. Additionally, the plugin may save some user preferences in the <code>wp_usermeta</code> table, in particular, the records having s key with the prefix <code>_bstw</code>. If you want to totally remove the plugin including its data, just uninstall it and then remove the above records from the database. You may use the following SQL queries for removal (Note: adjust table prefix according to your database settings):
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
WordPress has a nice <a href="https://codex.wordpress.org/Embeds">autoembed feature</a> that allows you to embed videos and other stuff in an easy way, by just putting the URL in the content area. This is also possible for widgets created with this plugin. If you are using a version of WordPress prior to 4.0 or a version of Black Studio TinyMCE Widget prior to 2.0, for best results it is recommended to put the URL inside an <code>[embed]</code> shortcode. Example: [embed]https://www.youtube.com/watch?v=XXXXXXXXXXX[/embed] Ensure that the URL has not a hyperlink. Alternatively, if you don't want to use <code>[embed]</code> shortcode, ensure that the URL is not surrounded by a <code>&lt;p&gt;</code> tag. WordPress has a nice <a href="https://codex.wordpress.org/Embeds">autoembed feature</a> that allows you to embed videos and other stuff in an easy way, by just putting the URL in the content area. This is also possible for widgets created with this plugin. If you are using a version of WordPress prior to 4.0 or a version of Black Studio TinyMCE Widget prior to 2.0, for best results it is recommended to put the URL inside an <code>[embed]</code> shortcode. Example: [embed]https://www.youtube.com/watch?v=XXXXXXXXXXX[/embed] Ensure that the URL has not a hyperlink. Alternatively, if you don't want to use <code>[embed]</code> shortcode, ensure that the URL is not surrounded by a <code>&lt;p&gt;</code> tag. Details
WordPress has a nice <a href="https://codex.wordpress.org/Embeds">autoembed feature</a> that allows you to embed videos and other stuff in an easy way, by just putting the URL in the content area. This is also possible for widgets created with this plugin. If you are using a version of WordPress prior to 4.0 or a version of Black Studio TinyMCE Widget prior to 2.0, for best results it is recommended to put the URL inside an <code>[embed]</code> shortcode. Example: [embed]https://www.youtube.com/watch?v=XXXXXXXXXXX[/embed] Ensure that the URL has not a hyperlink. Alternatively, if you don't want to use <code>[embed]</code> shortcode, ensure that the URL is not surrounded by a <code>&lt;p&gt;</code> tag.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
Compatible with 3rd party TinyMCE customization plugins (TinyMCE Advanced, WP Edit, ...) Compatible with 3rd party TinyMCE customisation plugins (TinyMCE Advanced, WP Edit, ...) Details
Compatible with 3rd party TinyMCE customization plugins (TinyMCE Advanced, WP Edit, ...)
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
Full featured TinyMCE Visual Editor (the same you have for pages and posts) Full featured TinyMCE Visual Editor (the same you have for pages and posts) Details
Full featured TinyMCE Visual Editor (the same you have for pages and posts)
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
You may alter widget title and text via code using the <code>widget_title</code> and <code>widget_text</code> filter hooks (see <a href="https://codex.wordpress.org/Plugin_API/Filter_Reference#Widgets">Codex</a> for details). The plugin also internally uses <code>widget_text</code> filter to apply specific features: You may alter widget title and text via code using the <code>widget_title</code> and <code>widget_text</code> filter hooks (see <a href="https://codex.wordpress.org/Plugin_API/Filter_Reference#Widgets">Codex</a> for details). The plugin also internally uses <code>widget_text</code> filter to apply specific features: Details
You may alter widget title and text via code using the <code>widget_title</code> and <code>widget_text</code> filter hooks (see <a href="https://codex.wordpress.org/Plugin_API/Filter_Reference#Widgets">Codex</a> for details). The plugin also internally uses <code>widget_text</code> filter to apply specific features:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
The appearance of widgets in the frontend depends on both CSS and HTML. This plugin does not insert any additional CSS to your website frontend, so if you need to customize the styling you'll have to do at theme level, or you have to insert explicitly insert <code>&lt;style&gt;</code> in your widget using the Text / HTML mode (this option is not recommended though). As for the HTML, most of the markup is controlled by WordPress and by the theme. The HTML output of a widget includes the following parts: The appearance of widgets in the front end depends on both CSS and HTML. This plugin does not insert any additional CSS to your website front end, so if you need to customise the styling you'll have to do at theme level, or you have to insert explicitly insert <code>&lt;style&gt;</code> in your widget using the Text / HTML mode (this option is not recommended though). As for the HTML, most of the markup is controlled by WordPress and by the theme. The HTML output of a widget includes the following parts: Details
The appearance of widgets in the frontend depends on both CSS and HTML. This plugin does not insert any additional CSS to your website frontend, so if you need to customize the styling you'll have to do at theme level, or you have to insert explicitly insert <code>&lt;style&gt;</code> in your widget using the Text / HTML mode (this option is not recommended though). As for the HTML, most of the markup is controlled by WordPress and by the theme. The HTML output of a widget includes the following parts:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 23:04:30 GMT
Translated by:
webaware
Priority of the original:
normal
<a href="https://www.blackstudio.it/en/">Author's web site</a> <a href="https://www.blackstudio.it/en/">Author's web site</a> Details
<a href="https://www.blackstudio.it/en/">Author's web site</a>
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
If for any reason you need to remove the filters above, you may use the following code snippet (or a custom version of it): If for any reason you need to remove the filters above, you may use the following code snippet (or a custom version of it): Details
If for any reason you need to remove the filters above, you may use the following code snippet (or a custom version of it):
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
There's also an additional hook, that you may use to specify to not display widgets if their content is empty: There's also an additional hook that you may use to specify to not display widgets if their content is empty: Details
There's also an additional hook, that you may use to specify to not display widgets if their content is empty:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
Example 2: Totally remove markup for <code>[before_text]</code> and <code>[after_text]</code> Example 2: Totally remove markup for <code>[before_text]</code> and <code>[after_text]</code> Details
Example 2: Totally remove markup for <code>[before_text]</code> and <code>[after_text]</code>
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
current
Date added:
2019-02-15 22:58:50 GMT
Translated by:
webaware
Priority of the original:
normal
1 2 3 16
Legend:
Current
Waiting
Fuzzy
Old
With Warnings

Export as

Skip to toolbar