Can't change FTH2 admin

This problem is reproducible w/ Firefox if the change web page is loaded with http: instead of https: -- I have not tried this w/ Safari, but I suspect it is the same "trigger".

For some reason that I have not yet figured out the change page is getting CORS (cross origin security errors) errors when it is loaded w/ http: This is odd, since I am explicitly using relative URL references to avoid this sort of problem.

When I use Chrome, it forces the connection to be upgraded to https: for me, so the problem is not seen then.

For now, we need to make sure this page is loaded w/ https: until I can figure out how to prevent the issue.

NOTE: This issue may also apply to the new website setup page, since the coding is similar.

Ok, I have added a line of Javascript to force these pages to load w/ https: as a workaround until I can figure out the root cause of the CORS issue and fix it.

Every thing should work OK now.

Hi Steve,

Someone got the system to send me a confirmation request to change admins. Whoever did that, that you very much! I made the change successfully.

There's a page on the FTH2 site, "When previous administrator is no longer available." On that page is a link to www.toastmastersclubs.org/change/ . If I click that link, I am taken to the change page with http: (I looked at the page source) and it still doesn't work for me. But if I change the URL to https: it does.

So thank you for your research into this issue. You might want to change the link on the "admin no longer available" page to use https: since that seems to be the issue. I don't know if there are other links on the FTH2 site that might need to be changed.

And you might point out to Brian that "You have a local issue with your PC" was not the source of the problem, so jumping to that conclusion was a bit premature.

Thanks again,
-Ken

kenbraly wrote: And you might point out to Brian that "You have a local issue with your PC" was not the source of the problem, so jumping to that conclusion was a bit premature.

Maybe, but please understand that we are still a bit on the learning curve about some of the nuances of supporting https in the system, and this problem was actually the result of a combination of subtle factors that only showed up in certain browsers, so I think you should cut Brian some slack.

I had to really dig for the factors that caused the problem, and I was only able to determine that it was https related from your posting of the Javascript error messages and doing some Google searching for whether https can cause CORS errors in Javascript. (It can.)

I could probably make a reasoned argument that https is not really needed for this form, but since our support for it for the websites was getting muddied with this form (which really is a system form not associated w/ any particular club) in this case, I just decided to save myself some future headaches and I am now forcing the form to load w/ https.