-
All replies
-
Helpful answers
-
Dec 1, 2015 9:19 AM in response to léonieby Ralf Chmielus,I will try this as a last resort, because under 10.11.1 the difference was the same for the first time, so I thought this will be sorted out in the beta process and I already send this to Apple with no answer or change through the different builds. So I think 11.2 is not to far away, I will wait until the final version will be released.
thanks
-
-
Dec 1, 2015 9:25 AM in response to MACaineerby HelgeKreutz,My photos version is 1.2 (340.4.0) and in photos I only use the extensions tonality, noiseless and snapheal. All other apps from the kit did not plug-in.
-
-
Dec 1, 2015 9:32 AM in response to HelgeKreutzby Ralf Chmielus,Hello Helge,
photos wasn't indeed in the selections list, but I thought this was due to another concept of extensions working. I' m too still working with Aperture and yes I downloaded new versions today for Snapheal and it needed my admin password to install new versions of extensions,but nothing changed. And still I own non-Macphun-Software with extensions and they won't show up either. No, normally I would check and repair file permissions, but this shouldn't be necessary in El Capitan.
Does anybody know, where the extensions should be installed, then I could compare permissions of the directories and files on my perfectly running iMac with my MacBook Pro?
ciao Ralf
-
Dec 1, 2015 9:41 AM in response to MACaineerby Ralf Chmielus,The latest beta ist Photos version 1.3 (350.23.0) and I also don't know any lens correction extension for photos so far
-
Dec 1, 2015 9:57 AM in response to Ralf Chmielusby HelgeKreutz,Mine is installed in applications -> creative kit 2016.
Tonality was previously installed as single app under documents -> presets and textures, which is unusual but has also worked.
-
Dec 1, 2015 10:16 AM in response to HelgeKreutzby Ralf Chmielus,Hello Helge,
no sorry, you misunderstood me, the installation of the apps are obvious, I'm searching where these apps are installing the extensions, so they should appear in photos, there must at least be a directory, where the active installed extensions or their aliases are listed.
-
Dec 1, 2015 10:23 AM in response to Ralf Chmielusby léonie,I will try this as a last resort, because under 10.11.1 the difference was the same for the first time, so I thought this will be sorted out in the beta process and I already send this to Apple with no answer or change through the different builds.
By reinstalling I did not men to downgrade to the current stable version. The extensions are working for me on the Macs that are running the same Beta as you are running.
I recommended reinstalling a full Version of MacOS X to ensure, you have a consistent installation.Updates do not install all basic frameworks new, not even Combo updates. Booting into recovery and reinstalling will ensure a consistent System.
-
Dec 13, 2015 6:26 AM in response to léonieby Ralf Chmielus,Hello Leonie,
yesterday I got the time to reinstall, as you pointed out and thank you a lot, this did the trick. Now everything is back to normal on my MacBook Pro too and should be the first try for all here who got the same problem and the terminal command of Apple support isn't working!!
-
Dec 13, 2015 7:15 AM in response to Ralf Chmielusby léonie,That is great Ralf! Thanks for letting us know.
