Could someone please confirm this Chrome issue?

[Mat]

Update: Issue solved. 

----------------------------------------------

If you're using chrome:

As reported in #3955,  I find that the Chrome setting "Block third-party cookies" (direct: chrome://settings/content/cookies?search=cookies ) also blocks the uploading from local to tiddlyspot, and possibly any such remote host. My amateur interpretation is that Chrome interprets the password a cookie.

Could someone please try to save from local to tiddlyspot, with the above blocking active?

To simplify, here are the needed links, including a pre-made tiddlyspot:

Setting:         chrome://settings/content/cookies?search=cookies

empty.html:   https://tiddlywiki.com/#GettingStarted

tiddlyspot:     http://3955.tiddlyspot.com/

- username: 3955

- password: password

Kindly confirm or dismiss this by also stating what OS you're on.

Thank you.

<:-)

[TonyM]

I have not used classic for so long. I had trouble finding my way around

However I seem to have achieved an upload at 31/05/2019 16:51:26 without any change to default cookie handling.

I can't see in chrome developer option  how to view cookies/storage. But I recall TiddlyWiki classic was driven by cookies, that's why there was a cookie jar plugin.

In TWC the password for tw-receiver is saved like a cookie, in local storage. But password may get special treatment.

Can you allow cookies just for the tiddlyspot.com/ domain?

best of luck

Tony

[Mat]

I have not used classic for so long. I had trouble finding my way around

No, wait, you don't have to use classic in any way for my request. The idea is only that you upload a TW5, e.g an empty one or whicever you want, to overwrite that TiddlySpot. To overwrite the TiddlySpot with a TW5 is actually (and unfortunately) the standard procedure when using TiddlySpot because that service, great as it is, doesn't offer TW5 by default. And the very first overwrite has to be done with Chrome for reasons unknown to me. Possibly Safari works too but FF/Edge don't.

 

However I seem to have achieved an upload at 31/05/2019 16:51:26 without any change to default cookie handling.

But my request is that someone does set Chrome to "Block third-party cookies" to see if this messes up the upload, as it does for me.

I'd appreciate it if you could make another test, but with that Chrome setting activated? It is actually not a request for me personally (because I now know what the problem was) but to make sure this discovery can be properly dealt with (core change or merely documentation update).

Thank you.

<:-)

[TonyM]

I can try it tomorrow.

Tony

[Mat]

 can try it tomorrow.

Tony

Would be great. Thank you.

<:-) 

[TonyM]

Mat,

Since I have my own host and use tiddlywiki internally a lot I have lost track of using tiddlyspot so I am reacquainting myself. 

Sorry for any delay.

Regards

Tony

[TonyM]

Post Script

I note you can give exceptions by site to this policy of not retaining cookies and local storage. Perhaps that is a good work around.

Regards

Tony

[Mat]

On Tuesday, June 4, 2019 at 2:18:35 AM UTC+2, TonyM wrote:

Mat,

Since I have my own host and use tiddlywiki internally a lot I have lost track of using tiddlyspot so I am reacquainting myself. 

Sorry for any delay.

No panic, but there really isn't anything to get acquainted with since I already set up a Tiddlyspot. The only thing I'm asking is that you upload any local TW to it by going that local TWs controlpanel>saving>tiddlyspot and type in username:3955 and password:password

Now before doing that, go to your chrome settings (here is a shortcut:  chrome://settings/content/cookies?search=cookies  ) and "block third-party cookies".

Really, there's nothing to it. Should take 2 minutes, tops.

<:-)

[Mat]

I note you can give exceptions by site to this policy of not retaining cookies and local storage. Perhaps that is a good work around.

I didn't get this to work for a local TW. I don't know why.

<:-)

[Mat]

I'm happy to report that Jermolene just solved this! The problem was in deed caused from blocking cookies.

Thank you to everyone who was involved.

<:-)