Profile Picture

How to keep several distinct WikiPlus sites in the same web app

Posted By Josh Korn 8 Years Ago
You don't have permission to rate!

How to keep several distinct WikiPlus sites in the same web app

Author
Message
Josh Korn
Posted 8 Years Ago
View Quick Profile
Forum Guru

Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)

Group: Forum Members
Last Active: 7 Years Ago
Posts: 37, Visits: 76
I need to know precisely what to do in order to keep several WikiPlus sites under the same web app. If that's not possible, I need to know that ASAP in order to plan sites, web apps, etc. now.

The key rule of thumb is that no two sites will have the same customizations (i.e. each will have a different look and feel, different terminology, different page editor, etc).

From what I can tell at the moment, it's not clear how I could maintain two WikiPlus sites in the same web app if each requires different terminology customization (since it looks like there's only one wikiplus.resx on the web app).

More info will make this issue clearer.

Thanks in advance

Josh

Josh Korn

Kevin
Posted 8 Years Ago
View Quick Profile
Forum Member

Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)

Group: Moderators
Last Active: 6 Years Ago
Posts: 35, Visits: 67
WikiPlus is built on on master pages and CSS files that allow you to easily customize just like out-of-the-box SharePoint sites. Each WikiPlus site can be branded with its own master page and css files, just like SharePoint. In fact, the default WikiPlus site has a master page that can be used as a starting point for your custom site.

The resx files in all of SharePoint are only intended to be used for translation, and are scoped per farm. This isn't a WikiPlus limitation, but a SharePoint one shared by all SharePoint sites.

The editor for each WikiPlus site can be different. By default, the editor for all wiki site/libraries uses the toolsfile.xml and configfile.xml located at

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\KWizCom_Wikiplus\RadControls\Editor

WikiPlus is designed to check if there are customized versions of these files at the site/web level. WikiPlus first checks to ensure the default toolsfile.xml and configfile.xml exist. These two files are used as a fallback if custom versions do not exist. WikiPlus then checks for a web (site) specific toolsfile.xml and configfile.xml by looking for a files named toolsfile.{GUID of WEB}.xml and configfile.{GUID of WEB}.xml. If these files don't exist then WikiPlus checks to see if there is a site collection specific toolsfile.xml and configfile.xml by looking for files name toolsfile{GUID of SITE}.xml and configfile{GUID of SITE}.xml. One thing to take into consideration here is that you can have a custom toolsfile.xml for your sub web(sub site), but use the same configfile.xml for your entire site collection. Or use the same toolsfile.xml across your site collection but use a different configfile.xml for each sub web (sub site). The WikiPlus editor uses the following priority to determine which files are used:

  1. Web specific xml file (Sub Site specific)
  2. Site collection specific xml file
  3. Default xml file
Here is are examples to better illustrate. Let's say I have 3 sub webs (sub sites) with the following GUIDS

HR Site: {428AE37A-63D0-4d45-9681-8FC4DD9E7435}

IT Site: {ABFD5E80-02DD-4f2c-94AF-813D4C952307}

Finances Site: {07D85DBE-5355-4a80-A6E6-F6125AC5EA7F}

And a site collection root site with the following GUID: {07D85DBE-5355-4a80-A6E6-F6125AC5EA7F} If I wanted the IT Site to use a custom toolsfile.xml I would creat the following file:

toolsfile{ABFD5E80-02DD-4f2c-94AF-813D4C952307}.xml

If I wanted the HR Site to use a custom configfile.xml I would create the following file: configfile{428AE37A-63D0-4d45-9681-8FC4DD9E7435}.xml

If I wanted the site collection to use the same custom configfile.xml and use a different toolsfile.xml for each site and sub site including the root site I would create the following files:

configfile{07D85DBE-5355-4a80-A6E6-F6125AC5EA7F}.xml -- > config file used for entire site collection

toolsfile{07D85DBE-5355-4a80-A6E6-F6125AC5EA7F}.xml -- > tools file used by root site

toolsfile{428AE37A-63D0-4d45-9681-8FC4DD9E7435}.xml --> tools file used by HR Site

toolsfile{ABFD5E80-02DD-4f2c-94AF-813D4C952307}.xml --> tools files used by IT Site

toolsfile{07D85DBE-5355-4a80-A6E6-F6125AC5EA7F}.xml --> tools file usd Finances Site

Cheers,
Kevin

Product Development Manager
KWizCom
Markham, Ontario
Edited
8 Years Ago by Igor
Josh Korn
Posted 8 Years Ago
View Quick Profile
Forum Guru

Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)

Group: Forum Members
Last Active: 7 Years Ago
Posts: 37, Visits: 76
Kevin:
  • defaultWiki.css
  • LAYOUTS/KWizCom_TaggingFeature files such as TagTreeControl.ascx and TagPagesListControl.ascx
