Switch from iWeb to WordPress?

          A week ago I asked about alternatives to iWeb for blogging on this forum.
One suggestion received from Roddy was to consider software created by
RageSW called iWeb to WordPress.
I did explore this and chose to try it.
Specifically, I paid $120 for one year's webhosting services.
This included provision of a domain and installation of WordPress
at my new website.
          My reaction so far is mixed for the following reasons:
1. My current weblog, a health-related blog, consists of a welcome page,
which is fixed, and four pages on which I place posts to diverse audiences
every few months as appropriate to the on-going health story.
2. In WordPress terms, these four pages are considered four separate blogs.
3. When iWebtoWrdPrs is used on the files published to a local folder, they
must be broken into four separate blogs. The result was that all 28 posts
from my four pages wound up in one WrdPrs blog.
4. To separate these back into "four groups", I chose the names of my iWeb
pages to create four WordPress "categories", which can be displayed in the
blog page sidebar. Then, I assigned each post to its related category.
I consider this marginally satisfactory and certainly neither elegant, nor
user-friendly.
5. The navigation menu at the top of the page looks like the one iWeb
produces, but it accommodates several fixed pages and one blog page
with all the posts. This seems to make sense for commercial entities;
for me it seems clumsy and rigid.
6. To use the software one must be using iWeb3.0.x.
7. On the plus side, the staff at RageSW have been very responsive and
helpful.
          In the short term I will continue using iWeb; my MobileMe subscription
runs thru next June. RageSW also offers hosting for iWeb publishing if you
want to experiment with your own domain. There are many tutorials on
WordPress available on-line and a good support community. Maybe I'll find
a satisfactory way to implement my blog in WordPress down the road.

Yes, if you have purchased both a domain name and hosting, then it is your server - so I have a domain name registered with hosting space from HostExcellence and that is my server space.
WordPress.org can only be loaded onto a server/hosting space as it is seen as one of the Content Management Systems's similar to Joomla and Drupal. For this you need server space and a database and most hosting companies have automatic loading of something like WordPress.org onto the sever - you just click on install and it will all be loaded onto the server for you along with the database needed.
The difference between the WordPress.org is that as it is installed directly on your server, then it is linked directly to your own domain name so the url will be http://www.domain.com/Blog or http://www.domain.com/WordPress. The last name depends on how you choose to install it on your sever. I have 2 blogs using WordPress.org on my server and the domain names for both are http://www.domain.com/Blog.
With my other host, I wanted to create the whole website using WordPress, so I installed WordPress directly onto the server, so now, when you enter my domain name direclty the whole WordPress site comes up.
WordPress.org has more templates available for it and you can customise it a little more, but the great thing is that it is installed on your server directly, so no messing around with the url http://www.name.wordpress.com. It is on your own server rather than that of WordPress.

Similar Messages

How do I move my blog posts from iWeb to Wordpress?

I want to move all my blog posts from iWeb to Wordpress. Is that possible and how?

Depending on how many posts you have, it may be best to copy and paste them into Wordpress. I don't know for sure, but I dought if there is any process that will do that automatically for you. I would have your iWeb blog (edit Mode) window open and then Create a new blog in Wordpress. Copy the iWeb title/paste into Wordpress - Copy the iWeb blog text/paste into Wordpress. It should go fast once you get the first one done because you'll do the same for all. Hope that helps.

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

Export from iweb to Wordpress

Hi
I've been running a blog via iWeb, but I've been advised to move it to something more SEO-able, and to allow log in from anywhere - Wordpress in fact.
There are quite a few entries in my blog, is there any way of exporting everything from iweb so I can import into Wordpress directly? I'd like to put all the old entries up without having to copy and paste every one.
Thanks
Nigel

Yes, if you have purchased both a domain name and hosting, then it is your server - so I have a domain name registered with hosting space from HostExcellence and that is my server space.
WordPress.org can only be loaded onto a server/hosting space as it is seen as one of the Content Management Systems's similar to Joomla and Drupal. For this you need server space and a database and most hosting companies have automatic loading of something like WordPress.org onto the sever - you just click on install and it will all be loaded onto the server for you along with the database needed.
The difference between the WordPress.org is that as it is installed directly on your server, then it is linked directly to your own domain name so the url will be http://www.domain.com/Blog or http://www.domain.com/WordPress. The last name depends on how you choose to install it on your sever. I have 2 blogs using WordPress.org on my server and the domain names for both are http://www.domain.com/Blog.
With my other host, I wanted to create the whole website using WordPress, so I installed WordPress directly onto the server, so now, when you enter my domain name direclty the whole WordPress site comes up.
WordPress.org has more templates available for it and you can customise it a little more, but the great thing is that it is installed on your server directly, so no messing around with the url http://www.name.wordpress.com. It is on your own server rather than that of WordPress.

How to publish from iWeb to Wordpress

I want to take the advantage of those beautiful design sofware to create an amazing blog for my wordpress account. But I run into problem of not know how to do it and I do not want to live in the restriction of wordpress has for me on the web design.

