Unpublished pages

[thisazlife]

I'm recently on 18.3.1
Sometimes, more frequently recently, I publish the Entire site, clear browser cache and some pages don't updated. To fix I have to go to the page that didn't update and select, "Selected Page Only" and publish. Any idea why this might be happening all of a sudden? Is there a log I can turn on or reference? Thanks so much!

[Pablo]

There is no difference between publishing all pages of only a selected page. In both cases the exact same functionality is used.
But maybe the server space is full or is there another error that prevent the files form being uploaded?
It is difficult to say anything meaningful about this without seeing the publish log.

[bkjohns]

Are you clearing the cache via Ctrl-F5 or just F5? Also you might try publishing all pages if you are now only publishing updated pages.

[thisazlife]

First publish of all, one html file did not update. Second publish it did publish.
No errors.
Any other ideas what might be causing it?

31/07/2023 12:00:59.806 *** START OF PUBLISH ***
31/07/2023 12:00:59.806 Scanning publish folder...
31/07/2023 12:00:59.818 Found 449 file(s).
31/07/2023 12:01:47.943 Removing temporary files...
31/07/2023 12:01:47.944 Successfully published!
31/07/2023 12:01:47.944 *** END OF PUBLISH ***
31/07/2023 12:20:42.074 *** START OF PUBLISH ***
31/07/2023 12:20:42.074 Scanning publish folder...
31/07/2023 12:20:42.074 Found 21 file(s).
31/07/2023 12:20:44.985 Removing temporary files...
31/07/2023 12:20:44.985 Successfully published!
31/07/2023 12:20:44.985 *** END OF PUBLISH ***

[alan_sh]

I've had something similar - do a full publish and every page is updated apart from index.html. Choose a different location (empty) and do it again and all pages get updated. Log files say all successful in both cases.

I haven't gone into any detail as to why this is happening yet - and I'm still on 18.2.2. So, more work to do. I don't think it's WWB, but something weird is going on.

Alan

[thisazlife]

Yes it started with that version and stated with index file. I published over and over but index would not update. Permissions were as all other files. Finally I deleted index and it updated just fine. Logs always show successful. Today it was a different html file that wouldn't update when publish "all site" but did update when selected only. If you figure it out please post here. Thanks so much.

[thisazlife]

Are you clearing the cache via Ctrl-F5 or just F5? Also you might try publishing all pages if you are now only publishing updated pages.

I actually go into browser settings and delete all cache and then do Shift+F5 for reload without cache. I publish, "Entire Web Site", "Publish all files".
Log shows complete without issue.
Clear browser cache, shift+f5, page isn't updated. Publish entire side again, still not updated. Publish, "Selected Page Only", "Publish all files" and 9 times out of 10 it will then update but on occasion I have to delete the html file manually. I don't see any difference in the html file permissions from any other html file so can't figure out what the issue is. I appreciate your input.

[Pablo]

Please set the log level to 'all'.

The software will publish all files the same way. So, the page name does not matter.
If there is a problem then it's usually on the server side. For example, the file may be read-only.

[alan_sh]

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

Alan

[alan_sh]

Well, it happened again today. The log file says everything is OK, but the html file is not updated. It's vacancies.html

*** START OF PUBLISH ***
Scanning publish folder...
Found 24 file(s).
Copying 'font-awesome.min.css'...
Copying 'New_gmnscouts_18-all.css'...
Copying 'vacancies.css'...
Copying 'fleur-de-lis-marque-purple-32-16.ico'...
Copying 'fontawesome-webfont.eot'...
Copying 'fontawesome-webfont.svg'...
Copying 'fontawesome-webfont.ttf'...
Copying 'fontawesome-webfont.woff'...
Copying 'fontawesome-webfont.woff2'...
Copying 'FontAwesome.otf'...
Copying '81lhtf72ou.jpg'...
Copying 'img0001.png'...
Copying 'img0001_over.png'...
Copying 'img0003.png'...
Copying 'img0003_over.png'...
Copying 'img0006.png'...
Copying 'img0008.png'...
Copying 'logo-stacked-purple-jpg.jpg'...
Copying 'mastercover5-2800.jpg'...
Copying 'jquery-3.6.4.min.js'...
Copying 'DC-Search-pack-Bolton-South-w-Farnworth.pdf'...
Copying 'searchindex.js'...
Copying 'vacancies.html'...
Copying 'wb.sitesearch.min.js'...
Removing temporary files...
Successfully published!
*** END OF PUBLISH ***

When I looked, the html file still had a modified date of 2 days ago. And I did do a refresh.

I'm publishing to a file share on my NAS server. I'll experiment with publishing to a local folder on my PC. Is there a way to get more information into the log file?

Alan

[alan_sh]

OK - panic over (I hope).

I tried publishing to a local disk. All worked fine, including republishing.

I then rebooted my NAS server and that seems to have done the trick. I'll keep an eye on it.

Alan

[WWBman]

Just one thing I noticed.
Files should not begin with a number (81lhtf72ou.jpg).
viewtopic.php?t=131

[alan_sh]

Just one thing I noticed.
Files should not begin with a number (81lhtf72ou.jpg).
viewtopic.php?t=131

Humm, I wonder where that came from. It's not one of mine. Thanks for noticing - I will investigate.

Alan

[alan_sh]

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

[Pablo]

Based on your previous log it does not look like you have set the log level to 'all'

However, I doubt that this has anything to do with WWB. The software works the same every time you use it. The exact same instructions will be used each time!
If the server reports that the transfer was correct then there is no way to know if or why it failed.

[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