Old site publishing over new site.

  • 1
  • Problem
  • Updated 7 years ago
  • In Progress
Basically, I made a new version of my site the other day, which involved unpublishing the original site, at a .yolasite address, before publishing the new site, which was created as a separate site. I published the new version of the site at the .yolasite domain the original was on, and all seemed to be working smoothly. The old version remained in My Yola, unpublished, as a back-up, with no domain assigned.

However, it is showing up under the domain in place of the new site. This is most irregular, as Yola reports it as unpublished, with me even going to the extend of re-publishing the old site at a different .yolasite address, and then unpublishing that.

This is an awful issue. I hope I can resolve it ASAP.

The address is: http://www.tvpresuk.yolasite.com
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
  • frustrated

Posted 7 years ago

  • 1
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
At the moment, it has flickered over to the new version. It appears to fluctuate.
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
Now though, it has fluctuated over to the old version. Extremely irritating.
Photo of Emmy

Emmy

  • 5892 Posts
  • 299 Reply Likes
Hello Jim,
That does sound very irritating. If I am understanding correctly, you have a site in your account published to tvpresuk.yolasite.com as well as a site in the account that used to be published to that domain. Is the problem that the published site itself keeps jumping back and forth between the two? Can you tell me what is currently showing on the home page, or now showing, so that I can compare what is published currently to the two sites in your account.

Thanks,
Emmy
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
Hi Emmy,

Thanks for getting back. You are correct in diagnosing my problem. The new version of the homepage shows a 'Welcome' banner, along with a 'Recently Updated' area, and a Twitter feed where links are highlighted in blue. The old version doesn't have a 'Welcome' banner or 'Recently updated' section, and the Twitter links are highlighted in Green.

It seems to happen most commonly around times when I've republished the new site as it has been updated.

Also, I've noted that whilst the homepage switches to the current version of the site sometimes, clicking a link or navigating anyway takes you to the correct page, but it will have lapsed into the old version of the site.

I've even republished the old version of the site to a different .yolasite domain, and then unpublished it, to no avail.

I hope we can solve this issue soon.
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
Thoroughly confused now.

Just re-published my site with an update. Worked normally, and thought the issue may have been resolved.

However, after navigating away and then navigating back, the page slowly began to load. It then redirected itself to the back-up address, where the old homepage is. The back-up homepage and site isn't even published, with the back-up .yolasite domain used for about 15 seconds in an attempt to resolve the issue yesterday, which was to no avail. There is nothing in reference on any part of the site in code to redirect.

Looking again now, it redirects to the page, but instead with the 'This subdomain isn't in use' message.
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
I thought I'd bump this up now.

Basically, it appears that Yola, without prompt, is redirecting to a URL that isn't published, with a homepage where the banner hasn't even loaded.

I've just cleared my cache to check it isn't me, but that hasn't helped.
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
I'm positive of the issue now, as users are reporting issues, which initially look to be my own fault. However, I'm next to certain that I've not provoked this by inserting code to redirect or anything.
Photo of Emmy

Emmy

  • 5892 Posts
  • 299 Reply Likes
Hi Jim,
I just wanted to hop on here quick and let you know that I am looking into this right now. I'll post back here within the hour of what I am seeing and how I can help. Thanks much for your continued patience, I know this is frustrating for you.

Emmy
Photo of Emmy

Emmy

  • 5892 Posts
  • 299 Reply Likes
Hi Jim,
I see it, exactly what you are referring to. Right now the published site matches up with the site that is not published in the Sitebuilder.

I am going to log this with our engineering team right now. I know this is a huge inconvenience for you, but can you not touch the site for a few days until we have had a chance to try to debug it. The reason for that is we cannot troubleshoot something that is not replicatable, meaning we need to be seeing the problem too, and I can see it right now. It is Saturday, and I feel it might be Monday before someone will be able to look at this. Let me know if that is ok with you.

Emmy
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
Hello again Emmy,

Thanks for helping out. If it's the only way to go about resolving the issue, then I'll leave it as it is so the Tech's can take a look.

Jim
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
I'm not 100% yet, but it looks like my issue has resolved. No idea if it has just been fixed, as 30 minutes ago it didn't work.

Whilst it took a while to load, which made me dread more errors, it now appears to work as normal.

Can someone clarify if the issue has been fixed?
Photo of Marije

Marije, Official Rep

  • 4636 Posts
  • 237 Reply Likes
Jim - I managed to catch one of our engineers who took a look at the issue and just fixed it a few minutes ago. Thanks for posting the confirmation!
Photo of Jim Trott

Jim Trott

  • 84 Posts
  • 9 Reply Likes
Hi Marije,

Thanks ever so much for that! Therefore, am I able to edit and update the site as normal now? Also, are you able to disclose what the issue was?
Photo of Marije

Marije, Official Rep

  • 4636 Posts
  • 237 Reply Likes
You can definitely carry on as normal with editing and updating. I'm not able to tell you why it was happening other than "technical glitch" - if we do hear other information, we'll let you know.