Kat Hagan
Forum Replies Created
-
Forum: Plugins
In reply to: [Post By Email] PHP older 5.3 not supportedHi, sorry for the delay in replying to this – turns out I wasn’t getting notifications for new topics. 🙁
I believe I have fixed this issue now – can you test it again and let me know?
Thanks!
Forum: Plugins
In reply to: [Post By Email] feature requestThanks for the suggestions! The latest version of the plugin does implement PIN-based authentication, which would allow you to protect against email addresses getting spoofed.
If an email is received from an address that doesn’t match a user on the blog, it will be set to pending so that an administrator can review. Additionally, even if it matches a blog user, that user needs to have “publish_posts” capability (Author, Editor, or Administrator by default), otherwise those posts will also be set as pending.
Since WP admin already includes the ability to manage which users are allowed to create new posts, I’m hesitant to duplicate that functionality within the plugin, but maybe if the UI listed which users do have that capability, with a link to the user management screen so the admin can add/edit them?
Forum: Plugins
In reply to: [Post By Email] Activation errorSorry for the delay in answering this! Turns out I wasn’t receiving notifications for support topics. 🙁
Can you confirm whether you’re still having any of these issues with the latest version of the plugin? I have fixed quite a few bugs and made some improvements to the UI, including some better status messages.
Forum: Fixing WordPress
In reply to: add class to anchor in next_post_link & previous_post_linkFor anyone else curious, the reference to the twentyten theme is a translation/localization function. If you are making your own theme, you would change “twentyten” to be your theme’s name — just tells it where to look for translation files.
http://phpdoc.wordpress.org/trunk/WordPress/i18n/_wp-includes—l10n.php.html#function_x
Thanks for this! I was overjoyed to dig into the code and find that custom taxonomies are supported.
I had to make a small modification so that it would use BOTH the category and the custom taxonomy option (returning results that were in either the post’s category or the provided taxonomy). Adding multiple custom taxonomies would be pretty much the same.
Here’s what I did (in CatList.php):
// Added custom taxonomy support if ( !empty($this->params['taxonomy']) && !empty($this->params['tags']) ) { $args['tax_query'] = array( 'relation' => 'OR', array( 'taxonomy' => $this->params['taxonomy'], 'field' => 'slug', 'terms' => explode(",",$this->params['tags']) ), array( 'taxonomy' => 'category', 'field' => 'id', 'terms' => explode(",",$this->lcp_category_id) ) ); } else if ( !empty($this->params['tags']) ) { $args['cat'] = $this->lcp_category_id; $args['tag'] = $this->params['tags']; } else { $args['cat'] = $this->lcp_category_id; }The “relation => OR” is what does the magic of combining the results of the two arrays. You’d use “AND” if you want to return only posts that are in both.
Also, you have to take the $args[‘cat’] out at the top of that function (I just declared $args as an empty array); if ‘cat’ is defined in $args, it will ignore the tax_query and JUST return results from the category, so that’s why the ugly “else” code up there.
Just a five-minute hack but maybe it will help someone.