I have a multiple language website.
I'm using the TYPO3 Backend to move many content elements from page to page, but this move the CE only in one lang, but i would like to do it only once, so if i move a Content from page 4 to 8, it should be done in all the 4 languages.
Thank you!
do the moving in the List module. In List module you can mark the records for all languages at the same time and put them into the clipboard.
Related
I am new to TYPO3 and have trouble understanding the general relation between extensions and the backend of TYPO3.
For example, is it true that the goal of making an extension is to be able add edited/new content elements to your page that cannot be found in TYPO3 out of the box?
For example if I wanted to add a carousel to my page, would I make an extension and design it in such a way that I can add it from my backend to the desired page? Or would it make more sense to, for example, put it as a partial and import it to the desired page using fluid (all of this without using the backend and just using code).
Or are both approaches possible and when would you go for the first or the second (or seek out a third approach)?
Sorry if this question is too general/vague. I feel like I do not understand how the backend and the files in my TYPO3 folder communicate to generate the website and that I am using content elements in the backend one time and typing out the elements in HTML the next time without a good reason for it.
I try to bring some light into the dark areas.
Backend This is the admin area of the CMS where in most cases the content is created by editors.
Frontend: How the website looks to a regular visitor
Extension: An extension is custom code, either your own code or by others which extend TYPO3 in one or more ways. The benefit is that you don't change the code of TYPO3 core itself and therefore it can be always updated.
An extension can be used for a lot of things:
- Shipping a site template with all the assets like CSS, JavaScript, HTML template, ..
- Providing custom content elements
- Providing new record types like news or forms
- Improve user experience
So yes, if you want to have a new kind of content elements you need to use an extension:
Search on https://extensions.typo3.org to check if there is already something which fits your needs
Use https://extensions.typo3.org/extension/mask/ (best in combination with https://extensions.typo3.org/extension/mask_export/) or https://extensions.typo3.org/extension/dce/ to make it a lot faster to create content elements
If experienced you can also create a custom content elements without any additional extension but for start I don't recommend that.
One approach to look at this question in a different way might be to differentiate between content created and maintained by editors (the backend users which typically add and maintain content) and parts of the visible webpages created in other ways. For example, the header, footer, menu of a site may be created by a sitepackage extension - this is something the editor (backend user without admin access) typically has no permission to access and that is one of the points of a CMS - the content is editable by someone without technical background. Of course this improves the stability as well because you don't have people fiddling around with things they should not be able to have access to and thus cannot break.
If you want your editors to be able to add (remove, change) content - do it in a way they have access to (typically using content elements).
You are right, the core provides content elements (such as "textmedia"), extensions can extend this by adding other content elements.
For your example with "carousel" you might want to look at the (official) Introduction Package which uses the bootstrap_package which offers a carousel content element. The Installation Guide explains how to setup a TYPO3 installation with "Introduction Package" so you may already be using that.
For example, is it true that the goal of making an extension is to be able to add edited/new content elements to your page that cannot be found in TYPO3 out of the box?
That is one of many, many other possible purposes of an extension. For example, look at the extension "min". It does not provide any content element and there is no visible change for the editor. An extension is just a way to extend the TYPO3 core (while the core itself also consists of extensions).
Introduction of Extensions in TYPO3 Explained
Sitepackage Tutorial
I'd like to minimize the number of times I have to type dates and version numbers across release notes pages and such on Confluence.
How can I reuse a text string within the same page as well as across pages on Confluence?
Right now, I have a bit of text (for example, a version number) which is typed out in multiple locations:
Page A
Top of page
Middle of page
End of page
Page B
I'd like to be able to type the value once and have it automatically appear in all places.
There are multiple bits of text I'd like to do this with on one page.
The closest I've found so far is the MultiExcerpt macro, but unfortunately it displays all content with newline wrapping instead of inline and that's a dealbreaker for me.
You may want to look into Comala Metadata, sounds like what you are looking for.
Disclaimer, I work in the company behind that app, in Comalatech.
Regards,
Gorka
Have you tried using Confluence own Include Macro or the Excerpt Macro. The include macro can be inline if you keep it on the same line in the editor.
There is an official extension called Multi Excerpt. It works like Excerpt, but you can use more then one for one page.
I need to create a website with two languages one with English and German. I'm not aware of TYPO3 scripts.
As I studied different references I saw this one and tried to work out.
But I'm not able to use it because their is no language bar in top of my TYPO3 back end. Also when i tried to add language in drop down of edit page and add content page it shows only 'Default' in the list.
How can make a website with different language switching in front end?
thanks in advance
The "List"-Module (on the left) is your friend:
chose the list module and afterwards your rootpage in the pagetree (PID = 0).
In the content section in the right upper bar you can "create a new record".
Chose "Website language" and fill in the wanted properties and values...
Afterwards you will find the dropdown to create a page translation in the newly added language...
I'm using an own Extbase extension with my articles, which are stored in a Sysfolder.
It is possible to move the Search Box in the Backend's List module from the bottom to the top?
This is not possible since the html is not located in a template but is hardcoded located in the \TYPO3\CMS\Recordlist\RecordList::main() function (see: typo3/sysext/recordlist/Classes/RecordList.php).
I don't know if the back-end has a contentPostProc-all hook. If some kind of hook exists you can move the html by your own class.
I was wondering if page templates can be built instead of individual components in Teamsite 7? I've seen other cMS systems where it is just a page template that has lots of functionality built I and you can "switch" on and off elements that you want to display instead of having to drag components onto a page? Is this possible?
Old question, but since I just came across it:
Yes, TeamSite supports templates (.template) files which can be partial or full page templates. The default location is iwadmin/main/livesite/template.
I recommend downloading the developer guides from Autonomy's web site for detailed information.
Templates in teamsite/livesite is like a bag that can contain components. But in order for a functionality to be developed in teamsite/livesite we need to create components. certainly we can avoid dragging and dropping components in each page by creating templates and dropping components within it for once. Keep in mind templates are bound to layouts. for each type of layout we need to create a template. Please have a look at TS_7.3_SiteDeveloper_rev1, Chapter 5.
Yes, you can create templates instead of dragging components.
Since, TeamSite supports templates (.template) files which can be partial or full page templates and resides at location : iwadmin/main/livesite/template.
So, whenever you try to create a new page everytime the HTML code required for that page gets automatically added with the template and layouts you selected.
But, again this is not good since you can have any number of templates you need but this could create confusions at times when you try to create a new page since you will need to remember every template name and contents that you will need for a particular page so it's better to have small lists of templates and layouts since then we can say that there is reusability in our application/website which we are going to develop using Teamsite and Livesite.
Please vote the solution if its helpful.
Thanks!