_ck_

Aha, through the magic of trac we can generate a zip of the changed files…

https://trac.www.ads-software.com/changeset?format=zip&new=6293&old=6293&new_path=tags%2F2.3.1&old_path=tags%2F2.3

I made a patched version of text control awhile back that now works in 2.1-2.2 and also works on pages in addition to posts.

https://ckon.wordpress.com/2006/08/14/updated-version-of-text-control-that-works-with-wp-21/

One thought might be to check all the words against a “txt speak” dictionary and if the score is 10 or higher, the user is warned and comment moderated.

Okay I’ve figured out it’s a rewrite issue in htaccess – a rule outside wordpress that worked in apache is messing up litespeed – seems their compatibility is still not quite perfect even in 3.1

I disabled the rule (it was to remove index.php/html from urls that didn’t need it) and wordpress works correctly now (and much faster too!)

In the end, for now, I’ve just hacked wp-cache to handle only my feeds. Rather easy to do and since the feeds represent the 3rd most requested pages on the site, it has to help the load to some measurable effect. I’ll know soon enough!

Ah I get it now – especially once I realize the whole point of the cache is not to load the thousands of lines of wp code and plugins.

I guess what I need to do is find a variable that detects if wp-cache is turned on but experiencing a dynamic page call and cut out any custom bits like displaying the logged in user’s name.

Actually it might be more complicated than that – without wordpress loaded how does it know who is about to comment on a post and display the entry form for logged in vs guest commenters? I guess it doesn’t?

Try this FAQ and look in the middle where it tells you how to keep certain functions dynamic:

https://dev.wp-plugins.org/browser/wp-cache/trunk/README.txt?format=raw

I’ve opened a trac ticket on this. I could try to write such a routine myself but I figured I’d give the “pros” a chance to look at it first:

https://trac.www.ads-software.com/ticket/3907

By the way, if I edit new-post.php and make it load the older edit-form.php instead of edit-form-advanced.php it works perfectly.

It’s not plugins, it’s something to do with the ajax system that’s failing and causing a 30 second timeout.

added: note this is not an “update serivces” issue as I have nothing listed there – and besides it happens simply on loading the write new post page, not just saving it…

Oh wait, I just had a very simple idea pop into my head.

By forcing all comments to be unapproved on a per-post basis, the visitor would only be able to see their own comments.

Hence making them private comments.

Most other plugins should obey the fact the comment is unapproved and not show it.

The trick is hooking the comment before it is saved and making sure the approved status is set to ‘0’

Private comments are EXTREMELY tricky to pull off in wordpress. I experimented with it briefly but gave up because of the lack of plugin compatibility.

It’s very easy to control comments being displayed (except for the comment owner) via hacking your commments.php template page HOWEVER consider how many other plugins tie into comments without checking any other settings about them. There are search plugins that will allow searching and showing of comments without any checks for private, there are “subscribe to comments” plugins that would be ignorant of any privacy etc.

Even the blog-wide RSS comments would have to be patched so others would not see the comments.

If you don’t care about plugin compatibility I can basically show you how to patch comments.php to simulate private comments.

I can verify this (bad) behavior on 2.2 It also causes the “previous posts” “next posts” to not be shown because the count is gone. Only shows the results for one single page based on the number of posts per page you have set. Disabling it puts everything right again.

By the way I am using this code instead to get the post count which while nasty in technique at least uses the internal WP search to match the exact search process.

WordPress’s horrible search/results is perhaps it’s worst dirty little secret and in serious need of a major overhaul ??

Use the Text Control plugin 2.0b2 with my little fix documented here

You can then turn off wptexturize for individual posts which will fix the formatting for embed and objects (and script and other tags like that).

https://static.www.ads-software.com/builds/