Publishing multiple websites

Hi. Can anyone tell me whether iWeb 08 allows you to publish each site you create separately? I've read in the forums about separating out the domains to publish separately for '06 version, but wondered if this problem is now solved in the update.
Many thanks - and please be gentle as it's my first post and I'm not very techy!

The application is iWebsites. I emailed the author last night to find out if he has tried his application with iWeb '08 as I haven't received my copy yet.
In the meantime, just in case, I have saved my sites in separate folders in the "pre iWebsites" fashion to multiple locations.
Create a folder called, for example, "My Websites".
Inside this folder create a folder for each of your websites.
Make your first website and save it.
Go to Home Folder/Library/Application Support/iWeb and you will see a file called "domain.sites". Drag this file into the file you created for that particular website.
Quit iWeb and relaunch.
Create website #2 and repeat above.
To return to website #1, quit iWeb, open the folder for website #1 and double click the domain.sites file. Website #1 should now launch in iWeb.
Every time you save any work you have done on a website you have to save it and drag the resulting domain.sites file to the folder for that particular site.
iWebsites allows you to have multiple ".sites" files in the Application Support/iWeb file and creates a directory to access these files thus avoiding the above tedious procedure.
As always, whatever method you use, backup your domain.sites files regularly and store them on a re recordable CD/DVD or an external drive because, as we know through painful experience, if you lose or corrupt your domain.sites file you are totally screwed!

Similar Messages

How do I publish multiple websites from iweb?

Hi, I'm new with iweb and .mac in general and wanted to know about publishing multiple accounts from my iweb.
I bought a five-user edition of .mac last week and I wanted to get at least three different websites up and running. One site is almost 50% done and has uploaded just fine but when I tried to create another site in iweb, I have no idea where it's going. I created a second account in .mac and it shows up (I can log into and everything) but how can I publish to my brand new site without the other one going through each and every time?
This question may sound really dumb but please bear and mind that I'm a newbie with iweb and mac (I just got this powerbook in Sept. 2006).
Thanks in advance,
Dale

Actually, Dale, this is a pretty common question.
If you want the different sites to load to different .mac accounts (or different sub accounts), the easiest solution is probably to set up several different user accounts on your computer, one for each .mac sub account. In each of those accounts, set the appropriate .mac info in system preferences. Seems like I've heard of another approach, but this is probably the simplest.
Have you already started building a second site in the same user account (on your computer) as the first site? If so, we'll need to walk you through domain separation, too.
One other heads up: it is very important to back up your domain files (in your case in each account). The domain file is found in ~/library/Application Support/iWeb, where ~ refers to your home folder for your user account on the computer. Make sure to make a backup copy (preferably on an external hard drive or CD) after every major change in your website. Don't be lulled into thinking that a published website serves as a backup. It is not possible to import a published site back into iWeb. The domain file is your only link to creating/editing the site in iWeb.
Please post back if you have any questions or if I haven't been clear.

How to Publish Multiple Websites Using Domain Masking

Let's say I have a mobileme acct called applesoranges, but then I decided not to use this name for my website. Using iweb, I have created a different website called blueberry.com, and was able to figure out how to set up my personal domain and then mask appleoranges so that only blueberry.co, appears.
I now want to add another website called strawberry.com. With one mobileme acct (applesoranges), is it possible to host 2 separate websites, each of which is masking the original mobileme acct? How does one set up 2 separate websites using iweb (each masking the original acct name)?
Many thanks!

For every MobileMe account you can only use the personal domain name option and CNAME only once. You enter your first domain name into your MMe account and then go and set up CNAME forwarding at your domain registrar to forward to web.me.com. For any other sites that you create, you need to go to web forwarding. You set-up the other domain names by using masked web forwarding and point them to web.me.com/username/sitename and by masking these will just show your domain name address and not your MobileMe/iWeb url.
Make sure that you separate out your sites, as it will be easier. You can either duplicate the domain.sites files and have one site per a domain file or use a program called iWebSites to help you manage multiple sites.
You also have the option of not using MMe and you can publish to a folder instead and upload directly to each domain hosting space. This gets away from the problem of how to forward sites to iWeb/MMe.

Publishing multiple websites through iWeb

Hello,
I could use a little help. I have my main website published through iWeb and the mobleme system.
I would like to make another website (which already has a host) on iWeb but can't figured out how to do it.
Any help would be great. Thanks

