Closed jeffreyflores closed 8 years ago
+1, having the exact same problem
Hi @jeffreyflores, @josedesousa-tcc,
This fix didn't make it in 2.0.10 that we released tonight, however it is coming in the next release which will be a big one.
More soon!
Happy New Year all!
Just wondering if there was any news on the next big release. Would love to see this issue resolved.
Hi José! Happy New Year to you as well! Our team is working on updates to the plugin during Q1 of 2016. We hope to have a new release soon. Thank you!!
On Mon, Jan 4, 2016 at 10:12 AM, José De Sousa notifications@github.com wrote:
Happy New Year all!
Just wondering if there was any news on the next big release. Would love to see this issue resolved.
— Reply to this email directly or view it on GitHub https://github.com/StudioMercury/digital-publishing-tools-for-wordpress/issues/29#issuecomment-168702352 .
Sarah Capers MERCURY 1133 Broadway Suite 218 New York, NY 10010 310.663.2564 sarah@smny.us
Hey @StudioMercury,
Just wondering if there was any news on the next release?
Having the same problem if i want to update an articles content i have to delete it from Adobe Experience Mobile Manager and push it again through the plugin. or update meta data refresh page and then upload.
I know both of those a bit annoying so hoping for an update soon.
Update All will upload the HTML/CSS content, following refresh.
Update Article Folio hasn't worked for me at all. I always have to download, unzip, and upload the .article archive through the AEM GUI on initial upload. For subsequent uploads of the same article, Refresh > Update All always works.
Could there be a bug with the sidecar.xml and content directory in the export? Only the .article file should be uploaded.
edit: Was able to successfully use Update Article Folio after first choosing "Create in the Cloud" and then updating article folio without having edited properties or uploaded a thumbnail image. Using browser refresh seems to help with all content saved.
We've just released a major update to the plugin. This bug and other versioning bugs should be fixed in this new update. The plugin was pushing the images / metadata first then trying to upload the .article file after the version number had changed. Pushing .article files now work as expected.
When attempting to update article folio content after a change has been made to article, I always get an error on the DPS Content Producer side though the WP plugin tells me the upload has been successful.
To "remedy" this, I've needed to try to update my article's metadata, which gives me this error 100% of the time:
I then proceed to refresh my page as instructed, and at only that point, I can update article folio content with success.