Uploaded image for project: 'CMS'
  1. CMS
  2. CMS-2375

Content export/rendering pipeline in the CMS workspace can't handle binary formats

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 3.1
    • None
    • Workspace : CMS
    • None

      The content export/rendering pipelines (versioned and not versioned) in the CMS workspace can't handle binary formats:

      workspace.xml
      <map:match pattern="_content.*">
    <map:act type="get-content">
        <map:parameter name="id" value="{request-param:contentId}"/>
        <map:parameter name="contentVersion" value="{request-param:contentVersion}"/>
        
        <map:generate src="cocoon://_plugins/{plugin}/{contentType}.{../1}"/>
        <map:serialize type="xml"/>
    </map:act>
</map:match>

      If "_content.pdf" is called to generate a PDF version of the content, this pipeline is still serialized in XML...
      The pipeline should be reverted to a "map:redirect-to" instead of generate/serialize calls.
      This bug applies to the versioned "_content/v_**.*" pipeline as well.

          [CMS-2375] Content export/rendering pipeline in the CMS workspace can't handle binary formats

          Nicolas Gavalda (Inactive) made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Cédric Damioli made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Raphaël Franchet made changes -
          Assignee New: Cédric Damioli [ cedric ]
          Nicolas Gavalda (Inactive) made changes -
          Description Original: The content export/rendering pipelines (versioned and not versioned) in the CMS workspace can't handle binary formats:
          {code:xml|title=workspace.xml}
          <map:match pattern="_content.*">
              <map:act type="get-content">
                  <map:parameter name="id" value="{request-param:contentId}"/>
                  <map:parameter name="contentVersion" value="{request-param:contentVersion}"/>
                  
                  <map:generate src="cocoon://_plugins/{plugin}/{contentType}.{../1}"/>
                  <map:serialize type="xml"/>
              </map:act>
          </map:match>
          {code}

          If "_content.pdf" is called to generate a PDF version of the content, this pipeline is still serialized in XML...
          The pipeline should be reverted to a "map:redirect-to" instead of generate/serialize calls.
          This bug applies to the versioned "\_content/v\_**.*" pipeline as well.
          		New: The content export/rendering pipelines (versioned and not versioned) in the CMS workspace can't handle binary formats:
          {code:xml|title=workspace.xml}
          <map:match pattern="_content.*">
              <map:act type="get-content">
                  <map:parameter name="id" value="{request-param:contentId}"/>
                  <map:parameter name="contentVersion" value="{request-param:contentVersion}"/>
                  
                  <map:generate src="cocoon://_plugins/{plugin}/{contentType}.{../1}"/>
                  <map:serialize type="xml"/>
              </map:act>
          </map:match>
          {code}

          If "_content.pdf" is called to generate a PDF version of the content, this pipeline is still serialized in XML...
          The pipeline should be reverted to a "map:redirect-to" instead of generate/serialize calls.
          This bug applies to the versioned "\_content/v\_\*\*.*" pipeline as well.
          Nicolas Gavalda (Inactive) made changes -
          Description Original: The content export/rendering pipelines (versioned and not versioned) in the CMS workspace can't handle binary formats:
          {code:xml|title=workspace.xml}
          <map:match pattern="_content.*">
              <map:act type="get-content">
                  <map:parameter name="id" value="{request-param:contentId}"/>
                  <map:parameter name="contentVersion" value="{request-param:contentVersion}"/>
                  
                  <map:generate src="cocoon://_plugins/{plugin}/{contentType}.{../1}"/>
                  <map:serialize type="xml"/>
              </map:act>
          </map:match>
          {code}

          If "_content.pdf" is called to generate a PDF version of the content, this pipeline is still serialized in XML...
          The pipeline should be reverted to a "map:redirect-to" instead of generate/serialize calls.
          This bug applies to the "_content/v_**.*" pipeline as well.
          		New: The content export/rendering pipelines (versioned and not versioned) in the CMS workspace can't handle binary formats:
          {code:xml|title=workspace.xml}
          <map:match pattern="_content.*">
              <map:act type="get-content">
                  <map:parameter name="id" value="{request-param:contentId}"/>
                  <map:parameter name="contentVersion" value="{request-param:contentVersion}"/>
                  
                  <map:generate src="cocoon://_plugins/{plugin}/{contentType}.{../1}"/>
                  <map:serialize type="xml"/>
              </map:act>
          </map:match>
          {code}

          If "_content.pdf" is called to generate a PDF version of the content, this pipeline is still serialized in XML...
          The pipeline should be reverted to a "map:redirect-to" instead of generate/serialize calls.
          This bug applies to the versioned "\_content/v\_**.*" pipeline as well.
          Nicolas Gavalda (Inactive) created issue -

            cedric Cédric Damioli
            ngavalda Nicolas Gavalda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: