Comments on: TypePad has no pagination features (next and previous buttons at the bottom of the page) AND no way of implementing them!! http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm Blogging tips and tricks, theme and plugin info, blogging software reviews, and more Tue, 07 Feb 2012 07:27:12 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Michael Schaffner http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-48794 Michael Schaffner Sun, 07 Jan 2007 22:01:48 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-48794 It looks like they are STILL working on it. Here is the response I just received from my question Jan, 7 2007. "At this time, TypePad does not support pagination, or the addition of Next/Previous links on your index pages. We are currently working on adding this feature to TypePad in the future as it is one of the most requested features." It looks like they are STILL working on it. Here is the response I just received from my question Jan, 7 2007.
“At this time, TypePad does not support pagination, or the addition of Next/Previous links on your index pages. We are currently working on adding this feature to TypePad in the future as it is one of the most requested features.”

]]> By: Max Watson http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-4658 Max Watson Thu, 08 Jun 2006 02:46:03 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-4658 WTF? I just thought I'd do a Google search to see how to add this to my blog--and it's not even a possibility? Lame. I'm really tempted to convert to WordPress now. WTF? I just thought I’d do a Google search to see how to add this to my blog–and it’s not even a possibility? Lame. I’m really tempted to convert to WordPress now.

]]> By: Kareem http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-1663 Kareem Tue, 21 Mar 2006 03:12:03 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-1663 I have to agree with this post... I've just spent a few minutes googling for a way to put in "Previous" and "Next" links on pages and am *STUNNED* that typepad does not offer this. This is basic UI 101 for blogs. It is hard for me to imagine that typepad has been around for as long as it has and that they have not recieved enough complaints to figure this out. Can it be so hard (especially if MT plug-ins exist for the same functionality)? I have to agree with this post… I’ve just spent a few minutes googling for a way to put in “Previous” and “Next” links on pages and am *STUNNED* that typepad does not offer this. This is basic UI 101 for blogs. It is hard for me to imagine that typepad has been around for as long as it has and that they have not recieved enough complaints to figure this out. Can it be so hard (especially if MT plug-ins exist for the same functionality)?

]]> By: Disreputable http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-1406 Disreputable Sun, 15 Jan 2006 21:13:24 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-1406 Hey! Textpattern has that! I have tried just about all the Blogging and CMS platforms in the past couple of years including MT, Wordpress, Nucleus, Serendipity, B2Evo, Drupal, Boastmachine, Blogger and Expression Engine.. I (think) I have settled on Textpattern. It is SOOO adaptable to whatever you NEED it to do. I still maintain a Nucleus Blog but only because it would be such a PITA to change it over to TXP. I Love what you are doing and look forward to your future posts and opinion. Hey! Textpattern has that!

I have tried just about all the Blogging and CMS platforms in the past couple of years including MT, WordPress, Nucleus, Serendipity, B2Evo, Drupal, Boastmachine, Blogger and Expression Engine.. I (think) I have settled on Textpattern. It is SOOO adaptable to whatever you NEED it to do. I still maintain a Nucleus Blog but only because it would be such a PITA to change it over to TXP.

