Adobe Community: Content generation error - version string does not have the right format

Currently Being Moderated

1. Bob Levine,

Jun 26, 2012 4:38 PM in reply to Angusdog

Report

Can we see a screenshot of the folder structure?

Bob

|

Mark as:

Currently Being Moderated

2. Angusdog,

Jun 26, 2012 5:07 PM in reply to Bob Levine

Report

Hi Bob,

Sure - above image shows 'root' folder and also the image folder within that.

Thanks,

Simon.

|

Mark as:

Currently Being Moderated

3. Bob Levine,

Jun 26, 2012 5:39 PM in reply to Angusdog

Report

Is that file in the root of the libraries? You need to treat it the same way as the InDesign files.

Bob

|

Mark as:

Currently Being Moderated

4. Angusdog,

Jun 26, 2012 5:59 PM in reply to Bob Levine

Report

Hi Bob,

Yes, I have separate folders for each article, all within one enclosing folder.

The HTML article is one of about 20.

Perhaps I need to recrate the folder... I'll try that in the meantime.

Thanks Bob,

Simon.

|

Mark as:

Currently Being Moderated

5. Angusdog,

Jun 26, 2012 6:03 PM in reply to Angusdog

Report

I copied the files into another folder (the old one has previously had an .indd file in it, so was wondering if it had a reference to that file).

The HTML file is HTML5; could that cause it to fail? The Folio Builder panel goes nowhere, just pauses then generates the error.

COuld it be down to the v21 build? Other 'plain vanilla' .indd articles continue to upload fine.

|

Mark as:

3,433 posts
May 29, 2007

Currently Being Moderated

6. Bob Bringhurst,

Jun 27, 2012 8:20 AM in reply to Angusdog

Report

Here's an article on importing HTML articles:

http://help.adobe.com/en_US/digitalpubsuite/using/WS67cb9e293e2f1f6053 0cf39c12f5fcd6d46-8000.html

|

Mark as:

Currently Being Moderated

7. akecj,

Jun 27, 2012 3:55 PM in reply to Bob Bringhurst

Report

I have now encountered the same issue and fail to resolve it.

After having tried every possible combination of folder structures (assets in local subdirectory, same root and moving everything into HTMLResources), trying various flavours of html (5, 4s, 4t) and turning my nose 90 degrees east while pressing "import"... the error persists.

I am pretty sure that this has absolutely nothing to do with the content or structure of my HTML article. Heck, even a completely vanilla HTML file (valid of course) with a single line of text in the body and no styles, assets whatsoever: fails.

It does work when importing it to a completely new folio though.

Can someone please confirm that she/he is still able to import HTML articles to preexisting folio, after the latest folio builder panel update?

|

Mark as:

Currently Being Moderated

8. akecj,

Jun 27, 2012 5:08 PM in reply to akecj

Report

The reason for this issue seems to be simple and is indeed connected to the last update.

For each folio project, you can now set a viewer version in the folio properties.

Folios created prior to the update, have this set to "undefined".

Set it to v20/v21 = problem solved.

edit:

I think a problem of this scale should not have made it to retail and the error message points to sloppy QA as well. The value being undefined is not a format mismatch. Assuming the above can be confirmed by others, of course.

|

Mark as:

Currently Being Moderated

9. Angusdog,

Jun 27, 2012 6:06 PM in reply to akecj

Report

Thanks Akecj - perfect! Changed my settings on the folio (Was unspecified, now v20 just in case) and works a treat. The problem was not with the way I publishing the HTML or the formatting I used.

The joys of emerging technology!

|

Mark as:

3,433 posts
May 29, 2007

Currently Being Moderated

10. Bob Bringhurst,

Digital Publishing Suite

Content generation error - version string does not have the right format

Jun 26, 2012 4:14 PM

More Like This

Bookmarked By (1)

Answers + Points = Status