You could achieve this with HTML localStorage. Here's an example:In
article A with the navto link to article B: Click
me function navtoHandler(strNavToUrl, strCustomParam) { //
sets the parameter for "param1" in HTML localStorage
localStorage.setItem('param1', strCustomParam); // redirect the window
using the navto window.location.href = 'navto://' + strNavToUrl; }
In article B (with article name 'xxarticlenamexx'): // wait
until the DOM is ready $(document).ready(function() { // makes sure that
the code is loaded everytime and not cached in iOS window.onAppear =
function() { if (localStorage.getItem('param1') === null ||
localStorage.getItem('param1') === '') { // the "param1" is empty,
should ignore } else { // there is a value for "pa...
The publicationID is the ID for a DPS 2015 project. You can find this in
the browser URL when you navigate to the Content & Layouts section of
the DPS 2015 portal and select the project that you wanted. The
screenshot below the example that you mentioned in that help article
illustrates this.- Mike
Confirmed with the engineers that Android doesn't have an embedded PDF
viewing capability, like iOS. So you will have to open it externally by
using window.open() or linking to it like you did with the button. This
script should work for both cases:setTimeout(function() { var pdfFile =
"path/to/file.pdf"; if(navigator.userAgent.match(/Android/i)) {
window.open(pdfFile); } else { window.document.location.href = pdfFile;
}}, 100);You can also use window.open() for iOS, but the experience will
be d...
Hi,You can try delaying the script to open the PDF with setTimeout (in
milliseconds):setTimeout(function() { window.document.location.href =
"path/to/pdf";}, 100);- Mike
Hi,By uploading, did you mean creating the article entity or uploading
the .article content to the article entity or both?If creating article
entity, as jerwarren mentioned, the articleName is unique. If attempting
to create an article entity with the same articleName, then it will fail
and you'll have to check the response code for a HTTP 409 (see
getResponse()). The script will not force quit from this error because
it has other uses, such as a trigger to switch to an entity update.The
ingesti...
Hi,dps2015sdk\contentService\Collection::addEntity() requires an entity
HREF, please try replacing your line #4 with the
following:$collObj->addEntity($articleObj->getHref());Please let me know
if this doesn't solve the issue.Best,Mike
Hi,The issue list URL that you were referring to is for DPS (Classic),
please refer to the following article on how to generate the similar
issue list for DPS 2015:Digital Publishing Solution Help | Use the
Content Producer Service API to access collection and product
detailsBest,Mike
Hi,I am assuming that you tried double clicking on the HTML Article
Packager icon. It is not "crashing", it is expecting HTML article
contents. You can simply drag and drop the HTML article contents into
the HTML Article Packager icon and it will automatically generate the
.article files relative to the same directory as the HTML article
contents.Please refer to this article for more info: Create HTML
articles for DPS 2015- Mike
The WordPress plugin that you are using will only work with DPS 2015.
You can migrate your DPS (Classic) contents over to DPS 2015 easily
using the Folio Migration Tool (see this for more info) and continue the
test with that WordPress plugin.- Mike
Hi,The socialSharing image URL is part of the entity metadata, in the
field "socialShareUrl":// sample code$objArticleEntity = new
Article($arrCredentials, $arrParameters,
$arrEndpoints);$arrArticleMetadata =
$objArticleEntity->getMetadata()->getResponse();$strSocialSharingUrl =
$arrArticleMetadata['socialSharingUrl'];The thumbnail image URL can be
generated by using the
following:https://pecs.publish.adobe.io/publication/{{publication-id}}/{{entity-type}}/{{entity-name}}/contents;contentVersion...
Hi,Please make sure that there aren't any file with 0byte size within
the .article zip file. Even if the .article zip file that you uploaded
is 54kb, the contain of the zip file may contain 0byte size files. -
Mike
Hi,Please update the line that you pointed out (file
/class/sharedEntity.php line #70) to as follows:$headers =
$this->_setHeaders($this->mimetypes['json'], null,
$this->parameters['client_upload_id']);Also, in the demo script (file
/sharedContent/create_shared_entity.php starting line #49), please make
sure that it matches the following:// request & store the latest content
URL$sharedContentObj->getMetadata()->printCurlData();// request for the
sharedContent
manifest$sharedContentObj->getManife...
While we wait, you can also tackle this using the DPS 2015 Content
Producer Service APIs.Here's a recipe structure for this:load the XML
file into memorySet the necessary credentialsSet the project Id and
collection entity name (not title)Request for the list of content
elements within the specified collection (step 3)Iterate through the
list of content elements and update each entity metadata with the data
from the XML file (step 1)Please note that the content element will
reference an entity, ...
Hi,An update to the WordPress plugin was just released recently, you are
now able to select from the list of projects that is displayed after
entering the device Id and device token, see v2.0.3.
Hi,Someone already reported this bug (see list of bugs here) and Studio
Mercury is working on a fix for this issue, where the article thumbnail
or article content (or both) failed to be uploaded to DPS
2015.Currently, the WordPress plugin will only manage articles.- Mike
Hi,The current version of the plugin does not support this feature. The
workaround is to have the Adobe Id, used to generate the device Id and
device token, to be only added to a single project.Please note that, for
best practice and security reasons, you should not use the Adobe Id that
is the master account to generate the device Id and device token. - Mike
Hi,The PHP examples you're referring to are to be run by itself, either
via an apache server (i.e. MAMP for localhost or real web server) with
PHP or terminal. There is a README.md file in the PHP examples, along
with another README.md in the /demo/ folder, where it will contain steps
to create/upload/update content and add to a collection.The Wordpress
and Drupal plugin have their own coding framework and style, so you
can't copy and paste from one to another.- Mike
Hi,Currently there aren't any predefined templates, but you can check
the WORING WITH TEMPLATES section of the Wordpress plugin page to create
your own templates: Digital Publishing Tools for Wordpress- Mike
Hi,Did you select to upload the thumbnail image (in article > Properties
> Images and then article > Cloud > Upload Content) and the .article
file (in article > Cloud > Update Article Folio)?When you first select
Cloud > Create in the Cloud, this will only create the article entity.
You will have to upload the thumbnail image and .article file by
selecting the options mentioned above.- Mike
Hi,Neil was referring to the DPS 2015 Content Producer Service API, the
same set of APIs that the DPS 2015 dashboard is using to interact with
your contents. You can refer to the following article on how to utilize
shared resources via the Content Producer Service
API:https://helpx.adobe.com/digital-publishing-solution/help/shared-content-api.htmlBest,Mike
Hi Haeme,That error isn't due to the plugin. The text you entered,
"Author URL", isn't a valid value for the metadata field Author URL, you
must enter an actual link to the author information or leave it as
blank.Best,Mike
The client secret should be within the DPS 2015 Content Producer API
request form. Please email me (mikey@adobe.com) your client ID and I'll
try to find the secret.
Hi,Did you enter the client ID and secret in the AEM instance? It is
located in AEM dashboard > Tools > Web Console > and search for Adobe
Digital Publishing Solution Client. Double-click on it and it'll ask for
the client ID and secret.
No, the issue with the other post was because of the request id (uuid)
generated by the WordPress plugin didn't match our JSON schemas. I have
followed up with Studio Mercury regarding that issue.
