Feature #1040
openGlobal wiki
Added by Carl Nygard over 16 years ago. Updated over 3 years ago.
0%
Description
It would be very helpful to have a global wiki for generalized instructions. The main home page should be the global wiki. The current functionality of news, recent projects, etc. could possibly be implemented with macros() in the wiki, so could be available globally. You could extend this paradigm (idiom, design, convention?) to all the project-specific main pages, and give the managers of each some ability to customize their own main page.
This would be extremely useful in our own situation, where we are using Redmine to manage diverse projects across our engineering group, so we have some need of a "global" wiki area for generalized policy docs, user guides, procedures, etc.
Files
draft-feature-1040.patch (24.1 KB) draft-feature-1040.patch | Mizuki ISHIKAWA, 2020-07-30 09:05 | ||
draft-feature-1040-r20825.patch (23.8 KB) draft-feature-1040-r20825.patch | Mizuki ISHIKAWA, 2021-03-19 02:31 |
Related issues
Updated by Maxim Krušina over 16 years ago
+1 For now, we're using wiki of one project as global wiki, and I added link to whis Wiki to main top menu, with text "Wiki", but it's just a workaround hack ;)
Updated by Lane Roathe over 16 years ago
+1 as I'm having to create some temporary hacks in order to present company wide information, like programming guidelines, vacation policies, etc. on the Home page. It would be great to have the ability for any module to be "site wide", including ability for existing permission settings, etc. these modules have.
Updated by Toni Kerschbaum almost 16 years ago
+1
Would be great. That way, info that is meant to be company-wide could be published easily, without a need for workarounds.
Updated by Denys Rogovchenko over 15 years ago
+1000 it would be really great, because a lot of companies hasbig amount projects which are similary... and it so stupid idea to have a lot of independent wiki... Also it good idea to have global file storage, global documents and global forum. I created for that separate project, but it not so good idea because it's not pure project, and it hard to find for people within big amount of real projects in project list... So please make this functionality, users really need it.
Updated by Maxim Krušina over 15 years ago
+1.3 :)
we're still using menu hack which point's to one project's wiki... no nice solution
Updated by Maxim Krušina over 15 years ago
- Status changed from New to Closed
this is duplicate to #1040
Updated by Maxim Krušina over 15 years ago
- Status changed from Closed to Reopened
ssry, I din't know that linked issue will close both original and duplicate ;(
Updated by Jean-Philippe Lang over 15 years ago
Maxim: closing the duplicate won't close the original. But closing the original will close the duplicate.
Updated by Mischa The Evil over 15 years ago
Maxim Krušina wrote:
ssry, I din't know that linked issue will close both original and duplicate ;(
/me ranting out loud while being a bit corny {
He should know better... He should have been known to the automatic-duplicate-closure behaviour of Redmine since it was explained in-depth by J-PL in this forum-thread started by .... Himself...
}
:-)
Updated by Maxim Krušina over 15 years ago
JPL> Ach so, thnx! ;)
Mischa> There should be no "He should know better" in good app, all must be self-explaining. I just read again forum you sugested, but I think it should be much moe clear how the mechanismus work. All we are heavy Redmine users and even it's a bit confusing now, so some fine-tuning will help!
I bet there will be lot of other users a bit frustrated about this.
In other words: functionality is just OK, but it should be somehow better communicated and self-explaning...
Updated by Kirill Ponomarev over 15 years ago
+1 It would be very helpful for me too.
Updated by Paul Rivier over 15 years ago
I would implement this using the newly available unlimited project nesting, and thinking this global wiki as being "the wiki of the root project". Then we can discuss common trees behaviour like inheritance and accumulation. For example, "wiki inheritance" would allow a child project to reference a wikipage of a parent project using only the name of the page, i.e without mentioning the project name. Dynamic resolution would look parents project until it finds the page. I guess this is pretty much what you want for a global wiki
Updated by Kirill Ponomarev over 15 years ago
Paul Rivier wrote:
I would implement this using the newly available unlimited project nesting, ...
It is a good idea!
Updated by Ryan Rangel about 14 years ago
Without this feature we will need to setup a completely seperate Wiki to hold general company information.
+1
Updated by Attila Antal over 13 years ago
+1 Good idea! The text could be 'Global Wiki'.
Updated by Florian Breitwieser over 13 years ago
+ 1. We have several projects which all should have a common Wiki.
Updated by K. Scott Tripp almost 13 years ago
+1. But as Feature #6027 mentions a global forum is just as important.
Updated by Frode Nilsen almost 13 years ago
+1
We currently use a "General" project, but global wiki/news/forum would be more elegant.
Updated by Dipan Mehta over 11 years ago
+1. This is VERY VERY important. Please have it.
Updated by Toshi MARUYAMA almost 7 years ago
- Related to deleted (Feature #13722: setup wiki page with default page)
Updated by Toshi MARUYAMA almost 7 years ago
- Related to Feature #26554: Select Wiki Page as Project Start Page added
Updated by Michael Gerz over 6 years ago
+1 (is anyone actually counting them?)
Updated by Mizuki ISHIKAWA about 4 years ago
- File draft-feature-1040.patch draft-feature-1040.patch added
I've attached a patch that adds a global wiki.
The test is a draft version not yet written.
Any feedback is welcome.
I would be particularly pleased if you could review if you have the proper permissions to view the global wiki.
Updated by Timo Schüring over 3 years ago
Hi Mizuki, thank you very much for your effort,
I will try it the next weeks but I have to understand the patch first,
which will take a bit cause I am new to Redmine.
Updated by Mizuki ISHIKAWA over 3 years ago
Timo Schüring wrote:
Hi Mizuki, thank you very much for your effort,
I will try it the next weeks but I have to understand the patch first,
which will take a bit cause I am new to Redmine.
Thank you.
Conflict occurred when patching the latest Redmine trunk (r20825).
I will attach the fixed patch.
These patches are developed to be applied to Redmine under development (trunk, r20825) , so it may not be applicable to released Redmine such as Redmine 4.1.
Updated by Mizuki ISHIKAWA over 3 years ago
Updated by Timo Schüring over 3 years ago
Thank you again, Mizuki-san,
we use Redmine so far on our Synology NAS with an old version based on
a Docker package. So I guess I have to adapt the patch anyway.
And/Or I have to learn how to get the development patch running.
Environment:
Redmine version 3.3.10.stable
Ruby version 2.3.8-p459 (2018-10-18) [x86_64-linux-gnu]
Rails version 4.2.11.1
Environment production
Database adapter Mysql2
Updated by keineahnung 2345 over 3 years ago
Thank you, Mizuki-san,
I managed to do some trivial changes to make it compilable on Redmine 4.1.1 and 4.1.2: https://gist.github.com/keineahnung2345/4f5eee59079128645cad8aa88016fa77/140e02176ad78bf45ab67dbb8de14c0487cf878f.
But later I found that there are permission problems or redirection path problems on some buttons(new button not showing, internal server error after editing, internal server error after deleting, rename button not working). So I made some changes to make them work as expected: https://gist.github.com/keineahnung2345/4f5eee59079128645cad8aa88016fa77/240d94bce8017f3e52cfce6f9101f39685c91888.
Could you please check the revised code and check if those problems also happen on truck r20825? Thanks.
Updated patch for redmine 5.0.5: https://gist.github.com/keineahnung2345/5431ffbde8f62698533c3ad5d9ffb840