Is It A Mistake To 'Bet' On iWeb

I love the look of iWeb templates and the ease of incorporating streaming video, audio and photos. I also love the fact that I, without knowledge of html, can create a good looking site.
But I'm building a commercial web site that I hope will draw a large number of visitors. I also hope it will be advertiser supported. Am I making a mistake trusting this to iWeb and .Mac?
Do the software and the ISP have the heft to support me? Is anyone else using this as a heavily trafficed commercial site?
If you have easy-to-use alternatives that can handle more tasks and/or volume, please let me know. Also, let me know where I can learn to 'supercharge' iWeb.
I'll be very grateful for any insights.
PowerBook G4 Mac OS X (10.4.5) My web: www.newsroomconfidential.com

Also, let me know where I can learn to 'supercharge' iWeb.
There are some basic tips on my site www.willg4pb.com, and the Links page leads to more useful sites.
Also see www.iwebusersites.com to see some examples of what other people have done.
Will

Similar Messages

Firefox 3 beta 4 + iweb photo pages = not working

hello,
I just installed firefox 3, beta 4 and when trying to look at a photo page (which looked fine in the earlier firefox) on my site. The banner photo at the top loads, but no others do. Anyone else having this problem?
here is the link to the page I was trying:
http://web.mac.com/stephenjames716/home/saintpattysday.html
Thanks,
Steve

You're not alone.
http://discussions.apple.com/message.jspa?messageID=6858988&tstart=0

Something Better than iWeb?

I'm looking for a website program for the Mac that is as easy as iWeb but can build sites more like dreamweaver. I don't like iWeb because it's too private, family, media, mac like. Are there any programs for the Mac other than iWeb that are like this? (Without the confusing HTML).

Sandvox is fairly similar to iWeb and has a Pro version with added features...
http://www.karelia.com/
You could also have a look at Goldfish...
http://www.fishbeam.com/en/goldfish/
Shutterbug has a kind of quirky interface but has a lot of good features and is inexpensive....
http://xtralean.com/SBOverview.html

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

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

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

Comments and a question about iWeb

Hi all
I have recently created and posted my university web site using iWeb on the univerity server (using CaptainFTP). If you are interested you can look at it: http://host.uniroma3.it/linguisti/lcs-ingles/
I am quite happy with the end result. However, I am a bit disappointed at how slow the pages download on the university computers (no macs, unfortunately, and all using windows with IE). So I've put a banner for Firefox on my first page as it appears to work much better with iWeb-generated pages on Windows machines (at least the ones at the university).
I've also inserted comments on my newsblog using iComment (very easy to use!).
However, there is one thing I would like to be able to do, but not sure how possible it is. My students need to sign up for exams at the end of each semester (unfortunately, the university system is a total disaster!). Is there any way I could use some type of form for this? I realize that this is not possible in iWeb itself, but I thought there might be some way to integrate this capability. It would be great if this information arrived to me or the web page in an organized manner (so that I could easily pop it into an excel worksheet)... keep in mind that we have four different exams so I would also have to separate these entries (according to the exam that needs to be taken). I think that I'm asking too much.... especially since I have no experience with HTML programming (but I would be willing to learn some if any of you think it's possible to do this). If the students could sign up for their exams and then this information could be organized it would save me hours of headache (and it would also give me a clear idea as to how many people have signed up for an exam).
If anyone has any suggestions please let me know.
As always thank you all for your help.
Michael Boyd
Rome
iBook G4 12 Mac OS X (10.4.5)

I just did a quick search and all the posts I see are referring using a different editing program and a different host.
http://discussions.apple.com/thread.jspa?messageID=1675548&#1675548
You've already got the different host thing down since you're not using .Mac, but there's many different ways to do forms. I just did a Google search and found this presentation..
http://www.rochester.edu/its/web/briefings/webforms/sld001.htm
which gives some info into how it's done... the steps of which differ depending on the server you're using, the technologies available, and your level of skill. Looking at this, I'm not surprised Apple didn't implement it because it'd just be one more feature that only works on .Mac (since that's the only server where Apple KNOWS how it's set up).

IWeb '08 and non-QT video's

