Updating published site

I published my site, and revised it several times, it worked like a charm.
However last night I was trying to revise it again but it would not allow me to.
It took the new info and went through all the steps to publish , then it asked if I want to visit the new published site, when I click yes it did not show the new changes. The old site remains , however when I go back to view from iweb directly the new revises are there.
Now this morning it will not even allow me to publish.
If I reinstall will I lose all my site info?
Does anyone know why this is happening or what I can do?
Much thanks in advance.

Yes, if you reinstall you will lose your site, all the data sits in.
User>Library>Application Support>iWeb>domain (this file is your site)
First thing to do is clear your cache in Safari, Safari > Empty Cache..
This often solves the issue of not seeing the changes.
Secondly, you could trash your iWeb.plist file, this is the preference file and lives here:
User>Library>Preferences>com.apple.iWeb.plist
Then empty your trash and reboot your machine and then reopen iWeb.
This is a harmless approach and could fix it for you without having to do a reinstall.
Will

Similar Messages

Update publishing site to web as well as folder

I have a site that I am publishing to my MobileMe account. I want to also publish it to a local folder so that I can make a CD from it for special uses. I have done both of these things, but the media files are not kept parallel --- the local folder is not replacing the QuickTIme movies I am using (although the MobileMe site did). I have deleted the entire local folder and republished everything and it still finds some old version somewhere (I have no idea where) of some files and publishes them. What's up?
Along the same vein --- maybe related? ---, when I update the media files (these QuickTime videos) the "publish site changes" in iWeb does not realize those files are updated and so does not publish the new files unless I publish the entire site again. What am I doing wrong?

Usually publishing to a folder will give you the latest in changes to the site. It's often the MMe version that has a difficult time. Strange. Try deleting the iWeb preference file, com.apple.iWeb.plist, that resides in your User/Library/Preferences folder, launch iWeb and try publishing to a folder again.
If that fails, you can, as a workaround, mount your iDisk, go to the iDisk/Web/Sites folder and drag your site folder to the desktop to get a local copy.
OT

Cannot update published website without errors: requires deletion of site, then creating a new one.

