GoLive “could not mark in use index.html”

January 2, 2008 at 4:59 pm | In Software | Leave a Comment
Tags: , , ,

Today I received the following error message in Adobe GoLive CS2 when I tried to edit a file:

Could not mark in use index.html. Version Cue reported an error. Error: 13 The requested operation could not be performed because it would override a conflicting change.

Odd, since the file was not checked out by anyone. Searching the web, I found mention of this problem in the Adobe Forums under Could not mark in use index.html. For that user, the fix involved erasing the problem file and copying it back, presumably from the Version Cue server.

Unfortunately, every file in my project seemed to be affected. (But only this project, no others.) So I decided to rename the original project folder and completely recreate it from Version Cue, which I did by choosing “New” and then “Connect to Site” in GoLive.

That did it—problem solved!

GoLive CS2 deletes nbsp

January 8, 2006 at 5:13 pm | In Software | Leave a Comment
Tags: , ,

In Adobe GoLive CS2, non-breakable spaces ( ) are sometimes replaced with normal spaces, typing option-space does not create a non-breakable space, and ampersand character codes are converted into Mac-equivalent symbols.

This appears to be due to a bug in how GoLive handles HTML pages that are encoded using the utf-8 charset. If a page is encoded in utf-8, whenever the page is edited in Layout mode all HTML character codes (e.g., ° for °) are converted to their equivalent Macintosh symbol. Non-breakable spaces ( ) are converted to regular spaces. The Macintosh characters will display properly in GoLive, but not in other browsers and/or operating systems. The removal of the non-breakable spaces may cause formatting problems.

Unfortunately, it appears that GoLive CS2 defaults to the utf-8 (“Multilingual”) character set. In previous versions of GoLive, HTML pages defaulted to iso-8859-1 (“Western”). Thus even if you are not purposely creating multilingual pages, you may run into this problem.

If your web pages are written in English, you can get around this by changing the default charset back to iso-8859-1. Choose “Preferences…” from the GoLive menu, click on “Encodings”, expand the “Roman” encoding, and then click the “Default” radio button to the right of “iso-8859-1″. If you’ve already created pages using the utf-8 charset, you can change them back to iso-8859-1 by expanding the “Head” section of the page, clicking on the flag icon, and then clicking on the “iso-8859-1″ radio button in the Inspector window.

If your web pages are written in a language other than English, you may be able to get around this problem by choosing a different charset. For example, if your web pages are written in traditional Chinese, try using “big5″ instead of utf-8.

GoLive CS2 creates duplicate CSS links

January 8, 2006 at 5:03 pm | In Software | Leave a Comment
Tags: , ,

In Adobe GoLive CS2, if you use page templates and your template includes a link to a CSS file, when you create a page based on the template the page may contain two links to the CSS file, one in the “locked” header section of the page and one in the modifiable header section.

This is because GoLive CS2 automatically adds a link to the “default” CSS file to all new HTML pages. When a template already has a link to the same CSS file, the result is two links. One of the CSS links may be absolute and the other relative, causing problems when the page is viewed.

The solution is to tell GoLive CS2 to stop adding links to the default CSS file. To do so, locate the default CSS file (most likely “basic.css” in the “css” folder), hold down the control key while clicking on the file’s icon, and then uncheck “Set as Default CSS” in the popup menu.

Blog at WordPress.com. | Theme: Pool by Borja Fernandez.
Entries and comments feeds.