Return-Path: Delivered-To: apmail-incubator-aries-dev-archive@minotaur.apache.org Received: (qmail 19777 invoked from network); 20 Apr 2010 20:16:36 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Apr 2010 20:16:36 -0000 Received: (qmail 69414 invoked by uid 500); 20 Apr 2010 20:16:36 -0000 Delivered-To: apmail-incubator-aries-dev-archive@incubator.apache.org Received: (qmail 69312 invoked by uid 500); 20 Apr 2010 20:16:35 -0000 Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: aries-dev@incubator.apache.org Delivered-To: mailing list aries-dev@incubator.apache.org Delivered-To: moderator for aries-dev@incubator.apache.org Received: (qmail 45911 invoked by uid 99); 20 Apr 2010 17:45:08 -0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=AWL,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=sYWzD+Vsj9tIbkZk2jdHunqrILJdGQepZlRgX78jWjf02MlhQX4d/2xMdLsvkEiu; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Message-ID: <4BCDE808.2090201@earthlink.net> Date: Tue, 20 Apr 2010 13:44:40 -0400 From: Joe Bohn User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: aries-dev@incubator.apache.org Subject: Fwd: Re: confluence formatting Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: c408501814fc19611aa676d7e74259b7b3291a7d08dfec79d3439d7ccc2d610fbfc0dca24c7eadff350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 129.33.49.251 I had the following exchange on the infrastructure list regarding our wiki pages which don't seem to be formatted correctly when viewed via the http://incubator.apache.org/aries URL. It seems that the rsync may be having issues and perhaps needs to be updated following the confluence upgrade. Guillaume (or anybody else with authority) ... can you take a look? Perhaps we need to make some updates based upon the update confluence installation? Joe -------- Original Message -------- Subject: Re: confluence formatting Date: Tue, 20 Apr 2010 11:59:43 -0400 From: Daniel Kulp To: infrastructure@apache.org CC: Joe Bohn Actually, the version that is present on cwiki is OK: https://cwiki.apache.org/ARIES/blog-sample.html The problem seems to be that the rsyncs from the new cwiki to people.apache.org are not working (or were not setup) so it's not getting the new exports synced over and then synced to the sites. I don't have access to the new cwiki machine to try and investigate that. Not sure where/how that rsync is supposed to be triggered. Dan On Tuesday 20 April 2010 11:34:18 am Daniel Kulp wrote: > Ick. OK. > > We had this problem before and it turned out there are two plugins that can > provide the {code} macros. One works with the autoexport and the other > doesn't. I need to dig through it a bit again and figure out what I did > to fix it last time. > > Dan > > On Tuesday 20 April 2010 11:16:53 am Joe Bohn wrote: > > I noticed that there are some format issues in confluence since the > > recent upgrade. I suspect this is a result of the new version > > attempting to protect against XSS/XSRF attacks but I'm not really sure. > > > > One such case involved the {code} tag which seems to not render the > > content after export in some cases even though it displays the content > > when within the view (or preview) panel in the wiki editor. > > > > For example, have a look at: > > http://incubator.apache.org/aries/blog-sample.html > > > > where there are 4 {code} blocks that are displayed as empty. Here is > > the content of one of the {code} blocks: > > > > {code} > > java -jar osgi-3.5.0.v20090520.jar -console > > {code} > > > > We might be able to find ways to edit these fields and make them display > > (I'm currently trying {noformat} ) ... but that may mean that a lot of > > projects will have to make a lot of changes. I'm just wondering if this > > is a known issue and if there is a recommended work-around. I'm also > > wondering if there is some configuration setting that we can set to get > > the {code} sections working again without compromising security? > > > > Thanks, > > Joe -- Daniel Kulp dkulp@apache.org http://dankulp.com/blog