From: George Clark <gac@sp...> - 2004-12-29 04:43:12
My Apache log is flooding with the following messages.
[Wed Dec 29 04:41:27 2004] [error]
called but no skin found (so using default) for http://www.worcesterapa.org\n
[Wed Dec 29 04:41:27 2004] [error] Which was called by:main:PerlTransHandler
subroutine `Slash::Apache::IndexHandler':1:determineCurrentSkin called but no
skin found (so using default) for http://www.worcesterapa.org\n\n
Anything I can set to stop this?
From: Eric Dannewitz <ericdano@ja...> - 2004-12-29 05:05:45
Jamie and Shane said something to this effect.....
> Jamie McCarthy wrote:
>> Check your 'skins' table. A piece of data there may have not
>> been set up correctly during the upgrade. Check that your
>> skin named 'mainpage' has a nexus value that corresponds to
>> rows in the topics and topic_nexus tables that are your actual
>> mainpage nexus. E.g., on Slashdot:
> None of those things matched my site. I changed them. Don't really
> see any changes........my apache log is flooded with:
> 5.8.5/mach/Slash/Utility/Display.pm:470:cannot getSkin for empty skid
That's just debug-output that's still in the code from the
section-topics changes. You can comment it out in the code and make
install to remove it, removing won't affect anything.
Get latest updates about Open Source Projects, Conferences and News.