Presets Not Showing Up

I have downloaded some presets from a cool website, and in Beta versions they showed up in the preset window. But now , with 1.0, they are not showing at all. I have quit twice but to no avail.
Did Adobe change where the presets go?

~/Library/Application Support/Adobe/Lightroom/Develop Presets/
Where "~" is your user directory.
From: www.lightroomextra.com - download section

Similar Messages

  • All PDF Presets Not Showing Up in Menu

    There are 14 total PDF presets between both Settings folders on my computer (Mac 10.8.5). Only 10 of them are showing in the Adobe PDF Presets menu item. Does anyone know why all of them wouldn't be showing up?
    Thanks,
    Lloyd

    I'm in InDesign CC 2014. All of the missing ones came with InDesign, as far as I know…they all have the same creation dates. I created two and they ARE showing up. And it's not consistent; some from each folder are showing up, and some from each folder are not showing up. A couple of them are named PDFA1b as opposed to PDFX1a (etc.). Also, two that aren't showing up have JPN in the file name (right before the period) but one that has JPN in the file name IS showing up. It's not a huge deal, I was just curious why some would and some wouldn't.Thanks!

  • Camera Raw Defaults & Presets not showing menus (BRIDGE)

    Hi There
    I just upgraded to a new version of PS CS3 & Bridge and the option to apply Presets, or to Apply Camera Raw Defaults is not showing when I right click a file in Bridge. It also doesnt show up in the menu. I need to be able to Batch process hundreds of photos at a time and then convert them to Tif formats. I used to be able to do this by applying my Adobe Camera Defaults to many images at once. How do I do this now????
    I am running Bridge 2.0.0975 and PS 10. Help!! This is critical for me!!!
    thanks so much!

    > Even if old versions are available for download, having older versions available on disk in case of malfunction is a perfectly acceptable practice.
    > This applies to any update of any software.
    Agreed. I have gigabytes of disk space packed full of iso's, dmgs, and zips for
    (almost) all of the software I've installed on my computers. It's a pain to
    manage sometimes, but I know I can go back and reinstall PS7 (for instance) if I
    need to even though I have no clue where the CD is at. It's just one part of my
    configuration management and backup strategy. I don't have a sysadmin to take
    care of this kind of thing for me any more, unfortunately, so I have to do it
    myself.
    This plan also has the advantage that I don't have to be online to download
    older versions from a vendors site (if it's even available) or go searching for
    a seeded torrent (if it's not).
    I'm not saying this approach is good for every one or even good for anyone but
    me, but it is a perfectly valid way of doing things.
    -X

  • Why does my paid presets not show up in lighroom 5.6

    I purchased Presets for lightroom by miracle design and installed it with creative cloud. Creative cloud and adobe extension manager show that it is installed but presets are not showing in lightroom.

    Since there are no free Miracle Design LR presets, I can’t experiment and tell you my experience with the install process.  Have you done what it says in the “Where to find it” tab?

  • PDF presets not showing up in indesign CC

    Hi,
    We have about 28 CC users on mac (mavericks), and we've just started using Indesign CC within the last month or so.
    My problem is that we are 'deploying' via remote desktop, a standard set of PDF presets so everyone have the same settings. This works fine on cs3-cs6. But for some reason it does not work with indesign CC. CC wil only show the presets that are in the users/xxx/Application support/Adobe PDF/Settings folder and not the ones from the default folder /Library/Application support/adobe/adobe PDF/settings .
    I can add them by either loading the presets in indesign one by one, on every single mac, or manually  also on every single mac, put the presets in the users folder, but both options really suck. Mind you we change presets very often, so this is really not ideal for me.
    Hope someone can help direct me to the master PDF preset folder for CC - The one folder who rules them all !!!

    http://forums.adobe.com/community/indesign may be a better place to ask
    This forum is actually about the Cloud as delivery, not about using individual programs
    If you start at the Forums Index http://forums.adobe.com/index.jspa
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll

  • Why are animation presets not showing in pop-up list for fractal noise?

    In a standard install of AE CS4, the animation presets pop-up list showed a bunch of presets for fractal noise (see attached image).
    In a standard install of AE CS5.5, the animation presets pop-up list showed a bunch of presets for fractal noise (see attached image).
    In a standard install of AE CS6 (on the Mac), the pop-up list is empty. (Yes, I enabled the "Show presets"), despite the fact that, eg, "Curtain.ffx" is in the equivalent Presets>Backgrounds folder.
    Is there another switch to turn on? I'm using Mac OSX 10.7.5.

    In a standard install of AE CS4, the animation presets pop-up list showed a bunch of presets for fractal noise (see attached image).
    In a standard install of AE CS5.5, the animation presets pop-up list showed a bunch of presets for fractal noise (see attached image).
    In a standard install of AE CS6 (on the Mac), the pop-up list is empty. (Yes, I enabled the "Show presets"), despite the fact that, eg, "Curtain.ffx" is in the equivalent Presets>Backgrounds folder.
    Is there another switch to turn on? I'm using Mac OSX 10.7.5.

  • Lightroom 3.2 previews of presets not showing in Develope module.

    Hey, any idea why LR 3.2 will not preview the effects of presets when scrolling over them in the Develop module?  This was a fast way to work creatively with previous versions of LR.
    This happens for all presets, including those shipped with LR.  Presets "work" but you cannot see effects unless you apply them first.  Preview is broken.
    Anyone else having this issue or have a fix idea?
    Thanks!

    THEY SURE DO!  WISH I SLEPT MORE...:)
    THX!

  • Lightoom 5.4 Presets not showing

    Can anyone explain where the presets have gone in Lightroom 5.4. There is no drop down menu for them in Develop mode.
    Thanks.

    Thanks Jim,
    I would never have found that, especially on a Mac. What a strange design not to have it under 'View' or 'Develop'. That's anoher thing I'd change on Lightroom 5.5!!
    Best Wishes
    Chris

  • Compressor presets not showing up in FCPX.

    So I just bought compressor, I made a custom output option and it showed up in FCPX. I deleted that one and made a new one...now the 'custom' folder is empty in FCPX but it has an item in the folder in Compressor.
    I'm sorry if this is dumb, but I searched google and here before I posted and couldn't find a resolution.

    Nevermind, I figured it out. For some reason if you choose 'QuickTime Export Components' it won't show up in FCPX but other custom settings will. Oh well.

  • The "My Mixology" is not Showing up in my Import or Develop Presets of LR3

    The "My Mixology" is not Showing up in my import or develop Presets of LR3. Do I have to download this?
    Thanks for your assistance.

    Hello dj_paige.
    Thanks for the reply.
    Here is a YouTube video which shows the presets in LR3, which is what I have.  At the 1:50 mark you will see in the develop module where he clicks on the Lightroom Presets drop down.  In a "LR4" Youtube video which I viewed (I can't find the dern thing!) a group called "My Mixology" was shown under which their were some other presets.
    http://www.youtube.com/watch?v=VOdC561kt5I
    I am unsure if My Mixology is available only in LR4 or if I can import these or what.  I have looked googled for the answer but have been unable to locate it.
    Thanks again for your assistance.

  • The presets and brushes I installed are not showing up.

    I have installed lightroom 5 on my windows 8 PC. I had lightroom on my previous laptop, which was also windows, and had to purchase it again. Anyway, I installed some brushes and presets on it and they will not show up anywhere. I've done this before and never had any issues. I have googled everything and am coming up with nothing. Can you please help me?

    What version of PSE? And is this on a mac? If so you never, never, never want to put ANYTHING in the system folder.

  • IPad 3 Mailboxes not showing even after syncing with iMac and switching on SSL and port readings the same; even tried rebuild. Switched iPad off, rebooted and discovered settings went back to preset?

    Hi to all techies,
    Ipad3 with new iMail does not show mailboxes.  Have tried swithcing SSL on and making port same number 993 as imac; then telling imail in imac to synchronise but to no avail still no mailboxes appearing on ipad mail.  My husbands new ipad air worked straight away same OS?

    I'm sorry. I probably wasn't clear enough in my response. What I am saying is that one can create mailboxes in the Mac mail app and those mailboxes can be for local storage only - the "on my Mac" mailboxes. Those do sync to any other device. The ability to creat those mailboxes is a feature of the Mac mail app.
    You cannot create additional mailboxes on the iPad unless your email account is an IMAP account. I am not familiar with BT internet at all so I don't know if you have IMAP or not. I assume that your husband has the same email provider and if his mailboxes did sync to the iPad, then yours should as well.
    You can check to be sure if you don't know if your email account is an IMAP account. If you go to your email account in the iPad Mail app and look at the window where your inbox, trash folder and sent folder are - if there is an Edit button at the top of the window - tap that and then tap Add Mailbox at the bottom. If an new mailbox appears, you have IMAP.
    If the Edit button is not there - you cannot create folders on the iPad. Your email account is not IMAP. Only IMAP email accounts can create folders on the iPad. Any folders that you would already have in an IMAP account would sync to the device as well.

  • NO GUITAR Rig 2.2 Presets? They are in the presets folder but do not show

    They do not show up in Logic!
    ideas?
    Thanks

    Were they there when you first installed and then disappeared or is this a new installation? I had that problem one day. I restarted my computer and it was fine after.

  • 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&amp;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 &amp; 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 &amp; 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

  • Calendar invites are not showing up in the Calendar Inbox

    Calendar invites from Google Calendar are not showing up in the iPhone Calendar Inbox.  They do show up in the actual iPhone calendar (greyed out waiting for a response) but if you are managing multiple invites it's very important to view the invites especially if dealing with multiple invites on different days.  This is affecting users with Iphone4, 4s and 5 on multiple iOS's.

    Sorry for the late reply, it is still an irritating issue.  Apple says it's Google's poblem.  Google thinks it's Apple's issue.  Extremly irritating.
    I tried setting up the Calendar using the Exchange presets but that did not solve the invitation problem.

Maybe you are looking for

  • How do I get sound to play on my Samsung HDTV from my macbook pro?

    I've been trying to figure out how to get sound to play on my TV from my laptop for several days now and was wondering if anyone had any suggestions for a solution to this. I bought an Mini Display Port to HDMI converter (Kanex Iadapt) off Amazon tha

  • Adobe Reader XI will not print fillable text.

    I have a user that is having issues with printing a fillable pdf file.  Two things are happening.  First: the document prints fine except what is filled in the sections that are to be filled out.  Second: It always prints this along with it:  "This j

  • Get plugins page is displayed in a different language then my firefox language

    The get plugins page inside the plugin manager is displayed in german eventhough my firefox is in turkish.

  • Place images, reassemble slices, layer issues

    I am creating a sprite of images I have in the bridge. I placed button images from the bridge.  I tried to merge the layers so there is only one layer for the sprite.  When I did the merge the images got locked onto the background layer and I can't m

  • Scaling of text outlines in svg format

    I'm in need of a solution for scaling text outlines in an svg format. I'm working on developing a Flash app that allows users to type in Flash text with an outline that is then exported out in an svg format. When user then scales the resulting svg fo