We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 21122
    • 153 Posts
    Hi there,

    I’ve just transferred a site from a test domain to the live domain, and experienced some problems when I did so.

    I had Wayfinder spitting out some links for a menu, and it seemed to be behaving strangely.

    I had pages within a container (the container is called ’blinds’) and whenever I was on one of those pages, the link Wayfinder would spit out was always wrong. It would try sending me to /blinds/blinds/mypage.html instead of just blinds/mypage.html. When I am on a page on the top level of the site (home.html for instance) the same Wayfinder call works properly and would just lead to blinds/mypage.html.

    It seems to be working fine on the test domain, and the only thig I’ve changed since then are the base href (to the new domain) and my htaccess (also to the new domain details).

    Anybody can shed some light?

    Thanks
      • 28215
      • 4,149 Posts
      You need a <base href="[[++site_url]]" /> tag in your header.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 21122
        • 153 Posts
        Hi Shaun,

        Thanks for this. I always start off with that tag in my header, but because I almost always install the site to a test domain before it goes live, I have issues with this when I go live because the [[++site_url]] placeholder is set to the test domain, and not the live one.

        Do you have any idea what I should do in this case?

        Also, I commented on one of the topics on your blog (Twitter I think), and you’ve yet to reply wink

        Neil
          • 28215
          • 4,149 Posts
          Hi Neil,

          Use [[!++site_url]] then, to make it uncached.

          And also, to move your site, you need to do a few steps as well: http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server

          And I usually don’t reply to direct support requests, as to be honest:

          1. It’s not my job, which is to develop the product
          2. That’s not fair to the community at large, who would benefit much more from a forum post
          3. I simply don’t have time to respond to every single person’s help requests sent to me
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 21122
            • 153 Posts
            Of course Shaun, I understand! smiley

            Anyway, onto the question at hand. The site actually doesn’t move servers. In most cases, we set up a test domain on our servers, then when we’ve finished the site, we transfer the clients domain to our server and just configure IIS to swap them over. This never seems to be a straightforward process however (not as straightforward as I’d like!) and I spent a long time today swapping out a Wayfinder menu with static links because of this (luckily the client wasn’t paying for CMS, I just like to build with MODx anyway).

            So would you suggest using [[!++site_url]] for the test site too? And then it should work when its on a new domain?

            And would I need to follow any of the steps in that link you posted if the site isn’t moving to a new server, merely a new domain?

            Thanks again
              • 28215
              • 4,149 Posts
              Yes, and yes. You’d need to change the *_URL settings in the config file to represent the new domain.
                shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                • 21122
                • 153 Posts
                Excellent. Will keep this in mind for the next time I’m doing this.

                Thanks Shaun.