Lets try keep this simple.
Given a SharePoint site (english) and a feature (localized with resource files) to English (default) and Czech (but could be any language).
Why do I need to install a Czech Site Collection to get the Czech localization strings to work. I thought localization worked from user context, IE: based on the currently logged on users regional settings which trickle through to the browser?
A feature is not really meant for "end users", but for site admins to roll out only. So localization files pertaining to the feature itself (i.e. description, title etc.) are shown in the language of the site collection. Any controls and aspx pages etc. you create though could be localized for the display language of the current user's browser, just use the normal ASP.NET way of doing this. To be able to have your site actually listen to the user's language preference you need to change the web.config of the web app also though by setting the globalization to auto like so:
<globalization fileencoding="utf-8" uiCulture="auto" culture="auto" />
Any aspx page needs to have Culture="auto" UICulture="auto" in the <%# Page directive.
Al off the above is an "excerpt" from Hristo Yankov's excellent article.
I believe a feature LCID will be related to the RootWeb.Locale.LCID of the Site Collection.
That said, you probably need to code your own logic to grab culture info and display your respective resource file.
Related
I Want to Show custom welcome screen when a user logs in to Dynamics CRM 2016. I searched and i just got how to disable welcome screen tour but i couldn't find how to show my own custom screen (message or HTML).
Any help is appreciated.
Thanks
Make a dashboard with a single large HTML web resource.
Place your content inside that HTML web resource.
Set that dashboard as the default for new users. Display a specific dashboard by default for a specific user role
You can also add your welcome page as HTML web resource, add its link to your sitemap and set this sitemap subarea as a default tab for every user.
EDIT (detailed description):
Create custom HTML web resource and publish it in CRM.
Edit your sitemap to contain link to newly created web resource. Sample configuration below:
Sample
In my case my web resource HTML name is "new_welcome.html"
Go to user's personal options and set your new site.map position to be your user's default tab. You may do this with CRM interface (separately for every user :()) or with the tools for personal options mass update (for example with User Settings Utility from XrmToolBox)
Sample results of above mentioned operations:
Solution of you problem is Announcements.
Its easy to configure and easy to circulate the information across all the users.
Follow the below links for more information about Announcement,
https://www.microsoft.com/en-us/dynamics/crm-customer-center/broadcast-announcements-to-an-entire-organization.aspx
I would suggest not to use announcements because of the following reasons:
It is legacy functionality from CRM 2011 version.
It does not support rich text formatting or html components, images, etc.
You still need to create custom web resource to present it to the end user (so from the work effort perspective it also does not make sense)
I have a portal in Liferay 6.2, and need to design the velocity template of a web content that must have a menu listing the pages (linked names) of the site where is present.
My questions are:
Is this possible?
What would be the correct way to do this?
Would it be better to make a portlet instead of a web content for this purpose?
Thanks for the help.
It feels a bit like you are trying to solve many problems in a single template - consider to compose the UI from many different elements (e.g. custom portlets) rather than building the one structure/template that fits all requirements.
That being said, as there's also the chance that your template doesn't do more than just displaying the current navigation: You have two options: The out-of-the-box Navigation portlet is quite configurable, you might be able to utilize that one instead of implementing anything yourself (check the configuration options).
And lastly, if you want to implement for yourself: Get hold of the themeDisplay object. With getLayout() you'll get the current page, while getLayouts() you'll get all pages of the current site and can enumerate them. However, there's one problem: You typically don't have access to the themeDisplay object from a CMS template. But there are several ways to still get to the data (search the Liferay forums for cms template themedisplay). Also, an Application Display Template will be a lot more powerful - and you can also check how the layouts collection is built - just search for usage of ThemeDisplay.setLayouts in Liferay's source code. But with ADT we're diverting from your original question.
Liferay offers a sitemap portlet out-of-the-box which lists pages of a site. You can configure it and define your own application display template (ADT).
I am trying to implement a static website using Liferay's WCM. I want content to be displayed in user specific/selected language.
I am not sure whether I have to write separate content for each language or is there any way by which Content will get translated to user specific language?
I have tried "Add translation" in web content but it seems to be not working.
Any help is appreciated.
There's no automatic translation to another language. If you choose "Add translation" in the Web Content Editor, you'll have to edit the translated version yourself. Then you can use the user's profile settings or the "Languages" portlet or just the URL to determine the language. If an article is available in the user's language, that version will be shown.
You can try the URL parameters by just adding the language code as the first part of the page. E.g. https://www.liferay.com/community brings you to the default version for your user profile (if you're logged in), while https://www.liferay.com/de/community shows the german (de) version of that site. Every content that is translated to german will show in german, while the content that's not translated will be shown in the default language.
There is an existing app in MOSS, which allows to create polls for a call center, operators fill them out as they call targeted customers. Then this Web app outputs the results of this poll.
Is it possible to change the interface language of this existing web app? Operators don't understand English. If it's not about language packs, it would still be easier for me to embed new names and labels, rather than rewrite in a system I am not familiar with.
Also, is it possible to change the authentication type from Windows authentication to regular username/password check (username and password will be stored in DB or somewhere only for this site)
If it is possible, can you direct me to some kind of tutorial, help or manual which would show how to do it?
On MSDN it's written that language can't be changed, but I'm not sure whether it's about the Web app language.
Thank you.
Have a look at chapter 4 in our free SharePoint Development Guidelines.
I have no mutch idea about web app language
But I shall share you the links for sql authentication
http://weblog.vb-tech.com/nick/archive/2006/06/14/1617.aspx
http://www.codeproject.com/KB/sharepoint/moss_enableforms.aspx
For SharePoint it is possible to create different web's in different languages. Not that i know you could use one web in different languages.
But, it may be funny or not, a crazy idea or not, but could work: before dumping rendered contents to user, maybe you could extract text values excluding form values, post them to Google or Bing translator and put back translated values? You can override global.asax file and use PreSendRequestContent to modify contents just before they are sent to client.
If your company is not huge and it's an intranet page, then, althought slower, but it could work. Better than nothing.
PreSendRequestContent. This event
signals that content is about to be
sent to the client. This provides an
opportunity to modify the content
before it is sent.
We are researching the various options that exist in our environment to create an Employee Directory. We have a SharePoint portal, AD and recently moved from Lotus Notes to Exchange. Our current employee search is a custom Notes DB that has since been retired.
Since moving to SharePoint an year ago, we've used a custom list using SharePoint Profiles that are updated from AD. But the simple list interface isn't very user friendly and is very slow. Sone of the requirements include type-ahead, pictures, and details of skills/certifications and other demographic information etc. We are considering building an ASP.NET or SilverLight application that can consume the information in the SharePoint list. With the introduction of Outlook and the Global Address List, we are now wondering if it might be easier to build something within Outlook.
Has anybody traveled a similar path and what would you advice us to do?
Microsoft has a huge set of offerings for Collaboration and Social Computing in Sharepoint.
See this document, pages 8 and 9 for information about features related to an employee directory, including details of skills/certifications and other demographic information.
A la carte availability of individual features (such as People Profiles and People Search) and pricing may be an issue, but you may want to look into buying something rather than building it (if you can get the pieces you want for a price you can afford).
Sharepoint can connect with Outlook to keep the lists synchronized if you want to use outlook. And there are definitely a lot of different ways to change the way the lists are presented in the Sharepoint portal to make them more user-friendly. Having those details on the portal will certainly be a boon when combined with the powerful search and indexing features in SharePoint so you can identify employees based on their profile details easily.
We use the people search for this pretty effectively. We populate data in AD, then connect profile properties to AD attributes. That's only if you have MOSS, though. If you're working with WSS, you'll have to build something more custom.
One gotcha, though, is that the People Search out of the box doesn't easily do partial searches (i.e. searching for "john" doesn't match "johnson"). That's a big downer in my mind. You can use Ramon Scott's approach of a Content Editor Webpart with a form and some Javascript to work around it, and you can also get there via the advanced search box (albeit indirectly), but it sure would be nice if it were easy to make the default search box do partial name searches.
I recently just discoverd a somewhat easy visual basic script that draws information from the active directory where you can specify which OU to draw from where it displays all user information in a simple .HTM page. it includes a search bar, recognizes patterns (address) (company telephone number) etc... If you would like i can post it for you. you only need to fill in a few sections (display name for directory, OU, OU display, and tags) and you can always change the way things look too.
This should be taken care of by using the My Site feature that's available within SharePoint. You will then be able to search SharePoint users by skills, certifications, projects, and educational qualification.
Please refer to the SharePoint Planning and Deployment material on TechNet for more info.
SH.