Web Viewer or questions!

Similar Questions

• Creating a Web Viewer only question

  Then, I got to step 4 in these instructions.

  /helpx.Adobe.com/Digital-Publishing-Suite/help/creating-Web-Viewer-only-rendition.html

  Step 5 now says building that allows an application with social sharing and test rendering Web Viewer.

  What this means enter the DPS App BUilder and the same steps as the app for submission to Apple of construction?

  Will it all certificates etc. ?

  Someone there done of one of them and can give me more details?

  Dave

  Yes, it's exactly what you would do.

  Neil

• limitations of the web viewer (unanswered question - 1 week later... come on adobe)

  with reference to this article:

  "That an iframe the instance of the library is supported (you must have a web browser open on your page)."

  I try to publish a number of guides as an iframe on Surf Life site, one which is here:

  http://www.surfinglife.com.au/guides/travel-Bible-2014

  
  the next guide will be the wetsuit guide 2014, it is expected that he would have a different URL, for example: http://www.surfinglife.com.au/guides/wetsuit-Bible-2014

  the above limitation would restrict me to be able to present it on this separate URL?

  Thank you

  C

  Hi C,

  I apologize for the delay. The restriction does not only having more than one iFrame which contentviewer.adobe.com of frames on the same page. Given that your situation is hosting an iFrame on two different pages, this is supported. I hope this helps.

  Thank you

  Christine

• Site Web Viewer question - buttons within WHO

  I have not seen this as a problem "known", but I think it could be a common. Buttons in multi-state objects are not displayed when you use the web viewer. It does not seem there are a lot of States or buttons that trigger the issue.

  The question as I was creating a custom menu in a section to browse the pages.

  Steps to reproduce the bug:

  1 create a multi-state 2-State on page 1 of a folio

  2 al ' State 1 or 2, create a button 'navto' to the next page of the current article.

  3 send page, publish account with 'sharing' is enabled.

  4. notice of publication with web viewer using the latest browsers Chrome and Safari for Mac.

  Results: MSO buttons not displayed on the latest browsers Chrome and Safari for Mac.

  Expected results: MSO on-screen buttons and function.

  Hello

  I am one of the engineers responsible for the Web Viewer. In the last days, we have provided an update to the Web Viewer that should solve the problem you describe.

  Could you please you try to display the article once again, see you if the problem has been resolved?

  If she was not, could you send the link to the article in a reply or send me a direct message, so we can diagnose what is happening?

  Thank you.

• Viewing and buying Desktop / Web Viewer Question.

  I understand that if you share your free content via your iOS app it can be viewed in a browser (with a few features missing like hitting swiping images.)

  My question is this...

  I have a business account... A person buy the magazine and finds the whole magazine through a desktop computer with the DPS Web Viewer? Or its just limited to free content on your web browser, but they must have an iPad to view all mag?  They get full access to the desktop so they buy.

  Thank you

  Ron

  For a professional customer, can be considered as free content that was shared on the web viewer/office. For customers of the company, content restricted access are accessible via the right using the SDK Web content viewer

• vCO Web view question

  Hello

  I'm trying to follow the following steps to create a simple vCO web view:

  https://pubs.VMware.com/vSphere-50/index.jsp#com.VMware.vSphere.vco_develop_web_views.doc_42/GUIDA1900774-b720-40A7-96FE...

  I was able to follow the steps successfully up to the following:

  https://pubs.VMware.com/vSphere-50/index.jsp#com.VMware.vSphere.vco_develop_web_views.doc_42/GUIDC56F8242-B1CD-4B54-A872-A8F567ED40D4_copy.html

  I was able to put the server in view of 'Web' development mode and stressed the display Web directory to ' / mnt/webviews / ", which is NFS mounted on a server, the service has restarted after doing this.

  When I go to the new web view, I'm just a page of detention saying: 'not defined default page.  The Web "Virtual Machine Manager" mode has no defined default page.  "A default page is a page that is at the root of the webview and named index.html or default.html.

  The default.html is currently sitting in the following ' / mnt/webviews/MyWebView / ', which should be in the right place... I think so.

  Has anyone encountered this problem?

  Thanks in advance.

  You need to check the permissions for the entire repertoire of Maye

  When you go on https://vco-ip:8281/vco/vmo /

  Do you see something? It should list your web pages display when it is published.

