Stories not showing in Firefox or Safari
codatory
ago. We have 2 projects, one with over 200 stories that is behaving
strangely. Everything is working fine in Chrome and Opera, but Safari
and Firefox are flaking out and not showing any stories (and thus
nothing works). The JS Console in both browsers gives the following
bit of insight:
'end iteration number must be greater than start iteration number'
when calling method: [nsIDOMEventListener::handleEvent]'
We're running pretty close to the github repo with only some minimal
config changes (database, registration emails limited to our domain,
general Heroku stuff, etc.). All of our functional changes have been
submitted and accepted as pull requests.
This just started when I updated sometime within the last week. Units
and Functional tests look OK, but Jasmine complains about a couple
things. (image: https://img.skitch.com/20111005-mc83exj6ycmw2qn16ybwe35g3b.png)
Any suggestions where to look? Is anyone else seeing similar things?
I'll look into it further as time permits but was hoping others had
more evidence for me to look at.
Malcolm Locke
> I'm having a little trouble with Fulcrum after I updated a few days
> ago. We have 2 projects, one with over 200 stories that is behaving
> strangely. Everything is working fine in Chrome and Opera, but Safari
> and Firefox are flaking out and not showing any stories (and thus
> nothing works). The JS Console in both browsers gives the following
> bit of insight:
>
> 'end iteration number must be greater than start iteration number'
> when calling method: [nsIDOMEventListener::handleEvent]'
Can you put the following debug in around line 92 of
public/javascripts/models/iteration.js:
if (end < start) {
console.debug(startIteration.attributes);
console.debug(endIteration.attributes);
throw "end iteration number must be greater than start iteration number";
}
> We're running pretty close to the github repo with only some minimal
> config changes (database, registration emails limited to our domain,
> general Heroku stuff, etc.). All of our functional changes have been
> submitted and accepted as pull requests.
Are all of your changes pushed to your github fork? If so, which one is
it :) I'll try and reproduce on a fresh clone of your repo.
> This just started when I updated sometime within the last week. Units
> and Functional tests look OK, but Jasmine complains about a couple
> things. (image: https://img.skitch.com/20111005-mc83exj6ycmw2qn16ybwe35g3b.png)
>
> Any suggestions where to look? Is anyone else seeing similar things?
> I'll look into it further as time permits but was hoping others had
> more evidence for me to look at.
I'm scratching my head over this. I've tried, unsuccessfully, to
reproduce this on Firefox (mine is pretty out of date though, 3.6), and
Safari (version unknown).
I'm suspecting the failure on 'should return a readable created_at' is
a bug related to UTC. I didn't write that code, so will have a dig
around and see what's going on.
The error on 'should have the iteration number and date' is probably
just a difference in the default output of toDateString() from that
particular browsers Javascript engine. We may have to modify that test
or explicitly set the format.
A few questions:
* What is your default language / locale?
* Which git revision are you at? (git rev-parse HEAD)
* Which versions of Safari and Firefox are you running? Do you get the
Jasmine errors on both?
Malc
malclocke
development machine.
Issue filed at https://github.com/malclocke/fulcrum/issues/57
Malc
Malcolm Locke
https://github.com/malclocke/fulcrum/commit/2c5de8470cc8dce011310808fb462acd0b181c16
Malc
codatory
On Oct 18, 5:42 am, Malcolm Locke <m...@wholemeal.co.nz> wrote:
> This is should be fixed now on the master branch.
>
> Malc
>
>
>
>
>
>
>
> On Mon, Oct 17, 2011 at 03:59:44PM -0700, malclocke wrote:
> > I can confirm this problem on Firefox 7.0.1 now that I've upgraded my
> > development machine.
>