Website Multiple bugs when trying to set a mod as 'Unlisted'

[delta.]

attempting to create a mod as unlisted after checking all minimum requirements for a mod to be uploaded no longer does anything (clicking the create mod button animates the button, but helio does not start any of the mod uploading operations). when trying to circumvent this by creating a draft (which succeeds as normal) and changing the draft to unlisted, heliosphere does not recognize that all valid fields have already been uploaded and fails with this text box appearing:



i am uncertain if this has something to do with a previous post about letting collaborators see drafts. i used the unlisted feature to do this, and i don't mind changing my workflow around to accommodate these changes, but i would just like to know if that's something i should change about my workflow going forward. thanks!

 

[anna]

Works fine for me. Try clearing your cache.

 

[delta.]

apologies, i logged off for the rest of the day after i posted. trying again today with a cleared cache and i'm still getting the same issue. if it's working for you, then maybe it's because i'm using a firefox fork (waterfox) as my main browser...? not sure what else it could be.

 

[anna]

I see other people creating unlisted mods, as well. Are you sure you're filling in all necessary fields? No red errors if you scroll up after clicking submit? Are you including a file? I use LibreWolf without issue, so it's probably not Waterfox.

 

[delta.]

I use LibreWolf without issue, so it's probably not Waterfox.

none that i can see. i also tried librewolf earlier since i use that for containerized web apps and planned to make heliosphere one, and i still received the same error when i attempted it earlier this morning. i can try again after cloudflare stops going haywire.

 

[anna]

If you press F12, click "Console", then click the submit button, are there any errors logged in the console after clicking?

 

[delta.]

it didn't produce any errors in the console, though i figured out what my issue was. heliosphere doesn't tell you that entering a description for the mod is a required field when making a mod, and does not produce an error visible to the user when attempting to make an unlisted mod without one. i can make drafts with no descriptions, but not unlisted mods. it's only when trying to update the draft to an unlisted mod that the error in the screenshot (correctly) occurs.

 

[anna]

Strange, it should produce an error. I'll add fixing that to the list. None of this has anything to do with unlisted. Nothing is required for a draft: that's the purpose of a draft.

 

[delta.]

yeah, i kinda figured that after i pinpointed what the error really was :') my bad.