NextCellent Gallery - NextGEN Legacy
[resolved] thickbox conflict with wordpress 3.9 (5 posts)

  1. ds123
    Posted 2 years ago #

    when i upgrade to wordpress 3.9 and nextcellent 1.9.18 thickbox doesn't work anymore it will enlarge photos but the entire screen is darkened including the enlarged photo ..if i deactivate nextcellent gallery plugin then the issue goes away

    can you please advise on how to fix?


  2. ds123
    Posted 2 years ago #

    i think i figured it out ...wordpress 3.9 changed the core file thickbox.css .... my issues seem resolved by adding back the font css stuff and then the issue with z-index

    /* thickbox fix / hack because wordpress has changed the includes thickbox.css core file */
    #TB_overlay {
    	z-index: 999 !important; /*they have it set at some crazy number */
    #TB_window {
    	font: 12px "Open Sans", sans-serif;
    	color: #333333;
    #TB_secondLine {
    	font: 10px "Open Sans", sans-serif;
    .rtl #TB_window,
    .rtl #TB_secondLine {
    	font-family: Tahoma, sans-serif;
    :lang(he-il) .rtl #TB_window,
    :lang(he-il) .rtl #TB_secondLine {
    	font-family: Arial, sans-serif;
    #TB_window a:link {color: #666666;}
    #TB_window a:visited {color: #666666;}
    #TB_window a:hover {color: #000;}
    #TB_window a:active {color: #666666;}
    #TB_window a:focus{color: #666666;}
    /* end thickbox fixes */
  3. niknetniko
    Posted 2 years ago #

    This shouldn't happen, normally. The NextCellent css file should not interfere with the thickbox css.

    Are you using a custom nggallery.css file?
    Do you have a link to your site?

  4. ds123
    Posted 2 years ago #

    no and this isn't limited to nextcellent but users that have thickbox as the effect for nextcellent might have this issue ...any image using thickbox doesn't work at least on my theme since wordpress changed the thickbox.css file ...i did get it working by using the above css

  5. Pat K
    Posted 2 years ago #

    Thanks ds123!!!

    I AM using a custom nggallery.css file and your fix worked perfectly. Saved me a bunch of time trying to figure this out. Thanks for sharing your solution!


Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic