plugin:plugin
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
plugin:plugin [2015-03-04 13:03] – 203.244.212.26 | plugin:plugin [2023-02-28 21:26] (current) – Aleksandr | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Plugin Manager plugin ====== | ||
+ | ---- plugin ----- | ||
+ | description: | ||
+ | author | ||
+ | email : chris@jalakai.co.uk | ||
+ | type : admin | ||
+ | lastupdate : 2013-12-07 | ||
+ | compatible : (bundled up to version Binky) | ||
+ | depends | ||
+ | conflicts | ||
+ | similar | ||
+ | tags : configuration, | ||
+ | screenshot_img : : | ||
+ | ---- | ||
+ | |||
+ | ===== Important Notice ===== | ||
+ | |||
+ | The Plugin Manager plugin was bundled with Dokuwiki up to version Binky (2013-12-08). | ||
+ | |||
+ | :!: Since version Ponder Stibbons (2014-05-05) the Plugin Manager is superseded by the [[plugin: | ||
+ | |||
+ | ===== Description ===== | ||
The Plugin Manager plugin allows [[config: | The Plugin Manager plugin allows [[config: | ||
Line 73: | Line 95: | ||
- | All the download-links to github are automatically redirected to ssl-connections, | + | All the download-links to github are automatically redirected to ssl-connections, |
Problem is, as of now SSL transports are disabled on XAMPP and UniServer (WAMPs) and all cheap webhosters I tried so far (even those very few, that allow sockets at all). | Problem is, as of now SSL transports are disabled on XAMPP and UniServer (WAMPs) and all cheap webhosters I tried so far (even those very few, that allow sockets at all). | ||
Line 90: | Line 112: | ||
--- [[user> | --- [[user> | ||
- | > This is a known problem, see http:// | + | > This is a known problem, see https:// |
>> Thanks, Anika. Strange discussion there... it almost seems, they don't get the point. Claiming security at github against plain http as an //option// for package downloads sound ridiculous to me. I was wondering -- maybe some kind of proxy in-the-middle thing might work, but I'm not sure, if it's worth the effort. | >> Thanks, Anika. Strange discussion there... it almost seems, they don't get the point. Claiming security at github against plain http as an //option// for package downloads sound ridiculous to me. I was wondering -- maybe some kind of proxy in-the-middle thing might work, but I'm not sure, if it's worth the effort. | ||
Report and possibly workaround: [[bug> | Report and possibly workaround: [[bug> | ||
+ | |||
+ | ---- | ||
+ | |||
+ | A solution that often works when your shared webhosting doesn' | ||
+ | |||
---- | ---- | ||
====/ | ====/ | ||
:!: One for those that may follow the red herring that incorrectly points to this issue: | :!: One for those that may follow the red herring that incorrectly points to this issue: | ||
- | Ubuntu 12.04 Precise fully patched, all the extensions needed were installed. Running on a VPS, Dokuwiki the Splitbain | + | Ubuntu 12.04 Precise fully patched, all the extensions needed were installed. Running on a VPS, Dokuwiki the Splitbrain |
Update via the plugin manager fails. | Update via the plugin manager fails. | ||
- | | + | |
Issue was eventually diagnosed as a / | Issue was eventually diagnosed as a / | ||
- | |||
plugin/plugin.1425470634.txt.gz · Last modified: 2015-03-04 13:03 by 203.244.212.26