[...]> These files are all installed with perm 0600 and so, AFAICT, wwwoffle won't > serve them. > ./en/messages/README.CONF.txt > ./en/README.CONF.html > ./en/FAQ.html
These files are all auto generated at compile time. The default ones in the tar file have the correct permissions. It must be something to do with environment where they were created.
Mmmm,.. My Umask is 0077. Not unreasonable but I guess that's probably why I get this problem and others don't.
> Tiny typo in wwwoffle.css. The "BODY.wwwoffle-message" values should end in > semi-colons or they'll have no effect.
Good catch.
Unfortunately, I still can't quite get WWWOFFLE to do what I want.
If I change the "BODY.wwwoffle-message" properties this affects the (WWWOFFLE generated) ftp directory listing too - which isn't the effect I'm looking for.
Ideally I'd have sections like this in the CSS to play with;
"BODY.wwwoffle-message" "BODY.wwwoffle-error" "BODY.wwwoffle-ftp-listing" "BODY.wwwoffle-control"
BTW, if I could, I'd configure out WWWOFFLEs urge to create the directory listing, and let the browser do the work - but I can't find a way to do that. Would that break anything but "Monitored pages" - which I don't use.
---- End of even slightly interesting bit - Start of waffle ----
This is in an effort to make the three most common WWWOFFLE errors that (my) users see absolutely crystal clear - that they are from wwwoffle in the first place, and what to do before bugging me about it.
Bear in mind that I'm trying to make this easy enough for kids to use.
I thought I'd make the WWWOFFLE generated page backgrounds a lurid colour to get their attention.
I'm thinking of; 1) "HostNotGot.html" 2) "RefusedRequest.html" 3) "ServerError.html" - when generated with the error "SSL proxy connection while offline is not allowed." message.
'1' and '2 are easy enough.
I can't alter "ServerError.html" to say "Bring up the Internet connection for that URL", *only* for that particular error though.
I admit I've never seen ServerError.html tell me about any other error, but altering "ServerError.html" still isn't anything like the right thing to do.
I suppose it must make sense programmatically, but '3' just doesn't feel like a 'server error' to a user - it just means they forgot to connect to the Internet.
Regards TonyC
