From: SourceForge.net <no...@so...> - 2006-11-29 19:42:50
|
Bugs item #1605121, was opened at 2006-11-29 02:55 Message generated for change (Comment added) made by dhsanto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1605121&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: macosx-specific Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: David Schmidt (david__schmidt) Summary: missing file or symlink or incorrect installation of same? Initial Comment: Version of Privoxy: 3.0.6, via installer.pkg. DL-Date: 11/28/2006 Mac OS X v10.4.8 Apple built-in firewall. Clamav. Safari "kill popups" UNchecked. Privoxy only, unless you count POPfile? Safari v2.0.4 (419.3) Mac OS X 10.4.8. email: dh...@wi... Privoxy 3.0.6 works just as well as version 3.0.3 did. In the "config" file in /Library/Privoxy, I commented-out the user-manual URL - http://www.privoxy.org/user-manual/ - and substituted my own, just where the installer had installed it - /Library/Privoxy/user-manual/. When viewing the Privoxy "main page" and clicking on "Documentation," the page displayed! However, while inspecting the logfile, I saw an error listed. Apparently, within one(?) of the Privoxy files, "index.html" is appended to the config-file URL (/Library/Privoxy/user-manual/) and the page displays, but, the error states that Privoxy can't find the "p_doc.css" file AND it's looking for it in /Library/Privoxy/user-manual/! Well, it's NOT there, nor is there a symlink. It IS IN the top directory - /Library/Privoxy/. So, the easiest thing to do was to put a symlink into the user-manual folder. That cured the logfile error, but, it did nothing to change the displayed main page. I suspect that the cascading style sheet may have to do with the cgi interface? As far as I know, I'm just using html. I could be wrong though. Dave Santo dhsanto"AT"wildblue"DOT"net ---------------------------------------------------------------------- Comment By: dhsanto (dhsanto) Date: 2006-11-29 12:42 Message: Logged In: YES user_id=1656669 Originator: NO Always appreciate good comments. My main point was that the Privoxy installer.pkg DID NOT INSTALL "p_doc.css" (file OR symlink) into the user-manual sub-folder but Privoxy LOOKS FOR IT there anyway and produces an error-line in the logfile because it doesn't find it there. The file DOES exist in the top directory. So, my conclusion was: the installer didn't install "p_doc.css" into the proper (sub-)folder OR if "p_doc.css" is supposed to be in the top directory, a duplicate or a symlink wasn't installed into the user-manual sub-folder. The fault probably lies either within the installer.pkg itself or in the file that produces the (output-to-screen) documentation. Like I stated in my original post, "So, the easiest thing to do was to put a symlink into the user-manual folder," but should any of the developers of Privoxy wish to correct this extremely minor matter, at least now they're aware of the issue. ---------------------------------------------------------------------- Comment By: Fabian Keil (fabiankeil) Date: 2006-11-29 05:41 Message: Logged In: YES user_id=875547 Originator: NO A symlink should do, but of course the differences with and without external style sheet are easy to miss if one doesn't compare them directly. I think the most visible change is that on some pages Privoxy and other applications names are colored in red (if they are tagged in the source). On the index page that's not the case, however the style sheet still affects the font settings and the indentation. ---------------------------------------------------------------------- Comment By: Hal Burgiss (hal9) Date: 2006-11-29 03:53 Message: Logged In: YES user_id=322640 Originator: NO The user-manual should look like the one that's linked from privoxy.org. Its the same stylesheet. I believe the locally installed one must have the stylesheet in the same directory, so try copying it instead of the symlink. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1605121&group_id=11118 |