Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-14971

Confluence has lost all code examples in Tapestry docs

    Details

    • Type: Bug
    • Status: Waiting for Infra
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Confluence
    • Labels:
      None
    • Project:
      Tapestry

      Description

      We just discovered that all the code examples on the Tapestry docs site (https://tapestry.apache.org) are gone. Upon looking at the source pages in Confluence, the {code} examples are not displaying at all, despite working fine since they were last edited, and the source for them appears to be totally gone in Confluence.

      For example, see https://cwiki.apache.org/confluence/display/TAPESTRY/Layout+Component

      I believe these code examples were using the {code} macro.

      Any idea what's happening? Did a recent Confluence upgrade or bulk data conversion break our pages?

        Issue Links

          Activity

          Hide
          gmcdonald Gavin added a comment -
          It has been a several months since the last Upgrade - when were your docs last edited - when did you visit the site last and noticed them working ?
          Show
          gmcdonald Gavin added a comment - It has been a several months since the last Upgrade - when were your docs last edited - when did you visit the site last and noticed them working ?
          Hide
          bobharner Bob Harner added a comment - Reporter
          I think it has been 2-3 weeks since the most recent edit, but the problem exists for all pages, even those that were last edited a couple years ago (such as the Layout+Component one I linked to). I think the last time I personally viewed a page and would have noticed any brokenness would have been about a week ago. Tapestry users certainly would have reported the problem if it lasted any longer than that. Last night (about 10 hours ago) was the first report of a problem.
          Show
          bobharner Bob Harner added a comment - Reporter I think it has been 2-3 weeks since the most recent edit, but the problem exists for all pages, even those that were last edited a couple years ago (such as the Layout+Component one I linked to). I think the last time I personally viewed a page and would have noticed any brokenness would have been about a week ago. Tapestry users certainly would have reported the problem if it lasted any longer than that. Last night (about 10 hours ago) was the first report of a problem.
          Hide
          Internal
          ctargett Cassandra Targett added a comment -
          The same thing has happened for the Solr docs (Solr Reference Guide: https://cwiki.apache.org/confluence/display/solr/Post+Tool). All those {{#666666nonesolid}} you see in the referred page are supposed to be code blocks.

          We're transitioning away from cwiki as host of Solr docs, but don't yet have a redirect in place so Google searches (and user habit) still direct people there. A consequence of the transition is that our space has been locked against all edits since early May, so this isn't something anyone changed on individual pages.
          Show
          Internal
          ctargett Cassandra Targett added a comment - The same thing has happened for the Solr docs (Solr Reference Guide: https://cwiki.apache.org/confluence/display/solr/Post+Tool) . All those {{#666666nonesolid}} you see in the referred page are supposed to be code blocks. We're transitioning away from cwiki as host of Solr docs, but don't yet have a redirect in place so Google searches (and user habit) still direct people there. A consequence of the transition is that our space has been locked against all edits since early May, so this isn't something anyone changed on individual pages.
          Hide
          bobharner Bob Harner added a comment - - edited Reporter
          I think this happened at or just before 4:23 AM US/Eastern on Fri, Aug 25, 2017, because that was when the Tapestry Commits mailing list received a flood of emails from buildbot indicating that the Confluence-to-HTML export process was undergoing a bulk re-export. I don't know what triggered that action. It was NOT triggered by a content change, according to the Confluence history of changes for that space.
          Show
          bobharner Bob Harner added a comment - - edited Reporter I think this happened at or just before 4:23 AM US/Eastern on Fri, Aug 25, 2017, because that was when the Tapestry Commits mailing list received a flood of emails from buildbot indicating that the Confluence-to-HTML export process was undergoing a bulk re-export. I don't know what triggered that action. It was NOT triggered by a content change, according to the Confluence history of changes for that space.
          Hide
          gmcdonald Gavin added a comment -
          I dont really know much about the confluence to html exporter either, do you know more about it?

          It wasnt afaik triggered by Infra.

          Some plugins were updated a few weeks ago, and an upgrade happened months ago.
          (Another major upgrade is happening soon too)

          Show
          gmcdonald Gavin added a comment - I dont really know much about the confluence to html exporter either, do you know more about it? It wasnt afaik triggered by Infra. Some plugins were updated a few weeks ago, and an upgrade happened months ago. (Another major upgrade is happening soon too)
          Hide
          bobharner Bob Harner added a comment - Reporter
          Tapestry's site export process is described at http://tapestry.apache.org/confluence-site-setup.html -- but the problem is apparently unrelated to that process, because you can see the symptoms occurring in the original Confluence pages.
          Show
          bobharner Bob Harner added a comment - Reporter Tapestry's site export process is described at http://tapestry.apache.org/confluence-site-setup.html -- but the problem is apparently unrelated to that process, because you can see the symptoms occurring in the original Confluence pages.
          Hide
          gmcdonald Gavin added a comment -
          Ok, at this stage we are just going to have to go with, something happened, maybe a plugin upgrade or deprecation.

          Do you know which plugin the {code} macros belong to?
          Show
          gmcdonald Gavin added a comment - Ok, at this stage we are just going to have to go with, something happened, maybe a plugin upgrade or deprecation. Do you know which plugin the {code} macros belong to?
          Hide
          bobharner Bob Harner added a comment - Reporter
          I believe the code macro is part of core Confluence -- https://confluence.atlassian.com/doc/code-block-macro-139390.html

          Is it possible to restore the Tapestry space from backup from a few days ago?

          Alternatively, do you have access to Atlassian support to ask them about the problem?
          Show
          bobharner Bob Harner added a comment - Reporter I believe the code macro is part of core Confluence -- https://confluence.atlassian.com/doc/code-block-macro-139390.html Is it possible to restore the Tapestry space from backup from a few days ago? Alternatively, do you have access to Atlassian support to ask them about the problem?
          Hide
          gmcdonald Gavin added a comment -
          If there is a change in a plugin, then restoring a space to a few days ago wont change a thing. Also, if it part of core that is the problem, then that needs fixing and restoring a space to a few days ago wont help then either.

          Let us investigate some more before contacting Atlassian shall we.
          Show
          gmcdonald Gavin added a comment - If there is a change in a plugin, then restoring a space to a few days ago wont change a thing. Also, if it part of core that is the problem, then that needs fixing and restoring a space to a few days ago wont help then either. Let us investigate some more before contacting Atlassian shall we.
          Hide
          Internal
          elyograg Shawn Heisey added a comment -
          This has also happened to the old version of the Solr Reference Guide in Confluence. Thankfully this has been migrated to documentation generated from information in the source code repository. We have asked infra to set up redirects in INFRA-14849, but it's apparently not a small job. Users are noticing. See SOLR-11357 for an example of that.
          Show
          Internal
          elyograg Shawn Heisey added a comment - This has also happened to the old version of the Solr Reference Guide in Confluence. Thankfully this has been migrated to documentation generated from information in the source code repository. We have asked infra to set up redirects in INFRA-14849 , but it's apparently not a small job. Users are noticing. See SOLR-11357 for an example of that.
          Hide
          gmcdonald Gavin added a comment -
          Hi [~elyograg] thanks . I am actively working this ticket. I have our test instance at a stage in time where these are working.

          See https://cwiki-test.apache.org/confluence/display/solr/CharFilterFactories for an example.

          Show
          gmcdonald Gavin added a comment - Hi [~elyograg] thanks . I am actively working this ticket. I have our test instance at a stage in time where these are working. See https://cwiki-test.apache.org/confluence/display/solr/CharFilterFactories for an example.
          Hide
          bobharner Bob Harner added a comment - Reporter
          While this issue is being worked, I have temporarily reverted the Tapestry HTML docs (in svn) to the 7/9/2017 version (the last commit before the 8/25/2017 version where the problem first appeared). I believe the source code examples are all now appearing correctly. However, this means our docs can't be edited with Confluence until this issue is resolved.
          Show
          bobharner Bob Harner added a comment - Reporter While this issue is being worked, I have temporarily reverted the Tapestry HTML docs (in svn) to the 7/9/2017 version (the last commit before the 8/25/2017 version where the problem first appeared). I believe the source code examples are all now appearing correctly. However, this means our docs can't be edited with Confluence until this issue is resolved.

            People

            • Assignee:
              gmcdonald Gavin
              Reporter:
              bobharner Bob Harner
              Request participants:
              None
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: