EnglishMike
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Comment ModerationI had a similar weird problem with one post that showed a count of 4 comments even though I had deleted them a long time ago (and were no longer in the database at all).
I was only able to fix it by adding a new comment to that post (then deleting it).
So try posting a new comment to the post the moderated comments were added to (if you can remember). That might reset the counters for you.
Forum: Plugins
In reply to: Possible to override wp_die() ?Use the ‘wp_die_handler’ filter and return the name of your own die handler function.
Just to add my 2 cents. I was having the same problem with my Lunarpages-based WordPress blogs — plugin automatic upgrades were failing because of DNS issues with the server I was on.
I opened a ticket and it took about four exchanges with support over 2 days before it finally got to the right person, and they quickly fixed the problem.
As jazzylee77 said, it pays to be politely persistent. One of the support staff replied to my bug report telling me that since I can upgrade plugins manually it wasn’t their problem to fix. I politely explained (again) why it was a server issue and needed to be fixed, and this time the gatekeepers let the bug report through.
Considering I am only paying $5/month for my shared server account (which is running three active blogs and a couple more in the near future) I am realistic about the level of support I will get from Lunarpages. Having said that, I have always found them to be very responsive (sometimes after a little persistence) and they have fixed all the issues I have reported to them — even one which took a fair amount of time and debugging on their behalf.
They don’t always get it right first time of asking, but in the end I am very happy with their support over the last year.
Forum: Fixing WordPress
In reply to: Using Tags with CategoriesDunno if this will help, but it worked for me:
// Filter out all the posts tagged with "demo" add_filter('request', 'em_filter_request'); function em_filter_request($params) { $params['tag__not_in'] = array(18); return $params; }Forum: Plugins
In reply to: [Plugin: AZIndex] CSS validation errorsThe problem was fixed in AZIndex v0.7.5. Thanks.
Forum: Everything else WordPress
In reply to: Table of Contents based on HeadingsHi, Hans. If you want a table of contents for your blog, showing links to all (or some) of your posts, then AZIndex will do that for you — no programming required!
But if you’re looking for a way to create a table of contents for the contents of one post (like you would in an MS Word document) then I’m afraid AZIndex isn’t for you.
Forum: Fixing WordPress
In reply to: Hiding Pages In The Navigation BarOk, there used to be a way to do this without a plugin or tweaking your theme code — all you had to do was create a private page and then add a public page as a child page. Works fine in 2.5 (and probably 2.6) and works for existing pages in 2.7 too, but when I just tried to do this again, WordPress won’t let me add a child to a private page any more.
This is a shame, and a quite unnecessary restriction — there is intrinsic reason why you should not be allowed to add a child page to a private page.
Forum: Plugins
In reply to: [Plugin: AZIndex] [AZ Index plugin] how to EXCLUDE categoriesD’oh — could be another problem. Silly me, I hard-coded the table names when I should have used the $wpdb prefix (like I did with the rest of the SQL query). I will update the plugin 0.6.2 — please try that version to see if it fixes your issues. If not, then it still could be an old version of MySQL.
Forum: Plugins
In reply to: [Plugin: AZIndex] [AZ Index plugin] how to EXCLUDE categoriesHey, yeah. Can you check to see which version of MySQL you are using. I tested this on MySQL 5.x and MySQL 4.1.x, but hadn’t realized that some WordPress installations are still using 4.0.x (which is over 4 years old!) and the support I added for excludes depends on subqueries which was added in back in MySQL 4.1.
You are the second person to report this, but I would like to confirm the the level of MySQL you are using before I do anything. If it’s 4.0.x then do you have an option to upgrade to 4.1.x or 5.0.x? My web host provides a painless upgrade path, so yours might too.
Sorry about the hassle. I do try not to use features that are not supported on all platforms WordPress runs on, but this one slipped through the cracks.
Mike
Forum: Installing WordPress
In reply to: [Plugin: AZIndex] Not caching the generated page?I just looked into AZIndex’s behavior when WP Super Cache is enabled. To my (pleasant) surprise, index pages are already cached correctly. When you enable WP Super Cache either half-on or full on, then even a multi-page index is cached correctly (i.e. all the pages in the index are cached separately).
Now, they only go into the regular cache (WP-Cache) not into the super-duper Super-Cache bucket (not sure why yet), but the AZIndex plugin code is not hit at all when those pages are accessed again proving that the cache is working. So if you have caching enabled, you should not be seeing any database access once the pages are in the cache.
Please let me know if that is not happening for you. The WP-Super-Cache settings page has a counter for the number of pages in each cache, so it should fairly easy to check if the index pages are going into the cache correctly. Once in the cache, the database access should stop on reload of the index page.
There is one issue I do need to fix. I have code which checks to see if the index might have changed in some way (when a new post is added or an existing one is modified). That currently does not get triggered if the index page is in the cache, so I need to hook into the cache code to ensure that changed will invalidate the cache.
Mike
Forum: Plugins
In reply to: [Plugin: AZIndex] [AZ Index plugin] how to EXCLUDE categoriesUpdate — the code for excluding cats and tags is written! Look for a new version this week!
Forum: Installing WordPress
In reply to: [Plugin: AZIndex] Not caching the generated page?Hi — glad you’re using the plugin successfully 🙂
I am just putting the finishing touches to a couple of new features — an option to include child categories and the ability to exclude items with certain categories and tags from an index — and then I will take a look at full page caching. I still have no idea if I can hook WPSuperCache yet, but it’s next on my list to look into.
Mike
Forum: Installing WordPress
In reply to: [Plugin: AZIndex] Not caching the generated page?Hey edelen. Sorry I didn’t see your question earlier — I’ve been out of town and very busy on other things since I got back.
There are a couple of things to keep in mind. AZIndex just caches which posts are included in the index and the order in which they are sorted within the index. This allows AZIndex to avoid having to sort and filter the complete index every time a page from the index is displayed. When a post is changed in a way that it affects it’s place in the index (e.g. the title is changed) then the index is flagged as dirty and the AZIndex cache is rebuilt which can be a very database intensive task. So the current caching does help reduce the load on the database by a large amount for big indexes.
But (and you knew there had to be a ‘but’) what AZIndex does not currently do is cache the contents of the index pages themselves. Therefore, if you have a 100 posts in your index page, AZIndex has to retrieve the information used in the index from each post — e.g. all the titles, subtitles, and descriptions. So the more entries per page you have in your index, the more database accesses there will be.
But I did try to be smart about it — the SQL query I use does not retrieve the content of the posts — just the metadata and titles, so there should be no risk of megabytes of data being retrieved for each page access. However, I suspect I can do more to alleviate the situation. I know that WPSuperCache does provide hooks into their code to allow other plugins to use their services. I will certainly take a look at see if I can enhance AZIndex so that it can use their caching facilities. I really don’t want to have to build a more complete caching solution from scratch AZIndex.
One thing you can do in the meantime which will reduce the database accesses per page is to reduce the number of items you display on one page (if possible). If you only have 20 – 30 items per page, I would be surprised if that puts too much of a load on your server.
I will check back in a couple of days, so feel free to leave a reply here if you want to.
Forum: Plugins
In reply to: [Plugin: AZIndex] [AZ Index plugin] how to EXCLUDE categoriesHi. Sorry for the slow reply. I haven’t been logging on for the past month or so, what with vacations and other stuff, so I have a bit of a backlog of requests and comments to go through.
I will take a look at the possibility of adding exclusions to the search. It all depends on how easy it would be to add them to the current SQL query without slowing it down too much. It might be feasible.
I will add it to my list of things to look at for a future release. (The list is getting quite long).
Thanks for the feedback.
Forum: Plugins
In reply to: [Plugin: TinyMCE Entities Patch] yes, but…Hey maddler, I understand your comment, but I respectfully disagree. The whole point of this little plugin is to make it easier to write posts without having to switch to HTML mode and use tags that at least some bloggers won’t know about.
Visual mode is a WYSIWYG mode and should *be* a WYSIWYG mode (or as close as possible) and not convert HTML entities that typed in visual mode — it should leave them alone (or, at least convert them to HTML that will make sure they appear in the post as they were typed).
When I am in visual mode, when I type &ersand;lt; and &ersand;gt that’s because I *want* &ersand;lt; and &ersand;gt; to appear in my post, not < and >. I should not have to jump though hoops whenever I want to insert any HTML entity in a post. When I type < and > TinyMCE converts that to &ersand;lt; and &ersand;gt; under the covers to make sure that you always get < and > in the post, so why shouldn’t users expect the same to happen when they want an HTML entity to be displayed in a post (and not the character it represents)?
Sorry, but forcing users to switch to HTML every time they want to do a little formatting or insert anything beginning with an ampersand is just bad usability — especially when there is a very simple fix/patch available.