Page 1 of 1

WYSIWYG Web Builder 8.2 update

Posted: Mon Jun 11, 2012 7:34 am
by Pablo
WYSIWYG Web Builder 8.2 fixes known problems, adds new features and includes other improvements.

What's new in 8.2?
- Fixed: Grid does not have correct offset when scrolled.
- Fixed: Master page modifications can cause for crash closed pages using that master page.
- Fixed: <ctrl>+<right arrow> doesn't work properly if 'snap to grid' is enabled.
- Improved: Added 'background-color:transparent' for background images (useful for transparent images).
- Improved: First selection of GoMenu no longer generates error if user did not select a link.
- Improved: Replaced ereg() with preg_match() in PHP code. ereg() is not longer supported in newer versions of PHP.
- Improved: SiteTree object now also supports generic background styles (transparent, solid, gradient, image, pattern, texture).
- Improved: 'Error reports' now also verifies master frame objects for the current page.
- New feature: Added the ability to add custom code to a content place holder (only works if it has a border or background)
- New feature: Added support for background textures to Theme Manager.
- New feature: Added box shadow to text object.
- New feature: Added 'Synchronize with Site Manager' option to Go Menu.
- New feature: The 'core' of extensions is now built into the application. This reduces the overhead, quicker loading and less memory usage. Also it provides closer integration possibilities with WWB.
- New feature: Added 'Optimize inline styles' to HTML options. This is option attempts to cleanup the HTML code by moving inline styles to the page's style sheet.

How to update from previous 8.x versions?
1. Download the latest version here:
2. If you already have version 8.x you can install it over your previous version. Make sure you select the same folder!

Advanced users can also download the update files only here (no installer):

Re: WYSIWYG Web Builder 8.2 update

Posted: Thu Jun 14, 2012 6:30 am
by Pablo
WYSIWYG Web builder 8.2 now generates even cleaner HTML code where the styling (CSS) is seperated from the HTML.
However this means that more than ever it's important to make sure your IDs are unique within the context of the page, otherwise the same object will get multiple styles definitions.
You can use the new Error Reports tool (Menu->Tools->Error Reports) to check for duplicate IDs.

More details: