![]() ![]() ![]() Please let me know if I'm missing something here. Once you do that, you can select Wiki from the tab. Even though it can lead to an empty project wiki (if it even actually allows deleting a last wiki page, which I am not sure about currently), the project wiki itself remains available thus editable with the appropriate permissions. Adding a Wiki Tab Similar to adding the YouTube app, you can create a Wiki Tab with the Add a Tab button in your channel. This does not look like an issue when wiki pages are deleted. Pundri kaithal news, Aeronave hercules, Prospan syrup wiki, Mitch grassi fan art. This actually makes no sense and is fixed by the patch in #34643 by disabling the wiki module for the project after deleting its wiki. To start a new wiki afterwards, you'll need to disable the projects' wiki module first, to re-enable it successively to let Redmine create a new empty project wiki and set it a new start page. In that case all pages are deleted, thus no page set as start page remains, and the wiki itself is deleted. The problem seems to arise only with the deletion of the wiki as a whole. the wiki as a whole (via the contextual 'delete' links on the wiki index pages after #26579, :manage_wiki permission needed).ĭeletion of wiki page versions is not an issue here.wiki pages (via the contextual 'delete' drop-down button on the wiki page show view, :delete_wiki_pages permission needed) and.wiki page versions (via the wiki page 'history' view, :delete_wiki_pages permission needed).In the end this would be a great help for both ends, saving countless hours support and makes you looking good, being so supportive to your customers.Just to provide some information: there are three things that can be deleted within the wiki module: And of course - now that I´ve revealed this marketing strategy to you, we should talk about my share. If you would advertise vaultwiki with that kind of import-option every user is capable of, I am convinced your addon would sell much more often. Unlike the XML import I did, where the structure is incomplete and "pages" and all images are missing in the backup and the import into vaultwiki has to fail about that. From there the import from the (own) mediawiki to vaultwiki should be a breeze. Rearding the wiki backup-tool this would be the part where you step in: you´ld only need to write a step-by-step documentation how the customer has to mount Python and how to mount the wiki-tool into Python (that´s the part where I am stuck), add a preconfigured config for the wiki-tool where the customer only needs to change the API-Url of the wiki he wants to import and the directory where the backup shall be stored on his harddrive.Īfter he has finished the backup he uploads the backup file to his server, goes into his mediawiki copy, imports the backup and has all data at once, including images, revisions etc. The installation itself is done via an installer and just needs a few clicks to be done with it. After that he goes to the Python website and downloads the Python3 software package (available for free) on their website and installs that on his local PC/MAC. The customer prepares 2 things on his server: he installs vault wiki and an empty mediawiki on his server. So, why don´t ease this all up for the enduser? ![]() That only would lead to more problems as people a) don´t like to let anyone into their shell for obvious reasons, b) they are on a vhost and don´t have access to the shell console and c) they are not familiar with setting up python on their servers via shell commands. But that doesn´t necessarily means that you have to run it on your internet server. The backup tool from Wikiteam has to be run under python3. What I am suggesting is to include a flawless import-tool into your package (or at least the basic configuration and the customers have to download the main software from the official website) and boost their capabilities for importing parts of a wiki or entire wikis to their vaultwiki. On the other hand you are one person and you couldn´t keep up with all those help requests (if they would get in touch with you instead of discarding vaultwiki). What I am suggesting is to close a gap for most potential users, as they are not familiar with wiki-imports and - like me - just give up at this point. I wasn´t referring to a single use - but I was a little unspecific. ![]()
0 Comments
Leave a Reply. |