ImTheirWebGuy

OK, so there are no config options to change that. I just wanted to confirm. Do you know of any custom solutions that present to the user a more intuitive experience? Right now they’re attempting to register and getting basically nowhere.

Thanks, Ron!

Just popping on to post that your snippet saved my life. Or at least pretty close to it. Thanks, Sutherland.

Same, nothing happening on upload click.

?? Glad it worked for you.

Found it. You’ll need to grab the updated jQuery.xml2json.js from below and replace the one included in the theme as it’s out of date.

https://www.fyneworks.com/jquery/xml-to-json/

@mightypixel, couldn’t we extend your idea of deregistration to deregister the remote js and replace it with a local call? Obviously, that would move the burden of version control to the local dev, but it seems a neat solution to the offsite script code concern.

Me too! It specifically broke Google Analyticator when 3.8 hit, so I figured other folks might want this ability as well.

OK, well, bad news. With the change in how Facebook requires links to be sent, this plugin is just no longer going to work until it’s massively updated. The links it generates for each content state return a 404 when accessed directly. Hopefully the dev will push an update soon.

OK, swapped out to my own app, and that error goes away, but the main error doesn’t; it just changes to:

“The href URL is not properly formatted”

The URL for the lightboxed state that’s generated is:

https://mygallerypage.com/#gs_img_uIghb+xpJTtQDHA3DHdVWA

The URL being sent to Facebook is:

http%3A%2F%2Fmygallerypage.com%2F%2F%3Fgs_img%3DuIghb%252BxpJTtQDHA3DHdVWA

So, when the script is generating the href value to pass to Facebook, it’s URLEncoding it. I don’t think I’m going to have time to unpack the JS right now, but I’ll check back later if someone else hasn’t already figured it out.

There’s an error message in the dom you can see by using Chrome inspector on the image display, and expanding the content tables:

“Given URL is not allowed by the Application configuration.: One or more of the given URLs is not allowed by the App’s settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App’s domains.”

The plugin calls a specific Facebook app, so I’m going to swap out for my own and see where that takes me.

I’m seeing the same thing. Shame. This plugin used to be pretty good. I’m digging into it to see if it’s an easy fix, will post back if I find something.

Hey all, great thread, which led me to my solution. I noticed I was having issues with mobile after pdwalker and acub’s solutions above, so I edited header-nav_walker.php to use WordPress’s built-in mobile check, and serve up one or the other:

function start_el(&$output, $item, $depth = 0, $args = array(), $id = 0) {
      $item_html = '';
      parent::start_el( $item_html, $item, $depth, $args);

      if ( $item->is_dropdown && ( $depth === 0)) {
      	// Enable top level links on desktop, disable on mobile
      	if ( wp_is_mobile() ) {
        $item_html = str_replace( '<a' , '<a class="dropdown-toggle" data-toggle="dropdown" data-target="#"' , $item_html);
        $item_html = str_replace( '</a>' , ' <b class="caret"></b></a>' , $item_html);
				} else {
        $item_html = str_replace( '<a' , '<a class="dropdown-toggle"' , $item_html);
        $item_html = str_replace( '</a>' , ' <b class="caret"></b></a>' , $item_html);
      	}
      }
      elseif (stristr( $item_html, 'li class="divider' )) {
        $item_html = preg_replace( '/<a[^>]*>.*?<\/a>/iU' , '' , $item_html);
      }
      elseif (stristr( $item_html, 'li class="nav-header' )) {
        $item_html = preg_replace( '/<a[^>]*>(.*)<\/a>/iU' , '$1' , $item_html);
      }

For anyone looking, Teslina’s solution seems to work pretty well: https://www.teslina.com/en/748/wordpress/qtranslate-code-syntax-bugfix/

I’m not using the more tag, so not sure if ChrisFo’s issue is still at play. I’m currently using WP 3.4.1 with qTranslate 2.5.31.