Unfortunately I could not find anything helpful with my google skills. Coming from wordpress I am quite new to TYPO3 and I am a little overwhelmed with it.
I would like to adjust the RTE only in my TYPO3-extension. It should allow iframes and images.
Can anyone help me how to do this in the best way?
Images in the textarea would void the clean separation of images and text, but there is an extension rte_ckeditor_image which would enables it.
Otherwise you could define configuration presets, which you could assign to your fields.
More info in the manual for the rte_ckeditor
Related
I have a custom extension, and i need to use some form of text editor in the front-end. According to the documentation, it should be possible, but the documentation and tutorials seem to be deprecated. I think this is not available in typo3 7.6 :
require_once(t3lib_extMgm::extPath('rtehtmlarea').'pi2/class.tx_rtehtmlarea_pi2.php');
Can it be done somehow or do i need to install another extension for this, maybe just a viewhelper? Thank you in advance.
I did lots of researches trying to use the rtehtmlarea in the FE, but failed. Then, I realized I could use any RTE, as they are nothing but js+css. All I need is to render the contents with RTE.FE, like how the BE does, and save the result into the database, which is all I want. I have already done this in many sites, using standalone tinymce, and it works great. So, I think maybe you could try this solution.
To be honest, that feature worked only in theory and never in reality. Use an RTE like ckeditor or whatever fits best
I have a question before downloading tinymce.
Does anyone know if its possible to disable features for the users? (Example, make it so the user can only input text, not pictures)
And also, is it possible to change the style/css of the buttons and toolbar so they fit with your site?
You should manipulate tinymce.init() by adding or removing the unwanted plugins.
There are tons of options, so do some experimenting.
However, you should really begin with reading the documentation.
I found a better JS RTE out there and would like to know how to replace the TYPO3 default with the one I found. I googled a lot but couldn't find anything stating how to achieve this.
This is not easily possible without "loosing" many TYPO3 features, because the rtehtmlarea highly integrated into TYPO3.
Especially the link handling is custom, so you would have to write special support to make this work.
A possible replacement is tinemce_rte. It works fairly well, but it does a little more than just replacing the editor with tinymce, e.g. it also adds custom linkhandler support. You can look into this extension if you really want to do this work.
You can download tinyrte or ask in tinyrte forum how to replace htmlarea. Here is the download link: http://typo3.org/extensions/repository/view/tinyrte.
Up to now, I used to use template auto-parser. I like the fact I can modify any element of the template using typoscript, without altering the initial HTML file. I also like the fact that I can render the html template directly in a web browser, filling it with dummy elements to see examples of menus and content elements. Finally, with the new backend templates, i now can place content elements anywhere on a grid, in a way that mimics the real aspect of the website.
I know there is also TemplaVoila. I never took the time to learn it. My feeling is that it is less compatible with some extensions, but maybe I am wrong.
Now, there is fluid, that will be used in the next version of Typo3. While it is clear that it is better using it that using template markers, I don't really understand why I should be better using Fluid than using template auto-parser or TemplaVoila. What I dislike is the fact it requires to modify the html template with special tags, meaning that either the web designer has to know Fluid, or the Typo3 integrator has to modify templates from the designer each time a modification is performed.
My question is: should I migrate form template auto-parser to Fluid for my website template? What are the benefits of using Fluid? Why should it be better? What template system should I use with Typo3?
As long as TypoScript does not support objects, the benefits of FLUIDTEMPLATE over template auto-parser are only a few. So there is no need to migrate.
But IMHO there are some arguments to switch to fluid:
more and more extensions will use fluid, so it will help you to learn fluid
you can use an ide with code-completion for fluid (it is just XML!)
fluid is really powerfull, you can have f.e. if statements which checks for empty content
some day TypoScript will support objects as well
But for extension developement, it is totally different. In an Extension, i would allways prefere using FLUID. You do not have to deal with template things inside your extension anymore. Just pass the data to fluid and things which concern the view will be done in your template.
Whever you choose, it should be something based on Fluid - this will allow you to be extremely versatile and it makes the implementation less important than the template, which is quite good.
I myself am the creator of the "Fluid Powered TYPO3" framework (formerly known as FED) and would of course recommend that you take a look at what this framework can do for you - it's capable of great things, not the least of which is saving you a lot of time while at the same time allowing you to create even more consistent templating for pages and content - and even backend modules.
And we're always happy to help new users. We are currently in the process of improving our documentation, but you can already find many fully up-to-date guides on our Github page - https://github.com/FluidTYPO3 - the repository called "documentation" is the place we will store all the documentation.
You may want to have a look at http://fedext.net http://fluidtypo3.org - especially the "Tour of features" which tries to explain the point of Fluid Powered TYPO3 in as few words as possible. After that, the examples from the documentation will give you a much clearer picture of what Fluid Powered TYPO3 can do for you.
We focus on efficiency always - we've tried to do all the heavy lifting so that you really can just sit down and begin creating page templates. We took a lot of inspiration from TemplaVoila but there is no more re-mapping of content and things like this: when you change your templates, that change is immediately reflected, which makes it very nice to work with in iterations and do things like continuous delivery and -integration.
Hopefully this helps!
Cheers,
Claus aka. NamelessCoder
You could also argue, that adding special tags like
<f:section name="typo-content">
<div id="content">This is where the designer intended content to go</<div>
</f:section>
Could assist your designer while doing a redesign to know where you "mapped" your content elements to. This is neither the case with autoparser nor with TemplaVoila. So if the designer moves stuff around you probably get your templates back and they still work without any modifications.
I'm fairly new to TYPO3 and as far as I can see it's pretty poorly maintained as far as documentation goes. Some of the tutorials and documentation are almost a decade old and I was wondering if anyone here knows of any useful extensions that could enhance the standard content tables in the backend.
I have some tables that contain a bunch of links with images. A sort of categories gallery with thumbnails if you will.
The point being that at some point this gets passed on to a client who won't know what to do with HTML markup and i was wondering if anyone knew of 1) a good WYSIWYG table editor extension and 2) a categories gallery plugin with the option to add thumbnails to each category.
Cheers.
Look for some of the more recent plugins. I don't usually go back more than a year or two when searching for an extension.
I'm not exactly sure what you're looking to do, but did you know you can arrange the standard image elements in different ways, linking each image to a different page, kind of like what can be seen at: http://www.thedemo.ca/demonstrations/image-and-text-alignment.html
Simon