New Changes

Posted 2 March 2008 by

I've made some changes to our custom javascripts and some of our backend code. I've also enabled compression of the webpages. Hopefully, things will be more responsive. Our biggest change was the migration from the Prototype javascript library to the jQuery library. Most of the behavior is the same, although some bugs have been fixed. Our most noticeable change was replacing the existing spellchecker with a new one: GoogieSpell.

58 Comments

PvM · 2 March 2008

Search goes to a login page

Reed A. Cartwright · 2 March 2008

Huh. I just tested it now and it is fine.

PvM · 2 March 2008

yes, it works... Hangs head in shame

flashbaby · 2 March 2008

sorts my speling out to

Frank J · 2 March 2008

I know this is OT, but since the thread is about computers, maybe someone could help.

Can anyone recommend a way to access Talk.Origins to a komputer klutz, now that Google Groups has been blocked?

I'm not a fan of GG, but I want to avoid going from the frying pan into the fire. I don't need bells and whistles, just ability to post. I can still search old posts with GG.

Pete Dunkelberg · 2 March 2008

Frank J, get a real news reader such as Free Agent. You won't miss GG.

Frank J · 2 March 2008

Thanks, Pete.

I think I found the site, but don't see anything "free," but rather $29 to download. Is that the right site? The cost is not a problem (I won't do monthlies, however) but I would like to know what I'm getting - or if it'll even work, before paying.

Pete Dunkelberg · 2 March 2008

google free agent reader for the free version. You'll like it. Once back in the group you can ask people which readers they like. There are lots.

Henry J · 2 March 2008

I’ve also enabled compression of the webpages.

I wonder if that's why a right-click download of a page doesn't work any more? It's getting the compressed version? Henry

Reed A. Cartwright · 2 March 2008

Henry J: I wonder if that's why a right-click download of a page doesn't work any more? It's getting the compressed version?
That could explain it, especially if your browser isn't bothering to decompress it for you before it saves it.

David B. Benson · 2 March 2008

New spell checker link is to the upper right.

"abiogenesis"

is not a word in this spell checkers dictionary, either.

But it is much faster!

Henry J · 2 March 2008

“abiogenesis” is not a word in this spell checkers dictionary, either.

Well off coarse knot, sense it wood brake awl the laws off probability if it happened. Henry

Reed A. Cartwright · 2 March 2008

bump

Shebardigan · 2 March 2008

Any chance that we will ever again see the nifty "go to last read comment" from the earlier version of the site? Trying to find the new material in the longer threads is a serious pain.

Reed A. Cartwright · 2 March 2008

Shebardigan: Any chance that we will ever again see the nifty "go to last read comment" from the earlier version of the site? Trying to find the new material in the longer threads is a serious pain.
Huh? It was only away for about a week back when when changed the style of the blog. I recently changed the backend, but the behavior is the same. Click the "comments (#)" link under a post title to go to the new comments.

Shebardigan · 2 March 2008

Reed A. Cartwright:
Shebardigan: Click the "comments (#)" link under a post title to go to the new comments.
I do that, and I am transported to the very first comment, each time without fail.

Shebardigan · 2 March 2008

Reed A. Cartwright: Click the "comments (#)" link under a post title to go to the new comments.
I do that, and I am transported to the very first comment, each time without fail.

Reed A. Cartwright · 3 March 2008

What browser are you using? Do you have cookies disabled?

Shebardigan · 3 March 2008

Moreover, at this point even the workaround I had been using is now broken. I would leave interesting threads open in a tabbed session (browser is Opera latest version on Mac OS X) and hit Apple-R to refresh the page, which would leave me at the last position but show the new entries below.

At the moment, doing a refresh sends me back to the top of the page.

This appears to be PT-specific, because I can still use the refresh strategy at antievolution.org.

Shebardigan · 3 March 2008

Cookies are enabled. In fact, everything is turned on for this site. Looking at the cookie cache, I see only the entries for name, email address and URL.

Return-to-last was working before the change, but never since.

Reed A. Cartwright · 3 March 2008

