You’ll get a standard Open dialog box navigate to that folder on your desktop where you put your extension files and choose the folder with the extension name it’ll have the extension.
Older versions of safari plus#
Click Continue.Īt the bottom of the Extension Builder window click the Plus (+) button and choose Add Extension. The first time you open the Extension Builder, you’ll be asked whether you really want to use it instead of Xcode: you do. There should now be a Develop menu between the Bookmarks and Window menus from it, select Show Extension Builder. If you don’t already have the Develop menu in the menu bar, go to Safari > Preferences, click on the Advanced tab, and check the “Show Develop menu in menu bar” option. You’ll now have a folder of source files for each extension. (Tip: If you type the first few characters and hit the Tab key, it’ll autocomplete the rest.) Repeat for each extension file. Type xar -xf followed by a space and the name of the extension file, and hit enter. The next part of this requires a little command-line trickery, so fire up Terminal, navigate to that directory you just created on the desktop (or just type cd followed by a space in the Terminal window and drag the folder you just made on your desktop into the Terminal window). Drag any extensions you want to save from here onto your desktop I recommend putting them into a folder. Fortunately, Safari 12 doesn’t remove the extension files for deprecated or inactive extensions. TerminalĮxtensions are stored in ~/Library/Safari/Extensions.
Older versions of safari how to#
Those warnings out of the way, here’s how to actually run those old extensions on your Mac.
Older versions of safari update#
One downside to this approach, based on my testing with the Mojave public beta, is that every system update re-enforced the new rules, meaning that you might potentially have to perform this procedure again in the future. It’s unclear when this might happen-you may get a couple years out of them yet, and perhaps by the time they do, sanctioned alternatives will become available. Sooner or later, this trick will probably stop working, and/or older extensions will no longer function correctly with new versions of Safari. If you’re going to use this feature, I’d recommend limiting it to older extensions that you already trust, not necessarily as a way to bypass security restrictions for new extensions.
Give new life to old extensions in Safari 12Īmong yesterday’s barrage of updates was a seemingly minor one: Safari 12.
0 kommentar(er)
