Beginning iWeb

2 questions:
1. i made some text that is in quotes, i.e., "How America Lives"
and Ladies' <<--apostrophe.
iWeb using Safari is not rendering those properly.
<a class="jive-link-external-small" href="http://">http://www.math.fsu.edu/~trogers/data/pics/LHJ/
2. how do make it stop using the site and page title in the absurdly long URL?
thanks!

iWeb using Safari is not rendering those properly.
http://www.math.fsu.edu/~trogers/data/pics/LHJ/
I see it on FireFox in WinXP as well. I see that you are hosting on a non-.Mac server. The strange characters could be either a server encoding incompatibility or an FTP settings issue. Tom Gewecke has some tips on troubleshooting and resolving these issues here...
http://homepage.mac.com/thgewecke/iwebchars.html
2. how do make it stop using the site and page title
in the absurdly long URL?
If you ask me, this is the #1 biggest and most boneheaded "feature" of the current versions of iWeb. It creates more problems than it is worth and gosh darnit I hope something is done about this in iWeb 2.0 (if we have to wait that long). It limits what people can use for their page names in the navigation menus and such. If you have illegal (from a URL standpoint) characters like apostrophes and colons or forward slashes or percent signs, this direct conversion to the URL also wreaks havoc for website navigation.
I'm totally with you on this. Unfortunately, there is no remedy right now, unless you want to set a simple site/page name in iWeb, publish, then go into the HTML code and edit all the title attributes yourself. And this still wouldn't work for the navigation menu directly.

