maryjanesfarm

Forum Replies Created

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

  • Me too. Uninstall brings back the widgets, but I want to be able to use Google Analytics. Any updates to this issue????

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Yep. Looks surprisingly exactly the same… ??

    Good!

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Also, along similar lines — now that I’m replacing my modifications after updating Print-o-matic (and having forgotten initially that I had modified it) — I’ve added the following into the printomat.js file @ line 33 (after var w = window.open…):

    w.document.write("<!DOCTYPE html><html><head></head><body></body></html>");

    If I remember correctly, this was necessary as well in getting Internet Explorer to work as desired. (It was certainly only IE throwing a fit just now w/o my 2 modifications in there.)

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    OK. Heard back and resolved the issue, it seems.

    Not at all what I’d expected.
    Windows 7 x64 at church and home, with a Samsung Android tablet. IE 8, with Opera as the browser of choice.

    Removing AdSense resolved the issue. Squared it away on my phone, too – no need to select “Desktop view” now.

    I found a few things in searches about AdSense causing blank screens. I’ll keep looking further for why this would be an issue. I’m especially wondering about the ad-randomizing function in relation to AdSense. Maybe those conflict. It could be that leaving AdSense but removing the randomizing function would work, too. All sorts of combos to try, and since the user’s system is Win 7 x64, all I’d have to do is reset to IE 8 to see if I see the same.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Yes, it was good to learn how scripts were intended to be handled in WordPress, and that it was already calling jQuery in some fashion.

    Even if I derived from a newer theme, it would still be the desire that I create a fixed-width theme (effectively). There’s not much call in this venue for fluidity or adaptability.

    But, thanks again for your help. And songdogtech, too!

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Well, this is why I make slow progress learning programming…
    OK!
    Finally removed duplicate call to a jQuery library; moved all my head Javascript to external files and determined how to link Javascript files “the right way” so they could actually access jQuery; spent time troubleshooting why $ wouldn’t work anymore (assign random variable like $j the jQuery object reference, since apparently there was some sort of conflict over $ once I removed my call to a jQuery library); duplicated the PHP info that was readily available in head to make it available to an external Javascript file; and all seems to work still, again.

    Correct my assumption that JetPack inserts the call to jQuery. jQuery is built into WordPress. Probably the reason I didn’t realize this initially is because of the conflict over $, and so thought jQuery was not available. Dunno.

    Also, my phone stopped displaying the page properly once I went through this process. So, apparently duplicate jQuery calls were not the answer for that. But! I happened to run across a setting for the page, “Desktop View”, click that … golden. I’m assuming the phone won’t display the page normally because it looks for or gets dumped over into a mobile view, except there’s no mobile stylesheet.

    (If I click “View Mobile Site” at the bottom [from JetPack, I’m more certain this time], I do get a workable mobile site.)

    Anyway, still have to find out whether any of these changes affect the end user on IE.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    @songdogtech

    Well, now you’re raining on my parade.
    I hadn’t noticed the duplicate JQuery library. I’m assuming the 2nd is Jetpack. I’ll just have to get rid of the request I had originally.
    At this point, until I know better, I’m just setting sites to pull in a static version of JQuery so I know it won’t go and change on me. Thus, if my JS worked when I made it, better bet than relying on it remaining stable with the web’s love for constant change.

    As for the old-school stuff, I would love to update it. At the time, it was the only way I knew to reliably and quickly get the design to work. Relying on JS, CSS, and user’s having newer browsers … that’s not an option for the audience I’m often building for. (I’m still always holding my breath when I push the envelope with all this fancy CSS 2 on the sites I build. Thank heavens for JQuery, or I’d have had to abandon all JS, since I could never make it work reliably across browsers with my knowledge level, even w/ the internet as a reference. I still often have to answer for having tried to do something “fancy” or “modern”.)
    I still don’t know that I could build a more reliable structure today than a table for the stupid design I was handed; and not risk any given browser deciding to add its own space, or dump something down to a new line, or display nothing because there’s no real content but a background-image. Not without using lots of CSS/JS/browser-specific hacks and tricks and such, which I hate.

    As for changing the Doctype, not to be smart, but I did change it, and it did work. And has worked fabulously for years. If new browser versions come along and play properly with HTML, CSS, JS, etc and mess up my mojo… well, that’s something else and I’ll have to be utterly proper, then, with my HTML markup.
    I understand that does make it hard for others to troubleshoot and to trust my design decisions aren’t the issue.

    So I hear you that it’s more likely the theme on any given issue; but given that the only changes were sidebar images, some Javascript, and the post content, and when I see things working well on all the browsers I have access to (ignoring mobile), what with all the other frequent updates in browsers and platforms and such, there’s no way I can assume even WordPress remains viable across all platforms, esp given it’s last update was in Feb or earlier (eeeeons ago).
    That’s why I came running here to check on issues. ??

    Heck, to my point: I would think that Google AdSense would be unquestionable. It’s Google! But, there it is having issues on my Android phone.
    Having said that, though, I obviously must troubleshoot what you mentioned about duplicate JQuery calls and how such things possibly cause conflicts in plug-ins and other grab-n-go code; as well as the modification I made to the code Google handed out, so I could not have ads display on my test site, but also not fiddle with the code every time I jump between pasting the sidebar content in my test site and my live site.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Well, here’s a juicy tidbit. Now that I’ve removed AdSense, my phone is no longer blanking out.
    And, paid a visit to the only other site I’ve placed AdSense on (non-WP) – that site also does not display: loads, then *poof* blank white.

    So, my phone (at least) does not like AdSense. Funny, given it’s Android OS.

    1 down; 1 to go.
    I’ll have to wait now to hear back from our visitor with the blank screen who uses IE.

    I was going to try the SCRIPT_DEBUG on my test WP installation, but the only thing I had to see whether that helps was my phone. Since AdSense took care of its issue, I no longer care about that.

    Resetting IE didn’t help thepioneerwoman.com on my computer. Since I haven’t had any issues w/ IE for my own site, that doesn’t exactly matter much anyway.

    Well, thanks for all the prodding and prompting on things to check, WPyogi! I’ll let you know if I hear back from our user.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Pretty sure there’s no JS errors, because I’m not so comfortable with JS, so I usually check it pretty well (and it mostly just plain ol’ doesn’t work when I do get errors).
    AdSense show_ads was displaying an error in Firefox with an asynchronous document.write(); but I just decided to remove AdSense for a bit while troubleshooting. So that’s gone now.

    …
    XD
    I can’t believe this is an error in IE’s console:
    SEC7115: :visited and :link styles can only differ by color. Some styles were not applied to :visited.
    hehe hehe Apparently someone had problems with that. Holy hyper-control fetish, batman.
    OK. I’m done now.
    …

    Yep, pretty sure there’re no JS errors.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    I could certainly imagine it’s largely themes that are the issue.
    I could also imagine my theme doesn’t do so well on mobile, having had no thought put to that – though it shouldn’t just go blank after loading, unless all non-mobilized sites did that on my phone (which they don’t). I don’t have anything that complex going on.

    It just seems the oddest thing, and I’m having troubles imagining what to even ask the visitor to troubleshoot, if they’ve been viewing the site all along and only just started having problems. Even if they updated to IE10, that can’t be it, because no one around my network has had obvious issues – if they use IE, they’re on IE10 now (except the one XP user who refuses to be upgraded).

    The only aspect that has been getting modified much is adding more Javascript to handle things like randomizing the display order of content in the sidebar. But if that works for me and my other network users here, it should be good in general. And it shouldn’t make a whole page go blank, unless JQuery is not working well on newer browsers. Can’t imagine that … just like WordPress having issues en-masse. These are staples of the web, and so if a new browser doesn’t play well with them, I’d think there’d be a large stink being raised.

    I can imagine that I would write or modify code such that it messes up in particular circumstances; but given that I can see another WordPress site “blanking out” in [whatever version of] IE, that suggests there’s something more occurring than just errors that I myself created. Could be plugins we both happen to have in common.
    …
    Then again, all the issues I’ve seen could, of course, be 100% unrelated.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    That’s just me changing the comments that came with Twenty Ten to reflect that I had changed it. ?? They effectively mean nothing, since it’s not exactly a distributable theme. It’s been that way for the life of this site.

    So, also, no, I haven’t updated the theme to capture anything that might’ve happened to Twenty Ten since I first made the theme, or that might’ve been improved in Twenty Eleven or Twenty Twelve.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Validation turns up some things. Though I don’t know for sure, I’d have a hard time believing they’d kill a page.

    Since I’ve declared the newer HTML5 Doctype, the vast majority of the errors pertain to me having left name attributes on some images and all the old cellspacing/cellpadding-type attributes on tables wherever I’ve used them, mostly in the header.
    It reports an issue w/ the Facebook XMLNS, of course; and an issue with a style element inserted at the bottom of the body element.

    For CSS, there was only one margin-bottom that should’ve been a margin, and a bunch of -moz and -webkit statements it didn’t like, mostly for border-radius, and some to do with the CSS I was going to look at (that came in Twenty Ten) -webkit-text-size-adjust for “=Mobile Safari”.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    My main thinking in comparing the other site is to see whether WordPress might have certain issues with IE10 because IE10 is so new. WP itself doesn’t recognize it. So, will definitely have to get more info from the other user to clarify that issue.

    Comparing to a site that has a mobile theme can help figure out whether my phone’s issue is w/ WP itself or a lack of mobile theme; and from that, too, whether my phone’s issue is at all relevant to the user’s IE issue. Very suspicious that the issues are similar – that’s why my thinking goes towards comparing other WP sites.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Oh! sheesh. I even know that, duh, but it wasn’t occurring to me what’s happening with a function that’s echoing (by default). And that’s probably where the untagged printout on the page was coming from, which once printed left the conditional check unverified (as you’re pointing out) so that it wouldn’t echo the entire tag and title set.

    So many little things I have to keep straight in programming still. Thank you.

    Thread Starter maryjanesfarm

    (@maryjanesfarm)

    Whee! What the heck!? That makes even less sense.

    Oh, wait! I need the inverse – if ( get_the_title() ) … [removed the NOT operator].

    Without the NOT operator, yes, that works – no heading tags when the title is empty; heading tags written out along with the title when it has content.

    I don’t know what the effective difference is between what you did and what I did, except that yours works.
    Well, if you’ve got an explanation, great; either way, thank you for looking that over. ??

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