Is there any solution to inherit permissions from parent site page to child site page in Liferay?
Maybe you can add a Page Template, configure its permissions, and use it for all your pages? That way child pages have the same permissions as parent pages.
Related
I need to block anonymous from entering the site, but I can't find the controller that builds the Home page nor the routing that redirects there.
Going to the widget admin and unpublishing/deleting everything in the anonymous layer, only hides the items but I need to redirect to the login page, just as the Admin area functionality.
And I cant' just remove the anonymous role, because they can access some pages and content, just not the Home.
Orchard, by default (though you can override this, see the blog module), uses the same controller to render all content items, including the home page.
What you need is the content permissions module, that has a part you can attach to content types (e.g. Page) that will let you specify, per item, what roles can view it. Attaching this and setting only authenticated to view your home page should redirect to the login page as desired.
I'm retrofitting a V9 site with a new 'sub site' This site will have it's own navigation system and IA. My plan, maybe, is to create a new folder in the content tree named 'New Site' and then created all my pages and items within there.
For the domain, i would then create a domain alias, and set the 'Default Alias path' to the 'New Site' folder.
This so far seems clear. Is it possible to have cross site contamination? Ideally, the old and new sites wouldn't mix under a single URL. I'm worried about navigation on the old site ('css list menu') picking up pages from the new site.
Had i know this was the plan, i would have created folders for each site to isolate, but moving to that structure may cause a lot of problems.
Based on the answers you posted, what I've done in the past is to:
create a new page type called Divisions or whatever you'd like.
Then create a new page template which doesn't inherit anything from the master page and flag it as a master page. Add the webparts you need on there, specifically a Head HTML webpart with your stylesheets, js, etc. Because it won't inherit from the main master page. But if you have a stylesheet assigned in to the site in the Sites application, that will be inherited unless you specify otherwise on the General tab of each new sub site.
Back on the page type you just created set the default page template to be the master page you just setup.
Add a new sub site/page to the content tree
Add new pages under the sub site in the content tree. Set your navigation path to be /{0}/% so it always selects the sub site as the root.
In your other master page you shouldn't need to worry about the other pages, because the parent page won't be visible in the navigation so the children won't show.
I will sum the logic through 4 easy questions:
Can/should private pages have public child pages? (it seems private pages are using other site or context for any group/user)
Can/should public pages have private child pages?
Can/should hidden pages have non-hidden child pages?
Can/should a page which certain user is not allowed to VIEW have a child page which certain user is allowed to see?
Does some of the previous scenarios change parent page's behavior? I mean maybe allowing you rights to a child page makes you automatically authorized to see parent page.
Furthermore, what is the difference between hidden and *non-hidde*n pages? I can browse both through links!
In answer to your questions (for Liferay 6.1, may differ for earlier versions):
Private pages can only have private child pages
Public pages can only have public child pages but the children can
be hidden (so they don't appear in the navigation but can be
accessed directly by the URL)
They can, but they also won't appear in the navigation unless
you've changed your theme so that they do
Yes it can, and again it's up to you and whether you want to
theme to have that restriction or not
Parent page behaviour is not affected by child page settings.
Hidden page: Pages that are hidden from the navigation but can be accessed directly via links or typing in their URL
Non-Hidden pages: Can be seen in the navigation, and can accessed in the same way as hidden pages.
Private pages: Can only be accessed by authenticated members of the community that they belong to. They are effectively gated pages so hidden from public viewing without having to set the page permissions for Guest users.
I hope this answers all your questions.
~~ EDIT ~~
As Julien Lafont as mentioned below: Hidden pages are visible in the search portlet. If you want to hide them from a particular group of users, use permissions. Thanks Julien.
the problem: when sending out marketing emails we should track on the website whether user came by a link from an email. The site is hosted in SharePoint 2003 environment and our *.aspx page is in an iFrame. How can I pass QueryString parameter from SharePoint URL to the iFrame URL?
In other words, if user comes by URL:
http://mainsite.com/default.aspx?email=1
then my iFrame should point to:
http:/iframesite.com/page.aspx?email=1, otherwise to http:/iframesite.com/page.aspx
I don't have development control over the CMS, only editorial one. Thanks in advance.
Are the parent and the child in different domains? If so, your only option is to set the proper URL in the parent site (the child can't get anything from it's parent if the parent is in a different domain, browsers don't allow that for security reasons).
I have a Joomla (nginx + mysql) site running as UI and some JSP (tomcat + mysql) handling calculation logic.
I want to integrate JSP pages in to Joomla as iframe. I succeeded doing that, but the question is:
How do I make JSP pages NOT visitable to public but only visitable via Joomla site?
For example,
Joomla site is under mydomain.com/Joomla
JSP pages are under mydomain.com/JSP
When a user visit mydomain.com/JSP in the browser, the user cannot see the JSP page(see error or empty page instead).
But when the user open mydomain.com/Joomla in the browser and go to the page that contains the JSP site within an iframe, the user can see the JSP page there.
I am thinking about changing folder/file owner and permission. Am I on the right track? How should I approach exactly?
Thanks,
Milo
You need to change the way you're currently workin on.
1) Use composent JUMI to create virtual Joomla component based on your scripts.
2) On each page add this code at the very beginning of each of your scripts:
<?php
defined( '_JEXEC' ) or die ('Restricted Access');
?>
It'll prevent users for loading directly your scripts without any active Joomla session.