Not being a native English speaker, this sure presents a new meaning to 'unrelated'! Turns out all along it meant 'I have absolutely nothing to do with whatever broke out there, didn't touch that program in a month, must be the new guy doing whatever he's been doing'. Pleaze korrekt me bad inglish if u pleese?
Anyway, I'll put it on the list of 'Things to do when you want a lazy afternoon'. Just for future reference, you never know when it'll come in handy.
Well it now seems to be fixed, not been able to log in for 2 days until now.
I tried posting a new thread earlier, and also tried responding to one, and it doesn't appear to have taken either.
Edit: But I see that this one posted successfully.
Some people are saying they're still having trouble logging into the site.
If this is wide-spread, i'd like to know about it.
email me at email@example.com
I logged off yesterday and attempted to log back on, but it wouldn't let me. I closed and reopened IE but it still didn't work. However, I could log on OK this morning. I turn my PC off at night and back on in the morning, so maybe that has something to do with it (or maybe it's just a coincidence).
There was a MAJOR bug in CGILIB that was introduced when we added a feature that allows our customers to use CGILIB's substitution (scan/replace) tools for emailing. The concept was to allow folks to call CGILIB subprocedures to merge data with text or HTML-based email and then send the email using whatever.
To do that I added a MODE to CGILIB that would avoid running certain Web Server calls which would cause them to blow up if the server was not started or the job wasn't a web server job.
However, if you (i.e., the programmer) did not set back that mode value to its "run normally" mode, it continued to run in non-Web Server mode or "read-only" mode.
I was just as guilty as my customers, in that I would simply not remember to reset that value after calling CGIINIT().
Today I discovered this bug and automatically reset the CGILIB mode back to normal after its read-only stuff has been run.
Assuming I didn't miss anything, this should correct a number of bugs in MidrangeNews, including:
Posting a comment and the comment jumps to the Edit/Change Existing Comment box and never posts.
Sign On ignoring your user ID and password unless you were already signed in.
Creating a new Article for the website dropped some of the items.
Creating a new Discussion Thread would fail.
Pretty much anything that posted data to the site would fail, but ONLY AFTER a site user sent themselves an email or a new user signed up and an email was sent to them, and then your web session was routed through the same webserver job. I know, what are the odds? But HTTP Server for i does like to reuse the most recent jobs over and over, so it happened frequently.
Thanks for everyone's complaints--it led me to look into some of these issues that seemed like they were working (and were) but just not always--the most difficult of bugs to track down.