Iweb9 No Longer Publishing

In anticipation of the demise of mobileme, I migrated my website to machighway in April. It uploaded successfully and since then I have updated the site periodically without any issues.
Yesterday when I tried to update the site I got an error message
There was an error communicating with the FTP server. Try again later, or check with your service provider
Nothing has changed except possibly this is my first update since switching to Lion at the end of June.
I've rebooted the computer and tried several times with the same result. My internet is working perfectly.
Could this have killed my ability to seamlessly update my site? The instructions for machighway contain complicated instructions for iweb8 which require exporting to a folder and using a third party FTP application.
Back when I was researching the move, I downloaded demos of some web building applications but since my needs are fairly simple, I decided to stay with iweb9 since it appeared to be working fine with the machighway.
Any suggestions regarding why it isn't publishing? Could Lion have killed it?
Am I better off making the switch to another web building application since eventually iweb is going to be dead given Apple's abandonment.
Thanks.

Thanks.
Oddly I had a problem with bad names for some picture files when I first migrated from mobileme to machighway but the error presented itself with a slightly different message so I assumed it was related to the Lion upgrade.
But when I checked carefully some of my new web pages had been successfully loaded and when checking further, those pages which were still "red" in iweb (indicating not having been successfully published) were actually published except for one or two pictures.
The two pictures turned out to be the culprits so I deleted from iphoto - corrected the name (space before the .jpg suffix) - opened back up in iphoto and then added to iweb and republished with success this time.
Strange that it gave me a slightly different error message this time.

Similar Messages

I can no longer publish my ICal work calendar

Just updated to the new calendar in mobile me but it deleted all previous calendars that were on my iCal app on desktop computer. Fixed that with apple's help, but can no longer publish new calendar updates that are created on home desk top computer/ical (not mobile me). The radio beacon is no longer present on the work calendar that has been published for 5 years and in the tool bar under Calendar "published" is not able to be selected. I have 81 mb of my iDisk being used and over 9 gb of free space. Any help/ideas out there. Thank you.

