Protect the form definition yaml from being overwritten - forms

I'm working on a legacy page with TYPO3 9.5
I made a form and heavily edited the form'S YAML file. I especially added YAML aliases.
When I now edit the form in the TYPO3 BE form editor and save it, the anchors and aliases are lost.
Is there a way that I can protect parts or the whole of my YAML definition to be not touched by the TYPO3 BE form editor on save?

This should be possible - check the documentation about that at https://docs.typo3.org/c/typo3/cms-form/main/en-us/I/Concepts/FormFileStorages/Index.html
As this change has been implemented with 8.7 (see here) it will also work on 9.5
TYPO3:
CMS:
Form:
persistenceManager:
allowSaveToExtensionPaths: false
allowedExtensionPaths:
100: EXT:my_ext/Resources/Private/Forms/

Related

Update extensions with rte fields and <link>Syntax

i have to update an extension from TYPO3 6.2 to 9.5. This extension uses three fields with rte which contains links in old syntax: and so on. After running all TYPO3 update scripts the old syntax was not corrected. I changed the TCA of the extension to the new syntax and installed the extension so i can edit all entries in the backend. It seems that most is working correctly now but not the old internal links. In the database they are in the old syntax so the links vanish in the RTE in backend. I tried to rerun the update script but this doesn't change it. How can i trick the the updater to convert the fields of my extension?
Thanks!

Typo3 No template was found for new FrontendForms

I'm experimenting a bit with Forms in TYPO 3 version 8.7.13
I have created a form in the typo 3 backend, all good and it looks good, however when I add the form to a page and the load the front page I get the error
Sorry, the requested view was not found.
The technical reason is: No template was found. View could not be resolved
for action "render" in class "TYPO3\CMS\Form\Controller\FormFrontendController".
Is there anything that needs to be added to the Typoscript config in order for them to work ?
You need to include the static template in your TypoScript template.
You have a TYPO3 form plugin on your page. See the details of the form system extension in the TYPO3 backend page module.
**Form No form selected.**
Apply the necessary yaml file to your form. Or hide or delete the form plugin.

RTE in own backend module based on Extbase and Fluid

for a complex structure of a domain model (lots of fields and some relations) it´s planned to write an own backend module to be more flexible according to the structure and usability of that module. And there are some dependencies of some fields which I think I cannot make it just via TCA resp. FlexForms. So one thing I hope someone has done that before: If I build an own BE module with extbase and Fluid etc. and have forms with input fields or better textfields:
How can I add an RTE to such a field? Is that possible? I´ve read the TYPO3 Extbase book, but the example there do not contain a RTE.
in case you would like to use the same RTE as TYPO3 it is quite difficult to add all required scripts including the configuration of RTE to a field and I can't help you with that.
But I would like to remember you that in TYPO3 8 LTS the ckeditor becomes the new TYPO3 editor. So you may look forward to directly use it in your backend module or check out the docs of 8 LTS regarding the usage of it on own fields (if any docs exists yet).
http://ckeditor.com/

Typo3 7.2 Where to edit default templates + backend layouts?

Where do I edit default backend layouts that come with typo3 7.2 official introduction package? there is a table in the db that holds backend layouts but only those that I created, not the default ones. But where do I find the colPos layout for the default templates that already come with the installation? I only want to make slight modification in the html template and I'd like to make the changes editable from the backend.
Backend layouts are defined via PageTS below mod.web_layout.BackendLayouts.<key>. This is not a standard functionality, but a possibility provided by one of the integrated extensions.
The mapping of the backend layout ids to the template files is done in the actual TypoScript template at the path page.10.file.stdWrap.cObject.<key>.value.
For backend layouts created via the database, the key is the numeric id of the backend layout record.

Creating a new page template in Typo3

I'm using Typo3 for the first time and have been asked to update a site built on it.
Making changes to existing templates so far has been OK since they were mainly CSS changes or replacing images. Now though I need to create a couple of new page templates.
What's the easiest way to go about this? The existing site has a home.html and layout.hmlt in the fileadmin directory. Do I need to create a new html file there, if so how do I use this as a new template for some of my pages?
I'm coming from a mainly WordPress background in terms of CMS (I've nearly given in a recoded the site as a WordPress site since I think it would be quicker at this stage) but I'd really prefer to figure this out.
Any suggestions would be greatly appreciated as I'm pulling my hair out trying to read through the documentation and getting nowhere. The site is using Typo3 version 4.4.6
Thanks!
How you add a new template to your page depends on how templating is handled. Sadly TYPO3 has a poor templating out of the box, so there is most likely an extension that does the job on your site.
Probably one of these:
automaketemplate
templa_voila
flux & fluidpages
Check if one of these extension is installed and add a new page template according to the extensions manual or specify your question afterwards.
Edit:
If plain TYPO3 was used, you'll find something like
page = PAGE
page.10 = TEMPLATE
page.10 {
file = fileadmin/myTemplate.html
}
in your Typoscript. You can add tmplate files like the ones that are already there. To use a different template on a page, you have to replace the page.10.file with the template you want to use. This can be done with a new template record (crated in backend via the template module). But this is a rather anoying procedure to change the template, because you have to create each time you want to change the page template for a page and its children. That is why mostly extensions are used for this.
The out of the box situation gets better with newer TYPO3 versions but in 4.4.6 there are no Backend Layouts that could be uses for a template switch ot something like that.
In Addition to change the mere file you have to adjust the subparts or marker that are filled with the content. You'll find that configured in your TypoScript as well