Plugin for Static Publish

Why would you want to print your posts as a Static page?

WP stores information in the database, offers you permalinks, thus allowing updating / backup to be easily done.

I’m looking for this too. Why waste server resources generating pages on every request? It also lets all the caching and HTTP work be handled by Apache rather than re-implementing it in PHP. See Bake, don’t Fry for some more thoughts on this.

Try WP-cache.

Yes, WP-Cache will give you the same advantages of static files without losing the advantages of dynamic ones.

My thoughts Exactly… Why waste server resources!

I too am new to WordPress and am a Long Time GreyMatter user.

The static pages are Much more “server friendly” in that a Very Hefty .htaccess file does not have to be read with each request and sql resources are not used.

I’ve just downloaded the WP_Cache plug-in and will give it a try. The plug in may very well be the defining factor for a “Total Swith-Over” from GreyMatter.

@johnhouston,
Are you saying that GM with its rebuilding of pages and all the other stuff is less resource waster than WP? ??

I think one can always debate this but the fact remains that static pages served by apache will any day be faster than any sophisticated cacheing engine.
This apart, it also gives me an advantage to publish the same blog to multiple servers, using different themes (if i want). Repurposing of content, if you will ??

/a
https://apoorv.info

> I think one can always debate this but the fact remains that static pages served by apache will any day be faster than any sophisticated cacheing engine.

Nice, and? HTML 3.01 is faster to parser than XHTML and CSS. man pages are even cheaper.

But the point of software is to save human efforts, not CPUs. That’s to say, if you use WP and want to save lot of CPU without losing (well, almost) any dynamic feature including users’ preferences, use WP-Cache, which provides order of magnitud improvements (in the same order as static pages).

If you don’t like WP and want other blog software that produces static pages and hardly publish any comment in “real time”, go ahead… Save CPU time, waste yours ??

PS: I really don’t understand your reasoning. WP gives you lot of nice and useful features, WP-Cache bring the response time –and cpu usage– down to “almost” as static pages’ response time. And everything for free –in every sense–. But, yeah, you are arguing about the difference between “almost” and “same” [time]. Strange, to say the least.

I believe the following tutorial is compatible with WP v1.5.x, but you’ll have to do some thinking when it gets to the template modification section, as it only shows parts of the v1.2.x templates and not the v1.5.x themes.

https://www.tamba2.org.uk/wordpress/static/

I have been surfing blogger blogs for sometime now that I don’t see them any faster than WP blogs. In fact, I find them quite slow. WP-Cache is enough for a blog.

>PS: I really don’t understand your reasoning. WP gives you lot of nice and useful features, WP-Cache

I have never even once argued against those features. Infact i agree with you and that is why i moved to WP from blogger. All i am saying is that it would have been GREAT if i had the ability to publish static pages. Even in static publishing, i could use all those features that you mentioned and got the advantage of publishing to multiple blogs – one optimized for big screens and another one for PDAs. I know there are alternatives but the case in point is the ability to publish to multiple destinations.

/a
https://apoorv.info

Apoorv, if all you’re after is “the advantage of publishing to multiple blogs – one optimized for big screens and another one for PDAs,” try this plugin: https://dev.wp-plugins.org/browser/wordpress-mobile-edition/trunk/

> All i am saying is that it would have been GREAT if i had the ability to publish static pages.

It is “almost” what wp-cache allows to.

>Even in static publishing, i could use all those features that you mentioned

No. With static pages you cannot –for example– store users’ form data as wp [and wp-cache] does .

macmanx: Thanks for this. I’ll have a look at it. from whatever little i saw, it will still be on the same server. I guess i am expecting to much from a blogging system because i am used to bigger CMSes like vignette and interwoven where you can publish to multiple servers. So i was hoping i would be able to publish to my current blog as well as tripod ?? But thanks anyways. I’ll have a look at it. The other alternative i am looking at is to write some cron job which will ftp the WordPress XML feed to whichever server i want and then that server will have pages (phpm perl or even jsp) that will display this feed.

gallir: when i say static publish i understand that certain things like comments and user data will still be dynamic. Please have a look at blogspot and it will be more clear what i mean. The comments part is dynamic in blogspot but your blog entries are all static htmls.

I had made my own caching system, but realized that it didn’t make that much of a drop in resources even though I was getting ~10k hits a day.

Unless you’re running the server off a 386 or have 10 million blog posts, I say don’t bother as WordPress isn’t making much of a dent at all.