Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi clubeddie,

    let me try to explain this in english. An ePaper is hosted at our webserver. The URL to the ePaper is a static point of entry. If you upload a new ePaper the data at the server will be updated but the channel URL will remain the same. Thats what you have to know at first.

    The behavoir you′ve reported is caused by Facebooks cache policy. If you share an ePaper on facebook, the static URL of your ePaper channel is used. This URL an the appendant data are stored by Facebook. Stored once, Facebook will not refresh this data very often. Thats why older informations are diplayed, even you created a new ePaper in your wp.

    You can force Facebook to refresh the data. Just open this link… ->

    https://developers.facebook.com/tools/debug/

    … and paste your channel URL into the inputfield. But even you do this, it can take several hours, til the data truly updated by facebook. Please let me know, if this was helpflul for you.

    bless

    In fact we cleaned the server last week, the servers database was not refreshed automatically. Checking this today, we found serveral ePaper still having a do_publishing state. Thats the exact reason why a few users couldn′t create new ePaper with their apikeys. So ALL apikeys work atm. We′ll implement a new cronjob on the server in the next few days, so that this problem hopefully is permanently eradicated in future. Please note that files you use should keep the standard PDF A – 1b still.

    bless

    Hi kutchuday,

    Please send me the email adress you′ve registered the plugin with and the text of your last post to [email protected]. So i can have a closer look. Thanx

    Please note, also we detected that one of our servers was under heavy load during last weekend. We fixed this yesterday in the evening 6 p.m. CET. So there shouldn′t be any problems atm..

    Kind regards

    Hi @ all,

    Please ignore the post before, sometimes strange things happens when using short cuts. So i just installed a brand new wp on my local machine, downloaded the actual 1000° plugin and created a new ePaper. It works without any problems. So in most cases the error you get are issued by the pdf file you use. Please make sure your pdf observe our standard. We highly recommend keeping the PDF/A-1b standard.

    1. Make sure the pdf is not protected by password.

    2. Make sure the pdf file only contains only of single pages keeping the same format.

    3. Make sure the colour mode is set to rgb.

    4. Don′t use transparency or colour gradient on single layer. Bring them in line with the according pictures or objects. Keep the layer hierarchy as flat as possible.

    5. Don′t use complex vector graphics in your document. Raster vector graphics before you upload the file.

    6. All fonts must be embedded. Thats why we highly recommend only the usage of truetype fonts, cause most a opentype fonts can′t be embedded
    properly.

    7.Last but not least, make sure your pdf is not oversized.

    Specially take care of point 4. and 6. Transparency and vector graphics are known as top sources of error. As the case may be, it could be your browser settings or plugins interfering the upload also. So if you get a error message like reported, please try the upload with a different browser. Firefox, Chrome and Safari are welcome.

    Hi karste [email protected]

Viewing 6 replies - 1 through 6 (of 6 total)