iWeb publishing nightmare

Hi folks
I found this solution in a german forum:
http://www.macnews.de/news/76142
Try to understand or translate it

Workaround

Einige haben bereits aufgegeben, und iWeb 1.0.1 wieder aufgespielt. So müssen sie zwar auf neue Funktionen verzichten, dafür arbeitet das Programm fehlerfrei. Andere haben sich nicht abschrecken lassen und weiter gesucht. Und die Lösung gefunden, wie es scheint. Der Anwender mit dem Pseudonym Alxalx schlägt folgenden Workaround vor:

1) Nachdem man die Webseite erstellt hat, lässt man die Webseite von iWeb in einen lokalen Ordner speichern.

2) Auf der iDisk löscht man die alten iWeb-Dateien im Verzeichnis "Web/Sites/iWeb".

3) Jetzt kopiert man die lokalen iWeb-Daten in das iWeb-Verzeichnis der iDisk.

4) Zum Schluss stellt man sicher, dass iWeb beendet ist. Navigiert im Heimverzeichnis in den Ordner "Library/Application Support/iWeb" und lässt sich mit einem rechten Mausklick den Packetinhalt der "Domain"-Datei anzeigen. Darin sucht man die "PrePubllishState.plist" und legt sie in den Papierkorb.

5) Öffnet man danach iWeb, erscheinen die dort angelegten Webseiten "blau". Änderungen an den Dateien lassen sich anschließend fehlerfrei veröffentlichen.

In einem Praxistest in der Redaktion hat dieser Weg tatsächlich zu dem Ergebnis geführt, dass iWeb wieder fehlerfrei arbeitet. Und trotzdem bleibt ein schlechter Beigeschmack: Warten auf ein weiteres Update-Update. (chr)

I catch your point but the fact is that they know that the problem exist. So it is a reply made for this problem and not a basic .Mac reply

That is what I wanted to say

🙂

I used an online translator

Some have already surrendered, and have played iWeb 1.0.1 again. Indeed, thus they must renounce new functions, for it the program works perfectly. Others could not be deterred and had further looked. And the solution found, as it seems. The user with the pseudonym Alxalx hits the following Workaround vor:

1) After one the web page has provided, one leaves the web page from iWeb in a local folder speichern.

2) On iDisk one extinguishes the old iWeb files in the list ' Web/Sites/iWeb '.

3) Now one copies the local iWeb data in the iWeb list iDisk.

4) in the end one makes sure that iWeb is finished. Navigated in the home list in the folder ' Library/Application Support/iWeb ' and lets itself indicate with a right mouse click to the Packetinhalt of the ' Domain ' file. In it one searches the 'PrePubllishState.plist' and lays them in the Papierkorb.

5) Opening one afterwards iWeb, the web pages invested there seem "blue". Afterwards changes in the files can be published perfectly.

In a practise test in the editorial staff this way has really led to the result that iWeb works again perfectly. And, nevertheless, a bad flavor remains: Vantage points on another update update.

Where do we provide feedback to apple on iweb? could someone post a link please. thanks

Same problems here as with everyone, unable to publish, dumb error messages.

We do daily blogs of the new baby for family.....I really want to get this working again.

iWeb 1.1 SOLUTION FOR DOTMAC USERS???

Hi, here is a possible solution for people publishing to dotmac.

In iWeb, publish your site to a folder - save it somewhere on your system.

There should be TWO items: your "site" folder and an index.html file.

Navigate to your iDisk/Web/Sites/iWeb and locate your site folder AND an index.html.

Make sure you are IN the iWeb folder.

REMOVE these two items (YOU CAN TRASH THEM, BUT BEST MOVE THEM SOMEWHERE SAFE). This may take some time - site size and internet speeds.

Now copy the two items: (your "site" folder and an index.html file) that you previously published to your system, INTO THE IWEB FOLDER ON YOUR IDISK. Once again this may take some time ("zo find zomething else to do...").

If you find that there is no iWeb folder on your iDisk , have another go at trying to publish from iWeb to your dotmac. When it fails there is a good chance that at least it will have got as far as creating it - NOW REPEAT ABOVE.

Hope this helps, it worked for me, see: Recordiauawen.com

Good luck


G5 Dual 2.0 Mac OS X (10.4.6)

Where is the Isle of Anglesey? It looks beautiful.

There does not seem to be much progress from Apple on this issue, you would at least think they could acknowledge the issue exists.

I have managed to publish my web site but it's very hit and miss, and I had to rebuild the site and then publish it a page at a time.

Although there are still problems, I have added some photos to a photos page and I get an error message as usual, although I can see that iWeb does in fact carry on and complete the page. I just have to live with the 'red' unpublished highlight in iWeb.

Searches still don't appear to work they don't return any results for me, but I have had success with using comments.

I guess we will see a revised version of iWeb sometime, but in the mean time this is not doing the Apple ease of use message much good is it. Talk about 'things that just work', not in this case.

I think I am more aggrieved because I have paid for iLife '06 (I did not get it free on my Mac, I got iLife '04 on my iMac when I bought it). I always buy the annual update and I have been a .Mac subscriber since it changed from iTools. Seeing as we are in fact paying for the software and the .Mac service I think we should expect a better level of quality and service from Apple.

Either .Mac and iLife are tools they want to promote as mainstream or they are not. If they are then let's see the support they and we deserve.

Imagine all the new MacBook owners who will have iLife '06 installed (many of them switchers, who will no doubt have been pushed to purchase .Mac with the new machine), they get home, use their new machine, and get a software update for iLife, they then use iWeb and find it does not work, not a good first experience.

What is even more surprising is that Apple are still offering the iWeb 1.1 update on the download page. I am sure they would have less issues if they withdrew it until the problem was solved rather than letting more people update and then have these issues.

Ian

Off the coast of North West Wales in the UK - separated from the mainland by the Menai Straits.
Glad you like it, it's better when the sun is shining.

Done, no success 😟
Back to 1.0, re-update to 1.1.... no

Is there still no fix?

I removed iComment but still have the same png error

Yes what about the code

I am actually not shocked at all.
Sad, but true.

Apple attention to detail over the years is lagging.

I also cannot publsih and I'm having the same error

APPLE, PLEASE WAKE UP AND FIX THIS
OR, TELL US THAT YOU ARE FIXING IT!
SAY SOMETHING

I used to be able to publish from anywhere, now I can't
I used to be able to publish from different macs, now I can't
I used to be able to quickly take movies from my camera in iphoto and publish them.. now I can't

The family pack doesn't make any sense if you have to publish from one mac only.

why is there no 'option' sign on US keyboards ? (they are in the menu's and every other countries keyboards).. the list goes on and on.

I use my iweb page for my business.. I completely rely on it.

I am now completely screwed.

thank you apple yay !

Mac OS X (10.4.6)

Everything is working fine for me now, so blaming Apple is just silly.
Most people must of used iComment or iWeb enhancer get rid of it at least iComment i don't know about enhancer i never used it.

These programs edit the code "hallo".

I did have all the above problems but after not running iComment even statcounter through iComment.

It does work!

My iWeb is completely stock with enhancers or addons or whatever I still can't publish.