This is odd: I have no trouble doing this. However I'm on Snow Leopard, so I don't know what difference Leopard makes.
When Apple sorted out your initial problem with the calendars after the upgrade, are you sure they didn't land you with MobileMe calendars? The new calendars live on MobileMe and Leopard can read them and display them in your iCal - I don't know whether it lists them under your MobileMe login name as Snow Leopard does.
Try this: create a new calendar and make sure that it's 'On My Mac'. Add a single event to it just so that there is something there. Can you publish this? If so, then the other calendars probably are on MobileMe and need to be transferred back to your Mac (from where they won't sync with MobileMe).
This is the procedure for shifting calendars back to 'On My Mac':
Select a calendar listed under your MobileMe login name.
From the File menu choose Export...>Export. An .ics file will be saved at your designated destination.
Create a new calendar with the same name as the one you've just exported from, choosing 'On My Mac'.
From the File menu choose Import... Select the .ics file and choose to import it into the calendar you just created (make sure you don't import it into the MobileMe version).
When complete, check that it's OK and then you can delete the MobileMe version.
Repeat for other calendars. I should keep the .ics files for a bit as a safety until you are quite sure everything is correct.

All my games show that: This app is no longer published. How to solve it . My account seems blocked

all my games show that: This app is no longer published. How to solve it . My account seems blocked
my accout:
[email protected]

best is to contact support from your dev center
Microsoft Certified Solutions Developer - Windows Store Apps Using C#

Photo Page will no longer publish new photos

I have an Photo Album with with 12 Photo Pages. Total number of photos in the Album is 364. My newest Page will no longer publish new photos. The Album and Photo Pages, up to now, have been working fine. Is this a case of where I need to break up the Album Page.

The "empty cache" command is gone from the Safari dropdown but Option/Command/E still works and is in the develop menu.
A hard refresh (Shift/Command/R) has been missing for a long time - maybe V 4?
Safari is becoming more and more dumb with every update. I keep saying that its hardly worth testing in Safari since its a minority browser but does anybody listen?
Test your local version in Firefox and the one on the server in Chrome. See my last post in this discussion to see why you should use the error console now and again...
https://discussions.apple.com/thread/4361444?tstart=0

Using iweb 11 I can no longer publish site updates, please help.

I am using iweb 11 and Lion and I can no longer publish site updates, please help.

What a brilliant solution, Roddy. Never would have thought of that.

Very long publishing times

Hi,
since a week know I'm facing problems with very long publishing times.
I also get error messages during publishing which tell me that the "target server failed to respond".
Are there any known issues?
Any help will be appreciated.
Best regards
Felix

If the disk is getting hit VERY hard during the GC, then it is possible that your system is thrash its page file. What else is running besides the Java process? If the total RAM size (not including page file) is smaller than the working set (which during GC basically includes the entire JVM heap) the system will hopelessly thrash.
You probably need a smaller heap, fewer other processes running or more RAM.

IWeb suddenly no longer publishing

Has this long-running issue been solved?
Having enjoyed iWeb problem-free for ages, today it suddenly refuses to publish with an error.
I have deleted the preferences and domain files. I have re-installed. None of it works. I can publish to a folder, but not to .Mac
My connection is just fine. .Mac is not syncing at the time, but iWeb does not want to know. Deleting all pages means that the new file/site menu items get greyed out, so that does not seem to be the way to go.
I have repaired the keychain, and repaired all permissions, in fact I have done a full system maintenance.
I am stumped. Help?
JKB

I have just discovered that I am having the same problem. Got the error saying 'The document 'iWeb" could not be saved' right after "Preparing to publish". It worked fine before. What worries me is the following sequence of events before this:
- yesterday safari all of sudden crashed, closing all the safari windows opened;
- then I did a software update, was told to install a security patch for mac os and to restart. did it;
- some time after that, mac ox suddenly crashed after I launched safari, asking me to force a restart by powering down;
- today after I downloaded photos to iphoto from my canon, I found out that I could not launch the Adjustment window to adjust my photos;
- then I discovered that I could not publish iweb.
I makes me wonder if there is anything seriously bad happening to my macbook. I used to be a windows user. this is my first mac. thought it would be nice and smooth ...
MacBook Pro Mac OS X (10.4.9)
MacBook Pro Mac OS X (10.4.9)

Can no longer publish changes

I've obviously heard that Apple are no longer running MobileMe but I thought it was running until next year.
Have been trying to publish changes to my website via MMe but keep getting message saying 'can't connect to MobileMe'. Admittedly, this has happened since I upgraded to ilife 11.
Any answers anyone?

Try this:
go to the System/MobileMe preference pane and log out of MMe.
login with a bogus username and password like "test" and "test". This clears the caches.
login with your correct username and password.
launch iWeb and try again.
If still not working try the following:
delete the iWeb preference file, com.apple.iWeb.plist, that resides in your Home()/Library/Preferences folder.
go to your Home()/Library/Caches/com.apple.iWeb folder and delete its contents.
launch iWeb and try again.
OT

I can no longer publish iPhoto Journals to iCloud

I have succesfully published and shared many iPhoto Journals to iCloud over the last few months. This was my main reason for purchasing the App.
It no longer works, I just get a spinning wheel and the perpetual indication that the journal is uploading. I have checked my iCloud storage space and have over 4GB of space so that's not the problem. I keep the iPad and Apps up to date. I have also tried deleting iPhoto from the iPad and starting over.
Any ideas or is this a known bug that requires an Apple update in the future?
Thanks!

I have since received AppleCare's advice:
Backup then restore iPad as new.
This worked, albeit a rather frustrating and unelegant solution.

IWeb no longer publishing

My iWeb site http://web.mac.com/longhorn89/iWeb/Site/Library.html no longer works on either my home or work computers. OSX 10.4.11. iWeb 1.1.2. MobileMe is active. Please advise. Thanks in advance.

When did you notice that the site couldn't be found? When was the last time you updated the site? If it's been a while, several months the .mac sites have been changed to .me sites and the sites are being published to your iDisk/Web/Sites folder. Files in other folders on the iDisk are no longer reachable online.
Try this:
go to the System/MobileMe preference pane and log out of MMe.
login with a bogus username and password like "test" and "test". This clears the caches.
login with your correct username and password, launch iWeb and try again.
republish your site in full.
then try this URL to get to your site: http://web.me.com/longhorn89/
See if you can find your site now.
OT

Why? Why will it no longer publish?

I run iWeb 2.0.2. I have a 5 section web site with pictures in it. I used to publish it ok, up to my last series of additions of this morning :
- added a gallery with Widget Web
- edited some typos here and there
- created a new site with a blog in it and more photos (different theme, different subject altogether)
- deleted it since it did not seem to be able to even complete its initial publishing step at all.
Now the site saves ok, publishes to a folder ok, but will not publish to .mac. The site folder is 77 MB in size while the domain.site2 file is 240MB. It takes a heck of a long time to let me know that there is apparently a problem accessing my .mac account. Fact is, my .mac account is perfectly ok, has lots of room to grow and is in order in all possible manners!
I also noticed that now all the pages icons in iWeb are red, even those pages that I have not edited at all for a long time. They used to remain blue if I did not touch them.
So iWeb 2.0.2... are you for real or are you a bomb to crash Apple stock?? I just cannot beleive the number of probems that iWeb has created since its new arrival as part of iLife8. Truly a catastrophy.
Meanwhile... anyone has an idea? Is there a timeout issue involved here? Can it be corrected? Should I try to upload from folder to iDisk? Where exactly? I wish I did not have to futts around like that.
URL : http://web.mac.com/flaroche (online version before my desired changes. Can I back it up?)
Message was edited by: flaroche

Posted By: Mark W.
Created in: Forum: iWeb '08
Posted: Oct 10, 2007 5:00 PM
Apple is aware that some .Mac members have reported recent difficulties publishing from iWeb. Apple is actively working with customers to collect further data to help us better investigate any performance issue. If you'd like to help with this investigation, please contact .Mac Support by visiting http://www.apple.com/support/dotmac/publishing/# and filling out the form.
Thank you

Muse will no longer publish to business catalyst if jpegs are included in file

Hi there,
I'm in a pickle and hope someone has a solutuion to my bizzare problem.
Since the last Muse update I am unable to publish to my unlaunched business catalyst site.
The error message always comes up at overall publish progress 61% complete and is:
'Error uploading file '...'.jpeg. There was no response from the server. Check your network connection and try again. If this problem persists try again later.'
My network connection is working well.
I have narrowed down the problem to image files. If I remove all the jpegs in my Muse file it publishes without a problem.
Has anybody experienced this issue???
Thank you for your help!!

Zak,
I reported this issue on the 8th of April. http://forums.adobe.com/thread/1445684?tstart=0
On the 16th, I was able to publish to my test blog site while responding to your reply. This appeared to have been a case of leaving the dialog box up for a period of time wherein it seemed to automatically try again and succeeded. I did not find a "solution" to the problem, I was just "lucky" in that 1 out of roughly 50 attempts to publish, and after leaving the dialog up without clicking anything, the site did in fact publish.
I recommended continuing to look into the issue but haven't received a response since. Others are now experiencing the same or similar issues relating to images being in the site files.
I confirmed in my thread that this issue isn't isolated to one particular filetype or file size. For me it always appears to be the very first image file Muse tries to upload, some 60+% of the way through - and this seems to be whatever is set to be the background fill. I wonder if anyone else is using an image as a background fill as well? If no image is used as a background fill and they choose a colour, which file does it hang on? Is the image attached to anything (ie a setting, a fill, a slideshow etc.)? Or is it simply a placed image?
For me, this has ONLY been occuring since the latest Muse update (April 2nd) and I believe it to be an issue between Muse's attempts to upload and the BC servers. Perhaps it's a timeout issue pertaining to uploading image files?
My issue began when trying to use an abnormally large file as a background fill (although this was still well under the 25mb you've referred to), however I reduced this down to a fairly small tiled image and the issue remained. The issue repeated itself when I began cycling through file types.
I can confirm that the bug I'm encountering is NOT where Muse hangs on the attempt to upload the first file. Nor am I using XP or Vista anyway.
I can confirm the publish DOES stop on the same file (in my case), however there are no .swf or .oam files attached to my particular site and the only image files I'm using are either .png (my preferred type) or .jpg - Some of those images have been "optimised" for web in Photoshop. Incidentally, as you've mentioned it, some of my image files use several "-" characters in the filename, but this is not exactly a "special" character and thus I wouldn't think this would be an issue during the upload process.
I can confirm that by clicking "Resume" NO further progress is made. However, as I said above, I left the dialog up for a while and the publish completed on its' own (as if by magic) and I've had no problems publishing to that site since.
Having been forced to delay my latest paid project for over a week now, I cannot delay it any longer and will be beginning work on a new site this coming week and will attempt to publish SOMETHING to a temporary address just to test and see if this issue continues with each new site I create. However, I request this issue becomes a priority for both the Muse and BC teams as it is preventing people (not just myself) from publishing sites - and even committing to projects - and thus potentially losing us all income.
I would prefer not to have to wait for a patch/fix for this while working on this new project as I will appear unprofessional not being able to give dates for project milestones.
Having an issue like this reflects VERY poorly on us, the small agencies or individuals, of whom many have bought into not only the Creative Cloud for Muse, but BC as Premium Partners, meaning we RELY on your services to be able to provide our own. We look bad (and extremely unprofessional) when this stuff happens and personally, having known about this issue for nearly 2 weeks now and having still not seen a solution (besides my ONE lucky publish) I'm growing frustrated and anxious regarding my latest paid project.
I appreciate that you're working on a multitude of problems and are looking into this but I respectfully request this becomes top priority as it's hardly worth it for us if your software/services can't achieve the very goals they set out to do (publish websites) while we sit here twiddling our thumbs not knowing what to do.
I do love Muse and think it's a great tool and will continue to be once further improvements are made (BC is a different story...) but I'm getting increasingly exasperated waiting for this issue to be resolved. I hope you and/or the rest of the team can find a resolution to this problem swiftly (as a priority) and can keep us all in the loop regarding progress on this.
I look forward to a response soon with useful news.
Thanks.

I can no longer Publish my web site changes since I let Face Book be involved in the Publishing.

Seriously- It just freezes somewhere when it asked to update via FB after I hit publish. There's no place to get face book out of the mix! I looked everywhere, Preferences, etc , nada! Help! I've rebooted the program a bunch of times even the computer. Also, now if I hit "publish changes" still freezers.
How can I reset the Publish preferences so it doesn't ask me for my FB log in , etc . I believe that's why it's freezing.
I have a few typos on my web site I'd really like to correct.
Any help is appreciated!
Best,
kyttiegirl

Try publishing to a local folder and then switching back to the iWeb FTP.
If that doesn't work, publish to a local folder and then do the troubleshooting step under "Fix iWeb" here...
http://www.iwebformusicians.com/iWeb/iWeb-Tips.html

Can no longer publish to WL using WS4WL

Hi.
Last week, my Workshop4WebLogic suddenly decided that it would go on a deployment strike. I've tried several negotiation methods, even mortal threats and violence, but the IDE is very persistant.
It spits out the following protest each time I try to perform a rebuild and publish:
Publish failed
Error with publish task 'Controls Assembly'.
Controls assembly failure running assembly on standalone WAR 'TRACK'.
java.lang.NullPointerException: null
Error(s) occurred during assembly. No modules will be published.
I've employed a temporary deployment worker - ANT to function as the deployment manager for Workshop4WebLogic, but this is not an optimal solution. I'm not sure that ANT will write the appropriate Beehive code for me when I compile, so I constantly use clean and rebuild before running ANT. It used to take about 50sek. between the time of a code change and the time I could test the code. Now I use about 110sek.
Could somebody please tell me what this error means, and how to fix it? The server console log does not say anything...

Hi Raj.
I'm using Workshop for Weblogic 9.2.1 build 842050 with the following installed extensions:
* Aptana 0.2.7.13425
* SubClipse 1.0.5
I'm developing on a Dynamic J2EE Web project using Hibernate, Spring, Beehive running on JRockit 90_150_04.
The server domain has one configured datasource referenced by Hibernate.
Extract from .log file:
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:07:20.580
!MESSAGE Deployment manager created @21300451
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:27.871
!MESSAGE Publishing beginning.
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:29.604
!MESSAGE Deployment manager created @24778833
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:31.345
!MESSAGE ***dm.getAvailableModules (initModuleNameCache)
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:34.177
!MESSAGE ***dm.stop (stopModule) TRACK
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:35.553
!MESSAGE Waiting on ProgressObject:@7671005
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:36.313
!MESSAGE ProgressObject completed :@7671005
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:36.316
!MESSAGE Stopped TRACK
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:36.318
!MESSAGE ***dm.undeploy (undeploy) TRACK
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:37.365
!MESSAGE Waiting on ProgressObject:@18594359
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:40.928
!MESSAGE ProgressObject completed :@18594359
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:40.983
!MESSAGE Module TRACK was undeployed sucessfully.
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:42.367
!MESSAGE Releasing deployment manager @24778833
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:42.386
!MESSAGE Publishing finished.
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:12:44.420
!MESSAGE Deployment manager created @13090583
!ENTRY com.bea.wlw.controls.core 4 4 2007-02-08 19:13:00.887
!MESSAGE Failed in attempt to detect callbacks from pageflows. No warnings will be supplied.
!STACK 0
java.lang.NullPointerException
     at com.bea.wlw.controls.core.publish.ControlsClassLoaders.findToolsJar(ControlsClassLoaders.java:143)
     at com.bea.wlw.controls.core.publish.ControlsClassLoaders.createParentClassLoader(ControlsClassLoaders.java:71)
     at com.bea.wlw.controls.core.validation.ControlValidator.build(ControlValidator.java:66)
     at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:593)
     at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
     at org.eclipse.core.runtime.Platform.run(Platform.java:783)
     at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:168)
     at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
     at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:231)
     at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
     at org.eclipse.core.runtime.Platform.run(Platform.java:783)
     at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:234)
     at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:253)
     at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:282)
     at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:211)
     at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.checkAutoBuild(WeblogicServerBehaviour.java:541)
     at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:326)
     at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:301)
     at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:803)
     at org.eclipse.wst.server.core.internal.Server.publish(Server.java:791)
     at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:13:02.219
