Next

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

added Type::Bug (Triage) scoped label

added to epic &64

changed milestone to %"sprint: Modest Monkey"

assigned to @benhayward.ben

Thank you for staying on these blog bugs, Ben.

Hey, not a bother. I've still been unable to replicate a some of them, for example we recently fixed some bugs in the blogs section, but specifically with things like the post/save button breaking, I've been totally unable to make happen for me.

Have you seen it happen at all? Maybe its something we've fixed inadvertently, but I don't like settling on that answer very much.

changed milestone to %"sprint: Nuanced Numbat"

added Sprint::09/11 - Nuanced Numbat scoped label

removed milestone

changed weight to 5

changed weight to 3

changed time estimate to 5h

I know that you need for me to say something exact, but all I can give you is that the Post/Save button has not broken, which may mean it's fixed. Blogs feels better, safer, smoother; because it's just not hitching on me, ever, although the P/S bug may be lying in wait just hoping I'd lower my guard and say that, so it can laugh and freeze.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

Please do keep me updated if you experience any more issues. The issues we've fixed in blogs could have fixed it, one was something relating to the buttons bar, another was image selection... and a few other various things. Maybe one of those was the root cause, but I'm not comfortable closing this ticket until we are 100%, so let us see what happens.

I'll continue to monitor and maybe thicken our testing around the area of blogs.

Quite the contrary, I just absentmindedly clicked a notification, which would have lost the unsaved parts of the blogpiece that I was writing, only to encounter the new warning message. Saved by the Ben! No, I have not experienced any screen freezes and I've been writing quite a lot. In terms of smooth and stable it's like a new blog platform. Please thank everyone. :)

I do note that lots of things that aren't bugs but are real problems aren't fixed yet. For example, I still can't move linked or illustrated copy cross-platform or even within the document without loosing the links and/or graphics. That for us is serious.

We do still need automatic save, which is a different animal, for those times when a computer connection burps, or the scene freezes, etc., but this simple warning, is a grand addition. Do you know where the team is on giving us a choice between two graphic sizes? That would be gravy but good gravy.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

Will bring up minds#733 with the team this week and see if we can get the ball rolling on that. I entirely appreciate the frustration that must come with that.

Automatic save - is something that will take a good amount of planning on our end. I know @ottman is keen to see us implement it though, so hopefully we can make it happen in the near future. I'm thinking alongside auto-save though, we will have to implement things like version history.

You're right. The multiple graphic sizes would have to be part of solving the cross-platform problem (of losing links and graphics when we paste from somewhere else or even within the document), because typically I use smaller graphics when writing elsewhere. I think most people/platforms do.

Having a history of versions is MUCH less important than having auto-save. That should come first. When you do give us version saes, make it optional. On longreads, versions can take up a lot of server space, very unnecessarily, because the platform interprets any save as a version.. We ought to be able to decide when we're through editing, puttering, obsessing and rearranging and have a "version" that we want to save. Giving up a toggle will save you a lot of server space too.

It's all good though. You're making a whale of a difference already....

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

added Status::InProgress scoped label

My worry making me lean towards version history, is that you could write over part of an article that you want, and if it auto-saved permanently, you'd lose the content when you refreshed. It's a good idea to make auto-save optional definitely, I think leaving that up to the authors writing style makes sense.

I'm looking at this particular issue now (with your old posts being marked as NSFW in your personal blogs section) - I think I understand why its happening, but I'm wondering, if a user marks a blog as NSFW, and others see it that way (so all is well), should it really have the NSFW grey overlay when the user is browsing their own blogs page?

Maybe.. maybe not. Will have to have a think on it.

Note for myself, the line thats at fault here is: https://gitlab.com/minds/front/blob/master/src/app/modules/blogs/tile/tile.component.html#L5

It might be that we need to rework that function, it might be that we need to just handle it differently for this edgecase.

added 1h of time spent at 2019-09-13

removed Status::InProgress label

Totally agree on version history. Prefect.

My thought is that we need to see the grey overlay ("fog", takes fewer characters,lol), because otherwise we would not know it was grey-overlaid, but overlaying just a corner would do it.

I had to open each one to figure out what it was, and since that was stored research it was maddening. Especially with these HUGE thumbnails to laboriously scroll down, I've basically lost access to my pre-hash research. Tiles, or at least a tile option, would be significantly better.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