• Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Medium Medium
    • None
    • 2.10
    • None

      An example can be seen on extranet under:

      http://extranet.atlassian.com/pages/viewpage.action?pageId=1678542589

      Here is the page history:

      http://extranet.atlassian.com/pages/viewpreviousversions.action?title=Picnik+Proposal&spaceKey=DEVNET

      The exception that is being thrown is:

      Cause
      java.lang.RuntimeException: Error rendering template for decorator root
          at com.atlassian.confluence.setup.velocity.ApplyDecoratorDirective.render(ApplyDecoratorDirective.java:232)
      
      caused by: java.lang.RuntimeException: Error rendering template for decorator page
          at com.atlassian.confluence.setup.velocity.ApplyDecoratorDirective.render(ApplyDecoratorDirective.java:232)
      
      caused by: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getDisplayableLabel' in class
       com.atlassian.confluence.plugin.descriptor.web.model.ConfluenceWebLabel threw exception com.atlassian.core.exception.InfrastructureException: 
      Error occurred rendering template content @ /decorators/includes/content-navigation.vm[2,36]
          at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)
      
      caused by: com.atlassian.core.exception.InfrastructureException: Error occurred rendering template content
          at com.atlassian.confluence.util.velocity.VelocityUtils.getRenderedContent(VelocityUtils.java:132)
      
      caused by: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getLatestVersionsOfAttachments' in class
       com.atlassian.confluence.pages.Page threw exception net.sf.hibernate.LazyInitializationException: 
      Failed to lazily initialize a collection @ getRenderedContent[1,15]
          at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)
      
      caused by: net.sf.hibernate.LazyInitializationException: Failed to lazily initialize a collection
          at net.sf.hibernate.collection.PersistentCollection.initialize(PersistentCollection.java:201)
      
      caused by: net.sf.hibernate.HibernateException: collection was evicted
          at net.sf.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:3305)
      

            [CONFSERVER-13656] Editgrid macro can cause system errors

            BillA added a comment -

            Editgrid plugin/macro is no longer available so closing as obsolete.

            BillA added a comment - Editgrid plugin/macro is no longer available so closing as obsolete.

            Please note this issue should only be used for cases where Editgrid is responsible for this error.

            There are other situations where the same error could be presented that are not directly related to this issue.

            Andrew Lynch (Inactive) added a comment - Please note this issue should only be used for cases where Editgrid is responsible for this error. There are other situations where the same error could be presented that are not directly related to this issue.

            Hi Team,
            Any update on this case.

            We are not able to use the Office connector plugin because of this issue with the viewfile macro.

            Infact we donot have teh Editgrid plugin installed in our system at all.

            Thanks and Regards
            Aditee Pandey
            Wiki Support

            Cisco IT Wiki Support added a comment - Hi Team, Any update on this case. We are not able to use the Office connector plugin because of this issue with the viewfile macro. Infact we donot have teh Editgrid plugin installed in our system at all. Thanks and Regards Aditee Pandey Wiki Support

            This is happening with pages without the Editgrid macro as well.
            In one of the cases, the page has just the viewfile macro for embedding a word document.

            Gurleen Anand [Atlassian] added a comment - This is happening with pages without the Editgrid macro as well. In one of the cases, the page has just the viewfile macro for embedding a word document.

            Anatoli added a comment -

            The problem only happens when editgrid macro is not given a filename parameter. When the parameter is present the plugin works fine.
            The major problem here is that once you have made a mistake and saved a page with editgrid macro without a filename parameter you can no longer view the page as the exception is thrown all the time. For an average user it means that they will not be able to edit page and therefore will not know how to fix the mistake.

            The workaround is to go to the edit URL directly: BASEURL/pages/editpage.action?pageId=PAGEID

            I am trying to convince EditGrid to investigate/fix it.

            Anatoli added a comment - The problem only happens when editgrid macro is not given a filename parameter. When the parameter is present the plugin works fine. The major problem here is that once you have made a mistake and saved a page with editgrid macro without a filename parameter you can no longer view the page as the exception is thrown all the time. For an average user it means that they will not be able to edit page and therefore will not know how to fix the mistake. The workaround is to go to the edit URL directly: BASEURL/pages/editpage.action?pageId=PAGEID I am trying to convince EditGrid to investigate/fix it.

            Anatoli added a comment -

            Clark Li from EditGrid came back saying that he could not reproduce this problem with 2.10-m8:

            I tried installed confluence-2.10-m8 (WAR) version in my tomcat, installed EditGrid Plugin, created Spreadsheet (use macro), edited spreadsheet and saved spreadsheet. but did not see the error in log files.

            Anatoli added a comment - Clark Li from EditGrid came back saying that he could not reproduce this problem with 2.10-m8: I tried installed confluence-2.10-m8 (WAR) version in my tomcat, installed EditGrid Plugin, created Spreadsheet (use macro), edited spreadsheet and saved spreadsheet. but did not see the error in log files.

            This won't be fixed in 2.10. We are awaiting response from the EditGrid people since the problem seems to be within their product. Until we get more information from them we can't give an estimate of when this will be fixed.

            Paul Curren added a comment - This won't be fixed in 2.10. We are awaiting response from the EditGrid people since the problem seems to be within their product. Until we get more information from them we can't give an estimate of when this will be fixed.

            Since the issue isn't with the plugins framework, I'm taking myself off the issue.

            Don Brown (Inactive) added a comment - Since the issue isn't with the plugins framework, I'm taking myself off the issue.

            jens added a comment -

            How is this not a blocker if it renders pages unaccessible? I think we will have to sort this out as soon as possible. Customers who have bought the EditGrid plugin would not be too happy if they cannot access their data and Confluence Support will be the ones who suffer.

            jens added a comment - How is this not a blocker if it renders pages unaccessible? I think we will have to sort this out as soon as possible. Customers who have bought the EditGrid plugin would not be too happy if they cannot access their data and Confluence Support will be the ones who suffer.

            Anatoli added a comment -

            This bug is not a blocker as it only happens with pages with editgrid macro - lowering the priority.

            Anatoli added a comment - This bug is not a blocker as it only happens with pages with editgrid macro - lowering the priority.

              Unassigned Unassigned
              jens@atlassian.com jens
              Affected customers:
              6 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: