Publishing

[quote=Jpikachu1999][quote=ShiftyCake] [quote=Jpikachu1999] On the topic of publishing, I'd like to see a glitch I've had several times fixed. If your internet dies for even a second while you have your publish action pending, your guide whole page can fail and get the whole "Cannot connect to Mobafire servers". Reloading it usually ends up with rewriting several of my parts and deleting others. I've learned to keep backups because of this, but it's fairly annoying when my internet cuts for a couple of seconds and does this. [/quote] You could suggest adding in an auto-save feature, where if your internet stops working/closes in the middle of making a guide then it saves it to a backup folder where you can recall it at your convenience. Th only problem I can see with that, though, is if it takes up too much space (say someone spams it with 20 useless guides). It's a simple fix, where it only keeps one or two saved at a time. [quote=Jpikachu1999] Just gonna say, it would probably be better if it said "Are you sure you want to publish?". Not that most people would have a problem, but some people might be seriously confused if a message popped up while they were on a different tab (the request was still pending). [/quote] Good idea, just shorten it to something like "Publish?" and then a yes or no button. Otherwise it takes up too much space on the screen, giving it an unprofessional feeling. [/quote] I was going to suggest a backup folder sort of thing, or a button that backs it up into another guide under your profile. Problem is, I don't want to bother Matt [b]that[/b] much, and it would probably take a ton of work, not to mention all the space for where the backups go. He already technically has "backups", but it's quite difficult to access them, and I don't want to put that much work for him. Good idea on the "Publish?" idea. +rep[/quote]

[quote=ShiftyCake][quote=Jpikachu1999] [quote=ShiftyCake] [quote=Jpikachu1999] On the topic of publishing, I'd like to see a glitch I've had several times fixed. If your internet dies for even a second while you have your publish action pending, your guide whole page can fail and get the whole "Cannot connect to Mobafire servers". Reloading it usually ends up with rewriting several of my parts and deleting others. I've learned to keep backups because of this, but it's fairly annoying when my internet cuts for a couple of seconds and does this. [/quote] You could suggest adding in an auto-save feature, where if your internet stops working/closes in the middle of making a guide then it saves it to a backup folder where you can recall it at your convenience. Th only problem I can see with that, though, is if it takes up too much space (say someone spams it with 20 useless guides). It's a simple fix, where it only keeps one or two saved at a time. [quote=Jpikachu1999] Just gonna say, it would probably be better if it said "Are you sure you want to publish?". Not that most people would have a problem, but some people might be seriously confused if a message popped up while they were on a different tab (the request was still pending). [/quote] Good idea, just shorten it to something like "Publish?" and then a yes or no button. Otherwise it takes up too much space on the screen, giving it an unprofessional feeling. [/quote] I was going to suggest a backup folder sort of thing, or a button that backs it up into another guide under your profile. Problem is, I don't want to bother Matt [b]that[/b] much, and it would probably take a ton of work, not to mention all the space for where the backups go. He already technically has "backups", but it's quite difficult to access them, and I don't want to put that much work for him. Good idea on the "Publish?" idea. +rep [/quote] ty, and I worried about the space too. Yet it will take the same amount of space as a guide, and since mobafire was created for the guides there should be plenty of space. If he already has backups, then he just needs to change the coding of them for easy access. Bothering Matt is our job.[/quote]

[quote=Matt]I read this forum more often than my PMs. FYI :) This forum is the best place to raise issues and get my attention. It's the first place I look when I'm catching up, and if I have very little time it is sometimes the only place I look. If I'm MIA on this forum, it's because I'm knee-deep in coding a big project, but I will be back once things slow down and will likely peek in now and then anyways to make sure nothing vital is happening. Idea noted! Long as noone will get annoyed at constantly having to click twice, but I don't imagine you guys publish all that often, you likely save every time and then only publish sometimes. Also agree that saving is sketchy. The problem is that there is a massive amount of data being sent to the server, which then has to do a lot of processing to store it. Adding async saving was done to help protect from this and make it easier. Generally if the site is down and you click save, you should just get an error back, and if you wait till the site is back up and hit save again it should work fine. Is that not happening?[/quote]

[quote=luxie060]I don't have a problem with it. I just accidentally published my [[Annie]] guide and now people can see what was suppose to come...[/quote]

[quote=ShiftyCake][quote=Matt] I read this forum more often than my PMs. FYI :) This forum is the best place to raise issues and get my attention. It's the first place I look when I'm catching up, and if I have very little time it is sometimes the only place I look. If I'm MIA on this forum, it's because I'm knee-deep in coding a big project, but I will be back once things slow down and will likely peek in now and then anyways to make sure nothing vital is happening. Idea noted! Long as noone will get annoyed at constantly having to click twice, but I don't imagine you guys publish all that often, you likely save every time and then only publish sometimes. Also agree that saving is sketchy. The problem is that there is a massive amount of data being sent to the server, which then has to do a lot of processing to store it. Adding async saving was done to help protect from this and make it easier. Generally if the site is down and you click save, you should just get an error back, and if you wait till the site is back up and hit save again it should work fine. Is that not happening? [/quote] hmmm...what about external storage? I suppose that would be costly and risky though, so it seems ot be more a coding problem then a general problem. Therefore I leave it to you, to scrap it or use it.[/quote]

[quote=Matt]It's not storage, it's purely the process of communicating and managing an extremely complicated and varied data set over finicky media (web browser and internet). The builder is basically the last thing we haven't visited for a long time. TBH I need to scrap it and rewrite the whole thing, it's still running day 1 code on the client-side, and that code SUCKS.[/quote]

[quote=ShiftyCake][quote=Matt] It's not storage, it's purely the process of communicating and managing an extremely complicated and varied data set over finicky media (web browser and internet). The builder is basically the last thing we haven't visited for a long time. TBH I need to scrap it and rewrite the whole thing, it's still running day 1 code on the client-side, and that code SUCKS. [/quote] Ahhhh, so it is possible. I'm happy just to know you have put it under your to do list. Even if that list is vast :P[/quote]

[quote=jhoijhoi]Matt, I assumed by the "Are you sure" thing, Kat was only referring to the initial publish. Like the one that makes your guide public. I doubt anyone is really too worried about hitting publish *after* the guide has been released. So in that case, it'd be a "once off" kind of coding, "Are you sure you want to publish this guide? Once published, this guide cannot be deleted, only archived."[/quote]

[quote=Keondre]Yes. It would be annoying to hit the thing again again as you make changes to your guide. Maybe it can be coded to just pop-up in the initial publish?[/quote]