Web Content, Digital Assets, Form Builder, SEO Tools, Decision Support
Multisite Management, Multilingual Support, Site Synchronization, Deployment Options, Security, Scalability
Personalization, Email Marketing, Mobile, Social Media, Analytics
Integration Platform, Connector for Salesforce, Connector for Microsoft Dynamics CRM, Connector for Marketo, Connector for SharePoint
Product Catalogs, Multiple Storefronts, Targeted Offers, Payment Processing, Order Management
Custom Content Types, UI Framework, ASP.NET MVC Support, Visual Studio Support, Comprehensive API
Behaviour Tracking, Data Integration, 360° Customer Profile
Audience Segmentation, Predictive Analytics, Campaign Recommendations, Campaign Tracking
Marketing Attribution, Conversion Tracking, Persona Profiling, Lead Scoring
Predictive Personalization, Persona-Based Targeting
Does the new sitemap generation feature in version 7.1 work in azure? When I configure it and click the generate the sitemap button it says Sitemap generated successfully, however nothing is generated in the location I specified.
That would have been something good to note in the documentation.
Is this something that is planned to be fixed? Is there a PITS item for it?
Is it going to be like the search on Azure which has never worked?
You may want to try moving your Sitemap location to inside the App_Data folder.
Azure sets this folder with write permissions by default while the root is not.
I have tried this and get the generated files as expected.
That's good to know except the whole point of this is so that you can hit the regularly scheduled and generated sitemap.xml file with google webmaster tools. I don't think I can hit a generated file inside the App_Data folder with a public url.
You can by using the /Sitefinity/ path which replaces the /App_Data/
Awesome. Great solution, thanks.
Now if only they supported uploading that somewhere or just hosting a service method since redeployment is going to blow these generated sitemaps away.
I took your point about the App_Data folder and looked into things a bit and I have a working solution.
Have a read. It mainly about solving the search issue but works for the sitemap as well.
While this works, please keep in mind that Azure cloud roles do not keep their state. Any search indexes that Sitefinity generates will be gone after you do a new deployment or the machine does host updates (windows updates).
The best solution is going to be using a search service like the new Azure Search Service and then creating a search display control in Sitefinity.
I am not well versed in Sitefinity on Cloud Service with worker role machines as I run all my sites on Azure websites. The search indexes are stored on the file system which is persisant. (Its physically separate from the actual IIS server in the Azure architecture) so even if the physical host fails or is updated I don't lose my site or the indexes.
Yes I am interested in the new Azure Search and am wondering if Sitefinity will add a new search provider as an alternative to the Lucene one they have.
Make Sitefinity work best for you.
Progress, Telerik, Sitefinity and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.