Transferring from IWeb 2.0.4 to IWeb 3.0.1

I have created a website file that is stored on my old Macbook Pro OS 10.5.3 on IWeb version 2.0.4.
I would like to transfer it to my new Macbook Pro OS 10.6.3 with the IWeb version 3.0.1.
Is this possible without corrupting the data or settings?
Thanks,
Jim

do you have the installer to the 3.x? Just pop it on your old MBP - it will upgrade the file, then copy the file to your new MBP
Although, you could always try the easy way.
Just copy the old 2.x file right onto the new MBP, open it and see what it does... Tha won't hurt anything, if it looks corrupted, you can always delete it, right?
Message was edited by: Jiri Krecek

Similar Messages

The Domains.site2 file transferred from another mac won't open in iweb

Just transfered a Domains.site2 file from one mac to another in the applications support/iweb folder. But when I open iweb I get the error: can't read Domains.site2 file. Any thoughts on why this might be? It's a large file - over 2 gigs, transferred from an iMac running OX 10.5 to a macbook running OX 10.6
Thanks!

Try the following:
delete the iWeb preference files, com.apple.iWeb.plist and com.apple.iWeb.plist.lockfile, that resides in your Home() /Library/Preferences folder.
go to your Home()/Library/Caches/com.apple.iWeb folder and delete its contents.
Click to view full size
launch iWeb and try again.
If that doesn't help continue with:
move the domain file from your Home/Library/Application Support/iWeb folder to the Desktop.
launch iWeb, create a new test site, save the new domain file and close iWeb.
go to the your Home/Library/Application Support/iWeb folder and delete the new domain file.
move your original domain file from the Desktop to the iWeb folder.
launch iWeb and try again.
OT

I've Made the Switch (from iWeb) & Lived to Tell About It.

