Support
Troubleshooting

Troubleshooting: E-Paper not imported

4min

Purple Importer



Summary

If your e-paper hasn't been imported correctly, this page will give you all the troubleshooting options to get your import working via Purple Monitoring Server, Purple Manager and sFTP Server.

If you want us to help you investigating on the problem, you can always open a support ticket via the support helpdesk. We are happy to help!Please let us know in the ticket which troubleshooting steps you have already taken.



Preconditions

While troubleshooting, you should get familiar with


1

Troubleshooting in Purple Monitoring Server

To investigate possible reasons, why your e-paper was not imported successfully, you might find the first answer, when analysing your imported data via Purple Monitoring Server.

To do so, check the message in the column 'Status'

Status: IMPORTED

Status Imported in Monitoring Server


Troubleshooting: 'Pubdate'

Check in the column 'Publication date' in Monitoring Server, if the date is in the future.

--> Yes, the publication date is in the future:

  • The issue will not be displayed in the release app/web-kiosk until the release date is reached. The import process is not linked to the pubdate.
  • In preview apps/web-kiosk all issues are displayed regardless of the pubdate.

--> No, the publication date is NOT in the future:

  • If the displayed publication date is already reached, continue with the step 2 'Purple Manager' further down on this page.

Status: ERROR

Document image


Troubleshooting 're-import'

--> Click on the button 'Reimport selected' in the top bar in Monitoring Server to trigger a re-import of your issue.



If you already re-imported the content and the Status 'ERROR' still persists, continue with these steps:

Troubleshooting: 'Zipfile not compressed correctly'

Also, if you are importing a plain PDF (not an EPUB) as a Zip file, please ensure that the compression is correct. Simply changing the file extension is not sufficient.

--> Make sure, that the publication is spelled correctly: Go to the import CSV file and make sure, that the publication is written in exactly the same way as the Publication you created in your team in Purple Manager.

Document image

Name of the Publication in Purple Manager
Name of the Publication in Purple Manager


Troubleshooting 'The import CSV file does not match requirements'

--> Make sure Import CSV requirements are met: Check, if your Import CSV file matches the requirements listed here: Import CSV requirements

--> Make sure, that none of this common configuration mistakes was applied in your Import CSV file:

  • Have you used comma instead of semicolon? 
  • Was the Import CSV file not encoded with UTF-8? This can happen when Excel is used to create the CSV file.
  • Was a not supported date format chosen for the publication date? 

Troubleshooting 'The File (PDF or EPUB) does not meet requirements'

--> Make sure, that the PDF file is not broken and meets the Requirements for PDF imports

--> Make sure, that the EPUB file is not broken: Download the ePub file and try to open with Apple eBooks app. If it does not open, it is broken

--> Make sure, that the EPUB file meets the requirements: If you can download AND open the ePub file, validate that it meets the XML (EPUB) Specification

Status: PUBLICATION NOT FOUND

Troubleshooting: 'Publication not found'

It may be possible, that the publication mentioned in the import CSV file does not match the naming convention of the Publication created in the Purple Manager team. This could be caused by spelling mistakes or wrong upper and lower case letters.

2

Troubleshooting in Purple Manager

If you have checked your imported data in Purple Monitoring Server and the message in the column 'Status' was 'IMPORTED' it may be due to the following errors:

Troubleshooting 'Issue imported but not activated' 

--> Make sure, that the Issue has been activated for preview and release:

  1. Activate the Issue for release and or preview in Purple Manager
  2. Check the import parameter in the Import CSV file. If there is no parameter preventing the issue to be activated please create a Support Ticket

--> Make sure, that there no duplicated publication in Purple Manager:

It might be, that there is a second publication with the exact same name in your Purple Manager team. If this is the case, rename or delete the "wrong" publication. 

3

Troubleshooting in sFTP server

Troubleshooting 'File not delivered to sFTP'

--> Make sure, if the issue with the exact filename (.pdf/.zip) can be found:

  • Look for your file in the 'Upload' folder
  • Look for your file in the 'Archive' folder

If your file can't be found in one of both folders, it wasn't delivered on sFTP

If you can find the file it was delivered on SFTP. If it was anyways not imported, check if the name of the output matches with the Import CSV file:

  • Are there any spelling errors?
  • Does the ending of the files not match, e.g .PDF instead of .ZIP?

Troubleshooting 'File name does not match CSV'

This implies that you have written the wrong file name in the CSV. If this is the case, please correct the mentioned file name to e.g. PDF or ZIP. 

Troubleshooting 'The File (PDF or EPUB) does not meet requirements'

If the File was delivered and the CSV file is correct:

--> Make sure, if the PDF file isn't broken or does meet requirements: This can lead to an import error.

  1. Download the PDF file which you uploaded in the sFTP Server and open it with Acrobat, to see if there is something obvious. 

--> Make sure, if the EPUB File isn't broken (in case you use Readmode):

  • Download the file and try to open with the Apple eBooks app. If it does not open, it is broken.

If the EPUB file can be opened:

--> Make sure, if your ePub file meets the requirements: Check for the XML (EPUB) Specification

Troubleshooting 'Multiple CSVs with the same content in the same folder'

If you have one or more CSV files stored in a folder that reference the same data, the import process will not start. Certain combinations of entries should not be referenced in multiple CSV files or entries.

--> Make sure you haven't store or more CSV files stored in a folder that reference the same:

  • Issue Name
  • Publication Date
  • Publication (in combination with the above two)

To solve the problem, move one of the CSV files in the sFTP Server to a subfolder and place the associated files there. This ensures that the imported data is unique and prevents conflicts.

Troubleshooting 'The issue name referenced exists in several CSVs or entries'

Ideally, an issue name should not be referenced in several entries or in several CSV files. 

--> Make sure, to have run the import via one single CSV and entry: If you import several versions of an issue, e.g. an evening edition with a different file name but the same issue name this can also lead to errors.