I know there was already a discussion about this and I tried to delete it by clicking the three little dots, but it didn't work for some reason? (Brand new to this site and got my subscription the same day I discovered it. This site is a gift for all writers in the world, thank you!)
.png)
Well a couple things:
Sections disappear when you delete all their categories, categories are deleted by the aforementioned dots.
What browser are you using? The recent upgrade to the site could be causing the issue. I checked from my primary and secondary browsers (Edge and Chrome, respectively) and I had similar issue with the dots in both. (specifically the dots not opening a menu when clicked)
If the menu does open for you but it just won't delete it could be because the site uses a small pop-up window to confirm the deletion and blocking causes deletion to not work, this can be fixed by allowing pop-ups on this domain.
Either way @andrew (Our Supreme Lord and Overseer) it may be worth looking in to this.
Thanks, both. Looks like the recent upgrades did indeed break the dots – very sorry about that! I'll have them fixed shortly. :)
I am currently having a problem with the custom categories.
I tried to make one of my own, but it didn't do anything – except for making my slider-bar-thingy disappear. It comes back when I go to a different section, like Discussions, but the point is, I can't make custom categories. If there's someone who can help with this, I would greatly appreciate it. :)
That is certainly a problem…
I couldn't replicate the issue in either of my browsers, so I have to ask: What browser are you using? And (if it isn't a bother) could you provide a screenshot?
If the issue is that when you click "create field" it just doesn't, try clicking on the actual text instead the box as the box itself doesn't do anything (you can tell if the link through will work by the url appearing in the bottom left of the screen when you hover over it).
Browser: Firefox
And I tried clicking on the text, the plus, and the box itself
Huh, that's interesting.
It would seem to be an issue with Firefox being that it worked fine for me…
I don't know anything about Firefox but the timing means it will probably be fixed along the issue higher in the thread.
Best suggestion? You might be able to invite people as collaborators and work around the problem that way until the issue is resolved. (and I'd be willing to help to that end if you'd like)
Sorry I couldn't be more helpful!
Hey, this should be fixed now. :) Let me know if you see any other issues!
Oh dang, I saw that on one of mine also but I just assumed it was from me mangling data on my own account. @MainframeSoleil do you remember what the actual name of the field was? I'll get it fixed up quickly, but that'll help me dig in quicker if you remember it. :)
I do not, sorry.
That's okay, it should still be saved on the backend. Thanks for the heads up!