Submitted by CodeTRUCKER on 2009/08/24 16:54
Hi All,
 
Admitedly, this is probably not a bug with IQ, but since it is a "bug" with this IQ forum, I thought this the best place to ask for help.  FYI - I have already done the obligatory searches and have disabled every Firefox extension.
 
The "bug" is that when I try to reply to or author a new post I have no "Comments*" field to enter any verbiage?!?  I have to resort to IE7 to make a reply or post for help.
 
Has anyone seen this and/or offer any solution?
 
Fair winds,
Calvin

Comments

I get this all the time. I haven't taken the time to find out if Firefox, or win 7 64 bit is the culprit , but here's my  workaround,
 
I click "More information about formatting options", then go back in the browser, whereupon the comments area appears.

jan_rifkinson

2009/08/24 18:24

In reply to by KeithB

Keith, what exactly happens @ your end?  I ask only because I've always used FF for this forum w/o issues & I'm currently working on 64bit machine, again w/o issues. 
 
BTW, the task file you did is Tks
 
--
Jan Rifkinson
Ridgefield CT USA
HP Blackbird Vista Ultimate SP-2

KeithB

2009/08/24 19:56

In reply to by jan_rifkinson

[quote=jan_rifkinson]
Keith, what exactly happens @ your end?
[/quote]
It looks like that, just a blank area, "non-clickable"
 
I think the only things I've changed recently was getting a new computer with 64-bit, and changing some forum editor settings (to be able to get emoticons), that may be another possibility.
 
Since I'm not the only one with the problem, I'll experiment a little and see if the forum software settings may be the culprit.
 
 
 

CodeTRUCKER

2009/08/24 22:53

In reply to by jan_rifkinson

[quote=jan_rifkinson]
Keith, what exactly happens @ your end?  I ask only because I've always used FF for this forum w/o issues & I'm currently working on 64bit machine, again w/o issues. 
 
BTW, the task file you did is Tks
 
--
Jan Rifkinson
Ridgefield CT USA
HP Blackbird Vista Ultimate SP-2
[/quote]
 
FYI - the screenshot Keith posted is what I see too.
 
Fair winds,
Calvin

CodeTRUCKER

2009/08/24 18:25

In reply to by KeithB

Thanks, Keith.  It works! (but you knew it would, right?) 

I am guessing it has something to do with the PHP page load.  Has this been added to Mantis? 
 
Admittedly, it is a low priority now, but it ought to have a place holder so it can be addressed "someday."  Again, it is small potatoes, but it really should be addressed as far as what is within Pierre's power. 
 
Definitely want to ferret it out before IQ goes mainline!  Imagine hoards of (possibly) frustrated users being (possibly) frustrated with not being able to record their issues!?!  A recipe for a marketing disaster.  Would you agree?

Thanks again for the tip!
 
Fair winds,
Calvin

Strangely enough, I had this happen on the first post this evening, but it has worked properly since, for several posts.

CodeTRUCKER

2009/08/24 22:50

In reply to by KeithB

[quote=KeithB]
Strangely enough, I had this happen on the first post this evening, but it has worked properly since, for several posts.
[/quote]
 
FWIW - I still have to use your "method."
 
Fair winds,
Calvin

not very scientific,
but anytime there'S a problem with FF one of the first things I do is clear the cache.
 
Saying that I havent had this particular problem . .
 

CodeTRUCKER

2009/08/25 05:19

In reply to by Tom

[quote=Tom]
not very scientific,
but anytime there'S a problem with FF one of the first things I do is clear the cache.
 
Saying that I haven't had this particular problem . .
 
[/quote]
After some experimentation, it turns out that the culprit is the "sqlnotes.net" cookie; however, this creates a "Catch 22."  If I delete the cookie, the expected "Comments" text box shows up, but I lose my login status on the server and I am identified by the server as "Anonymous" and asked for my email address. If I want to be recognized by the server as a member, I have to re-log back in, but that re-populates the errant cookie!
 
If I figure it out, I'll update this thread, but I won't be offended if someone comes up with the solution before I do.
 
Meanwhile, KeithB's workaround is a solid performer!
 
Fair winds,
Calvin