Existing users, 
 PithHelmet - 2.8.4Safari 3.2 plugin adds content filtering & site preferences |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
How to make PithHelmet work for Safari 4 and later versions - Version: 2.8.4, 6/28/2009 05:02PM PST
Thunderforge8
I'm becoming disenchanted - Version: 2.8.4, 6/11/2009 10:06AM PST
Doctor J
I've used PH for years, and have paid the shareware fee. It was a godsend at first, blocking lots of unwanted junk. However, support for this product has deteriorated significantly in the last year or two:
* Bugs are not being fixed (I've reported one several times).
* Updates (or, rather, lack thereof) do not keep up with Safari versions.
I realize that this is shareware. However, I *did* pay the fee that the developer requested. I'd pay more, if i were confident that the quality and support would return to their previous levels.
* Bugs are not being fixed (I've reported one several times).
* Updates (or, rather, lack thereof) do not keep up with Safari versions.
I realize that this is shareware. However, I *did* pay the fee that the developer requested. I'd pay more, if i were confident that the quality and support would return to their previous levels.
Cannot get magic code to work - Version: 2.8.2, 6/10/2009 01:34AM PST
bettyann88
I am running v 2.8.2 (I cannot get a more recent version to install).
I am running Safari Version 4 (5530.17) (final version; not beta).
Currently Info.plist contains:
<key>SIMBLTargetApplications</key>
<array>
<dict>
<key>BundleIdentifier</key>
<string>com.apple.Safari</string>
<key>MaxBundleVersion</key>
<string>5525</string>
<key>MinBundleVersion</key>
<string>523</string>
</dict>
</array>
When I modify MaxBundleVersion to 5530.17, Safari quits when I create a new tab.
When I modify MaxBundleVersion to 5530 and MinBundleVersion to 17, again Safari quits when I create a new tab.
Any suggestions as to how I might get Pith Helmet to work with the most recent version of Safari? Thanks.
I am running Safari Version 4 (5530.17) (final version; not beta).
Currently Info.plist contains:
<key>SIMBLTargetApplications</key>
<array>
<dict>
<key>BundleIdentifier</key>
<string>com.apple.Safari</string>
<key>MaxBundleVersion</key>
<string>5525</string>
<key>MinBundleVersion</key>
<string>523</string>
</dict>
</array>
When I modify MaxBundleVersion to 5530.17, Safari quits when I create a new tab.
When I modify MaxBundleVersion to 5530 and MinBundleVersion to 17, again Safari quits when I create a new tab.
Any suggestions as to how I might get Pith Helmet to work with the most recent version of Safari? Thanks.
Most Recent Replies: View All 2 Replies
- Cannot get magic code to work (1 replies)
1. Open Safari and click on the "Safari" menu at the top of the screen. Select the option "About Safari"
2. A window will pop up that will have something like "Safari 4.0.1 (5530.18)" Note the number in parenthesis without the decimals (in this case 5530). This is the build number.
3. Quit Safari.
4. Go to "/Library/Application Support/SIMBL/Plugins/"
5. Right click on PithHelmet.bundle and choose "Show Package Contents"
6. Open the "Contents" folder that appears and open "Info.plist" in either TextEdit or Property List Editor
7. Look for the section called "MaxBundleVersion" which will be preceded by a number. If you have PithHelmet 2.8.4, it will say "5525"
8. Change this number to the build number you found earlier (e.g. 5530 if you're using Safari 4.0.1)
9. Save the file and relauch Safari. PithHelmet will now work just as it always has.
I can't guarantee that there won't be any problems that might result from this, but so far I have yet to experience any issues. If you do run into problems, uninstall PithHelmet and send an e-mail to the developer saying that you love his product and would really appreciate it if he supported it for Safari 4.