Okay, so lets just get this clear first of all - which version of iWeb are you using? iWeb 08 or 09? There are differences - if using 09 then click on the name of the site that you want to publish and there should then be a drop down menu at the top of the page that has FTP Mobile Me, FTP Server and then Publish Local Folder. To publish to a folder just click on the Publish Local Folder option and your site will be published to a folder.
iWeb 09 will let you publish individual sites.
If using 08, then this is an 09 forum and there is an 08 forum that you can post to.
However, in iWeb 08 you can choose to Publish to MobileMe and/or then publish to a folder- in 08 there is no ftp to server option and unfortunately, as you have discovered it will publish all sites rather than just individually. If you want to publish individually, then you need to separate out your domain files or use the programme iWebSites to help keep your sites separate.

Publishing Multiple Web Sites

I purchased IWEB 09 so I could publish multiple websites through mobile me. Do I need to purchase an upgrade to mobile me to be able to do that?
poccsteve

Yes, I am trying to use multiple personal domain names.
You can use one CNAME pointed domain name per MobileMe account. It goes to the topmost site in the iWeb site organizer. You can use URL Forwarding for as many other domain names as you want, pointing them at the appropriate MobileMe sites web.me.com/username/sitename.
This note from Roger may help:
http://homepage.mac.com/rfwilmut/notes/twosites.html

How we set up multiple websites on OSX Server