The current version of iWeb does a bad job of dealing with video that is not *.mov. It trys to use QuickTime to run wmv, mpg, avi, ect files. Only a few of the people viewing my site have QT installed and I don't like forcing them to install it. (Obviously they are Win Users.)
Is this better in iWeb '08?

partly!
quicktime will still be the main format - but you can add any other formats via the html snippets!
max

IWeb - Dream Weaver Tag Team

I used iWeb to design my site
and really dig how user friendly it is.
I don't understand why pro web design apps can't be this easy.
I want to use dream weaver only to make updates to my gallery.
This would keep me from having to re-upload the whole site with
any small change. Could someone point out how
I could add pix to my gallery in dream weaver and keep the layout from iWeb.
When I try to edit or add images it acts as though it is locked.
Sorry to ask a dream weaver question here. Here is my gallery. http://macmcrae.com/Site/GALLERY.html

Grant...
When you publish a site, only the pages that have changes to them get uploaded. To see this for yourself, you will notice in iWeb that any page on the page listing turns red when it gets a change. This means "has changed and needs to be published". So, iWeb is smart enough to recognize when something has been changed and not yet published.
Then when you tell iWeb to publish the site, watch the dialog that appears and you will see that only the changes page(s) get sent. It is likely true that iWeb sends everything on that page (all photos, for example) even for a minor text change on the page has occured. But this is much better than iWeb sending the entire site.
Jim

IWeb communication with FTP serve

I am trying to publish from iWeb to an FTP server. I have done this before with no problem. But using all the same settings, to update the site and replace pages, I keep getting the message,
PUBLISH ERROR
There was an error communicating with the FTP server try again later, or check with your service provider.
I have tried later for a week, with no luck.
I have checked with the service provider who confirms all is ok.
I have checked all the settings. The field path is blank, but I never filled this in the past and filling it now just brings up the message, path not recognised.
When I test the connection in iWeb (With path left blank) it confirms I can publish.
When I publish, it prepares the files and tells me publishing will continue in the background. Then after a while the message error message appears. It feels as if it is getting stuck.
I did try going round iWEB by using iWeb to create the site, publishing it to the local folder and then using classic FTP uploading the site to the host server URL. It works, but with errors and 404 messages leaving some pages either marked as 404 errors and others with bits missing.
Anyone got any thoughts.

Try publishing to a local folder and then uploading your site with either Cyberduck or Transmit and see if this makes a difference.
Check that all your files are being uploaded too - error messages can occur due to this.
If you are sure that you have done everything correctly - publishing your site to a local folder, and then filling in the correct username, password and ftp details in either Cyberduck and Transmit and checking to see that all files have been uploaded to whichever folder you need to upload them to - public_html, htdocs or whatever, then I would suggest that you contact your hosts technical support department to see why you keep getting error messages.
Do you have Linux or Windows hosting? Linux is always better for iWeb sites, so if you have Windows then try and change it.

Google Analytics Automator breaks iWeb blog comments

Hi
I added a blog for our Small Business site that I created with iWeb. We used Google Analytics and the Automator script add the HTML snippet to track visits on our site. Since I added the blog I realized that after running the GA automator script the "Add a comment" link disappears.
Kinda defeats the purpose of the blog. I have to choose between tracking how many visitors have been on the blog, or visitors posting comments, but I can't have both. How can I fix this and track how many visitors were on our site, and have a blog where visitors can leave comments? Any ideas and solutions would be most welcome. Thanks,
Zoltan

Unfortunately, as you have discovered, inserting Google Analytics into your site requires post editing. This means that you cannot just publish directly to MobileMe from iWeb - to insert the analytics you need to publish to a folder, insert and then place the Blog directly on your iDisk - unfortunately, this way you loose the features that your iWeb blog provides when published directly to MME - i.e. Blog comments.
Do you have an ordinary website too or is it just a blog? If you have an ordinary website, what some people do, including myself, is set up a blog with WordPress, E-blogger, or http://www.posterous.com and link to it from your iWeb site.
If you are just after setting up a blog on its own without a site, then I would suggest you look at http://www.wordpress.com, http://www.eblogger.com or posterous (link provided). You can set up a blog with any template you like and can add entries on line at any time, rather than being limited to updating with the domain.sites file as you are with iWeb.
In WordPress, you can also add as many pages as you like, so you can effectively have a website as well as a blog, so the other alternatives might be a better bet than iWeb and I think they have their own built in analytics too.

