Hello! Recently we got a security certificate to enable access via "https://" which seems to have made things buggy with posting to some fellows.

After removing hard-coded references to http:// we're still having some "doo doos" posting-wise as per reports. Let's use this thread to address & debug it.

---

P.S. in case you didn't catch the announcement, we're moving to an Icelandic operation this very month. It's "full blown" this time, with me quitting my day job to focus on becoming an Internet developer/creator:

https://betselection.cc/general-discussion/what-made-you-spend-so-many-months-on-this-forum-Victor/msg61279/#msg61279

It's a scary step yet exciting at the same time!

The finished product differs from traditional forums in a rather positive way.

Good times for us a community

Using the latest Firefox:


                   *  Login was successful

                   *  This post and one other went through the first attempt, and without problems.


An important security milestone achieved. Well done, Victor. 

Hopefully members will log in not using the same password that they use for everything else!


Good luck with your future $$ plans -- a Big Step to take....




[After making a small modification to the post I clicked SAVE and Fox warned me this message was "...on an insecure connection and could be read by third parties"   

That's odd because when I logged in BOTH  the https AND the padlock are clearly shown green in the address bar.

But in the post editor I now see there is now an !  attached to the padlock which indicates an insecure connection]

Cannot edit after already posted within the time frame allowed.  Cites about the security issues, etc. 

Compared to before Victor worked on it once again this time, a larger amount of typos, our program changing (second Guessing what our words typed out should be, etc) and a much larger amount of letters left out of words en if we type them, etc. 

Thanks for the report Max & Glen.

There's old code still hanging around. After years of modifications this code-base is messy but we've already moved to a better one, with me coding both the "core" & the modules as a big shift forward for decades to come

https:// issues should be minimal by now.

Posting, replying and modify page should be working for every topic.

Anything, please report

Yes modification is fixed!

Yes, to a certain point, the system is not self correcting the wrong words or changing them as bad as it was.

It is also not slowing down as bad while typing. 

Let's see what happens. 

The only thing I am noticing right now, is failure to print a letter typed, your system is skipping some letters.  Always has in fact.  I do type extremely fast, but even if i do slowly, also skips some?

Quote from: alrelax on February 24, 2018, 03:13:16 PM
Yes modification is fixed!

Thanks for your report.

Quote from: alrelax on February 24, 2018, 03:13:16 PMYes, to a certain point, the system is not self correcting the wrong words or changing them as bad as it was.

Roger that. I'm on it.

Quote from: alrelax on February 24, 2018, 03:13:16 PMIt is also not slowing down as bad while typing. 

Let's see what happens.

Okie.

We're only doing maintenance. All the new feature development time goes to the new server / new setup

Hi Victor,

I'm having problems posting with Firefox. I kept getting an error message saying the verification was incorrect. It was only when I tried a different browser that I realised Firefox wasn't even showing the pictures you have to match.

Quote from: CoderJoe on February 25, 2018, 09:11:24 AMHi Victor,

I'm having problems posting with Firefox. I kept getting an error message saying the verification was incorrect.

Hello Joe, thanks for your report & welcome to the family

We're going to stick to this web engine for the whole month of March so it's worth to have posting working correctly for the fellows May we get to know the exact error message displayed by the 'Fox?

[attachimg=1]

Cheers!

[attachimg=2]As you can see from the screenshot, the problem is that Firefox doesn't show the collection of images which are part of the verification process. Nothing! So since I can't click on the image to get the best match I always get the error message after typing the letters.

[attachimg=0]

oops, sorry about the multiple images. Dunno how that happened.

Joe, I've checked for an easy fix; there's no obvious one.

We're rolling our new network of sites slowly so don't really want to mess with our .CC forum much (here) since we need this one to remain online during the transition process.

Don't worry, as we roll the new space with me in full control of the code base, it's certain fellow Firefox users get to register without issues

We're going to use your quality testing services again as the new "BetSelection.is" space comes to life (thank you very much!) 

Hi Victor,

Thanks for the reply, but the issue seems to have resolved itself. No problem now replying to posts using Firefox, and actually there is no image verification at all. Maybe it only exists for a new user's first posts on the forum?

Quote from: CoderJoe on March 04, 2018, 09:21:12 AM[...]using Firefox, and actually there is no image verification at all.

Joe, I've checked & double-checked and it isn't our issue; it's definitely peoplesign.com having their https:// misconfigured.

https://peoplesign.com/

Peoplesign is our captcha image provider.

...Can't really do anything on our end but wait until we roll our own (home-grown) human verification code within our new server

Quote from: CoderJoe on March 04, 2018, 09:21:12 AMMaybe it only exists for a new user's first posts on the forum?

Yes, there's a bit of verification for new posters. It helps us keep the blatant/very obvious spam bots away

Glad to see it resolved for you; it means you're not a bot

Thanks again for your report!