Jump to content

Recommended Posts

Posted

I do see this behavior for some days now, namely if you go to the Affinity forum in a webbrowser and press immediately "Reject Cookies" it will produce an "Error code: 2S119/1". - Before the whole behaved well for Cookies and dismissed the "Important Information" panel, now it always generates an "Error code: 2S119/1"!  -- BTW seems to be the same odd behavior now for "Accept Cookies" too here.

screen_one.png.61319edbffcd6adfc2b64378f4de4326.png

screen_two.png.208abda8aa8dd9d42fb314d99e87a603.png

 

See also related ...

 

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

  • Staff
Posted

Hi @v_kyr,

I'm not seeing this here in Chrome, Safari or Brave on MacOS 14.2.1.  Even tried Safari on my iPhone and didn't get this error.

Which browser are you using?

 

Posted
2 hours ago, stokerg said:

Which browser are you using?

As can be seen from my Sig I mostly still use El Cpitan (maxOS 10..11.6) for surfing, thus I have to use older webbrowsers which still work under that OS version like ...

  • FF 78.15.0esr
  • Chrome Version 103.0.5060.134
  • Safari Version 11.1.2 (11605.3.8.1)
  • ... etc.

 

 

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted
1 hour ago, stokerg said:

Hi @v_kyr,

I'm just waiting to hear back from QA who will have access to El Capitan, as the oldest version of MacOS I have access to is Big Sur. 

I will check if something might be blocked (cookies port wise) now, or if Little Snitch might possibly have lost some port rulings here. But so far, as I indicated above, only the Affinity forum's cookies handling is affected here.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

  • Staff
Posted

Sorry but the forum software only officially supports the latest two browser versions, and our implementation is a very vanilla one, so it will not be something we have done. Your browsers are effectively unsupported, sorry.

Incidentally, as we don’t use analytics on the forum, the difference between accepting and rejecting cookies is very little. For us, the only difference was one additional cookie (containing timezone) when accepting compared to rejecting - if that’s any consolation.

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Posted
58 minutes ago, Patrick Connor said:

Sorry but the forum software only officially supports the latest two browser versions, and our implementation is a very vanilla one, so it will not be something we have done. Your browsers are effectively unsupported, sorry.

It's something I didn't encountered one or two weeks before by using the same webbrowsers (as always and their settings). So as far as nothing forum software wise has changed lately this month here, something else is then producing side effects here.

1 hour ago, Patrick Connor said:

Incidentally, as we don’t use analytics on the forum, the difference between accepting and rejecting cookies is very little. For us, the only difference was one additional cookie (containing timezone) when accepting compared to rejecting - if that’s any consolation.

I will try to inspect/debug the browser flow here now, in order to possibly find out & see what might affect the whole here now. - So far I always see that it has newly to do with the accept/dismiss cookies panel (before that worked fine and as suggested) and thus is related to that.

BTW actually when trying to accept or dismiss bottom cookies info, it always jumps to that "OOPs ... Something went wrong" ("Error code: 2S119/1") error message. But when from that error page then clicking again on/at the top LOGO + AFFINITY forum site entry point URL, then the bottom cookies Important Information panel itself will be finally removed/dismissed without jumping to the error message page. So after that previously told click on forum's main URL step from the error page, things behave normal as in the pasts.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted

I think the whole is somehow "crsfkey" related, since those initially seem to don't match here, even cookies adblocker etc. are overall disable for the forum site.

forum_csrfkey.png.bed42a62fb518d69866dad2971f8737b.png

I can see this behavior in all webbrowsers (FF, Chrome, Safari, Brave) under El Capitan so far.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.