When you click on the comment link, you are initially destined for the #comments-new location. If you are destined there, a javascript in the page looks at a cookie to see what the last comment you viewed was and then changes your locating to to go there.

However, if it can't find a former location, then it sends you to the #comments location.

So when you click a link containing #comments-new, does your address bar change at all?

Shebardigan · 3 March 2008

Clicking on the comments link causes the address bar to change to http://pandasthumb.org/archives/2008/03/new-changes.html#comments-new

Bringing up Firefox, this behavior takes me to the last read comment, and I see a cookie in the cache named last_comments_a. For some reason, something is no longer setting cookies properly in Opera.

Reed A. Cartwright · 3 March 2008

It sounds like Opera isn't executing the script at all.

What version are you using, I'll experiment with it some.

shebardigan · 3 March 2008

Under Firefox, the address bar indicates http://pandasthumb.org/archives/2008/03/new-changes.html#comment-144798

Shebardigan · 3 March 2008

9.26. Same behavior on both Windows and Mac OS.

Reed A. Cartwright · 3 March 2008

I figured out the problem. Opera doesn't support the Object.toSource method in javascript. I've added a work around.

Reed A. Cartwright · 3 March 2008

Let me change that, I'm working on a workaround.

Reed A. Cartwright · 3 March 2008

I've fixed the problem by implementing a version of toSource that is compatible with Opera.

You may need to clear a last_comments_a cookie if it is set to get the jump to work right. My previous attempt to fix it last night created a corrupted cookie that needs to be removed.

Bill Gascoyne · 3 March 2008

WRT getting to new comments, FWIW I noticed the same thing, clicking on "Comments" for new comments took me to the first comment, but after I scrolled down, finished reading, and went back to the home page, it worked the next time I tried it. So my experience was not that the feature stopped working altogether, rather that it was a one-time reset that started working again after I "re-initialized" it.

Shebardigan · 3 March 2008

All is well. All manner of things are well.

Many thanks.

W. Kevin Vicklund · 3 March 2008

Our most noticeable change was replacing the existing spellchecker with a new one: GoogieSpell

I am an Amurkin, so I'm naturally irony-deficient, but would that count?

Henry J · 4 March 2008

misssppellede worddss

Ze spel checkerrr doesn't seem to work for me.

It says "No spelling errors found" for the above sentence.

Henry

Stacy S. · 4 March 2008

I am unable to "Quote" anymore ... any advice?

shebardigan · 4 March 2008

Stacy S.: I am unable to "Quote" anymore ... any advice?
Additional info: works with Firefox, does not work with Opera or Safari.

Reed A. Cartwright · 4 March 2008

Stacy S.: I am unable to "Quote" anymore ... any advice?
Fixed. The problem is that jQuery wants to fire my toSource on random objects. If these objects are huge, it breaks the interpreter. If I know this is happening, I can direc toSource to break early.

Shebardigan · 4 March 2008

Reed A. Cartwright:
Stacy S.: I am unable to "Quote" anymore ... any advice?
Fixed...
Still seems to be broken with Safari (persistent finger cursor and 50% CPU load but no quote function).

Reed A. Cartwright · 4 March 2008

If you can find your javascript error console and send me the error message, I'll see what I can do. I may just have to abandon jumpto in favor of quote.

Reed A. Cartwright · 4 March 2008

The Safari bug is similar to the Opera bug, but my opera work around does not work.

I'm going to need to figure this out.

As for the spell checker I'll get that to work again. It may have something to do with cookie handling.

Shebardigan · 4 March 2008

Reed A. Cartwright: If you can find your javascript error console and send me the error message, I'll see what I can do.
I can't find any way to evoke that in Safari, but then I almost never use Safari. We'll just have to wait for some MacManiac to get sufficiently exercised in this regard.

Reed A. Cartwright · 4 March 2008

bumping

Reed A. Cartwright · 4 March 2008

Shebardigan:
Reed A. Cartwright: If you can find your javascript error console and send me the error message, I'll see what I can do.
I can't find any way to evoke that in Safari, but then I almost never use Safari. We'll just have to wait for some MacManiac to get sufficiently exercised in this regard.
I found it with a copy of Safari for windows.

