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.
Related
When I am inspecting elements there are styles applied which are generated by webpack dev server and pasted in <style> elements. But when I try to inspect how those styles look like I am getting just partial content of that element.
How could I see the whole content?
I tried to find it in "view page source", but those style elements are added dynamically so they are not present in page source.
Only option I found so far is to click on style element, so it is selected. In console, let print content to console $0.innerHTML. $0 is reference to latest marked html element in Elements tab.
Store style element as a global variable, then assign it innerHTML to a variable and show it in console. I was able to copy full 25kB contents of style tag
image to help
I have cq5 content page below content tree in crxde.
The content page has a header, a footer and one component in the body section.
I am trying to get the only content that authored in that specific component (No header, No footer, No Edit bar of component)
I tried following, but it produced the whole page with header, footer and component.
<sling:include path="/content/site-content/disclaimers/risk-considerations.html" />
then, I tried this, there is no header, footer but it still displays Component edit bar.
<sling:include path="/content/site-content/disclaimers/risk-considerations.content.html" />
How could I achieve only returning authored content into another page?
Based on what you need, reference component as Abhishek said fits your use-case. Given that you won't want to hardcode a path within a component or page you would use a dialog to get the path to HTML to include, reference component does that for you in addition to that your use-case of disabling edit-bar/behavior is taken care of within the component.
But in case you are constrained to use your existing approach, then to disable editbar you would need to update your component script to change the mode prior and post inclusion. You can refer to reference component for same. You can also refer to stackoverflow answers here and here
Requirement is simple , Want to render the content of sub page in main page.
Is it possible using vhs extension ?
I want to render all the sub-page content in [9]Zweckverband Parent Page.
Requirement is fully dynamic , sub-pages can increase and we need to render all the sub page content in parent [9] page.
we can render the menu using vhs , and can render the page content using vhs.
We need to combine both the coding to achieve this requirement.
Thanks in advance !
You can just render a menu of the subpages, but instead rendering a menu item for each of them, render their content (and maybe a headline or something). Rendering the content of an arbitrary page can be done with
<v:content.render pageUid="{currentPage}" column="0"/>
Other content retrieval viewhelpers should also have the pageUid parameter, so you could use them as well.
One thing that could come up is caching: If a subpage is changed, the rendering result of the main page changes. But probably TYPO3 won't recognize that, because the content on the main page itself didn't change. You might want to look into the clearCacheCmd and the like to solve that.
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.
I am very new in Typo3 world (I came from Joomla and WordPress) and I have some doubts related a thing that has been requested by a customer that use Typo3 for its site
He ask me to create some colored boxes into a specific page. Each of these boxes simply must contain text or links.
How can I do this?
I am thinking that I can solve in the following way (but I have not idea if this is a GOOD solution):
In the backend I go in the Page section and I open the settings related to the page that I have to modify
Here I have 3 columns (Left, Normal, Right) and for example I add a NEW Regular Text Element into this central column
Now appear to me the wysiwyg editor, so I click on the Toggle text mode icon and I pass from the wysiwyg mode to the pure HTML editor's mode and now I will create some div tags (settings the CSS settings for the background color and the dimension) that rappresent my boxes (and into these div I put their textual contents).
Is it a possible solution or is it a bad solution?
Tnx
Andrea
You may either use the RTE typoscript config to add some new paragraph styles, which will make the boxes or use the section_frame field in tt_content, a field called "frame" in the backend when you edit a content record. Both solutions would just need some typoscript (which you will deal with very often in the TYPO3 world) and CSS code.
If you need some more structure in the backend, there is also an extension for that called multicolumn. If you just need "more" columns in the backend (in combination with backend layouts) to achieve different looks, this can also be done by adding some typoscript config. To give you a more precise recommendation, some sort of scribble or design screenshot of what you want would be nice.