martinlbb

I also noticed that selecting ‘HTML Tidy’ instead of ‘Default’ on HTML Minify will mess up any foreign language website (mine is both French and English).

Keep ‘Default’ to avoid this.

It works for me!

Thanks for help.

BTW, to avoid auto erasing of modified settings in /wp-content/w3tc/min/.htaccess after each Minify update, you can modify following file:

/wp-content/plugins/w3-total-cache/lib/W3/Plugin/Minify.php
At lines 1076 and 1085 and 1088 add ‘QSA,’

Before:

$rules .= "    RewriteRule ^w3tc_rewrite_test$ index.php?w3tc_rewrite_test=1 [L]\n";

        if ($engine == 'file') {
            if ($compression) {
                $rules .= "    RewriteCond %{HTTP:Accept-Encoding} gzip\n";
                $rules .= "    RewriteRule .* - [E=APPEND_EXT:.gzip]\n";
            }

            $rules .= "    RewriteCond %{REQUEST_FILENAME}%{ENV:APPEND_EXT} -f\n";
            $rules .= "    RewriteRule (.*) $1%{ENV:APPEND_EXT} [L]\n";
        }

        $rules .= "    RewriteRule (.*) index.php?file=$1 [L]\n";

After:

$rules .= "    RewriteRule ^w3tc_rewrite_test$ index.php?w3tc_rewrite_test=1 [QSA,L]\n";

        if ($engine == 'file') {
            if ($compression) {
                $rules .= "    RewriteCond %{HTTP:Accept-Encoding} gzip\n";
                $rules .= "    RewriteRule .* - [E=APPEND_EXT:.gzip]\n";
            }

            $rules .= "    RewriteCond %{REQUEST_FILENAME}%{ENV:APPEND_EXT} -f\n";
            $rules .= "    RewriteRule (.*) $1%{ENV:APPEND_EXT} [QSA,L]\n";
        }

        $rules .= "    RewriteRule (.*) index.php?file=$1 [QSA,L]\n";

Sorry, copy/paste error.

But now, it works. And I found my error:

I was using window.onload, who trigger too early I think.

Using jQuery(document).ready, It works perfectly!

Example:

<script type="text/JavaScript">
jQuery(document).ready(function(){
  jQuery(document.location.hash).click();
});
</script>

Thanks for your help Pedro ??

Ok I modified my code.

<a id="les-quais" name="les-quais" href="/portfolio/test-photo/les-quais.jpg" title="A Lyon" rel="lightbox[test-photo]"  >
<img title="Les quais" alt="Les quais" src="/portfolio/test-photo/thumbs/thumbs_les-quais.jpg" width="200" height="133" /></a>

And JS:
jQuery('#uap').click();

No error in Console, but nothing show up.
If I try jQuery('#uap').start(); I get ‘is not a function’.

From my memory, click is not allowed in Firefox. Maybe is it linked?

Sometimes, I’m too dumb!

Thanks Pedro for this usefull help!

BTW, I think I can’t use $, but I have to use jQuery instead of.

BTW, jquery is already used in my WordPress blog.

Following your suggestion, I tried this:
<a id="les-quais.jpg" name="les-quais.jpg" href="/portfolio/test-photo/les-quais.jpg" title="A Lyon" rel="lightbox[test-photo]" ><img title="Les quais" alt="Les quais" src="/portfolio/test-photo/thumbs/thumbs_les-quais.jpg" width="200" height="133" /></a>

And then in Javascript (short version, I removed autoload):

<script type="text/javascript">
$('#les-quais.jpg').click()
</script>

Nothing happened, I just have an error in my console:
Error: $("#les-quais.jpg") is null.

Any ideas ?

ALex already included a default preset parameter for using monoslideshow.

Just use preset=”” on your shortcode.

Example : [monoslideshow id=1 w=640 h=358 preset=”Spot”]

If you are using custom made XML, just put your custom name.

Worked for me, I’m using different monoslideshow with different XML theme on various pages.

Are you using this plugin?

https://www.ads-software.com/extend/plugins/jj-nextgen-unload/

If yes, this plugin avoid CSS to be load…. Try unloading it.

Good news!

That’s weird. I created a brand new blog to test galleryview (only WordPress, nextgen and galleryview installed) and it worked.

Reading your web code, you’re taking jquery v1.4.3 straight on Google site. Is that normal?
Usually, NextGen Gallery is using a local version of jQuery (actually 1.4.2).
I think your error come from this mismatch.
Try using genuine jQuery version from NextGen Gallery.

OR

Try disabling any extension, and then enabling one by one. Maybe one extension got a mismatch with nggGalleryView.