I Love what you are doing and look forward to your future posts and opinion.

]]> By: Su http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-1405 Su Thu, 12 Jan 2006 11:04:01 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-1405 The ultimate point here is that you seem to be getting riled up over not receiving something that was never offered. Again, please point to whatever makes or made you think pagination was available in TypePad. Otherwise, you are in effect blaming them for your own incomplete feature review when choosing to use the product, and are fully entitled to cancel your account if it's that important to you. Xanga and Wordpress.com offer paging. I'm pretty sure Blogger does not. While you might reasonably make a post pointing out the missing feature and inquiring why, it does not call for multiple exclamation points. They didn't offer you a free pony, either. Might sound callous, but it's also the facts as I see them. You're the customer, and you want a feature; I understand that. I'm approaching this from the standpoint of someone who's maintained a /very/ large Movable Type installation(13+ sites rapidly approaching 100k entries, etc.) and been at least partially accountable for what it did to the server it was installed on. And my situation doesn't even begin to approach what 6A have to deal with. You do NOT just add a feature because it's a good idea(which it is) or somebody wants it. In fact, you actively try to simplify things, so there are fewer pieces to potentially fail, and fewer to dig through when something inevitably does. I don't doubt that there was a meeting where the question came up as to whether to offer paging through TypePad. Maybe they decided it might not be that important to their target audience. Maybe that was wrong. And maybe you're now finding yourself on the outside edge of what they consider to be their target. Do understand that I'm not disagreeing with you wanting this. I'm just not so sure your refusal to accept the absence is on a proper basis. Re: your point in referencing, it's still incorrect. The article acknowledged the importance of pagination within the blogging *application.* It said precisely nothing about its importance as regards the output, which is what you're complaining about. Yes, they do have full control of the TypePad servers. While that removes one problem, it's one of the smallest aspects of the matter. I've already given you one speculation above as to why they may not offer paging (yet?); there are loads of other possibilities, and the final answer probably involves several of them. One more is that dynamic content(ie: pagination via PHP) eats more server resources than static content. Those recent service problems they've been having? Probably would've happened much sooner and much more violently if they were offering dynamic functions. For the definitive reason, however, you'll have to ask their support department. The ultimate point here is that you seem to be getting riled up over not receiving something that was never offered. Again, please point to whatever makes or made you think pagination was available in TypePad. Otherwise, you are in effect blaming them for your own incomplete feature review when choosing to use the product, and are fully entitled to cancel your account if it’s that important to you. Xanga and WordPress.com offer paging. I’m pretty sure Blogger does not.
While you might reasonably make a post pointing out the missing feature and inquiring why, it does not call for multiple exclamation points. They didn’t offer you a free pony, either. Might sound callous, but it’s also the facts as I see them.
You’re the customer, and you want a feature; I understand that. I’m approaching this from the standpoint of someone who’s maintained a /very/ large Movable Type installation(13+ sites rapidly approaching 100k entries, etc.) and been at least partially accountable for what it did to the server it was installed on. And my situation doesn’t even begin to approach what 6A have to deal with. You do NOT just add a feature because it’s a good idea(which it is) or somebody wants it. In fact, you actively try to simplify things, so there are fewer pieces to potentially fail, and fewer to dig through when something inevitably does. I don’t doubt that there was a meeting where the question came up as to whether to offer paging through TypePad. Maybe they decided it might not be that important to their target audience. Maybe that was wrong. And maybe you’re now finding yourself on the outside edge of what they consider to be their target.

Do understand that I’m not disagreeing with you wanting this. I’m just not so sure your refusal to accept the absence is on a proper basis.

Re: your point in referencing, it’s still incorrect. The article acknowledged the importance of pagination within the blogging *application.* It said precisely nothing about its importance as regards the output, which is what you’re complaining about.

Yes, they do have full control of the TypePad servers. While that removes one problem, it’s one of the smallest aspects of the matter. I’ve already given you one speculation above as to why they may not offer paging (yet?); there are loads of other possibilities, and the final answer probably involves several of them. One more is that dynamic content(ie: pagination via PHP) eats more server resources than static content. Those recent service problems they’ve been having? Probably would’ve happened much sooner and much more violently if they were offering dynamic functions. For the definitive reason, however, you’ll have to ask their support department.

]]> By: Emily from How to Blog http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-1404 Emily from How to Blog Wed, 11 Jan 2006 15:31:09 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-1404 @Su: I did mention that the article pertains to Movable Type, which is of course made by the same folk as those who run TypePad. My only point in referencing the article was to point out that the Six Apart team acknoledges the huge importance (and widespread expectation) of pagination in a blogging tool. I stand corrected in that it is not actually built into MT, but rather requires the Paginate plugin or similar. However, you wrote, "they have no idea what your server environment is going to be, much less what you choose to develop on the server with. If they released a plugin for say, PHP, everybody will start whining about bringing enough for the rest of the class, and complain for them to develop versions for whatever their favorite scripting language or templating system is.", and I'm assuming that you're talking about why it isn't built into MT, but that provides no reasoning whatsoever as to why it isn't built into TypePad. TypePad runs exclusively on 6A's servers, and as such they control the hosting environment in it's entirety. They can surely install PHP so that they can incorporate the pagination plugin (or some derivative of it) into the TypePad code base. Since you mentioned that the pagination code has nothing to do with the templating system at all, but rather is part of the application and/or it's plugins, then it shouldn't matter what template folks are using if 6A implemented pagination in TypePad. It's a very basic MUCH needed feature and certainly not too much to ask for in a blogging platform. I still find it ridiculous that there is currently no way to utilize pagination within TypePad. @Su:

I did mention that the article pertains to Movable Type, which is of course made by the same folk as those who run TypePad. My only point in referencing the article was to point out that the Six Apart team acknoledges the huge importance (and widespread expectation) of pagination in a blogging tool.

I stand corrected in that it is not actually built into MT, but rather requires the Paginate plugin or similar.

However, you wrote, “they have no idea what your server environment is going to be, much less what you choose to develop on the server with. If they released a plugin for say, PHP, everybody will start whining about bringing enough for the rest of the class, and complain for them to develop versions for whatever their favorite scripting language or templating system is.”, and I’m assuming that you’re talking about why it isn’t built into MT, but that provides no reasoning whatsoever as to why it isn’t built into TypePad.

TypePad runs exclusively on 6A’s servers, and as such they control the hosting environment in it’s entirety. They can surely install PHP so that they can incorporate the pagination plugin (or some derivative of it) into the TypePad code base.

Since you mentioned that the pagination code has nothing to do with the templating system at all, but rather is part of the application and/or it’s plugins, then it shouldn’t matter what template folks are using if 6A implemented pagination in TypePad.

It’s a very basic MUCH needed feature and certainly not too much to ask for in a blogging platform. I still find it ridiculous that there is currently no way to utilize pagination within TypePad.

]]> By: Emily from How to BlogEMAIL: howtoblog@gmail.com http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-2241 Emily from How to BlogEMAIL: howtoblog@gmail.com Wed, 11 Jan 2006 15:31:09 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-2241 @Su: I did mention that the article pertains to Movable Type, which is of course made by the same folk as those who run TypePad. My only point in referencing the article was to point out that the Six Apart team acknoledges the huge importance (and widespread expectation) of pagination in a blogging tool. I stand corrected in that it is not actually built into MT, but rather requires the Paginate plugin or similar. However, you wrote, "they have no idea what your server environment is going to be, much less what you choose to develop on the server with. If they released a plugin for say, PHP, everybody will start whining about bringing enough for the rest of the class, and complain for them to develop versions for whatever their favorite scripting language or templating system is.", and I'm assuming that you're talking about why it isn't built into MT, but that provides no reasoning whatsoever as to why it isn't built into TypePad. TypePad runs exclusively on 6A's servers, and as such they control the hosting environment in it's entirety. They can surely install PHP so that they can incorporate the pagination plugin (or some derivative of it) into the TypePad code base. Since you mentioned that the pagination code has nothing to do with the templating system at all, but rather is part of the application and/or it's plugins, then it shouldn't matter what template folks are using if 6A implemented pagination in TypePad. It's a very basic MUCH needed feature and certainly not too much to ask for in a blogging platform. I still find it ridiculous that there is currently no way to utilize pagination within TypePad. @Su:

I did mention that the article pertains to Movable Type, which is of course made by the same folk as those who run TypePad. My only point in referencing the article was to point out that the Six Apart team acknoledges the huge importance (and widespread expectation) of pagination in a blogging tool.

I stand corrected in that it is not actually built into MT, but rather requires the Paginate plugin or similar.

However, you wrote, “they have no idea what your server environment is going to be, much less what you choose to develop on the server with. If they released a plugin for say, PHP, everybody will start whining about bringing enough for the rest of the class, and complain for them to develop versions for whatever their favorite scripting language or templating system is.”, and I’m assuming that you’re talking about why it isn’t built into MT, but that provides no reasoning whatsoever as to why it isn’t built into TypePad.

TypePad runs exclusively on 6A’s servers, and as such they control the hosting environment in it’s entirety. They can surely install PHP so that they can incorporate the pagination plugin (or some derivative of it) into the TypePad code base.

Since you mentioned that the pagination code has nothing to do with the templating system at all, but rather is part of the application and/or it’s plugins, then it shouldn’t matter what template folks are using if 6A implemented pagination in TypePad.