BACKGROUND
After fiddling and futzing around for weeks (actually since last year) I've finally figured out how to set up multiple websites (virtual sites) using one port and one IP address. While there seems to be lots of discussion on this topic, it seems that the basic assumption is that one knows everything about websites, DNS and all that stuff, which I do not.
When our network was originally established the engineer set up a wiki and also configured webmail, so we had two sites, one secured for mail and the other open for Calendar and the wiki. We were not hosting any websites locally because our school website is hosted by a company in New England.
This year I wanted to set up websites for teachers and students. As great as the wiki is, there are some things it just can't do as well as a website. So I figured if I set up the sites teachers could link back and forth from one to the other. In addition kids could now start to use a real website instead of the cobbled together file mess I had when we ran a Windows network. Also iWeb is a much more accessible tool than FrontPage.
SERVER SIDE:
Snow Leopard Server - 10.6.4
There are two - actually three pieces if you want your iWeb clients to connect to the server: Server Side Web Services, DNS and, in my case, FTP.
================================================ SERVER SIDE - WEB SERVICES
If you haven't turned on Web services, you'll need to open Server Admin and do that. If you don't know how to set up web services - just reply and I'll step you through that as well.
Once web services are set up and turned on, you'll see it listed under your server’s name in the Server Admin sidebar. Click on "Web" and then click on the "Sites" tab at the top of page. This is where you list all your sites.
Click the plus button and enter the fully qualified name of your site, for example: "students.myschool.org". Don't use the defaults here (no name) - that's what got me in trouble before. BE SPECIFIC!
You'll be looking at the "General" tab (the other tabs, "Options", "Realms", etc. we'll deal with in a second).
On the "General Tab", the default IP address ("any") and port (80) is just fine. We'll run everything over port 80. (Apache figures all the virtual site stuff out - you don't need your rocket science degree for that.)
"Web Folder:" is important because this is how you'll "segment" your websites. While I would NEVER do this again, we have a solid state hard drive for the OS and a RAID array for our data files. IF you have that, make sure you do NOT use the default "Web Folder" because it will store all your files on your solid state drive. There may not be enough room, over time, on that drive. I've not experienced it yet, but it's my understanding that if the drive fills up, the server shuts down.
I store my web sites on a folder on the RAID array.
Everything else on that tab can be left as the default. (Just make sure that you have an "index.html" or "index.php" file in your web folder root, but iWeb will take care of that for you.)
I would put in your email address in the "Administrator Email:" field.
Under "Options" you really don't have to put anything. I've tested making websites with iWeb and it doesn't appear that anything needs to be checked.
Nothing needs to be entered in "Realms" as well from what I see working w/ iWeb.
The defaults in "Logging" are fine.
You can leave "Security" alone, but we do have a (self-issued) certificate listed for our webmail site.
"Aliases" is important. Under "Web Server Aliases" you enter how you want the site to respond to when users type in a URL in their web browsers.
When our web server was initially set up the engineer set up "wiki.myschool.org" on port 80 and "mail.myschool.org" on port 443. In the aliases section was nothing but a "*" (the wildcard character). That means, from what I can figure out, that the webserver will respond to these sites regardless of what is typed in the URL. (Well, something like that - point is, if you create OTHER websites, you'll NEVER get to them because the wildcard character in the "Aliases" section, in effect, grabs those web requests and redirects them to the sites that are already there.
In my case I deleted both of those wild card characters. For my "wiki.myschool.org" site, I entered "mail.myschool.org". That means if you type EITHER "wiki." or "mail.", go to the site that’s stored in the “Web Folder” we set up when those sites were created.
For "mail.myschool.org" I just DELETED the wildcard character. I wanted that site (since it was secured) only to respond to "mail." - nothing else. (You're not going to that secured site for any other reason than to get your mail.)
"Proxy" can be left blank. Have no idea what that does. As time permits I'll do some research and figure out what it's used for.
"Web Services" is if you want to provide any MORE services to this particular site. Most likely you'll want to uncheck all the boxes. For our "wiki." site, we have checked "Wikis", "Blogs", and "Calendar". For our "mail." site we have those checked PLUS "Mail".
I would create a separate "Web Folder" for each of your sites. I don't know if that's a requirement but for housekeeping purposes, I would keep the sites separated. And I SUSPECT that it's "best practice" to separate your wiki from your other websites.
SERVER SIDE - DNS
OK...now you have to make your site reachable and the only way to do that is to set up DNS so that folks don't need to type in the IP address of your web server. You need to set up DNS inside your network and, if you want folks in the outside world to reach your website, you'll need to set up an external DNS as well. I'm going to cover INTERNAL DNS - if you don't know how to set up EXTERNAL DNS - reply or email me and I'll post those instructions.
Most likely you have already created Zones for you network...all you really need to do is create "Aliases" so that when you type "students.myschool.org" your web browser will know that site resides on IP address XXX.XXX.XXX.XXX.
If you've set up Zones then you already have a "Machine" setting that translates your server’s name to an IP address and vice versa.
All you need to do is create an "Alias" (CNAME) record for, in this case, "students". You’ll see the choices for types of records when you click the "Add Record" button.
There are only two fields to configure for a record: "Alias Name" - in this case "students" and "Destination" - in this case "servername.myschool.org". (You've already entered a machine record that says "servername" = 192.168.1.x.)
That's it for Internal DNS.
SERVER SIDE - FTP
Now you have to get iWeb to communicate with the webserver.
There are only three ways iWeb will communicate with webservers: MobileMe, Local Folder and FTP Server.
Local Folder is really only practical if you want to host a website on a laptop (I was blown away initially when I found out that all Macs had a built-in web server - how neat is that?). I think there are some very cool things teachers could do with configuration, and, of course, you wouldn't need to set up any web services on the web server, but that's for another discussion. You need to set up FTP services on the web server.
Turn on and enable FTP on your webserver.
You can leave the defaults for "General", "Messages" and "Logging". "Advanced" is the only thing you want to set. I set "Authenticated Users See:" to "Home Folder Only". I set the "FTP Root" to the same root folder in which I plan to store my web sites (/VOLUMES/RAID Array/WebServer/Documents). This setting sets that folder only to be accessible via FTP.
I would suggest returning to your DNS settings and adding one more "Alias". Set "ftp." to point to your webserver. Why? So folks can edit their sites from home (see below).
CAVEAT: If you are running FTP on other servers, make sure that the settings here do not conflict with the settings on the other servers. For example, I'm running FTP on my file server so that my scanners can communicate with it. However, I configure my FTP settings by machine name and NOT "ftp.myschool.org".
================================================
CLIENT SIDE - CONFIGURING iWEB
Now you have to configure iWeb so that it will communicate with your server.
Click on the "Site" icon so that "Site Publishing Settings" appears.
Publishing:
"Publish to:" = "FTP Server"
You can set the "Site name:" and "Contact email:" to whatever you want. But see below!
FTP Server Settings:
"Server address"=ftp.myschool.org (you could also enter in servername.myschool.org or the IP address. However, if you want folks to be able to work on the site from home, you will need to configure external DNS for that. If you use the IP address, you're out of luck for remote access to the site. (You can do it but it's beyond the scope of this discussion.)
"Username" & "Password" should be your user's network login credentials.
"Directory/Path" - this is important. Remember, you set your "FTP Root" to be "/VOLUMES/RAID Array/WebServer/Documents". If you leave this field blank then the website will be dumped into this folder. If you are only setting up one site, that may be OK. However I wanted to set up a "students" site folder, a "faculty" site folder and a separate site for our literary magazine.
THEREFORE: I have, in my ..../Documents folder (on the server), a "students" folder, a "faculty" folder, and a "litmag" folder.
SO...in my "Directory/Path:" field, I have "/faculty". That means the full path to this website is "ftp root/faculty" or "/VOLUMES/RAID Array/WebServer/Documents/faculty" (You don't need a trailing "/" character. iWeb will automatically append the folder for you user depending on what you entered in "Site Name:" in the "Publishing" area.
Website URL:
This is the root website depending on whether it is "students" or "faculty". Since iWeb will append the site name to this root website, I accomplished what I hoped to accomplish in this post (http://discussions.apple.com/message.jspa?messageID=12288561#12288561).
Faculty sites will be @ http://faculty.myschool.org/username. Students @ http://students.myschool.org/username. PERFECT!
iWeb is such a GREAT tool - NOW the kids can start using it!
I want to reiterate that this works for our school but it should work for you as well. There may be better ways to do this but it works for us.
Hope this has been helpful and you won't have to spend weeks trying to figure this all out by yourself!

OK...here's how we did it.
To get access to the website you created from outside your network there are a couple of steps.
First, you have to have a STATIC IP address from your ISP. If you have a T1 circuit, no problem...you usually get a couple of static IPs you can use. However, if you have a cable modem circuit, most likely you have a dynamic IP address which changes when you connect to the internet. Usually a static IP will cost a bit more because the ISP has to go through a couple of steps to set it up for you. But once you have the address, you now have a way for folks outside your network to connect with you.
(I’m also assuming that you use a router of some sort through which traffic flows out to the internet and that you aren’t using connection sharing or something like that.)
The next thing you need to do is have your new static IP address associated with the server on which you are hosting your website. You've probably already done that if your website works inside your network. However, you've associated a private ip (192.168.x.x, etc.) to your web server. That doesn't mean anything to folks on the outside because private IP addresses are just that - private - folks can't access them. (I won't get into VPN because that's a whole other topic.)
The way you associate your new static IP address to your web server is through some sort of dns application from your ISP. For example, we use TierraNet to manage our external DNS information. They have a web interface control panel that is very similar to the DNS interface for XServer. You can create CNAME records (aliases - other ways that folks can access your servers).
Basically you create an "A" (CNAME) record with a fully qualified domain name (e.g. webserver.myschool.org) and point it to your public IP address (XXX.XXX.XXX.XXX) which you just got from your ISP. It's going to take a while (24-48 hours) for this change to take effect. BTW, you can create as many “A” records as you want. For example mail.myschool.com and wiki.myschool.com could point to the same place.
You want to make sure that the fully qualified domain name you enter in the external dns utility matches the name you used when you created your internal dns records on your XServer.
OK...so now folks can get to your domain - but, remember, you have a private network IP scheme between them and you. You now have to tell your router that when web traffic arrives, allow it inside the network and direct it to your web server.
Let's say your public IP address is 205.100.112.50 and your web server is 192.168.0.5.
You have to create, in your router’s "Security Zone" (router companies call them different things) a couple of rules. Usually the first rule is: "Let everything inside the network get out to the web." You've probably already done that if folks inside the network can reach the internet.
You then have to tell the router to allow web traffic (port 80) into your network AND redirect that traffic to 192.168.0.5.
We use AdTran routers and they have a web interface which allows you to write "rules" affecting public and private traffic. Public is folks outside the network, private is folks inside.
AdTran calls them "Security Zones" and you modify those zones with policies.
So my "Policy" would say, in the above example, redirect traffic from my public IP (205.100.112.50) -> to my web server -> (192.168.0.5).
THEN you have to modify this policy with what AdTran calls "Traffic Selectors". You've said, OK, you can get in, but WHAT can get in?
The "Traffic Selector" is written to say: "Permit" "TCP" traffic from 205.100.112.50 only through Port 80. (That's the port that web traffic goes over. If you wanted a secure website, you'd add another traffic selector that opens port 443, for example.)
I'll tell you I'm no genius when it comes to this. I called AdTran and had them configure my router for me. I told them what I wanted done, they remoted into the router and configured it. But then I could go to the web interface and see what they did and then added rules later on when I wanted, for example, to get access to the network via Apple Remote Desktop or VPN into the network on my iPad.
I'd bet that your router has a maintenance agreement that includes this service and if it doesn't it should have.
I did find that I still had issues when I tried to set this up originally and it had to do with the ORDER of the policies. I can’t remember exactly what the issue was, but, effectively one of the policies highjacked traffic before the policy that I wanted got triggered. Simply moving them around in the list fixed that issue. So if you have this set up but still can’t access the site, check the order of your rules.
I don’t know if that helps or not, but I try to think about this stuff conceptually and then get someone to help me with the details. I work with this stuff so infrequently that I forgot how I did something 6 months or a year ago. I’m in the process of creating a wiki for the school which documents all this stuff, but that’s a major undertaking.
Cheers,
John

Multiple websites, multiple woes: Best IWeb 09/MobileMe strategy?

I'm still a bit confused as to the best strategy for using IWeb 09's much-touted-in-reviews but apparently rather limited ability to publish to two or more separate MobileMe accounts.
In IWeb 08, I would set up several different user accounts on my Mac, associate each one with a separate MobileMe account from my Family Pack, and maintain separate domain files for each (all stored in the same folder on my hard drive, but given different names like "Domain_personal" or "Domain_business"). This worked fairly well, despite the inconvenience of sometimes not having a photo I wanted to use readily available, as it might be part of an IPhoto library that belonged to another account.
(I would generally log-in to the user account I wanted to use and work on the MobileMe domain file I had "assigned" to that account. But now and then I might forget, and start working on a domain file for the "wrong" Mac user account. That didn't seem to be a problem -- I could still save my latest changes, log out and then log in to the "right" user account, where I could publish my revised domain file to the intended MobileMe account.)
But in IWeb 09, my previous strategy is resulting in a slew of problems. Unexpected crashes. Or IWeb refusing to save a file after I've changed it (it just tells me the file cannot be saved, no explanation). Or images and/or video files that will suddenly go missing. Last night I found that one domain file/site I had published over and over with no problems in Iweb 08, now appeared to be a complete mess in IWeb 09 -- numerous missing images, including some png files that are apparently part of the Apple-supplied IWeb design template. Yet the graphics (mine and Apple's) were suddenly back when I opened that same domain file in another user account on my Mac.
So my IWeb 08 strategy does not seem to be working in IWeb 09. I guess an alternative would be: Do all my IWeb work in the same user account, swap domain files as I'd been doing before, and reset my MobileMe identity for that user account every time I want to publish. Or -- essentially the same thing -- use IWeb's ability to maintain multiple sites in the same domain file. But once again, I'd typically need to manually change my MobileMe identity to a different account at publishing time, to get an individual site going to the right place. And hope like heck that I don't accidentally mess up ICal, etc., by accidentally syncing to "wrong" Mobile Me account, to which I've logged in solely to accommodate IWeb.
Am I missing something here? Is there some logical reason why Apple would set up IWeb 09 to allow you to publish multiple sites, stored in one domain file, to various multiple external sites via FTP with ease? But make it essentially impractical to publish to several different MobileMe accounts, without the hassles I've mentioned?
It seems to me that if I want to use IWeb 09 for multiple web sites, the only sane thing is to drop my extra MobileMe accounts as soon as possible, and add some more external sites --- since (if you can do the RSS, etc., yourself) Apple has just made it so much easier to publish to anywhere-else-but-MobileMe.
Anybody have a different take on this? Or a better solution?

webalias rex wrote:
Anybody have a different take on this? Or a better solution?
The following may not be a better solution, but it does provide a different "take". I haven't tried it myself, so I wouldn't be surprised if there's a fatal flaw in the idea. Anyway, taking that risk...
Since we don't know what, in iWeb '09, is causing your "slew of problems", it's not possible to say whether this proposed approach would make any difference. But in theory it would enable you to:
• maintain your separate Domain files
• publish to your multiple MobileMe accounts
• from the same user account on your Mac.
Take a look at this Apple doc:
MobileMe: How to publish a custom website
The idea is to publish your iWeb sites to different MobileMe accounts from a single Mac user account as +"custom websites"+ and, as that doc says:
"If you only plan to publish custom sites to your MobileMe account, you can make your site's URL shorter by placing your site (and its main index.html file) in the main Web/Sites folder instead."
...Presumably iWeb 09's integrated non-MobileMe publishing is FTP only, not WebDAV that iDisk requires. So you would need the free Cyberduck or pay for Transmit to publish your sites via WebDAV protocol to a MobileMe account's iDisk. And for a Domain you are about to publish, you would have to remember to use the appropriate MobileMe "destination" of the several you've set up to use in Cyberduck or Transmit.

Adobe Muse keeps crashing every time I publish any website all of a sudden

Adobe Muse keeps crashing every time I publish any website all of a sudden. Not just for the website I was working on but now all my websites. It was working perfectly fine and when I hit publish it just crashes. I have multiple copies and different websites and they are all crashing when I try to publish. It seems like it is not an error for just the one website I was working on but the entire program is not functioning correctly. Here's a screen shot of the error.

Mac or Windows? What's the error that appears? If it's an Apple Crash Report, please copy/paste the first few pages of it here.
I strongly recommend against it (for multiple reasons below) but if you uninstall Muse, then go to the Creative Cloud Desktop App, and choose "Previous Version" in the Find New Apps section there will be a dropdown arrow next to the Install button. That dropdown will list all versions of Muse.
If you've saved over top your existing file using the current version, reverting Muse won't work, since older versions cannot open files saved from newer versions. If you've don't significant work in the current version, that will be lost because you'll have to go back to the file as last saved using the prior version of Muse. Finally, there's a significant probability that error/crash is related to content in the file, network configuration, or other outside forces and if that's the case reverting won't avoid the error/crash.
If you share more info about what error you're encountering, I expect we can determine a workaround/solution.

Multiple websites on multiple user accounts. Want all websites in one user

I have multiple websites in multiple user accounts. At the time I started this way iWeb 08' didn't allow more then one website per user.
I now have three limited user accounts with three iweb sites. One in each account. I'd like to move two of them to the main user account and have all three available to me in the user account I call mine. Is this possible with iWeb 09'? i can, by hand, recreate them in the main account, but I'd like an easier solution.
I am hoping it is possible to combine the files from each "Domain.sites" and make one magical come together with each site in place.
Thanks Everyone

Move all of the Domain.sites2 files to one user account and rename them to represent the site inside, i.e. Myfirstsite.sites2, Mysecondsite.sites2, etc. Put them all in your User/Library/Application Support/iWeb folder.
Using the application suggested by Wyodor merge the sites into a new domain file. You can only merge 2 sites at a time so you'll have to do 2, then select that new one and merge with a 3rd file, etc.
Click to view full size
New domain files are created by the merge process so your original domain files will be untouched.
OR, you can leave the domain files as they are, named individually, and use iWebSites to choose and open the site you want to work on and publish. I manage multiple sites with iWebSites:
This way the domain files loads more quickly and if there's a problem only one site is affected.
OT
Click to view full size

TS2167 I am running OS X 10.8.2 and IWeb 3.0.4 (601) and everytime I try to publish my website I get an unexpected error and it does not publish my changes. My website is pretty simple, mostly made up of iPhoto albums in different categories.

I am running OS X 10.8.2 and IWeb 3.0.4 (601) and everytime I try to publish my website I get an unexpected error and it does not publish my changes. My website is pretty simple, mostly made up of iPhoto albums in different categories.

Where are you publishing to? Can you publish successfully to a folder on your hard drive? Have you read this webpage: Publish iWeb site using FTP. It may have a clue to where the problem is.
A quick troubleshooting fix is
Try the following:
1 - delete the iWeb preference file, com.apple.iWeb.plist, that resides in your
User/Home/Library/ Preferences folder.
2 - delete iWeb's cache file, Cache.db, that is located in your
User/Home/Library/Caches/com.apple.iWeb folder (Snow Leopard and Earlier).
3 - launch iWeb and try again.
NOTE: In Lion and Mountain Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
However, when you delete the preference file you probably will have to use the app described below to select and open your domain file with iWeb:
In Lion and Mountain Lion the Home/Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
To open your domain file in Lion or Mountain Lion or to switch between multiple domain files Cyclosaurus has provided us with the following script that you can make into an Applescript application with Script Editor. Open Script Editor, copy and paste the script below into Script Editor's window and save as an application.
do shell script "/usr/bin/defaults write com.apple.iWeb iWebDefaultsDocumentPath -boolean no"delay 1
tell application "iWeb" to activate
You can download an already compiled version with this link: iWeb Switch Domain.
Just launch the application, find and select the domain file in your Home/Library/Application Support/iWeb folder that you want to open and it will open with iWeb. It modifies the iWeb preference file each time it's launched so one can switch between domain files.
WARNING: iWeb Switch Domain will overwrite an existing Domain.sites2 file if you select to create a new domain in the same folder. So rename your domain files once they've been created to something other than the default name.
OT

Creating Multiple Websites

I want to create multiple websites which appears possible with iWeb but how will I visit the ones that aren't my primary site once they are published? Thanks.

The other sites will have a unique URL once they are published. When you do publish you'll get a window with the option to announce the site via email and it will have the URL.
I handle multiple sites by using iWebSites to create and manage separate domain.sites files for each of the sites. Like before, each of the sites will then have a unique URL address that I use.
I've found that it's easier to do editing on several sites and then be able to just publish the one I want this way.
Do you Twango?

Publishing another website

hi-
i have used iWeb to create my first website, which i'm publishing through .mac. everything's working fine, nothing to report.
i'd like however to publish another website, not related to first and was wondering why it's not working... i've created the second website and whenever i hit 'publish' nothing seems to happen. it looks like it's not published anywhere. when i select to 'visit the site', i'm taken to my first site.
are we only allowed 1 site per .mac account? is this why my second account is not being published?
HELP!
thanks!!
macbook Mac OS X (10.4.9)

Try clearing Safari's caches (CommandOptionE) and try again.
I use iWebSites to manage multiple sites.. It lets me create multiple sites and multiple domain files.
If you have multiple sites in one domain file here's the workflow I used to split them into individual site files with iWebSites. Be sure to make a backup copy of your Domain.sites files before starting the splitting process.
This lets me edit several sites and only republish the one I want.
I found that this method greatly increases my productivity as far as managing multiple sites.
Do you Twango?

I want to use the Web module to publish to the a website... What kind of server do I need to be able to publish my website?

I want to use the Web module to publish to the a website... What kind of server do I need to be able to publish my website?

You don't need a server, you just need a web hosting package such as the ones from GoDaddy or many other hosts. You then send the web gallery directly from LR to your web space.
As you're asking such basic questions, it might be best if you read articles like this and see if a friend or colleague can get you started.

Multiple Websites using iWeb

I currently created one website through iweb. www.michelemcloughlin.com
I now want to create multiple websites for clients, friends etc. Is it possible to do this? I have iLife 08, what would be the best way to do this?
help!!!

MicheleMc08 wrote:
Do you think its easier to buy ilife 09 and not need to go through this process of individual folders?
Michele ~ I think it's better to keep sites for different clients and friends each in their own iWeb Domain file — but that's just a personal opinion and others may differ.
Also, I have a mac account, if I were to design another website for a client do they need to buy hosting as well in addition to their domain name?
As above, I think it's better for clients and friends each to have their own hosting and domain name — although it's not necessary. Perhaps it wouldn't be inconvenient for you to have a close friend's site hosted on your MobileMe account. Also, there are some restrictions regarding setting up multiple domain names to a single MobileMe account — read more here:
http://iwebfaq.org/site/iWeb_Domains.html
With iLife 09 is the back up necessary.
Backups are always necessary — your Mac's internal HD could crash at any moment. Do you have a plan for when that happens? ...There are only two types of HD: Those that have crashed and those that haven't — yet:
http://www.shirt-pocket.com/SuperDuper
http://www.bombich.com/software/ccc.html
http://www.corecode.at/smartreporter
This back up.. can I copy this domain file and put it on an external hard drive?
Yes.

Publishing multiple calendars in iCal

Is there a way to publish multiple calendars in one view. It seems that I can
only view one calendar at a time. I want to be able to overlay all of my calendars
so we all know who's doing what when.
I''m a Mom with two girls with lots of sports activities, I want the girls to be able to view all events in all calendars like I can see on my Mac.
Thanks for any input.
Roberta

Hi Roberta,
You can publish multiple calenders by creating a Calendar Group. Here are some styp-by-step instructions:
- Open the menu 'File' and click the option 'New Calendar Group'.
- Once this new Calendar Group has been created, rename it (for instance to 'Family', 'Sports' or whatever you like).
- After renaming the Calendar Group, add the calendars which you wish to publish.
- FInally... publishing Calendar Group works the same as for single calendars (select the Calender Group and choose from the menu 'Calendar' the option 'Publish').
I hope this works.
Bas

Publishing multiple websites

Similar Messages

Maybe you are looking for