<div align="justify"><p><u><b>HTML Editors</b></u> </p><p><b>Automatic Rollover Creation</b> </p><p>Have you ever created a rollover on a web page?
Probably thousands of times, right? Well, GoLive 6.0 makes this tedious process easier than any web authoring application in the world and it happens to be one of our favourite new features!
GoLive 6.0 can learn how you name the image files that make up the multiple rollover states so that all the required images are detected and all the JavaScript code is written (including preloading) automatically! To teach GoLive 6 how you name your rollover images, select any image in Layout mode and choose 'Rollover Settings...' from the 'Image Inspector' paletbox, or asp:dropdownlist. </p><p><b>CSS with Contextual Menus</b> </p><p>Most people use the CSS palette to apply their CSS classes to page elements, but contextual menus offer an easier way to mark-up your pages in GoLive 6.0. Select the objects or text in Layout mode and Control-click (Mac)/Right-click (Windows) and choose the appropriate option from the Apply CSS Style menu. </p><p><b>Text in old pages seems too large)</b> </p><p>If you open web pages created in older versions of GoLive your text might appear larger then you expected. GoLive 6.0 now uses 96 dpi as the default for rendering text in Layout mode because this is the W3C recommendation and what most current Macintosh and Windows web browsers use. This means what you see in Layout mode in GoLive 6.0 is probably more like what your visitors will see in their web browsers. To ensure your text renders more consistently across platforms and browsers, we recommend using CSS to set your font sizes in pixels. If you really must force GoLive 6.0 to render fonts in the outdated and non-standard way, then here's the trick. Open the file AdobeGolive.agluap present in C:\Program Files\Adobe\GoLive6\Settings\UserAgentProfiles\AdobeGoLive\. Find the line that says [var name-?dpi? value=?96?/] and change it to [var name=?dpi? value=?72?/]. Quit and relaunch GoLive. </p><p><b>Hidden Elements Disturb Table Measurements (Tables)</b> </p><p>If your table cells contain any invisible elements-a Hidden form element, a comment tag, an image map, a floating box, or any other GoLive placeholder which the program previews with a tiny icon onscreen but isn't shown in a browser page-the table's measurements may be off. GoLive includes those invisible items as part of its calculations for a table's legal size.
The simple solution is to select 'Hide Invisible Items' from the View menu. By default, all of these placeholders are categorized as 'Invisible Items', and are removed off the screen but remain in the code. </p><p><b>Offsite Graphics (Images)</b> </p><p>Many Web sites offer affiliate or click-through links that include graphics. Instead of providing you with a graphic itself, they offer up a small bundle of HTML that you need to insert in your page. GoLive only previews local content in the Layout Editor. To view the image that the Web site provided to you in HTML, which is actually stored on their site or a partner's, preview the page in a browser. The browser should successfully retrieve the image over the Internet. If it doesn't, check that you pasted the HTML correctly. </p><p><b>Levels of SQL Access (Dynamic Content)</b> </p><p>GoLive 6.0 users have stumbled into a permission issue with MySQL databases and GoLive's Dynamic Content feature. Each user of a MySQL (or any SQL) database is assigned certain privileges. A user can be assigned read-only access to a given database or even a single table in a database, which allows them to create dynamic pages, but not to create, delete, or modify records. If you're using the record changing features in GoLive 6 to update or add records in a database, make sure you have these permissions from the database administrator before you go nuts troubleshooting the problem from the GoLive side. </p></div>