Viewing 15 replies - 61 through 75 (of 88 total)
  • In settings, change the Siteurl and Home to the full name so in my case, would be https://www.somesite1.com.

    Did you do this?

    I did not. That is interesting. I may try it. Might solve some odd links I occasionally get. Or might break it. Lol

    When I look in Network/Dashboard/Sites, I see no mapping on either the main site or the new site I just entered. That section is blank.

    Hm. You won’t see it for the main site but you should see it for site 2. Refresh…maybe?

    This is confusing. Just remember…this area is the very heart of caching nightmare. It should be working. Clear ask caches, log out, log back in…

    Thread Starter bloggy2013

    (@bloggy2013)

    Logged out, cleared cache, refreshed, still nothing shows under Mapping in Sites

    I tested editing the site settings and more that site is tossing 404 errors. Pretty sure we don’t want to do that. Lol. I haven’t done it on others. It may be a caching issue as I have a cache plugin running. I’ll try to rest more later today.

    I have not played with those settings before and I’m curious what they do.

    Thread Starter bloggy2013

    (@bloggy2013)

    I’m almost ready to nuke it all and start again.

    Hmmm. I know the feeling. I can’t figure out what is wrong. It feels like you are very close. Like it should be working.

    On a whim…did you map both www and plain? Setting only one to primary?

    Have you opened the site via visit site? Just to make sure it fully created?

    Thread Starter bloggy2013

    (@bloggy2013)

    I’ve not mapped both because I was waiting for an answer. So you mean map both in the Domains section of the mapping plugin right?

    Thread Starter bloggy2013

    (@bloggy2013)

    I added both and still only see the primary network domain.
    Now I see somesite1 mapped to somesite1.com in the Sites listing.

    However, trying it from remote still only takes me to the main site or actually, it’s trying to take me to somesite1.domain.com.

    Even more confusing now.

    Thread Starter bloggy2013

    (@bloggy2013)

    Also, when I mapped both as you suggested, I made the https://www.somesite1.com the primary.

    Are you set up as sub domains or sub folders?

    Try logging out and back in…Just in case. I can’t remember what but I had an issue with something in the site recently that I thought wasn’t working…But was after I logged back in.

    Thread Starter bloggy2013

    (@bloggy2013)

    I set up for sub-domains for this server.
    I cleared the cache, logged in and out several times ??

    I wonder if that has anything to do with it? I’m set up for sub folders. Just guessing.

    Thread Starter bloggy2013

    (@bloggy2013)

    I don’t know. What I do know is that I have a few sub-domain servers working and those were never a problem. They work right from the start.

    Remember that I edited that domain on the site to test it? The site broke. I put it back, but it was still broken. I cleared the cache — still broken. Then I shut down my browser and restarted — and all was well. So weird. I do think that a ton of the issues we have around domain mapping are cache related. There are caches in the browser, the server, and who knows how many stops in between.

    When I look under network admin-> sites, I definitely see both mapping definitions.

    Maybe delete the one that isn’t showing and re-enter it?

Viewing 15 replies - 61 through 75 (of 88 total)
  • The topic ‘Using 0.5.4.3 and WordPress 4.0 bug?’ is closed to new replies.