Premier Elements 9 - DVD Main Menu not showing navigation highlights
Hi All,
Apologies if this discussion / question appears twice. I seemd to lose the original and did not think it had been posted.
New to Adobe and just started using Premier Elements 9 for a basic DVD project.
I managed to work out importing, editing, transitions, adding soundtrack etc and got to the DVD Menu stage where everything seemed to come together.
Once i had burned to DVD i checked it worked on the PC which it did but when i tried in a number of DVD players, there was an issue with Main Menu marker navigation.
This project has a main and four scene menus plus an 'Extras' marker i added to the Main Menu pointing toward Stills..
On all the Scene menus, i can see a clear highlight dot move from scene to scene as i navigate with the remote, showing where I am as you would expect.
On the Main Menu however, where i have Play Movie, Scenes and Extras markers, there is no sign of any dot or highlight to tell you which of these you are currently on so its a lottery as to which you get when navigating with a remote from the Main Menu.
I am pretty sure this is user error and if anyone has thoughts of what i have done or not done when i set up the DVD Menu section maybe, i would very much appreciate it.
A little additional info is apart from adding the 'Extras' button to the main menu i imported a still image/Logo to show up in the middle of the menu screen and added a sound clip to the main and all the 'Scene menus.
Whether that has anything to do with it i don't know.
thank you in advance for any clues as to what i have done wrong.
Regards
psutt.
Hi ATR,
My sincere apologies for not getting back to you sooner. This project has been above and beyond my day to day work as an integrator to the Post Production area and everything went a little nuts over the last few weeks.
I wanted to let you know that I was successful in the end, thanks to your input.
I ended up substituting the ‘Fun in the Sun’ with’ Memory Box’ HD under ‘Memories’ and this was the magic solution.
I got bogged down trying to lengthen rolling end credits and lengthening a title plate that headed the Extras but I left as is in the end.
The main thing was the menus worked just fine after the change so I won’t go near Fun in the Sun again if I do another sometime.
I kept it to NTSC widescreen and it looked fine.
Many thanks again for your input.
Kindest Regards
Peter Sutton
Technical Director
Kaurus® Limited
cid:[email protected]
Similar Messages
-
[?] Main Menu not showing after "Restore", resetting not helping
Hi,
I recently received my 30GB iPod Video 5G (got it for myself for Christmas). I began charging it. Meanwhile, I uninstalled my old iTunes, and installed the iPod / iTunes / Quicktime software on the CD that came with the iPod. All fine.
I checked the iPod after four-five hours and it had finished charging. I restarted my computer, plugged it in, and iTunes wouldn't detect it. After some frolick, I went to the iPod Updater and clicked Restore. Bad idea!
Since then on, I haven't been able to access the main menu in any way. I've tried reinstalling the software a few times, and nothing helps. I've tried resetting the iPod, but I keep getting that little sign with the exclamation point. My iPod is fully charged.
I'd try the "5 Rs", but I can't reset my iPod, and I restoring it doesn't help, and I've reinstalled all I can.
I've a question - does restoring actually erase the little main menu? If so, where can I reinstall it? If not, what should I do?
- by the way, throughout this little crisis, I got iTunes to start up at one point.
Don't think it's my USB port.
To recap, the problem is that I'm stuck, and I can't reach the main menu. I don't always see "Disk Mode", although I can get to it by holding the select button and the play/pause button at the same time.look here for info on the exclamation point.
http://docs.info.apple.com/article.html?artnum=61003
Pressing the center buton and the menu button does a soft reset.
did you look hhere for general info
http://www.apple.com/support/ipod101/
Simply restoreing your ipod to factory settings resets your ipod to the way you recieved it when you unpacked it. It does not erase the main menu it simply erases all the music/photos/videos from your ipod if there was any.
sound like when you say that your ipod is stuck its frozen did you folow this
http://docs.info.apple.com/article.html?artnum=61705
since you are using windows 200 do you have meet the tech specs in regards to the service pack? Do you have a USB 2 or earlier?
GFF -
A slide show with audio created in PSE 9 plays fine in edit. When brought to Premier Elements for dvd burn, the audio no longer plays. It appears in the edit, but no audio is played. This happens consistently. What setting might be wrong?
H-SPhoto
That Photoshop Elements 9.0.3 Update has generally been discouraged by the Photoshop Elements gurus. But, I am not going to factor that into this at this point.
This is what I would ask you to look at in the Elements Organizer 9 accessed from the Photoshop Elements 9 or Premiere Elements 9.
a. Create your slideshow in the Elements Organizer 9/Create/Slideshow/Slideshow Editor. Then use the Output option of Edit with Premiere Elements.
From your description, you are probably using the Output Option of Burn to Disc DVD which will take your slideshow directly in the Disc Menu section of Premiere Elements 9. The preferred transfer of the Elements Organizer 9 slideshow to Premiere Elements 9 Editor is by the non wmv route "Edit with Premiere Elements" not the wmv route of Burn to Disc DVD.
Let us explore if any of the above is involved in your issue and then we will decide what next if necessary.
Thanks.
ATR -
Disc menu not showing up on DVD
Hi, I selected (and changed to suit my needs) a template for the opening screen disc menu set. When I burned to DVD, it did not show up though it played during the preview. Also the overal movie had some studders to it that are not in the original vob clips. What to do? I'm using PE 10 with a windows 7 system.
One can alter the PrE Menu Sets, but with DVD Menus, there are several considerations, that must be adhered to.
I use Photoshop to customize my PrE Menu Sets, and it works fine.
Within the constraints of DVD Menus, one can do some things in PrE, PS or PSElements.
When it comes to Sub-picture Highlights, there are many, many more constraints, and limitations, but one can do quite a bit of customization.
Steve Grisetti covers the in's and out's of PrE Menu Set customization, in his PrE books, and especially the Photoshop Elements/Premiere Elements book.
If you need more details, let us know, as Ihave a few discussions, that I can share, should you wish to do customization, beyond just adding an appropriately Scaled Stil Image, or Video, as a background.
Good luck,
Hunt -
Adobe premier elements 11 downloaded but will not install
adobe premier elements 11 downloaded but will not install?
Hunt
What you just wrote may have revealed the Photoshop Elements Premiere Elements integration consideration. If you have Premiere Elements 11, you need Photoshop Elements 11 for the integration between the programs to produce the DVD version of the Photoshop Elements Slideshow.
All along I was picturing Meyerswalter already in Premiere Elements 11/Publish+Share/Disc/DVD and being told to install Premiere Elements to get the burn to disc accomplished.
But, if Meyerswalter is using Premiere Elements 11 and a non integrated version of Photoshop Elements for this matter, that could very well fit.
So, Meyeswalter, so that we can dispel those thoughts
a. What versions of Photoshop Elements are you using with Premiere Elements 11? And, are you in the Photoshop Elements Slideslide Show Editor using the Output of Burn to Disc DVD or Edit with Premiere Elements Editor and getting the load software message somewhere along the line?
b. To prove this point, if you have not already, what happens if you take Photoshop Elements out of the equation. Import some media into Premiere Elements 11 and try to burn to disc from there Publish+Share/Disc/DVD?
If that is the core of the issue, I will post a list of Photoshop Elements Premiere Elements integrated combos as a guideline for you.
If this is the core of the issue, you could always keep the non Photoshop Elements 11 version that you have, output the slideshow to a wmv file sized for DVD and then import that into Premiere Elements 11 via its Add Media. More on that later if necessary since right now I am speculating on an explanation for what you are encountering.
Thanks.
ATR -
Main Menu:Not enough disk space for asset encoding
i tried to burn my project first i got an error that in track 1 i've got no assets/videos and i added an asset, then a problem with the story and dragged the same story in both columns.. now i tried to burn again and got this error
Main Menu:Not enough disk space for asset encoding
Build cancelled
Building was not successful. See log.
any help appreciated. Thanks in advanceSounds like your hard drive is getting full. You need as much space on your drive as you can get - at least as much as the disc contents, twice. If you are burning a DVD-R at 4.7Gb then allow ten Gb free space before you start.
-
I have photoshop elements 9 and iphoto does not show it in my advaced preferences drop down, it used to be there, how do I get it back again?
Hi, Yes you are correct in iPhoto Prefernces, Advanced tab editing I used to have iPhoto and "Use external editor.". It changed to iPhoto and iPhoto Library. I have einstaleed PSE 9 and downloaded the update. There is still no lkink to external editor in the drop down box. Have I done something wrong inadvertently or is there a clitch? can you reinstal iPhoto. I am new to Macs. Every thing came preinstalled. it is the top of the range system with 16 Gb of rRAM, 2 Tb hard drive to top graphics card etc. I used to be on Windows PC. Have more than 27,000 photos on the system. Much apprecite your reply and interest in this.
-
Adobe Photoshop Elements 12 for Mac does not show up in Applications. Tutorial for editing from iPhoto shows selecting the Adobe software in Applications. Am I missing a step in registering product?
I answered my own question: There's a difference between "download' and "install." Hunt for "install" (1.5 hrs in my case) and line up your passwords, Adobe ID, etc, then install. Took 15 min. The right choice shows up in Applications. Now it's on to figuring out why photo selected for edit in iPhoto does not show up on screen in Elements.
-
I've researched to death and tried everything but can't fix this.
Recently did a clean install on my iMac and since then iWeb won't work.
I have :
- Reinstalled from original disc then updated to latest version 3.0.4
- Deleted the com.apple.iWeb.plist file and com.apple.iWeb Cache Folder, restarted, and tried opening again
- I have removed my domain.sites2 file to try and open iWeb and initiate making a new site
iWeb is fully loaded and operational - in Activity Monitor it does not have a red flag - shows as being operational. I can access iWeb's Preferences, open and close various Inspectors, but the main window is simply not visible.
I am on Lion 10.7.2
I had updated my website using iWeb while on Lion 10.7.1
I have a small business and my website is outdated and will be losing me new customers at this point who will think I don't have the latest stock and information.
Any help appreciated - naturally no need to reply if 'fixes' are as per other posts and noted as having been tried above.Where is the main page not showing? In iWeb or online?
In Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
For opening your domain file in Lion or to switch between multiple domain files Cyclosaurus has provided us with the following script that you can make into an Applescript application with Script Editor. Open Script Editor, copy and paste the script below into Script Editor's window and save as an application.
Just launch the application, find and select the domain file you want to open and it will open with iWeb. It modifies the iWeb preference file each time it's launched so one can switch between domain files.
do shell script "/usr/bin/defaults write com.apple.iWeb iWebDefaultsDocumentPath -boolean no"delay 1
tell application "iWeb" to activate
You can download an already compiled version with this link: iWeb Switch Domain or from Toad's Cellar.
WARNING: iWeb Switch Domain will overwrite an existing Domain.sites2 file if you select to create a new domain in the same folder. So rename your domain files once they've been created to something other than the default name.
OT -
Application menu not showing in preference pane
Have brought some games for the iphone and ipod touch but have no application menu not showing in preference pane to upload them to to ipod touch. All software is current both itunes and ipod touch
Help would be very grateful,If you go to Preferences, General you should be able to see the "Applications" check box, below "Audiobooks". Check the box, this will show the Applications icon in your library.
Message was edited by: googood -
Premier Elements 11 installed but does not launch
I installed premier elements 11, the installation did not have any problems, but when I click on the icon nothing happens. It does not give an error message, is does not try to do anything, it simply does not launch. I uninstall, turn off the norton software, did a clean boot to prevent other services to load, re-installed the software and the problem continues.
I have window 7 64 bits 8 gb memory, more than enough disk space. What else can be wrong that is preventing the application from launching?Hi,
Could you please try the following solutions and see if any of these work:
1. Navigate to 'PhotoshopElementsEditor.exe' located inside:
Win x64: C:\Program Files (x86)\Adobe\Photoshop Elements 13
Win x32: C:\Program Files\Adobe\Photoshop Elements 13
Right click on 'PhotoshopElementsEditor.exe' and select 'Run as Admin'
2. Just after this keep on pressing 'Ctrl+Alt+Shift' on Windows (or Command+Option+Shift on Mac). You will get a popup asking to delete Elements settings file. Click Yes.
If the above does not work, please try the following:
3. Please rename SLCache folder present at location "<root drive:>\Program Files (x86)\Common Files\Adobe\SLCache"
Also please rename opm.db on your machine to resolve this issue @ <root drive>\Users\<user name>\AppData\Local\Adobe\OOBE
Now re-launch the application.
4. In case any network printer is attached try to launch without network or printer uninstall or make different printer as default.
5. Try launching with anti-virus off or removing PSE from conflicting list.
If none of these work, please let me know.
Regards,
vaishali -
Dvd/cd rom not showing up on computer.
dvd/cd rom not showing up on computer. Where do I find the driver for the dvd/cd?
Have a pavilion dv6915nr with windows vista. Somehow the dvd/cd player is not showing up and will not play anything.
Any suggestions on what I can do.Is this because i am an idiot and need a DVD drive?
Have you got a DVD drive?
Have you been able to playback DVDs before? If not, then you may very well need a DVD drive... not just a CD drive.
You'll be able to tell what you have by looking in 'My Computer' when there are no discs in the drives. The drives should show up as things like: 'CD-ROM Drive(D:)' or 'CD/DVD Drive(D:)'. If none of the drives have DVD in the title, you may just need a DVD drive.
If you have any luck getting them to show up, take a look at this thread for help on ripping DVDs to iPod.
{ If this is helpful, please click the '+' on my post. Thanks! } -
I have made a simple DVD with one track, one menu and one button. When I put the burned DVD into the player the menu will not show up. It just skips straight to the one track. My "First Play" is definitely definiteley set to "Menu 1". Does anyone know why this is happening? I have never had this problem before.
DVD players do not function properly when a menu is set as first play
create a black image in Photoshop and import into DVDSP
make a new track and drag the black still into the track and set the end jump to your first menu
set the track to first play -
Adobe Premier Pro cs4: Maximum render quality not showing in drop down menu in Export screen
I have been trying to export a movie with settings i previously used but for some reason the Maximum render quality option that comes from the drop down menu next to video audio filter multiplexer etc is not showing up.. will someone plz tell me how to fix this...
Maximum render quality was introduced in an update for Premiere Pro CS4. Choose Help -> Check for Updates.
-
Spry 2.0 menu not showing in IE8
I have a webpage with a horizontal and vertical Spry 2.0 menu on the page. Both menus work correctly in Firefox, Chrome, Safari, and IE9, but the vertical menu does not show at all in IE8. In addition in IE8 the browser scroll bar disappears when the vertical menu is added. The test page is http://www.njslom.org/001banner5.html
I am using CS5 and the Spry 2.0 Widget in an html template.
Any help at all would be appreciated.
[email protected]
Page 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" xmlns:spry="http://ns.adobe.com/spry">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- TemplateBeginEditable name="doctitle" -->
<title>Untitled Document</title>
<!-- TemplateEndEditable -->
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
<style type="text/css">
body,td,th {
font-family: Arial, Helvetica, sans-serif;
body {
background-color: #EBEBEB;
margin-top: 0px;
</style>
<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="/Spry-UI-1.7/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>
<link href="/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<style type="text/css">
#MenuPublic1 {
background-color:#F2F2F2;
font-family: 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: bold;
font-size: 12px;
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 ".MenuPublic1FixedCentered br" rule bleow */
display:none;
.MenuPublic1LeftShrink {
float: left; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuPublic1RightShrink {
float: right; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuPublic1FixedLeft {
float: left;
width: 70em;
.MenuPublic1FixedCentered {
float: none;
width: 70em;
margin-left:auto;
margin-right:auto;
.MenuPublic1FixedCentered br {
clear:both;
display:block;
.MenuPublic1FixedCentered .SubMenu br {
display:none;
.MenuPublic1Fullwidth {
float: left;
width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuPublic1 .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. */
#MenuPublic1 .MenuItem {
padding: 0px 0px 0px 0px;
background-color:#F2F2F2;
border-width:0px;
border-color: #cccccc #ffffff #cccccc #ffffff;
border-style: none solid none solid;
#MenuPublic1 .MenuItemFirst {
border-style: none none none none;
#MenuPublic1 .MenuItemLast {
border-style: none solid none none;
#MenuPublic1 .MenuItem .MenuItemLabel{
text-align:center;
line-height:1.4em;
color:#ffffff;
background-color:#F2F2F2;
padding: 7px 28px 7px 28px;
width: 10em;
width:auto;
.SpryIsIE6 #MenuPublic1 .MenuItem .MenuItemLabel{
width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuPublic1 .SubMenu .MenuItem {
font-family: Arial, Helvetica, sans-serif;
font-weight: bold;
font-size: 12px;
font-style: normal;
background-color:#F2F2F2;
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;
#MenuPublic1 .SubMenu .MenuItemFirst {
border-style: solid solid none solid;
#MenuPublic1 .SubMenu .MenuItemFirst .MenuItemLabel{
padding-top: 4px;
#MenuPublic1 .SubMenu .MenuItemLast {
border-style: solid solid solid solid;
#MenuPublic1 .SubMenu .MenuItemLast .MenuItemLabel{
padding-bottom: 4px;
#MenuPublic1 .SubMenu .MenuItem .MenuItemLabel{
text-align:left;
line-height:1em;
background-color:#F2F2F2;
color:#ffffff;
padding: 4px 12px 4px 5px;
width: 175px;
/* Hover states for containers, items and labels */
#MenuPublic1 .MenuItemHover {
background-color: #69adee;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuPublic1 .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
background-color: #69adee; /* consider exposing this prop separately*/
color: #000000;
#MenuPublic1 .MenuItemHover .MenuItemLabel{
background-color: #69adee;
color: #000000;
#MenuPublic1 .SubMenu .MenuItemHover {
background-color: #69adee;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuPublic1 .SubMenu .MenuItemHover .MenuItemLabel{
background-color: #69adee;
color: #000000;
/* Submenu properties -- First level of submenus */
#MenuPublic1 .SubMenuVisible {
background-color: #F2F2F2;
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;
#MenuPublic1.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;
#MenuPublic1.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 */
#MenuPublic1 .MenuLevel1 .SubMenuVisible {
background-color: #F2F2F2;
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 #MenuPublic1 .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
background-color: #69adee; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuPublic1 .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
background-color: #69adee; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuPublic1 .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>
<script type="text/xml">
<!--
<oa:widgets>
<oa:widget wid="2141544" binding="#MenuPublic1" />
<oa:widget wid="2141544" binding="#MenuPublic1_2" />
</oa:widgets>
-->
</script>
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuPublic1_2 */
/* 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 #MenuPublic1_2 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.
#MenuPublic1_2 {
background-color:#8ca7d2;
font-family: 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: bold;
font-size: 12px;
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 ".MenuPublic1_2FixedCentered br" rule bleow */
display:none;
.MenuPublic1_2LeftShrink {
float: left; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuPublic1_2RightShrink {
float: right; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuPublic1_2FixedLeft {
float: left;
width: 175px;
.MenuPublic1_2FixedCentered {
float: none;
width: 175px;
margin-left:auto;
margin-right:auto;
.MenuPublic1_2FixedCentered br {
clear:both;
display:block;
.MenuPublic1_2FixedCentered .SubMenu br {
display:none;
.MenuPublic1_2Fullwidth {
float: left;
width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuPublic1_2 .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. */
#MenuPublic1_2 .MenuItem {
padding: 0px 24px 0px 0px;
background-color:#8ca7d2;
border-width:0px;
border-color: #cccccc #ffffff #cccccc #ffffff;
border-style: none solid none solid;
#MenuPublic1_2 .MenuItemFirst {
border-style: none none none none;
#MenuPublic1_2 .MenuItemLast {
border-style: none solid none none;
#MenuPublic1_2 .MenuItem .MenuItemLabel{
text-align:left;
line-height:1.4em;
color:#ffffff;
background-color:#8ca7d2;
padding: 6px 10px 6px 10px;
width: 175px;
.SpryIsIE6 #MenuPublic1_2 .MenuItem .MenuItemLabel{
width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuPublic1_2 .SubMenu .MenuItem {
font-family: Arial, Helvetica, sans-serif;
font-weight: bold;
font-size: 12px;
font-style: italic;
background-color:#0066ff;
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;
#MenuPublic1_2 .SubMenu .MenuItemFirst {
border-style: solid solid none solid;
#MenuPublic1_2 .SubMenu .MenuItemFirst .MenuItemLabel{
padding-top: 4px;
#MenuPublic1_2 .SubMenu .MenuItemLast {
border-style: solid solid solid solid;
#MenuPublic1_2 .SubMenu .MenuItemLast .MenuItemLabel{
padding-bottom: 4px;
#MenuPublic1_2 .SubMenu .MenuItem .MenuItemLabel{
text-align:left;
line-height:1em;
background-color:#0066ff;
color:#ffffff;
padding: 4px 12px 4px 5px;
width: 175px;
/* Hover states for containers, items and labels */
#MenuPublic1_2 .MenuItemHover {
background-color: #cae9fd;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuPublic1_2 .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
background-color: #cae9fd; /* consider exposing this prop separately*/
color: #000000;
#MenuPublic1_2 .MenuItemHover .MenuItemLabel{
background-color: #cae9fd;
color: #000000;
#MenuPublic1_2 .SubMenu .MenuItemHover {
background-color: #69adee;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuPublic1_2 .SubMenu .MenuItemHover .MenuItemLabel{
background-color: #69adee;
color: #000000;
/* Submenu properties -- First level of submenus */
#MenuPublic1_2 .SubMenuVisible {
background-color: #0066ff;
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;
#MenuPublic1_2.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;
#MenuPublic1_2.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 */
#MenuPublic1_2 .MenuLevel1 .SubMenuVisible {
background-color: #0066ff;
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 #MenuPublic1_2 .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
background-color: #cae9fd; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuPublic1_2 .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
background-color: #69adee; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuPublic1_2 .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 */
.text-white { color: #FFF;
</style>
</head>
<body>
<table width="950" border="0" align="center" cellpadding="7" cellspacing="0">
<tr>
<td width="284" bgcolor="#0000CC"><strong class="text-white">Serving Municipal Government in <br />
New Jersey Since 1915</strong></td>
<td width="305" bgcolor="#0000CC"><div align="center"><div align="center"> <!-- Begin PicoSearch Query Box -->
<table style="background-color:#004d8c" cellspacing="0" cellpadding="0" border="0">
<tr><td>
<form style="margin:0;" method="get" action="http://www.picosearch.com/cgi-bin/ts.pl">
<input type="hidden" name="index" value="520788" />
<table style="background-color:#004d8c" cellspacing="2" cellpadding="0" border="0">
<tr><td><a href="http://www.picosearch.com/cgi-bin/index.pl?wherefrom=picobox&type=allhttp://www.picosearch.com/cgi-bin/index.pl?wherefrom=picobox&type=all"></a></td>
<td align="right"><input type="text" name="query" value="" size="20" />
<input type="submit" value="GO" name="search2" /></td>
</tr>
</table>
</form>
</td></tr></table>
<span style="white-space: nowrap;">
</span><!-- End PicoSearch Query Box --></div></div></td>
<td width="319" bgcolor="#0000CC"><div align="right" class="text-white"><a href="http://www.njslom.org" class="text-white"><strong>HOME</strong></a> | <a href="http://www.njlmef.org" class="text-white"><strong>NJLM Educational Foundation </strong></a></div></td>
</tr>
</table>
<table width="950" border="0" align="center" cellpadding="0" cellspacing="0" bgcolor="#F2F2F2">
<tr>
<td width="135"><img src="/images-head/head-logo-1.jpg" width="128" height="200" /></td>
<td width="815" valign="top"><p> </p>
<p> </p>
<p> I will be adding the Spry Content Slideshow in this area</p>
</td>
</tr>
</table>
<table width="950" border="0" align="center" cellpadding="0" cellspacing="0">
<tr>
<td colspan="2" bgcolor="#F2F2F2"><ul id="MenuPublic1">
<li> <a href="#">Classifieds</a>
<ul>
<li><a href="#">Classifieds & Job Listings</a></li>
</ul></li>
<li> <a href="#">NJ Municipalities Magazine</a>
<ul>
<li> <a href="#">Current Issue</a></li>
<li> <a href="#">Advertise</a> </li>
<li> <a href="#">Subscribe</a> </li>
<li> <a href="#">Submission Guidelines</a></li>
</ul>
</li>
<li> <a href="#">Seminars & Events</a>
<ul>
<li><a href="#">Events & Registration</a></li>
<li><a href="#">CEU Requirements</a></li>
</ul>
</li>
<li> <a href="#">Legislation</a>
<ul>
<li><a href="#">Legislative Committee</a></li>
<li><a href="#">Legislative Priorities</a></li>
<li><a href="#">Legislative Bulletin</a></li>
<li><a href="#">Conference Resolutions</a></li>
</ul></li>
<li> <a href="#">Issues & Documents</a>
<ul>
<li><a href="#">Issue Alerts</a></li>
<li><a href="#">Press & Media</a></li>
<li><a href="#">Publications</a></li>
<li><a href="#">Sample Resolutions</a></li>
<li><a href="#">League Testimony</a></li>
</ul></li>
<li> <a href="#">NJLM Directories</a>
<ul>
<li><a href="#">Staff</a></li>
<li><a href="#">Executive Board</a></li>
<li><a href="#">League Officers</a></li>
<li><a href="#">League Attorneys</a></li>
<li><a href="#">League Affiliates</a></li>
<li><a href="#">League Committees</a></li>
</ul></li>
<p>
<script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuPublic1
var MenuPublic1 = new Spry.Widget.MenuBar2("#MenuPublic1", {
widgetID: "MenuPublic1",
widgetClass: "MenuBar MenuPublic1LeftShrink",
insertMenuBarBreak: true,
mainMenuShowDelay: 100,
mainMenuHideDelay: 200,
subMenuShowDelay: 200,
subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
</script>
</p></td>
</tr>
<tr>
<td width="175" valign="top" bgcolor="#F2F2F2"><p> </p>
<ul id="MenuPublic1_2">
<li> <a href="#">Home</a></li>
<li> <a href="#">Entertainment</a>
<ul>
<li> <a href="#">TV Listings</a></li>
<li> <a href="#">Music</a>
<ul>
<li> <a href="#">Hits</a></li>
<li> <a href="#">Ragga</a>
<ul>
<li> <a href="#">Roots</a></li>
<li> <a href="#">Reggaeton</a></li>
<li> <a href="#">Dancehall</a></li>
</ul>
</li>
<li> <a href="#">Country</a></li>
</ul>
</li>
<li> <a href="#">The Dirt</a>
<ul>
<li> <a href="#">Hollywood</a></li>
<li> <a href="#">NY Beat</a></li>
<li> <a href="#">London Scene</a></li>
</ul>
</li>
<li> <a href="#">The Web</a></li>
</ul>
</li>
<li> <a href="#">Politics</a></li>
<li> <a href="#">Sports</a>
<ul>
<li> <a href="#">Football</a></li>
<li> <a href="#">Baseball</a></li>
<li> <a href="#">Basketball</a></li>
<li> <a href="#">Racing</a>
<ul>
<li> <a href="#">F1</a></li>
<li> <a href="#">Indy Car</a></li>
<li> <a href="#">Stock Car</a></li>
</ul>
</li>
</ul>
</li>
</ul>
<script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuPublic1_2
var MenuPublic1_2 = new Spry.Widget.MenuBar2("#MenuPublic1_2", {
widgetID: "MenuPublic1_2",
widgetClass: "MenuBar MenuBarVertical MenuPublic1_2MenuBarVerticalLeftShrink",
insertMenuBarBreak: true,
mainMenuShowDelay: 100,
mainMenuHideDelay: 200,
subMenuShowDelay: 200,
subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
</script>
<p> </p></td>
<td width="773" valign="top" bgcolor="#F2F2F2"><!-- TemplateBeginEditable name="EditRegion3" -->
<p>EditRegion3</p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p>This is the bottom of the page</p>
<!-- TemplateEndEditable --></td>
</tr>
</table>
</body>
</html>I get the following error message
Perhaps you could have a look at KB927917
Gramps
Maybe you are looking for
-
How to create a muse site in various languages with multiple domains
I have been asked to create a website for a product. A very simple website with maybe one or two pages and one product for sale for which the client would like Paypal as the payment gateway. Simple right? No! This client would like to market their pr
-
Sql Loader and carriage returns
I am currently trying to use sql loader to load data from flat files that was extracted from sybase using bcp and delimited with pipes. There are text and varchar columns that contain carriage return line feeds. I want to preserve these, but I can no
-
i had lost the grey, round shaped rubber placed under my magic trackpad. i think it detached from the trackpad body and lost. where can i get this small spare part as i couldn't find this small spare part in apple store?
-
Search help - Make a field default without grey-out
Hi, I have a custom-search help, where in the dialog-popup I'd like to default a value without grey-out. If I import from memory via parameter ID, then the default value is ok, but it's greyed out. If I don't import it, then it's initial, but not gre
-
Conditions in Classic Scenario without IPC?
Hi ! I would like to know if possible to work with conditions in SRM without the IPC. Is it possible? There will be like 4 or 5 conditions, like freight and other purchase costs. My SRM version is 5.5. We are using the classic scenario (purchase orde