SN0WKRASH

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 47 total)
  • SN0WKRASH

    (@sn0wkrash)

    Actually, boiling down the code more, do you think I could use something like this:

    <?php wp_head(); ?>
        <meta name="viewport" id="viewport" content="width=device-width, target-densitydpi=device-dpi">

 		<?php if (is_mobile()) : ?><?php if (!is_ipad()) : ?>
		<script type='text/javascript'>
     	document.getElementById("viewport").setAttribute("content", "width=device-width");
		</script>
	<?php endif ?><?php endif ?>

    Thank you.

    SN0WKRASH

    (@sn0wkrash)

    Hello, I need the same thing. I have set up all mobile rules in the stylesheet like this:

    @media (max-width:767px) {/*mobile stuff here*/}

    This is what I have now as the viewport:

    <head>
	<meta charset="<?php bloginfo( 'charset' ); ?>">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="HandheldFriendly" content="True" />
	<meta name="viewport" id="viewport" content="width=device-width, target-densitydpi=device-dpi">

	<script type='text/javascript'>
		if (screen.width > 767) {
 document.getElementById("viewport").setAttribute("content", "width=device-width; target-densitydpi=device-dpi");
}
		if (screen.width <= 767) {
 document.getElementById("viewport").setAttribute("content", "width=device-width");
}
	</script>

    <script type='text/javascript'>
	(function() {
  if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
    var msViewportStyle = document.createElement("style");
    msViewportStyle.appendChild(
      document.createTextNode("@-ms-viewport{width:auto !important}")
    );
    document.getElementsByTagName("head")[0].appendChild(msViewportStyle);
  }
})();
	</script>

    But the problem with this is that when I use is_mobile() throughout my code, is_mobile() does not necessarily mean <= 767 wide and I get bad results in some cases. I need to somehow match-up is_mobile() to mean <= 767…

    Wondering if I can set up the viewport something like this:

    <?php wp_head(); ?>
        <meta name="viewport" id="viewport" content="width=device-width, target-densitydpi=device-dpi">

 		<?php if (is_mobile()) : ?>
		<script type='text/javascript'>
            if (screen.width > 767) {
     	document.getElementById("viewport").setAttribute("content", "width=device-width; target-densitydpi=device-dpi");
    	}
		</script>

    <?php if (!is_ipad()) : ?>
		<script type='text/javascript'>
            if (screen.width <= 767) {
     	document.getElementById("viewport").setAttribute("content", "width=device-width");
    	}
		</script>
	<?php endif ?><?php endif ?>

    Note: I am excluding the iPad due to many reports of iPads getting the mobile version for an unknown reason. This is also a problem with a couple of Nexus tablets, so I thought if I just excluded tablets !is_tablet() then it would work, but it caused a lot of problems so I stopped using that.

    Is something like this possible? Is there something I can modify in the plugin code that will allow me to add <= 767 to the list of things that mean is_mobile() ?

    Thank you so much for reading. Any pointer in the right direction is appreciated.

    Thread Starter SN0WKRASH

    (@sn0wkrash)

    Marking as resolved.

    Thread Starter SN0WKRASH

    (@sn0wkrash)

    So, this looks to have been a product of Google’s klunky authentication process used by the Yoast GA plugin.

    In case any one else is having problems with this, here is what we did to resolve it.

    We had followed all instructions multiple times but suddenly our GA Real-Time Analytics numbers dropped like a rock, so we knew that authentication was not happening properly. We purged all our caches on the server, deleted cookies and purged cache in the browser, re-authenticated with the correct property and purged caches once again on the server. It now works.

    Okay, I got it…

    I am not using a shortcode, but I realized I can’t use the userid the way the plugin author describes. I took the cue from @valuser – I logged into my youtube channel and saw this at the end of the URL: UCfaFafye0-ftr3roPVRU-Fg THAT is what I plugged into my widget as my userid instead of the username the way the author describes.

    After I used @quacos patch, and AFTER I unchecked the cache option on the widget…. IT WORKS!

    Oh, thank you everyone for your help! That was painful, but in the end, an easy fix for someone who comes across this now.

    If using widgets and using userid:

    1) get your real user id by logging into the youtube channel and grabbing it from the URL at the end
    2) Plug that in to your widget as your userid
    3) replace your youtube-channel-gallery.php file with the one @quacos posted
    4) be sure to untick the box in the widget for caching, if it is ticked

    Should work now for channel/user ??

    @oxizee Playlist works on sites I have that set up on. User ID (channel name) does not work on any sites I have it set up for that.

    @quacos – Downloaded your file again and pasted it into mine. Still get same error messages, and now, it doesn’t even show the not supported video. I am using the same valid user I always have been. Instead of videos it outputs all of this:

    Warning: simplexml_load_string(): Entity: line 2: parser error : AttValue: " or ' expected in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): <html lang=en> in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): ^ in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): Entity: line 2: parser error : attributes construct error in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): <html lang=en> in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): ^ in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): Entity: line 2: parser error : Couldn't find end of Start Tag html line 2 in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): <html lang=en> in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): ^ in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): Entity: line 2: parser error : Extra content at the end of the document in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): <html lang=en> in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557

Warning: simplexml_load_string(): ^ in .../wp-content/plugins/youtube-channel-gallery/youtube-channel-gallery.php on line 557
Message from server: Not Found. Check in YouTube if the id aBlogtoRead belongs to a user. To locate the id of your user check the FAQ of the plugin.

    @quacos – thank you for the effort, but it’s not working for me. I copied and pasted the entire php code from the file I downloaded from your DropBox.

    Something did change – instead of getting nothing to show up, a black box for the main video does show up, but the first thumbnail is the YouTube sad face not supported icon and no other thumbnails show up. I have 6 video thumbnails set to show. When I change the 6 to “7” in the widget, I just get a ton of error code. Ideas?

    Thank you for trying to help out. If I had the php skill, I’d be helping out.

    Thread Starter SN0WKRASH

    (@sn0wkrash)

    Oh thank you, thank you!

    Yes, works! Thank you.

    After the update, I’ve got the same problem – no output for many, not all articles. Seemingly random, but seeing on pages with pagination (page breaks).

    Disable the plugin and all is well (except no Google Analytics).

    Looks like a recent update has rendered the Focus Keyword feature on our posts unusable. No longer does it reflect the accurate information, but it gives the same erroneous info for ALL posts.

    They ALL now say:

    Article Heading: Yes (1)
    Page title: Yes (1)
    Page URL: Yes (1)
    Content: No
    Meta description: Yes (1)

    When there could be 30 mentions in the content and no mentions anywhere else, it doesn’t matter, it says this same thing now on every post. It looks as though it’s capturing the correct info (the analysis seems accurate when referring to keyword density, for example), but that there’s a breakdown when displaying the right numbers.

    Any ideas? Thanks in advance for your help, we use this feature daily.

    Someone marked this thread as resolved, but it is not.

    Any news? Still broken. We tried it again, but same problem.

    Thread Starter SN0WKRASH

    (@sn0wkrash)

    I completely removed the plugin, then installed a fresh plugin so it would be an updated version. Upon completion of install, it said it was successful, but when I tried to activate it, it pushed me to an empty page and gave this error message:

    “The plugin does not have a valid header.”

    It seems to be activated and it does seem to be working, I’ll be monitoring for any problems.

Viewing 15 replies - 1 through 15 (of 47 total)