David B. Benson · 4 March 2008

Spell checking works for me using Firefox 1.5.

Reed A. Cartwright · 4 March 2008

I'm still working on it, trying to get it to work properly with the rest of the site.

Reed A. Cartwright · 4 March 2008

Bump/rebuild

David B. Benson · 4 March 2008

Spell checking still works for me.

Stacy S. · 4 March 2008

"Reed A. Cartwright said:
Stacy S.:

I am unable to “Quote” anymore … any advice?

Fixed. The problem is that jQuery wants to fire my toSource on random objects. If these objects are huge, it breaks the interpreter. If I know this is happening, I can direc toSource to break early."

I'm a computer ZERO - don't know WHAT you are talking about :-(

Reed A. Cartwright · 4 March 2008

rebuild bump

Reed A. Cartwright · 4 March 2008

Okay, everything now appears to be working in Opera and Safari.

Reed A. Cartwright · 4 March 2008

I'm going to need to do a full rebuild before all the pages are updated.

Stacy S. · 4 March 2008

Reed A. Cartwright: rebuild bump
YAY!! You fixed it!! :-) Thank you!

Stacy S. · 6 March 2008

I don't know if anyone is still reading this, but I've often thought it would be nice if there were a link back to the "Main" page down at the bottom. :-)

Henry J · 6 March 2008

Stacy S.: I don't know if anyone is still reading this, but I've often thought it would be nice if there were a link back to the "Main" page down at the bottom. :-)
I just use multiple tabs (or windows), so the main page is still right where I left it. Henry

Altair IV · 7 March 2008

As a lurker who visits fairly regularly, but not every day, I'm still wishing for something on the front page that tells you when there are new comments on any particular thread. Even with the help of the jump-to-new-comments feature, it gets very tedious having to load up every single thread to see if there's anything new. My memory just isn't good enough to recall the number of comments that existed the last time I visited, on all of the 30 or so extant posts.

Even something simple like "last comment, March 5th at 11:45" appearing as a tooltip on the "new comments" link would work. Then I'd only have to remember approximately when I last visited PT.

A "closed to new comments" message when they've been turned off would also be nice.

In any case, keep up the good work.

Reed A. Cartwright · 7 March 2008

That is going to be way more difficult to do than what we have now.

I doubt that I will ever have the time to create such a feature. Maybe when I find the time to write my dynamic comments plugin, I can include that feature.

Citizen Z · 9 March 2008

Altair IV: As a lurker who visits fairly regularly, but not every day, I'm still wishing for something on the front page that tells you when there are new comments on any particular thread. Even with the help of the jump-to-new-comments feature, it gets very tedious having to load up every single thread to see if there's anything new. My memory just isn't good enough to recall the number of comments that existed the last time I visited, on all of the 30 or so extant posts. Even something simple like "last comment, March 5th at 11:45" appearing as a tooltip on the "new comments" link would work. Then I'd only have to remember approximately when I last visited PT. A "closed to new comments" message when they've been turned off would also be nice. In any case, keep up the good work.
The most convenient way I've seen to do this is to simply list the number of comments in a thread followed by a (+4) or whatever number of new comments there are since the last visit. No doubt technically more involved, but the presentation & usefulness are hard to beat. (Fark.com does this in their individual comment threads.)

Henry J · 10 March 2008

Maybe a series of pages that list the threads in descending order by date/time of last comment? As it is, if somebody adds comments to old threads (those that have fallen off the main page), few people will ever know it.

Henry

David B. Benson · 15 March 2008

Reed --- When using Firefox 1.5.0.12, clicking on any link, such as for the comments or the entire main thread or the 'more' result in causing that Firefox to terminate. This only occurs within Panda's Thumb.

This does not occur when using Firefox 1.0.

Reed A. Cartwright · 15 March 2008

Firefox 2.0.0.12 runs fine over here. If you are having issues with 1.5, it is probably going to be difficult for me to help you.

If you turn off javascript does it still happen?

Does it happen if you click on the Links link instead of any individual links page.

If you disable your extensions does it still happen?

What about in Mozilla safe mode?

Have you tried clearing your cookies and cache?