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 ‐‐‐‐‐‐‐

Thought. I was working on Google Docs yesterday, had just cut out three paragraphs of tightly linked material, intending to paste them higher, when our ISP blinked out. So when I got back there was this huge hole, perhaps four hours of work to recreate it, links and all. On Minds, I woulda died. On Google Docs, I just hit Undo. How hard is that technically?

Would that be a reasonable feature request?

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

BEN! I REPLICATED THE FREEZE! Certainly did not mean to, was just typing in a first draft, no links yet, in other words, with not a microdot of the number of saves I usually do. It's at https://www.minds.com/blog/edit/1020318811692371968

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

Ben, here's a blogpiece which will freeze for you if you save on it a few times. When it froze I refreshed, which wiped all my copy but gives you something to play with. The freezes are suddenly frequent and something new -- it's often not giving me permission to close, as though I were not me.

Minds is something of a free speech crusade for me, has been for three years, but Bill should have taken every cent of that million and fixed the platform. All the high-flying ideas in the world don't make up for a lack of stability. I wrote Nick in H&S but he didn't seem to recognize the impossibility of writing here, how serious this is. Not your fault. At all. Thank you for your help..

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

Hey, which account were you using to post? when I follow the link it unfortunately does not show me, but I can see the content of the blog still. (it just shows my avatar and wont let me save)

And so that blog will trigger it on command for you? I've probably asked quite a few times but what is your browser and OS again?

Seems like a good lead on it, but I tried to copy the content of the post over and try for myself, and it was working.

added 30m of time spent at 2019-09-18

I'm using a chromebook, and therefore Chrome.
The "Gail McGowan Mellor" Minds account
One blogpost WAS frozen but Nick suggested that I refresh. Knowing what was coming, I copied and pasted it elsewhere first, then refreshed. As I expected that wiped all my unsaved copy. So there's the BEFORE picture. It occurs to me that if our number-of-saves theory is correct, then if you hit that thing with some saves it will probably freeze again. That's not exactly "on command". I can't just shout "Freeze!" or enter an asterisk and it does, but a barrage of Saves should do it.
The first URL that I sent IS frozen There's the AFTER picture, the one-save-too-many example. Thing is, Ben that was a new blogpiece, not many saves. I therefore question our theory that what's triggering it is the number of saves.
Perhaps because of the work being done, there's a new problem. It's refusing me permission to save, as though it wasn't my channel. I have other channels, considered a crossbleed, but none of them were open..

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

added Status::InProgress scoped label

removed Status::InProgress label

Okay, I searched your account ID in our error tracking software, and 2 issues stand out to me as the most likely causes of the save issue. I've moved them into this sprint and will take a look into them.

The contents of these will likely mean very little to you but just to leave a paper-trail:

#1939 #1938 (closed)

Had a discussion with @eiennohi and @edgebal about this. I'm going to try these two fixes and see if they help for now, and we're going to look at pushing to the revamp closer.

Discussing the larger plans to revamp the blogs:

Copy-pasting between Google Docs, MS Word and others is apparently quite tricky to do in bulk like that, as Google and Microsoft both insert a lot of junk into the meta-data that we have to interpret on our end, and they both do it different.

The suggestion that came forward was that it would be much easier if we allowed import of common file-types instead, what do you think?

Also discussing moving to a markdown based system, but this would have to be accompanied by import and preferably export options if we did. Just to ask the community, how would you feel about that change?

Thank you, Ben.

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

As I alerted Nick, my accounts, @gail McGowan Mellor and @authorpendragon bleed into each other. I routinely get notifications for one that are clearly meant for the other and have commented on a post from say GMM only to see @authorppendragon's logo appear on it. I just cheerfully put up with it. You guys have got bigger fish to fry. But I'm increasingly wondering if the problems on Blogs are really this much-maligned platform and not something deeper in the system like indexing or channel bleedthrough -- which would affect Save permissions, yes?

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

Well, we are overhauling our permissions system currently, but that system should return an error if you did not have permissions, display it to you, and send a copy to us. So it could be the case. If the two above issues don't fix it then that would be a good starting point.

Whatever is causing the error is either doing it silently, or its due to one of the above mentioned issues.

Can you make it happen first try on your end?

And yeah, hopefully this is temporary, we are trying to move up the bigger revamp of the blog system up the list of priorities to get it dealt with sooner rather than in 6 months.

No I can't replicate because Ben I'm increasingly sure that it's systemic,like the bleed through of my channels, and I'm not doing that. I DO get messages that I don't have permission to Save, red ones --as recently as 3 04 4 days ago..

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

Sorry about that last character string. I meant "as recently as 3 or 4 days ago."

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

Oh I see, but sometimes there is no error provided also?

For the permissions ones, do you leave yourself logged in with one account and sign into another in another tab by chance? That'll cause issues like that. I'll have to play with my secondary account and see if I can make them bleed together.

If the errors in this are severe and frequent, maybe we should look into moving forward #542

I've heard a few multi-account users ask for it.

I have to work between my channels sometimes, need them both open, and Minds ought to allow for that, quite necessary. But each time that permissions thing hit, I glanced up to see if the other account was open (it usually wasn't) If it was, I got out of it> then I tried again. Still got no permission to use this account.

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

Another one froze.https://www.minds.com/blog/edit/1021444845894455296

I'm trying very hard to get this thing done, working from other copies so i have other Minds windows open but they're all on the same channel, @GailMcGowanMellor.

Chromebook/Chrome but I doubt that the device is responsible.

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

i'm wasting my life here on Minds. Literally. It just lost six hours of my work, not just the last save but the last six saves, taking me back to zero to when I started work last night, then gave me this For URL https://www.minds.com/blog/edit/1021921739061440512[Screenshot 2019-09-22 at 7.51.26 AM.png]

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

assigned to @eiennohi

Appreciate the frustration there. Assigning another developer to the card as we've had a few chats about this. Blogs are indeed high up on our priority list. Is the above what happens every time? Usually it just sticks right?

Hows your connection quality? I did notice while testing if I hit save, then go offline before it finishes, it gets stuck eternally. This is an issue but I don't think its necessarily related.

added Status::InProgress scoped label

added Status::Review scoped label and automatically removed Status::InProgress label

added Status::InProgress scoped label and automatically removed Status::Review label

added Squad::Yellow Status::Review scoped labels and automatically removed Status::InProgress label

removed Status::Review label

mentioned in issue #1965 (closed)

hey @authorpendragon , I've just been taking a look at your issue. I honestly think saving more frequently just increases the chances of you encountering the error, but it shouldn't have to do with the error per se.

At first glance, I'm thinking you may be having gateway timeout errors, and I just happened to notice we weren't showing those errors! so I created an MR (see !570). Once this is merged in, we'll be able to easily see if that's your issue.

Just in case, next time that happens, please try to include video or at least screenshots, console and network logs. Those would help us a lot

changed title from (bug): Old unlisted blog posts showing up with mature content flag in drafts. to (bug): Blog submission issues.

changed the description

How to show us the network logs: https://support.zendesk.com/hc/en-us/articles/204410413-Generating-a-HAR-file-for-troubleshooting

added Triage::Review scoped label

added Status::Follow Up scoped label

BRAVO, gentlemen! I don't know what you did but I'm up. It's working title was "14th try" :) https://www.minds.com/GailMcGowanMellor/blog/14th-try-1022730039699685376 The only thing that's different is that things were going so well...got the text done without a single hitch, illustrated, np, that when i started putting in links I got chicken and put in the bare minimum. Don't think that mattered but I mention it in case. THANK YOU!!!!!

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

Be warned, this fix could fix the issue, but in the worst case it should show you an error message.

We're working on this over the next couple of weeks #1967

Basically, the idea is that the blogs content will store its self in your browser data periodically, maybe after 5 seconds of inactivity, so if there is an issue where you cannot save, we can put an option in to restore from the backup (so long as you don't clear your browser data in between).

Restore from back-up? Magnificent option. The trouble with cutting and pasting to a new URL after a freeze is that all links and graphics are lost. This would fix that. YES!

I do want to repeat that i just posted that longread I have repeatedly tried to post since early September, and this time smooth as silk, without a hiccup. Something you did decisively worked. Thank you!

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

Hi Marcello! Will do. My last try -- and when I say "try" I'm describing hours of work to replicate the blogpost; I've been doing all 5000 words, with graphics and links from scratch each time so you could catch it happening --it it posted. That might be the luck of the roulette wheel, but if you changed something right BEFORE my last send to you, it apparently worked; no freeze, no denial os permission to save. Thank you for focusing on this. Gail

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

Okay. This is disastrous because I thought I was safe. It is denying me permission to save my own blogpiece again and I'll lose a lot of work if I can't. Please dig this one out for me.[Screenshot 2019-09-29 at 10.29.57 PM.png]ot of work if I can't.

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

It just published! Whatever you did, thank you.

If you did nothing, uh, it straightened itself out. All I did was look desperately and accusatorily at the PUBLISH button and keep hitting it.

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

No it's frozen. All that happened was that the notice saying that I did not have permission went away. It is not responding to Publish.

As always Chromebook, Linux, Chrome.

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

Two more froze in two days. Here's the second

[Screenshot 2019-10-02 at 4.36.52 PM.png] ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

The font is spontaneously switching to a pinpoint font, although font size is not an option on the Blog platform. This is happening spontaneously whether the post is open or closed, and randomly. There is no pattern to it[Screenshot 2019-10-02 at 4.51.06 PM.png].

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

escalating!

unassigned @eiennohi

changed milestone to %Misc. Q4 2019

added Sprint::10/09 - Pink Panther Status::Backlog scoped labels and automatically removed Sprint::09/11 - Nuanced Numbat Status::Follow Up labels

changed title from (bug): Blog submission issues. to Blog submission issues.

added Priority::1 - High scoped label

Mark, you just assigned Ben Hayward to the complex Blog problems. The long-intractable "freeze" which after a seemingly random interval prevented already-published blogposts from re-publishing if edited just cleared up. I have no idea whether that's coincidence or cause and effect, but someone fixed it. Thank you for getting involved.

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

Next

Blog submission issues.

Summary:

Steps to reproduce:

Browser and OS

The one place for your designs

Blog submission issues.

Summary:

Steps to reproduce:

Browser and OS

Related issues 0

The one place for your designs

Related issues
0