You notice how this plug-in reacts to not filling in all the required fields in a comment form? Seems to inject a little to much back on the page, right? On this site, it even changed the layout from fluid to fixed width because it loaded install.css as well.
Here’s the fix for that:
Open /ajax-comments-wpmuified/ajax-comments/ajax-comments.js
change:
msg = r.substring(r.indexOf('</h1>') + 5, r.indexOf('</body>'));
to
msg = r.substring(r.indexOf('<p>') + 3, r.indexOf('</p>'));
The end.
I will keep this very short. If you’re getting the “Operation Aborted” message on your WordPress site, it may be related to a Lightbox version with some old world coding.
Just make sure you’re using Lightbox by Rupert Morris.
The offending code in the “bad” version started with:
objBody.appendChild...
This was in the initialize function of the class that loaded along with the script in load-time. In other words, it was attempting to add child nodes to the <body> while the body tag was still being loaded (and had not yet been closed). IE7 apparently really doesn’t like this.
Although we all love to use Firefox, we have to admit it’s not the fastest app to launch. I always thought that its bottleneck was its modular XUL plug-in technology. After all, extracting plug-ins from compressed containers, then interpreting and integrating the contents to the app each time it launches, on-the-fly does take some CPU time, disk ops and memory allocation time.
Firefox 3 however has some improvements that should make it a phenomenal foe to IE7 when it comes to speed.
- Defragmentation, which has reduced memory usage after startup in more than one third.
- Image cache, fonts cache, back/forward cache, and more. They have all been tuned up to free used resources after certain time of inactivity.
- Uncompressed images are discarded from memory after a while if not active.
- More efficient animated GIFs storage in memory.
- About 400 memory leaks have been hunted and taken down thanks in part to better tools to identify them.
- A cycle collector takes care of objects referencing each other preventing either of them being cleared from memory.
Xillionation. To ‘xillionate’, meaning to separate a decimal number by its thousands delimitations. (1000000 becoming 1.000.000)
This word was spawned while coding a function that (so conveniently) does exactly what the word describes.
- Tanin
