file attachments

comments

Just following up on the open issues - this is kind of old now but do you know if you're still seeing an issue with this? The GalleryDetailsUrl in the feed should not be different based on how the package was pushed. That field is not stored on a per package
basis - it's generated dynamically based on a template in the AppSettings file.

David, I know why the GalleryDetailsUrl is incorrect - all of those packages have a null value for PackageType. What I don't know is how that happened in the first place. Any package that gets pushed should end up with a PackageType value of 'Package'.
Can you query the NuGet database and find out how many packages have null for that field?

Okay, then that's a problem. I suspect you're right - packages pushed via nuget.exe vs. uploaded through the gallery are probably ending up with a NULL package type. Thinking about it now, I believe I know how this was overlooked. The package type value
didn't use to matter on the server side. When a new package syncs over to the Orchard side, we automatically select the package type value if there is only one term defined in the taxonomy, which is the case for NuGet. So on the front-end everything has a
value.

At some point we added that GalleryDetailsUrl property to the feed - I think it was right before v1 was released. That was the first time that the value mattered for the feed, but we never considered the fact that packages pushed from nuget.exe won't have that
value. I think this is something we'll need to add to GalleryServer. In the meantime, I can think of one workaround that should work for NuGet. Since you only have one type you could make 'Package' the default value in the database to handle new submissions,
then just update all the existing null values.