Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter kaitlyn_

    (@kaitlyn_)

    For clarity, I don’t care about the parallax animation effect.

    I’m using Parallax because it lets me have a 2-layer image in the Big Header Section.

    What I’m hoping for help with is —–>> How to target the top layer of the Big Header Section image with CSS. So I can make it always fully visible <<——

    Thanks ??

    Hi all,

    I’m getting the same error as the OP, also when I try to click “Connect to ChimpMail” from the plugin settings. This is happening on two new 4.0 wordress.org installs. Across browsers.

    My auth info is correct, I’ve double and triple checked on the MailChimp site.

    I contacted MailChimp support and they sent me to this thread.

    Between raazxplorer(op), cfspod, divashadow, cwm00, gorgi888, fujidreams, and myself — SEVEN (7) independent people. I think we can confidently say there is an actual issue, whether or not it can be quickly reproduced.

    mc_elliot — Did you try reproducing the error by using WordPress 4.0? That is probably the problem. Can I expect a fix quickly, or should I move to another MailChimp plug in — because I’m not going to revert to an earlier WP version =p

    Looking forward to hearing updates on this issue! Cheers!

    Thread Starter kaitlyn_

    (@kaitlyn_)

    Thanks obi-wan-kenobi! I’m going to install that plug-in, as the ideal is for google to link right to the new URLs.

    Since that still doesn’t solve the problem of anyone who comes across an old-style URL getting the 404. Most people, even tech people, when they see ‘page not found’ will assume the content is gone before url hacking.

    So what I did was track down the file that makes that “page not found” page. It turns out it lives here:

    blog.kait.us/wp-directory/wp-content/themes/my-theme/404.php

    Since, my PHP is a bit rusty, I just wrote up some Javascript wrapped in a <script> tag and pasted it into the 404.php file.

    I made a big array of all my old and the corresponding new URLs. Perhaps not the cleanest idea, but since there is a set number of posts that were written before I moved to WordPress and that set is not changing, seems good enough. My script goes through that list, comparing each of the ‘old’ urls to the current url of the page, if there’s a match then it redirects me to the corresponding new page.

    This only gets executed when a reader gets the 404 / Page Not Found error. I would still be interested if anyone had any feedback or thoughts of a better way to accomplish this.

    cheers!
    –Kait

    <script>
    
    function redirectFromBloggerURL() {
    
    var bloggerTable = [
    ["https://blog.kait.us/2014/07/stella-cat.html",
    "https://blog.kait.us/2014/07/stella-the-cat/"],
    ["https://blog.kait.us/2014/06/ravenna.html",
    "https://blog.kait.us/2014/06/ravenna/"],
    ["https://blog.kait.us/2014/06/hiking-dolomites.html",
    "https://blog.kait.us/2014/06/hiking-in-the-dolomites/"],
    ["https://blog.kait.us/2014/06/visiting-veneto.html",
    "https://blog.kait.us/2014/06/visiting-emanuele-and-silvia-in-veneto/"]
    ];
    
    var currentURL = document.URL;
    
    var wantedURL = '';
    
    for(var i = 0; i < bloggerTable.length; i++) {
    	currentKeyVal = bloggerTable[i];
    	if (currentURL == currentKeyVal[0]) {
    		wantedURL = currentKeyVal[1];
    		break;
    	}
    }
    
    if (wantedURL != '') {
    	window.location = wantedURL;
    }
    }
    
    redirectFromBloggerURL();
    
    </script>

Viewing 3 replies - 1 through 3 (of 3 total)