The Scenario
I have a website with several autogenerated menus:
Main menu ("root level" pages)
Tree menu (full tree down to current page)
Breadcrumb (only .ACT)
Now I see two possibilities regarding these menus and the RealURL extension.
Strategy A: Root as Front Page
I will create the page tree like so:
⊛ www.site.tld
↳ Page 1
↳ Page 2
↳ Page 3
Pros & Cons
Con: I will have to manually add a link to the "Front Page" (content from page "www.site.tld") to all permutations of the menus (as this is not on the same physical level as the other "root level" pages)
Pro: RealURL will per default render all links to the front page (the root page) as /
Strategy B: Front Page as Separate Page in Tree
I will create the page tree like so:
⊛ www.site.tld
↳ Front page
↳ Page 1
↳ Page 2
↳ Page 3
Pros & Cons
Pro: A link to the "Front Page" is automatically added to all permutations of the menus (as this is an explicit page on the correct level)
Con: RealURL will per default render all links to the front page as /front-page/ while I want it to link as /
Best Practice?
Is there a best practice in the front-page-as-root vs. front-page-as-separate-page question? I.e, should I go with A and manually extend the menus, or with B (if so, how to configure RealURL to render the correct links)?
Edit: The Answer
Phil provided me with a solution to the specific problem. Go with strategy B, but let the page "Front page" be a link (dokType = shortcut) to the root (the page "www.site.tld"). This will fix the menus and the links. ("Front page" being a shortcut, contents will reside on "www.site.tld".)
If anyone knows of alternatives to this one, please let me know. I do believe, however, that this will satisfy my needs concerning this issue.
I see 2 solutions (if I really understand youre question).
Put the Front page type to link, and link it to /
If you have access to the .htaccess, redirect /front-page/ to /
The solution B is easier, and it can be done without a special RealURL config
Related
I have followed this tutorial https://help.liferay.com/hc/en-us/articles/360018167031-Creating-Layout-Templates to create custom layout for Liferay 7.3. After deploy the layout to the Liferay manually using app manager, I'm not able to find the custom layout in Fragment and Widget option.
When I check in Global Menu > Control Menu > Components > Layout Templates. I'm able to see my custom layout.
Did I missed anything or is there any other way to add custom layout to Fragment and Widget options?
Thanks
You missed one crucial info: "Layout Templates" are only applicable to pages of the type "Widget Page" (the default and pretty much only page layouting method in Liferay 6 and earlier). "Page Fragments", on the other hand, are only applicable to pages of type "Content Page" (which came up somewhere between 7.0 and 7.3). You set the type of a page at the moment you create them, by selecting one of the corresponding page templates.
So, if you want to create a certain row/column layout as a template for your "Content Page", you may want to look into the page fragment type "section". Basically, you'll be creating a Page Fragment that incorporates some <lfr-drop-zone id="invent-your-own-id"></lfr-drop-zone> tags in its HTML. Documentation on dropzones is very sparse at the moment (best source I found is Liferay's issue tracker plus experimenting yourself), but as this tag currently does not allow more attributes than id, you can simply experiment with it.
(Side notes: Due to some arcana in some standard documents, you cannot use the self-closing form of the <lfr-...> tags, so <lfr-drop-zone id="abc" /> will fail silently. Also, remember that the HTML part of a page fragment actually will be interpreted as an FTL template using Freemarkers alternative syntax before the <lfr-...> tags are interpreted., which gives you the option of placing a configurable amount of dropzones using a loop.)
But: take a moment to check whether you really need a custom "dropzone layout", as Liferay already provides you with a configurable "row section" in the content page editor; and anything more complex will give you headaches when making it responsive.
We are going through this exact same situation. Up until 7.1, we used Layout Templates on Widget Pages to enforce a consistent design over our Org's Intranet, while still having per-Department Authors (see Herding Cats).
New requirements, including the Users overall desire to have more control over page layout and simplified editing, as well as personalization (using Segments), are forcing us to implement the features of Widget Pages (and Layout Templates) in Content Pages. So far, Page Fragment Sections (as #orithena suggested) are giving us a path forward.
Now, we're developing for 7.2. 7.3 seems to be taking this concept even further, with the afformentioned drop zones, nested row layouts, and Master Pages.
I'm in trouble to build a multilevel drodown menu in a site made with typo3.
I created the pages and organized them in their hierarchy, but the second level of the dropdown menu doesn't appear.
I searched but just find TypoScript related topics, but I'm in an specific environment that doesn't allow me to Code with TypoScript.
I wonder if there is any configuration I haven't seen.
Can anyopne help me?
If you are not allowed to use typoscript at all you are only an editor. And it's not the job of an editor to build menus. Go to your admin/integrator and give him the job to display multiple levels.
If you have the possibility to create template records, but the whole configuration is done in a site-extension (where you have no access), you still can create/ enhance the menu and give that typoscript to the developers.
There are contentelements to build menus, but for the page main-menu I never would use them.
A better solution is the usage of menu viewhelpers in the page templates/ partials/ layouts.
My preferred way: build the menu in typoscript in a fluid-variable and use it in the fluid-templates.
I don't know how your site gets it menu. From your description I assume that the menu misses either the configuration for deeper level at all. Or it missses expAll = 1 so you only see pages around your rootline.
I have two pagetrees in a TYPO3 (6.2) with different Domain records.
Tree A is the tree where we log into the backend.
When the editor tries to view a hidden page in tree B, he always get a 404 (and not the preview-mode).
I think this is because of the cookie mismatch between be and fe.
How can i configure the backend that the editor can preview all hidden pages?
This is basically not possible and your guess is correct. Possible solutions are:
Log in at this domain as well
Use "hide in menu" instead of "hidden". Please be aware that the page is then available for everyone
Many visitors visiting our website by a link to content in a different language from their mother tongue. If they click on the language switcher, they will be redirected to the home link of the current menu. That means they have to navigate to the content again.
Is there a Plugin available that solve this problem?
The use should change the language and see the english version of the specific content.
That should not be the case, if you have set up bi/multi language in the right way.
Have you associated the articles to each others as well as the menu entrys?
You need to have exact copies of your menu.
Are you talking about "Content Pages" that have no menu entry? If so, try to create a menu which is not visible for the user, but use it to associate content.
You find the Association Tab in the Menu Entry Edit
The Falang component allows you to manage all your content translations, even the content of all your components/modules, on your web site.
Falang doesn't use the default language system of Joomla 2.5 and 3.3. You don't have to specify a language for each content article or menu item (which results in a huge amount of duplication). You don't need to create few menu copies, few articles/categories copies for different languages.
Here is described how to use it
How could I trigger in JS a click on the pageitem of TYPO3 BE pagetree by an ID of the page ?
Looking for solutions for versions 4.5 and 6.1.
The basics are described in this document (might be slightly deprecated):
http://buzz.typo3.org/people/steffen-kamper/article/backend-navigation-in-typo3-45/
For example, to open the submodule "task center" in the "user tools" module, enter this
top.TYPO3.ModuleMenu.App.showModule('user_task');
or, to change to the pagetree, this
top.TYPO3.ModuleMenu.App.showModule('web_layout');
inside the firebug console. According to the author,
The pagetree resides in top.TYPO3.Backend.NavigationContainer, the
content resides in top.TYPO3.Backend.ContentContainer.
I haven't really understood what you'd like to click on exactly. But it might get you started.
I think in real life (or in an html fragment in a page in the backend) you can set <a javascript:...> urls</a>
I am still trying to figure out the fine points of this javascript myself. I for one want to also click on a select-box in the content Iframe after clicking in the Admintools/Report submodule. The first part is this:
top.TYPO3.ModuleMenu.App.showModule('tools_txreportsM1');