Skip navigation
Currently Being Moderated

Web content

Sep 22, 2011 3:01 AM

Does it make sense that loading a very simple, small HTML file (4kb) via Overlay Creator's Web Content would turn an article upload that happens in seconds into a 105mb mini-monster that takes minutes to upload?

 

John

 
Replies
  • Currently Being Moderated
    Sep 22, 2011 10:11 AM   in reply to john beardsworth

    Well, a simple html  file (one liner with a <video> tag)  ended up with a 350 MB file for me. So that's 400 kB without the html oneliner, and 350 MB with. The video was supposed to be retrieved online, but it looks like it is embedded (though it still requires an Internet connexion to work).

    Could it be that html inclusion fills the folios with cache?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 22, 2011 12:46 PM   in reply to john beardsworth

    really? DPS is carrying around this bug since prerelease. Hope they can get

    around this soon.

     

    —Johannes

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 22, 2011 1:11 PM   in reply to john beardsworth

    I don't think this is a "known" (as in "acknowledged") bug. I just

    encountered this behaviour in prerelease and just hoped they fixed this in

    some of the many versions after that.

    I think it is hard to identify all the assets an HTML file needs (because of

    some lazy load techniques and indirect refers, such as @import), so they

    just pust all the content lying around the HTML file into the folio.

    I always put HTML in a separate folder (just to keep myself organized) and

    so came around this behaviour.

     

    —Johannes

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 22, 2011 1:49 PM   in reply to john beardsworth

    good point with that folder-pointer.

     

    —Johannes

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2011 2:51 AM   in reply to john beardsworth

    We just ran into exactly this problem. We found about 95Mb of useless-to-the-user InDesign files, tiffs, PSDs, whatevers, buried in the commercial App! But only on pages where the HTML was sat next to the InDesign file.

     

    There are both file size and IP issues here, which we could really do without.

     

    Thanks for the tip about putting the HTML in a separate folder - we'll deploy this for our update.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2011 2:05 PM   in reply to john beardsworth

    what are IP risks?

     

    —Johannes

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 27, 2011 2:27 AM   in reply to Johannes Eckert

    IP, as in Intellectual Property - copyright protected stuff.

     

    If it sweeps up everything sat next to the HTML file, you could inadvertently distribute a bunch of Jpegs from picture library that happened to be in that folder.

     

    I appreciate they'd be packaged up in the App, so most users would be blissfully unaware, but it only took me 2 mins to discover how to get to them.

     

    Bob

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points