PM drafts not saved

[Sir Osis of Liver]

Clean install, new db, today's github package.  Post drafts are saved, pm drafts are not.  Same problem with previous package (28 Jun).

[Suki]

Does inspecting the page yields any errors on the console?

[Sir Osis of Liver]

Code Select Expand



Request to access cookie or storage on "http://ff.kis.v2.scr.kaspersky-labs.com/FD126C42-EBFA-4E12-B309-BB3FDD723AC1/main.js" was blocked because we are blocking all third-party storage access requests and content blocking is enabled.



Confirmation message is displayed, draft isn't saved.  No forum or server errors.  Works fine in post editor.

[Sir Osis of Liver]

Can this be fixed? It's gumming up the works on a modification I'm working on.

[albertlast]

i tested the github version.
i was able to save the draft version and
then to open this and to send this.

so the issue didn't exists?

[Sir Osis of Liver]

I'll try the current gh dl..........

[Sir Osis of Liver]

Doesn't save PM draft in IE11 or FF67.  Post drafts are saved in both.

[albertlast]

By the error message you provide above,
i would guess that your anti virus software could be the root of the issue.

[Sir Osis of Liver]

Thought that, but does same thing if I exit KAV.

Just tried it again, close KAV, confirm it's not running in task manager, pm draft does not save, post draft works.  From console -

Code Select Expand



Request to access cookie or storage on "https://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js?smf21rc2_1562473562" was blocked because we are blocking all third-party storage access requests and content blocking is enabled.



Something must be different between post and pm editors.

[albertlast]

appears the error message,
when you exit kav?

[Sir Osis of Liver]

Updated previous post. ^

[albertlast]

The error message i got too,
but doesn't hurt.

[Sir Osis of Liver]

Same thing if I disable cookie blocking.  Why do post drafts save and pm drafts do not?

[Sir Osis of Liver]

I get same error in console when post draft is saved successfully.  See a lot of them, also on this forum, but they don't break anything.

Code Select Expand



Request to access cookie or storage on "https://static.simplemachinesweb.com/smf/default/scripts/spellcheck.js" was blocked because we are blocking all third-party storage access requests and content blocking is enabled.



[albertlast]

do you always install?
or use your existing setup/database?

[Suki]

Can this be fixed? It's gumming up the works on a modification I'm working on.

Can't replicate the issue, OP doesn't state if this is a clean install or has it been modified somehow, without enough details its pretty difficult to track this or even replicate it.

[Sir Osis of Liver]

Clean install, new db, today's github package.  Post drafts are saved, pm drafts are not.  Same problem with previous package (28 Jun).

Ran into this problem on a work install I was mofifying.  Assuming I broke something, did a clean install with new db, same problem.  Have overwritten it with two subsequent github packages, most recently last night, same problem.  Save draft, displays confirm message, nothing's saved.  Works fine in post editor, there must be something different in pm editor.

IE11 is blocking first & third party cookies, allows session cookies, domain is whitelisted.  FF67 is blocking trackers, cryptominers, fingerprinters, and third party cookies.  Ghostery is blocking everything.

But it works in post editor.

[Sir Osis of Liver]

<sigh>  Never mind, was flogging the wrong end of the horse.  PM and post drafts are both being saved, and I've got my modification working.  There's some irony here, but I'm sure the explanation wouldn't be appreciated.  Thanks.

[Suki]

See, this somehow do bothers me. I just spent a significant amount of time trying to replicate this for no good reason. The fact that you were expecting this to be fixed merely two days after you posted it without giving enough details didn't help either.

I don't mind looking at bug reports but it will be seriously awesome if anyone reporting a bug could post some more info about it or a quick "how to reproduce" guide. We already have a handy template on GitHub when users open a new issue, I wholeheartedly suggest to use it.

[Sir Osis of Liver]

I did post relevant info up top, didn't think this was a bug (it wasn't), and generally find github unuseable and over my head.  Turns out it was caused by exactly the problem I was trying to fix, which I've now done.  I, too, have wasted time chasing non-problems here in support, and try not to create those situations myself, but if I knew what was wrong I wouldn't have to ask for help.