Details

      Description

      This issue is for projects to report any issues with their spaces during pre-upgrade checks on the test instance and also post-upgrade once the production instance has been upgraded.

        Issue Links

          Activity

          Hide
          Gavin added a comment -
          Projects should mention their SPACE name, the problem, and whether or not any macros or plugins are involved.
          Please note we will not be testing for or looking atr any Autoexport problems at this time.
          Show
          Gavin added a comment - Projects should mention their SPACE name, the problem, and whether or not any macros or plugins are involved. Please note we will not be testing for or looking atr any Autoexport problems at this time.
          Show
          Lukasz Lenart added a comment - Why everything is centred? https://cwiki2.apache.org/confluence/display/WW/Home https://cwiki2.apache.org/confluence/spaces/viewstylesheet.action?key=WW
          Hide
          Lukasz Lenart added a comment - - edited
          Ok, got it :-) But why it works with the old version?

          I have edited space css and removed text-align: center; from body{} section
          Show
          Lukasz Lenart added a comment - - edited Ok, got it :-) But why it works with the old version? I have edited space css and removed text-align: center; from body{} section
          Hide
          Gavin added a comment -
          I used the <center> tags for the notices at the top and bottom of the test instance. That may interefere with some of the older layouts. Certainly the newer layouts like the Documentation Theme don't have an issue.
          Show
          Gavin added a comment - I used the <center> tags for the notices at the top and bottom of the test instance. That may interefere with some of the older layouts. Certainly the newer layouts like the Documentation Theme don't have an issue.
          Hide
          Lukasz Lenart added a comment -
          Another problem is with editing. The old content is wrapped inside {wiki markup} and it must be manually translated to the new fancy format - is it expected behaviour?

          Check this out, I have re-edited page but I must translate each link or markup to the new format
          https://cwiki2.apache.org/confluence/display/WW/Version+Notes+2.3.15
          Show
          Lukasz Lenart added a comment - Another problem is with editing. The old content is wrapped inside {wiki markup} and it must be manually translated to the new fancy format - is it expected behaviour? Check this out, I have re-edited page but I must translate each link or markup to the new format https://cwiki2.apache.org/confluence/display/WW/Version+Notes+2.3.15
          Hide
          Gavin added a comment -
          I know we are missing the code macro (https://cwiki2.apache.org/confluence/display/WW/CRUD+Demo+I) which I'll look at.
          The wiki markup not sure yet, any old code should have been converted unless it was using an unsupported/deprecated space theme.
          Can you change to the documentation theme and see how that looks ? - - feel free to use the 'Copy Space' function in space admin and convert a copy of your space to try it.
          Show
          Gavin added a comment - I know we are missing the code macro ( https://cwiki2.apache.org/confluence/display/WW/CRUD+Demo+I ) which I'll look at. The wiki markup not sure yet, any old code should have been converted unless it was using an unsupported/deprecated space theme. Can you change to the documentation theme and see how that looks ? - - feel free to use the 'Copy Space' function in space admin and convert a copy of your space to try it.
          Hide
          Daniel Kulp added a comment - - edited

          The {html} macros are not enabled in the new test instance. Some site have used them for various things. Example:

          https://cwiki.apache.org/confluence/pages/editpage.action?pageId=2330660

          The question really is should we enable them for compatibility with previous stuff or keep them disabled and let the projects know they'll need to update their pages that use them. (I'm going to be editing that page in the test instance to see what I can do to work around it)
          Show
          Daniel Kulp added a comment - - edited The {html} macros are not enabled in the new test instance. Some site have used them for various things. Example: https://cwiki.apache.org/confluence/pages/editpage.action?pageId=2330660 The question really is should we enable them for compatibility with previous stuff or keep them disabled and let the projects know they'll need to update their pages that use them. (I'm going to be editing that page in the test instance to see what I can do to work around it)
          Hide
          Alex Boisvert added a comment - - edited
          Quick note that we're using the {code} macro on the BUILDR space (I see Gavin already mentioned above).

          Here's a page that can be used for testing if needed: https://cwiki2.apache.org/confluence/display/BUILDR/Common+Problems+and+Solutions
          Show
          Alex Boisvert added a comment - - edited Quick note that we're using the {code} macro on the BUILDR space (I see Gavin already mentioned above). Here's a page that can be used for testing if needed: https://cwiki2.apache.org/confluence/display/BUILDR/Common+Problems+and+Solutions
          Hide
          Gavin added a comment -
          Show
          Gavin added a comment - got the code block working ( https://cwiki2.apache.org/confluence/display/test/code+block+test )
          Hide
          Gavin added a comment -
          [~lukaszlenart] I re-ran the wiki-to-xhtml conversion process, any better?
          Show
          Gavin added a comment - [~lukaszlenart] I re-ran the wiki-to-xhtml conversion process, any better?
          Hide
          Daniel Kulp added a comment -

          A page using an {html} tag to add a search form:

          https://cwiki2.apache.org/confluence/display/CXF20DOC/Index

          Show
          Daniel Kulp added a comment - A page using an {html} tag to add a search form: https://cwiki2.apache.org/confluence/display/CXF20DOC/Index
          Hide
          Gavin added a comment -
          Show
          Gavin added a comment - Pricing for the HTML plugin: https://marketplace.atlassian.com/plugins/org.swift.confluence.html/pricing
          Hide
          Gavin added a comment -
          So I managed to get a valid license for the plugin, but it still wont load yet, investigating.
          Show
          Gavin added a comment - So I managed to get a valid license for the plugin, but it still wont load yet, investigating.
          Hide
          Gavin added a comment - - edited
          Fixed. (The HTML Macro Plugin)
          Show
          Gavin added a comment - - edited Fixed. (The HTML Macro Plugin)
          Hide
          Gavin added a comment -
          For those watching this issue, try this out on your own cwiki space: http://blogs.atlassian.com/2013/03/3-killer-features-for-creating-awesome-confluence-page-templates/
          Show
          Gavin added a comment - For those watching this issue, try this out on your own cwiki space: http://blogs.atlassian.com/2013/03/3-killer-features-for-creating-awesome-confluence-page-templates/
          Hide
          Daniel Kulp added a comment -
          Many pages seem to have been imported as one giant "Wiki Markup" block which then doesn't work properly for editing or display and such. Code format blocks are wrong. Etc... For example:

          https://cwiki2.apache.org/confluence/display/CXF20DOC/JAXB
          https://cwiki2.apache.org/confluence/display/CXF20DOC/JAX-WS+Dispatch+API
          etc....

          Is there an easy way to fix those?
          Show
          Daniel Kulp added a comment - Many pages seem to have been imported as one giant "Wiki Markup" block which then doesn't work properly for editing or display and such. Code format blocks are wrong. Etc... For example: https://cwiki2.apache.org/confluence/display/CXF20DOC/JAXB https://cwiki2.apache.org/confluence/display/CXF20DOC/JAX-WS+Dispatch+API etc.... Is there an easy way to fix those?
          Hide
          Lukasz Lenart added a comment -
          [~ipv6guru] much better :-)
          Show
          Lukasz Lenart added a comment - [~ipv6guru] much better :-)
          Hide
          Lukasz Lenart added a comment -
          [~dkulp] we had the same with WW space but [~ipv6guru] did some trick and now everything is ok.
          Show
          Lukasz Lenart added a comment - [~dkulp] we had the same with WW space but [~ipv6guru] did some trick and now everything is ok.
          Hide
          Gavin added a comment -
          I see nothing here to postpone the upgrade so it will proceed as planned tomorrow morning my time. (About 20 hours from now things will start)
          Show
          Gavin added a comment - I see nothing here to postpone the upgrade so it will proceed as planned tomorrow morning my time. (About 20 hours from now things will start)
          Hide
          Lukasz Lenart added a comment -
          [~ipv6guru] from our side (Struts project) the only problem is missing support for autoexport plugin - our release process heavily depends on it. Let us know what is the status here - should we wait for working solution based on autoexport plugin or should we switch to something else.
          Show
          Lukasz Lenart added a comment - [~ipv6guru] from our side (Struts project) the only problem is missing support for autoexport plugin - our release process heavily depends on it. Let us know what is the status here - should we wait for working solution based on autoexport plugin or should we switch to something else.
          Hide
          Daniel Kulp added a comment -
          As announce 2 years ago, the autoexport plugin is completely deprecated and is being removed.

          Some projects have switched to an external build (buildbot run) to accomplish the same thing. See: http://svn.apache.org/repos/asf/cxf/web/

          That has been updated to work with the new confluence, although I expect some more updates may be needed. Also see:

          http://mail-archives.apache.org/mod_mbox/camel-dev/201306.mbox/%3CE488D280-44CA-435F-A85C-F0F88453B189%40apache.org%3E

          for more details about changes required in the velocity templates.
          Show
          Daniel Kulp added a comment - As announce 2 years ago, the autoexport plugin is completely deprecated and is being removed. Some projects have switched to an external build (buildbot run) to accomplish the same thing. See: http://svn.apache.org/repos/asf/cxf/web/ That has been updated to work with the new confluence, although I expect some more updates may be needed. Also see: http://mail-archives.apache.org/mod_mbox/camel-dev/201306.mbox/%3CE488D280-44CA-435F-A85C-F0F88453B189%40apache.org%3E for more details about changes required in the velocity templates.
          Hide
          Gavin added a comment -
          Typically the dry run upgrade went fine. the actual upgrade failed for 3.5.17 to 4.3.
          So I'm leaving it at 3.5.17 (on a new server) for today and will try again tomorrow to go to 4.3 and then to 5.1.x
          Show
          Gavin added a comment - Typically the dry run upgrade went fine. the actual upgrade failed for 3.5.17 to 4.3. So I'm leaving it at 3.5.17 (on a new server) for today and will try again tomorrow to go to 4.3 and then to 5.1.x
          Hide
          Lukasz Lenart added a comment - - edited
          [~dkulp] Thanks, I didn't know that :\

          Anyway, I'm looking into cxf-web project and one thing is wondering me: in the update-site script there is {{mvn -Pconfluence,nochecks}} but I don't see such profiles in the poms. Is it a mistake?

          Another question is: does that exporter is available as a Maven archetype or should I copy it to Struts repository and use from there?
          Show
          Lukasz Lenart added a comment - - edited [~dkulp] Thanks, I didn't know that :\ Anyway, I'm looking into cxf-web project and one thing is wondering me: in the update-site script there is {{mvn -Pconfluence,nochecks}} but I don't see such profiles in the poms. Is it a mistake? Another question is: does that exporter is available as a Maven archetype or should I copy it to Struts repository and use from there?
          Hide
          Daniel Kulp added a comment -

          Lukasz:

          The README in the directory describes the confluence profile (mostly to provide a username/password). The nochecks isn't really needed, it just takes longer. It uses the CXF parent pom which by default enables Checkstyle and PMD checks on the code which can take a few extra seconds. The nochecks turns that off.

          I'd copy everything but the "src" dir to struts and edit the templates and such. Use an svn:external to grab the src dir from CXF so as I keep fixing things as we transition to the new Confluence, you'll get the fixes. Users are finding little issues each day still and I expect even more once 5.1 goes "live". Alternatively, don't put a src dir at all and "depend" on the "SNAPSHOT version of CXF's that I'm deploy to the Apache Nexus snapshot repo.
          Show
          Daniel Kulp added a comment - Lukasz: The README in the directory describes the confluence profile (mostly to provide a username/password). The nochecks isn't really needed, it just takes longer. It uses the CXF parent pom which by default enables Checkstyle and PMD checks on the code which can take a few extra seconds. The nochecks turns that off. I'd copy everything but the "src" dir to struts and edit the templates and such. Use an svn:external to grab the src dir from CXF so as I keep fixing things as we transition to the new Confluence, you'll get the fixes. Users are finding little issues each day still and I expect even more once 5.1 goes "live". Alternatively, don't put a src dir at all and "depend" on the "SNAPSHOT version of CXF's that I'm deploy to the Apache Nexus snapshot repo.
          Hide
          Lukasz Lenart added a comment -
          [~dkulp] Thanks! I got it running, almost :-)

          Two problems so far:
          - missing code highlighting - I probably have to include some JS
          - how to run plugin just for main project but not for submodules?
          Show
          Lukasz Lenart added a comment - [~dkulp] Thanks! I got it running, almost :-) Two problems so far: - missing code highlighting - I probably have to include some JS - how to run plugin just for main project but not for submodules?
          Hide
          Daniel Kulp added a comment -

          Check the CXF template:
          http://svn.apache.org/repos/asf/cxf/web/template/template.vm

          for the javascript that's needed. I don't really understand the second question.
          Show
          Daniel Kulp added a comment - Check the CXF template: http://svn.apache.org/repos/asf/cxf/web/template/template.vm for the javascript that's needed. I don't really understand the second question.
          Hide
          Lukasz Lenart added a comment -
          [~dkulp] thanks again :-)

          The second: I have added it to multi-module project and Maven is trying to execute it for each submodule, but this is less important.
          Show
          Lukasz Lenart added a comment - [~dkulp] thanks again :-) The second: I have added it to multi-module project and Maven is trying to execute it for each submodule, but this is less important.
          Hide
          Lukasz Lenart added a comment -
          [~dkulp] everything works brilliant :-) Thanks a lot! A have one wish - could you post announcement when the final version will be available?
          Show
          Lukasz Lenart added a comment - [~dkulp] everything works brilliant :-) Thanks a lot! A have one wish - could you post announcement when the final version will be available?
          Hide
          Gavin added a comment -
          Closing.

          We are now on 5.0.3 (and soon to be $latest) , if any new problems arise with the latest upgrade, please file separate tickets.
          Show
          Gavin added a comment - Closing. We are now on 5.0.3 (and soon to be $latest) , if any new problems arise with the latest upgrade, please file separate tickets.

            People

            • Assignee:
              Unassigned
              Reporter:
              Gavin
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development