desertjo

never mind. I got confused looking at the tags links. pretty new stuff make crazy brain.

After some poking around, and talking with the person who helped with the redesign, it seems that the calls the host admins were complaining about was the category listings from the right sidebar.

I had changed it to an ordered list from what had been there before, and yes, there are about 120 different categories (and increase that I hadn’t been aware of).

So, either the number of categories became a problem going from 1.5a6 to 1.5, or my use of a different procedure call to sort them was the problem.

Right now, I yanked out the category listing completely, and the site seems to be running 1000% faster.

didn’t know that… done 🙂

I hope I filed it in the right section… I almost chose “trivial” until I noticed the category “text”… I figure it belongs in “text” since it really isn’t affecting any application behaviors.

figured out part of the problem.
there’s a problem with this version where if you choose X number of days to show on the index page instead of X number of posts, all of your date related archives stop working. when the site went live, i’d chosen 35 posts for the index page, and left it alone.
seems like someone else with admin access started mucking around in the Options, and changed it to 6 days, which made everything date related disappear again.
a third admin caught it and changed it back, but it also uncovered a behavior that i wasn’t aware of… the 6 days bug permeates across all archives, monthly and category, so that all the monthly archives disappear (being that they are older than 6 days), and no category matches older than 6 days will appear either.
when you change to X number of posts, you only get X number of posts for each month or category. this interesting cascade doesn’t seem to affect the narchives.php script. anyone know if the date bug has been fixed in alpha4?
and allusion, i had been posting my questions about these problems in the Beta forum, but the lack of response there was what made me crack open and vent here 🙂

sorry for the misinterpretation, Root. i know the problems i’m running into are not the garden variety types most users run into, but if i’m the only one, then not enough people are putting the alpha versions through all paces, which is detrimental to everyone else in the long run… it means that what could be an impressive product is merely notable.
i’m not an old fart, but i’m starting to pine for the days when people took pride in trying to break a product while in the alpha stages, thus ensuring it wouldn’t break when it went gold. i guess Microsoft’s programming standards have permeated farther downstream than i’d imagined 🙂
the trackbcak ping bug i ran into seems to have been fixed in versions after 9/22, so current plan of action is to try something from earlier this week. i just have to wait until after the 3rd debate, and take advantage of the late night lulls during the weekend, and see what happens.

maybe. still, i’d really like to hear from one of the developers if there are any changes in a newer release because i don’t want to make any changes that could adversely affect what i already have in place.
right now, the site is live, http://www.reachm.com/amstreet/ running on 1.3a2, and has about 45 registered contributors. we’re still working on getting them used to WP, so if the two bugs i mentioned above haven’t been addressed, i’d be inclined to stay put until a version has been released that does fix them.
i’d also love to know if anyone else has run into issues where using the Spam Words and WP Blacklist may/do conflict with each other, but i haven’t had much luck in getting folks to respond to any of my posts… you were the second one 🙂

another update, with what looks to be very strange behavior… it seems like the use of the built in “spam words” to hold comments for moderation conflicts with Fahim’s WPBlacklist 1.21 plugin.
here’s what happens on my test site:
Fahim’s plugin is installed and activated, but would only hold posts with URLs containing any words in the blacklist table, but not any posts containing just the words themselves.
this behavior stayed the same when i entered the latest Spam Words into the Comment Moderation box in the Discussion Options panel, catching URLs but not the plain words.
but when i deactivated WPBlacklist 1.21, comments with both the URLs and plain words were held for moderation.
is it possible the built in WP code that parses for spam words and holds those comments is clashing with Fahim’s WPBlacklist code in a way that messes with both method’s ability to catch the words, but doesn’t affect how they catch URLs with those words?
anyone? anyone?
still using 1.3alpha2 (dated 30 Aug 2004), and Fahim’s WPBlacklist 1.21