since these live in the 12 hive, it's not clear to me how to get one WikiPlus site to use one set of variants, and another to use a second set, etc. The contents of configfile.xml and toolsfile.xml seem to relate only to the editor itself.

>> The resx files in all of SharePoint are only intended to be used for translation, and are scoped per farm.
>> This isn't a WikiPlus limitation, but a SharePoint one shared by all SharePoint sites.


Let me give you a directly relevant example. In the one site I built, I replaced every occurrence of the words "tag" and "wiki" - because they would have sown confusion (and possibly caused one of the decision makers to veto its use). On a couple of other sites (still to be built), where the community is more tech-oriented, those words are OK as is.

So far, the only way I've found of making those changes was to use to resource file and "translate" the terms "tag" and "wiki" into English. If there's another way to do this, please let me know what it is and I'll make use of it right away.

Hope this makes sense.

Josh

Josh Korn

Edited
8 Years Ago by Igor
Kevin
Posted 8 Years Ago
View Quick Profile
Forum Member

Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)

Group: Moderators
Last Active: 6 Years Ago
Posts: 35, Visits: 67
Each one of your sites can have a custom master page that inlcudes a custom css file that overrides the styles in defaultwiki.css. That way each site can have a custom look. If you don't want to use a custom master page  for each site you can create a delegate control that inlcudes a different css file for each site that overrides the appropriate css styles. There are many options for creating master pages and css files that override styles. Thereby changing the look and feel for each site.

Tranlsation/Modification of resx files affect every site in the farm. If you change the word entry "wiki" to "document" in the wikiplus.resx, every page/control that uses that entry will be affected. There is no real way to have different "labels" for different sites unless the locale of the site changes. These files are meant more for tranlsation that re-wording.

Cheers,
Kevin

Product Development Manager
KWizCom
Markham, Ontario
Edited
8 Years Ago by Igor
Josh Korn
Posted 8 Years Ago
View Quick Profile
Forum Guru

Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)Forum Guru (61 reputation)

Group: Forum Members
Last Active: 7 Years Ago
Posts: 37, Visits: 76
Kevin:
  • How do I handle the files that are outside the boundaries of the page editor? (e.g. TagTreeControl.ascx), -and-
  • How do I get two different sites with different words as per the above example?
I posed them because I really need to know how to solve this.

Josh

Josh Korn

Kevin
Posted 8 Years Ago
View Quick Profile
Forum Member

Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)

Group: Moderators
Last Active: 6 Years Ago
Posts: 35, Visits: 67
Josh,

You can't change the words in rex files for different sites. The resx changes are shared farm wide. The resx files are stored in the 12 hive under RESOURCES and shared amongstevery web application.

What do you mean by handle the ascx file?

Cheers,
Kevin

Product Development Manager
KWizCom
Markham, Ontario
Edited
8 Years Ago by Igor
Shai
Posted 8 Years Ago
View Quick Profile
Junior Member

Junior Member (17 reputation)Junior Member (17 reputation)Junior Member (17 reputation)Junior Member (17 reputation)Junior Member (17 reputation)Junior Member (17 reputation)Junior Member (17 reputation)Junior Member (17 reputation)Junior Member (17 reputation)

Group: Administrators
Last Active: 4 Years Ago
Posts: 17, Visits: 26
Hi Josh,

It seems what you are asking for is not supported in our product currently.

Most of the things are duable by editing the master page, but others are not.

I have forwarded this thread to our product manager to review yoru request,

It would be helpful if you could post some more information on what you are trying to achieve, print screens would be nice.

Thanks,

Shai.

--------------------------------
Shai Petel
kylomon
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 4, Visits: 9
Can I please get some clarification...

The {} are special characters - do I leave them out... so my filename would be toolsfile.guid.xml? I tried it but it does not seem to work. I put the file at the root of my site collection and my Web and they still do not show my customizations.
Kevin
Posted 8 Years Ago
View Quick Profile
Forum Member

Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)Forum Member (35 reputation)

Group: Moderators
Last Active: 6 Years Ago
Posts: 35, Visits: 67
1. The brace brackets are necessary

2. You don't move the files to your site collection. You leave them in the same place as the original files on the server.

Cheers,
Kevin

Product Development Manager
KWizCom
Markham, Ontario
kylomon
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 4, Visits: 9
I see the confusion.

When I read the line "WikiPlus is designed to check if there are customized versions of these files at the site/web level"

I take that to mean  that I need to have the custom config files in the root directory of the site or web.

What you mean is that "WikiPlus checks to see if there are customized config files for the Site or Web"

The Custom Config Files go the same place as the originals. 


Similar Topics