Here's a version of 2.5.7 which is compatible - I just bumped the version check. Apparently it works OK on El Capitan.
http://www.finderpop.com/Might-work-on-El-Capitan.zip
I'll get around to doing a proper release real soon now.
27 Sep 2014, 08:39
FinderPop 2.5.7 (tagged "Autumnal Equinox") is now available.
Note that FinderPop will not work properly on OS X 10.11 El Capitan
when System Integrity Protection (aka "Rootless") is enabled.*
It may be that having both FinderPop and SIP enabled will never be satisfactorily resolved because FinderPop relies on OS features which,
when SIP is enabled, have deliberately been removed by Apple with the aim of increasing system stability.
* And even with SIP disabled FinderPop v 2.5.7 won't work 100% as the El Capitan Finder does some stuff differently and I'm still trying to figure out what it's doing.
INSTALLATION:
Ensure you use Apple's unzipper to unzip the FinderPop zip file as some third-party unzippers do not respect permissions.
Ensure that the System Preferences panel is CLOSED. Quit. Not running. Double-click the FinderPop.prefpane icon. System Preferences will
open and ask if you want to install FinderPop for all users or just you. Choose "All Users" and continue.
On 10.6+, FinderPop "sees" what it was you clicked on in the Finder via the Services subsystem - ensure that you have Folder Actions Setup
enabled: System Preferences > Keyboard Shortcuts > Services > Files & Folders > (ensure Folder Actions Setup is checked.)
- 2.5.7 Allows FinderPop to work with alias files produced by the Yosemite 10.10 Finder.
- In FinderPop's Move/Copy/Alias dialog, you can control-click the Alias button and FinderPop will create symlinks instead of aliases.
- Fix minor bug in the Move To... and Copy To... scripts introduced last time (see the 'FinderPop Extras' folder.)
- Add new Alias To... and Symlink To... scripts to the 'FinderPop Extras' folder. These can be moved into your FinderPop Items folder if you wish.
These scripts will only be visible in FP menus if you have a Finder selection; they allow you to choose a destination folder into which to alias or symlink the selection. Added bonus: option-clicking the "Choose" button in the "Choose Folder" dialog will get the Finder to display the destination folder after the items have been aliased or symlinked. - Fix a buffer overrun bug which could cause a crash in rare instances.
The previous version of FinderPop is available here (2.5.6).
If you're installing this over a previous version of FinderPop, you'll have to restart or logout/login for it to take effect.
As usual, if there are any issues with this, reply here in the forum!
24 Oct 2014, 10:25
Hi,
www.finderpop.com seems currently inaccessible ?
> Server not found
> Firefox can't find the server at www.finderpop.com.
24 Oct 2014, 12:17
Cheers Alain - should be fixed now.
Apparently I am requied to validate every time the domain renews and dotster was sending these validation emails to an old email address... sorry about that!
27 Oct 2014, 17:27
I've got that damned thing again where having FinderPop switched on causes slowdowns. Specifically, with FinderPop on:
1. A slowdown in FinderPop's own system preference options. Each tab takes quite a few seconds to be selected. Turning the "off" radio button takes a long time - a few seconds - before it registers. But with FinderPop off, all actions/selections in the pane are super-quick, as with any other System Preference pane.
2. A slowdown when selecting (just selecting, not opening) apps in the applications folder. It used to be (when I experienced this before) that this slowdown affected all selections of apps in the applications folder. This time (running OS X 10.10 aka Yosemite) it's the first 2 app selections only that are slowed down (beachball for about five seconds before the Finder manages to select them). Yes, I know - bizarre. After that, the third selection of an app, and further selections of apps are at the normal speed, i.e., instantaneous.
I hate this! For a long while I used FinderPop in Mavericks and this --thing -- had gone away. Now it's come back, this time using Yosemite.
*sigh*
27 Oct 2014, 20:23
Deja Vu!
Can you get things set up in the Finder so that reproducing your problem will be easy. Then quit all apps other than the Finder. Then fire up Terminal.app, and enter the following command (you'll also need to enter your admin password.)
sudo fs_usage -w -f filesys
and then switch to the Finder and try to perform one of the tasks that FinderPop slows down (icon selection.)
Then switfch back to the Terminal window, press Control-C to kill the fs_usage command (there will be a lot of output), and mail me the contents of the terminal window - turly@finderpop.com.
This will tell me what files are being accessed and may give me a clue as to what might be happening on your system. Presumably you did an upgrade and not a clean install?
29 Oct 2014, 14:42
Turly - for some reason the problem has disappeared. I don't exactly know what intervening factor caused it to disappear. It might have been me relaunching the Finder. Anyway, if it happens again, I'll immediately follow your instructions and send you the results.
11 Nov 2014, 10:07
Out of the blue, a small window popped up, saying sth like: “ fp [sic!] didsomethingbla caused Finder to restart”. When I chose to show the log, not send to apple, it disappeared but no log was shown and no apparent harm. Console output under „FinderPop” comes pe e-mail, the hang must have been around or after 17 o'. Looking for something meaningful, I found ominous wodoo (no idea about programming but I like to read things). Like: invalid events for BetterTouchTool which I do not remember touching or KodakBonjourAgent (the Kodak printer I have is 1000 miles away from here. Or:
10.11.14 12:40:21 Preview[1320] Error loading /Library/ScriptingAdditions/QXPScriptingAdditions.osax/Contents/MacOS/QXPScriptingAdditions: dlopen(/Library/ScriptingAdditions/QXPScriptingAdditions.osax/Contents/MacOS/QXPScriptingAdditions, 262): no suitable image found. Did find:
/Library/ScriptingAdditions/QXPScriptingAdditions.osax/Contents/MacOS/QXPScriptingAdditions: mach-o, but wrong architecture
10.11.14 12:40:21 [0x0-0xc40c4].com.apple.Preview[1320] Preview: OpenScripting.framework - scripting addition "/Library/ScriptingAdditions/QXPScriptingAdditions.osax" declares no loadable handlers.
10.11.14 12:40:21 PopChar[315] exception in selectedFamily: *** -[NSCFArray objectAtIndex:]: index (-1 (or possibly larger)) beyond bounds (162)
10.11.14 12:40:21 PopChar[315] no members
10.11.14 12:40:21 PopChar[315] *** -[NSCFDictionary setObject:forKey:]: attempt to insert nil key
10.11.14 12:40:22 Preview[1320] _mthid_copyDeviceInfo(216172782187184128) failed
10.11.14 12:40:22 [0x0-0x23023].com.finderpop.fp-injector[318] FinderPop-beta-x86_64-25702: Patching 'Preview' 0:c40c4 (CF-c)
10.11.14 12:40:23 kernel Preview (map: 0xffffff802476eaa8) triggered DYLD shared region unnest for map: 0xffffff802476eaa8, region 0x7fff88000000->0x7fff88200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
11 Nov 2014, 11:52
Unfortunately the "fp didsomething caused Finder to restart" message isn't ringing any bells, shame you didn't take a screenshot or something -- it's definitely not one of mine!
There is no mention of either "crash" or "restart" in the Console.log you sent... did the Finder actually restart? All references to FinderPop in the log are normal and there is no mention of the Finder restarting (though the machine seems to have slept and woken up a couple of times.)
A quick Google shows that QXPScriptingAddtions.osax is related to Quark Express - you should probably get rid of that osax (in /Library/SciptingAdditions) as it doesn't seem to be valid for your architecture - I think it's PowerPC only and you're on Intel.
When FinderPop patches certain Apple apps, you'll get a "triggered DYLD shared region unnest for map". This is expected behaviour.
PopChar, BetterTouchTool and FireFox's numerous complaints are almost certainly not caused by FinderPop.
In short, no idea :-/
11 Nov 2014, 15:33
Thanks for replying. Should have put this in the Support area, sorry. Yes, the Finder did restart and the Desktop was „rearranged”. The small window mentioned „fp” and the word „inject” I believe, I was too fast. I'm mailing you the next part of the log, perhaps it was later. But what are all those apps complaining about all the time? Naughty code
21 Nov 2014, 20:06
I’ve had 10.10.1 installed for a couple of days now, and previous to that, the beta version for about a week. Today, all of a sudden, I experienced the screen going black but with the computer apparently still running. Anyway, I discovered that it was only happening with the user account that has FinderPop installed.
The console reports:
11/21/14 10:43:47.241 AM finderpop-daemon[1582]: AppleEvents/sandbox: Returning errAEPrivilegeError/-10004 and denying dispatch of event aevt/ansr from process 'Mail'/0x0-0x8b08b, pid=1515, because it is not entitled to send an AppleEvent to this process.
and it kept repeating again and again until I disabled FinderPop. I did notice lately that FinderPop would not immediately pop up when clicking on the blank space on the menu bar. I would have to click several times before it would come up.
Re-activating FinderPop produced this feedback in console:
11/21/14 11:01:06.084 AM finderpop-daemon[9413]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
11/21/14 11:01:06.084 AM finderpop-daemon[9413]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
11/21/14 11:01:06.819 AM Numbers[6208]: FinderPop: current app appears to be SandBoxed
Hope this helps you figure out what’s going on. I’m am running Yosemite 10.10.1 (14B25) on a MacPro3,1, 16 GB RAM. I will find life hard without FinderPop.
21 Nov 2014, 20:47
tonyaguila wrote:Anyway, I discovered that it was only happening with the user account that has FinderPop installed.
Not sure if this is the cause of the issue you report, but with recent OSX versions (since Mountain Lion?) FinderPop will only work properly when installed for all users.
Try:
Uninstall FinderPop (FinderPop prefs panel > Etc. tab > Uninstall FinderPop button)
Restart with FP uninstalled.
Install a fresh copy of FP For All Users.
22 Nov 2014, 02:58
With FinderPop installed for all users, including root, Console (from root user) still reports:
11/21/14 5:45:01.825 PM finderpop-daemon[17776]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.1 instead of 10.10.1. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
and
11/21/14 5:45:02.866 PM finderpop-daemon[17776]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
Hope this helps.
22 Nov 2014, 08:55
tonyaguila wrote:With FinderPop installed for all users, including root,
How did you do the installation? Not for each user separately, I hope.
At installation (by double clicking the prefs panel file) you choose the option to install "for all users".
FinderPop works fine in Yosemite for others. If you did the installation properly, we'll have to wait for Turly to shed light on this problem.
22 Nov 2014, 10:16
I am not sure what is going on in your system. I've never heard of FinderPop causing the screen to go black.
WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.1 instead of 10.10.1. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
FinderPop 2.5.7 does not call _Gestalt to get the OS version, so this is a surprise. Are you sure you're running 2.5.7? Do you have multiple versions installed for different users?
I think your best bet would be to uninstall FinderPop as RonaldPR suggested. (FinderPop prefs panel > Etc. tab > Uninstall FinderPop button.)
If you have installed FinderPop multiple times for different users, uninstall it for all such users too (this will mean logging in as that user and repeating the FinderPop prefs panel -> Etc. tab -> Uninstall FinderPop. The user's preferences and FinderPop Items folders should not be affected.)
Restart now with FinderPop completely uninstalled.
When you're back, make sure that System Preferences is not running - quit it if so.
Did I mention to quit System Preferences?
Double-click the FinderPop.prefPane icon from the latest version you downloaded.
When System Preferences opens it'll ask you whether FP should be installed for all users or just you. Choose "All users".
The messages from sandboxd about not having privileges to send AppleEvent replies is a red herring (and as far as I'm concerned, is a bug in sandboxd.)
The message about the missing semicolon in and old-style plist file also only appears on older versions of FinderPop (and is harmless.) As a matter of interest, are you using a localised (non-English) version of FinderPop?
30 May 2015, 21:44
I have been experiencing similar problem of "I experienced the screen going black but with the computer apparently still running" for a long time but never considered that it was related to FinderPop. I am using Mac OS X.6.8 (Snow Leopard). What I get is if the computer is idle for a long time, instead of going to sleep, screen just goes black, then sometimes it will not "wake up:" but you can tell the computer is still running. In that situationmy only option is to restart. Note that I rarely shutdown my computer. I can go 30-40 days and only let it sleep.
Using 27" iMac 2010 i7 2.93 GHz.
Any one else experience this?
31 May 2015, 10:49
Hmm, I can't think of anything I do in FP which could possibly cause sleep/wake problems - but you could simply disable FP for a week or two to see if the black screen problem recurs.
The Apple Discussions Boards have plenty of "screen black after sleep" threads if you want to see if any of the solutions work for you.
Hard to say really, but my money would be on one of your USB devices preventing sleep and/or wake. And you could reboot more often too
16 Jun 2015, 17:59
OSX 10.11 reports Finderpop is not compatible.. Really?!?!? Haha.. I know its a bit early, just a FYI..
- Attachments
-
- Screen Shot 2015-06-16 at 9.54.49 AM.png (239.16 KiB) Viewed 5120 times
- wgite
- Posts: 6
- Joined: 17 Jun 2012, 06:04
Re: FinderPop 2.5.7
by turly » 17 Jun 2015, 14:14
27 Jun 2015, 15:58
Sorry, but don't work with El Capitan 10.11
27 Jun 2015, 16:00
Apologise me. I have not see you last answer on El Capitan
10 Jul 2015, 09:59
Hi there,
I've upgraded to the Public Beta of El Cap a few hours ago - the might-work-FinderPop-version worked after the first boot, but doesn't want to run anymore after this first success. Any help/update is appreciated
10 Jul 2015, 12:32
Can you be a bit more specific? When you open the FinderPop prefpane, does everything look normal - nothing greyed out, no messages?
Was your install of the El Capitan public beta a clean install or an upgrade? What were you running before?
I would recommend this:
Uninstall FinderPop by following the instructions on the FP prefpane's "Etc." tab's "Uninstall FinderPop" button.
Your FinderPop Items folder will be left untouched if you do this.
Then re-install the "might-work on El Capitan" FinderPop -- for ALL users, remember!
I haven't gotten around to installing the public beta of El Capitan yet, after getting my fingers burned when I installed the 10.9 beta a while back. I'm waiting for at least public beta #2 this time
10 Jul 2015, 13:14
I just tried the uninstall/reinstall (using "might work" version. Unfortunately, it doesn't seem to work. I am using Beta 3 (same as the public beta).
10 Jul 2015, 13:23
Hmm, is it just that FP is not running or that my patching no longer works?
How are you on Terminal?
Fire up a Terminal session and run this:
killall finderpop-daemon
/Library/PreferencePanes/FinderPop.prefPane/Contents/Resources/finderpop-daemon.app/Contents/MacOS/finderpop-daemon
and either paste here or email me (turly@finderpop.com) the output.
Thanks!
10 Jul 2015, 17:19
turly wrote:Can you be a bit more specific? When you open the FinderPop prefpane, does everything look normal - nothing greyed out, no messages?
Was your install of the El Capitan public beta a clean install or an upgrade? What were you running before?
Of course I can (Sorry
) - PrefPane reacts normally, finderpop-daemon kicks in as usual, but there's nothing to see in the context menu anymore.I have directly upgraded from 10.10.4 (FinderPop working great before). Before upgrading, I've switched to the might-work-version
Terminal output:
- Code:
================================================================================
================================================================================
FinderPop-beta-x86_64-25702: Patching 'Finder' 0:c00c (Immed-e)
(Still nothing in the contextual menus)
On second thought I'm afraid this might have something to do with the new rootless system (system integrity protection) of the OS - afaik this should keep tools from hooking into system processes alongside securing the System folder (I've read that somewhere...). At least that's why the guys from TotalFinder, XtraFinder etc. are having a tough time now with 10.11
10 Jul 2015, 18:37
Just reading up on rootless now. I think this could be... challenging.
http://www.quora.com/Can-someone-elabor ... d-Rootless
The Rootless feature makes certain operations only permissible for Apple code (as determined by code signature), so that 3rd party code, even if it’s running under the root account, can’t do certain things. In my tests I noted several changes:
1. Anything under /System (and several other folders) can no longer be modified by anyone other than Apple components (such as various installer and updater components)
2.Certain APIs such as the good old task_for_pid are no longer supported if they’re called on system processes. This means that programs that “inject” themselves into system processes such as the Finder, Messages, or the kernel will no longer work.
Hmm.
By way of a workaround, can System Integrity be disabled?
10 Jul 2015, 18:53
turly wrote:By way of a workaround, can System Integrity be disabled?
Yup -
- Code:
sudo nvram boot-args="rootless=0"
or booting into Recovery Mode and disabling it from the menu bar (new option - at least now in the developer versions...)
//Edit:
I've just disabled it: It works now, but kills the contextual menu options...
- Attachments
-
- Bildschirmfoto 2015-07-10 um 20.24.08.png (32.98 KiB) Viewed 7933 times
-
- Bildschirmfoto 2015-07-10 um 20.24.03.png (48.7 KiB) Viewed 7933 times
- Larsen2k4
- Posts: 6
- Joined: 26 Jul 2012, 11:00
Re: FinderPop 2.5.7
by turly » 10 Jul 2015, 20:48
Well, that's a bit of a bugger. I'll have to get the finger out and install it... but I'm up the walls with real work atm.
Reading more about rootless, Apple may well remove that NVRAM hack which would be bad news I think, though someone on tweakbsd.org reckons a kext might be able to work around it, but that's just playing whack-a-mole .
Reading more about rootless, Apple may well remove that NVRAM hack which would be bad news I think, though someone on tweakbsd.org reckons a kext might be able to work around it, but that's just playing whack-a-mole .
11 Jul 2015, 05:13
Yup, I guess this will be a dead end for many tools and helpers, since there is no guarantee that these switches will still exist in final releases or future versions of OS X. The dev from TotalFinder also made a good point that on the other hand it's no good way to tell all novice users to disable their protection just for the little helper.
25 Jul 2015, 19:27
turly wrote:Well, that's a bit of a bugger. I'll have to get the finger out and install it... but I'm up the walls with real work atm.
Reading more about rootless, Apple may well remove that NVRAM hack which would be bad news I think, though someone on tweakbsd.org reckons a kext might be able to work around it, but that's just playing whack-a-mole .
Based on WWDC videos and other information, Apple will remove the NVRAM hack before final release, but it will still be possible to disable Rootless from Recovery mode for the foreseeable future.
06 Aug 2015, 06:56
Can someone conform the FP does not work with El Capitan Public Beta 4, or am I doing something wrong.
Dave
06 Aug 2015, 10:22
As the previous page of posts testifies, FinderPop doesn't work with the new "rootless" security feature of El Capitan.
Even when you disable rootless, FP still doesn't work properly with the new Finder, I need to install it and grovel around in the new Finder to see how it is handling contextual menus.
Unfortunately I have been up the walls with "real" work for the last couple of months and this will continue for the next few months too.
I should have a spare weekend sometime to install it and play with it and hopefully fix the contextual menus in the new Finder, but given that it will need "rootless" turned off in order to work at all, I can't see many people willing to do that. Unless another workaround is discovered, of course, but my feeling is that Apple will play whack-a-mole and kill such workarounds.
18 Oct 2015, 10:07
Hello, will be a Version for El Capitane... (maybe with workaround to disable SIP temporary...?)
please give us a feedback...
thanks... Rene
19 Oct 2015, 15:38
Unfortunately, SIP would need to be disabled all the time while using FinderPop.
26 Oct 2015, 12:52
I loved finderpop and used it all the time. I'm really sorry to see that it is disabled under the new MAC OS and that there is no remedy.
28 Oct 2015, 13:10
Because of El Capitan, Finderpop is disabled and access to the folder of Finderpop items is denied. Is there anyway I can get to that folder since I have some original items in it?
28 Oct 2015, 23:00
Spotlight will find it ... IIRC the FinderPop Items folder is in your home directory's Library folder.
09 Nov 2015, 14:56
wmgmartin wrote:Because of El Capitan, Finderpop is disabled and access to the folder of Finderpop items is denied. Is there anyway I can get to that folder since I have some original items in it?
Easiest way: Open System Preferences/FinderPop. Select "Items" tab. Select "Show 'FinderPop items' folder..." Now you can add/remove to your hearts content.
At the top of that Finder window, you should see a blue folder with "FinderPop Items" next to it. Grab the folder and put it in your Finder sidebar. It will always be available henceforth.
What indication are you seeing that denies you access to that folder? Is it because you are running in a standard User account rather than an Administrative account? Does the folder have a little red badge on it? If the latter, "Get Info" on the folder. At the bottom of the new window, click the lock and unlock it with the Admin password. Then select the gear and add yourself and Read & write to the permissions section. Now you have access and can add/rem one as desired.