I am using Sitecore 7.2(rev. 140228), I have multiple sites & all of them have their own content store or meta-data. Now I wants to give them choice to select datasource either from own meta-data of other site. Although I know another option to make meta-data global outside of all site but in my case it's not an option.
I have wrote an simple Xpath query:
./ancestor::*[##templatename="Main section"]/*[##templatename="SiteFolder"]//*[##templatename="ContentStore"]
Which return me valid result in Sitecore rocks that I wants as below
But when i updated this in my rendering's data source field it returns just first instead of both.
Is there any way to show multiple datasource here.
Thanks ,
There is a bug in early verions of Sitecore 7.x - mutliple roots are not supported for datasource selection.
The issue was fixed in Sitecore 7.2 rev 140526. Check reference number 389483 in Sitecore 7.2 rev 140526 release notes.
If you cannot upgrade to the next version, you may want to contact Sitecore Support - I had the same issue and they sent me a patch which worked for me.
Related
I'm currently encountering a weird behavior of sharepoint in my current project.
The task is simple in its core:
We have a site collection, where we can create projects (projects are then subsites of the root site again). In v1 our product was only available in one language. In v2 we implement multilanguage.
When the new solutions are deployed, new project site are in the correct state.
The rootsite and older project sites are not.
I'm currently developing the update mechanism for the root and subsites.
And here somethin unexplainable (at least for me) happens:
Navigation:
The navigation nodes have to be updated the following way
foreach (CultureInfo culture in web.SupportedUICultures)
{
node.TitleResource.SetValueForUICulture(culture, SPUtility.GetLocalizedString("$Resources:" + key, resource, (uint)culture.LCID));
}
node.Update();
When I initiate the update while having german as my active display language, exactly 2 nodes are shown as $Resources:.... in german, but in english they are correct.
If i initiate the update while having english as my display language, all nodes are correct in both languages.
Listviewwebpart
On one page we introduced a few listviewwebparts. I create them and customize the view of the webpart. When I start the update with english as language, everything works fine.
The listview is completely translated both in german and english.
However, the moment i let the update run with german as active language, some fields are not translated. And here is the thing: Only in this exact listview! When i switch to the list, and check the fields, everything is ok!
I don't get it.
So in short:
- Update with german: 2 Navigation don't get the resource value (just german, english works fine)
- Update with english: Fields in listview not translated, but the fields are translated in its core.
Did someone ever encountered a behavior like this?
I tried changing the order in which the update works, but nothing changes.
When searching through files indexed using Windows Desktop Search,
it would be nice if I could see a snippet of the text within the
document that is related to the search text. However when I try to
retrieve "System.Search.QueryFocusedSummary" or
"System.Search.QueryFocusedSummaryWithFallback " I get a
"column name not found" error.
(The code that I am using to query this is shown in this question:
Microsoft Desktop Search - CONTAINS not returning results on windows server 2008 )
This is confusing because when you do a search within explorer,
you get the snippet of text in your results. So it's possible somehow.
According to this documentation http://msdn.microsoft.com/en-us/library/windows/desktop/bb760171%28v=vs.85%29.aspx
it should be retrievable, the same that AutoSummary is.
This question has already been asked on MSDN here:
http://social.msdn.microsoft.com/Forums/en-US/windowsdesktopsearchdevelopment/thread/dcfb40ea-b250-4294-80d0-727c7365745e/
but I'm hoping that the clever stackoverflow people can help me.
As a side note, I'm quite confused as to why this doesn't work, don't lots of
people need to index and search documents? Does everyone use Lucene and/or Solr
or Windows Search Server instead?
A colleague of mine ran into this problem recently. QueryFocusedSummary and QueryFocusedSummaryWithFallback are indeed not accessible via OLEDB. They are, however, accessible via Shell.
In the Windows SDK, there is a sample, $WIN_SDK/Samples/winui/shell/appplatform/ExplorerBrowserSearch, which will get you set up on using Shell functions to perform a search. From here, it should be trivial to add support for QueryFocusedSummary and QueryFocusedSummaryWithFallback via the Shell Property Keys PKEY_Search_QueryFocusedSummary and PKEY_Search_QueryFocusedSummaryWithFallback respectively.
Since you didn't post any code I have to speculate a bit...
I assume you are using OleDB/SQL to execute a query...
Neither QueryFocusedSummary nor QueryFocusedSummaryWithFallback are real columns and thus NOT available via OleDB/SQL !
The only columns available this way are AFAIK
AutoSummary
Contents
EntryID
GatherTime
Rank
Store
QueryFocusedSummary and QueryFocusedSummaryWithFallback are IIRC properties accessiable via COM or a Shell interface .
Sorry if I will ask the question that already exists or just has easy solution, i'm just a new comer to Sharepoint.
The question relates to Sharepoint 2007 search engine.
I have a few crawled properties and correspond managed properties. I need to crawling all these properties, but without one property!
I have own xsl and I use own presentation of search results, but it so similar to native SP presentation. And there i use "Description" SP property (isn't mine), which show me all my properties (it's values), and it's ok, but i need to exclude only one property from the "Description" property in the search results.
Could you give me explanation of how to do this by the code (.NET) or maybe good advices and references?
Thanks in advance!
I already found out the solution. In the SP UI we can uncheck "Include values for this property in the search index" checkbox of crawl properties. And these properties will removed from search results in SP "Description" property. And it isn't hard to found out the way how to do this programmatically.
Thanks to all anyway.
Hi All I am having this problem. Locally everything is working fine. Once I upload the published version on production the IDs of all elements will have a different prefix.
I know that the prefix is caused by using master pages, but why it is different from local to production?
See Image
alt text http://img.skitch.com/20100708-pg6exce3jd6f3dga2huse1u7pi.jpg
This happens. The lesson to be learned is don't rely on "hardcoded" client-side control ids. That's why asp.net gives you the Control.ClientID property. Use it in place of your hard-coded value.
I agree with Matt-dot-net, dont use hardcoded client-side control ids.
However, check your dev/production web.configs for xhtmlConformance mode="Legacy" (or something similar), if only one of your configs has this set then it may account for you having different ids on dev and production .
Cheers Tigger
First, some background to my problem.
There are many versions of Internet Explorer 6 and 7 that do not support more than 20 Key-Value pairs in a cookie. I have a list of full versions that do and do not support this. This is fixed in a windows update, but it's not possible for me to force the users of my app to carry out windows update in order to use my app.
We have developed a different cookie jar for versions of Internet Explorer that do not support this, however the performance of this is not optimal, and therefore we need to only use this on versions of IE that require it.
The full version number of an IE browser is in the format 6.00.2900.2180. Everywhere I have found suggests using Request.Browser to find out browser information, but this is far too limited for my needs. To clarify this, MajorVersion returns 6, and MinorVersion returns 0, giving me 6.0 (6.0 is the version of pretty much every version of Internet Explorer 6 that exists). So what I need is the third and fourth parts (or at the very least, the third part) of the full version.
So, does anyone know of a way, in ASP.Net with C#, to find out the information I need? If someone has looked extensively into this and found it to impossible, that is fine as an answer.
You may need to revisit why you're storing so many different key-value pairs. Going low-tech, couldn't you concatenate the values into fewer or maybe even a single key? What sort of values are you storing--in a cookie?
Try grabbing the "User-Agent" request header using Request.Headers
Copying this from meandmycode to accept it as answer.
IE doesn't specify the long version
number in the user-agent header so you
have absolute no chance of detecting
this other than sending a 'snoop' page
with javascript to detect the complex
version number.. but doing something
like that is dodge city, and
javascript may not be able to find the
full version either.