Allow publishing of non-xml pages

Favorite-off Notification-off
15 Thumb-up Thumb-down
Idea by chris.armistead about 1 year ago Favorite-off - Open
Cascade users would like the ability to publish non-xml pages.

8 comments

  • 2 points Thumb-up Thumb-down Favorite-off by slota.benoit about 1 year ago Permalink
    Yes, it could be great to be able to generate and publish plain text page (Ex : .password, .properties, .csv, ...)
  • 0 points Thumb-up Thumb-down Favorite-off by jraller 10 months ago Permalink
    Add to the list .htaccess and .css files. Particularly if .css files can be generated from a page and utilized by other pages.
  • 1 point Thumb-up Thumb-down Favorite-off by irifkin 10 months ago Permalink

    Regarding .htaccess files, if you like hacky work-arounds, you could create a template and put in it something like:


    <Files> <system-region name="DEFAULT"/> </Files>


    The above is valid XML. But then in the page have it output something like:


    <!--#START-ROOT-CODE Redirect 301 / http://www.brandeis.edu #END-ROOT-CODE-->

    Because the .htaccess directives are within that start-root-code tag it should appear above the block so the published output would be:


    Redirect 301 / http://www.brandeis.edu <Files> </Files>

    I haven’t tested this thoroughly, but I think it should work.

  • 0 points Thumb-up Thumb-down Favorite-off by Megg@VC 9 months ago Permalink
    We do .htaccess as a file, not a page.  But when we edit we have to change the file to end in .txt, save, then edit again, rename it back to .htacess.  If we don't change the name it only allows us to upload a replacement.  Would be nice to simply hit edit and get the content in the text box (like it does when named .txt)
    • 0 points Thumb-up Thumb-down Favorite-off by irifkin 9 months ago Permalink
      Megg,

      There's a setting in Cascade for that! In the content preferences make sure .htaccess is listed as both a "Editable File Extensions" and a "Plain Text File Extensions."

      Ian
    • 0 points Thumb-up Thumb-down Favorite-off by jraller 9 months ago Permalink
      I believe if you change the "Editable File Extensions" under "Preferences|Content" you can edit the file in the system. The reason to treat it as a page instead of a file is that you can generate the content using xsl, which would prevent or reduce the need to edit it by hand.
  • 0 points Thumb-up Thumb-down Favorite-off by jraller 8 months ago Permalink
    Another file type that this change would make possible is .iCal.
  • 1 point Thumb-up Thumb-down Favorite-off by jraller 7 months ago Permalink
    An alternative that would preserve the "purity" of page output would be to allow a new asset type: the dynamic file. A Dynamic file would have one region to which a single block/format could be applied. Output would be allowed to be of any type. This would expand the options beyond pages, which should be standards compliant from files which aren't dynamic (other than link rewriting).
    Dynamic files should be able to be consumed by pages (if they are .css files for instance).

No attachments


* Note - To input code samples, click the pencil icon (this will remove the WYSIWYG) then be sure to start and end code sections with @@@ (three '@' signs).  For more information on textile markup, click here.  

Sign in

Follow us on Twitter

Current Category