I've gotten a lot of help and useful information from this forum over the years and I will certainly miss it. I've just completed a 2 month transition where I've migrated my site from iWeb/Mobile Me to a new site made in RapidWeaver and hosted by Host Excellence. I figured I'd write a little (or a lot) about my experience, to give some others an idea of what they've got to look forward too. Hopefully it will arm you with some things to do and look out for. While I am describing RapidWeaver here, a lot of this process will be the same no matter what new software you use. I started off being pretty happy with what I had going in iWeb and not being thrilled at all about making the switch. Now I am so glad I made the switch and I am far happier about the new site than I was with the old one. BTW: the new sites address is: http://grillinsmokin.net . Feel free to visit. I think you'll quickly notice some things you simple can't do in iWeb. This isn't a knock against iWeb. I was very happy with iWeb and had no plans to switch. Where it hasn't been developed actively for four years now, it has been left behind somewhat.
To begin at the beginning: I've had a site made with iWeb since January of 2006 called Grillin' & Smokin' that combined my love of outdoor cooking and photography. Over the years it had grown rather large, with 375 photo entry pages and 230 blog pages. The Domain file was around 1.4 GB. This was not something I ever wanted to have to recreate from scratch. However losing MobileMe as a host was taking away Value Added features like the Hit Counter, Slide Show, Blog Comments, Blog Search etc. The handwriting is on the wall for iWeb too. I might have gone on using iWeb, but between losing key features and the fact iWeb was starting to show it's age, it was time for me to move on. Just before the iCloud announcement this Spring, I began researching website building software. I looked at their features, working methodology, themes, plug-ins and extensions. I download trial versions of the software where it was available as well as some of the themes or plugins I might be using. I gotta tell you, at first I was very frustrated and upset, because I was not finding anything that had the ease of use of iWeb and looked like it was going to be able to recreate the appearance of my original site. It appeared to be a series of compromises. I'd like the features of one package but I hated the themes available for that software. Another looked promising but isn't being upgraded regularly. My biggest frustration was some of the iWeb page types just don't exist in other packages. For example the Album Pages where multiple Photo Pages can be grouped and displayed, don't have a direct equivalent in any other package I saw. As part of my discovery process I read reviews of the various packages, including head to head comparisons of some of them. I also visited their discussion forums. After doing this for 3 weeks I "settled" on RapidWeaver. It was under active development; had a thriving developer community turning out a wide variety of add ons, plug-ins and themes; had an active user community & had lots of help resources available. The web pages it produced were standards compliant and you could get nice effects without resorting to Flash. I think the biggest selling point was all of the add-ons-kind of the same advantage the iPhone has with it's App Store.
Once I bought RapidWeaver & a 3rd Party theme, I tried the demo versions of some of the plug-ins and made sample versions of my page types from iWeb in RapidWeaver. I wanted to have a process in place, before I started mass production on the site. You really do need to do some of this homework in advance to avoid unpleasant surprises. The biggest minus I'd turned up about RapidWeaver (RW from this point on) is it didn't handle big sites well at all. The equivalent of the iWeb Domain file is the RapidWeaver Sandwich file or RWSW file. Once the RWSW file reaches 100MB or so you can get crashes or hangs uploading your site. Now 100 MB doesn't sound like much particularly when I was talking about a 1.4GB iWeb Domain File for my site, but RW doesn't include the photos in the RWSW file. Still I knew I was going to have to divide my site across several RWSW files. Initially the plan was to divide it into 3 sites: The main landing pages was one RWSW file and is the site reached by the url for the site. I was going to have a second RWSW file for my blogs and a third for my photos. Ultimately I ended up dividing the photos into 3 RWSW files. These extra files are hosted on sub-domians whose name goes in front of the main domain (http://sub-domain.main-domain.com). This meant some extra setup for me with my web-host, although they made the setup for the 4 sub-domains very easy and they were free. If you have a huge site and will need to split it, you'll want to check with your prospective web host if they charge extra for hosting additional sub-domains. For small iWebs sites this is not an issue-you have one RWSW file and one web address, just like you do now. My having sub-domains also meant more work linking files together across sites. RapidWeaver has something called an Offsite Page which helped with some of this, but having to split my sites up was the biggest PITA for me about the whole process. But knowing about this going in was better than finding out at the end when I tried to upload a single massive site. If you have a small site, the setup for uploading it is as straight forward as iWeb. RW has a built in FTP uploader or you can publish to file and use an FTP client like CyberDuck.
Once I had my site organization in place and had experimented with best practices for recreating each iWeb page type in RW, it was time to begin. I've gotta tell you when I started out I was not a happy camper. I liked the iWeb way of doing things about 70 percent of the time vs 30 percent for RW. At the end of the first week I told myself I have to move on and give up on the past. I was no longer going to be using iWeb and the sooner I embraced the RW way of doing things, the better off I'd be. At this early point it was still hard to see down the road to the end results. No matter what new package you buy, you should try to go with the flow and learn a new way of working. You'll be happier and less frustrated in the end. In my case after having gone through the entire process now, I've ended up changing my opinion. Now that I've gone through the entire process, I like the RapidWeaver way of doing things about 95 percent of the time and 5% for iWeb. That 5 percent is mostly the large site issue I've described. As I began working I was able to reuse much of the text from my iWeb blog in RW. I did have to paste it in as unformatted and reformat it in RW. My pictures were well organized in Aperture which also helped speed the process. One of the things I did is automate some of the tedious repetitious tasks. I created Quickeys macros to do things for me when ever possible. For example I could go to a particular photo page in iWeb and select the first caption. I would then trigger a macro that asked how many captions are on this page. It would then select the caption in iWeb, copy it, switch to RW and paste it in place and repeat XX times. If you know Quickeys or Applescript (I am guessing) there are plenty of opportunities to put it to good use.
RW present a different way of working than you are used to in iWeb and you'll just need to get used to it. What I am describing here would be true of any of the other packages I looked at too. First off it isn't WYSIWYG while you are editing. You are working with fairly basic looking text with few clues as to what the real page looks like. You switch to a preview mode to see what the page looks like in a browser. At first blush iWeb seems to win here. But what I soon realized is RW allows you to mix regular text and pictures together with html snippets right in the same text box. This makes adding counters or badges easy. Plus you can use HTML formatting for things like Titles occurring through your page. Instead of increasing the font size, making the text bold and changing its color, you can simply say this is Heading style 2 or 5 and this happens automatically per the predefined style. Better yet if you change a style everything on that one page or the entire site (your choice) inherits that change. So by working in a non-WYSIWYG mode you gain some long term. advantages over how iWeb works. The same is true with positioning. In iWeb it is fast and easy to place things on a page right down to the pixel. RW just doesn't give you that type of precision and next to splitting my site, layout was my biggest frustration with RW. At least to start. But there is a good reason for this "lack of precision" that may not be apparent until you view the site in a browser. When iWeb came out, you really didn't zoom your browser. iWeb uses Absolute Positioning where it uses anchored boxes for everything, whereas RW uses Relative Positioning. Objects with anchored text or picture boxes like iWeb start having problems if you zoom in or out more than one step. Text starts over flowing other text because the text boxes are anchored by one point. Pages just start looking scary if you try to zoom in or out too much. RW is looking at items relative positions and their relationships with one another. So initially you aren't placing the objects in the same way, it is more like eyeballing things in a way. But when viewed in a web browser you can zoom in or out to your heart's content. So what seems at first like a big disadvantage at first for RW, is actually a HUGE advantage.
This is why you need to go with the flow and try to embrace the new way of working. I mentioned earlier that I wasn't able to find a page type that was equivalent to the iWeb album page. I was able to use a very flexible plug-in for RW called stacks, which allows you to create various single and multi-column or multi-row layouts using empty stacks. You then populate the empty stacks with content, pictures text etc. These pages were not like iWeb albums where you nest the Photo Album Pages in the Album page and they create a skimmable preview and an automatic link to the album. Once I actually started making these new "Album" Pages in RW I realized I was gaining as much or more than I was loosing. The skimmable preview pictures was eyecandy I could live without. Nice touch, not essential. I never liked the way the preview picture shown on the Album page was the first photo in the Photo album. You couldn't change this. Now that I am placing my own photo on the Album page, I could use any picture and make it any size I wanted too. In iWeb the Album Caption was the name of the Photo Page. If this name was too long the caption didn't go to a second line, it got cut off. Any link in RW can have a description added to the link which is what you see in the yellow box when you hover your mouse over the item being linked. I used to hide text boxes links under the pictures on the Albums page for SEO and navigation help. So yes now I have to manually link the Album picture to the Photo Page, but I am no longer creating a hidden text box with a link that I have to remember to move when I add pages to the album. So once again my first impression was wrong. Advantage RW.
Another advantage to RW is any page type can have a sidebar. You can easily add favicons and site logos. You can easily add metadata to any page and customized the names of the path to your pages. The Themes can be more powerful and customizable too. About one week into the process I was begining to really go with the flow and see this new way of working had far more advantages for me than disadvantages.
By the time I finished my new RW site, my iWeb site was looking tired and dated. My biggest and most pleasant surprises were saved until the end. Any kind of SEO was a PITA with iWeb. You had to embed snippets on each page with a code from HaloScan or Google Analytics. Problem was, iWeb erased any such HTML code while you were uploading. So you then had to use a regular expression in the text box ("HaloScan goes here"), upload your site and replace the regular expression with the actual code using a 3rd party tool. Oh and don't do that on any blog page where you are using the built in Apple commenting system because the comments will disappear. I also had problems where the new comment badge would not show up for weeks or months after a comment was made. It was getting so the things I had to do AFTER I uploaded my site to MobileMe were taking longer than uploading the site. Once the site was recreated, it was time to add blog comments, a guestbook, a contact form, Google Analytics, and publish a site map. In my iWeb-influenced mind, I was saving the fussy PITA things for last. I was dead wrong. Unlike what you go through with iWeb, it couldn't have been been easier in RW:
-Blog Comments: Set up an account with the provider. Then I had to go into the page setup in RW for my blog page and click on a popup menu of comment providers & select Discus. If your provider isn't listed you paste some HTML code from the provider into a dialogue box provided by RW for the blog page. In my case it was simpler, just set Discus in the popup menu. Now instead of the iWeb badge showing me new posts (and only when it was in the mood), I now get an email.
-Google Analytics: Set up an account with Google. Go to the Stats area in the RW side bar, click on Configure, paste in your code from Google and you are good to go. You can monitor your Google analytics stats right from within RapidWeaver. (Also works this way for GoSquared Live Stats).
-Guestbook: Same as iWeb. You add a page with an HTML snippet from your Guestbook provider in an iFrame.
-Contact Form: This is a RW page type which masks your email address from the spambots by transferring the information to an invisible and inaccessible page within your site. This page then emails you the information.
-Full Site Search: This doesn't exist in iWeb. You can search your blogs right now, but this is one of the features you lose when MobileMe shuts down. By adding an inexpensive Plug in called RapidSearch Pro I enable full site search. You set up a MySQL server for your site. Host Excellence walked me through the 4-Step Process via a well written Help File. You then control what pages are indexed via your sitemap.xml file. You let RapidSearch Pro index your site and you are good to go.
-SiteMap: There is a simple SiteMap generation feature built into RW 5. There are third party tools for doing this for iWeb. I purchased an inexpensive RW plug in called SiteMap plus that not only generates the sitemap.xml file, it allows you to customize what pages get searched and at what frequency. This ties into what is searched via RapidSearch Pro. This plug-in also generates a visible and customizable sitemap page to help your site's users find their way around. Another bonus of being hosted off Mobile Me is when I went to add my sites to my Google account they had already been indexed. It seemed like they never crawled MobileMe unless you told them you wanted them to look at your site.
Link Checking: This doesn't exist in iWeb. I bought another inexpensive plug-in called Link Inspector for RW. It checks all of your internal and external links and generates a report showing the status of all links. This was just what the doctor ordered for my large site. I will run it periodically to make sure external links are still working and that I haven't broken any internal links.
My site was pretty much wrapped up on Monday August 8th. I just had to add in Blog Comments, Google Analytics, the Guestbook, Full Site Search and the Site Map. I figured I would go public on Tuesday or Wednesday. To my great pleasure these 5 items took all of 2 hours to get set up and working. This was a nice touch after 2 months of hard work.
So there you have it. This is the process I went through converting my site over to RapidWeaver. Your mileage may vary. I am not pushing RapidWeaver for everyone. You have to find what program is the right fit for you. You may find staying with iWeb on a new host is the right fit for you. You need to decide if you can live with the features you lose once you aren't hosted on Mobile Me. For me there was great pain, but in the end there was a lot of gain too. I do like my new site and I feel it will serve me well for years to come. Good luck to all of you in whatever path you choose. Lastly thanks one last time to the helpful folks around here
Jim
http://grillinsmokin.net
Message was edited by: Jim Mahoney

Thanks Roddy. I agree with your take on some of the other software you mentioned, at least from the perspective of having dabbled with demo versions of some of the others. I will add that with Sandvox I felt a little nervous about it. Kind of almost like the software was a "hobby" effort a la the first gen Apple TV.
I also agree with some of your points regarding RapidWeaver. But now that I've built my rather large (for a hobbyist site) website with it I will have to respectfully disagree about it being at the same level as iWeb, or as you put it: a sideways move. While iWeb can be made to do things it was never originally meant to do, there are many places it simply can't go that RapidWeaver can. I was often hitting the limits of what you could do in iWeb, whereas with RapidWeaver, with one exception, I didn't feel like I was running up against any limits yet. The exception is it's lack of ability to handle large sites well. That was almost the deal breaker for me. I find it unexplainable that a software package with all kinds of add-ons helping you make more ambitious sites, can't handle those same sites in a single file. This was almost a deal-breaker for me. For folks who have small to medium sized iWeb sites this isn't a concern. There are also ways to warehouse images on the server to keep file size down, but this gets more complex than many folks coming from iWeb would want to do. Me splitting my site up the way I did was more work than I wanted to do.I almost bagged the whole thing and was close to just taking the old site down.
Now if we were to fantasize for a minute I can think of a way where I could also say iWeb to RapiWeaver is a sideways move: While I don't think iWeb '09 is the equal to RapidWeaver 5, I'd bet that iWeb 11 or the oft rumored iWeb Pro might have been. I kept hoping that Apple would keep pushing the limits of what iWeb could do and add in some missing features and head down the HTML 5 road.
I will conditionally agree on your saying that the shopping list for RapidWeaver can be substantial. I will qualify that by saying: Depending on what you are doing with it, your shopping list for RapidWeaver can be substantial. With one exception, I do think the base package of RapidWeaver is fairly priced. I think the basic Stacks functionality and a few basic stacks should be part of RapidWeaver. The more esoteric stacks can be pay as you go. When iLife 11 was announced without a an update to iWeb, I did some preliminary pricing and I was rather discouraged at the total. This spring I got more serious about things and repriced RapidWeaver and add-ons. After trying out various themes and plug-ins, I was able to sharpen my pencil and reduce the cost of entry considerably. One of the things that helped is the theme I bought had a couple features built into it. It had a nice lightbox type slideshow for photo pages and animated banners/headers capabilities built in. This saved me the expense of several additional plug-ins. Also while I have a blog, I don't consider myself a blogger. I was able to use the built in blog page and I don't feel limited by it at all. Some of the other ad-ons I bought: such as the link checker, site wide search and a more sophisticated sitemap generator were items I added because I could tell I would want to keep the site going long term. Those 3 plug-ins did that a a low price. I didn't think they needed to be built in.
But everyone's mileage may vary. RapidWeaver or any other web design program isn't right for every iWeb user. It all depends on personal needs, abilities and budgets. I'm just glad I can get back to posting to the site and not recreating it.
Jim

IPad no longer reads PDFs from iWeb site like it did in mid April offering to read PDF in iBooks.

iPad no longer reads PDFs from iWeb site like it did in mid April offering to read PDF in iBooks.

How to Transfer Everything from an Old iPad to New iPad
http://osxdaily.com/2012/03/16/transfer-old-ipad-to-new-ipad/
iOS: Transferring information from your current iPhone, iPad, or iPod touch to a new device
http://support.apple.com/kb/HT2109
Moving Content to a New iPad
http://tinyurl.com/qzk2a26
How to Transfer App Data and Game Saves from One iOS Device to Another
http://lifehacker.com/5891964/can-i-transfer-app-data-and-game-saves-from-my-iph one-to-a-new-ipad
How to transfer data from your old iPad to your new iPad
http://www.imore.com/how-transfer-data-your-old-ipad-your-new-ipad-air-or-retina -ipad-mini
Transferring your prepaid cellular data account depends on your carrier. AT&T lets you move it yourself when you go to Cellular Data in Settings and log into your account with your previous AT&T user name and password. For iPads with Sprint service, you can set up an account on the new iPad and contact Sprint Customer Care (888-211-4727 and go through the menus) to deactivate the old plan and get credit for unused service. For Verizon, call the company’s customer service number for mobile broadband support (800-786-8419) and ask to have your account transferred.
 Cheers, Tom

Cannot publish from iWeb 08 after upgrading to Leopard

When I click on Publish from iWeb I first get a window .Mac Information asking me to login and a smaller window saying "logging in to iWeb". I click on sign in button from .Mac Information window and then get the System Preferences window telling me I am signed in and giving me my account status. From here nothing happens. The "logging into iWeb" message stays and nothing happens.
What should I do?

Thanks and Merry Christmas to you too! I have experienced both modem/network problems and was unable to publish in Tahiti and Cook Islands because of that and now these problems which have nothing to do with network it seems - so yours may or may not be network related. I was able to cheat and copied my "Site" folder from my hard drive to my iDisk rather then publishing. I can't remember if you've tried this or not (read a lot of strings today) but you can publish to a folder and then copy that folder to your iDisk at /Web/Sites/iWeb/Site as "Site" after first renaming the one that is out there now. Let me know if you have any questions on how to do it. It sounds like you are traveling like we are and anxious to communicate with friends and family back home. When you are bored, our site is web.mac.com/baganworldtour.
At least we now have our first update out there in two weeks. But it took almost two hours to copy the folder and this won't work forever. Hopefully we, whether by the discussion room or .mac support next week, will be able to fix the problem for real.
Thanks. Good Luck. Merry Christmas

Error Publishing from iweb 09 - Server or iweb problems??

I upgraded from iweb 08 (I had no issues) to iweb 09, and I have publishing errors more than half the time. Are the mobileme servers having problems, or is there a hack in the iweb software?
This is a big problem because I have 20 Gb of pages with video that I need to re-publish. It is bad enough that I will be tying my network up for 2 weeks, but that I often don't make progress.
The message is "Error connecting to mobileme, check network.. .." The problem is that it uploads for an hour or so before it stops.. I am double checking to see if my routing is causing the problem, but I don't think so..
Is Apple working on this? Are there numerous people who are now stuck re-publishing their sites and the servers are getting beat up? Does anyone know how to diagnose this type of problem?

Finally i solved the issue of Publishing Error in iWeb 09 with MobileMe.
Procedure which i followed and might also help you guys.
Lets say your default site name is XYZ then create a new site e.g. ABC.
Thereafter dragged all pages from default site XYZ to new site ABC ONE BY ONE.
*In the preference folder delete any PLIST files related to iWeb (i had two files in my folder).*
*Once you drag all pages from your default site to new site there after just make a new blank page and publish the site.*
Then start dragging first one page from new site ABC and publish one page. There after repeat all pages one by one and publish after every page you drag from new site ABC to default site XYZ.
Once you finish then take a backup in time machine of the domain.
There after start your blog page then publish again then start photos album page, publish again then your movie page, publish again etc because these are the pages which were mostly creating errors.
After you complete the final page and publish remove the blank page and publish again.
I spent 3 days with the same problem and finally i could finish by this method in few hours.

Changes from iWeb 08 to iWeb 09 - is there a complete list anywhere?

Hi all -
I just upgraded from '08 to '09. Before I start mucking around too much, I'm wondering if there is a complete list of the changes out there somewhere.
Thanks,
roxpat

What a flippin' disaster. You were correct, Roddy. I updated one page on my website - the front page (very poor decision) - and iWeb 09 completely screwed it up. The WSYIG concept is totally gone from iWeb 09. Everything looked fine in iWeb itself, but when I uploaded it to the server the paragraphs were spaced differently, text boxes were larger than they should be and were placed differently than what they showed up as in iWeb itself. I spent a good hour just trying to make it look decent again.
This weekend I will revert back to iWeb 08 until I hear that 09 is working properly. Boooooooo Mac - what were you thinking???

I am trying to move a picture that I brought over from iWeb and it is locked. I need to move it. Can anyone help?

I am trying to move a picture that I brought over from iWeb and it is locked. I need to move it. Can anyone help?

It is probaly just "inline" ie part of the text.
click on it > Inspector > Wrap > Floating
Peter

Cannot publish from iWeb to .Mac, Help please!

I am trying to publish to my site from here in Australia. I was able to publish in the country at the beggining of the trip, but can not now. I get the message "Publish Error - an error occurred while publishing file /Web/Site/iWeb/Site/Blog". I had updated two blog entries and changed the date on an entry. Since then in trying to fix the issue I deleted both of those entries. I have been through .mac support troubleshooting steps to ensure it is not a network error. I have been able to publish to a folder, but when I try to copy the Blog folder from that folder to my iDisk I get "The Finder cannont complete the operation because some data in "" could not be read or written (Error code -36)". Since then they asked that I try to publish from a trial .Mac account or from a new OS X user account on my machine. Both of those attempts failed as well, which they say indicates it's not a .mac account or OS X user set up issue. They asked that I put a copy of my domain file out in the public drive for them to look at, but when I try to do that it goes through and does the copying and then freezes at "Copying Domain.zip to Public, Copied 599.5MB of 599.5MB (Closing file...) - Please wait". Then I get the same error code -36 and am disconnected from iweb. Can anyone out there help please?
Thanks!

Thanks and Merry Christmas to you too! I have experienced both modem/network problems and was unable to publish in Tahiti and Cook Islands because of that and now these problems which have nothing to do with network it seems - so yours may or may not be network related. I was able to cheat and copied my "Site" folder from my hard drive to my iDisk rather then publishing. I can't remember if you've tried this or not (read a lot of strings today) but you can publish to a folder and then copy that folder to your iDisk at /Web/Sites/iWeb/Site as "Site" after first renaming the one that is out there now. Let me know if you have any questions on how to do it. It sounds like you are traveling like we are and anxious to communicate with friends and family back home. When you are bored, our site is web.mac.com/baganworldtour.
At least we now have our first update out there in two weeks. But it took almost two hours to copy the folder and this won't work forever. Hopefully we, whether by the discussion room or .mac support next week, will be able to fix the problem for real.
Thanks. Good Luck. Merry Christmas

Cannot publish from iweb to iweb website

Had to format hard drive and re-install OS. Suspect domain file is gone? I can see my website on .mac - but it does not show on iweb. when i publish from iweb, it tells me it's been published, but no changes on .mac - any ideas? help!

I have the same problem. I tried your advice but still cannot get iweb to publish. Before I had my computer serviced it worked fine and publishing took place automatically.

How can i delete a website made in iWeb from MobileMe but not from iWeb

The problem is that I have made changes to several pages (almost all of them) on my site and since the changes my site no longer displays correctly in Internet Explorer.
I have looked in the IE CSS file and the CSS file for IE is completely messed up and would take a long time to correct by correcting the code for every page, so I decided just to delete the whole site from MobileMe and then republish it as a new site, rather then as an altered site.
The problem is I don't want to delete the site from iWeb, because it has took me months to build it and I don't want to have to start again. I just want to delete the site from MobileMe, so I can republish it as a new site (and hopefully correct the screwed up code).
So how can I delete a website created in iWeb and published on MobileMe from MobileMe without deleting it from iWeb.
Huge thanks
Jay

Hey thanks for your reply, unfortunately I have already tried to delete my site from iDisk >> Web >> Sites. But it said that i didn't have permission and it wouldn't delete the files.
I am loged in as an Admin and I still cant delete them
Thanks again
Jay

I'd like to edit my site from iWeb on two computers, is this possible?

I'd like to edit my site from iWeb on two computers, is this possible?
I started creating my site on a PB 15", but when I'm home I like the speed of my iMac and I'd like to continue the editing process on my iMac but I can't find the files that iWeb saves.
I'd ideally like to save my site on my 30gig iPod using it as a hard drive between both. I would love for this to happen but I can't find the files saved by iWeb. Is this even possible?
I've even tried linking my PB to my iMac via firewire as a hard drive. No Luck.
Please Help . . .
john
PB G4 15" 167GHz 80HD, iMac G5 2Ghz, 160HD Mac OS X (10.4.5)
PB G4 15" 167GHz 80HD, iMac G5 2Ghz, 160HD Mac OS X (10.4.5)

I think iWeb only recognizes the 'domain.sites' file so while you can set up more than one site, they are in the same project.
Of course, the workround is to move the domain.sites file out of the default location, which them makes iWeb create a new one. You can then work on any number of projects, only moving the correct file into the default location for work on each one. Not elegant by any means, but until someone suggests a better way (or Apple produce a more flexible version of the software) it works fine that way.

Photo gallery page from iWeb '08 doesn't work for Mac OS X 10.3.9 user?

I have recently published a photo gallery page with comments on using iWeb '08 (latest update). Displays fine for me and apparently a lot of other mixed-platform users. But one user is saying that his eMac with Mac OS X 10.3.9 and the Safari of the day don't display the pictures. He gets the banner and background image for the gallery, but not the actual pictures. I asked him to try Firefox, but so far no reply on that.
Do the older versions of Safari work with content from iWeb '08?

QuickTimeKirk wrote:
The only thing missing when viewed using older browsers is those features that require newer Web browser software.
It was no different when AOL went from version 3 to version 4.
The very complex javascript files written by iWeb 2 still allow older browsers view (limited features) view the basic parts of your pages.
Unfortunately this is not true. On an iMac G4 10.3.9 using Safari you cannot even view the photos, the photo page or even the web gallery itself. You just get a warning. Had I known that my friends and family would have a problem viewing photos I would have passed on the update. I don't expect my Father to upgrade his system to view photos from the "user friendly" Apple programs. That's why we got him an iMac to begin with. I find iLife 08 a very poor release from Apple and more trouble than it is worth.
It was no different when AOL went from version 3 to version 4.
I didn't know AOL even still existed, that alone upgraded!? (haha)
+The images should load but many of the Web 2.0 features will not work (image rollover viewing, changing dimensions or background colors).+
But Kirk, they don't, none of them! and this kind of stuff just seems crazy to some of us. I wish that Apple would TELL US or advertise the facts like, Oh, you only get ONE gallery for each user on Web Gallery (useless) and Oh, you will not be able to edit 06 iWeb pages with 08 iWeb and the iLife 08 version of iPhoto you will not be able to view these galleries without upgrading to the latest Safari web browser. Yes we always expect some bugs with a major update but this is getting ridiculous.
I have not yet had anybody try downloading the newest version of Firefox that will work with 10.3.9. Do you know if that will make a difference? Thanks for your help.

I trying to publish a web page from iweb, but it doesn't recognize my MobileMe account

I trying to publish a web page from iweb, but it doesn't recognize my MobileMe accouI trying to publish a web page from iweb, but it doesn't recognize my MobileMe account, what can I do?

MobileMe has been discontinued for over 2 years now. You'll need to find a new hosting server for your website.
This may be of help to you: Life After MobileMe.

Pdf-file with clickable links from iweb 09

How can I create a pdf-file with clickable links from a website created in iweb 09?
All iwork apps have an export button, which fulfills this task, but iweb does not.
Any idea?

I am running 10.5.6 on a MacBook Pro 2.53 GHz. I create my PDFs via the print dialogue. I tried to create a PDF from iweb with Hyperlinks activated and all links are dead. I tried to create the PDF from the Safari window, were all links are active, and – funny enough – sometimes all, sometimes half of my links are dead. But most of them do not work. As soon as I create PDFs from third party sites, everything works fine.

Transferring from IWeb 2.0.4 to IWeb 3.0.1

Similar Messages

Maybe you are looking for