unable to make changes to my website on new host

tom-durkin wrote on 10/20/2021, 12:26 PM

Because Xara/Magix does not support SSL, I migrated my website to siteground.com. I have Xara Web Designer Premium 18.5.0.62892 DL x64 Aug 11 2021 running on a x64 laptop using Windows 10. My changes to my website clearly upload to siteground - and siteground tells me the files are definitely appearing on their server, but they can't explain why the uploaded pages are not changing the website. They say it must be a flaw or cache that needs to be cleared in my Xara program. My website is https://tomdurkin-media.net/

Comments

emmrecs wrote on 10/20/2021, 1:42 PM

@tom-durkin

I cannot access your site via the address you give. I receive an error message "This site can't be reached", suggesting there is a possible typo in the address you give.

The most common reason for web pages seeming to not update is because the "old" version of such pages is in your Internet cache on your computer. Because your computer thinks you already have those pages it does not download and show you the "new" version. To check (and resolve) this, with one of the "old" pages open on your computer, press F5 or, perhaps better, Ctrl+F5 (to force the cache to be refreshed). Can you now see the "new" page(s)?

Jeff
Forum Moderator

tom-durkin wrote on 10/20/2021, 3:33 PM

Thank you. Jeff. This is definitely my website: https://tomdurkin-media.net/ I don't know why you can't see it. I have cleared caches on my browser and at siteground, I have rebooted, I have refreshed with F5 and Ctrl+F5, talked with siteground. Nothing is working. Siteground confirms my revised pages are uploading, but somehow they are not changing my website. Siteground is telling me there's something wrong with my program or cache in the program. Nothing in the documentation for Xara says anything about a cache. I don't know what else to do. Do you have any other ideas?

browj2 wrote on 10/23/2021, 2:15 PM

@tom-durkin

Hi,

Can you show us a screen shot of a page that you see that shows up as not changed and a screen shot from Xara that shows the changed page that you uploaded?

BTW, clicking on some of the menu items opens the page in a new window, so I end up with multiple windows. Check the parameters for your sub-menus so that they do not open in a new window.

John CB

tom-durkin wrote on 10/23/2021, 8:33 PM

@browj2

The site is finally working. I think what was happening was that web host SiteGround was set up with a public_html folder and Xara was uploading its own public_html, and they conflicted. My best guess is that SiteGround removed its public_html, letting Xara load its public_html. Last time I talked with them, they told me I had to change how Xara/Magix uploaded. That left me dead in the water since I didn't see any way to even see how Xara uploaded beyond the Publish dialog box. I was surprised to accidentally discover things were finally working properly, so I honestly don't know what the problem was, who fixed it or how it got fixed.

I'll look at how the windows open. If it goes offsite, it's definitely going to a new window. Maybe I'll let it open in the same window for internal links.

Thanks for trying to help.

Tom

johnebaker wrote on 10/24/2021, 3:06 PM

@tom-durkin

. . . . I think what was happening was that web host SiteGround was set up with a public_html folder and Xara was uploading its own public_html, and they conflicted. . . .

In the Publish settings did you set the Sub folder (optional), indicated in the image below, to public_html ?

If so, then this is unnecessary as by default the username and password for uploading (FTP'ing) to your host should already point to the correct folder where your site is to be published.

Setting the subfolder option told Web Designer to create a subfolder in the default folder so that your site was actually in public_html/public_html.

HTH

John EB
Forum Moderator

tom-durkin wrote on 10/27/2021, 10:09 AM

As I saw it in the FTP folder, Xara was bypassing and not uploading to public_html as it should have. I believe that was a problem with SiteGround. Whatever. The problem has been solved. Thank you for your help.