WebGrabber Release Notes 2016 R1.0
This is the initial release for ActivePDF WebGrabber 2016 (Build 2016.1.0.17153). This release includes bug fixes and new features.
- Software Requirements
- Hardware Requirements
- New Features
- Bug Fixes
- Installation and Getting Started
- API Reference
Software Requirements
The following software is required to successfully use WebGrabber.
- Windows Server® 2008 (32- or 64-bit edition) OR
- Windows Server® 2008 R2 OR
- Windows Server® 2012 R2
- Microsoft® .NET Framework is required to use WebGrabber's .NET component
(.NET 3.5 for the API, .NET 4.0 for the service — if it is not detected, you will be given the option to install it.)
Note: For WebGrabber installations WG2016 R1 and higher, when using the Internet Explorer Engine we recommend using Internet Explorer 10 or higher.
Important! If using Windows Server 2012 or above, and using the Internet Explorer engine for conversions, follow the instructions in the Installation section of these release notes before installing WebGrabber.
Hardware Requirements
The minimum hardware requirements for WebGrabber are:
- 350 MB of RAM
- 175 MB of hard disk space (for application)
New Features
For more information, see the New Features topic in the online WebGrabber 2016 API Reference manual.
- Updated Native Engine
A major update to the Native Engine used to convert HTML to PDF improves the overall quality of output PDFs.
Bookmark and Link Support- Automatically generate bookmarks, and choose which HTML heading to use.
- Automatically generate links from href attributes in HTML "a" elements.
- New Look for Configuration Manager
Configuration Manager's layout is updated, and settings reorganized for a more user-friendly experience.
Other Enhancements:
For more information, see the New Calls topic in the online WebGrabber 2016 API Reference manual.
- The new FieldFont property allows you to select the encoding to use for text in form fields.
- The new SetScaleFactor method allows you to set custom height and width scaling for the page sizes in the output PDF.
- The SslProtocol property has two new choices for cipher protocols. In addition, WG supports TLS 1.1 and TLS 1.2 by default.
Note: In earlier releases, the default port number for COM was 90 or 58585. The default is now Port 52525.
The default for .NET has not been changed, it is still Port 57975.
Fixed Bugs
ID # | Description | Resolution |
340 | COM: Remote conversion using a large input string or a large file occasionally timed out. | General updates to the code base resolved this issue. |
2673 | If SetMargins is used, the PDF links converted from hyperlinks are misaligned in the output PDF. | General updates to the code base resolved this issue. |
3142 | Instead of being deleted during conversion, href links that pointed to destination anchors created links in the output PDF. These links pointed to the original HTML page. | Updates in the WebGrabber 2016 release to bookmarks and links resolved this issue. |
4392 | Internet Explorer engine: If the text in a header or footer includes an apostrophe, neither the header or footer printed. | The code was updated to handle apostrophes in footers. |
4831 | URL specific: A graph does not convert to PDF (using either engine). | General updates to the code base resolved this issue. |
10112 | When FitToPage is used with text-align: right, the text in the output PDF has extra spacing and the text was not fully right aligned. | Setting the new WriteTextFormat to 0 (Write the text to the output; one "text run" at a time.) solves this issue. |
10120 | File specific, Native Engine: WebGrabber closed unexpectedly without providing and error message when it attempted to process this script that referenced an unsupported SSL protocol. | Changes to code relating to how URL addresses are handled resolved this issue. |
10135 | File specific: When FitToPage is set to True, the last word of a line breaks to a new line. | General updates to the code base resolved this issue. |
10241 | When the source page that includes an HTML5 inline SVG image is converted, the output PDF is missing the image. | General updates to the code base resolved this issue. |
10366 | Internet Explorer engine, Evaluation and Dev installations: When the PDFWidth and PDFHeight properties were set, the automated ActivePDF watermarks could not be created, and the conversion failed, generating an invalid-license error. | Changes to code relating to how stamps are handled in relation to paper size resolved this issue. |
11193 | When editing the filepath to the log file in the WebGrabber Configuration Manager or the WebGrabberSettings.xml file, issues were encountered.
| WebGrabber no longer supports the option to edit the filepath to the log file using the WebGrabber Configuration Manager or the WebGrabberSettings.xml file. |
12524 | Internet Explorer engine: When a normal web request includes cookie data set in the HTTPHeaders, the cookie data is not passed through. | Changes to code relating to how cookie data is handled resolved this issue. |
1313 | Spacing at the top of the first page was sometimes different than the spacing at the top of the second page. | General code updates resolved this issue.
|
13355 | After a vulnerability scan was run, an expired certificate was shown for the ActivePDF P3 Service. | Updates made to the ActivePDF P3 service resolved this issue. |
13517 | When a page contained Hebrew characters, WebGrabber did not convert the text correctly. | Setting the new WriteTextFormat to 0 (Write the text to the output; one "text run" at a time.) solves this issue. |
3824 | File or URL specific: These issues that were specific to a file or URL are now resolved. | General updates to the code resolved these issues. |
1318 2544 | These items were related to the Native Engine, most of them involving issues such as fidelity, alignment, line breaks, and spacing. | Updates to the Native Engine resolved these issues. |
Note: For a list of Known Bugs, see:
https://www.activepdf.com/support/kb-special/kb-bug-report/wg-known-bugs-2016-r1-0
Installing WebGrabber on Windows Server 2012 or above
If you are working on a Windows Server 2012 or above, and will use Internet Explorer as a conversion engine, follow these three sets of steps.
- Set up a WebGrabber user account and add it to the Remote Desktop Users group
- Log on to Windows Server ( 2012 and above) as Admin user.
- Create a new user account for the WebGrabber user.
- Add the new WebGrabber user to the Remote Desktop Usersgroup to grant remote login privileges.
Note: For more information about Remote Desktop Users, see these Microsoft article:
Configure the Remote Desktop Users Group
Install WebGrabber (Windows Server 2012 or above)- Log on to Windows Server (2012 and above) as Admin user.
- Launch WebGrabber installer.
- Follow the Quick Start Installation instructions, and in the WebGrabber Internet Explorer Login Information section, when prompted for IE login, enter the WebGrabber user account created in the steps above.
- Complete the installation.
Select IE to use for WebGrabber conversions(Windows Server 2012 or above)- Launch the WebGrabber Configuration Manager.
- In the WebGrabber top page, make sure the Enable Internet Exploreroption is checked, then click the Save icon.
Note: The Enable Internet Explorer option only displays on Windows Server 2012 or above installations.
Notes:
- In order to perform conversions with the Internet Explorer engine on Windows Server 2012 or above,
the WebGrabber Remote Desktop WebGrabber User must be logged in (but can be disconnected). - For more installation instructions and general startup information, see the Quick Start Guide listed below.
WebGrabber Quick Start Guide
See the Legacy section for the WebGrabber Quick Start Guide for information about installation and using the WebGrabber Configuration Manager at:
http://documentation.activepdf.com/WebGrabber_GS/Default.htm
API Reference
See the Legacy section for the WebGrabber API Reference Guide for information about .NET and COM methods and properties at: