I Spend most of the time trying to fix Muse's Problems

Question

I'm getting more than a little tired of Muse's unreliability with it's output.
The amount of times I output a website and it 'decides' not to output an image is driving me nuts. It's a never ending cycle of trying to keep the site together.
I output a page. Then there's an image that decides it won't show up. I then open Muse, re-place that image and its shows up on the next output. Then I create the mobile site. Then the mast head on the main site decides to dissappear.
ad inifinitum.
I have this problem since the first version of muse. We are in version 6 and this still happens! I'm trying to build a service offering around this app, but I spend so much time trying to get Muse to do what is says it does, that I waste hours and hours on issues like these.
Here is a screen shot of what it's meant to look like in Muse's Design mode.
Here is the link to the test hosting:
http://www.hollands.com.au/test1
I have opened the FTP site, and cleared the directory and re-uploaded with 'All Files' option in the upload to FTP.  Notice the Twitter bad in the red stripe also missing. I've given up trying to get that to come out. The yellow banners at the top are missing. And there is meant to be one in the footer aswell.
Just venting my frustration...
Can we figure this out? What is going on?

Answer 1

Thus far I've been unable to reproduce the bug you're encountering. I expect the bug is either related to memory management or the specific timing of events related to when the image was last read in off disk (out of the .muse file) by Muse. Either way, I haven't had any luck so far with reproducing the memory environment or timing necessary to reproduce the bug.
Here's some additional information regarding how/when Muse decides to generate and upload new versions of files. It may help you workaround the bug while we continue to attempt to reproduce it so we can track down and fix the underlying cause.
When you Publish, Upload to FTP Host, or Export as HTML, Muse includes a file named manifest.xml. This file stores information about the state of all the pages in the site at the time of the publish/upload/export and all the files that were published, uploaded or exported.
The next time you publish, upload or export, the first step is that Muse grabs the manifest.xml file that already exists. It uses the information in the file to determine which pages have changed (and thus what files need to be generated) and then verifies the data for each generated file is in fact different than what's already present before it takes the time to upload or write the file to disk.
The theory for what's happening when the bug occurs is the an image is failing to draw either due to a poorly handled low memory situation or due to a timing problem where the publish/upload/export process is actually producing the file before Muse has completed creating the image that should appear in the file.
Once this bug has occurred and the blank image file has been uploaded, the information in the manifest.xml will cause Muse to believe everything is up-to-date and a subsequent publish/upload/export will not update the blank image, even if a subsequent publish/upload/export attempt would have created a correct image file.
When the bug has occurred, if you change anything about the page where the error is occurring (i.e. just nudge an item one pixel right then one pixel left), Muse will generate the data for all the files associated with the page and then check to see if the data differs from what's in the files recorded in the manifest.xml during the previous publish/upload/export. Assuming this operation successfully created the image the data will be seen as different and the corrected image file should be published/uploaded/published by this second attempt.
It would be helpful to know whether or not this "alter the page" and re-publish approach works or not, since that knowledge may help us narrow down the root cause of the bug.
If it doesn't work initially, then quit and relaunch Muse, alter the page and re-publish. Doing so will make an out of memory situation very unlikely and it will be likely to change when image is loaded into memory relative to when it's needed by the export process.
My apologies for not having a quicker resolution for this.
Anyone else reading this thread that's encountering the same or similar bug with images exporting as blank, please speak up. Given how difficult it is to reproduce, having multiple example .muse files that have encountered the bug may make it easier to find a common underlying cause. Thanks.