It’s a very basic MUCH needed feature and certainly not too much to ask for in a blogging platform. I still find it ridiculous that there is currently no way to utilize pagination within TypePad.

]]> By: Su http://www.emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm/comment-page-1#comment-1403 Su Wed, 11 Jan 2006 05:36:36 +0000 http://emilyrobbins.com/how-to-blog/typepad-has-no-pagination-features-next-and-previous-buttons-at-the-bottom-of-the-page-and-no-way-of-implementing-them-316.htm#comment-1403 Be careful what you use as back up. * TypePad is not Movable Type. * The ProNet articleyou linked--which, if you check the title, is about MT--regards a pagination control for use within the Movable Type /application/, not the output templates you're concerned with. That piece is about developing plugins, not sites. * Not that it entirely matters, because MT does /not/ provide template pagination, either. Check the manual. There /is/ the Paginate plugin, which requires PHP, but I challenge you to find a decent host that doesn't offer it. Beyond plugins, there is another way to do it with Smarty(also PHP), and ultimately with any other templating engine you may want to use. * My guess would be that 6A simply didn't want to get into it. There are a lot of potential reasons for this, starting with the fact they have no idea what your server environment is going to be, much less what you choose to develop on the server with. If they released a plugin for say, PHP, everybody will start whining about bringing enough for the rest of the class, and complain for them to develop versions for whatever their favorite scripting language or templating system is. This would be a colossal waste of time, so they let the third-party developers deal with it for plugins, or individual users to come up with their own solutions. (I had links in here, but HTML is completely disallowed?) On to TypePad, it has never been sold as a full-featured "control everything" product(that's MT). Quite the opposite, and I'm guessing Comet is going to be even further removed from the system, to be more like MSN Spaces, for example. While I'm not suggesting it's okay that the feature isn't there(I agree it probably should), I've never seen even a suggestion that it was. If you can point out a page where they said TypePad offered pagination, then you have an argument. But again, it's supposed to be easy. Have you looked at the documentation for the Paginate plugin? It's still one of the largest and most involved in existence. You're probably going to come back and say that they could offer a stripped-down set of options, but let's be realistic. The moment they do that, someone is going to ask for a new little facet to be added, and it will easily balloon out to that level of complexity, possibly breaking the templates of people already making use of it in the process, since their users are sharing a system to some degree. Be careful what you use as back up.

* TypePad is not Movable Type.
* The ProNet articleyou linked–which, if you check the title, is about MT–regards a pagination control for use within the Movable Type /application/, not the output templates you’re concerned with. That piece is about developing plugins, not sites.
* Not that it entirely matters, because MT does /not/ provide template pagination, either. Check the manual. There /is/ the Paginate plugin, which requires PHP, but I challenge you to find a decent host that doesn’t offer it. Beyond plugins, there is another way to do it with Smarty(also PHP), and ultimately with any other templating engine you may want to use.
* My guess would be that 6A simply didn’t want to get into it. There are a lot of potential reasons for this, starting with the fact they have no idea what your server environment is going to be, much less what you choose to develop on the server with. If they released a plugin for say, PHP, everybody will start whining about bringing enough for the rest of the class, and complain for them to develop versions for whatever their favorite scripting language or templating system is. This would be a colossal waste of time, so they let the third-party developers deal with it for plugins, or individual users to come up with their own solutions. (I had links in here, but HTML is completely disallowed?)

On to TypePad, it has never been sold as a full-featured “control everything” product(that’s MT). Quite the opposite, and I’m guessing Comet is going to be even further removed from the system, to be more like MSN Spaces, for example. While I’m not suggesting it’s okay that the feature isn’t there(I agree it probably should), I’ve never seen even a suggestion that it was. If you can point out a page where they said TypePad offered pagination, then you have an argument.
But again, it’s supposed to be easy. Have you looked at the documentation for the Paginate plugin? It’s still one of the largest and most involved in existence. You’re probably going to come back and say that they could offer a stripped-down set of options, but let’s be realistic. The moment they do that, someone is going to ask for a new little facet to be added, and it will easily balloon out to that level of complexity, possibly breaking the templates of people already making use of it in the process, since their users are sharing a system to some degree.

]]>