Anyone still using iWeb having issues with El Capitan?

Hi Petermac - thanks for you note. But I have glitch on text box not showing if Hyperlink is added. Any thoughts or solution on that ; ). Best.

Sorry, can't help you out there. All working fine at my end

Pete

This is a known issues with hyperlinks and text boxes and there have been lots of posts about this on the forum, so do a search of this forum to find answers.

I think you have to import shapes instead and then they show up.

There have been lots of posts on this very issues over the past few months so either do a search or have a look back over some old posts and see.

Ah! This explains why my uploaded update had missing bits! I was able to use TimeMachine to go back to an earlier version of the site, FYI. So now it sounds like I just need to get rid of shapes that have hyperlinks and or odd fonts and treatments....

Thanks, folks!! Just can't find a chunk of time big enough to make the switch to EverWeb or whatever right now..

I have the same problems but i have made a solution.

1. I bought a 200 Gb USB drive

2. I installed OS Mountain Lion on it (http://getintopc.com/softwares/operating-systems/mac-os-x-mountain-lion-free-dow nload/) AND I've copied iWeb from the internal Macintosh HDD to this External disk also

3. When I start my iMac (mid 2010), I push the Alt button, when the chimes comes.

4. After a few seconds there will by a booting menu

5. I choose OS Mountain Lion on the external disk

6. Then I copy the iWeb Domain file (domain.sites2) from the internal Macintosh HDD to this External disk

7. Then I start iWeb and now I can edit and upload in the old fashion way.

When i have to make changes in my websites i do it under OS X El Capitain.

When I finish editting I reboot with the external disk and copy the iweb domain.sites2 files from the Macintosh HD to the external HDD, upload my website and thats it.

Works fine.

Yes it does, because it support HTML widget you can integrate PHP with HTML to make a fully functional iWeb Template with PHP. This basically allow you to have a whole set of feature of a WYSIWYG template editor that interacts with your PHP pages. I have several sites which use iWeb template and has PHP via the HTML. There are no need for any widget add ons or the need to edit any of the existing iWeb files or the publish iWeb template file.

And has been awhile there is one thing at time you can also do by editing the the published templates js file to add other features. Normally that js only has to be edited once, but if you republish the site that effects the js you have to reset that edit. Been awhile, so I don't recall which js that was and would have to look it up

I also have problems with IWeb and El Capitan I have never had before.

For example, IWeb numbers a list whereas it should be unnumbered.

It's sad.

C.V.

I had to change the font, choosing among the Web collection. I think it's the best solution or, at least, a good compromise

If you are creating a list, then you should have 2 options, one for an ordered list (numbered) and one for an unordered list (without numbers) - are you sure you chose the correct one?

Also, you say that this is sad - why? You are continuing to use an unsupported product after all, so this should come as no great surprise to you!

Count me among the many still hanging onto iWeb - mostly because I have too many good pages created with it - and because each time I go searching for replacements, I end up frustrated and with no really good alternative. I'm afraid "get over it ! 😠 " simply doesn't do it for me.

Now - here is the clunky workaround that works for me. From the very first page I created in iWeb years ago, I have always "published" to a folder on my computer and uploaded with an FTP app (Transmit for the past 4 or 5 years...) When I first started running onto certain text elements that refused to update in the published files, even though the changes appear fine in iWeb, I started playing around on the publishing side. Since I could see the "failed to update" pages when I used a browser to open the file on the computer, it was clear that I wasn't dealing with a server issue. I tried "Publish Full Site" instead of "Publish Changes", but that was no help. But - guess what DID work?? Instead of publishing to the default folder that normally held all the HTML pages, I created a New Folder(in the same directory) and did a "publish Full" to that folder. VOILA! -all the changes appeared fine and I could upload the revised pages to my internet server - and all is OK!

Clearly, this is still a PITA compared to the way that iWeb used to work so efficiently and quickly for me, but for now I am hanging with the iWeb faithful 👿