Release 4.35 and FireFox

[jkunes]

I upgraded Nettalk from 4.30 to 4.35 yesterday and I brought in everything including all of the examples.  My application works mostly correctly in IE, however in FireFox it is really broken.  And I tried several of the example apps and got the same results.  In FireFox the browses do not work.  Cannot select records from the browses at all and none of the buttons on the browse page work.  Because the initial browse doesn't work I haven't been able to try much else in FireFox except logging in, which DOES work.  I suppose there is something I have missed.  Please let me know.

I also experienced the same problem as described in vsorensen's post from yesterday, using IE.  I made some modifications to my application, which fixed it.  I did not experience the same behavior in the example apps.

Thanks.

[jkunes]

I am still having the same problem.  I reinstalled Nettalk 4.35 including the examples and I compiled example 21.  It works as expected in both IE6 and IE7.  In Mozilla Firefox 3.0.11 the browses do not work.  The menu works, as I am able to select any of the browses.  The browse page is displayed as expected, however I can do nothing else - cannot select records and none of the buttons work - it acts like it is frozen.  Can someone else try Nettalk 4.35 and example 21 with Firefox 3.0.11 and let me know if it works for you please?

Thanks,
Jill

[Bruce]

Hi Jill,

My guess is that the script files etc are cached in your copy of firefox.
Open the page and press Ctrl-F5 to reload all the script files.

Hopefully you've remembered to update your web folder in your app.

If that doesn't help then it sounds like you have either cookies or javascript turned off in your FF browser.

Cheers
Bruce

[jkunes]

Thanks Bruce,

Ctrl-F5 did the trick.  I had tried that several times before but apparently not at the right time - probably I did it before selecting the local host site.  Also, I had restarted my machine several times over the course of the last few days and assumed that would take care of the caching problem anyway.  Guess not.  Apparently IE doesn't do caching the same way Firefox does.  I will see if I can turn caching off in Firefox as this was a bit of a pain.

Jill

[Bruce]

Hi Jill,

you definitely want to keep caching on - it makes a huge difference to site performance. Otherwise it would need to download the scripts & styles with _every_ page. Just remember to press Ctrl-F5 if you get wierd behaviour after an update.

Cheers
Bruce