There's no know method to conver an iWeb blog, design wise, to a wordpress blog. Rage software, however, has offered an application that can export the entries and comments of a current iWeb blog for use in an wordpress blog. Convert Your iWeb Blog to a WordPress Blog | iWeb to WordPress for Mac OS X But the design and layout must be created by wordpress.
OT

I have iWeb '08 and just switched from Mobileme to GoDaddy and using Filezilla. Now when I make changes through iWeb it doesn't actually publish to my desktop folder. In fact, it doesn't publish at all but says that it did.

I have iWeb '08 and just switched from Mobileme to GoDaddy and using Filezilla. I also just upgraded to Lion. Now when I make changes through iWeb it doesn't actually publish to my desktop folder. In fact, it doesn't publish at all but says that it did. How can I make changes in iWeb and publish to a folder?

Choose the destination in the publish settings page as shown in the second example on this page...
http://www.iwebformusicians.com/iWeb/Publish-Website.html

IWeb help needed in switch from MobileMe to iCloud

I recently switched from Snow Leopard and Mobile Me to Lion and iCloud. In doing so, I seem to have "lost" iDisk, which is where I stored my public, downloadable files from my iWeb site.
I found iDisk, but it is not listed in iWeb as a destination source. Where do I now post public files? Thanks in advance for any help.

Singing up for iCloud automatically logged you out of MMe. Just go to the System/MMe preference pane and log back into MMe. iWeb will then be able to communicate with the iDisk server again.
OT

I have been using DREAMWEAVER MX for almost ten years to keep a website up-to-date. Can I switch to iWeb now to do the job, and if so, how do I go about it?

With MacOS 10.7 looming on the horizon, using veteran software DREAMWEAVER MX any longer does not seem to be such a good idea. I would like to use an editor that can cope with the new MacOS. Is iWeb that editor?
Specifically, I need some clarity on these issues:
Can I switch to iWeb now to create and publish content in my old website for which I have been using DREAMWEAVER MX?
Can I use the html layout I have been using in DREAMWEAVER, or do I have to steel myself for drastic changes?
How do I import the complete website into iWeb – if at all?

If you switch to iWeb you will have to build the site from scratch since iWeb can't read or import html files. Also since the future of iWeb is a little uncertain as to if it will be continued to be supported by Apple it might not be the best move at this time.
You might look into upgrading to Dreamweaver for Mac.
OT

Can I publish to blogger from iWeb?

I want to publish from iWeb but I don't want to pay for a website, and I'm only going to blog for a couple of months while I am on vacation. Any Thoughts?

No you can't.
Blogger is Google's blog and it is free, so sign into Google and you can create a blog for free directly there.
Your other alternative is to use http://www.wordpress.com. This is also a free blogging service and if you are on vacation, you will be able to update it from any terminal you can get to - a PC or a Mac and you can do this online. Once you don't need the blog anymore you can delete it from the WordPress servers and that's it. You don't need to pay for a website.
Don't use the iWeb blog as it is too restrictive to use whilst travelling - just use either Google's blogger or WordPress.com at source, with both being free.

Text format change from iWeb to browser

Has anyone else had a problem with their text looking different (in both Safari and Firefox)? In one place, the font switches from 14 to 12. On another page, my indentations don't line up. Overall, I'm pleased with the software, but it is irritating that my website doesn't look as clean as it does in iWeb. Thanks.
--Patrick

Yes, and it can be much worse looking at a page from a Windows browser. I'm currently struggling with "white space" at the bottom of the text box on the blog page. The amount of space is very noticeable, especially if the background of your text box differs from the page background. In this case it has to do, I believe, with font settings, type, size, justification, and line spacing, even inserting pictures into the text box.
Unfortunately, there isn't much that can be done. Every browser renders pages differently. It is rather appalling that the iWeb team can't even get their WYSIWYG to match what is seen in Safari, but what can you do? You can either keep things simple or design for a particular browser audience. Something like 85 perent of people use Internet Explorer for Windows, so I tend to think that's the best solution, if an unappealing one.

Iweb created, wordpress embedded.

Hello,
My ideal situation would be to create a website in iweb, have a domain, host and website with Wordpress (software) pages, and transfer or embed my iweb website to wordpress(.org). Is this possible?
I'm not talking about blogs (I know Wordpress is for blogs), I'm talking about website pages, layout and creation.
Obviously I'm trying to use the best part of both iweb and wordpress. iweb is extremely easy to use to create websites (especially coming from DVD Studio/Motion) and I love Wordpress' free plugins, navigation and setup.
If what I'm asking is not possible, what would be a similar solution? Dreamweaver and Wordpress? iWeb straight to the server (and alternate Wordpress-type plugins)? Another program?
I'm trying to create a few websites, but when it comes to designing I enjoy the free range of experimenting visually with text, color, layouts, etc that iweb and Dreamweaver offers over trial and error of html, css, and php.
THANK YOU in advance!

