[Imc-bristol-tech] Re: [Oscailt] Bug with internet explorer?
crash at subsection.org.uk
crash at subsection.org.uk
Wed Feb 1 19:10:47 UTC 2006
my last email can be ignored as we did have an archive of Oscailt 2.0.4
intact. We appear to have solved the problem and think it was related to
the publishcomments.php file, although were unable to pinpoint the exact
code. Good old internet exploiter.
-------- Forwarded Message --------
From: crash at subsection.org.uk
To: oscailt at lists.indymedia.org
Subject: Re: [Oscailt] Bug with internet explorer?
Date: Wed, 01 Feb 2006 18:26:29 +0000
Re. our internet explorer bug, I have rolled back as far as I can with
all three files and unfortunately this bug is still with us. I also
can't find the oscailt software, which I think I remember was accessible
If I can find the original download for V.2 I will have a go at using
the original release version of these files.
On Tue, 2006-01-17 at 12:45 +0000, chekov wrote:
> Crash wrote:
> >at Bristol imc, we have recently come across a bug -- we're not sure whether
> >this has been reported on other sites; if not it's possibly something we've
> >When adding a comment to a story on our site, Internet Explorer gives the 'Oops!
> >Cannot add comment as no story has been specified !' error, which suggests that
> >$comment->story_id is set NULL.
> >This error does not occur on Mozilla-based browsers. Are you aware of this bug
> >occurring on other sites? If not I will see if there is someone here with a bit
> >more knowledge of browser compatibilities than myself.
> >BIMC Tech
> Hi Crash,
> I'm getting the bug using Firefox 1.0.7 trying to comment on story 24586
> - your current feature.
> In fact I'm getting it whenever I try to comment on a feature - but not
> when I try to comment on regular stories.
> We haven't seen this bug before, so it is difficult to say what is
> causing the problem. The error text does not indicate that the story id
> is null, but that the story query object (objects/storyquery.inc) has
> found no stories in the database to match the query - which is not
> correct behaviour since the relevant stories are there.
> In terms of finding and fixing the source of the bug, I'd suggest a
> couple of things.
> 1. Look at the feature entry in the story type table (edittypes.php)
> and make sure the excluded setting is not set and make sure that the
> active setting is set. I'm not sure that these settings could prompt
> the error, but they're a good place to start looking.
> 2. Roll back any recent changes you might have made to the
> objects/storyquery.inc or publishcomments.php files to see if this makes
> the bug go away.
> 3. enable sql debugging. In objects/systemconfig.inc set the value of
> $sql_debug to 1. This will print the content of all the sql statements
> executed to file. With this setting turned on, try to comment on a
> feature, capture the resulting output and send it to this list - that
> should allow us to find the source of the problem.
> Hope this helps
> 1 of imc.ie
More information about the Imc-bristol-tech