Comments

3 comments

  • Avatar
    Nils Bier

    Hi Tim,

    thanks for the information.

    To further anylze the problem it would be great if you could send the following information to support@k15t.com:

    * A support-ZIP
       To create a support ZIP in Confluence, please follow these instructions: http://www.k15t.com/display/SUPPORT/Creating+a+Support+ZIP+File

    * A XML export of the space.
         To create a full XML export of a space, please follow these instructions: http://www.k15t.com/display/SUPPORT/Creating+a+XML+Export+of+a+Space

    * Your Scroll EclipseHelp Exporter template.

    We'll then be able to have a deeper look and will come back to you as soon as possible.

    Cheers,
    Nils

    0
    Comment actions Permalink
  • Avatar
    Tim Statler

    Hi Nils,

    Thanks for the reply, just getting back to looking at this now. We installed a trial version of the latest version of the EclipseHelp Exporter and it solves the issue with the TOCs. However, this version seems to handle attached images differently than the previous version we were on (2.x). Previously, each image was placed in a folder (e.g. "/images/attachments/xxxx/etc/image.png") but in this version (3.0.7) they are all now placed in the same root folder, and the "/"'s replaced with _'s (e.g. /images_attachments_xxxx_etc_image.png).

    I didn't see any options in the export setting dialog to control this behavior. Is there some other setting that let's us control image paths?

    thanks again,

    Tim

    0
    Comment actions Permalink
  • Avatar
    Nils Bier

    Hi Tim,

    thanks for the information. I'll copy Jens answer to this forum post and we'll further work on your problem in our support-system, if that's okay for you.

    Cheers,
    Nils

    _________

    Jens answer:

    Hi Tim,

    the new names are a side-effect of the filename sanitizing we've introduced in one of the recent releases.
    Does this break something on your side? The images should still display fine as the generated HTML files in the plugin file contain the updated paths to them.

    Currently image locations are not configurable (and probably won't be in the future).

    However if there is a valid reason why we should return to the old filenames we will consider that :-)

    Cheers,
    Jens

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk