Publish all vs publish one page at a time - different results

[mike_kallet]

I added a small annimate gif file to a few of my master pages. When I publish the entire website, some of the pages have some objects incorrect positions, including the .gif, and some sizes for graphics were condensed (other objects). When I publish a page that got clobbered by itself, without making any changes it looks fine.
The website has about 200 pages in total. Using WB version 14.2
Update .. when I open 20 pages and publish all opened pages, it seems to work.
When I publish all pages, close to 200, that's when some of the pages are clobbered.

[Pablo]

When you change the master page, then you will need to republish all pages that use that master page. Because it affects the HTML code of all these pages.

[mike_kallet]

Yes, I did that. When I published using All pages however many pages published incorrectly. When I published 20 pages at a time, using publish open pages, they published correctly.

[Pablo]

Maybe your browser caches the old page?
Or maybe there is an error in the publish log?

[mike_kallet]

I looked at the logs, and everything was successfully loaded.
I had cleared the cashes thinking this might have been the problem, but didn't help.
I even switched from Chrome to Explorer and problem still occurred.
Is it possible WYSIWYG ran into some capacity issue. When I publish the entire website, including all files, the log said their were 669 files, and probably about 1/3 of the files had html issues with the placement and size of some of the Master pages elements. When I just opened about 20 pages and published the logs indicated I had between 49 and 129 files and these all published fine. So I got around the issue, but just opening 20 or so pages at a time and publishing open files, then closing those pages, and opening another 20 more, and publishing those open pages, instead of publishing the entire website at one time. Of course, not the most convenient way, but got all the pages to look good.

[Pablo]

If you are using the 64bit version then you should not run into any storage related issues.
But even if there was a problem then there would be an error message.

Maybe the server storage is full?

[mike_kallet]

No, got plenty of server storage. I'm using bluehost. It's possible they ran out of server storage, but I did this at multiple times, so I don't think so. It works when I publish a series of subsets of the entire website, but I get a different result when I try to publish the entire website at once.

[Pablo]

I have never heard about this behavior before.
To be able to help you, I need a demo project and the exact steps to reproduce this behavior.

Related FAQ:
http://www.wysiwygwebbuilder.com/forum/ ... 10&t=82134

See also:
http://www.wysiwygwebbuilder.com/forum/ ... =5&t=88125

[bkjohns]

Have you checked what you get when you preview or publish to your local hard drive? Perhaps that would help narrow down the source of the issue.

[mike_kallet]

When I preview it looks fine. I haven't checked the local drive however, so that's a good idea. I'll give that a try.

[mike_kallet]

OK. The local files were good when i published the whole website.
I setup a test directory on the hosted server, and published the whole website again. And this time it worked.
So, my only guess at this point is that my hosting provider may have had some issue, that affected the upload work yesterday.
Since I can't reproduce this, I thank you for your time, and consider this an anomaly.
Regards,
Mike