Re: Fix duplicate divs caused by old Adobe GoLive bug?

Hello Greg, I too was a little concerned that Rich and Patrick might think I was getting a little too far off-topic. :) At any rate, it seems that I may have been worrying about nothing. You see, a while back I installed Automatic’s “AMP” plugin, but then I forgot about it. I just researched

Re: Fix duplicate divs caused by old Adobe GoLive bug?

Bill, Rather than continue to hijack the topic, I’m responding privately. The easy way is to install JetPack (which you should be using anyway), and then avail yourself of the “custom CSS” capability. Then you can define and use custom classes, and apply these via divs or spans. I don’t know,

Re: Fix duplicate divs caused by old Adobe GoLive bug?

Greg, I am glad you brought up that point regarding WordPresss, because this is something I have been wondering about since last night. As you already know, AMP specifications outright prohibit certain standard HTML tags -- such as the font tag — and inline styling in HTML document bodies.

Re: Fix duplicate divs caused by old Adobe GoLive bug?

What I mean is that if your pages are generated by WordPress (for example), then it's marginally easier to insert all the special AMP coding. When the pages are generated programmatically, then each page should be pretty much the same for any given template, so you can sample-validate a few

Re: Fix duplicate divs caused by old Adobe GoLive bug?

On Feb 22, 2017, at 1:58 AM, Fletcher Sandbeck wrote: > The trick is to figure out what the problems are and then apply those fixes > to all your pages using BBEdit's multi-file search/replace. However, finding > the errors is easier than fixing them. Exactly. I have

Re: Fix duplicate divs caused by old Adobe GoLive bug?

> On Feb 22, 2017, at 1:40 AM, Fletcher Sandbeck wrote: > > I've worked on converting some large sites to AMP and it has been good for > the HTML quality on the sites. My sites are generally dynamic, but contain > user submitted articles and comments so it's been a two

Re: Fix duplicate divs caused by old Adobe GoLive bug?

On Feb 22, 2017, at 1:00 AM, Greg Raven wrote: > AMP seems better suited to programmatically-generated web pages, not manually > maintained static pages. The main problem I have with AMP for static pages is > that there is no way to validate AMP code ... each page will

Re: Fix duplicate divs caused by old Adobe GoLive bug?

The trick is to figure out what the problems are and then apply those fixes to all your pages using BBEdit's multi-file search/replace. However, finding the errors is easier than fixing them. This pattern "\s*

Re: Fix duplicate divs caused by old Adobe GoLive bug?

I've worked on converting some large sites to AMP and it has been good for the HTML quality on the sites. My sites are generally dynamic, but contain user submitted articles and comments so it's been a two step process. Ensuring that the template and navigation of the site is AMP-friendly. And

Re: Fix duplicate divs caused by old Adobe GoLive bug?

AMP seems better suited to programmatically-generated web pages, not manually maintained static pages. The main problem I have with AMP for static pages is that there is no way to validate AMP code ... each page will generate a bunch of errors due to AMP's non-standard HTML. Some of my static

Re: Fix duplicate divs caused by old Adobe GoLive bug?

If the only issue standing between you and a simple search-and-replace is the varying spaces from page to page, create a TextFactory that Optimizes your entire site (HTML pages, that is), and then perform the search-and-replace. Afterward, you can use a TextFactory to Format each of your HTML

Re: How do I change the "Currently Open Documents" sort order?

To avoid other people's frustration, who found this thread and wonder why it just doesn't work: the correct user default command that works for current TextWrangler (version 5.5.2 (397016), Mac App Store build) is: defaults write com.barebones.textwrangler SurfNextPreviousInDisplayOrder -bool

Re: Fix duplicate divs caused by old Adobe GoLive bug?

One way to avoid a lot of the clutter is by converting your website over to the AMP — Accelerate Mobile Pages — standard, which is what I recently did with my primary website. It was a lot of work — and very challenging and frustrating at times due to my own lack of knowledge — but I believe

Re: Fix duplicate divs caused by old Adobe GoLive bug?

That is a problem with all WYSIWYG editors. If you don't get it right first time, you get silly situations like those nested tags and nested divs. There are two ways to tackle this. Manually: using BBEdit's syntax checker to find errors in the markup and fixing them individually.