How to remove section from TinyMCE link plugin - tinymce

In my app I using tinymce plugin for adding some files from local machine - link plugin. And it works great, but, there is one section - target, that I want to hide from users.
Because I'm just using '_blank' as default and type 'none' make some troubles.
In documentation I can't find option for hide this section. So I try to hide this by css. Unfortunately id and classes are dynamic, so it was bad idea with css 'display:none'.
It's possible to hide this section somehow?

You can remove the target list altogether by placing this in your TinyMCE configuration:
target_list: false
That is documented here: https://www.tinymce.com/docs/plugins/link/#target_list
To disable the option dialog set target_list to false

Related

How to set up a TypoScript Playground in Typo 3?

How can one play around with TypoScript code shown in documentations about TypoScript?
Tested with a local Typo3 test instance, Typo3 version 9.5.5, Official Introduction Package installed.
In the backend, create a new page in the tree. Rightclick -> enable it (the red overlay should disappear). Make sure it is selected in the tree.
Click on the blue Template button on the left. Usually it will show you the blue No Template message.
Make sure on the top Info/Modify is selected from the drop down.
Click the gray + (New record) button under the drop down.
On the bottom, click Edit the whole template record.
Optionally give it a speaking template and website title, like 'Playaround' and 'Play Around'.
Optionally, under tab Options -> Clear, select Constants and Setup - this will clear everything this Template has inherited from parent templates, but will also disable the debug infos at the bottom of the frontend for this page (if you have installed the Official Introduction Package).
Under the tab General -> text entry Setup, enter the following TypoScript:
page = PAGE
page.10 = TEXT
page.10.value = Hello World
press the Save and then the View button.
A new tab opens, showing you the frontend for your page, printing the text 'Hello World'.
Now you can play around with the code examples given in eg. the TypoScript Reference.
Funnily enough, I just found out that Typoscript is by definition not a programming language, but a configuration description. That's why Typo3 is needed as a substructure for this, I think. There seem to be online demos of Typo3 on the net, but I don't know whether they are up to date and whether you can test TypoScript there. Therefore access local containers / installations as suggested. Or if the possibility exists a dev subdomain.

Update Link Plugin in RTE Touch UI

I am looking for overriding the features of Link plugin in RTE, Touch UI. Basic feature I want to override root path, that by default is "/content/mysite/en" to "/content".
Its always points to "Website" . I want to select document from DAM
Other is I want to disable the auto-select feature of modify-link option.
Do someone have the idea to achieve this in TOUCH UI. In Classic i can do via changing LinkDialog.js but in Touch UI which will the file I need to change.
Thanks
You are looking for Links plugin in RTE for touch UI. There is a inplace editing plugin for specific purpose
And enabling/disabling features is as simple as what plugins are we adding under the edit config. Hope this helps.
You are probably looking for the links plugin, you can find it here: /libs/cq/ui/rte/core/plugins/LinkPlugin.js editing that is not recommended, you might want to create a new plugin that overrides this one and add the root directory you want.

not able to register two plugins of touch-ui rte dialog

I am using the steps given in the URL to make a color-picker rte plugin
http://experience-aem.blogspot.in/2015/01/aem-6-sp1-touchui-richtext-editor-color-picker-plugin.html
and at the same time I am making another custom rte plugin to do some text modulation.
But only one of them is working using rte.coralui2 as categories.
and both icons are coming at the same location.
If I disable one js then another is working.
I have registered the plugin with different name and I have also used different variables.
I am not able to make the rte plugin button at different location.
Please suggest the possible solution.
it's possible you are overlaying rather than extending the rte.coralui2 category. I suspect your custom clientLibs are competing with each other and only one is available.
It seems like you are using the same steps provided in the blogpost for creating both the plugins and while doing that, you are using the below code twice with different icons :
if(items.indexOf(ExperienceAEM.TCP_UI_SETTING) == -1){
items.splice(3, 0, ExperienceAEM.TCP_UI_SETTING);
}
So, maybe, the icons are being added at the same place and only one of them is shown.
You should create ExperienceAEM.CuiToolbarBuilder Class only once and add both icons inside that class

TinyMCE Remove Advanced tab from Tables dialog

I dont want to see the advanced tab on the tables dialog, and I dont want to remove it from the source in case its overwritten with updates.
Note: not Wordpress.
Any suggestions?
In TinyMCE v4, there are three plugin options: table_advtab, table_row_advtab and table_cell_advtab, that specify whether the Advanced Tab is enabled on the Table Properties, Row Properties and Cell Properties dialogs respectively.
So, if you want to hide the Advanced Tab for all table properties, you would set all of these options to false like this:
tinymce.init({
table_advtab: false,
table_row_advtab: false,
table_cell_advtab: false
});
Reference for these options can be found here:
https://www.tinymce.com/docs/plugins/table/#table_advtab
I have to tell you, that this is not possible. There are several settings concerning the table plugin, but not the one you are looking for.

TinyMCE editor disable

How can I disable tinyMCE?
I'm not trying to make tinyMCE not exist, just trying to disable the field temporarily using PrototypeJS's Form.disable.
Is there a particular way to mark a field disabled for editing?
One option is to use the plugin 'noneditable'
Or you could investigate the 'mode: exact' setting and only setting it on the exact id of the form field you want to control.
Your use case isn't really clear, so hope the above tips work.