Having trouble editing iweb HTML. Help!

Hello,
I have been trying repeatedly to edit my websites html that I created with iweb. I bought the domain with godaddy.com and changed the cname to web.mac.com so that I could create pages and publish them to .mac, which would then show up on my .com name. After a few weeks of being satisfied, I wanted to make my site better, and iweb just wouldnt cut it. So now I have the html code for my front page of my website to include a random image upload each time the website is visited. I've been reading about how to edit the html in iweb in multiple forums and how-to guides, but none of it works for me.
I attempted to publish to a folder and then edit the html and save it in the same place, with the same name, but this didn't have any effect on the actual website. What do I do? Someone please lay this out for me step by step and tell me what I am doing wrong. This is frustrating! Thank you.

Thanks for your response. Your second idea is what I'm looking for ---I want a few images to display, one after another, while the homepage of my website is open. It's not really a banner that I want the images to sit in (I think of a banner as being at the top of the page). I want to position the images lower in the body of the page. I had researched this topic quite a few months ago and found some things that might help---that's why I didn't start a new thread---but I couldn't locate the information this second time. I guess it's time to start a new thread as you suggested.
I checked out your demo. I think that my images need to cycle a little more rapidly, but your javascript is doing the thing I'm looking for. I haven't worked with java. I"m pretty low on the totem pole of web construction. I know how to insert html snippets (impressive, hunh?).
Give this a try:
1) add a new page to your project.
2) add pictures to the page, keep track with their file names you'll need them for the script.
3) add the following javascript to the page using HTML Snippet:
<center><img id='imageholder' src='' ></img></center>
<script type='text/javascript'>
images = new Array();
images.push('P8080212.JPG'); // change this to your file name
images.push('P8080214.JPG'); // change this to your file name
images.push('P8080215.JPG'); // change this to your file name
// there is no limit to number of images
// to add image, add it to the page
// then add images.push('blah_blah'); to this script
var image_index = 0;
function rotateImage() {
if (image_index == images.length - 1) { image_index = 0 } else { image_index++ }
document.getElementById('imageholder').src = images[image_index];
setInterval('rotateImage()', 1000); // change this number to change rotation interval, 1000 = 1 second.
</script>
4) in those lines: images.push('blah_blah.jpg') , change file names (inside the single quote) to your image file names
5) size and place the HTML Snippet on the page.
6) Set the images' opacity to 0% after you are done so they won't show on your page.
That's it, there is no limit to number of images, when you add an image to the page, just add another line: images.push('blah_blah.jpg');
And by the way, I have Chinese Houses in my yard and was photographing Gilia a week ago myself. Are native plants one of your interests?
Yes, they are low maintenance, the Gilia aren't blooming yet.

IWeb sites in internet explorer

I have created a site for our company that can be viewed at www.ourlandscapers.com. On Safari & Firefox, it looks fine, but on Internet explorer (which 99% of our clients use), it looks like a big mess, with overwriting, field boxes, red x's everywhere, etc.
I don't know what I need to do to get it to publish correctly in Internet Explorer as it does in Safari, etc.

Welcome to the Apple Discussions. I noticed you used some none web safe fonts, Handwriting-Dakota for one. That won't play well with IE which is considered antiquated as far as browsers (but used by more people than any other )
Make sure you're using web safe fonts:
Web Safe Fonts
Common fonts to all versions of Windows & Mac equivalents
Safe web fonts
If you're using a non web safe font in other than an html link, you can add adrop shadow to it with the Font window and set the opacity to zero and the text will be converted into an image file that will look the same in all browsers. It may take a little longer to load than text but it will look good.
Others will be in to suggest other things you can do. It will not be easy to dumb down the site for IE browsers but you can get fairly close. IE 7, I believe, does play better with iWeb than earlier versions. You can also put a note on the site that it's best viewed with Safari for Windows or Firefox. Can't hurt to nudge them into the 21st century as far as browsers are concerned.
OT

