Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 36963DF53 for ; Wed, 14 Nov 2012 16:46:35 +0000 (UTC) Received: (qmail 36749 invoked by uid 500); 14 Nov 2012 16:46:35 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 36667 invoked by uid 500); 14 Nov 2012 16:46:33 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 36631 invoked by uid 99); 14 Nov 2012 16:46:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2012 16:46:32 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates 209.85.160.175 as permitted sender) Received: from [209.85.160.175] (HELO mail-gh0-f175.google.com) (209.85.160.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2012 16:46:27 +0000 Received: by mail-gh0-f175.google.com with SMTP id z2so153672ghb.6 for ; Wed, 14 Nov 2012 08:46:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=yTMlk0akAIrIMqsj348IFNpnDayejXg0smMKtea9lkg=; b=xcoihmYj+dxWnKl411HPuebWcbmXTEBoZJty6oT1gcaaqDQ01V7I4jjta0Apn89Lx1 eUZ2DsWf25l0oati3BkOxEq0PGX7gpbqEk3AMi4tmfwFGzfo6IwxtEcTrP4kNX7+YFiu 714D7g1k6ixiPkc0cgyM5+YWpbb/xHHA4br2dzhdebxW3PGZ1GZNdEo2JemO9vj7EQKm 39gks0chofSxdHQONj4zUoubkYNnUS6vLgXMopditoZBOr1nryuDTUGuAOMj5eUFjPeJ qeLnYJ2mRqjMalwsjPR40M/EsUxKa+2biKKBzbqFsuyBQDlMv9U7oDtBdGW81kc6r+xw TfWA== MIME-Version: 1.0 Received: by 10.58.187.234 with SMTP id fv10mr32511136vec.8.1352911566891; Wed, 14 Nov 2012 08:46:06 -0800 (PST) Received: by 10.58.156.71 with HTTP; Wed, 14 Nov 2012 08:46:06 -0800 (PST) In-Reply-To: References: Date: Wed, 14 Nov 2012 11:46:06 -0500 Message-ID: Subject: Re: Whitelabeling: Documentation From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 11/14/12, Peter Ko=C5=BEelj wrote: > This is in part already covered and implemented by > https://issues.apache.org/bloodhound/ticket/85 > A couple of observations: > > 1. Currently this does not happen automatically when a new environment is > created. Any reason against it? If not we should probably open a new tick= et > for this. It happens in BH installer ... but maybe it's ok to make it work the way you suggest . > 2. This only covers wiki pages, links from UI still point to old wikis. > Example 1: When a TracError is handled on UI a link to old "TracGuid= e" > is rendered > Example 2: On the bottom of ticket page "TracTckets" is referenced > You are right . What shall we do ? > Some of this are in BH code and some in Trac. > We should at least fix instances in BH code. If you come up with something keeping all the pieces altogether in a consistent manner I'm ok with whatever you suggest ;) > Can we do some kind of > script that would "fix" Trac code on installation or something? > Automatically upgrading the wikis is precondition for this. > There are many ways to fix Trac code without actually applying a patch against its source code . In this particular case , at least for informative messages in wiki pages my suggestion is to determine inside _modify_* methods (theme plugin) whether Trac* or Guide/* pages are installed . Based on this pass some data to the BH templates to choose the correct wiki page and render the link . ... feel free to get this done the way you consider more appropriate , but please , at least for links in help messages , do not patch Trac source code. There's no need to . --=20 Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: