Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Hi Dan
I first thought this would be easy by just using the Get-EPiAddOnFeeds PowerShell command ( http://world.episerver.com/Blogs/Sergey-Vorushilo/Dates/2013/12/Command-line-support-for-Add-On-system/ ) but it just returns the filter tag names.
... but the again if you ILSpy the assembly EPiServer.Packaging and look in the EPiServer.Packaging.Constants you'll find the DefaultFeedUrl with value: https://addons-api.episerver.com/feed/
So I guess that is the only url but it contains the add-ons tagged with : EPiServerAddOns, EPiServerBetaAddOns and ThirdPartyAddOns (to be able to filter them in the EPiServer Add-Ons UI)
To be able to add our own feeds see: http://world.episerver.com/Documentation/Items/Developers-Guide/EPiServer-CMS/75/Modules/Add-ons/ (section: Creating additional repositories)
Hope this helps, cheers Antti
Does anyone know how the Add-On store works with pulling down manifests and content? What URLs do I need to white-list in order to enable the server to be able to get to the Add-On store (the deployment is very locked down). Are 3rd party Add-Ons hosted on the same URLs, or on the 3rd party site URLs?
If anyone happens to know the answers it would be appreciated as using a HTTP listener and testing everything would be somewhat time consuming!
Thanks!