treorenegade

I just tried it (broadband). Only a slight wait. My guess would be the size of the various graphics, but you said this is the first time you’ve encountered the delay. FWIW, sometimes, for reasons beyond anyone’s control, page loads slow down. The ones after page #1 seem quicker, because the images etc are already downloaded and in cache. Suggest you wait a few days before you get seriously concerned.

I don’t know enough to give you a definitive answer, but I can share my troubleshooting technique when it comes to diagnosing htaccess-generated 500 errors.

First, note that my wp area is within a subdirectory (/wp/). But this should still work for all. I use a /test/ directory, because it confines the errors to an area unused by anyone, except me while testing. Keep it directly off root, even if you have a /wp/ style subdirectory. Makes it easier to get to.

1.) Create a special domain.com/test/ directory.
2.) Insert a plain index.html file with the body containing only <h2>ok</h2>.
3.) Copy your wp-related .htaccess to your harddrive’s /test/ directory.
3.) ftp to your server, create /test/ , and copy/transfer the .htaccess and index.html files to the directory you just created.

Enter mydomain.com/test/ in your browser. If the OK shows, you know the .htaccess file is, at least, correct in its syntax. Syntax errors = what causes those 500 error messages. (Note: this assumes your server will automatically read domain.com/test/ as domain.com/test/index.html. If not, type in the whole thing in your address bar.)

If you instead get the 500 error message, go back to the .htaccess file on your harddrive, and work thru it line by line. First go round, keep the condition lines but only one rewrite rule. Re-ftp. Call the /test/index.html file. If it shows, those few lines are ok. Go back, and add another rewrite line, test .. and so on down the lines of the .htaccess file. Sooner or later, after you ftp the file after adding a line, the error will occur. At that point, you know the exact line that’s causing the problem. Comment out that line (stick a # at the beginning of the line) , add the next rewrite line, ftp, and test. Keep repeating this til you’ve worked your way thru the entire file. At the end, you’ll have the offending line or lines. Once the precise problem line(s) is/are isolated, it’s a heck of alot easier researching your way to a solution (webmasterworld.com … Apache section is VERY good for this, although you likely will not find wordpress-specific solutions there).

BTW, FWIW, I just compared my wp .htaccess to yours.

1) I don’t see that “Structure:” business anywhere. I’m referring to line 14 and all lines thereafter, treating the rewritebase line as #0.

2) Further, there’s no /category … /author etc. (same lines #14 to end) at or near the start of my rewrite lines. Instead, it’s ^category/ …. ^author/ ….

Therefore, if I were confronted with your problem, I’d start by removing the “Structure: /” from each line in which it appears, ftp it to the /test/ area, and see if I get an ok. If so, then you’ve confirmed the offending lines. My permalinks work fine without that “structure: /” stuff, so I’d imagine yours would as well. But you’d then need to do one of 2 things: pinpoint what part of WP is causing those structure thingies to be inserted into the htaccess file; or, once you clean up that file, change permissions to turn off world-writable, so it can’t be adversely affected again.

=============
To be clear, your line #14 begins:
RewriteRule ^Structure: /category/(.+)/feed/

Mine begins:
RewriteRule ^category/(.+)/feed/

Ditto re: the remaining rewrite lines.

Example of a line turned-off, via commenting:
# RewriteRule ^Structure: /category/(.+)/feed/

=============

I’m using the latest WP, 1.5.3 I think is the number. But I didn’t see your “structure:” stuff in prior 1.5.2 either. Perhaps a plugin is causing this weirdness? You can check my list of active plugins to confirm that they play nice with others. https://law4pda.org/wp/plugins-used/ .

Again, I am NOT an expert or guru. I just learn as I plod along …

Could you kindly advise how to include the date, such as
Y.m.d (-linked title here-)
?? Please, and thank you!

This new plugin, Live Extended Archives, isn’t exactly what you’re talking about, but it’s very close. It can also be customized by folks like me (noob):

plugin home page
https://www.sonsofskadi.net/index.php/extended-live-archive
default look: https://www.sonsofskadi.net/index.php/archives/

customized version in action:
https://law4pda.org/wp/live-archives/

Apache/Unix-flavored server:

Create a plain textfile, named .htaccess . The command lines you need will look like the following. The # lines are comments, to remind me what I was doing months down the line.

[code]
# turn on rewrite engine; this line can
# only appears ONCE in this file
#
RewriteEngine on
#
#--------------
# look for the S.O.B. referer or host or referer
# vanguardnewsnetwork resolves to 66.139.76.169
# NC = ignore case (capitals vs lowercase)
# OR = satisfy any condition (host or referer or addy)
#
RewriteCond %{REMOTE_HOST} \.vanguardnewsnetwork\.com [NC,OR]
RewriteCond %{HTTP_REFERER} \.vanguardnewsnetwork\.com [NC,OR]
RewriteCond %{REMOTE_ADDR} ^66\.139\.76\.169
#
#-----------------
# send 'em right back where they came from
#
RewriteRule ^(.*) %{HTTP_REFERER} [R=301,L]
[/code]

— rewrite cond lines = 1 long line per ; this forum wraps ’em —

To test that your syntax is correct (without temporarily killing your site), create /test/ directory. Create an index.html file with one line: OK!, and upload that index file to the /test/ directory. (You can take mine: law4pda.org/test/index.html ). Upload your newly created .htaccss file to /test/ . Most hosts are configured to see index.(extension) as a default. Use your browser to navigate to yourdomain.com/test/ . If you see OK, you’re good to go, and can now place the .htaccess file in your root www directory. If you get a 500 internal server error, recheck the htaccess lines carefully, revise as necessary and retest.

example from my style.css:
code
input, textarea {
border: 1px solid #A1A19F;
margin: 1px 2px;
-moz-border-radius: 4px;
background-color: #FFFFCC;
color: #000000;
}
/code

https://www.navidazimi.com/projects/wp-lists/

https://russ.innereyes.com/wp-media/plugins/wp15/rustLinkoffs.zip

You’re not alone in wondering about this particular how-to.

Dang, I luv this place. Searching always gets me to a bingo! I’ve been quietly testing a b2evolution-to-wordpress installation, in a /test/ directory. Came here to figure out how to move WP to root. Ain’t e-life wunnerful?! ??

Hi Sara,
FWIW, I was looking up the identical issue here, but around 4a.m. (US/ET). I did find a 3 page thread that resolved things, but I didn’t save the URL. I do recall searching on <future post>, and that the thread was listed in the top half of the hit list. Only a handful. Sorry I can’t be more precise.
Once I studied it, I was able to test with the precise results I anticipated. But the server and my locale are identical; folks contributing to the thread had various server vs locale deals though, so you’ll find something to help.

I stand properly corrected. Although, in my defense, L(osingmy mind) Apache MySQL and PHP would also be right on the money!

Future Post with Companion Future Ping??
(Sorry– inadvertently hit the enter key before)
I’m in the process of testing/trying various blogware, using a LAMP WinXP setup as the testing bed. The one feature about which I’m very interested = scheduling future posts. While trying Expression Machine, I discovered that while one can arrange a future post, and that post will not appear until the scheduled date/time, the pings are sent out immediately– that is, when the posts are actually created. PHP complications on this matter were explained to me, but it makes no logical sense to me to have scheduled posts capability without companion scheduled pings. So, with that as background: researching various posts here confirms the availability of the future posts feature. My questions: does that include an associated scheduled ping facility, or is there a plug-in/hack which will accomplish the same thing?