You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the CKAN badge only shows up on mods that were added by clicking the checkbox in spacedock. This could lead to mods showing the badge if the mod couldn't be indexed for whatever reason. It also leads to mods added through other means not showing the badge which could confuse users into thinking its not available from CKAN
Solutions:
Just a checkbox, and trust the mod maker
Search CKAN for the mods existence in some way
A custom field for the CKAN ID in the mods metadata (What would be really cool is a way to do an openin link that opens CKAN and installs the requested mod)
The text was updated successfully, but these errors were encountered:
This could lead to mods showing the badge if the mod couldn't be indexed for whatever reason.
This part was already addressed, admins can uncheck the checkbox as of #337.
mods added through other means not showing the badge
This can be handled by an admin checking the checkbox as needed. An automated pull request would be created, but it can simply be ignored and closed in one click.
Just a checkbox, and trust the mod maker
I'm not sure what this means. Isn't that the current state? But it's listed under "Solutions"?
Description (What went wrong?):
Right now the CKAN badge only shows up on mods that were added by clicking the checkbox in spacedock. This could lead to mods showing the badge if the mod couldn't be indexed for whatever reason. It also leads to mods added through other means not showing the badge which could confuse users into thinking its not available from CKAN
Solutions:
Just a checkbox, and trust the mod maker
Search CKAN for the mods existence in some way
A custom field for the CKAN ID in the mods metadata (What would be really cool is a way to do an openin link that opens CKAN and installs the requested mod)
The text was updated successfully, but these errors were encountered: