RTE still clutters any link with title="Opens external link in new window" and worse, title="Opens internal link in current window".
I've tried removing it with
RTE.classesAnchor.externalLinkInNewWindow.titleText >
RTE.classesAnchor.internalLinkInCurrentWindow.titleText >
in page TSconfig, but no luck. Actually, I'm not even sure if this has to go into TSConfig or TS.
How can I disable this legacy feature?
PS I do still use
config.extTarget = _blank
but if it's really necessary, I can turn it off
To get rid of these texts, right of the beginning of a project (before content is filled in) use this PageTS-Config:
## get rid of "Opens link in ..."
RTE.classesAnchor.externalLink.titleText >
RTE.classesAnchor.externalLinkInNewWindow.titleText >
RTE.classesAnchor.internalLink.titleText >
RTE.classesAnchor.internalLinkInNewWindow.titleText >
RTE.classesAnchor.download.titleText >
RTE.classesAnchor.mail.titleText >
To look for the right names, go into the Module "Info", select a page from the page tree, click "Page TS Config" on the Dropdown-Select on the Top, and then "RTE." on the following Dropdown-Select.
This will remove all title attributes from links when saving:
RTE.default.proc.entryHTMLparser_db.tags.a.fixAttrib.title.unset = 1
Related
Since powermail 6.0. it's possible to add a link in a checkbox label (for GDPR) as per the docu:
https://docs.typo3.org/typo3cms/extensions/powermail/ForAdministrators/Privacy/Index.html#add-a-link-in-a-checkbox-label.
It says:
Just use an option in your FlexForm like (with an example link to page 123 where the privacy terms are located):
I accept the <f:link.page pageUid="123">privacy terms</f:link.page> | privacy terms accepted
After that you have to enable html in labels (this feature is turned off for security reasons). Example TypoScript constants:
plugin.tx_powermail.settings.misc.htmlForLabels = 1
... yet it also says that '(this feature is turned off for security reasons)'.
What other options are there to accomplish this? (with no security loss?)
We add a normal content element with the link above the checkbox. For example to accept the terms and conditions. Then the content element is included in the form. See https://docs.typo3.org/typo3cms/extensions/powermail/ForEditors/AddANewForm/FieldContentElement/Index.html
You can enable it in:
Template - > Constant Editor - > Powermail_Aditional - > Allow html in html fields/ Allow html in field labels
Then you can use HTML-Code. Or better:
<f:link.page pageUid="123">Privacy Policy</f:link.page>
1) The solution with the content element is a good thing - that should also be described
2) It's wrong that powermail version 6.0 is needed to disable the IP-storing. This feature is available for years now but 6.0 turns it off by default
3) If you trust your editors or if you already allow your editors to add content elements of type HTML it's really also no problem to allow HTML in powermail field labels for your editors
Maybe I should update the privacy documenation to clearify this points
This solution appears again and again at the top of Google. But the name is edit!
here for the new Powermail Version:
plugin {
tx_powermail {
settings {
misc {
htmlForHtmlFields = 1
htmlForLabels = 1
}
}
}
}
You can set link in checkbox lable or title like,
I accept the privacy terms
in powermail/Resources/Private/Partials/Form/Field/Check.html
Change code
<vh:string.RawAndRemoveXss>{setting.label}</vh:string.RawAndRemoveXss>
to
<f:format.raw>{setting.label}</f:format.raw>
I did what it said here: Extbase and Fluid Autocompletion
In NetBeans right-click your Extension project and choose Properties
in the opened context menu to edit the project properties. Select the
category PHP Include Path and use Add Folder... to add the directories
of Extbase and Fluid.
So I added the Fluid and Extbase Folders which I previously copied onto my computer from the Server at /var/www/typo3_src/typo3_src-6.2.25/typo3/sysext:
but it didn't work - here's my Project:
And here is fluid stuff that the editor still doesn't recognize:
What am I doing or thinking wrong?
Found info here, works for me:
It's an old topic but I have a trick so that you can add Auto-complete
function for fluid, vhs, flux.
First of all, download the XSD schema files from here :
https://fluidtypo3.org/viewhelpers/fluid/master.html put them
somewhere locally.
Next step, in Netbeans, go to menu Tools > DTD and XML Schemas, add
your 3 DTD in user catalog :
Flux : Public ID = http://typo3.org/ns/FluidTYPO3/Flux/ViewHelpers URI
= path to your flux XDS file
Fluid : Public ID = http://typo3.org/ns/TYPO3/Fluid/ViewHelpers URI =
path to your fluid XDS file
Vhs : Public ID = http://typo3.org/ns/FluidTYPO3/Vhs/ViewHelpers URI =
path to your flux VHS file
Next, in project properties, go to 'testing' menu and add the folder
where you stored your DTD.
Now, in your Project > Test Files, add a new XML Document and choose
"XML Schema-Constrained Document" on next step, click the button
'Browse' and By File > Your Project > Test Files and select import for
all the xsd schema files.
Then, change the prefix f for fluid, flux for flux and vhs for vhs
choose fluid as primary and finish.
A file is created with this content :
And into the section <f:alias>, you have the auto-completion for
fluid, vhs and flux.
<f:alias
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns:f='http://typo3.org/ns/TYPO3/Fluid/ViewHelpers'
xmlns:vhs='http://typo3.org/ns/FluidTYPO3/Vhs/ViewHelpers'
xmlns:flux='http://typo3.org/ns/FluidTYPO3/Flux/ViewHelpers'
xsi:schemaLocation='http://typo3.org/ns/TYPO3/Fluid/ViewHelpers file:/home/florian/Documents/Docs/Netbeans/Autocomplete%20Fluid/Schemas/Fluid.xsd
http://typo3.org/ns/FluidTYPO3/Vhs/ViewHelpers file:/home/florian/Documents/Docs/Netbeans/Autocomplete%20Fluid/Schemas/Vhs.xsd
http://typo3.org/ns/FluidTYPO3/Flux/ViewHelpers file:/home/florian/Documents/Docs/Netbeans/Autocomplete%20Fluid/Schemas/Flux.xsd'>
Auto-completion here
</f:alias>
http://netbeans-org.1045718.n5.nabble.com/Schemas-for-code-completion-with-xsd-tt5752294.html#none
take files from https://fluidtypo3.org/schemas/
Some more info Use Netbeans to Create Sample XML from XSD
From a project that contains the .xsd:
Click New File on the tool bar or File > New File from the menu
Choose XML > XML Document
Name your file, click next
Choose XML Schema-Constrained Document, click next
Click the Browse button and use By File to navigate to the .xsd
Click the Import check box beside the file name, click next
Review the options available and click Finish to generate
You can use more than one .xsd file to generate the .xml. In this case it will use whichever .xsd file you choose as Primary to resolve any conflicts.
Shortly, i needed to help a good friend, to move her complete typo3 install to another provider.
There was no chance in getting help from the developer at all.
I exported and imported the tables
downloaded all of the folder and uploaded it again
I set new InstallTool Password and added new Administrator
I updated the MySQL-Connection
Now everything seems to work correctly, BESIDES an error calling at the top of the page (where the language selection is supposed to be) saying:
ERROR: Content Element type "sr_language_menu_pi1" has no rendering definition!
For now, I tried to hide this annoying layer with CSS-property display none ;)
But it's a website where I need to have multiple languages enabled.
I have no experience with typo3, so please describe possible solutions as simple as possible.
This error happens e.g. under TYPO3 6.2.17.
You must have a sysfolder called "Templates" where you create a new extension template setup for the extension sr_language_menu. (Template Module)
Use the title "+ext sr_language_menu".
There you enter a constants part like this:
plugin.tx_srlanguagemenu {
addSelectionListHeader = 0
showCurrentFirst = 0
defaultLanguageISOCode = DE
hideIfNoAltLanguages = 1
showInactive = 0
pointerImage =
defaultLayout = 0
addLinksListHeader = 0
doNotLinkCurrent = 1
separator =
token = |
selectionListSeparator =
showCurrent = 1
useIsoLanguageCountryCode = 1
}
And you enter a setup like this.
plugin.tx_srlanguagemenu {
_CSS_DEFAULT_STYLE >
flags.stdWrap.split.wrap = <ul id="langmenu">|*| | |*| |</ul>
flag.NO.stdWrap.wrap = <li>|</li>
flag.INACT.stdWrap.wrap = <li>|</li>
flag.CUR.stdWrap.wrap = <li>|</li>
links.stdWrap.split.wrap >
}
Then go to the tab "Include static (from extensions):" and set the
Selected Items to
"Language Menu setup (sr_language_menu)" and
"Language Menu CSS Styles (sr_language_menu)"
Then go to your main template setup. (Template Module).
Edit Template "Main Template" on page "..."
Go to the tab "Includes" and add the "+ext sr_language_menu". to "Include Basis Template:". You can use the page browser in the new popup window to navigate to the Templates folder and select the record with the template name "+ext sr_language_menu".
Then you must install static_info_tables 6.2.1 or higher, and install the country specific static_info_tables extensions. Deinstall sr_language_menu and reinstall it again. Then open the Extension Manager an see the green round arrow symbol "Execute the update script".
Afterwards the error message has gone and the language menu shows up.
You can see if the templates of this extension is present on the project installation.
Might be you din not include static from template of "sr_language_menu"
Go to Web > Template > Root page
Info/Modify: edit whole template
Something like: http://screencast.com/t/jq3rggQy
cheers,
Ghanshyam
I found in typo3 admin side(/typo3), you can have two ways to set up TS,
you can set up through template->root, I think TS here will affect the whole site.
you can set up through template->certain page, it will only affect this page.
So my question is:
If I want to find where(which page) has TS setting such as : code = LIST, how could I do?
Use Web > Template module it has tools, you can for an example use Template Analyzer for the search
Try querying the database in phpMyAdmin or similar. The following looks in Template Setup:
SELECT pid, config, constants
FROM sys_template
WHERE config LIKE '%code = LIST%'
Replace config with constants to look in Template Constants. pid is the page ID.
If it is not set in the TypoScript, it perhaps has been set in the plugin itself. Just check the plugin content element itself.
In the Template module, go to the page where the setting is in effect.
Use the TSOB (Typo Script Object Browser) to search for "list":
This must show you all TS for this page that contains "list".
If you don't see the setting you can run a cmd/ctrl-F Search over the entire results.
You would have to search for "[code] = LIST".
Which will lead you to the following entry:
Hovering over the label will produce the above tooltip. Copy the line number.
Now change to the Template Analyzer. Here, you can click through all cascading templates and search for the line number:
This is definitely the line that sets that value.
From the "Template hierarchy" tree you will easily find the template that contains the setting.
I want to find which page has installed this extension: jc_register, I can check every page, but it takes too much time since there are many pages, so I wonder if there is any fast way to find it instead of checking every page?
If you mean you want to find a content record of type "Insert Plugin" set to a particular extension, you can use "Admin tools".
Open "Admin Tools -> DB check".
Select "Full search" from the drop-down list.
Select "Advanced query".
Tick "Use formatted strings, labels and dates instead of original values for results". This will give you page titles in the results when pid is displayed.
Set the query so that it finds your plugin and lists the page IDs (which means that the "Select fields" must contain pid).
Note: Tested in TYPO3 4.5 LTS and might not work in later versions.
Hi the extension name is located in "tt_content.list_type" field. So something like this should help you:
SELECT tt_content.pid,pages.title
FROM tt_content JOIN pages ON tt_content.pid = pages.uid
WHERE tt_content.list_type LIKE '%register%'
ORDER BY tt_content.uid DESC
gl
If you need to do it more often, you might consider the extension backendtools: http://typo3.org/extensions/repository/view/backendtools
It offers an extension listing with search functionality and links to the according page.