Unpublished pages

[bkjohns]

Why still on the older version of WWB? Did you have issues with the latest?
Also, if it seems to work to local disk have you considered publishing to an empty server side directory and see what happens? Since the vacancies.html seems to be the issue, what exactly are you updating on that page and any other specific settings for that page (different master, different background, etc.)?

[thisazlife]

I can tell you that it's not just a single html file that is the issue. For me it's been a couple different html files that say they have uploaded but they were not updated on the host. From what I can tell of @alan_sh's posts he too is experiencing the same issue; we use different browsers, uploading to different servers, of course different webpages, etc. Having said that I am not saying it's a software error as Pablo has pointed out publishing "all" or "selected" does nothing different but I'm stumped as to what is causing the problem all of a sudden.

[thisazlife]

Yes, I was wondering whether Firefox was holding the page open. But I didn't have time to experiment.

Alan

I use Chrome and/or Edge and experience the same issue.

[thisazlife]

And it's started doing it again. Grr. Is there any extended log file information I can set to see what's going on?

Alan

When you publish from WWB, click publish "publish" then click "edit" and set your log level to "all".

[Pablo]

@thisazlife
If there are no error in the publish log then it's most likely a server related issue.
The software cannot tell if the publish failed if the server reports that it went ok.

What do you see in the log when the log level is set to 'all'?

[thisazlife]

@thisazlife
If there are no error in the publish log then it's most likely a server related issue.
The software cannot tell if the publish failed if the server reports that it went ok.

What do you see in the log when the log level is set to 'all'?

I just set my log to "all" and it doesn't happen every time but will post log and findings when it happens again.
Thanks!

[jerryco]

Can you verify with your host how many users are on their FTP server simultaneously? Mystery errors may be an indication of a server unable to handle the load? Or maybe the disk space is full?

[alan_sh]

I am the only person on the NAS system, although there are about 4 CIF connections open all the time. The system has 32Tb of space and about 15Tb free.

It isn't always the same .html file that is affected. But it's only .html files. And it's not the same .wbs file either as it happens to all the ones I am using.

If I create an empty folder on the NAS and publish there it works the first time. But after that, it's back to erroring. If I create a folder on my PC and publish there, it all seems to work.

I will set the log file to full and see what happens.

I agree with Pablo - it's probably not WWB that's at fault here - but I am blowed if I can see what it is.

I haven't updated from 18.2.2. because there's nothing in 18.3 that I need and when I update (apart from bug fixes), I normally do a full publish and that takes time.

[thisazlife]

...
It isn't always the same .html file that is affected. But it's only .html files. And it's not the same .wbs file either as it happens to all the ones I am using....

Yes, this.

[bkjohns]

"If I create an empty folder on the NAS and publish there it works the first time. But after that, it's back to erroring. If I create a folder on my PC and publish there, it all seems to work."

Seems to indicate a write permissions problem.

As for not updating because there is nothing you want, there are differences to some of the operating files, like the JS version in 18.3 is 3.7.0 and your log file shows an older version. Not saying that is the issue but there may be other files that don't publish to the server but may affect publishing.

Don't you just love these mysterious issues that pop up from time to time? Good luck with this.

[alan_sh]

Interesting that, because my NAS just did an update to node.js - I have since tested it and I couldn't get it to fail. But I'll keep an eye out now.

So, maybe there was something on the NAS that was buggy and they have fixed it.

Alan

[alan_sh]

Tried again today with a small one page update and it's still working.

Alan

[gofrank]

By any chance do you have CloudFlare enabled on your server? I have noticed when CloudFlare is in use, some page content is not updated immediately, even when Ctrl-F5 is pressed repeatedly. The update is typically recognized 12-24 hours later.

[alan_sh]

Not as far as I know. My NAS device is internal to my house.

Alan