Similar Messages

  • How Can I make a movie on my iweb begin playing before it is fully loaded?

    OK, Forgive me in advance. I am a new "Mac Man". 5 days and counting. I just published a web site using iWeb 09. I have a 12 meg movie on the page. The movie doesn't begin playing until it fully loads (takes about 60 seconds). How can I make the video play as the rest of it loads. (like it does on Youtube)?
    Thanks in advance,
    Greg

    tip for a new mac man. the inspector is your friend.

  • IWeb crashes the moment MobileMe begins synching

    Every time I'm in iWeb working, when the MobileMe sync menubar tool begins to spin indicating it is working, iWeb ''beachballs'' and then crashes. It's particularly frustrating when I've forgotten to hit ''save'' every time I change something.
    Any suggestions how to fix this or is this just yet another MobileMe specific glitch in a long line of them that will ''be fixed when it's fixed.''

    I don't know of a fix but as a workaround set the MobileMe sync to manual and sync only when you're now running iWeb. At least until you find the cause and solution.

  • I have more problems in iWeb than I can begin to describe.  For one, after an "unexpected shutdown" of iWeb, it just deleted 10 of my published pages.

    I published the updates to my site last night.  Today I have had to make some adjustments.  I saved iWeb before I left for lunch just in case.  After lunch, I made more changes and through an issue with a photo album, iWeb "unexpectedly quit".  When I went to Revert to Saved..., it did revert to saved, which I didn't realize until then that somehow iWeb had deleted 10 pages before I saved it.  So now I have lost 10 pages. 
    Every time I open iWeb, it tells me it no longer has the links to documents or any of the pictures.  Every time I work on iWeb, I have to reattached all the documents and re upload all the pictures all over my site.
    I could write for hours about the problems with iWeb.  Certainly I am doing something wrong ... but my IT company has no idea what is wrong or how to fix it.
    I have iWeb version 3.0.4 (601)

    First replace your domain file that's in the Users/Home/Library/Application Support/iWeb folder with a backup copy that was made before this happened.
    If you don't have a backup copy 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.
    OT

  • Cant change my iweb photo's, they appear wrong to begin with

    i published my photos to a FTP server using iweb 09 to make the web pages. Once I published, everything looked ok. Then when i visited site- photos were doubled, and in the wrong area. I open iweb again and tried to correct it and re-publish changes....but when i visit site again- nothing has changed. Anyone have similar problem or solution ideas?

    First scan you system with the free tools OSX/OpinionSpy Free Detection + Removal Tool & DNSChanger Removal Tool and scan you system. If nothing is found it might be time to reset your internet connections.
    When you open System Preferences->Network pane make sure the lock In the bottom left corner is unlocked, before you try to change something. No in the Network pane can you click on the 'Advanced' button?

  • IWeb Problem beginning

    I have a slight problem with iWeb.
    Opening iWeb for the first time i get iWeb open but its disabled and empty, i wish i could post a screenshot.
    I beleive normally yoy get a dialog asking to select a template, but i dont get that. I get a sidebar with a empty "site" tree. The add button is disabled, the secondary click shows "New Page" disabled.
    Please help

    i just reinstalled iWeb. Get the templates screen now..

  • How can I Publish to a Folder just one of the several websites I have created using iWeb?

    How can I Publish to a Folder just one of the several websites I have created using iWeb?
    it drives me nuts having to emove all the other websites when I want to upload one. 
    Sparrow

    For iWeb, I like to do only one site per domain file.  I move domain files out of the Application Support folder and place them inside project or client folders, or in DropBox. Once you duplicate a domain file and begin customizing it, it will load and behave as a separate project/site.
    I publish each iWeb domain/project direct to a server via FTP. Sometime I publish to a folder, then upload via FTP manually.
    iWeb is a remarkable tool, especially when you work from scratch with blank tamplates
    Here are a few of my iWeb sites:
    http://www.newcovenant.org
    http://www.visionmultimedia.org
    http://www.visioncomsolutions.com

  • Display data from CSV file in iWeb page

    Hi,
    I like to display data from a CSV file in iWeb page if a date value from CSV file matches todays value from the system. Here is an example.
    CSV data values
    01/20/2011,Sunny,87
    01/21/2011,Cloudy,100
    01/22/2011,Rainy,60
    If today's date value is 01/21/2011 the page should display 01/21/2011 Cloudy 100 in a tabular format.
    Appreciate your help in providing HTML code for this issue.
    Thanks

    I suspect there is a soft return in the excel database somewhere that can't be seen. Take the csv/txt file into notepad and look for a line that starts oddly compared to the others.
    I haven't had luck removing soft returns from excel files so I do this a rather odd way. I take the excel file into InDesign as a table, and then use find/change to replace any soft returns with nothing, then convert the text to table and then export the text out again by going export, and selecting text from the dropdown menu.
    For my money, I always save tab delimited text files from excel so that if a field does contain commas, it doesn't "trick" indesign into thinking a new field is beginning or not... instead the field delimiters are tabs and they are unlikely to have been used in the excel database.
    If you do choose to use this indesign import method of mine to clean up the database, i also noticed two things in your screengrab: first was that some fields have spaces at the start of the text... easy enough to fix with a GREP that looks for ^\s (start of a sentence followed by a space) and replace with nothing. The second thing is the T&C field that all entries (at least in the screengrab) all start the same – if all entries in the database start the same, couldn't that line be in the indesign file? Its only a small detail I know.

  • How to stop text box on iWeb page from automatically reverting to hyperlink when I click 'save'

    As far as I see, the main text box in the body section of my iWeb page reverts to a hyperlink (connecting to a file) when I click save.  I don't know how the hyperlink got activated to begin with--I must have done something, but I don't know what it was.  I tried this many times to fix it: went to Inspector "hyperlink" section, activated the text box in the page, un-clicked "make hyperlinks active" (so they are inactive), then un-clicked "Enable as a hyperlink."  That much works--the hyperlink (little white arrow in blue circle) disappears from the lower right corner of text box.  But as soon as I save (command S), the text box reverts to a hyperlink. 
    If I don't click save and move around the pages, it does not revert to a hyperlink.  It only reverts to a hyperlink when the file is saved.  Why is it doing this and how to stop this from happening--how to permanently return the text box to a non-hyperlink?
    The website page is: http://www.usronline.net/USR/VedicResearch.html.  If you click anywhere randomly in the main text, you'll get a prompt to download a PDF file.  This should not be, but I can't get this hyperlink to go away for good.
    Many thanks in advance.
    Vishnupriya

    Please pardon the reply delay--a big project deadline had to be met.  Now back to this work:
    Yes, the text in the oval object had a drop shadow (the oval object itself did not).  I removed the drop shadow from the text, but the image file icon stayed in the right corner of the oval object.  I deleted the text and then the image file icon disappeared.  But as soon as I typed text again inside the oval object (not even pasting the previous text) the image file icon appeared again.  I deleted the oval object entirely and simply typed the text inside the main text box itself.  The image file icon that was attached to that oval object is gone (along with the oval object).
    Still the image file icon is attached to the main text box, though.  I again tried to uncheck the Enable as hyperlink (same process as described in first posting) with that oval object gone, but when I "save" again it reverts to a hyperlink. 
    Next I tried this: I copied the text from the problem text box and pasted it into another text box (outside of the problem one).  Still in the new text box with the pasted text, the image file icon shows in the upper right corner. 
    I also removed all the drop shadow features from this main text box (there was one more, on some words typed in the main text box), but it is still showing as an image.
    I don't know how it became an image file, and I'm still stumped as to how to fix it (short of forgetting about trying to figure out how it became an image and just retyping all text into a new text box).
    The link you provided for "Web Safe Fonts" is returning this: "The server at www.ampsoft.net is taking too long to respond."  I'm using Arial and Georgia (Georgia only on the menu and header text) in the site, and I had verified before designing the site that these are web safe, so I had thought they were.
    If you or anyone have any further suggestions or suspicions on this matter, I'd be glad to hear them.
    Thank you.

  • I've Made the Switch (from iWeb) &amp; 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

  • Best options for life (gulp) after iWeb...

    Hey Gang,
    Been using iWeb since its inception. I've learned to love it.
    Well- with the begining of iCloud and the transition away from MobileMe I see the writing on the wall. I realize alot of people will continue to use iWeb but I want to be proactive as I have several business websites created on my iMac.
    About 2 years ago I had a strange backup issue and lost everything. I nearly switched off of iWeb at that time but I just loved it too much.
    I want to start making the switch sooner than later as I know that Apple will eventually not support iWeb. It's only a matter of time before there is some quirk with a new OS version and it probably just won't open or whatever it may be...
    So- yesterday I spent 12 hours and tried out each of these sites: Wix, Snappages, Webs, Intuit Websites, Weebly, Yola, Google Sites, Jimdo, Roxer, Neosites, Vistaprint, Moonfruit, and Squarespace.
    They all left ALOT to be desired except Squarespace. I think it has potential.
    As an alternative, I also downloaded Adobe Muse and did not like it at all. I used Rapidweaver in the past and didn't think much of it. I see their new version is packed with tons of extra costs- no thanks!
    I'm left with Sandvox which I am going to try today.
    Here's my question: What do you folks suggest? Moving away from actual software (Sandvox)? Transitioning to web-based (Squarespace) ? I really like the drag/drop functionality of iWeb but realize I might have to make some concessions!
    A concern is working on multiple sites that reside on my comouter and constantly having to backup. I might be creating 2-3 more sites for friends so that would mean I have close to 10. Do I really want to do that and essentially become a webmaster? No so sure.
    I welcome all suggestions!
    PS- I'm not a newbie but I also have not created and uploaded via an ftp/host. I do however have domains etc...
    I'd like to do what is easiest and makes the most sense in the long run..
    D

    A few months ago I had a look around at what was available in the way of software and you can download a PDF from this page under "Alternative Website Design Software"...
    http://www.iwebformusicians.com/iWeb/Why-iWeb.html
    The main alternatives to iWeb, such as Sandvox and RapidWeaver, were not an option for me since they suffer from the same restrictions and cost a lot more. The other available drag and drop style software is either flawed or like, Freeway, antiquated and badly designed.
    The online site builders do seem to offer a good alternative but they can be just as restrictive, cost a lot more and still produce huge ammounts of code. Some claim to be free but you need to look at the real cost - especially if you have more than one site. They do offer portable versions of the site suitable for iPhone etc and this has become a necessity - at least for a business site.
    I chose to move on to a code entry style software and this has proved to be fairly easy since the one I use is WYSIWYG and I can see the changes in real time in the preview window. Its also cheaper than RapidWeaver and Sandvox and doesn't require add ons to optimize and upload the files.
    HTML5 will allow us to build better, more efficient websites but its not quite there yet. If I hadn't made the move to code entry software I think I would have been tempted to stick with iWeb for the time being and use one of the online site builders to create a separate portable version for cell phones as a stop gap.
    There has got to be a better way to create websites using drag and drop and I believe something will come along that will make apps like iWeb, Sandvox and RapidWeaver redundant. After all, why did Apple quit on iWeb?
    iWeb does offer two alternatives for publishing...
    http://www.iwebformusicians.com/iWeb/Publish-Website.html
    ... and there's any amount of hosting out there...
    http://www.iwebformusicians.com/iWeb/Website-Hosting.html
    The  MobileMe only features can be replaced with alternatives if you need them...
    http://www.iwebformusicians.com/iWeb/Comments-Password-Protect.html
    "I may receive some form of compensation, financial or otherwise, from my recommendation or link."

  • Brand New ilife 09, all uploaded except for iweb 09

    Hi There,
    All of the other programs (GarageBand, iMovie, iPhoto) have successfully installed onto my computer. But the one upload I was most interested in, the iweb, doesn't install!
    I have tried three times now. I see that you can customize the download and I've tried that twice. But even then the system is questionable because it says upgrade 0 bytes and it has said that from the very beginning.
    I'm so confused and disappointed. Very much looking forward to anyone's help.
    Thank you.

    Welcome to the Apple Discussions. It could be a damaged disk. Download and run Pacifist to find, extract and install iWeb from the iLife 09 disk. If it can't open the iWeb package to work with it then there may be damage to the disk. Check the disk beforehand for any scratches or abrasions.
    OT

  • What is happening to my website in iWeb? Why does it look like a blog all of a sudden?

    What is happening to my website in iWeb?  Why does it look like a blog all of a sudden?  Was there some kind of notification that I missed?

    Unless you give us the URL we can't possible begin to help.
    Happy Holidays

  • Is there a way to automatically have a web page begin to scroll down?

    Is there a way -- sort of an "autoplay" sort of way to have a web page begin to slowly scroll down to the bottom like a teleprompter automatically? I know this isn't technically iWeb but the site is created in iWeb and from that basis I'm sure I"ll have to edit the code somehow -- like is done when making autoplay movies and music.

    Settings > iCloud > Photos > My Photo Steam > On.

  • I can't update iWeb. Error message:  "The disk may be damaged or full, or you may not have sufficient access privileges." I had received a response that gave me the "best" FTP, it was one that gave each iweb user their own support person. Need info again

    I keep getting an error message, sometimes the beginning part changes but it always ends with the quote above. I haven't had the time to work ont his in a few weeks, but weeks ago I got a response that indicated the "best" FTP to use, because they give each iweb user their own support person with whom the user can speal everytime, instead of getting as new person each call/email.
    I am currently with 1&1.co.uk, which was recomnmended to me by a friend who is much more website intelligent than me: he designs websites for a living. They may very well be very good for someone who knows what they are doing, but they are not so good for me or for Apple users. Since I am paying every month for not being able to get updates published, I would be willing to pay for an FTP which would give me, a novice, resal Apple support. I also do not want to have to completely redesign my website or loose my website address, so I want to transfer the whole critter to a new FTP.
    Thanks
    Resolute Woman

    Here's the hosting that gives you a personal support person...
    http://www.iwebformusicians.com/iWeb/Website-Hosting.html
    As for your problem, try the troubleshooting steps under "Fix iWeb" here...
    http://www.iwebformusicians.com/iWeb/iWeb-Tips.html
    Also check the files you are trying to upload - especially image files - for spaces or special characters in the file name.

Maybe you are looking for