Hello all,
This has been a long persisting issue since we purchased Muse in January 2013, but has since then led to a shutdown of my office's website and email in September. Multiple support technicians were eventually able to restore the website, as well as our email function, but the core of the problem lies in the fact that when I update my website, it becomes entirely scrambled, and the only solution provided to me right now is that I need to delete my site completely (through Adobe Business Catalyst) and then create a new one, while transferring over the same domain information. I have yet to receive guidance on how to resolve this issue properly:
September 06 Email: detailing the series of events
Good evening, Zak,
I am reluctant to bring this to your attention because of the comprehensive nature of the following, but I have been told that my absolute last effort should be to contact you with what has been a persistent problem since the last time we had mediated this particular issue. Essentially, when publishing a website multiple times, sooner than later the format becomes scrambled when viewed online. I am being told I am the only customer known to have this issue, and that it needs to be investigated deeper.
This is a blurb from our original conversation in March 2013:
(The whole thread may be found at the following address: http://forums.adobe.com/message/5653912#5653912)
9.Zak Williamson (Adobe),
Mar 12, 2013 4:03 PM in reply to essbarr
I'm also puzzled. This isn't a problem I've seen before for a site published to Business Catalyst.
Please try publishing again, this time to a new temporary site (they're free). You can choose this option under More Options in the Publish dialog. I'm curious whether publishing to a new empty trial site works.
If that doesn't work, please send me the .muse file at [email protected] along with a link to this thread. If the file is larger than 20Mb you can use a service like Adobe SendNow, SendThisFile, WeTransfer, Dropbox, etc.
Thanks.
10.essbarr,
Mar 13, 2013 6:49 AM in reply to Zak Williamson (Adobe)
Hi Zak,
I published the website to a new temporary site, and it worked beautifully. Now I just have to fuss with the horizontal bar, and then I'll be super happy. Thank you for your help!
Sincerely,
Sarah
Since this bit of advice, I have freely published to a new temporary site every time the website gets scrambled. I have had temporary websites titled:
argponline01.businesscatalyst.com
through
argponline15.businesscatalyst.com
along with a bunch more than I cannot recall.
and Muse files titled:
argp-uc.muse
argponline.muse
argponline_02.muse
through
argponline_05.muse
argponine_3A.muse
argponline_3B.muse
and currently, my file name is
argponline_4.muse (dropbox link)
I am using Muse on a Mac Powerbook, OSX 10.8.4.
I don't know how much of the above is relevant, but maybe it makes a difference to you.
The timestamp on the following thread says September 5th, 2013 4.50AM, but I really sent it the evening of September 4th, 2013. No difference anyhow:
http://forums.adobe.com/message/5653912#5653912
What was going on in detail:
1
I made a few changes to my argponline_4.muse file on September 4th, 2013.
The published website at that point was argponlined.businesscatalyst.com (D).
The domain name was argponline.com .
(D) was published probably about two months previous, maybe longer ago.
When publishing (D) on September 4th, 2013, the website appeared scrambled.
I tried to publish only modified files, as well as publish the entire site, as well as close programs, and restart the laptop.
I decided to follow the advice given previously, and I published and launched argponlinef.businesscatalyst.com (F).
2
At this point I have two bookmarked websites for Adobe Business Catalyst Admin Consoles.
For (D), the Admin Console address was argponlined.businesscatalyst.com/AdminConsole/#!/Admin/Websites.aspx
For (F), the Admin Console address was argponlinef.businesscatalyst.com/AdminConsole/#!/Admin/Websites.aspx
I was able to sign into both.
When signed into the Admin Console for (F), I tried to Add a New Domain, but was told that I only had a plan for one hosted website through Adobe Business Catalyst, and that I would need to purchase a plan that offered more hosted websites.
I signed into the Admin Console for (D) and deleted the domain, but given the option to keep associated files just in case, I opted yes, to keep them.
When signed into the Admin Console for (F), I tried to Add a New Domain, but received the following error message:
Domain already exists. Please delete all records associated with this domain before re-adding it.
There was nothing visible though the Admin Console for (D) to delete the associated records, so I deleted site (D) in its entirety.
I continued to try to Add a New Domain for (F), but continued to receive the same error Domain already exists...
3
At this point (the morning of September 6th, 2013) we have the following set of parts:
The published and launched site is argponlinef.businesscatalyst.com (F).
For (F), the Admin Console address is argponlinef.businesscatalyst.com/AdminConsole/#!/Admin/Websites.aspx
The website is now completely down, and I have disrupted email service for the office.
I chatted with Lokesh, who determined this was a technical issue, and I was forwarded to Anshul.
Anshul's assessment is as follows:
Anshul: I see the error, Sarah it seems there are some Domain traces left with the system , I tried to clear then out and I am getting errors as well. In this case , we might need to escalate the case to higher level to have deeper investigation related to this issue.
Anshul: Sarah, the issue is the domain not the site. It seems like there are some traces related this domain in the backend. This issue is more of related to BC and not Muse. I will have this issue escalated and checked with the team and request them to run internal queries to clear the traces and then you should be able to add the domain.
4
Soon after I received the following message from Matt Baracz:
Matt Baracz (Adobe Business Catalyst Support)
Sep 06 10:50 (EEST)
Thank you for contacting us.
I have escalated this issue to our engineering team and have requested them to clear any references to the domain argponline.com from our database. Once cleared, you will then be able to re-add the domain successfully to your site.
As soon as I receive a response from engineering confirming that this has been actioned, I will let you know directly via this support ticket.
Regards,
Matt.
Around 3 or 4pm, I had not heard anything back, so I attempted to Add a New Domain through the Admin Console for (F). (Turns out Matt works in Australia, and was unable to alert me due to the time zone difference. Understandable!)
This was done successfully, so the website began to work again, but the email was still down.
5
I began a chat again, this time with Srividya. I was transferred to technical support and began conversation with Sanjit. The length of our conversation was probably around 3 hours, and I am so grateful for the time he put in. What a great guy.
He stated that he had gone through the case details and that Engineering had fixed the issue. We spent some time coordinating the Site Domain information through the Admin Console for (F). Ultimately, email is still not working (settings were probably updated around 5pm), but I understand sometimes it takes a while. Just wanted to note, the last time I updated the email settings it worked within a couple minutes. Varying lengths of time are expected, but I am still curious what effects those variations. Regardless.
6
The current situation is this:
My boss is a bit steamed that our website was down for a day and a half, and that our email is down for a relatively indeterminate amount of time. It's bad for business, and ultimately, I am responsible for these disruptions. I am incredibly concerned that the next time I update our website there will be a slew of problems, which have the potential to knock down service for the website and email again. I am desperate for a surefire way to simply and fluidly update our Adobe Muse website to Adobe Business Catalyst without making the same mistakes again.
I don't believe I did this the right way. I looked at FAQs, Community Forums, goDaddy Support and anything I could lay my eyes on to try to do things properly, but managed to make a few well-intentioned blunders. I continued to try undo the damage I've done in the past couple days, and with utter frustration, have not been able to fix them on my own. The people who have helped me thus far have done an amazing job, but ultimately, I am happier when I am not taking up their time, or panicking here.
When I first launched the website a few months ago, there was a step-by-step process that took me through every single action with screenshots included when appropriate. It was exponentially helpful. I was so lost without it this time around, and I was wondering if I could access it again in the future if needed.
The following is a blurb from my conversation with Sanjit tonight:
Sanjit: You have purchased Muse subscription , correct ?
Sanjit: or Creative cloud >
Sarah Rushing: Yes, we purchased Muse for 1-year, as well as Business Catalyst for 1-year
Sanjit: Perfect
Sanjit: With Muse you get 1 free site , so once you create a site and then publish to BC. In admin console you launch the site, that makes your free count used. Now if you create another site, then system asks you to upgrade the site to a paid site plan. ut when you delete the previous site then the free count becomes free and can be used for any other site
Sarah Rushing: Yes, that is what I did. Is this what I need to do each time? Because I am concerned that the email and website will be disrupted every time I need to make slight adjustments to the website?
Sanjit: No, you dont need to do that everytime. If the site is scrambled everytime you publish then please report to us. Thats not the ideal way for solution.
Sarah Rushing: Well Sanjit, I can tell you right now, that is how it has been functioning since we bought the program. I am not entirely certain, but I believe we bought Muse and BC in January.
Sarah Rushing: I can absolutely guarantee you that the site will inevitably scramble. Am I the only customer you have heard of to have this issue?
Sanjit: Yes, i have not seen any other reports for this issue
Sanjit: Well this needs a deep investigation
Zak, anything that you could offer for clarity of process, would be incredible. I don't know if you will have time to look at this before Monday, but I can tell you I will be available at a moment's notice to fix this issue and to learn anything about Muse and Business Catalyst that you have to offer. Thank you for your time, and I hope you have a wonderful weekend.
Sincerely,
Sarah Rushing
I'm concerned that no one will really read this because it is so detailed and boring and comprehensive, but it is absolutely critical that I find a proper solution before the next update to the website. Thank you so so much to anyone who can possibly provide some insight into this issue.
Sincerely,
Sarah Rushing

In case anyone is experiencing the same issue, I am trying this today.
Sachin: Okay Sarah, so is it everytime you try to republish the website, it gets scrambled?
Sarah: Yes, that is correct. And the solution thus far was to publish to an entirely new site, meaning delete the existing one on Business Catalyst and transfer the domain information.
Sarah: The last time I did that I experience a slew of issues that resulted in no website and email for 4 or more days. My boss was very angry.
Sachin: Sarah, can you publish your site as a new trial site once.
Sachin: And provide me the URL.
Sachin: Then republish on the same trial site and let me check the results.
Sarah: If I updated the published site within the period of a day, it will be fine. It is when I update the next day or later than that, then the website appears scrambled. So I can create a trial site for you, but it will behave normally for now.
Sachin: Sarah, while republishing the site, did you select "Only modified file" or "All files" while publishing?
Sarah: I tried everything.
Sarah: I made a few changes to my argponline_4.muse file on September 4th, 2013. The published website at that point was argponlined.businesscatalyst.com (D). The domain name was argponline.com . (D) was published probably about two months previous, maybe longer ago. When publishing (D) on September 4th, 2013, the website appeared scrambled. I tried to publish only modified files, as well as publish the entire site, as well as close programs, and restart the laptop. I decided to follow the advice given previously, and I published and launched argponlinef.businesscatalyst.com (F).
Sachin: Okay. there is one more thing I would like you to try.
Sachin: Publish a site as a trial site.
Sachin: Then wait till tomorrow.
Sachin: After that login to the admin panel of the site.
Sarah: Okay
Sachin: There go to Site Manager>File manager
Sachin: There will be a file there named Muse_manifest.xml
Sachin: Delete that file and then republish the site from Muse.
Sarah: So in the Adobe Admin Console, underneath Site Manager, I see Web Forms and System E-mails. No file manager?
Sachin: Please hover the muse on your name at top right corner and click on My details.
Sarah: Okay, yes.
Sachin: Now scroll down and check the option that says Enable online content editing (incompatible with Muse)
Sachin: And then click on save.
Sarah: What does this do, and why does it say it is incompatible with Muse?
Sachin: It will help you see other options in BC.
Sarah: Okay, thank you.
Sarah: I see the File Manager now
Sachin: Okay.
Sachin: Now select the file named Muse_manifest.xml
Sachin: And use the delete button on the right side.
Sachin: but do it tomorrow
Sachin: With a trial site
Sachin: Not with the live site.
Sarah: Okay, could you please explain to me what deleting that particular file is supposed to do? I am just very interested in how this works.
Sachin: This file contains the information about your last upload.
Sachin: Deleting it will make sure that "ALL" the files are uploaded again from Muse.
Sarah: Okay, so:
Sarah: I will publish a trial site.
Sarah: Wait until tomorrow.
Sarah: Publish again. If I have an issue, I can log-in to the admin console for this particular trial site and go to Site Manager --> File Manager, and delete muse_manifest.xml.
Sachin: I will create a case for you and you can respond to the case.
Sachin: Correct.
Sarah: After that, I will try publishing again and see if it resolves the issue.
Sarah: That would be great, thank you Sachin.
Sachin: Thank you for contacting us. Have a Good Day!

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

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

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

Updated a page and now the "Publish Site" stays gray and can't update the site. What's up?

Updated my iWeb page and now it won't publish. "Publish Site" stays gray. What to do now? I'm not using Mobil Me. FTP published. Workd before. Haven't a clue now.

Try making a minor change to that same page, like moving an object a couple of pixels one way or the other, and see if the File ➙ Publish Site Changes menu option will work for you.
OT

Re Creation of Site Assets Library after Publishing site Title update

For some reason we don't need Site Assets library in publishing site so we have decided to delete that. But after Publishing site Title update Site Assets Library is getting re created . What would be the possible reason for that . Whether Publishing
feature is getting reactivated whenever title is getting updated.
Ashish Baranwal || To know what you know and what you do not know, that is true knowledge

Hi Ashish,
SharePoint Designer has the setting "Hide from Browser' to hide the List/Library from browser.
It only restrict the user to view the List/Library links from browser,but if user directly use the URL to reach that List/Library and the user can edit or add new items.
Better set the ready only permission to users and set the "Hide from Browser" to the Site Assets library through SharePoint Designer.
Follow the steps to hide the Site Assets Library through Designer:
In Site Object Section, Select Lists and Libraries
Select Site Assets Library on right side, it's navigate to List Settings
In List settings-> General Settings, Uncheck option “Display this list on quick launch”. [This is necessary], Check the “Hide from browser”.
Save the list.
Now the links are hidden from SharePoint Site in browser.
Follow the steps to Unhide the Site Assets Library through Designer:
Open SharePoint designer 2010.
Click the “All Files” folder at the bottom in left pane.
Right click your hidden list from “All Files -> Lists” folder and choose property.
Now you have your hidden list open in SharePoint Designer.
In List settings-> General Settings: Uncheck the “Hide from browser” and save.
Now the links are visible in SharePoint Site.
Indul Hassan
Microsoft Community Contributor
http://www.indulhassan.com
You Snooze.. You Lose !!

Unable to update/publish my site

Hello,
I updated my Blog last friday, it was working correctly, when i was in france.
Now i'm in California for 3 weeks, i must update my blog during my holidays, right it doesn't work !!!
Error during the publication..... "name of site/blog/"
Is that the same for you.?
I've got the lmessage only for the Blog part, for my 3 website.
Is that general issue?

Try publishing the site to a folder on your desktop. You can change the destination of the published site by clicking on the site folder and selecting where you want to publish it in the drop down menu in the window.
Click to view full size
If it won't publish to a local folder then you may have some damaged files in one of the sites pages.

I had my websites set up in iWeb on macbook. just purchased a new MacBook Pro, downloaded iweb09, and transferred all my iWeb content. I publish to local folder using filesilla. why don't i see my updates on site?

I recently purchased a macbook pro with osx 10.8.3. my websites are set up using iweb. i downloaded iweb 09 and transfered my files to iweb, published to local folder, filezilla seems to be working fine, but when i visit my site there are no changes. when i view published site the changes are there. what is the problem? can someone please help

If the files are in the right location on the server and you are sure they are replaced, then the only thing left to do is to clear the browser cache and reload the page.
Standard procedure.

Why is my published site not operational when using Firefox or IE?

The original problem I experienced had to do with the fact that my published site's navigation bar was totally missing on each page and replaced with a "period" as described by the following thread... http://discussions.apple.com/thread.jspa?messageID=9899999&#9899999
The weird thing is that this problem only exists when using IE or Firefox on a PC (at work). Site is 100% operational using Safari on a Mac (at home).
Thinking my iWeb files were corrupt, I uninstalled and reinstalled iWeb '08. After doing so, I republished my site. The good news: the nav bar is now present on each page and operational. The bad news: my photo pages and blog page have zero content other than the header banner and nav bar. Again, this problem only exists when accessing the published site using IE or Firefox on a PC. The site is fully operational and all photos/blog entries present when accessing the site using Safari on my Mac.
What gives? Did a recent iWeb update (intended for iWeb 09 users or intel-based macs) corrupt my iWeb '08 on my PowerBook G4?

Please note that Java and Javascript are not related. iWeb uses a lot
of Javascript, not Java. There may be some issues with the Javascript
generated by iWeb -- I don't know. If it seems to work for someone
and not for someone else then it is an issue at the browser end, not
the website end. Each browser may not be handling the Javascript in
exactly the same way. (You gotta love standards.)
Dave

Can't publish site

Greetings People,
Is there an any server updating occurring?
I keep getting this error message when trying to publish site. Please advise. Thank you.

Hi Robert,
That means when in your home network, Muse is not allowed to make connection with the servers at business catalyst. Please check your firewall and make sure nothing is blocking Muse. Was this working before?
- Abhishek Maurya

IWeb not updating published status within application

I'm having a strange iWeb problem that just started up within the last day or so. When I publish any of the sites within my domain (I have seven separate "sites" that are all part of the same domain file) the updates get published to my site, but the icons in iWeb do not change color back to blue. This happens whether I choose to publish changes or publish all.
Another symptom of this problem is that my published site (http://www.adamreisinger.com) does not reflect the changes online until about five minutes after iWeb gives me the dialog box that my site has been successfully updated.
The only thing I've changed on my system recently is applying the last round of software updates, including the iLife update. I've tried trashing the application preferences and the iWeb cache and re-publishing, as well as logging out and logging back into MobileMe within System Preferences.
Any help in this matter would be greatly appreciated.

Thanks for the suggestion. I tried the steps you outlined, and unfortunately the problem persists. Also, because the files were deleted from the Web folder the iDisk, iWeb is now under the impression that EVERY page has been modified, which has actually increased my publishing time.
Some other troubleshooting steps I've taken to try and narrow down this problem:
- I've tried publishing the domain from a newly created user account on the same computer (MBP running 10.6.2 and all latest updates applied)
- I've tried copying the domain file to a different computer (one that has not had the latest iLife support update applied) and publishing from there
- I've tried publishing to a different MobileMe account (a test account set up by Apple)
- I deleted an entire site from the source list in iWeb (one that, fortunately, was not needed)
After all these steps -- tried individually -- the issue persists.

Publish site changes edits every folder in "entries" directory

I utilize Lytebox slideshows in my blog entries and have an issue with MobileMe erasing the necessary Lytebox files from every blog Entries directory (Web/Sites/Site Name/Site Name/Entires/Year/Month).
I always update my website via Files>Publish Site Changes. I publish to MobileMe so that I can make my site private.
I expect MobileMe to overwrite the files in the Entries folder for the specific blog entry I have created/changed, but why are the Lytebox files erased from every single Entries folder? I just did a test by making a minor change to a blog entry, publishing site changes and then using Cyberduck to check the Entries directory. Sure enough, every folder in that directory was modified.
As a result, every time I make any changes to my website, I have to upload the Lytebox files to every Entries folder, currently I have 15 of them.
Any reason MobileMe is doing this? Can I avoid this from happening? If not, I'll post another question about how to quickly and automatically upload the lytebox files to every Entries folder.
Thank you.

Any 3rd party files/folders used for java based slideshows in an iWeb site should be placed in the iDisk/Web/Sites folder and linked to there and NOT in the site's folder itself for the very reason you're experiencing. That is, they get deleted when the site is republished. It's the nature of iWeb.
You should use the following URL to link to a particular file in the Lytebox folder (assuming that folder is named Lytebox): http://web.me.com/MobileMeAccount_Name/Lytebox/Filename.
OT

Should I update my sites to iWeb 8?

I got iLife '08 the day it came out... and while I love the iPhoto improvements, I was very unhappy with some others. And I read (on these forums, amongst other places) that iWeb '08 "affected" websites created on previous versions of iWeb. For instance, that pictures and other imagery were buggy.
Is this still the case? Any other pros, cons I should be aware of?
The main reason I ask is that my professional site (hosted externally) is up, and just fine. But I need to make some minor tweaks and I don't want to have to re-do everything.
I also have 3 other sites (2 on .mac) that I've been "juggling" by keeping the domain files separate. ...How does iWeb '08 handle multiple sites? Or, at least multiple domain files?
Thanks in advance,
e

A lot of us have had problems with converting sites to iWeb '08.
None of mine converted satisfactorily and I keep them maintained with iWeb '06 as I rebuild them in '08.
If you do decide to convert, make sure you have backup copies of the domain.sites files in case the conversion doesn't turn out to your satisfaction. Also, I wouldn't overwrite an existing site on your server until you see how the new one publishes and performs as there can be layout problems.
I keep iWeb '06 and the old domain files on an external drive so that I can boot my Mac from there and update old sites without creating havoc.
Multiple sites can be used in iWeb '08 more or less the same as '06. You can store the domain files in separate folders or use the freeware application iWebsites.

Published Site Does Not Match Design File

I've published a website but it does not match the design file. It's showing an older version that has since been changed and not sure why it's picking up something I've updated and saved over many times. Thanks for any and all help.

And now I'm seeing a problem of a similar nature. The design and preview show a smooth transition between all pages, but the published site shows the logo in the upper left "jumping" when I leave the home page. I've checked the page properties between all of the pages and they seem to be set the same. I am using only one master page for all of the pages. Any ideas on why this would be occurring? The website is jacksoncompany.net.

"publish site changes" writes to a subdirectory, not correct directory

Heres a poser.
I enjoy iWeb because I can update my pages, and then iweb updates just those changes to my host. Been doing this for years. As my web site is fairly large, I have a main web site, and have created sites under that, which reside on the same root, that links in the main web site connect to.
Well, I just made some basic changes to three pages of one of my sub-sites, and when I updated changes, iWeb wrote the folder not to the root like the original, but inside the directory of the top web site.
So original files were never changed. I had to remove old folder from root, move the new folder to the root directory for the new files to appear. Very strange, since iWeb wrote the original folder and files in the root, but wrote the changed folder and files to a different place.
In the iWeb FTP Server settings, the directory path indicated does show the top or main site on the root level as the directory/path. If I remove it from the settings (leave directory/path blank), the whole site goes red, implying the whole thing needs to be updated. And if i start that, it states there is a folder already there with the original name, do i want to replace it.
What is mysterious to me is that iWeb wrote these sites for me, has updated these sites for me no problem, till now, when it writes changes to a subfolder instead of original folder in root.
Has anyone run into this? I am baffled, and have not made any changes to iWeb, my site, my settings which would explain this to the best of my knowledge.
using iweb 3.0.4, in OSX 10.6.8
thanks so much.

If anyone figures out why iWeb of its own accord started writing subsite folders to the home site folder instead of the root, let me know!
When iWeb publishes a website it publishes a site folder and an external index.html file. If you leave the site folder and index file in place on the server it will publish the new or changed files to that folder. That's how iWeb works.
If you want to avoid having the domain name twice in the URL change the site name to something other than the domain name. Then your URL will be www.domain-name.com/site_name/page_name.html.
When you publish just the contents of the website folder to the server you will get rid of the duplicate domain name BUT you lose the ability to use iWeb 3 to publish directly to the server. You will have to publish the site to a folder on your hard drive and use a 3rd party FTP client like Yummy, Transmit or Cyberduck to upload the contents of the webfolder to ther server. Wyodor's link explains it in more detail.
Or you could just leave the double domain name in the URL and not worry about it and rely on the content and appearance of your site to keep bringing the visitors back.
OT

Updating published site

Similar Messages

Maybe you are looking for