Bad Quality When Sharing with iWEB

Sorry if this is posted somewhere on here. I could not find it.
I am having a problem with real choppy video when sharing with iWEB. My videos when viewed on my website are very blurry to the point that you can not see faces. Any help would be most welcome.

I am importing from miniDV. I believe it is HD, not sure if that matters or not. I recorded a clip off of the cam into iMovie. I added a soundtrack and a few sound effects. I saved my project and then shared it with iWEB. It is now on my website but just real blurry and the sound effect don't hit at the right times. It is perfect when view in iMovie (great picture quality). I also shared the same movie with iTunes and noticed, while better then iWeb, it is still not as good as when viewing in iMovie. Thanks for any help

Why iWeb will disappear ?

I want by a new Macbook pro 15" with Lion and I heard that in iLife application you do not have more iWeb!
Did iweb will disappear or it will be replaced by something better?

iWeb is no longer part of new iLife packages. Nobody knows if there'll be a new Apple equivalent.
However, if you have iWeb from an earlier installation of iLife, you can install it on the new Mac and it'll work fine.
Note also that iCloud will no longer offer website publishing, so you'll need to find your own hosting solution. (iWeb will publish to any FTP server you like.)
Matt

Will iWeb application ever be updated ? Alternatives ?

What a nice application! Today for the first time I was able to publish a five page website in just ten minutes without reading any documentation. Will Apple ever update this iWeb ?
If not, what is an alternative application the same or better than iWeb so one can FTP to a hosting website ?

No, I have not ever used Rage Webhosting, but I have used the product EverWeb with another host.
I think the reason that EverWeb was offered with Rage Software hosting was so that things worked better on their host as opposed to others - it was meant to be along the lines of iWeb and MobileMe hosting - so things like blog comments would only work if the site was hosted on MobileMe etc, however, I believe the Rage had a change of heart, so at first the contact form would not work on anything other than their own hosting, but they soon changed this.
Anyway, there is nothing to stop you going with GoDaddy or Blue Host - they may offer more benefits than Rage. I current have hosting with GoDaddy, Siteground and 1and1 and have uploaded an EverWeb site with Cyberduck with no problems at all.
The reason that I have used others hosts is so that I can change the platform that I use if I want to and GoDaddy, Siteground and 1and1 all support the CMS's like WordPress, Drupal and Joomla, which I have currently been using - Drupal is my favourite at present.
Anyway, good luck with whatever you decide to go with.
Other software worth taking a look at and that had come out with new editions very recently are Freeway Pro/Expresss 7 and Flux V. Perhaps a steeper learning curve though.

IWeb needs simple MySQL integration!

iWeb could be a fantastic program if it had MySQL integration, especially for those of us Mac users who like building CMS type sites. Better yet, iWeb would be the #1 web tool if it could build templates for Joomla, Drupal, Wordpress, etc., from within the App.

Thanks guys for the "heads up." However, I am extremely familiar with php, apache, and hosts.
I guess my suggestion deserves more explanation.
If iWeb contained a "Tables" and "Fields" manager, something similar to Navicat's MySQL tool, within its code base, then iWeb could allow a CMS or CRM to be built right within the app that doesn't require 3rd party involvement. It would also spark some great "security" opportunities for webmasters using iWeb.
It would allow a user to build a user table, giving the designer more flexibility in "who can see what" on the iWeb site. It would certainly up the viability of iWeb's use by Mac Users because it would better support "automated dynamic content." By iWeb having the ability to connect directly with MySQL (which comes with OS X), iWeb could become the Mac users choice for simple CMS and CRM website development / prototyping.
I especially dislike the proprietary nature of iWeb's abilities, in that, I have to pay for an Apple Hosting account that is far too limited on features and offerings for its cost. iWeb needs work, and I think experienced webmaster input is important for Apple to better satisfy the needs / desires of its consumers.
Maybe that clarifies what I meant by this post a little better?
Walt.
Message was edited by: Soundman5

Is It A Mistake To 'Bet' On iWeb

Similar Messages

Maybe you are looking for