DokuWiki

Just trying this which looks very promising I a) Installed the plugin b) Created a page http://localhost:8800/doku.php?id=epub:mybook c) Put the following in that page [[car:disk_electronic|Test]] d) saved page and pressed button That yields ... [More] only this error (on the page) processed: car:disk_electronic Using LESS: css3.php A fatal error occured during compilation of the CSS files. If you recently installed a new plugin or template it might be broken and you should try disabling it again. [variable @ini_link is undefined: failed at `color: @ini_link;`  in /lib/plugins/move/style.less at line 73] It seems independent of which page I choose. I am using the bootstrap3 template if that makes a difference. An epub is created at X:\Sync\DokuWikiStick\dokuwiki\data\meta\epub\aubreyb\17b671eb881c2ccf766534afb7730576\my-book.epub but this is not openable (by Sigl for example) It may have something to do with https://github.com/michitux/dokuwiki-plugin-move/issues/122 and https://github.com/splitbrain/dokuwiki/issues/1792 -- but I'm not sure why epub would be invoking the move plugin anyway which is mnot listed as a dependency?? Not at all sure where to go from here. Help much appreciated. as an aside can I ask why the epub output discussed in the plugin page as an example http://www.mturner.org/fckgLite/doku.php?id=ebook is not openable in Microsoft Edge. In Sigl it does open but with an error. Obviously Edge is not  gold standard epub reader, but it is likely to become the route to opening for many people especially when on the web. [Less]

Just trying this which looks very promising I a) Installed the plugin b) Created a page http://localhost:8800/doku.php?id=epub:mybook c) Put the following in that page [[car:disk_electronic|Test]] d) saved page and pressed button That yields ... [More] only this error (on the page) processed: car:disk_electronic Using LESS: css3.php A fatal error occured during compilation of the CSS files. If you recently installed a new plugin or template it might be broken and you should try disabling it again. [variable @ini_link is undefined: failed at `color: @ini_link;`  in /lib/plugins/move/style.less at line 73] It seems independent of which page I choose. I am using the bootstrap3 template if that makes a difference. An epub is created at X:\Sync\DokuWikiStick\dokuwiki\data\meta\epub\aubreyb\17b671eb881c2ccf766534afb7730576\my-book.epub but this is not openable (by Sigl for example) It may have something to do with https://github.com/michitux/dokuwiki-plugin-move/issues/122 and https://github.com/splitbrain/dokuwiki/issues/1792 -- but I'm not sure why epub would be invoking the move plugin anyway which is mnot listed as a dependency?? Not at all sure where to go from here. Help much appreciated. as an aside can I ask why the epub output discussed in the plugin page as an example http://www.mturner.org/fckgLite/doku.php?id=ebook is not openable in Microsoft Edge. In Sigl it does open but with an error. Obviously Edge is not  gold standard epub reader, but it is likely to become the route to opening for many people especially when on the web. [Less]

Just trying this which looks very promising I a) Installed the plugin b) Created a page http://localhost:8800/doku.php?id=epub:mybook c) Put the following in that page [[car:disk_electronic|Test]] d) saved page and pressed button That yields ... [More] only this error (on the page) processed: car:disk_electronic Using LESS: css3.php A fatal error occured during compilation of the CSS files. If you recently installed a new plugin or template it might be broken and you should try disabling it again. [variable @ini_link is undefined: failed at `color: @ini_link;`  in /lib/plugins/move/style.less at line 73] It seems independent of which page I choose. I am using the bootstrap3 template if that makes a difference. An epub is created at X:\Sync\DokuWikiStick\dokuwiki\data\meta\epub\aubreyb\17b671eb881c2ccf766534afb7730576\my-book.epub but this is not openable (by Sigl for example) It may have something to do with https://github.com/michitux/dokuwiki-plugin-move/issues/122 and https://github.com/splitbrain/dokuwiki/issues/1792 -- but I'm not sure why epub would be invoking the move plugin anyway which is mnot listed as a dependency?? Not at all sure where to go from here. Help much appreciated. as an aside can I ask why the epub output discussed in the plugin page as an example http://www.mturner.org/fckgLite/doku.php?id=ebook is not openable in Microsoft Edge. In Sigl it does open but with an error. Obviously Edge is not  gold standard epub reader, but it is likely to become the route to opening for many people especially when on the web. [Less]

