Re: {code} examples lost when publishing Confluence doc pages

[Bob Harner <bo...@gmail.com>]

Everybody,

I finally got around to investigating this problem myself. Newer versions
of Confluence render {code} tags to HTML in a very different way than
previously, using http://alexgorbatchev.com/SyntaxHighlighter with content
inside of <script> tags instead of <pre> tags. Dan Kulp's SiteExporter code
(at
http://svn.apache.org/repos/asf/cxf/web/src/main/java/org/apache/cxf/cwiki/)
has already been updated to accommodate this nicely, but we are running an
outdated copy of that code (at
https://svn.apache.org/repos/asf/tapestry/tapestry-site/trunk/src/main/java/org/apache/cxf/cwiki
)

Locally I switched to a updated copy of SiteExporter code, adjusted the
Velocity template file to match, and now everything seems to work properly
(on my desktop copy), except for some minor CSS issues that I haven't
addressed yet. However, I haven't committed anything yet because I haven't
fully evaluated what changes Uli made to the SiteExporter code since he
made the copy. I'll do that in a day or so unless he answers the question
before then.


On Sun, Aug 18, 2013 at 5:13 PM, Bob Harner <bo...@gmail.com> wrote:

> Hi everybody (especially Uli),
>
> I did a minor edit to the http://tapestry.apache.org/javascript.html<http://tapestry.apache.org/javascript.html#comment_1504> page
> recently and, although everything looked fine in the Confluence editor
> preview, when it was published all the {code} examples were omitted.
>
> Does anybody know what is broken in the publishing process?
>
> Missing {code} content was one of the issues noted and fixed with the
> switch to Confluence 5 a couple months back (
> https://issues.apache.org/jira/browse/INFRA-6406), and they seemed to
> work fine in recent weeks, I believe.
>
> Maybe we are suffering from using an outdated copy of Dan Kulp's CFX
> export code?
>

Re: {code} examples lost when publishing Confluence doc pages

[Howard Lewis Ship <hl...@gmail.com>]

+1 !


On Sun, Sep 22, 2013 at 9:07 PM, Kalle Korhonen
<ka...@gmail.com>wrote:

> Thanks so much Bob, this is really important work.
>
> Kalle
>
>
> On Sun, Sep 22, 2013 at 4:27 PM, Bob Harner <bo...@gmail.com> wrote:
>
> > I looked over Uli's commits and didn't see any functional improvements
> that
> > would be lost by replacing it with Dan Kulps improvements in the CXF
> > project, so I did so, and rebuilt the site.
> >
> > Now Tapestry, CXF, Camel, Geronimo and Struts all appear to be using the
> > same version of the export code.
> >
> > And it's once again safe to edit the pages in Confluence.
> > On Sep 15, 2013 9:49 PM, "Bob Harner" <bo...@gmail.com> wrote:
> >
> > > Everybody,
> > >
> > > I finally got around to investigating this problem myself. Newer
> versions
> > > of Confluence render {code} tags to HTML in a very different way than
> > > previously, using http://alexgorbatchev.com/SyntaxHighlighter with
> > > content inside of <script> tags instead of <pre> tags. Dan Kulp's
> > > SiteExporter code (at
> > >
> >
> http://svn.apache.org/repos/asf/cxf/web/src/main/java/org/apache/cxf/cwiki/
> > )
> > > has already been updated to accommodate this nicely, but we are running
> > an
> > > outdated copy of that code (at
> > >
> >
> https://svn.apache.org/repos/asf/tapestry/tapestry-site/trunk/src/main/java/org/apache/cxf/cwiki
> > > )
> > >
> > > Locally I switched to a updated copy of SiteExporter code, adjusted the
> > > Velocity template file to match, and now everything seems to work
> > properly
> > > (on my desktop copy), except for some minor CSS issues that I haven't
> > > addressed yet. However, I haven't committed anything yet because I
> > haven't
> > > fully evaluated what changes Uli made to the SiteExporter code since he
> > > made the copy. I'll do that in a day or so unless he answers the
> question
> > > before then.
> > >
> > >
> > > On Sun, Aug 18, 2013 at 5:13 PM, Bob Harner <bo...@gmail.com>
> wrote:
> > >
> > >> Hi everybody (especially Uli),
> > >>
> > >> I did a minor edit to the http://tapestry.apache.org/javascript.html<
> > http://tapestry.apache.org/javascript.html#comment_1504> page
> > >> recently and, although everything looked fine in the Confluence editor
> > >> preview, when it was published all the {code} examples were omitted.
> > >>
> > >> Does anybody know what is broken in the publishing process?
> > >>
> > >> Missing {code} content was one of the issues noted and fixed with the
> > >> switch to Confluence 5 a couple months back (
> > >> https://issues.apache.org/jira/browse/INFRA-6406), and they seemed to
> > >> work fine in recent weeks, I believe.
> > >>
> > >> Maybe we are suffering from using an outdated copy of Dan Kulp's CFX
> > >> export code?
> > >>
> > >
> > >
> >
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

Re: {code} examples lost when publishing Confluence doc pages

[Kalle Korhonen <ka...@gmail.com>]

Thanks so much Bob, this is really important work.

Kalle


On Sun, Sep 22, 2013 at 4:27 PM, Bob Harner <bo...@gmail.com> wrote:

> I looked over Uli's commits and didn't see any functional improvements that
> would be lost by replacing it with Dan Kulps improvements in the CXF
> project, so I did so, and rebuilt the site.
>
> Now Tapestry, CXF, Camel, Geronimo and Struts all appear to be using the
> same version of the export code.
>
> And it's once again safe to edit the pages in Confluence.
> On Sep 15, 2013 9:49 PM, "Bob Harner" <bo...@gmail.com> wrote:
>
> > Everybody,
> >
> > I finally got around to investigating this problem myself. Newer versions
> > of Confluence render {code} tags to HTML in a very different way than
> > previously, using http://alexgorbatchev.com/SyntaxHighlighter with
> > content inside of <script> tags instead of <pre> tags. Dan Kulp's
> > SiteExporter code (at
> >
> http://svn.apache.org/repos/asf/cxf/web/src/main/java/org/apache/cxf/cwiki/
> )
> > has already been updated to accommodate this nicely, but we are running
> an
> > outdated copy of that code (at
> >
> https://svn.apache.org/repos/asf/tapestry/tapestry-site/trunk/src/main/java/org/apache/cxf/cwiki
> > )
> >
> > Locally I switched to a updated copy of SiteExporter code, adjusted the
> > Velocity template file to match, and now everything seems to work
> properly
> > (on my desktop copy), except for some minor CSS issues that I haven't
> > addressed yet. However, I haven't committed anything yet because I
> haven't
> > fully evaluated what changes Uli made to the SiteExporter code since he
> > made the copy. I'll do that in a day or so unless he answers the question
> > before then.
> >
> >
> > On Sun, Aug 18, 2013 at 5:13 PM, Bob Harner <bo...@gmail.com> wrote:
> >
> >> Hi everybody (especially Uli),
> >>
> >> I did a minor edit to the http://tapestry.apache.org/javascript.html<
> http://tapestry.apache.org/javascript.html#comment_1504> page
> >> recently and, although everything looked fine in the Confluence editor
> >> preview, when it was published all the {code} examples were omitted.
> >>
> >> Does anybody know what is broken in the publishing process?
> >>
> >> Missing {code} content was one of the issues noted and fixed with the
> >> switch to Confluence 5 a couple months back (
> >> https://issues.apache.org/jira/browse/INFRA-6406), and they seemed to
> >> work fine in recent weeks, I believe.
> >>
> >> Maybe we are suffering from using an outdated copy of Dan Kulp's CFX
> >> export code?
> >>
> >
> >
>

Re: {code} examples lost when publishing Confluence doc pages

[Bob Harner <bo...@gmail.com>]

I looked over Uli's commits and didn't see any functional improvements that
would be lost by replacing it with Dan Kulps improvements in the CXF
project, so I did so, and rebuilt the site.

Now Tapestry, CXF, Camel, Geronimo and Struts all appear to be using the
same version of the export code.

And it's once again safe to edit the pages in Confluence.
On Sep 15, 2013 9:49 PM, "Bob Harner" <bo...@gmail.com> wrote:

> Everybody,
>
> I finally got around to investigating this problem myself. Newer versions
> of Confluence render {code} tags to HTML in a very different way than
> previously, using http://alexgorbatchev.com/SyntaxHighlighter with
> content inside of <script> tags instead of <pre> tags. Dan Kulp's
> SiteExporter code (at
> http://svn.apache.org/repos/asf/cxf/web/src/main/java/org/apache/cxf/cwiki/)
> has already been updated to accommodate this nicely, but we are running an
> outdated copy of that code (at
> https://svn.apache.org/repos/asf/tapestry/tapestry-site/trunk/src/main/java/org/apache/cxf/cwiki
> )
>
> Locally I switched to a updated copy of SiteExporter code, adjusted the
> Velocity template file to match, and now everything seems to work properly
> (on my desktop copy), except for some minor CSS issues that I haven't
> addressed yet. However, I haven't committed anything yet because I haven't
> fully evaluated what changes Uli made to the SiteExporter code since he
> made the copy. I'll do that in a day or so unless he answers the question
> before then.
>
>
> On Sun, Aug 18, 2013 at 5:13 PM, Bob Harner <bo...@gmail.com> wrote:
>
>> Hi everybody (especially Uli),
>>
>> I did a minor edit to the http://tapestry.apache.org/javascript.html<http://tapestry.apache.org/javascript.html#comment_1504> page
>> recently and, although everything looked fine in the Confluence editor
>> preview, when it was published all the {code} examples were omitted.
>>
>> Does anybody know what is broken in the publishing process?
>>
>> Missing {code} content was one of the issues noted and fixed with the
>> switch to Confluence 5 a couple months back (
>> https://issues.apache.org/jira/browse/INFRA-6406), and they seemed to
>> work fine in recent weeks, I believe.
>>
>> Maybe we are suffering from using an outdated copy of Dan Kulp's CFX
>> export code?
>>
>
>