I just installed the Forums module to my Orchard site. Also, I created Taxonomy Link menu that serves as categories for the Forum posts.
By adding the Taxonomy menu to the default layer, I could make it appear on all pages. My questions are:
How can I make the Taxonomy menu (i.e., Forums categories) appear only on the Forums page? It would have been simple if the Forums "page" was actually a page in Orchard context as I can just assign a custom layer to the page to control the visibility of the menu. But to my understanding, Forums is just a content type, which is not the same as a page -- in other words, I didn't create a Forums page; I simply created a new Forum with a permanent link to "~/Forums".
I initially assigned the aforementioned Taxonomy menu to the AsideFirst zone but it would not show up for some reason. But it shows up just fine if I assign it to the (for instance) ContentAside zone. Is this a known bug?
Any non-programming solutions and/or workarounds (if any) will be most helpful!
Use a url rule in a new "forums" layer, then put the widget in that layer.
2.Does the AsideFirst zone actually exist in your layer?
Related
I'm new here. I'm working on a SharePoint website and I want to create a different navigation bar for a part of pages while others use the global navigation bar. It is like they are different websites but actually they are not. I wonder is that possible? If it is, how can I make it?
In addition, according to my research, it's possible to have a different navigation bar if I create a subsite, right?
The problem now is that I don't have the permission to create a subsite, that's why I'm asking if I can create a different navigation bar for a set of pages.
Thank you!
For a SharePoint site, there are two sets of navigation.
One: Global Navigation. Two: Site Navigation (Which is mostly the sites Left side navigation)
These articles describes more about having multiple navigation elements in a site: https://technet.microsoft.com/en-us/library/ee695757.aspx
https://support.office.com/en-us/article/customize-the-navigation-on-your-sharepoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca
Note: Instructions vary based on your SharePoint environment and setup. For better understanding if you can share which version of SharePoint you are working on. can give more insights. Hope this helps!
Is it possible to add a cqwp in a page layout?
Ive tried to move the webpart from the page to the page layout used in the page. But In the second case i dont see anything.
Anyone have an idea?
Thanx
It is supported to add instance of CQWP into Page Layout.
Possible reasons why CQWP results are not visible:
Javascript/CSS that affect the visibility of web part
Verify source settings for web part. In case if page and page layouts located on different sites and the source property is configured to Show items from the following list or Show items from the following site and all subsites then this could be the reason. In both cases for for source property the relative path could be specified.
I have two features that add CustomAction to the SiteSettings page. One feature is at the Site level and the other is at Web level.
The CustomAction that is being added at the Site level is a link to the custom configuration page that manipulates Site level settings for my application. Therefore, I don't want the link displayed for the SiteSettings page of a subsite. I know there is a setting (RequireSiteAdministrator) that hides the page according to access level, but I would still like to have this page show up for Site owners at the top/root level site settings page and not in the sub site level setting page.
There is a RootWebOnly attribute for the CustomAction xml node which would solve my problem. The problem with this attribute is that it only available for SandBoxed solutions.
I know that this is possible, since I see the behavior for the Site collection administrators link in the Users and Permissions section of the Site Settings page. Please notice that if you go to the top/root level settings page, you will see this link. On the other hand, if you navigate to the Site Settings page of a subsite, the link is no longer there.
I have tried using HideCustomAction, but this hides the link on both pages.
After battling with this for two day, I had an ah moment that I thought I would share. This will allow you to place a custom action that will show only at the root web level.
Create 2 features. One at the site level (siteFeature) and one at the web level (webFeature).
Make the web feature hidden so that it can't be accessed (activate/deactivate) though manage features page.
Put the custom actions element xml in the web feature.
In the activation event receiver of the site feature, activate the web feature.
UnfortunlyUnfortunately this is not possible with custom actions and custom group.
All you can do is just to set up permissions on the link that will be shown only to SiteCollection Administrator
Example how it will be is "Site Collection Administation" group where links are hidden when you are not on the top site level and shown when you are.
Hope it helps,
Andrew
I have a page layout with a webpart zone in it. As per the requirement there should be 4 custom webparts in that webzone.I have placed the webparts in the order as per the requirement. But when I try to create a new publishing page with this layout, I could see
that the order of webpart I have given in layout is not same as in the newly created page. So once again I have to order these webparts in edit mode .Changed the zone index property for the webparts in layout but it’s still not coming in order in the newly created page.
Ex:
Ordering of webparts in the page layout.
Ordering of webparts after the page is created using the layout.
Any help for fixing this ordering issue will be greatly appreciated.
So you have preloaded the web part zone in the page layout with the four web parts in the order you wish? If so and the order is not correct then you might have to create an event receiver that can trap when the page is being created and then add the web parts manually via code. that would at least ensure the order but seems overkill to me.
If the web parts are included in the web part zones within a page layout though, they should be added in that order when the page is created.
I have a feature that deploys a few site columns, a content type (inheriting from Page Publishing Content Type) and a page layout based on my content type.
Everything is fine on two tests, performed on different servers, but on the third server, although the feature is being activated correctly and I can see the site columns, content types and the page layout in the galleries, I cannot create a new page based on my page layout because the page layout does not appear in the list of available page layouts.
On all tests I have used the administrator account.
Does anybody have any thoughts on possible reasons for this?
Thanks.
Did you have a look at the "Page layouts and site templates" page under Site Settings? On this page you can enable an option that limits the available page layouts to a specified list of page layouts.
I have worked on a project where we needed to limit the page layouts available on a custom site definition. We implemented this in a feature, that enabled the "limited page layouts" option and populated the list of available page layouts upon activation.
If this is the issue you are having you could simply turn off this option in the web interface or add the new page layouts manually, but you could also consider implementing a feature receiver that automatically adds your custom page layouts to the list of available layouts.
Thank you all for your answers.
What actually happened is that the page layout was, for some reason, deployed as a Master page and not as a Page Layout. The admin has manually changed this and now it works.
This is just an educated guess but check to see if the Page Layout is waiting to be checked-in or approved.
In my case the path for the layout was wrong so the layout itself ended up in a different location, when I corrected that i was able to see the results.
I had added files manually and it did not appear.
When I edited properties of that layout page from UI and saved it, it appeared.