rtatum

Whoops. Now I can’t access my blog either.

https://tatumweb.com/blog/

(sorry for the link)

Rich

Bryan, I love your plugin! Thanks for keeping up updated and for adding great features, like the re-feeding of the combined RSS.

I only wish it could also auto-generate an OPML file for each of my output templates. For that I still have to rely on either my blogroll or an external aggregator like Newsgator.

Hope you can maybe add that someday.

Rich
BlogRodent

Bryan, sorry, this is off-topic, but I hope you’re still subscribing to this feed.

I cannot access your site, apparently because ozpolitics.info currently has no A records since your hosting provider moved you to a new server. There is nothing listed on the root servers (info) for this at all right now.

As a bonus, I’m sure this relieved your traffic woes.

https://www.dnsstuff.com/tools/traversal.ch?domain=ozpolitics.info&type=A

Rich.
BlogRodent

Good luck, Soletan, either nobody knows what’s going on with this, nobody cares, or it has no impact — because this issue has been raised elsewhere before and nobody seems to have answers.

Weird.

Rich.

This post worries me because my ISP has been shutting me down due to excessive cron utilization, stating that something has been running a cron job every two seconds:

I was sent the following as an example:

67.15.211.3 – – [28/Feb/2007:11:13:35 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:13:37 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:13:44 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:14:06 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:14:13 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“

Is there any way to view current cron jobs in queue? Is there any way to control this? It looks like, from the above, that the cron job that is being requested isn’t being processed.

Rich.

If you go to itscales.com (former webperf.org) you can request their site download your page and it will give you a graph showing the dns lookup time, the first byte received, the time till the last byte received, and the total size of every element on the page. And you’ll also see how long it takes their fast connection to download your page. A well-optimized page should load here in under 5-6 seconds, 3-5 being ideal. Less than that is excellent.

Your site loaded on my test at 18 seconds.

https://tools.itscales.com/cgi-bin/pma-dl?url=https://gamenation.neareverything.com/

WebsiteOptimization.com will also give you further assistance.

https://www.websiteoptimization.com/cgi-bin/wso/wso.pl?url=http%3A%2F%2Fgamenation.neareverything.com%2F

Be sure to use gzip on your site, it helps speed delivery of content. There’s a hack to implement gzip with wp-cache:

https://markjaquith.wordpress.com/2006/01/31/wp-cache2-and-gzip/

Rich.
BlogRodent

I’m having the same kind of server load/server utilization pattern, though I have the wp-cron.php file in my root, and my wp-includes/cron.php file already has the mentioned fix.

Here’s what my ISP just told me:

It seems that there is a local script that executes a connection to a internal resources each 2 seconds:

67.15.211.3 – – [28/Feb/2007:11:13:35 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:13:37 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:13:44 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:14:06 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“
67.15.211.3 – – [28/Feb/2007:11:14:13 -0600] “GET /blog/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129 HTTP/1.0” 403 – “-” “-“

Any ideas?

Rich
[sig moderated]

TSGuitar,

Regarding my permalinks, you asked:

“On ‘Blog Flux,’ for example, did you modify the post slug and it just didn’t take effect in the link? Know what I mean?”

On that particular post, I don’t think I modified the slug, at all. The title was “Blog Flux Complete!” and the slug naturally became blog-flux-complete. I didn’t modify it. And prior to the upgrade to 2.0, it was working. The 404s came after the upgrade.

You also asked:

“When you go to the dashboard and manage your posts, what happens when you click on the ‘view’ link for any of the articles you’re having trouble with?”

When I’m editing the article, the preview displays the 404 page. After editing it, when I click on “view” from the management page, I get the 404 page. I tried editing the post slug so that it was <i>different</i> from before and no longer matched the title, and it was still broken.

In short, the “Blog Flux Complete!” link slug was unmodified, and it is broken. After modifying it to something else, it remains broken.

Rich.

https://tatumweb.com/blog/index.php/2005/12/09/blog-flux-complete/

Yes. Sometimes my titles are quite long, so I shorten the slug. This worked previously, and I assumed that’s why the option is there to modify the slug.

It does work on most articles, still. For example:

Title: A teen, a plan, an essay: Hassan’s Chistmas in Baghdad.

URL: https://tatumweb.com/blog/index.php/2005/12/30/hassans-xmas-in-baghdad/

Rich.

I’m having similar problems. Some of my posts permalinks work fine. Others return a 404. Even editing the file, returning it to draft, and republishing it don’t help.

I went into the options and had WP update the permalink structure. No joy.

I’m using the following permalink setup:

/index.php/%year%/%monthnum%/%day%/%postname%/

I went to my archives page and tried a few posts. Archives here:

https://tatumweb.com/blog/index.php/archives/

I do not have an /archives/ folder. This is a WP page.

These permalinks, among others, do not work:

https://tatumweb.com/blog/index.php/2005/12/09/blog-flux-complete/

https://tatumweb.com/blog/index.php/2005/12/07/blog-flux-coming/

https://tatumweb.com/blog/index.php/2005/11/15/blogrodents-car-crash/

https://tatumweb.com/blog/index.php/2005/08/22/blog-tech-and-blog-updates/

Any ideas?

Rich.