!MESSAGE Publishing beginning.
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:13:05.734
!MESSAGE Releasing deployment manager @0
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:13:05.737
!MESSAGE Publishing finished.
!ENTRY org.eclipse.wst.server.core 4 0 2007-02-08 19:13:06.53
!MESSAGE Publishing failed
!SUBENTRY 1 com.bea.wlw.server.core 4 0 2007-02-08 19:13:06.53
!MESSAGE Error with publish task 'Controls Assembly'.
!SUBENTRY 2 com.bea.wlw.controls.core 4 4 2007-02-08 19:13:06.53
!MESSAGE Controls assembly failure running assembly on standalone WAR 'TRACK'.
!SUBENTRY 3 com.bea.wlw.controls.core 4 4 2007-02-08 19:13:06.53
!MESSAGE java.lang.NullPointerException: null
!SUBENTRY 1 com.bea.wlw.server.core 4 4000 2007-02-08 19:13:06.53
!MESSAGE Error(s) occurred during publish assembly. No modules will be published.
!ENTRY com.bea.wlw.server.core 1 2000 2007-02-08 19:13:08.871
!MESSAGE Deployment manager created @1563473I will try to create the project anew... But I will have to get back to you on that. I will post this now, and make a new post a little later on...
Thank you for now.

Can no longer publish after latest Muse update (April 2nd 2014)

