Post bug reports here!
- Thread starter airwreck
- Start date
Friedman
Administrator
Thanks! The next update should resolve this issue.
daonewolf
Virgin
I am also experiencing the issue mentioned by lordxoprh, as well as something that might not be a bug but something missing from the site; if you save a story as a draft rather than publishing it, you can no longer access it. It doesn't appear in your stories or in your recent activity. In my case, I was able to hit backspace and go back to the story but I now have no way of publishing it or deleting it.
Is there a fix for this? Or am I doing something wrong?
Is there a fix for this? Or am I doing something wrong?
Trugbild
Really Experienced
mh...
markdown do not always interpret <> as html...
<Thought!> stays <Thought!>
but
<Thought...> or <Thought.> get interpreted as html-tag.
I think, that these brackets worked fine with markdown in the previous version of chyoa.
RicoLouis
Really Really Experienced
Second time it's happened for some reason. On One Big Horny family I have a chapter in the wrong place on the story map.
pinch penny's ass is under no just sit for a bit while it should be under yes to coffee just above, though I have a link under pinch penny's ass to the same chapter. Not sure if this is a glitch from using the linking system or what.
pinch penny's ass is under no just sit for a bit while it should be under yes to coffee just above, though I have a link under pinch penny's ass to the same chapter. Not sure if this is a glitch from using the linking system or what.
At first, I thought I would post this under suggestions, but to be honest, I see this as a usability bug. Currently, what happens if you accidentally close the tab you are writing on? (I've done this before, but it only occurred to me that this can easily be fixed.)
You lose the work, especially if you haven't saved as a draft. The best way to prevent this is to ask the user if they saved their work using a unload event and dialog to confirm. I usually hate these as it comes on a page "desperate" for me to stay, but in this case, it's welcomed since all the options you need, even to cancel is below the input area.
Thanks.
You lose the work, especially if you haven't saved as a draft. The best way to prevent this is to ask the user if they saved their work using a unload event and dialog to confirm. I usually hate these as it comes on a page "desperate" for me to stay, but in this case, it's welcomed since all the options you need, even to cancel is below the input area.
Thanks.
Zingiber
Really Really Experienced
Automatic periodic save of a current draft would fix this issue without adding the unload hook and confirmation dialog, with the virtue that it would also save you from a tab freeze or browser crash.
That can work too, but I figured that the dialog option would be easier and cheaper to implement. I guess it depends on how many simultaneous connections this site receives while editing/writing a new chapter. Google Docs is the most obvious to implement auto save, which I love, but they have the needed resources to handle auto saving by thousands (millions?) of users.
Trugbild
Really Experienced
A dialog prevents you from fast-closing the website. I think, that's no that good for a NSFW-website.
Periodic save draft could do the job.
Maybe there could be another way, but I'm not sure, if it is possible by programming and browser restrictions.
The dialog option has to be fired by the browser close command. Maybe it could be possible to use the same behavior to send the draft before closing. If successful, the draft reaches the server, if not, the changes since the last periodic save would be lost (if periodic save is implemented).
Periodic save draft could do the job.
Maybe there could be another way, but I'm not sure, if it is possible by programming and browser restrictions.
The dialog option has to be fired by the browser close command. Maybe it could be possible to use the same behavior to send the draft before closing. If successful, the draft reaches the server, if not, the changes since the last periodic save would be lost (if periodic save is implemented).
I remember that with current browser capabilities, you can actually store rather big unsaved/unpublished writings in the browser through localStorage or an alternate web storage api. The exact maximum size will differ (Generally it's in MB which should be sufficient), but it's another option that won't waste uncommitted space on the server. I'll stop here with the implementation suggestions, but again, I think this is a bug to fix or a "needed enhancement" in my view.
I'm really liking the fact that this site is so clean and already beating the competition with other known interactive sites. I hope to see it improve further.
Friedman
Administrator
Thanks! Should be resolved now.
airwreck
Really Experienced
On the mobile version, I noticed when I click I the Options bars to bring up the side bar that's on the desktop version that I can't scroll all the way down. Instead I start scrolling the original page. I noticed the page will flicker. Seems like a rendering issue. This seems to have started when the ad banners appeared.
I'm viewing the site on Chrome on Android.
I'm viewing the site on Chrome on Android.
Last edited:
Friedman
Administrator
I've pushed a quick fix but have to look at it in more detail. Thanks!
Hi, I'm a new user and since the first day I am experiencing an issue about the log-in.
On my first day here, I wrote and posted three chapters of a story; after I posted them, I couldn't log-in again in the main site. I can log-in regularly in the forum (here), I can't do the same to the main site. I am sure my password is right written.
Should I request a new password with the "Forgot password?" procedure, even though I didn't forget it? How can I log-in again and hopefully write more?
On my first day here, I wrote and posted three chapters of a story; after I posted them, I couldn't log-in again in the main site. I can log-in regularly in the forum (here), I can't do the same to the main site. I am sure my password is right written.
Should I request a new password with the "Forgot password?" procedure, even though I didn't forget it? How can I log-in again and hopefully write more?
