Slideshow won't work when published
I have published my first Muse site and it looks great & works perfectly, except the one slideshow wont run.
I have uploaded, then reuploaded my script files and it still doesnt work. Its hosted on a non-BC server.
Any ideas?
Please refer to the suggestions in the following topic:
My site doesn't work when I upload to my own web host, but it's fine in Preview. How do I fix this?
http://forums.adobe.com/message/4300529#4300529
If you are certain that your files are uploaded properly and in the correct locations, it is likely a permissions issue related to your scripts directory/files (suggestion #2).
Similar Messages
-
Slideshows don't work when published to .mac
After upgrading to iLife '08, the slideshows on my photo pages published from iWeb to .mac no longer work. They worked fine before. When I post to my web gallery directly from iPhoto, the slideshow works fine. I have checked to make sure the slideshow is enabled, and republished all of my pages. Now all of them don't work. Before that, only the new ones didn't work.
Thanks for your response, answered below:
If you build your site in iWeb '06 and converted it to '08 I would rebuild the photo pages from scratch. ANSWER The contents of the podcast track in '08 were replaced, not rebuilt
Do you still have an "iWeb" folder in Finder/Go/iDisk/My iDisk/Web/Sites? ANSWER: Yes, but there is nothing in it
THE CURRENT SITUATION is that the website loads, but the podcast picture doesn't appear, just a Quicktime logo with a ? in it. The sound tracks still play but no images appear.
Asked my husband to load the page on his PC, same thing happens ie the Quicktime logo with a ? appears. -
Does iWeb blogging (comments, etc.) only work when published to .Mac?
The subject says it all, but I was wondering how well the blog features of iWeb work when publishing to a non-.Mac host.
Right now I use WordPress for my blog. Is iWeb's blog feature a reasonable alternative?
dougThe iWeb features which are .Mac only are: Direct one-step uploading, Password protection, Hit counter, Slideshow with viewing controls, and Blog Comments/Searching.
-
my iPhone4 will not turn on or show that is working at all, i have tried to charge it so that the screen will light up but it won't work, when plugged into the computer iTunes does not show any sign it is plugged in, what do i do?
There is a hardware problem. Whether it's worth it to you to have no working phone for 2 months until you can update vs paying for replacement/repair now is a question only you can answer.
-
after upgrading to yosemite my magic mouse won't work when I wake up my mac mini. I have to power down and restore power for it to function. Also cannot send email from mac mini or iPad.
after upgrading to yosemite my magic mouse won't work when I wake up my mac mini. I have to power down and restore power for it to function. Also cannot send email from mac mini or iPad.
-
Close window not working when publishing as HTML5 on Adobe Connect using CP8
Hi all,
I'm trying to get a button that closes the project/window at the end of a video. I am using CP8.
I can get it to work when publishing as SWF to Adobe Captivate.
It also works when publishing as HTML5 but not on an LMS (Adobe Connect).
I have tried various methods including
- On success execute a Javascript = window.close()
- On success - exit
- On success execute advanced action = Assign cpCmdExit with 1
I also tried adjusting the slide settings On Exit: exit and the publishing settings Project End Options: Action: Close project.
Nothing works.
Any ideas?
Many thanks,
AimeeHi Aimee,
Can you test this to close the course window:
Insert 2 buttons or smart shape used as buttons (as Finish course buttons).
On the first button apply an action to execute javascript and in the script window, use this script: parent.close()
On the second button apply an action to execute javascript and in the script window, use this script: top.window.close()
Upload the published project on your LMS and check if any of these works for you.
Thanks
Himanshu -
My 8 key won't work when I press it to put in my password, what can I do?
my 8 key won't work when I press it to put in my password, what can I do?
Presumably you are connecting it from the *Dock Connector.* In this case, the controls on the car stereo should be controlling the iPod and the iPod's controls are disabled.
If you are using the car's connection interface, consult the car manual to find out how to control the iPod. If you are using an adaptor between the iPod and car, ask the adaptors installer or manufacturer.
Phil -
I have a mini mac updated to Yosemite, since I updated, my mac mouse won't work when I open ...So I have to unplug from my mac keyboard and plug back in again . Does anyone have the same problem?
Thanks Eric...a few other things have happened too...still working on them, I like the change just updating and figuring out why I might have some other problems...thånks again
-
My nano works when connected to a computer but won't work when unconnected. The battery is full.
My nano won't work when it is not connected to a computer. It won't even reset. If I pull it into my computer it will work and it shows that the battery is full. What might be the problem?
Then that sounds to be the Apple ID that owns this Mac, the OS and any preinstalled apps. Did that Apple ID set the Mac up when new?
-
Installed Windows 7 on bootcamp but now my wireless mouse won't work when in windows. What can I do?
Installed Windows 7 on bootcamp but now my wireless mouse won't work when in windows. What can I do?
assuming it is an optical mouse (no ball etc.) then there aren't any moving parts involve in the motion detection
so there's a faulty component or connection
from what you describe it could be just a loose/broken connection, so if you know someone familiar with electronics see if they can open it up and have a look -
Movies won't work when a DVD is inserted ?
Movies won't work when a DVD is inserted. What do I do to watch a movie ?
Just one DVD or all of them?
Some DVD's just need a gentile cloth and rubbing alcohol wipe on the bottom to rid of fingerprints etc.
If your using out of region code DVD's (each area of the world has regions codes assigned to the computer and disks) then that needs to be changed.
This can happen if you buy a Mac used from another part of the world or use DVD's from another region. -
Some link buttons won't work after publishing
I have noticed several of the buttons I created on my website in iWeb '06 don't work after the website is published but do work before it is published. What can I do to correct this?
Cathy JCould you supply a link, so I can look at the View Source and HTML? Have you tried re-building those buttons in iWeb that don't work when published and then re-publishing? It's probably not getting properly publish due to a import problem from the old iLife.
-
Captivate 6: Can't get any JavaScript to work when published as SWF
Version 6.0.1.240
Windows 7 x64
I have a button with an action of "Execute JavaScript" and can't event get a simple alert("hello"); to work when published as SWF. I've tried publishing it with each of the different Flash Player versions. JavaScript works fine when published as HTML5.@Erickj: Either do what Rod stated (adjusting your Flash Security settings) or test your content from a true web server. Flash automatically trusts content coming off a true web server where the web address begins with http or https and ends in .htm or .html.
The nice thing about Cp 7 is that it has a built-in web server so you don't run into issues like this when testing your content. -
Spry menu bar won't update when published
I am building a dreamweaver webpage though a template.
for some reason it will not change the spry menu bar to update the changes made to the links on it.
that and the links won't work on the website (i uploaded it to a test website).
I am not sure if it is the same problem.
I changed the links from site to document relative.
I also checked the codes in http://validator.w3.org/check and http://jigsaw.w3.org/css-validator/ .
I also read this link and it didn't help me http://helpx.adobe.com/dreamweaver/kb/paths-dreamweaver-templates.html .
Can someone help please!
Thank youI am not sure why that will not upload to the site correctly.
I am uploading to a godaddy server. Is there a way I should be saving things (links and such) that I might be doing wrong? am I naming my links incorrectly? how do I make them so they will work once uploaded.
I followed the suggestions that you made and it looks like it is there but for somereason when i preview the page in a browser or live view the background image (parchment) doesn't show up on the screen.and the spry menu bar only comes up as an unordered list. I am not sure what would be causing this.
I have attached the code for 2 pages the first is the code of the template test file you suggested I make and the second is the code for the education connection page (this is a page that was made from the template and the background image is not working-i had this problem before but i thought it was fixed as the website has it fixed when i published it)
TEST SITE:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="file:///C|/Users/james/Documents/DREAMWEAVER SITES/JanKardys.com/Templates/Main_sitepage_template.dwt" codeOutsideHTMLIsLocked="false" -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- InstanceBeginEditable name="doctitle" -->
<title>Jan Kardys' Literary Agency</title>
<!-- InstanceEndEditable -->
<style type="text/css">
#header {
float: left;
width: 1000px;
#Menu_bar {
float: left;
width: 190px;
#Page_Content {
float: right;
width: 1000px;
font-family: "MS Serif", "New York", serif;
#footer {
float: left;
width: 1000px;
#Main_content {
float: left;
width: 395px;
padding-left: 100px;
#xtra_content {
float: right;
width: 395px;
padding-right: 100px;
font-family: "MS Serif", "New York", serif;
#container {
width: 1000px;
margin: 0 auto;
background-image: url(file:///C|/Users/james/Documents/DREAMWEAVER SITES/JanKardys.com/Images/Parchment.gif);
overflow: hidden;
#header_title {
font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
color: #0C3;
float: left;
#header_menubar {
float: right;
</style>
<style type="text/css">
body {
</style>
<script src="/js/enhance.js" type="text/javascript"></script>
<script src="http://www.google.com/jsapi" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryDOMUtils.js"" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryWidget.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<script type="text/xml">
<!--
<oa:widgets>
<oa:widget wid="2466548" binding="#OAWidget" />
<oa:widget wid="2141544" binding="#MenuBar" />
</oa:widgets>
-->
</script>
<link href="/css/basic.css" rel="stylesheet" type="text/css" />
<link href="/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
These assume the following widget classes for menu layout (set in a preset)
.MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
.MenuBarVertical - vertical main bar; all submenus are pull-right.
You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
They only apply to horizontal menu bars:
MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
and centered in its parent container.
MenuBarFullwidth - Grows to fill its parent container width.
In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
background-color:transparent;
font-family: "Trebuchet MS", Arial, Helvetica, sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
MenuItem, and MenuItemLabel
at a given level all use same definition for ems.
Note that this means the size is also inherited to child submenus,
so use caution in using relative sizes other than
100% on submenu fonts. */
font-weight: normal;
font-size: 16px;
font-style: normal;
padding:0;
border-color: #ffffff #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
display:none;
.MenuBarLeftShrink {
float: left; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarRightShrink {
float: right; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarFixedLeft {
float: left;
width: 80em;
.MenuBarFixedCentered {
float: none;
width: 80em;
margin-left:auto;
margin-right:auto;
.MenuBarFixedCentered br {
clear:both;
display:block;
.MenuBarFixedCentered .SubMenu br {
display:none;
.MenuBarFullwidth {
float: left;
width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
padding: 0px 0px 0px 0px;
margin: 0; /* Zero out margin on the item containers. The MenuItem is the active hover area.
For most items, we have to do top or bottom padding or borders only on the MenuItem
or a child so we keep the entire submenu tiled with items.
Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
padding: 0px 0px 0px 0px;
background-color:transparent;
border-width:1px;
border-color: #cccccc #ffffff #cccccc #ffffff;
border-style: none solid none solid;
#MenuBar .MenuItemFirst {
border-style: none none none none;
#MenuBar .MenuItemLast {
border-style: none solid none none;
#MenuBar .MenuItem .MenuItemLabel{
text-align:center;
line-height:1.4em;
color:#33ff66;
background-color:transparent;
padding: 6px 15px 6px 15px;
width: 10em;
width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
font-family: Arial, Helvetica, sans-serif;
font-weight: normal;
font-size: 14px;
font-style: normal;
background-color:transparent;
padding:0px 2px 0px 0px;
border-width:1px;
border-color: #cccccc #cccccc #cccccc #cccccc;
/* Border styles are overriden by first and last items */
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
text-align:left;
line-height:1em;
background-color:transparent;
color:#00ff33;
padding: 6px 5px 6px 5px;
width: 7em;
width:auto;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
background-color: transparent;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
background-color: transparent; /* consider exposing this prop separately*/
color: #000000;
#MenuBar .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #000000;
#MenuBar .SubMenu .MenuItemHover {
background-color: transparent;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #333333;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
background-color: transparent;
min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
border-color: #ffffff #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
top: 100%; /* 100% is at the bottom of parent menuItemContainer */
left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
and your personal taste.
0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
on MenuItemContainer and MenuItem on the parent
menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
the dropdown with the left of the menu item label.*/
z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
top: 0px;
left:100%;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
background-color: transparent;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
top: 0px; /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
vertically 'centered' on its invoking item */
left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #333333;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
</style>
<!-- InstanceBeginEditable name="head" -->
<!-- InstanceEndEditable -->
</head>
<body>
<div id= "container">
<div id="header">
<div id="header_title"><h1>Jan kardy's Literary Agency</h1></div>
<div id="header_menubar">
</li>
</ul>
<!-- InstanceBeginEditable name="menubar_region" -->
<ul id="MenuBar">
<li> <a href="file:///C|/Users/james/Documents/DREAMWEAVER SITES/JanKardys.com/index.html">Home</a></li>
<li> <a href="file:///C|/Users/james/Documents/DREAMWEAVER SITES/JanKardys.com/about_jankardys.html">About Jan Kardys</a></li>
<li> <a href="#">Resources</a>
<ul>
<li> <a href="/Education_connection.html">Education Connection</a></li>
<li> <a href="/submission_guidelines.html">Submission Guidelines</a> </li>
<li> <a href="#">Blogs</a>
<ul>
<li> <a href="http://unicornwritersconferencect.blogspot.com/">Unicorn Writers Conference</a></li>
<li> <a href="http://advancenetworkingunicorn.blogspot.com/">Advanced Netwroking Blog</a></li>
</ul>
</li>
<li> <a href="#">First Steps to Publishing</a></li>
<li> <a href="#">Library & Publishing Events</a></li>
<li> <a href="#">Art Gallery</a> </li>
</ul>
</li>
<li> <a href="#">Clients</a></li>
<li> <a href="#">Contact Jan Kardys</a> </li>
</ul>
<!-- InstanceEndEditable --><script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
widgetID: "MenuBar",
widgetClass: "MenuBar MenuBarLeftShrink",
insertMenuBarBreak: true,
mainMenuShowDelay: 200,
mainMenuHideDelay: 200,
subMenuShowDelay: 200,
subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
</script>
</li>
</ul>
</div>
</div>
<div id="Page_Content"><!-- InstanceBeginEditable name="Content_main_editable" -->
<div id="Main_content">hi</div>
<!-- InstanceEndEditable --><!-- InstanceBeginEditable name="Xtra_content_editable" -->
<div id="xtra_content">
<h3>News & Events </h3>
<p> </p>
</div>
<!-- InstanceEndEditable --></div>
<div id="footer"> <h6>Webpage designed by James S. Molina</h6></div>
</div>
</body>
<!-- InstanceEnd --></html>
EDUCATION CONNECTION CODE:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/Main_sitepage_template.dwt" codeOutsideHTMLIsLocked="false" -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- InstanceBeginEditable name="doctitle" -->
<title>Jan Kardys' Literary Agency</title>
<!-- InstanceEndEditable -->
<style type="text/css">
#header {
float: left;
width: 1000px;
#Menu_bar {
float: left;
width: 190px;
#Page_Content {
float: right;
width: 1000px;
font-family: "MS Serif", "New York", serif;
#footer {
float: left;
width: 1000px;
#Main_content {
float: left;
width: 395px;
padding-left: 100px;
#xtra_content {
float: right;
width: 395px;
padding-right: 100px;
font-family: "MS Serif", "New York", serif;
#container {
width: 1000px;
margin: 0 auto;
background-image: url(/Images/Parchment.gif);
overflow: hidden;
#header_title {
font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
color: #0C3;
float: left;
#header_menubar {
float: right;
</style>
<style type="text/css">
body {
</style>
<script src="/js/enhance.js" type="text/javascript"></script>
<script src="http://www.google.com/jsapi" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryDOMUtils.js"" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="http://labs.adobe.com/technologies/spry/ui/includes/SpryWidget.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<script type="text/xml">
<!--
<oa:widgets>
<oa:widget wid="2466548" binding="#OAWidget" />
<oa:widget wid="2141544" binding="#MenuBar" />
</oa:widgets>
-->
</script>
<link href="/css/basic.css" rel="stylesheet" type="text/css" />
<link href="/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
These assume the following widget classes for menu layout (set in a preset)
.MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
.MenuBarVertical - vertical main bar; all submenus are pull-right.
You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
They only apply to horizontal menu bars:
MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
and centered in its parent container.
MenuBarFullwidth - Grows to fill its parent container width.
In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
background-color:transparent;
font-family: "Trebuchet MS", Arial, Helvetica, sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
MenuItem, and MenuItemLabel
at a given level all use same definition for ems.
Note that this means the size is also inherited to child submenus,
so use caution in using relative sizes other than
100% on submenu fonts. */
font-weight: normal;
font-size: 16px;
font-style: normal;
padding:0;
border-color: #ffffff #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
display:none;
.MenuBarLeftShrink {
float: left; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarRightShrink {
float: right; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarFixedLeft {
float: left;
width: 80em;
.MenuBarFixedCentered {
float: none;
width: 80em;
margin-left:auto;
margin-right:auto;
.MenuBarFixedCentered br {
clear:both;
display:block;
.MenuBarFixedCentered .SubMenu br {
display:none;
.MenuBarFullwidth {
float: left;
width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
padding: 0px 0px 0px 0px;
margin: 0; /* Zero out margin on the item containers. The MenuItem is the active hover area.
For most items, we have to do top or bottom padding or borders only on the MenuItem
or a child so we keep the entire submenu tiled with items.
Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
padding: 0px 0px 0px 0px;
background-color:transparent;
border-width:1px;
border-color: #cccccc #ffffff #cccccc #ffffff;
border-style: none solid none solid;
#MenuBar .MenuItemFirst {
border-style: none none none none;
#MenuBar .MenuItemLast {
border-style: none solid none none;
#MenuBar .MenuItem .MenuItemLabel{
text-align:center;
line-height:1.4em;
color:#33ff66;
background-color:transparent;
padding: 6px 15px 6px 15px;
width: 10em;
width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
font-family: Arial, Helvetica, sans-serif;
font-weight: normal;
font-size: 14px;
font-style: normal;
background-color:transparent;
padding:0px 2px 0px 0px;
border-width:1px;
border-color: #cccccc #cccccc #cccccc #cccccc;
/* Border styles are overriden by first and last items */
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
text-align:left;
line-height:1em;
background-color:transparent;
color:#00ff33;
padding: 6px 5px 6px 5px;
width: 7em;
width:auto;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
background-color: transparent;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
background-color: transparent; /* consider exposing this prop separately*/
color: #000000;
#MenuBar .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #000000;
#MenuBar .SubMenu .MenuItemHover {
background-color: transparent;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #333333;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
background-color: transparent;
min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
border-color: #ffffff #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
top: 100%; /* 100% is at the bottom of parent menuItemContainer */
left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
and your personal taste.
0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
on MenuItemContainer and MenuItem on the parent
menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
the dropdown with the left of the menu item label.*/
z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
top: 0px;
left:100%;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
background-color: transparent;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
top: 0px; /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
vertically 'centered' on its invoking item */
left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #333333;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
</style>
<!-- InstanceBeginEditable name="head" -->
<!-- InstanceEndEditable -->
</head>
<body>
<div id= "container">
<div id="header">
<div id="header_title"><h1>Jan kardy's Literary Agency</h1></div>
<div id="header_menubar">
</li>
</ul>
<!-- InstanceBeginEditable name="menubar_region" -->
<ul id="MenuBar">
<li> <a href="/index.html">Home</a></li>
<li> <a href="/about_jankardys.html">About Jan Kardys</a></li>
<li> <a href="#">Resources</a>
<ul>
<li> <a href="/Education_connection.html">Education Connection</a></li>
<li> <a href="/submission_guidelines.html">Submission Guidelines</a> </li>
<li> <a href="#">Blogs</a>
<ul>
<li> <a href="http://unicornwritersconferencect.blogspot.com/">Unicorn Writers Conference</a></li>
<li> <a href="http://advancenetworkingunicorn.blogspot.com/">Advanced Netwroking Blog</a></li>
</ul>
</li>
<li> <a href="#">First Steps to Publishing</a></li>
<li> <a href="#">Library & Publishing Events</a></li>
<li> <a href="#">Art Gallery</a> </li>
</ul>
</li>
<li> <a href="#">Clients</a></li>
<li> <a href="#">Contact Jan Kardys</a> </li>
</ul>
<!-- InstanceEndEditable --><script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
widgetID: "MenuBar",
widgetClass: "MenuBar MenuBarLeftShrink",
insertMenuBarBreak: true,
mainMenuShowDelay: 200,
mainMenuHideDelay: 200,
subMenuShowDelay: 200,
subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
</script>
</li>
</ul>
</div>
</div>
<div id="Page_Content"><!-- InstanceBeginEditable name="Content_main_editable" -->
<div id="Main_content"><img src="/Images/jankardys.jpg" width="171" height="234" alt="Jan_kardys_pictuer" /></div>
<!-- InstanceEndEditable --><!-- InstanceBeginEditable name="Xtra_content_editable" -->
<div id="xtra_content">
<center><h3>Signed Book Deal</h3>
<p><a href="http://jankardys.com/Advance_Royalties.html" title="Advance_Royalties.html">Advance/Royalties</a></p>
<p><a href="http://jankardys.com/Author_Quotes.html" title="Author_Quotes.html">Author Quotes</a></p>
<p><a href="http://jankardys.com/Book_Deal.html" title="Book_Deal.html">Book Deal</a></p>
<p><a href="http://jankardys.com/Copyright_Information.html" title="Copyright_Information.html">Copyright Information</a></p>
<p><a href="http://jankardys.com/Editorial_Assistance.html" title="Editorial_Assistance.html">Freelance Editorial Assistance</a></p>
<p><a href="http://jankardys.com/Electronic_Rights.html" title="Electronic_Rights.html">Electronic Rights Guidelines</a></p>
<p><a href="http://jankardys.com/Google_Products.html" title="Google_Products.html">Google Products</a></p>
<p><a href="http://jankardys.com/Out_of_Print_Reversions.html" title="Out_of_Print_Reversions.html">Out of Print Reversions</a></p>
<p><a href="http://jankardys.com/Permissions.html" title="Permissions.html">Permissions</a></p>
<p><a href="http://jankardys.com/Photo_release.html" title="Photo_release.html">Photo Release</a></p>
<p><a href="http://jankardys.com/Return_of_Advance.html" title="Return_of_Advance.html">Return of Advance</a></p>
<p><a href="http://jankardys.com/Subrights_Checklist.html" title="Subrights_Checklist.html">Subrights Checklist</a></p></center>
<p> </p>
<p> </p>
</div>
<!-- InstanceEndEditable --></div>
<div id="footer"> <h6>Webpage designed by James S. Molina</h6></div>
</div>
</body>
<!-- InstanceEnd --></html> -
External links won't work once published
Hi, I'm self taught so don't always understand everything and I'm a complete novice with iWeb, used Front Page before getting a Mac.
I'm in the process of building a new website using iWeb and I'm having problems with getting links to external pages to work. They work fine in iWeb. 'Enable as a hyperlink' and 'make hyperlinks active' is ticked for all links. I've formatted the links to be coloured red, then orange when visited and blue with an underline on roll over, grey if disabled. All works fine in iWeb but then when I publish the links won't work. They will momentarily and then they won't. If I refresh the page then one or two will work but when you go back to the page they won't work again. I've deleted them all and redone them, still the same problem. Tried it in Safari and Firefox, same problem. Deleted the site from the server and republished, same problem. Anyone got any ideas?
On the page in question I have a widget to SkyScanner, thought that was maybe causing a conflict. Deleted it and republished, same problem.
Here's a link to the page I'm having problems with http://www.marbella-rentals.co.uk/MarbellaRentals/flights.html and it's the links to airlines on the right that I can't get to work.
Also I have another couple of questions. How do you resample images? I have used a background image on the pages and I've managed to get it to stay static by altering the code slightly but don't know how to resample it so that the page will load quickly. Ditto with all the rest of my images. Don't want to have to resize them all manually if possible. Also, with the background image I don't know what size I should make it if I was to do it manually.
Last question... How do you change the title of your page and add a favicon?
If anyone can help me would be much appreciated.
ThanksYou have an image covering some of the hyperlinks - GraphPaper_01_3.png
Do a Command A on the iWeb page to find it.
Your background image seems to load OK. Use an optimizer to to get it and the whole site to download faster...
http://www.iwebformusicians.com/Search-Engine-Optimization/Optimize.html
See this page for howw to add a favicon...
http://www.iwebformusicians.com/iWeb/URLs-Favicons.html
To add title tag and meta description you need to open each HTML file post publishing and add them with an editor app. More conveniently, you can use iWeb SEO Tool...
http://www.iwebformusicians.com/Search-Engine-Optimization/Tags.html
Here's a checklist for the publishing workflow if you are adding SEO tags and Optimizing...
http://www.iwebformusicians.com/Search-Engine-Optimization/Website-Publishing-Wo rkflow.html
Maybe you are looking for
-
I think this thing read right before I loaded Yahoo Tool Bar so I could use Yahoo Mail as my default. Since then It hasn't been correct. It did read (4 unread) for a while then for some reason it changed to 6.
-
How can i remove comments from the "tell your frie...
How can I remove comments from the "tell your friends how you're doing" section?
-
hello guys. I need your help. I had an phone. iPhone5, bought last June of this month in China. I am a filipino, now I am here in Philippines. The problem has just started last week. Everytime I open my phone, there's a green color at center's screen
-
6510 printer not printing Black ink Error: NON-HP INK ????? IT is an 564 HP INK Cartridge ???
Subject: I ran out off black ink 564. Cartridge PS: I purchased this ink cartridge at Staples . Purchased new 564 XL cartridge for my HP 6510 printer. that is approx 1 year old Insatalled new 564 XL ink Cartridge. Problem : does not print
-
Trying to install Brother MFC-j475dw printer on older macbook (running osx 10.5.8) and need an inbox driver as Brother drivers are only for 10.6 and newer. Any ideas?