Cocking TypePad
As I've ranted about in the past, I find TypePad excruciatingly painful. For a variety of reasons, we use it for our blogs at work (which eventually launched over a year since we first started work on them). A couple of us are now quite familiar with them - me most of all (largely because I refuse to give in, and try to hunt down bugs), and M* is also pretty handy with them (after a slightly shaky start, where he caused me much pain).
Last week, TypePad announced - with about three days' notice - that they wanted you to make some changes to your blog, for their new "next generation" platform. This basically means that very long posts can be paginated, and comment feeds can be split across multiple pages. Since we make extensive use of Advanced Templates, we have to make a number of these changes ourselves.
By and large, the changes are mostly sensible and fairly easy to apply. "But," you say, "can I check to see if I've accidentally broken my layout by applying this?" The happy answer to this is yes. You can set a cookie via a 'hidden' page, and it will pretend the new system is in operation, and all is good. Right?
Wrong.
Unfortunately, TypePad have broken a number of things between the old platform and the preview (and, therefore, possibly the new platform?) in non-obvious ways. Most of these are down to bad stuff in our code to start with, but the old system didn't break and the preview does.
For example, in our code we have a number of sections where we #include some other code. This was the best I could do in very short amount of time to get the look and feel of our existing site. There may be better ways of doing this if you have time or more familiarity with TypePad, but it worked. Okay:
for your troubles.
As you might imagine, not knowing what was going on has caused me some annoyance.
Last week, TypePad announced - with about three days' notice - that they wanted you to make some changes to your blog, for their new "next generation" platform. This basically means that very long posts can be paginated, and comment feeds can be split across multiple pages. Since we make extensive use of Advanced Templates, we have to make a number of these changes ourselves.
By and large, the changes are mostly sensible and fairly easy to apply. "But," you say, "can I check to see if I've accidentally broken my layout by applying this?" The happy answer to this is yes. You can set a cookie via a 'hidden' page, and it will pretend the new system is in operation, and all is good. Right?
Wrong.
Unfortunately, TypePad have broken a number of things between the old platform and the preview (and, therefore, possibly the new platform?) in non-obvious ways. Most of these are down to bad stuff in our code to start with, but the old system didn't break and the preview does.
For example, in our code we have a number of sections where we #include some other code. This was the best I could do in very short amount of time to get the look and feel of our existing site. There may be better ways of doing this if you have time or more familiarity with TypePad, but it worked. Okay:
for your troubles.
As you might imagine, not knowing what was going on has caused me some annoyance.