Just trying this which looks very promising I a) Installed the plugin b) Created a page http://localhost:8800/doku.php?id=epub:mybook c) Put the following in that page [[car:disk_electronic|Test]] d) saved page and pressed button That yields ... [More] only this error (on the page) processed: car:disk_electronic Using LESS: css3.php A fatal error occured during compilation of the CSS files. If you recently installed a new plugin or template it might be broken and you should try disabling it again. [variable @ini_link is undefined: failed at `color: @ini_link;`  in /lib/plugins/move/style.less at line 73] It seems independent of which page I choose. I am using the bootstrap3 template if that makes a difference. An epub is created at X:\Sync\DokuWikiStick\dokuwiki\data\meta\epub\aubreyb\17b671eb881c2ccf766534afb7730576\my-book.epub but this is not openable (by Sigl for example) It may have something to do with https://github.com/michitux/dokuwiki-plugin-move/issues/122 and https://github.com/splitbrain/dokuwiki/issues/1792 -- but I'm not sure why epub would be invoking the move plugin anyway which is mnot listed as a dependency?? Not at all sure where to go from here. Help much appreciated. as an aside can I ask why the epub output discussed in the plugin page as an example http://www.mturner.org/fckgLite/doku.php?id=ebook is not openable in Microsoft Edge. In Sigl it does open but with an error. Obviously Edge is not  gold standard epub reader, but it is likely to become the route to opening for many people especially when on the web. [Less]

I've played with this idea before.  Is there any way to launch an appropriate program to deal with other format documents?  For instance it would be nice to launch Libre Office to handle .odts or the document viewer for .pdfs.  The sort of system I ... [More] was aiming for would use DW to handle document metadata and then hand off the document processing to a word processor, editor or similar.  Actual documents could be kept in either a hidden namespace or else in a separate directory.  I realise that there are issues with file ownership, specifically they would all end up as apache:apache, but then DW's inbuilt ACLs can handle this problem. [Less]

I've played with this idea before.  Is there any way to launch an appropriate program to deal with other format documents?  For instance it would be nice to launch Libre Office to handle .odts or the document viewer for .pdfs.  The sort of system I ... [More] was aiming for would use DW to handle document metadata and then hand off the document processing to a word processor, editor or similar.  Actual documents could be kept in either a hidden namespace or else in a separate directory.  I realise that there are issues with file ownership, specifically they would all end up as apache:apache, but then DW's inbuilt ACLs can handle this problem. [Less]

I've played with this idea before.  Is there any way to launch an appropriate program to deal with other format documents?  For instance it would be nice to launch Libre Office to handle .odts or the document viewer for .pdfs.  The sort of system I ... [More] was aiming for would use DW to handle document metadata and then hand off the document processing to a word processor, editor or similar.  Actual documents could be kept in either a hidden namespace or else in a separate directory.  I realise that there are issues with file ownership, specifically they would all end up as apache:apache, but then DW's inbuilt ACLs can handle this problem. [Less]

I've played with this idea before.  Is there any way to launch an appropriate program to deal with other format documents?  For instance it would be nice to launch Libre Office to handle .odts or the document viewer for .pdfs.  The sort of system I ... [More] was aiming for would use DW to handle document metadata and then hand off the document processing to a word processor, editor or similar.  Actual documents could be kept in either a hidden namespace or else in a separate directory.  I realise that there are issues with file ownership, specifically they would all end up as apache:apache, but then DW's inbuilt ACLs can handle this problem. [Less]

Quote by pop:What, exactly, do you want to do with those Word documents in the wiki, and what do you mean by "managing" them in a Wiki environment? One would hope they plan to convert them into wiki pages...

Quote by pop:What, exactly, do you want to do with those Word documents in the wiki, and what do you mean by "managing" them in a Wiki environment? One would hope they plan to convert them into wiki pages...