I have a multilingual site and use the Related Pages functionality here and there. What I've noticed is that related pages are not localized, meaning if I add a related page for the U.S. site, that page will be related to the U.K. site as well. And that's not what I want.
Is there a way to restrict Related Pages to only pages that are available in the current culture?
You can restrict relationship per site, but not per culture. you define relationship between tree nodes - not between documents.
You can restrict per site when you create relationship name (this include 2 tables CMS_RelationshipNameSite and CMS_RelationshipName) and name will be available when you create relationship between pages. Behind the scenes all sites use View_CMS_Relationship_Joined: So if a relation between 2 pages is already defined - it doesn't matter whether this relationship name is enabled for your site or not.
Relationships Module is sealed - so you will not be able to add culture.
That being said you can create your own custom form control and use custom table to define relationship between pages the way you want. As far as I understand you need document to document not node to node
Related
Does Liferay Service Builder peristence provide mechanism for isolating stored data into separate portlet instance specific (portlet added into two separate pages) tables?
If it is not possible what is the preferred approach to avoid mixing portlet data on two different portal pages?
As this is stackoverflow and related to anything with source code: You can create that single scope yourself - Liferay's scope is just on "group". Any other criteria that you add to the data can be there, but the filtering needs to be handled by you.
A non-programming way to achieve your goal is to open a subscope for your portlet. This can be inspected with (for example) the MessageBoards portlet: In its configuration you can select if you want the scope to be the "Site" or the "Page". Effectively this creates a new "group" (the API name for the scope) and you can just handle the data as if they were in a completely different site.
This illustrates one of the reasons why the API calls it groupId and not siteId, because it's not limited to denote a site.
Does anyone know if it is possible to share data between sites on a Kentico platform, such as news articles? I have tried searching but could not find an answer.
Thank you,
Yes. If you want the content to be the same and keep the URLs and Domains separate, then this is best accomplished with linked documents between the sites. This way if they are updated on either site, they will remain in sync on the other site. Read more here: https://docs.kentico.com/k9/managing-website-content/working-with-pages/copying-and-moving-pages-creating-linked-pages
https://docs.kentico.com/k9/e-commerce-features/managing-your-store/products/linking-existing-products-or-sections
Basically what you'd want to do in your content tree, is click "new page" and then select "Link an existing page" from the bottom of the next menu. After that, you will see a content tree to select a page from. Use the site selector in the top left to choose a different site, and then select the page you'd like to link in.
Note: Keep in mind that the page type will need to be allowed in that section of the tree (for example, if you are trying to nest a news article under a folder but folders are not an allowed parent type, you will get an error).
If you'd like to pull data from another site in via repeater and leave the content on the other site, then you can user a repeater or similar viewer control, and specify a site within the properties in order to pull the pages from the other site.
Each of these methods assumes the Kentico sites are on the same instance of Kentico with a shared database.
If you have multiple sites in one Kentico instance, in your repeater getting the news articles, specify the site you want to get the news articles from and it will be displayed on that site. If you want to combine them then create a custom query and use the query repeater to show the news articles.
I am beginning sharepoint development and have some quick questions concerning basic terms.
How do i find out whether a particular site is a site collection, or a site JUST BY THE URL? Is their a powershell command to do this?
I was creating some sites in sharepoint. Some sites were appended with /sites/sitename whereas others were just under the base url of sharepoint. What is the difference between the 2? AND, how do i recreate the ones under the sites node? For some reason, I cant find the option to create under the sites node again. Please explain this concept as all msdn tutorial are very confusion for beginners like me. Those are good once you get the hang of basics.
Please provide an analogy how to understand web app, site collection, site, web site, etc.
Is there a way to use NEWFORM.aspx for a document library instead of UPLOAD.aspx?
The Site collection is at the root level of your Web application.
So http://abc.com/ => Site collection
Using Powershell, open the Sharepoint Powershell prompt and run Get-SPSite to get all Site-Collections
the /sites/ is called as a managed path
It can be defined in the Central Administration for every web application.
The option to select the /sites will be available only when you create the second site collection under the Web Application (The first one take the / by default.)
Have a look at Technet Article
document library is for uploading file, not for storing user submitted data, for that you need to create a list
1) Document Set is used in cases where multiple documents have the same properties, its like putting all these documents in a folder and then providing attributes to that folder which are in turn applied for each document in that folder.
In your case, if all the files have the same values for the 8 fields then the document set is the correct way to go.
2)If there is additional metadata associated with the files then these can be added either to the content type (eg. document or document set content type) or to the columns in the library itself, you dont need to create a separate list for holding that data. Adding data to the content type ensures consistency across all the document libraries within that site collection, adding columns to the library affects only that library.
Is there a canonical list (public or private-that-you're-willing-to-share) of Magento objects (and their database persistance tables) that allow you add Layout XML Updates to the system? I realize there's an almost infinite number with third party modules, but I'm specifically interested in what ships with CE, Professional, and Enterprise Edition.
In case that's not clear, consider Magento's CMS pages. In the CMS admin there's a textarea for
Layout Update XML
in the Design tab.
This XML is persisted to the database with the CMS Page object, and these updates are added to the Layout object when that page is loaded.
There's multiple places in the Magento admin where this happens. I'm looking for a list of all of them.
I had trouble filtering by a specific branch with Google's search operators, but this is a decent start: https://www.google.com/search?q=%22custom_layout_update%22+site%3Asvn.magentocommerce.com
Not many that I can see,
Mage/Catalog/Model/Category.php
Mage/GoogleBase/Model/Attribute.php
And the CMS module as mentioned above.
I have an intranet on the Drupal platform. I am using permission to restrict access to certain node types that have sensitive information in them. This is all working nicely.
However, some of theses sensitive nodes use taxonomy as a method of categorization. The problem is, I have found certain paths, apparently created by the taxonomy module itself, that show teasers of these sensitive nodes, even to unauthenticated users.
for example:
mysite.com/category/traintype/site
Shows the companies training appointments where the training type is onsite. These nodes are set so that they should not be accessible to users of a certain roles, and certainly not to unauthenticated users.
I have looked through Views on the site, and I don't see any taxonomy views. So, how can I make these paths inaccessible?
Another method is to alter node.tpl.php to strip the teaser if the user does not have access.
You can use hook_menu() or hook_menu_alter() in a custom module to overwrite the default menu item that is created by the taxonomy module. Here you can add your own extra permission check or remove it altogether.