Hi all,
This issue is two-fold; the first is somewhat minor, but the second is concerning me greatly, particularly as my workload is picking up at the moment...
Every time I attempt to publish (having created the site through Muse - as I find this easier, and I upgrade subsequently) I get a message telling me the BC site has changed and am given the option to "review" the changes or publish anyway. If I hit "review" it automatically skips the "merge" or don't merge screen and makes the choice to "merge" on my behalf (what If I don't want to merge?)... This happens EVERY time I attempt to publish the current site I'm working on.
Sure, I've seen this message before and usually, it only pops up if there's been any changes on the BC side of things which is fair-do's, but this site hasn't actually been published yet - and I'll tell you why in a sec - but yet I'm still getting this message EVERY time I attempt to publish...?!
The funny thing is, nothing on the BC side could've changed because it hasn't successfully published ONCE yet. This is due the second part of my problem where the publish pop-up (progress bar) hangs at aroun 66%, whenever it gets to any image file (regardless of size or format - yes, I've tried numerous varieties).
So, in short, currently I cannot actually publish a site, and every time I attempt to, I'm told changes from the BC side of things need merging with the Muse side...
Anyone got any ideas on what's happening here, if there's anything I can do or whether I can expect an update to fix these (I guess) bugs any time soon? I need to publish this particular site ASAP and have a new commission I'm starting this week too - I don't want to commit to delivering in a certain timeframe if my software won't actually let me publish!!!
Any help would be much appreciated.
Thanks.

Hi Zak, thanks for the reply.
The filename is whatever is set to be the background fill of the site (I presume the desktop background fill, if mobile versions are set to be different). I've tried a number of different files, sizes and types/formats and the result is still the same, so as far as I can tell it's not the file itself causing the issue...
It uploads all pages (desktop, tablet and phone versions), .css files and .html files, and even the favicon .ico file but then hangs on the first image file, which incidentally is the background fill image.
The total number of files is said to be 154. It gets stuck on file number 24.
Yes the "Resume" dialog appears and upon clicking it just attempts to continue from the hang at the first image file (apparently 66% of the way through).
Re: the "BC site has changed" part - I thought as much but figured worth reporting.
... Incidentally, as I've written this reply, I left the "Resume" dialog open (ie neither clicking "resume" or "cancel" and just as I've finished typing it appears to have published the site successfully?!! (I must've left it for roughly 5 minutes)
Bizarre behaviour... I'm not sure if this will repeat itself with other sites but I'm sure there's a bug here that needs looking at regardless...?!
Any thoughts?

Iweb9 No Longer Publishing

Similar Messages

Maybe you are looking for