I knew I thought this sounded familiar when I responded to the support thread. Didn’t catch it was a double-posting.
Could you let me know your thoughts on a custom filter name vs the generic one? Will be looking to push this out soonish once hearing back from you (and knocking up the stars would be nice too 😉 )
Cheers.
I was specifically referring to allowing for hooks into the “text to show after form” and “text to show after form” textareas.
I hacked the class-bjgk-genesis-enews-extended.php file like this:
// Allow filtering on widget text.
$instance[‘text’] = apply_filters(‘widget_text’, $instance[‘text’], $instance, $this->id_base);
// Allow filtering on widget text.
$instance[‘after_text’] = apply_filters(‘widget_text’, $instance[‘after_text’], $instance, $this->id_base);
In my case I’m trying to allow for Markdown to be used in the two textareas.
Sorry, I meant “text to show before form” and “text to show after form” textareas.
Right, that’s the areas the commit changed, though looking at a specific filter, rather than using widget_text since I’m not sure that plugin devs/site admins using that filter (meant for the default text widget in WP) would expect it to fire on those areas. Thoughts?
