Sorry folks, I'm sure someone had a really good reason for choosing/creating this forum software.
BUT when you change to a faster, more responsive version, please send out an email to announce it.
Turning out the light...
Closing the door....
a faster, more responsive version,
There may be several things that could improve this forum, but I find it plenty responsive. Perhaps you were experiencing a general internet problem. Every once in a while all of Logos sites seem to have performance problems...it occurred from time to time on the newsgroups too.
Please leave the light on...the rest of us are still here. [I]
I participate regularly in several forums produced by companies of comparable size and revenue base as Logos. Logos's is as quick or quicker than the others.
Slowness in loading or painting can be due to internet connection, computer processor speed, video card ram, and other processes going on at the same time
Sorry folks, I'm sure someone had a really good reason for choosing/creating this forum software. BUT when you change to a faster, more responsive version, please send out an email to announce it. Turning out the light... Closing the door....
I'm getting consistent javascript errors today. Haven't seen them before. But the forums are considerably slower.
Here's the error message:
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.Script: http://bible.logos.com/jsapi/referencetagging.js:1
The script happens on all pages, not only those you'd expect to find a reference tag on.
Weird...what browser are you using? I'm not seeing those at all using Firefox 3.5 or IE7.
Sorry folks, I'm sure someone had a really good reason for choosing/creating this forum software. BUT when you change to a faster, more responsive version, please send out an email to announce it. Turning out the light... Closing the door.... I'm getting consistent javascript errors today. Haven't seen them before. But the forums are considerably slower. Here's the error message: A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.Script: http://bible.logos.com/jsapi/referencetagging.js:1 The script happens on all pages, not only those you'd expect to find a reference tag on.
I've been having problems with Javascript as well since I got my new computer and began running 64 bit Vista. I think, however, my problem is different from yours since it only occurs when I run 64 bit IE. Then I get a message that I need to update Java. Then I'm told when I try to update that they don't have a 64 bit version ready. I solve the problem by using the 32 bit version instead. As I said, probably a different problem.
Using FF3.5 as well. I was having some trouble with FF seeming to be slow on other pages too. So I shut it down (had to kill it in task manager too) and flushed the cache with CCleaner. Seems to be fine for now. At least I haven't seen an error message in a while.
I'm using Vista 32bit. In Chrome it works fine. I avoid IE anything and haven't tried it in Firefox 3.5.
I'm getting consistent javascript errors today. Haven't seen them before. But the forums are considerably slower. Here's the error message: A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.Script: http://bible.logos.com/jsapi/referencetagging.js:1 The script happens on all pages, not only those you'd expect to find a reference tag on.
Richard, I've been getting the same message fairly regularly over the last month or two using Firefox 3.5 at work and at home. It's not just the Logos forums; it's any site with RefTagger installed. I'm fairly certain it's a conflict between RefTagger and at least one Firefox extension, but I haven't been able to pinpoint the problem extension. If I figure it out, I'll let you know. Please do the same. Once we identify the problem, perhaps we can optimize the RefTagger script to fix the conflict on our end.
I am running the Mac version of FF 3.5 and have experienced no problems. The only plugins I am running are Greasemonkey (with the Facebook delete app), Evernote Webclipper, Gmail notifier and Google Gears (currently disabled due to not being compatible with 3.5).
If you read my other post, you'll notice that clearing the cache using CCleaner fixed it for me. I have CCleaner clean out the Download History, Internet Cache and Saved Form Information (I leave the rest). It's possible something left in the cache was causing the conflict with an addin, since cleaning it has seemed to solve the problem.
YMMV.
Update:
Okay, so I was trying to get the forums to work with the AutoPager Addin. After looking at the tutorials and trying a few configurations, I started getting the same error again. So likely culprits are the AutoPager Addin, or the engine that drives Autopager, or some strange conflict with a codec somewhere.
Update 2:
Cleaning my cache again solved the problem, even after using AutoPager on a number of threads. So I'm at a loss. Maybe it will show up again later spontaneously. (BTW, AutoPager is one of my fav addons. And I did get it to work with these forums.)
Richard, could you please send me a list of all of the Firefox Extensions you had installed when you were having the problem? Feel free to post the list here or send it to phil@logos.com. Thanks!
I'll send you an email.
FYI, I was getting the same scripting error yesterday. This morning all seems to be going well.
Okay, TODAY, the forums DO seem slow. Is it just me? Other Logos sites are fine.
Todd,
Once again, it is not just the forums. My Firefox Browser is Sloooowww.
I actually went back to IE7 this morning. I am running Firefox next to it but it hasn't picked up speed. Could it be that invisible user feedback program that collects anonomous statistics? I just upgraded to the latest and that's when I noticed the lack of speed.
Ok, I'll grant that Firefox may be an issue: the whole browser is non-responsive when loading the pages, and IE7 doesn't show that particular problem. However it was fine just a few days ago, and I use Firefox all day long in my job and don't have the issue on other sites...at least that I'm aware of. So I'm guessing that it's Javascript changes under the covers that may be causing the problem with FF.
IE7 has it's own performance issues for me. It's much slower when scrolling than Firefox is.
Well, I eventully got a non-responsive Javascript error for http://bible.logos.com/jsapi/referencetagging.js:1
I noticed that FF was running large: 240M of memory. I restarted Firefox, and the forums are responsive again. Memory leak?
Well, I eventully got a non-responsive Javascript error for http://bible.logos.com/jsapi/referencetagging.js:1 I noticed that FF was running large: 240M of memory. I restarted Firefox, and the forums are responsive again. Memory leak?
One of our web developers "identified a bug in FF3.5’sregular expression engine that causes a specific kind of complexregular expression to perform extremely poorly." RefTagger uses just such a complex regular expression. The bug has been reported to Mozilla, and it should be fixed in a future version of Firefox—hopefully in 3.5.1.
Since it gets worse the more time the RefTagger script is run, you can alleviate the problem a bit by restarting your browser regularly. Another solution is to use a different browser in the meantime. We're also considering temporarily disabling RefTagger.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
