Iweb/Mobile Me

I am trying to figure out how to use 2 different computers to be able to publish websites using iweb. I have home sites and I have work sites. I would like to use my work macbook to publish work sites and my imac at home to publish my home sites. However, last time i did that, it erased all my home sites after publishing the worksites from the mac book. Is there any way with iweb and mobile me to have two separate files on the mobile me server that you can publish to?
If so, how do you do this?

If you name your sites differently then they will not erase each other. You can publish as many sites as you want to with iWeb to MobileMe. They will only ever erase each other if they have the same site name.
Call your sites Site 1, Site 2, Site 3, WorkSite, HomeSite etc. and when you publish these sites you can get to them all via the url http://web.me.com/username/sitename, so web.me.com/username/WorkSite, web.me.com/username/HomeSite, web.me.com/username/Site 1 etc. etc.
Remember though that the site that you publish first will always come up if you just enter web.me.com/username. If you publish different sites and just access them via web.me.com/username then the last published site will appear, giving the illusion that your other sites have been overwritten, when in fact they have not. All you do is enter web.me.com/username/sitename and you can access them all.
There is no separate file that you can use on MobileMe for different sites - they are all published to the same place - just use different site names and you will be okay.
Your other option is to purchase a MobileMe Family Pack, but this is only necessary if you want up to 5 domain names linked to the account. If you have the domain names, then this is a good option, but if not, then just continue publishing multiple sites to one MME account.