• Does not refresh Web Viewer

  Hello

  I've updated my folio and it works very well for the iPad, but the web viewer will not update. Why is this?

  The release of v29 introduced some bugs that affect you most likely. These issues should be resolved in the next day or two.

  l http://helpx.adobe.com/Digital-Publishing-Suite/Release-note/DPS-bug-fix-release-notes.htm

  Known issues with web viewer

  • Some executives scrollables in web viewer is no longer work correctly with the version v29. This is discussed.
  • Social sharing does not work for apps v27 and v28 for folios published after the release of v29.
  • Smooth Scrolling items in web viewer may not display correctly on the last page if the length of the article of smooth scrolling is not an exact multiple of the height of folio. For example, the last page of an article 1024 x 2000 may be cropped, but a 1024 x 1536 (2 times the height) or 1024 x 2304 (3 times the height) should display fine. The question is particularly common in portrait orientation.
  • More than 70 x 70 are to be cropped instead of TOC resized images.

• Web Viewer and editor of marketing (article Allen)

  My client publish folio free and retail, and we want to understand how to use the Web Viewer via links (url) or through more traditional campaign vehicles. He wants to send a message to Facebook/Twitter like this:

  We have published this publication ipad 'XXXXX '! Please get a glimpse of some article here (link to web viewer).

  And then buy it on iTunes Store!

  So I have a few questions:

  (1) folio free ipad are visible in the web viewer with no limitation (it's ok).

  (2) free folio - Viewer web only - which never launched an iPad app and use only the web viewer. (it's ok).

  (3) the problem is the folio of detail, try to think of this structure:

  Article 1 (free)

  Article 2 (free)

  Article 3 (free)

  Article 4 (aerosol)

  Article 5 (aerosol)

  Article 6 (protected)

  Article 7 (protected)

  Article 8 (protected)

  Article 9 (protected)

  Article 10 (protected)

  Article 11 (free)

  Links to article counter display on desktop content without any limitation.

  If a user with this link can see all the article (also protected)! Is it possible to use a limitation for desktop users?

  This article by Allen Ellison has not helped me:

  .. .but once a URL custom hosting is associated with a publication, all users who follow a link from web viewer will end up in your URL, if you want to validate that users of iOS...

  http://www.Adobe.com/devnet/digitalpublishingsuite/articles/embedded-Web-Viewer
  

  All the article here with no limitations!

  http://Adobe.LY/XlscZ0

  http://bit.LY/1dDtgpY

  In a folio detail (as you describe in #3), users who click or press the link can see all folios free and none of the folios protected (unless they have right). They will be able to view the items counter, but only until they reach the threshold that specifies the editor. After that, the rest of the items are protected by a paywall.

  This applies to both built-in web viewers. However, with a web viewer integrated, you can give right to users to connect and consult the content that they have right to.

  That answer your question? I'm not sure of what got...

• Web Viewer: Best practices and Limitations

  The opportunity to share our publication online via a web viewer is an asset to have. However, I noticed some blockages in two folios, we have made available online: videos suddenly stop playing; slow scrolling pages are not completely accessible to see; interactivity does not work in different browsers. I wonder if there is any documentation or advice to ensure a smoother experience across all display options.

  Hello

  Thanks for the additional details. We look at the issues you reported and have a few comments.

  Here are a few quick notes for each of the elements.

  -Video suddenly stop playing.

  We had a new web viewer updated today, and this seems to have solved the problem with the video stopping on this article.

  http://ContentViewer.Adobe.com/s/Airman%20Magazine/c31b3f6bf51348f280a8bf8e57d33ee4/2013-0 6/7%20SUMMITS%20SIDEBAR.html

  In this article, there is a play button placed inside the OSM. ASM has been put to play as a slide show and the loop. It was originally an interaction with the video that caused it close. We have made some changes to the way video MSOs interact in this latest version, and that avoids this problem.

  Yet, in this case, apparently not necessary to use the DSO or even a button. For videos full screen like this, you can simply create the video overlay on the image of the button. With videos full screen, the area of overlay that you define behaves like a button "play" without you having to add explicitly one.

  -Scroll effect slow pages are not completely accessible for display

  We have also looked at this article and are able to reproduce the problem. As we develop a solution, we will work to get to a workaround to help you avoid this problem. We'll post here when we have some suggestions for you.

  -Interactivity does not work properly in different browsers

  We have experienced some problems with certain types of content in Internet Explorer. We are working on some improvements to help reduce these.

  I will address the two items that you referenced separately.

  -Multi-state objects does not properly

  There are some limitations with IE when it comes to the way it handles the interaction events. In this case, the layout of the content can be slightly adjusted to avoid this problem. I noticed that the positioning of several ESM is a little bit off.

  For example, the "VISUALS4" MSO is supposed to appear on the fourth page (index of the #3 page). However, if you look carefully at the InDesign file, you will see at the top of the OSM superimposed on the previous page of two pixels. As layering begins on the previous page, this is how it is rendered. Most modern browsers can handle this correctly, but it affects the stacking order in a way that causes a problem with IE.

  If you move all WHO the problem a few pixels to make sure that the upper part of the WHO is aligned with the top of the page, it should work properly in Internet Explorer.

  -Overlay of the play button has somehow to only changed the blue outline

  In reviewing the file folio for the article, it shows that the two States for the MSO play button use the same image.

  http://CDN-ContentViewer.Adobe.com/v/88e59469-94d0-4D3B-95cb-595c7d3a7944/7%20SUMMITS%20SI DEBAR/1/OverlayResources/InDesign_BNDLR_RSRC29936-633919858/Multi-state%2010_State%202_205 11_Content_L.png

  I don't know what the behavior planned for this MSO. It is configured as a slide-show mode that loops between the two States, once it is clicked. Because the OSM will be covered by the video full screen, which is the desired effect? Please explain what you want to achieve and we can provide suggestions.

  -No support for overlays

  On some browsers, including some versions of Internet Explorer, we support all interactive overlays. The screenshot you posted seems to be an overlay of imageSequence. This special overlay is not supported on some versions of Internet Explorer.

  Please let us know if you have any other questions or encounter other problems. We will do our utmost to help.

  Thank you

  JC Camargo

  Computer scientist, Adobe Digital Publishing Suite

• Web Viewer and folio portrait and landscape

  Hello

  two questions:

  (1) how to share only the orientation portrait a Folio? or landscape?

  Our magazines have everything from portrait and a page on the landscape. When the user share an article, the web viewer must first show portrait orientation. It is now always showing the landscape.

  (2) how to make navigation between folios (items) in orientation portrait?

  After turn to portrait and navigate to the following folio, it changes to the new landscape.

  Thank you.

  Question 1: The web viewer has enough simple rules for what to show. If the shared item is available in portrait mode and landscape, landscape by default and allow the player to change to portrait by clicking the direction control in the lower left corner of the footer. If the shared item is available in one orientation, which is that of the web viewer displays. We display the default landscape because the proportions of the fashion landscape is the "best fit" for almost all instructors (who are also in landscape mode). It is not possible at this time to specify the orientation of the content when it is shared, that determined when it is displayed.

  Question 2: Currently, we do not offer the ability to override the default values, as described above. There is a feature that we have on our 'to do' for the future I hope not too far away that would allow you (the Publisher) to specify what web orientation viewer should use for each folio by default, effectively replacing the current behavior of landscape first list. If you specify ' default viewer web site: portrait ", then the web viewer should always be first portrait mode (when both are available) for each item in this folio.

• DPS Web Viewer

  I have a question about the patch v27.

  Posted in the section new whats: ' in the web viewer, items that have a status of access set to 'Free' in producer Folio article can now be found in the office web viewer without counting against the threshold paywall. "does that mean that as long as an article is set to release, us will be not charged for viewing this article?

  can someone explain this in terms laymans.

  Thank you.

  
  

  He comes to the paywall threshold that the Publisher puts up for their customers, not downloading account that cool Adobe of publishers.

  Publishers can use the producer of Folio to set free articles, aerosol or protected. In the tool Admin account, they can set a threshold to limit the dose items that each customer can view in the web viewer. For example, if the threshold is set to 3, the customer can see 3 items Doss and crew to the fourth section counter displays a message paywall. In v26, inhalers and free items charged on the threshold. In v27, only equipped meter items count against her.

• Future plans for the App Web View

  I'd like say the new view of web get you sharing a folio is exciting. Question: What are the future hope or that he plans for this feature. SE Navto: / / buttons and overlays be fully supported?

  Thank you.

  The Web Viewer supports all overlays in the latest browsers (Chrome, Firefox, Safari, IE9, IE10) with the exception of the Panorama. There is also a limited overlay support in IE8 (hyperlink, 360 view, button, image)

  Kristy

• All items not protected from the Web Viewer

  Hello together,

  We use the Web Viewer for marketing stuff and send us an E-Mail with the link to the articles very often. The problem is: there are about 15 unprotected articles, only a few are displayed in the browser. Once the message appears: "Please buy this question!" - Although the article is not protected. Is it possible to display all items not covered in the Web Viewer?

  Thank you

  You can set a lower limit of Paywall threshold in your account application in respect of the Administration of the accounts. You can increase the Paywall threshold to allow all items not covered in the web viewer.

  You can also check this link for more information: http://www.adobe.com/devnet/digitalpublishingsuite/articles/integrated-social-sharing-with-num digital edition - suite.html

• problem with multiple digital signatures by deactivating the fast web view

  Hello, I use acrobat pro 9.1 and have questions regarding a problem with several signatures on a pdf document.

  Why I ask the question below? My job is to prepare PDFs for submission to the FDA. The FDA requires, among other things, the documents submitted electronically have quick view active web.

  I am currently exploring ways to use digital signatures to sign pdf reports and always make sure they are spec FDA compliant. My question concerns a document which would have several signature fields. What I do, it is to create at least two signature fields in the doc and then save and optimize everything for fast web viewing. When I connect the first box and save, the file retains the fast web view state. Yet, when I apply and signatures past one, the file is then left for quick web display with no obvious way to turn it back on. I'm confused as to why it gets disabled after the second, and not just after even the first condition has been signed. And, of course, I would like to know if it is possible to maintain the fast web view and how to do it. I will gladly accept "tinker under the hood' suggestions file if they exist as well.

  Please let me know if something is not clear or you would like more information.

  Thanks for your time and your help.

  ~ Vlad
  

  Hi Vlad,

  Real Michael has got the right answer. A "Linearized" file (which is a file that has been optimized for fast Web view) aims to get the first page to display as soon as possible so that you can start playing without waiting for the rest of the file to download. Incidentally, the first designated page should not necessarily be page 0 (use of PDF has zero according to the pages counting system), but it usually is. The PDF specification, "the main objective of linearized PDF is optimized PDF documents viewing read-only. It is expected that the linearized PDF generated once and read many times. Incremental update is still permitted, but the PDF is is more linear and subsequently is treated as ordinary PDF. »

  When you open a PDF file the first time that the backup process is a full 'save', it is the whole document is rewritten, so there is no more than two percent markers EOF (end-of-file) inside. The first expressions of folklore means what page to see the first and the second EOF designates the end of the rest of the file (so the browser knows when to stop downloading). However, when you add a second signature (or even longer) the file is saved as a "record growth" and new data is appended to the original file. It is that you can do a restore to the previous signed version and allows Acrobat/Reader verify the integrity of each signature regardless of any other signatures. It's the incremental save, breaking the linear optimization of the file.

  Steve

• Link Hypertext & Web view

  In the new InDesign 5.5, the link Hypertext & Web view only seem to be able to work in the Overlay of the Creator window Preview / Panel.

  But when I saw it by Folio Builder and the iPad, both of this interactive overlay does not work.

  The rest of the features like Pan, Video etc all works well.

  Can someone please?

  Thank you!

  OK, I was able to recreate the problem with hyperlinks and I went ahead and submitted a bug report to Adobe.  The key question, however, I wasn't able to recreate.  Check a few things and let me know if it fixes the problem.

  With your button, make sure that you have "navto://articlename" make sure that the name of the article is the same way, it appears in the Panel (which must match the name of acrobat.com) so not 'articlename_h' or 'articlename_folio' or something like that.  Update section of the folio builder Panel... and preview the FOLIO group level.  If she does not have article you made navto it will not work.

  Let me know if it helps