BUG: 1.2.3-RELEASE: Javascript error on "Diagnostics: Filter Reload Status" page



  • Here is the javascript error being reported from IE8 in both standards and compatability modes:

    Webpage error details

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET CLR 1.1.4322; Creative AutoUpdate v1.40.01)
    Timestamp: Sat, 19 Dec 2009 20:32:57 UTC

    Message: Expected ';'
    Line: 168
    Char: 51
    Code: 0
    URI: http://router/status_filter_reload.php

    Message: Object expected
    Line: 1
    Char: 1
    Code: 0
    URI: http:/router/status_filter_reload.php



  • I'm using osx with firefox.  I did the upgrade to final 1.2.3 from 1.2.2 and just noticed that my filter does not reload or change when it is supposed to; I've watched it for several minutes.  It was doing it before I upgraded to 1.2.3, so I don't know if there is something in 1.2.3 that doesn't like squid and snort together.  I updated squid today.  Also noticed a slow down on the machine once I had the upgrade installed.

    Any ideas?

    Thanks. ???


  • Rebel Alliance Developer Netgate

    The filter does reload, but this page doesn't refresh automatically.

    The other questions you have are unrelated, please start a new thread for those.



  • @jimp:

    The filter does reload, but this page doesn't refresh automatically.

    This will be my last input about this BUG, it´v been reported but no one seems be be able to solve the problem. More about older report here: http://forum.pfsense.org/index.php/topic,17969.0.html


  • Rebel Alliance Developer Netgate

    @DeCex:

    @jimp:

    The filter does reload, but this page doesn't refresh automatically.

    This will be my last input about this BUG, it´v been reported but no one seems be be able to solve the problem. More about older report here: http://forum.pfsense.org/index.php/topic,17969.0.html

    It can be solved, but as there won't be any more 1.2.x releases, it's sort of a moot point right now. I'm not sure if a ticket was ever opened on http://redmine.pfsense.org but even then, it may not be fixed. Development now is focusing on 2.0, and this is really just a cosmetic bug that can be worked around by hitting the refresh button in your browser a few times.



  • It won't be fixed in 1.2.x as there won't be any more releases, it's already fixed in 2.0. Note it's strictly cosmetic, the filter reloads work perfectly fine.



  • Right, time for fiddling  ;)

    I thought that this gotto be a Javascript fault so i look and replaced some lines and i got it to work. This what i did. From the webgui open (edit) this file  /usr/local/www/status_filter_reload.php

    …scroll down whare you see this:

    Replace with this:

    Hit save, now go and verify that the Status/Filter Reload page. Wait a sec and you should see that the page is giving you a reply: Done. "The filter rules have been reloaded."  :)

    Now 1.2.3 feeling more complete.

    Please notice that the script section is start with , replace section carefully!



  • Hi, I just finished the installation in an embedded system with Alix 6b2 motherboard and I have encountered this same problem. The solution proposed by DECEX helped me to correct the problem but I would like to confirm that it is replacing a variable by the constant of one of the available topics.

    Take this opportunity to acknowledge the help provided.

    Best Regards
    Jesús Berlínchez



  • Why won't these little bugs get fixed?  What's wrong with doing bug fixes on the 1.2.x track of a product that is intended (at least I assume) to be a viable enterprise alternative to the likes of Cisco, Sonicwall, Juniper, etc?

    (Please don't hurt me….. just askin')  :'(



  • I suppose someone could make a patch to install as a package on 1.2.3.



  • @valnar:

    Why won't these little bugs get fixed?

    Because we have very limited resources, there will not be another 1.2.x release unless it's necessary for a security fix, and with all our efforts focused on 2.0, we're not going to fix trivial things that have 0 impact on functionality. Git is available to the world, if it concerns you that much, make a merge request on RELENG_1_2.

    You obviously haven't used much Cisco gear, or any other vendor for that matter, if you think they fix little things like that, especially when they're getting ready to release a new major version. That's laughably untrue. I'm continually surprised how much better we do than huge vendors at many things like this.



  • @cmb:

    You obviously haven't used much Cisco gear, or any other vendor for that matter

    That's all I do in my day job.



  • And you've never run into bugs in IOS?  I certainly have.  Bugs much more serious than the above, which are never fixed :(



  • @danswartz:

    And you've never run into bugs in IOS?  I certainly have.  Bugs much more serious than the above, which are never fixed :(

    Actually, I've discovered several IOS bugs over the years and submitted them.  They got fixed.  I currently have one submitted for ASA 8.2x.  But now we're off subject, so I'll stop.



  • I didn't say they never fix any bugs - I have done the same as you.  I am saying I have found bugs that involved memory leaks and such, requiring reboots of the router every few days and finding out cisco would not fix them in the older release, requiring an upgrade to a newer (bigger) IOS image, which (in at least one case I remember), we couldn't do, because it was an older 2500 that didn't have enough flash.  "Cannot get there from here".


  • Rebel Alliance Developer Netgate

    The Cisco bit is especially irrelevant because someone earlier in this thread posted a solution for the bug and you could edit the file on your own system to fix it. Try that on a Cisco box. :-)

    Just because a whole new release isn't going to happen for a few minor bugs isn't a big deal when they can be patched manually by anyone who really hits them.

    https://rcs.pfsense.org/projects/pfsense/repos/mainline/logs/RELENG_1_2


Log in to reply