mckaymultimedia

Have you tried replacing the jQuery plugin in this plugin (jquery.nivo.slider.pack.js) with the latest version of the jQuery plugin available for the Nivo Slider (https://dev7studios.com/plugins/nivo-slider/) ?

Just curious if that would work for upgrading this plugin with newer versions of jQuery. Looks like the latest Nivo Slider jQuery plugin is compatible with jQuery version 1.10.1. If this works you can hack the plugin and update the jQuery plugin yourself.

In theory this should work.

That said I did find some that were similar. There was one that got close but forget what it was. I ended up just doing it myself out of frustration.

Oh I am actually glad someone followed up on this thread. I never quite found exactly what I was looking for.

So I ended up just building a completely custom theme from scratch using Boilerplate here and Bootstrap combined with the Navwalker here to get the menu functioning as it should.

You can see a working example here. The example site is incomplete content-wise but you can see that Bootstrap and the fundamentals of the site’s theme functions as it should.

In fact I did. I ended up figuring out a working query string on my own. Here is what worked for me.

<?php query_posts(array('posts_per_page' => 5, 'meta_key' => 'post_views_count', 'orderby' => 'meta_value_num', 'order' => 'DESC', 'ignore_sticky_posts' => 'true', 'paged' => ( get_query_var('paged') ? get_query_var('paged') : 1 ), )); ?>

Bumpsky.

From reading the documentation about the Facebook “Social Plugin” for comments I know that it is suppose to be capable of detecting the browser agent and converting to a mobile format with fluid widths when a mobile browser agent is detected or if mobile=true is called in the comments code. So why then does this Facebook comment plugin not utilize this aspect of the Facebook Social Plugin? I notice that this is a widespread problem with many of the Facebook plugins available for WordPress. Has anyone discovered or developed an effective solution for this issue?

That would be sufficient for my purposes in the short term. However I am in the process of migrating all of my personal project websites to responsive themes, so having a solution for NextGen coupled with WPTouch (Pro) is not alone sufficient. With the responsive themes WPTouch will no longer be utilized. I would rather not have to continue to customize NextGen every time there is an update or I make a new website when there are many comparable emerging image galleries/slideshows that have responsiveness already integrated in the plugin. That’s why I had hoped to get the NextGen developer to recognize the issue and do something about it.

After extensive research, I came the conclusion that this is a known compatibility issue with Google Adsense code and Windows Mobile OS. So there is not much I can do about it. It works just fine on IOS and Android so it’s not so bad. Thanks for the info though. Hopefully this will provide some insight for others that may be dealing with this issue.

If this issue with the lack of responsiveness is not addressed, and soon with the next release, then I have no other choice but to go with a different plugin for my galleries and slideshows. I am certain many other loyal users of NextGen are drawing the same conclusion. Who has the time to wait around for NextGen to catch up to the trend towards mobile-friendly/responsive functionality? Not me… It’s a shame. What was once such a good plugin is now lacking so much in terms of mainstream functionality with the current internet trends.

sykesjs:

Could you please provide a little more insight into how exactly you modified the adsense-new.php file to make the ads function in compliance with the New Adsense mobile platform.

I see the difference in formatting between how original adsense-new.php file is compiling the Adsense code and how the new Adsense mobile code appears but I am having some difficulty getting it to appear in the WPTouch. The only thing that is happening with the fixes I have implemented is that a blank space is now appearing in place of the ads, which is an improvement since an error was appearing before.

Any further clarification you can provide would be greatly appreciated.

I tried inserting your code in various ways into the code above and it didn’t work. What it did was just echo the shortcode again so that it appeared twice in the post which is typically the result I have been getting with all the potential solutions I have found from scouring the web.

Thanks for the suggestion though. I know there is a solution to this puzzle somewhere.

Thanks. I will give that a try.

Cool. I glanced over the part about new meta boxes feature. I am glad they are still there. Now my question would be why is that Quickie Metaboxes feature not working on the website with News theme then?