1.1.4-RC5

Just as I was about to release 1.1 as stable, a bug that appears to be minor was reported.
it turns out, that it was not so minor, and the fix was pretty massive, and although I gave FireStats some serious testing after I fixed that bug, I can’t be sure I didn’t miss anything.
This means 1.1 will wait for at least another week before its declared stable.

30 December 2006 | FireStats | Comments

5 Responses to “1.1.4-RC5”

  1. 1 Mark UNITED STATES Windows XP Mozilla Firefox 2.0.0.1 30 December 2006 @ 11:49 pm

    Hey Omry:

    I love this plug in – installed the stable 1.02 version a couple of days ago and it was working like a charm. Last night I saw a notice for the new release version and downloaded it – since then the plugin doesn’t work. There are no icons and none of the buttons work…

    I’ve completely deleted the Firestats database entries and started again with the stable version and the same issues are happening.

    Please advise and keep upt he great work.

    Mark

  2. 2 omry ISRAEL Debian GNU/Linux Mozilla Firefox 1.5.0.7 31 December 2006 @ 12:21 am

    Mark, please open a ticket with more details.
    server OS, php version, mysql version, browser version, and any javascript errors you see on the the browser.
    also attach a screenshot of what you see.

  3. 3 omry ISRAEL Debian GNU/Linux Mozilla Firefox 1.5.0.7 1 January 2007 @ 12:58 am

    I have made a small fix related to windows servers, if you are running firestats on windows re-download 1.1.4 and try again.

  4. 4 greggl UNITED STATES Windows XP Internet Explorer 6.0 24 January 2007 @ 7:05 pm

    With the latest Wordpress 2.1, FireStat 1.1.5.stable doesn’t appear to be supported. Can you confirm? All I get on the Dashboard->Firestats page is your logo/link, but no data down below. With WP 2.0.7 and previous, the stats showed up perfectly every time.

  5. 5 omry ISRAEL Debian GNU/Linux Mozilla Firefox 1.5.0.7 25 January 2007 @ 12:05 am

    Greggl, I tested and it works fine.
    some users encountered a problem that is caused by reaching the PHP memory limit with the new wordpress and all of their plugins.
    Carol took the time to describe the problem and the solution here.

Leave a Reply

  1.  
  2.  
  3.  

Search

Navigation

Pages

Categories

Archives

Meta


FireStats - the blog