prettyboymp
Forum Replies Created
-
Forum: Plugins
In reply to: [Lift: Search for WordPress] Sending trashed posts to be indexedIt is the desired behavior. In order for the search within the admin to work properly when the ‘trash’ post_status is selected, these posts need to be updated and available. The only post status currently filtered out is the ‘auto-draft’ that is created when first starting a post.
Forum: Plugins
In reply to: [Lift: Search for WordPress] Limiting indexed content types in v 1.3It’s an argument of the register_post_type() function. It defaults to whatever the ‘public’ argument is, which itself defaults to false. For more details, check out the codex, http://codex.wordpress.org/Function_Reference/register_post_type
Forum: Plugins
In reply to: [Lift: Search for WordPress] Author name not being sent to CloudSearchMarking resolved.
Forum: Plugins
In reply to: [Lift: Search for WordPress] Limiting indexed content types in v 1.3In version 1.3, we changed it from being a hardcoded list of default post types to include all posts types where the ‘exclude_from_search’ property was false. That is the correct way to filter out the post types you don’t want indexed within Lift, however, I would look at those other post types and figure out if they actually should have ‘exclude_from_search’ be set as true.
Forum: Plugins
In reply to: [Lift: Search for WordPress] Author name not being sent to CloudSearchThis should be fixed in v1.3.
Forum: Plugins
In reply to: [Lift: Search for WordPress] Author name not being sent to CloudSearchThank you for the details. We’re working on an update and should have an update version up later today or early tomorrow.
You’ll have to delete the transient rows manually. I incorrectly assumed that WordPress cleaned up it’s own expired transients, but actually doesn’t. The plugin works fine as long as you’re using a real object cache, but if not, you will run into the issue you had. I’ll try to get a fix released soon to correct this.
kduffy:
The plugin uses WordPress’ transient api, which is the built in caching wrapper for WordPress. If you’re not running a separate object cache, then yes, these items get stored in the options table with option names of _transient_xxxxxx.
Truthfully, if you’re clearing the cache when you save a new post and there is no other source of new content on the homepage that would need to otherwise be refreshed, you could set the expire argument to 0. This would keep it from ever clearing from cache except when you save a post.
No, since the block you may be caching might have nothing to do with posts, the cacheblocks timeout at 5 minute increments by default. If you need to clear the cache after a post is saved, you could add a hook to ‘save_post’ that will call back to WP_Cache_Block::GetInstance()->clear_cache();
Forum: Plugins
In reply to: [CMS Press] [Plugin: CMS Press] Admin Panel Links MissingUpdate has been released.
Forum: Plugins
In reply to: [CMS Press] [Plugin: CMS Press] Admin Panel Links MissingThank you for reporting. I’ll try to get a fix in this weekend.
Only use the same block-name if you want the same cached output for the other blocks where you call the same code.
Thank you for the find. I’ve updated the plugin to fix this issue and another I found with the key length being to long when transients are used.
Forum: Plugins
In reply to: [CMS Press] [Plugin: CMS Press] Appears To Break The Default Search FunctionDo you have any more detail for this? What do you mean by breaks? It doesn’t work as expected or you receive errors?