Ian Causton

After deploying an update to a recent EPiServer 6 and Composer 4 based site I received notification from a concerned client that the Composer toolb...

• 9/No stats
• 9/7.1 Upgrade issues with proxy
• 2/Published Composer areas reverting to previous version
• 10/Using Social Reach with a proxy
• 4/Retrieve PropertyDropDownList Options
• 1/Export pages to word/pdf
• 1/Global Blocks not showing when page is published
• 8/VirtualPathUnifiedProvider is null
• 1/Retrieving/specifiying a poll on a page
• 1/Mo Blog Questions
• 1/Clubs using friendly url's
• 1/Chatroom
• 11/Profanity Filter
• 9/Upgrading PageSearch to CMS 5
• 8/Custom Authentcation via Login Control
• 8/SqlServerMembershipProvider createUser
• 7/CMS5 R2 using WindowsMembershipProvider after upgrade
• 7/Adding to the user profile
• 7/Should the migration tool work on XP

• Extra div-s in page markup/RE:Extra div-s in page markup
• Published Composer areas reverting to previous version/RE:Published Composer areas reverting to previous version
• Published Composer areas reverting to previous version/RE:Published Composer areas reverting to previous version
• Retrieving/specifiying a poll on a page/RE:Retrieving/specifiying a poll on a page
• Poll Management in Relate plus/RE:Poll Management in Relate plus
• Profanity Filter/RE:Profanity Filter
• Custom Authentcation via Login Control/RE:Custom Authentcation via Login Control
• CMS5 R2 using WindowsMembershipProvider after upgrade/RE:CMS5 R2 using WindowsMembershipProvider after upgrade
• Adding to the user profile/RE:Adding to the user profile
• Should the migration tool work on XP/RE:Should the migration tool work on XP