FEED Validator

for Atom and RSS and KML

Congratulations!

This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 1, column 494: Self reference doesn't match document location [help]

... rel="self" type="application/rss+xml" /><link>https://jinkang.us</link>  ...
                                             ^

line 1, column 1054: Use of unknown namespace: com-wordpress:feed-additions:1 (5 occurrences) [help]

... >32</width> <height>32</height> </image> <site xmlns="com-wordpress:feed ...
                                             ^

line 1, column 16820: style attribute contains potentially dangerous content: background-image [help]

... s">blog about technology...</a>.</p> ]]></content:encoded> <wfw:commentR ...
                                             ^

line 1, column 16820: content:encoded should not contain data-recalc-dims attribute (5 occurrences) [help]

... s">blog about technology...</a>.</p> ]]></content:encoded> <wfw:commentR ...
                                             ^

line 1, column 27105: content:encoded should not contain sizes attribute (4 occurrences) [help]

... s">blog about technology...</a>.</p> ]]></content:encoded> <wfw:commentR ...
                                             ^

Source: http://feeds.feedburner.com/BlogAboutTechnology

<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" ><channel><title>blog about technology…</title> <atom:link href="https://jinkang.us/feed/" rel="self" type="application/rss+xml" /><link>https://jinkang.us</link> <description>#Azure #Office365 #SharePoint #Cloud #Geek</description> <lastBuildDate>Thu, 18 Aug 2016 13:46:46 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>https://wordpress.org/?v=4.7.5</generator><image> <url>https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/favicon.gif?fit=16%2C16&ssl=1</url><title>blog about technology…</title><link>https://jinkang.us</link> <width>32</width> <height>32</height> </image> <site xmlns="com-wordpress:feed-additions:1">114701447</site> <item><title>Microsoft Releases SharePoint Framework Developer Preview!</title><link>https://jinkang.us/2016/08/18/microsoft-releases-sharepoint-framework-developer-preview/</link> <comments>https://jinkang.us/2016/08/18/microsoft-releases-sharepoint-framework-developer-preview/#comments</comments> <pubDate>Thu, 18 Aug 2016 13:46:46 +0000</pubDate> <dc:creator><![CDATA[Jin Kang]]></dc:creator> <category><![CDATA[Office 365]]></category> <category><![CDATA[SharePoint Online]]></category> <category><![CDATA[cloud]]></category> <category><![CDATA[office365]]></category> <category><![CDATA[sharepoint]]></category> <category><![CDATA[sharepointonline]]></category> <category><![CDATA[spfx]]></category> <category><![CDATA[spfx-tooling]]></category> <category><![CDATA[spfx-webparts]]></category><guid isPermaLink="false">https://jinkang.us/?p=79</guid> <description><![CDATA[Microsoft just made the SharePoint Framework Developer Preview available via GitHub which was originally announced back in May 2016. Please see the links below for more details: Dev Center announcement: https://dev.office.com/blogs/sharepoint-framework-developer-preview-release GitHub repository: https://github.com/SharePoint/sp-dev-docs/wikiThe post <a rel="nofollow" href="https://jinkang.us/2016/08/18/microsoft-releases-sharepoint-framework-developer-preview/">Microsoft Releases SharePoint Framework Developer Preview!</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></description> <content:encoded><![CDATA[Microsoft just made the SharePoint Framework Developer Preview available via GitHub which was originally announced back in May 2016. Please see the links below for more details:Dev Center announcement: <a href="https://dev.office.com/blogs/sharepoint-framework-developer-preview-release">https://dev.office.com/blogs/sharepoint-framework-developer-preview-release</a> GitHub repository: <a href="https://github.com/SharePoint/sp-dev-docs/wiki">https://github.com/SharePoint/sp-dev-docs/wiki</a>The post <a rel="nofollow" href="https://jinkang.us/2016/08/18/microsoft-releases-sharepoint-framework-developer-preview/">Microsoft Releases SharePoint Framework Developer Preview!</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></content:encoded> <wfw:commentRss>https://jinkang.us/2016/08/18/microsoft-releases-sharepoint-framework-developer-preview/feed/</wfw:commentRss> <slash:comments>1</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">79</post-id> </item> <item><title>OneDrive for Business – Configurable Retention Period for Orphaned OneDrives!</title><link>https://jinkang.us/2016/08/11/onedrive-for-business-configurable-retention-period-for-orphaned-onedrives/</link> <comments>https://jinkang.us/2016/08/11/onedrive-for-business-configurable-retention-period-for-orphaned-onedrives/#respond</comments> <pubDate>Thu, 11 Aug 2016 19:05:38 +0000</pubDate> <dc:creator><![CDATA[Jin Kang]]></dc:creator> <category><![CDATA[Office 365]]></category> <category><![CDATA[SharePoint Online]]></category> <category><![CDATA[cloud]]></category> <category><![CDATA[office365]]></category> <category><![CDATA[sharepointonline]]></category><guid isPermaLink="false">https://jinkang.us/?p=71</guid> <description><![CDATA[Hello again! It’s a well-known fact in On-Premise SharePoint world that ever since SharePoint 2010, My Site Clean Up Timer Job is set to 14 days retention period before the My Site is deleted, and there’s nothing you can do about that other than disable the timer job and/or write your […]The post <a rel="nofollow" href="https://jinkang.us/2016/08/11/onedrive-for-business-configurable-retention-period-for-orphaned-onedrives/">OneDrive for Business – Configurable Retention Period for Orphaned OneDrives!</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></description> <content:encoded><![CDATA[Hello again! It’s a well-known fact in On-Premise SharePoint world that ever since SharePoint 2010, My Site Clean Up Timer Job is set to 14 days retention period before the My Site is deleted, and there’s nothing you can do about that other than disable the timer job and/or write your own timer job. Matter of fact, I recall at countless SP conferences where they would recommend that you disable this timer job and handle retention via custom process so you can have more visibility and control. In SharePoint Online world, this was changed to 30 days and if you’re like me and have corporate retention policies that are longer than 30 days, you would have to go thru series of workarounds to extend the retention period by leaving the Office 365 account active one way or another.Well let me tell you that the days of that for at least SharePoint Online are gone now! I was surprised to see that the May 2016 release of the SharePoint CSOM (v 16.1.5312.1200) introduced a new property called OrphanedPersonalSitesRetentionPeriod that allows you to Get or Set the default retention days to OneDrive for Business sites. Even better, the values can be set between 30 to 3650. That’s measured in DAYS! Which means max value is 10 years!!I’m glad Microsoft has added this option as it now gives a lot of flexibility for organizations to ensure OneDrive retention meets their corporate retention policies.Easiest way to change the retention is via SharePoint Online PowerShell commands: …and you can download the latest SharePoint Online PowerShell from <a href="https://www.microsoft.com/en-us/download/details.aspx?id=35588">here</a>#Connect to SharePoint Online Admin (change URL to your SPO tenant Admin URL) Connect-SPOService -Url https://contoso-admin.sharepoint.com -Credential (Get-Credential) #Set Retention period – change the value of ‘3650’ to value you prefer Set-SPOTenant -OrphanedPersonalSitesRetentionPeriod 3650 #Run the following command to confirm value has been applied (Get-SPOTenant).OrphanedPersonalSitesRetentionPeriod Here are some links to where you can find out more about this:<ul><li>SharePoint CSOM release (May 2016) – <a href="https://dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-may-2016">https://dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-may-2016</a></li><li>SharePoint Online PowerShell command (Set-SPOTenant) – <a href="https://technet.microsoft.com/en-us/library/fp161390.aspx">https://technet.microsoft.com/en-us/library/fp161390.aspx</a></li><li>How User Profiles are deleted in SPO and OneDrive for Business – <a href="https://support.microsoft.com/en-us/kb/3042522">https://support.microsoft.com/en-us/kb/3042522</a></li></ul>Good luck!The post <a rel="nofollow" href="https://jinkang.us/2016/08/11/onedrive-for-business-configurable-retention-period-for-orphaned-onedrives/">OneDrive for Business – Configurable Retention Period for Orphaned OneDrives!</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></content:encoded> <wfw:commentRss>https://jinkang.us/2016/08/11/onedrive-for-business-configurable-retention-period-for-orphaned-onedrives/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">71</post-id> </item> <item><title>Cloud Hybrid Search – Differentiate On-Premise and Cloud Search Results</title><link>https://jinkang.us/2016/08/10/cloud-hybrid-search-differentiate-premise-cloud-search-results/</link> <comments>https://jinkang.us/2016/08/10/cloud-hybrid-search-differentiate-premise-cloud-search-results/#respond</comments> <pubDate>Wed, 10 Aug 2016 21:22:35 +0000</pubDate> <dc:creator><![CDATA[Jin Kang]]></dc:creator> <category><![CDATA[Office 365]]></category> <category><![CDATA[Search]]></category> <category><![CDATA[SharePoint]]></category> <category><![CDATA[SharePoint 2013]]></category> <category><![CDATA[SharePoint 2016]]></category> <category><![CDATA[SharePoint Online]]></category> <category><![CDATA[cloud]]></category> <category><![CDATA[hybrid]]></category> <category><![CDATA[office365]]></category> <category><![CDATA[search]]></category> <category><![CDATA[sharepoint]]></category> <category><![CDATA[sharepoint2013]]></category> <category><![CDATA[sharepoint2016]]></category> <category><![CDATA[sp2013]]></category> <category><![CDATA[sp2016]]></category><guid isPermaLink="false">https://jinkang.us/?p=65</guid> <description><![CDATA[Greetings! It’s been a couple weeks since my last blog post so I thought I would share another area that may be helpful in your quest to deploy the Cloud Hybrid Search. As you know, one of the benefits of SharePoint Online is the ability for users to access it […]The post <a rel="nofollow" href="https://jinkang.us/2016/08/10/cloud-hybrid-search-differentiate-premise-cloud-search-results/">Cloud Hybrid Search – Differentiate On-Premise and Cloud Search Results</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></description> <content:encoded><![CDATA[Greetings!It’s been a couple weeks since my last blog post so I thought I would share another area that may be helpful in your quest to deploy the Cloud Hybrid Search. As you know, one of the benefits of SharePoint Online is the ability for users to access it from anywhere in the world, via trusted network (i.e. VPN, corporate network) or non-trusted network (i.e. home, cafe). This creates a bit of an issue for end users using the Cloud Hybrid Search Center as the returned results will be a merge of both cloud and on-premise results. If you are accessing SharePoint Online via non-trusted network and have not implemented a way for users to access the on-premise search result URLs via some means like reverse proxy… you’ll get an error message like “Network Error (dns_unresolved_hostname)” at least on Chrome. Not only that, it is not very easy to distinguish what’s cloud results and what’s on-premise results. Now the best solution is to implement something like reverse proxy to allow users to seamlessly access on-premise contents, however, there may be several reason why you may not want to do this such as corporate security policies, lack of funding, etc.So what I have done to help our customers is to append an indicator to all on-premise results on the Search Results Web Part. This way, users can at least distinguish what results are on-premise and require trusted network access. Before I go any further explaining how I achieved this, let me first give credit where credit is due. The code to achieve this is borrowed heavily from <a href="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2013/12/31/using-display-templates-to-feature-new-search-results-in-sharepoint-2013.aspx">Corey Roth’s blog post</a>.For the following Display Templates on the Search Center site collection: you can locate the display templates by going to Site Collection – Site Settings –> Master pages and page layouts –> Display Templates –> Search (download the following three files and open them in your favorite editor) <ul><li>Item_CommonItem_Body.html</li><li>Item_BestBet.html</li><li>Item_Discussion.html</li></ul>I inserted this in the main script block:function extractDomain(url) { var domain; //find & remove protocol (http, ftp, etc.) and get domain if (url.indexOf(“://”) > -1) { domain = url.split(‘/’)[2]; } else { domain = url.split(‘/’)[0]; } //find & remove port number domain = domain.split(‘:’)[0]; return domain; } var extContRegExPtn = new RegExp(/(contoso|contosocorp|ccontosonet){1}.net\/*.*/g); <— modify this RegEx expression to match your URL patterns var isExtCont = false; var extContUrl = extractDomain(ctx.CurrentItem.Url); if (extContRegExPtn.test(extContUrl)) { isExtCont = true } And then for Item_CommonItem_Body.html, locate the _#= titleHtml =#_ and insert the following code to append the indicator right after the Title of each search results that match on regular expression defined in the javascript we inserted to the main script block<!–#_ if (isExtCont) { _#–> VPN Required <—replace this value with anything you’d like <!–#_ } _#–>For “Item_BestBet.html”, locate the _#= title =#_ and insert the code. For “Item_Discussion.html”, locate the _#= Srch.U.trimTitle(title, maxTitleLengthInChars, termsToUse) =#_ and insert the code.Save your changes and re-upload them to the master page and layouts library. Also, don’t forget to check-in the file and publish it.Here’s what it looks like in the end. As you can see, the first result is on-premise result and it appended the “VPN Required” indicator. It will also do the same for Best Bet results (i.e. promoted results via Query rule) and results under the “Conversations” search tab.<a href="https://i2.wp.com/jinkang.us/wp-content/uploads/2016/08/Untitled.png?ssl=1"><img style="background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border: 0px;" title="Untitled" src="https://i1.wp.com/jinkang.us/wp-content/uploads/2016/08/Untitled_thumb.png?resize=369%2C235&ssl=1" alt="Untitled" border="0" data-recalc-dims="1" /></a>I hope this has been helpful! Good luck and if you have any questions, feel free to leave comments below.The post <a rel="nofollow" href="https://jinkang.us/2016/08/10/cloud-hybrid-search-differentiate-premise-cloud-search-results/">Cloud Hybrid Search – Differentiate On-Premise and Cloud Search Results</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></content:encoded> <wfw:commentRss>https://jinkang.us/2016/08/10/cloud-hybrid-search-differentiate-premise-cloud-search-results/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">65</post-id> </item> <item><title>How Do I Get Local Search Working With Sharing Cloud Search Service Application in SharePoint 2013</title><link>https://jinkang.us/2016/07/29/get-local-search-working-sharing-cloud-search-service-application-sharepoint-2013/</link> <comments>https://jinkang.us/2016/07/29/get-local-search-working-sharing-cloud-search-service-application-sharepoint-2013/#comments</comments> <pubDate>Fri, 29 Jul 2016 20:30:37 +0000</pubDate> <dc:creator><![CDATA[Jin Kang]]></dc:creator> <category><![CDATA[Office 365]]></category> <category><![CDATA[Search]]></category> <category><![CDATA[SharePoint]]></category> <category><![CDATA[SharePoint 2010]]></category> <category><![CDATA[SharePoint 2013]]></category> <category><![CDATA[SharePoint 2016]]></category> <category><![CDATA[SharePoint Online]]></category> <category><![CDATA[cloud]]></category> <category><![CDATA[hybrid]]></category> <category><![CDATA[office365]]></category> <category><![CDATA[search]]></category> <category><![CDATA[sharepoint]]></category> <category><![CDATA[sharepoint2010]]></category> <category><![CDATA[sharepoint2013]]></category> <category><![CDATA[sharepoint2016]]></category> <category><![CDATA[sp2010]]></category> <category><![CDATA[sp2013]]></category> <category><![CDATA[sp2016]]></category><guid isPermaLink="false">https://jinkang.us/?p=41</guid> <description><![CDATA[So it has been few months since official mark of General Availability (GA) for Cloud Hybrid Search on SharePoint 2013 and 2016. As you may know, it has been in Preview shortly after the big announcement at Ignite last year and has been an highly anticipated feature for customers who like myself are […]The post <a rel="nofollow" href="https://jinkang.us/2016/07/29/get-local-search-working-sharing-cloud-search-service-application-sharepoint-2013/">How Do I Get Local Search Working With Sharing Cloud Search Service Application in SharePoint 2013</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></description> <content:encoded><![CDATA[So it has been few months since official mark of<a href="https://blogs.office.com/2016/03/14/sharepoint-2016-rtm-and-the-future-of-sharepoint-event/"> General Availability</a> (GA) for Cloud Hybrid Search on SharePoint 2013 and 2016. As you may know, it has been in Preview shortly after the big announcement at Ignite last year and has been an highly anticipated feature for customers who like myself are stuck in a hybrid limbo. Since then, there has been flood of blog posts by others to share their thoughts, findings from their own testing with SharePoint 2016, and various How-To guides for folks like myself to try it out.Well I won’t bore you to death by writing another how-to guide as I think there’s plenty of good articles out there now. Instead, I’ll share a few links to articles that I’ve used to successfully install and configure Cloud Hybrid Search for Office 365 and share with you one particular challenge I faced with local search (i.e. local site search, library search, etc.) and how I was able to solve it.Here are few helpful links:<ul><li><a href="https://support.office.com/en-us/article/Plan-cloud-hybrid-search-for-SharePoint-33926857-302c-424f-ba78-03286cf5ac30?ui=en-US&rs=en-US&ad=US">Plan cloud hybrid search for SharePoint</a></li><li><a href="https://technet.microsoft.com/en-us/library/dn720906.aspx?f=255&MSPPError=-2147217396">Configure cloud hybrid search</a></li><li><a href="https://blogs.msdn.microsoft.com/spses/2015/09/15/cloud-hybrid-search-service-application/">Cloud Hybrid Search Service Application</a></li></ul>If you’re like me and have a <a href="https://www.microsoft.com/en-us/download/details.aspx?id=34976">Multi-farm architecture</a> with combination of SharePoint 2010 and/or SharePoint 2013 and a dedicated enterprise services farm and/or dedicated search farm, all message at the Ignite 2015 suggested the Cloud Search Service Application (SSA) will work right out the box just the way traditional Search SSA has been working simply by publishing the service application from the Search farm and consuming it from the Content farm after following some prerequisite steps (exchange certificate, setting some permissions, etc.). Well… this is not exactly true… everything about the Cloud SSA was working (able to index all on-premise contents, was able to query on-premise contents from o365, etc.) BUT I wasn’t getting any search results from local site search or list/document library search. See below for screenshots of what I was seeing…O365 Search Center – result from on-prem site collection: (found file: 1234_XYZ.txt)<img class="alignnone size-medium wp-image-48" src="https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-08-47.png?resize=300%2C148&ssl=1" alt="2016-07-29_15-08-47" srcset="https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-08-47.png?resize=300%2C148&ssl=1 300w, https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-08-47.png?w=735&ssl=1 735w" sizes="(max-width: 300px) 100vw, 300px" data-recalc-dims="1" />On-Prem local search result: (did not find file: 1234_XYZ.txt)<img class="alignnone size-medium wp-image-49" src="https://i0.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-10-37.png?resize=300%2C157&ssl=1" alt="2016-07-29_15-10-37" srcset="https://i0.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-10-37.png?resize=300%2C157&ssl=1 300w, https://i0.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-10-37.png?w=725&ssl=1 725w" sizes="(max-width: 300px) 100vw, 300px" data-recalc-dims="1" />But sometimes I was getting search results on my on-prem site… odd!<img class="alignnone size-medium wp-image-50" src="https://i0.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-11-33.png?resize=300%2C118&ssl=1" alt="2016-07-29_15-11-33" srcset="https://i0.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-11-33.png?resize=300%2C118&ssl=1 300w, https://i0.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-11-33.png?w=759&ssl=1 759w" sizes="(max-width: 300px) 100vw, 300px" data-recalc-dims="1" />I initially thought… I must have missed a step in my configuration for cross-farm service application for Cloud SSA so I double checked all my steps and even re-configured it all. … and I had the same problem…I then tried it on a different content farm … and I had the same problem…All I could think at this point was there’s either a bug or this isn’t suppose to work… And if you haven’t read any of the articles I linked earlier, all it recommends is refer you to a 2 year old TechNet article on how to configure your farm for cross-farm service application in scenarios like this.I then looked at how Cloud SSA works and discovered that Cloud SSA farm doesn’t actually retain its own local index (which makes sense!). During this period, I stumbled on this old <a href="https://blogs.msdn.microsoft.com/sambetts/2014/10/10/setup-hybrid-sharepoint-online-on-premise-search-federation-a-quick-guide/">article</a> discussing how to configure your traditional Search SSA for search federation with SharePoint Online. In this article, I realized that you needed to configure a Remote SharePoint Result Source pointing to our Office 365 tenant and set it to default to reroute all search query requests. Duh! it all makes sense now since Cloud SSA farm doesn’t have it’s own search index.You will need to define this new result source at the Cloud SSA. Here’s how you do this…<ol><li>Go to Central Administration of Cloud SSA farm</li><li>Go to Application Management –> Manage service applications</li><li>Locate your Cloud SSA and go to Search Administration page</li><li>From the list of links to the left of the page, go to Result Sources</li><li>Click on New Result Source<ol><li>Name: provide a name</li><li>Protocol: Remote SharePoint</li><li>Remote Service URL: https://<yourtenantname>.sharepoint.com</li><li>Type: SharePoint Search Results</li><li>Query Transform: default </li><li>Credentials: default</li></ol></li><li>Click Save</li><li>Locate your new Result Source and click on drop down arrow and select Set as Default</li><li>You’re done! The changes should be effective immediately</li></ol>Here’s what my result source looks like after I created the new “SharePoint Online Results”.Well that is all for now. I hope you had a smoother experience then I had implementing Cloud SSA and I hope this provides some assistance to those that are in similar situation.<img class="alignnone size-medium wp-image-52" src="https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-25-26.png?resize=300%2C214&ssl=1" alt="2016-07-29_15-25-26" srcset="https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-25-26.png?resize=300%2C214&ssl=1 300w, https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-25-26.png?resize=768%2C548&ssl=1 768w, https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-25-26.png?resize=1024%2C731&ssl=1 1024w, https://i2.wp.com/jinkang.us/wp-content/uploads/2016/07/2016-07-29_15-25-26.png?w=1182&ssl=1 1182w" sizes="(max-width: 300px) 100vw, 300px" data-recalc-dims="1" />The post <a rel="nofollow" href="https://jinkang.us/2016/07/29/get-local-search-working-sharing-cloud-search-service-application-sharepoint-2013/">How Do I Get Local Search Working With Sharing Cloud Search Service Application in SharePoint 2013</a> appeared first on <a rel="nofollow" href="https://jinkang.us">blog about technology...</a>. ]]></content:encoded> <wfw:commentRss>https://jinkang.us/2016/07/29/get-local-search-working-sharing-cloud-search-service-application-sharepoint-2013/feed/</wfw:commentRss> <slash:comments>2</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">41</post-id> </item> </channel> </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):

<a href="http://www.feedvalidator.org/check.cgi?url=http%3A//feeds.feedburner.com/BlogAboutTechnology"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//feeds.feedburner.com/BlogAboutTechnology

Home · About · News · Docs · Terms