« Viva el Hot Fuss | Main | KR apparently requires Class::ISA. Install it! »
September 11, 2004
busy, logging still on the horizon
If anyone is actively waiting for the logging functionality I have talked about to hopefully diagnose KR issues, I am regrettably going to be working 70 hour weeks for the next 2 weeks (and am on my way for this week) which does not leave a lot of time for hobby efforts.
If anyone skilled in the ways of Perl does install KoalaRainbow and notices any bugs, please do let me know, as putting out a patch release isn't so bad time-wise.
Posted by sombrero at September 11, 2004 02:15 AM
Comments
Hi, I'm not "skilled in the ways of Perl" but I'm getting an error, so I figured I'd let you know. The functionality looks awesome, but I get this error:
Can't locate OnlyTheWind/KoalaRainbow/WebGui.pm in @INC (@INC contains: ./extlib ./lib /usr/lib/perl5/5.6.1/i386-linux /usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1/i386-linux /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.6.1/i386-linux /usr/lib/perl5/vendor_perl/5.6.1 /usr/lib/perl5/vendor_perl .) at krgui.cgi line 31.
Any ideas on how to fix?
Posted by: Mark at October 24, 2004 03:51 PM
I think that problem is resolved in 0.10.1. Are you using 0.10.1?
Posted by: sombrero at October 28, 2004 09:02 PM
Oh, duh. I downloaded the plugin pack from MT and it didn't even occur to me to check for the new version. Sorry... and thanks!
Posted by: Mark at October 28, 2004 10:37 PM
Well, I've solved the ISA.pm issue - Class::ISA needs to be installed on the server.
One thing I've noticed, though, is that when KoalaRainbow is active on the server, it takes a very long time for the MT backend to respond. Considering I'm running the server on my local lan, when the page takes 30 seconds to load, there's something a bit off. Normally it's 1 second or less.
Posted by: Twyst at November 11, 2004 12:01 AM
Oooh, the Class::ISA thing could be the problem everyone is having. Curse Debian and its shielding me from the rest of the world. I will look into that more.
In any event, if you have a page with an extremely complex KoalaRainbow graphic that gets regenerated anytime you make a change, such as the fancy blurry thing on your front page, it is not surprising that you response time would suck. If you aren't even using KoalaRainbow tags, then something is very very wrong. If you are creating a complex graphic, perhaps trying something simpler, or ensure that you are expressing constraints such that they can be propagated to the DB request. If you are using a non-SQL backend, of course, that won't make a difference.
Posted by: sombrero at November 15, 2004 09:00 PM
Post a comment
Thanks for signing in, . Now you can comment. (sign out)
(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)