ruddo

If you cripple the home.php file that way, your blog is gone. Or you’ll have to write awkward conditionals to let your blog pages show.

This technique is way complicated. I devised a new two-step one.

My technique does let the blog pages work OK.

I created a new technique to get a static WordPress home page that does not require plugins or hacks, just a drop of a file in your theme folder. Hope you like it.

Supercharged changed names — it’s now called Turbocharged and packs more features than ever before.

I’m actually selling a CMS solution based on WordPress. It’s not heavy duty at all, but it covers most of Web site builders’ needs (and sure as hell bloggers’ as well). I’ll be building more CMS-oriented features slowly. Time is scarce, you know!

It’s called Turbocharged.

Oh, the archives page problem persists in version 1.5.3. I found myself hit by the bug, and there’s no easy fix for now.

For the time being, those of you who don’t have the archives page, create a page with a slug named “archives” and select “Archives” as its page template.

I sell one theme and a theme and plugin pack.

Burnin’ R is the theme for sale

Supercharged WordPress is the plugin and theme pack

I am working on one. Software shop may be what you want.

Well, version 1.3.2 of the theme solves these issues ??

Okay, lemme shed some light on this issue. When you log in on to WP2.0, the server redirects you to the dashboard. At this point, the redirect is picked up by the browser and the browser starts loading wp-admin/index.php. After 20 or so seconds of waiting, the server *closes the HTTP connection* as if the index.php PHP script had timed out or something. This shows up on IE as the typical DNS error (and it’s NOT a DNS error) and on firefox as a blank page, with the complete URL to it as the page title.

No warning, error or notice is printed on the Apache (or web server) log whatsoever, so finding the root cause of the problem IS SIMPLY IMPOSSIBLE.

I did notice that disabling my plugins and enabling them one at a time till I have enabled them all again fixed the problem… but only temporarily. The next day, things were back as usual – no access to the dashboard.

PLEASE WP DEVELS: HELP US, THIS IS DRIVING ME INSANE.

BTW, the Google Sitemaps plugin consumes tons of RAM, which causes the Web server (actually, PHP) to die when posting. So if you experience broken connections just after hitting Publish on the post editor, suspect the Sitemaps plugin.

Yes, there’s a fix. Try this: https://iozblog.ionosfera.com/archives/2004/08/29/wordpress_trackback_fix/
It worked for me, confirmed.

1.2.1 doesn’t trackback or pingback, I can confirm that as well.

My WordPress 1.2.1 installation is not sending pingbacks nor trackbacking. 1.2 did the trick just fine. I don’t want to downgrade. What should I do?

I am having the exact same problem. Pingbacks don’t work, either, as well. I am using the freshly released 1.2.1 WordPress release. Please help! They did work in 1.2.