Similar Messages

  • Is ilife any good at publishing simple photo galleries like iWeb/ mobile me used to be?

    is ilife any good at publishing simple photo galleries like iWeb/ mobile me used to be?

    As Roddy pointed out iWeb will still create album and/or photo pages that will work on the hosting server of your choice.  These two pages are demos of that: Using an iWeb Album Page as an Alternative to MobileMe Galleries  and Using an iWeb Photo Page as an Alternate to a MobileMe Gallery
    This may also be of help to you: Life After MobileMe.
    OT

  • Transfer iweb/mobile me site to wordpress

    I moved my iweb/mobile me site to wordpress over the weekend, in the process losing access to the old hosted iweb site and the comments that had been posted. Anyone know how to access those old pages now that my domain points to my new wordpress site?
    thanks!

    Use your MobileMe URL :
    http://web.me.com/MMeUsername

  • IWeb mobile site won't work

    I published an iWeb website and when I try to visit it on my iPhone, the phone automatically redirects the URL to "m.websitename.com" (even if I delete the m.) and then shows a message of "We are sorry, there is no such site.". I haven't found anything on iWeb about mobile sites, so I'm not sure why the mobile device won't just visit the normal site.

    Contact your host's tech support and ask them if they have a redirect on the server.
    Now that having a mobile version of your site is essential if you are in business, its usually set up as a sub domain with the prefix "m." or "mobile."
    Most hosting services allow us to decide which method, if any, to use to direct mobile visitors to the appropriate version of the site. Some have obviously decided to do it for us using either .htaccess or a server side script!
    Maybe you should leave it in place and take this as a strong hint to create a mobile compatible version of your site. It is possible to do this using iWeb if you think about it.

  • IWeb mobile me sign in problem

    I am trying to publish my iWeb website through the mobile me option but having problems logging in. Has anyone any suggestions please??

    MobileMe was discontinued a while ago and you will no longer be able to login or publish your iweb site. It was replaced with iCloud which does not allow you to publish your iweb site.
    You can find a new web hosting service as described in this article:
    http://iwebunlimited.com/iweb-tips/life-after-mobileme-transferring-to-a-hosting -company/
    Or one of the many others out there.
    iWeb has also been discontinued and will no longer be updated. Although it still works on Mavricks, some feature will no longer work properly.
    There are many alternatives suggested on this forum and you may want to do a search to find them. They include RapidWeaver, Sandvox, DreamWeaver and others.
    The most suggested replacement is the new EverWeb site builder which is very similar to iWeb but with new features. You can find a review about it here:
    http://www.allaboutiweb.com/2013/11/everweb-replace-your-iweb/
    Or download it here:
    http://everwebapp.com

  • Web page using iweb/mobile me

    Why doesn't my web page set up through mobil me come up on the computer when I enter the address with www.me.com/..........It won't load up unless I use only http://me.com/etc.etc..
    I want it to load my web page when I enter the address www.me.com/.........What is going on here? I have to advertise this web page and I cannot put it under www. Why?

    The url of any website published from iWeb to MobileMe will always be http://web.me.com/username/page name.html. www.me.com only exists to allow you to log into your MobileMe account online.
    If you want anything different, then you need to go to a domain name registrar and register a domain name from them and then link it to your MobileMe account. That is the only way.

  • IWeb, mobile sites, redirection...

    I'm working on this website http://www.davidpaulcarr.com using iWeb.
    I have also been playing with making a separate site for mobile devices which can be seen here http://davidpaulcarr.wayma.com .
    The idea, ultimately, is to add .3gp "light" versions of the flash content that is on the main website to a mobile one so that visitors using devices unable to use flash can access at least some of the main content (I hope that's clear!).
    There are various things I would like to do -
    1) Redirect visitors using mobile devices to a separate site adapted to their needs.
    2) Not use wayma.com (or a similar service) to make this mobile website - the functions are very limited, the default font is ugly and I can't get it to echo the design of the main website. Ideally, I would build the mobile site myself, using iWeb again.
    My questions -
    1) How to redirect visitors using mobile devices ? (I posted recently on a similar topic, followed up the leads but didn't get anything that worked).
    2) Is it possible to make a mobile site myself in iWeb and host it on my server? I suppose there are optimal page and font sizes, for a start...
    Any advice will be gratefully received. Please bear in mind that I have limited html skills, slowly learning what I need as I go along...

    Thanks for your reply!
    I was familiar with that thread and had added the Chris Bailey (modified) code to the appropriate page.
    I then - on the basis that my iPod touch would be recognized the same way as an iPhone (which I don't posess) - accessed the page but was not redirected, so I assumed the code wasn't working.
    Perhaps accessing from an iPod Touch isn't the same as accessing from an iPhone, I don't know...
    Anyway, I think I'm looking for a more global redirection solution that would work for smartphones, Blackberrys, anything with a big enough screen to usefully view my content...
    Any ideas about page size and fonts ? (and more generally whether I can use iWeb to cobble together a mobile website)...

  • Iweb-mobile me not working together.

    HELP!!!
    I am getting really frustrated. I had a site created in '08, have upgraded to '09, and now when I publish to the mobile me site, it looks like it is publishing, but when I go to view the site, I get this (see www.h2photo.ca). I need to get this fixed quickly, any help would be amazing!
    Hope

    when I go to view the site, I get this (see www.h2photo.ca).
    Looks fine to me. What do you think the problem is? Make sure you do Safari > Empty cache.

  • 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

  • I need help finding a workable web program that is not CSS based.  I tried IWeb and it just won't work for me.  Way too limiting.  I've been using a 12 year old copy of Macromedia Dreamweaver, but the new Dreamweaver is CSS

    Been building web pages for nearly 20 years, starting with GoLive.  Went to Dreamweaver about 12 years ago, the Macromedia version.  Tried going to iWeb when it came with a new Mac, but found it way too limiting with it's CSS template base.   Unknowlingly, I then bought a new copy of Dreamweaver.   Ooops, Adobe had bought Macromedia and Dreamweaver, too, is now CSS based, which for my money makes it useless to anyone who likes simplicity.   Now I find that even iWeb has been discontinued.  I was told yesterday that Apple doesn't have a web program any more.   At 12 years old, I just don't think it's practical to try to load my old Macromedia Dreamweaver into the new Mountain Lion (I'm getting a new Mac), though it is running, barely, in Snow Leopard.
    I need to find a web builder program that will permit simple construction of educational pages, nothing fancy, nothing artistic, just create a page, give it a color, type or drag in text, insert a table, insert pix in the table blocks, add text under the pix... done!    I should note that I am not looking to build traffic.  I teach simple things for free and people who want to learn those things (antique sewing machine repair, quilting, building longbows) find me.
    I've downloaded trial versions of half a dozen or so programs and looked at maybe 20 more, but all are either CSS based and drive me insane with requirments for constantly making rules and template models, and/or require that you base your web presence in their server.   Also, many will not work with pages built in other programs.  I maintian a volume of over 1000 web pages, many requiring regular updating, and they have been with the same server for more than 15 years.  I'm not about to change.
    So, anybody know a simple, old fashioned web builder that's happpy on a Mac platform?
    Captain Dick

    Although not supported anymore, iWeb does still function using Mountain Lion...
    http://www.iwebformusicians.com/iWeb/mountain-lion.html
    ... and you can purchase it from Amazon.
    Start with a blank page using the Black or WHite template.
    All modern websites use CSS and there are thousands of free templates to be had if you want to use a code entry style application. You will need to go this route if you want to create a site that is viewable on mobile devices although you can create an iPhone version using iWeb...
    http://www.iwebformusicians.com/iWeb/Mobile-iWeb.html
    Search this forum for numerous topics about iWeb alternatives.

  • How to move iWeb site with missing Domain.sites file

    I've been asked to host a friend's iWeb site now that MobileMe is no longer an option.  The problem is that the MacBook it was created with is long gone and the only original files remaining are the image files for the site. No Domain.sites file.  They are also not sure which version of iWeb was used, if that even matters.  Initially I was thinking we could just access the existing site using ftp and go from there - upload the site to my hosting account and use Dreamweaver to maintain it, but everything I've read seems to point to 'Not gonna happen that way'.
    Is there a way to transfer an existing iWeb site hosted on MobileMe to a new hosting account and be able to work on it with another editor, all the while not having the original Domain.sites(2) file?
    Thanks much,
    Mark

    Quite a few people are moving to other drag and drop style editors like Sandvox and RapidWeaver although they aren't really any better - just more expensive.
    I advise people not to use iWeb for new sites and just to keep it going to update existing ones until they are defunct or rebuilt some other way.
    I quit using iWeb about a year ago due to the fact that it, and similar apps, can't create responsive designs for mobile devices although I did figure out a stop gap design for iPhones...
    http://www.iwebformusicians.com/iWeb/Mobile-iWeb.html

  • Moving iweb/mobileme archive files to wordpress

    I was able to pull my more current posts from my iweb/mobile me site to my new site using an xml import. However, the xml file for older posts in the archive only contains headlines - no copy which means it facilitates importing a bunch of headlines and empty pages. Anyone know a work-around short of individually ftping the file for each archive post or copying and pasting into wordpress? I have a stored copy of the old site on my local hard drive so access is not a problem.
    thanks!

    You need to move the domain.sites folder from your computer to her computer.
    Go to the Go menu in the Finder and in the field that opens up enter;
    ~/Library/Application Support/iWeb/
    You wil see the domain.site file in there. Move it to the same location on her computer.
    All websites are stored as one project file in a single domain.sites file. So once you move it over to her computer you can open it up in iWeb and delete any other sites in there.

  • A fix to personal web domain name problem between iWeb and GoDaddy

    There are numerous posts about problems with iWeb understanding both your personal name domain with and without the www.prefix. After five days, 25 calls to both Apple and GoDaddy where I was getting much conflicting advice even within each organization, and I experienced many problems such as the site not being found and iWeb asking for password authorization whenever anyone visited the site. The good news is that I was finally able to resolve the problem with these simple steps:
    First, check that your Web site actually exists by going to http://web.mac.com/yourusername
    If that works then you need to set up a forward in GoDaddy.
    In GoDaddy's account manager, make sure that the forwarding address is set to http://web.mac.com/yourusername. This must be the same address that you just checked through your browser. (I also advise you to NOT USE the .ME designation that Apple is moving to. It's not solid yet. .MAC will work for a long time. It's web.mac.com/ that will work).
    Then click on the Total DNS Control and MX Records link.
    This is where my instructions that work differ from many other instructions, but heed my advice and you'll save a lot of time.
    Look in the CNAMES area and make sure that the www host alias points to "@" and not to anything else such as "web.me.com" or "www.mac.com". If you don't have such an entry, then create one by clicking on the "add a new CNAME Record"button. Caution - if you don't use the "@" (at sign) here you WILL run into trouble where your custom domain name will only work WITHOUT a "www." prefix. (While this may not be a problem for your mac friends, most everyone using a PC will think they need to type in a "WWW." and that will cause a problem).
    Then if you wish, you can also go back into your domain forwarding area and click on the masking tab and click to enable masking. This will make your url only show the short personal domain name rather than the very long iWeb mobile me URL appended with your personal domain name.
    Confirm your entry, and then wait anywhere from 20 minutes to four hours or more for the tens of thousands of servers around the world to repopulate those instructions. I was able to see a change take place in minutes where my associate in another state didn't see the change for two hours. Don't worry, just wait.
    If you do this, you should be able to then go to your Web site through either www.YourPersonalDomainName.com or YourPersonalDomainName.com
    Good luck!

    I was finally able to resolve the problem with these simple steps:
    Many people would not be interested in using url forwarding/masking as you suggest to solve this issue, since that makes it impossible to bookmark individual pages of your site. For those who do wish to set the www CNAME to web.mac.com, I think the problem can normally be solved by also setting the @ A Record to 17.250.248.34.

  • Slowness of rollovers in iWeb

    I finally straightened out how to make rollovers in iWeb and have incorporated them into my site.
    http://www.thomasbricker.com/
    What I wonder is why rollovers and load times are so slow on a site hosted on the Mobile Me server?
    It has always been this way. Seems to still be the case.
    Why?
    Is it the way that iWeb constructs it's CSS?
    I have tried opening an iWeb page in Dreamweaver and it kind of falls apart.
    Looks like iWeb uses AP Divs and CSS style sheets.
    I just cant figure out how they wrap the structure together.
    Is there any way to make an iWeb Mobile Me hosted website any zippier?

    MobileMe is definitely slower than the server I use. I have a MobileMe account and test sites on it before optimizing and uploading to Host Excellence.
    The Apple server has a restricted bandwidth and therefore limits the number of viewers who can access you site in any given time period which makes it unsuitable for commercial or popular sites.
    My hosting company cost is only slightly more than MobileMe and that is more than justified by the extra speed, reliability and available functions such as the ability to run scripts and set up mail forwards for processing forms.
    You can't really put a value on good tech support of which MobileMe has almost zero!

  • IWeb and stills - re-sizing?

    I've done a quite elaborate website for a film I'm producing.  I'd like to use the work I did on the website in a press-kit I'm preparing.  Can I use the iWeb project to pull stills for the press kit ... and still get the original resolution of the still?
    I've resized the stills in iWeb, but only by dragging IN iWeb, not by actually re-sizing the original stills.  Does iWeb do the actual auto re-sizing for the internet when I save the project, or when I upload to the web?  In other words: can I just grab the stills in the iWeb project and dump them in Pages and resize them (larger) in Pages and still expect to get the original resolution?  Or do I have to go back to the originals in Aperture?
    All ears,
    Ben

    Large image files slow a web page download time so they should be reduced in size preferably before dragging into iWeb.
    There's not a lot of poimt in dragging in an image that's 1200px x 900px if you are going to reduce its viewable area to 640px x 480px in the application.
    This is particularly important now that a growing number of people are viewing sites on portable devices. Ideally you would provide a different size of image for each device type although you can't easily do that with iWeb.
    When you create a presskit as a download you would include different sized versions of each image. A reviewer would then choose the appropriate size for whatever media they are using - newspaper, magazine, blog, TV, website etc.
    Its even more important with video clip files. You should provide four different sizes in the download and at least three on a website. Here's an example of a reponsive web page which loads three different versions of the movie based on device width...
    http://www.ezmacwebdesign.com/Responsive-Template/video-js.html
    As you drag the browser right hand edge to the left to reduce its width you will notice that the poster image changes in size. The browser is loading a different image for each device width and, when the image is clicked, the appropriate video file size plays. On a personal computer you can have all three playing at once if you really want to!
    In the above demo I am using VideoJS to play the movie so that I only have to provide one video format - MP4 - in three sizes.
    If you use HTML5 for playback you need to provide three formats, each in three sizes as well as three splash images! Even then your movie would not be viewable in some older browsers unless you provide flash fallback or a .swf or .flv file!
    The only easy way to achieve this with iWeb would be to offer direct links to the various movie files or to arrange for them to appear in different popup windows.
    What you can do with iWeb is to create a smart phone version of your site with the appropriate sized media files...
    http://www.iwebformusicians.com/iWeb/Mobile-iWeb.html

Maybe you are looking for