In TYPO3, if I need to create a menu for the different elements inside a page, I use the sectionIndex property. With Neos, how can I build a navigation for the elements inside a page?
I don't think you can, right out of the box.
That would require all elements on the page that you want to link to to have an ID attribute. In TYPO3 CMS all of the elements rendered with css_styled_content had one.
However there are multiple ways to do it with custom content elements. Like creating a section wrapper element with title and anchor id, wrap every section in such element and then create a custom content element that will look-up all of your section wrappers and make a list of anchor links pointing to sections.
Related
in TYPO3 there is a content element: a menu that displays subpages. Now I want to have some kind of filter function: the user should be able to select a TYPO3 system category and then the menu should only display subpages that belong to this category.
Is there an extension that I can use for a lookup or as a base to achieve my goal?
There is a content element type "Categorized Pages" that does exactly that.
If you need it to react to a user input coming form the frontend, you can easily add some lines of TypoScript to modify the rendering of that element so that it will consume a GET parameter to configure itself.
I have a website having a page containing multiple tabs
each tab is identified by cdk-step-content-0-1, cdk-step-content-0-2 and so on
please suggest me a good tutorial to create element by my own using hierarchy of pages and tabs
const element = document.getElementById("cdk-step-content-0-1")
The variable element will contain tab element.
You can find the parent or tabs wrapper element with element.parentElement.
I would like yo add something to the list view in order to make a report.
Is it possible without override the view and had some components or widgets below ?
How can I include the list view several times on a page ?
Thanks for your help
You can easily add stuff to the List page using Backpack Widgets. They basically allow you to include a view within an existing page. You can of course include a custom view (aka custom widget) instead of an existing one.
You CANNOT however include the list view more than one time per page. It's not coded in a way that allows that.
I have a typo3 server and using the mask extension. When an editor creates a new mask element, there isnt a title in the list view. Its always "no title":
I checked the database and found the titles in the db in the field: tt_content.header but no way to set them automatically oder manually by an editor. Anyone have an idea how the title can be set automatically? Oder manually by an editor?
ext:mask has the option to reuse existing fields of tt_content for new kinds of content elements (CEs). use it to get the bonus of better interoperability with TYPO3.
TYPO3 has a logic how to show records (content elements) in the backend. one of it is the usage of the fields header and description. if you reuse these fields your CEs will look like others automatically.
If you use other fields you need to declare your fields for usage AND in case you change the kind of a CE from your kind to e.g. TEXT with Media the header stays.
Especially header is handled in the layout/partial of FSC or CSC global for any kind of CE. if the handling/rendering is changed (e.g. special layout) in an installation your CEs need special effort if they have their own building of the header.
Try to use the same fields as existing CEs and your life can be easier.
I'm having the same issue, but I found a way around it for the meantime. I edit the mask element and chenge its type to something elseโlike Textโwhere I can set the title. After typing the title I save it, then change back to mask element and save again. This works by me without losing the content of the mask element. This way I can see the title in typo3 backend when I view as list or page or add content from another page. As I said, it doesn't solve the problem, but can help until there is a proper solution.
EDIT
I've just found another solution. You can add the title field to en existing mask element. To do it, go to ADMIN TOOLS > Mask, click your mask element to edit it. Add a new item by dragging the ๐ฆ๐๐ฟ๐ถ๐ป๐ด item (the one on top of the list of available items) to the right where your items are. Then in General under ๐๐ต๐ผ๐ผ๐๐ฒ ๐ณ๐ถ๐ฒ๐น๐ฑ dropdown choose an ๐๐
๐ถ๐๐๐ถ๐ป๐ด named:
๐๐ฒ๐ฎ๐ฑ๐ฒ๐ฟ: (๐ต๐ฒ๐ฎ๐ฑ๐ฒ๐ฟ)
Save, close, go to your page to add your title. This still doesn't add the title field automatically to all mask elements, but it is a step forward.
If anywhere, you should be able to set a static title automatically in your page tsconfig. You could to something like
mod.wizards.newContentElement.wizardItems.mask.elements.[title of your mask element].tt_content_defValues {
header = My Awesome title
}
Personally, I usually give every mask element a header field and ask content editors to fill it in.
See also this discussion on Mask elements and backend titles.
Hope, this helps.
I use the sitemap content element so that the editor can explicitly reference to individual pages in my page tree. Of course those pages do contain content elements (Textpic, Media, all the good stuff...) in their "normal" section. I need advice on how to modify the sitemap content element that it will output the content of the referenced pages.
I know there is already a plugin called "kb_sitemap" which basicaley does this job... but it does not handle the output of images or media (flash-, quicktime movies..) elements which is absolute necessary. The rendering relevant stuff is handled by Css Styled Content (CSC) which is necassary for me because it renders the media content element.
Do you use templavoila ?
Ok, go to page properties -> General tab (bottom part of the tab) and then you'll find all containers that possibly contain CEs, click to the lil folder icon and you may select content elements from any other page.
EDIT: added screenshot, page properties...
Note, showcase, maincontent, right content are just my names for my TV elements, could of course be name differently.