Daniel Fru?y?ski (sirzooro)

I have just released DB Cache Reloaded 2.1, compatible with WP 3.0. This version is works fine in single site mode, multisite requires extra work. Please upgrade.

All,
I am working on new plugin version – it will be compatible with WP 3.0.

I got information that DB Cache Reloaded works fine with WP3.0 in wrapper mode. In order to enable it, please go to DB Cache Reloaded options page, disable caching, and then check “Wrapper Mode” checkbox and enable caching again.

Note: this will not work well with multisite install – when one blog will clear cache, it will clear cache for all blogs in network. I am aware of this issue and I am going to resolve it soon, but probably not in next plugin version – I probably will start work on it after I update and release plugin version compatible with WP 3.0.

No, I do not block. Changelogger works fine on my local 2.9 install. On 3.0 WP displays informations about available plugin updates, but Changelogger does not.

I did some debugging and found that this is causes by following check on line 142:
if (!isset($current->response[$file])) return false;

I also found that notices are caused by code in lines 116 and 117 – wp_enqueue_script and wp_enqueue_style does not return anything, so empty value is passed as 2nd param to add_action() calls, what later triggers these notices.

Thanks! ??

WordPress by default replaces some chars with corresponding HTML entities, so I decided to do the same in my plugin. I can add extra configuration options to disable this.

I have this plugin installed on few WP installs, and did not find any issues with it recently. Please make sure that you have entered GA ID on plugin’s configuration page. You can also check page source and compare tracking code added by plugin with one you pasted manually – please check if following line is the same in both:

var pageTracker = _gat._getTracker("UA-1234567-1");

I logged my ticked against WP core, because I planned to use Taxonomy Metadata to store SEO-related data for taxonomy items (categories, tags, etc) – e.g. meta description, keywords, custom title. These data would be managed directly from my plugin (Meta SEO Pack), so I do not need extra UI for this – my plugin would take care of this.

No, it should work as-is, without any extra changes. I will check this on my computer later.

Thanks for your post. These features definitely needs implementing.

BTW, For now you can use define DBCR_CACHE_DIR to specify temp dir for cache files.

@lokrin2000: I agree that retrieval of API key for Akismet could be simplified – e.g. enter email and get your key (if you have one) or new one (if you do not have it).

I am choosing following points from list above:
– auto-taxonomy UI;
– new default theme;
– built-in “Welcome to WordPress” guide for 1st time admin use/checklist (set settings, add profiles, set up comment options, dashboard modules, add widgets, pick a theme, etc) with ability to dismiss as you move through;
– below post widgets.

I also would like to see few API enhancements, which are already captured in Trac:
– metadata support for taxonomies;
– support for custom post types.

It will be also great if you will be accepting trivial enhancements like new actions and filters without planning them first – risk is minimal, and potential benefit may be huge (especially for developer asking for them).

@neononcon: could you check the Meta SEO Pack plugin and let me know if it has the same issue? I am author of it, and would like to know if it is affected by the same problem or not.

I think you can still configure them – this should not hurt, and will allow Meta SEO Pack to provide good page title and meta description (blog title is used as part of title for every page; meta description for home page by default uses blog title and tag line).

If you do not want to use them at all, you should to to Meta SEO Pack options and configure title rewriting and meta description to not use them.

Ups… Looks that WP Plugin Repository does not add hidden files (with names starting from dot) to plugin archives. I have just released version 2.0.1, which addresses this problem. It should appear online in a few minutes.

I saw in other thread that you was able to remove plugin successfully.

As I wrote, I plan to add WPMU support in next version.

DB Cache Reloaded is not compatible yet with WPMU. I am going to investigate this and add WPMU support in next version.