I am not sure if you can do this and it all depends how much you are able to alter the WordPress html code or insert code into WordPress?
Are you using WordPress.com or .org? .org is more customisable than the .com version, but if you were to try and embed an iWeb site into WordPress, it would mean adding iFrame code to the html and I am not so sure that WordPress will allow you to do this in the same way that iWeb will - with iWeb it is simple - you just enter the iFrame code into an html widget and away you go.
If you know how to alter the code and add it in WordPress then great, but if not, I would do it the other way around and embed your WordPress blog into an iWeb site - by far the simpler option.

IWeb and Wordpress

Can I upload my html that I made in iweb to wordpress? i know you can get access to wordpress through FTP, but i cant figure out my FTP adreess in iweb. Any help? what would my FTP Address be?

iWeb/MobileMe does not have an ftp address. When you publish to MobileMe, your site will be published directly there to your iDisk, so no ftp address.
Basically, to get an ftp address, you need to go to a server such as GoDaddy or Host Excellence and purchase a hosting account from them where you can host your website and then you will get an ftp address where you can use Cyberduck or another ftp program to upload your site directly.
Do you have such as hosting account with GoDaddy or another host? To get an ftp address you will need to get one.
Are you totally sure that you really know what you are doing with WordPress? I do not know a lot about it, but from what I have read, you need to load WordPress directly to an external host - so you use ftp to place it on your host - hence where the ftp address comes in - so GoDaddy/Host Excellence.
If WordPress has the ability to deal with html code and can import published sites such as Dreamweaver can, then if you publish your iWeb site to a folder, then yes, it should be able to import.
You do need to get an external host though, as Apple servers/MME are not designed to deal with things like WordPress.

Cannot publish from iWeb 08 after upgrading to Leopard

When I click on Publish from iWeb I first get a window .Mac Information asking me to login and a smaller window saying "logging in to iWeb". I click on sign in button from .Mac Information window and then get the System Preferences window telling me I am signed in and giving me my account status. From here nothing happens. The "logging into iWeb" message stays and nothing happens.
What should I do?

Thanks and Merry Christmas to you too! I have experienced both modem/network problems and was unable to publish in Tahiti and Cook Islands because of that and now these problems which have nothing to do with network it seems - so yours may or may not be network related. I was able to cheat and copied my "Site" folder from my hard drive to my iDisk rather then publishing. I can't remember if you've tried this or not (read a lot of strings today) but you can publish to a folder and then copy that folder to your iDisk at /Web/Sites/iWeb/Site as "Site" after first renaming the one that is out there now. Let me know if you have any questions on how to do it. It sounds like you are traveling like we are and anxious to communicate with friends and family back home. When you are bored, our site is web.mac.com/baganworldtour.
At least we now have our first update out there in two weeks. But it took almost two hours to copy the folder and this won't work forever. Hopefully we, whether by the discussion room or .mac support next week, will be able to fix the problem for real.
Thanks. Good Luck. Merry Christmas

I am switching from a pc to mac and want to know how I go about transferring files from one to the other. There is a chance that I will have to hand my pc back before I receive my MacBook so I will need to transfer on to some sort of external hard drive.

I am switching from an acer laptop to a MacBook Pro. I may have to hand in my laptop before I receive my new MacBook. What is the best way to back up my files so that I can transfer them to my MacBook. I cloud cannot be installed on my laptop because it uses a version of windows that is older and doesn't support it. Hope someone can help.

Connect a blank powered external drive to the PC.
Right click on the Disk in the File manager and choose format: exFAT
(if it's a XP machine, first install exFAT from Microsoft and reboot)
navigate to your user account folders on the PC and drag and drop copy (or copy and paste) to the external drive.
(if a program has your files, then export them out first)
Hook up the drive to the Mac, and transfer files to the desktop or to their same appropritate folders.
Import photo's into iPhoto program, import music into iTunes etc and they will manage those files.
You can continue to use the external exFAT drive between Mac's and PC's
Do not format the drive NTFS or FAT, NTFS can't be written too by the Mac and FAT can't hold over 4GB sized files.
If you format exFAT on the Mac, it likely won't work correctly on the PC.
"Migration" type programs are a utter waste of time and effort between PC's and Mac's for the fact that only certain files (and no programs or anything else) will work between them, also it's a hassle and takes too long. So don't even bother with it.

I switched from an iPhone to a Droid and can't receive texts from iPhones now, help?

I switched from my iPhone 4s to a Droid and I do not have that phone anymore. I can not recieve texts from anyone with an iPhone and can not get in contact with my girlfriend or siblings now. I think their phones are trying to send their texts as iMessages to my phone that does not recieve iMessages. How can I just delete my Apple account and recieve texts again?

Sounds like you didn't turn of iMessage on your iPhone before making the switch. If you registered your iPhone with Apple using a support profile, try going to https://supportprofile.apple.com/MySupportProfile.do and unregistering it. Also, try changing the password associated with the Apple ID that you were using for iMessage.

Switch from iWeb to WordPress?

Similar Messages

Maybe you are looking for