I use the Weaver ii Pro theme, and I posted on their forum re this plugin which would be very handy for me. I figured a child theme would be the perfect place to put the code to make the plugin functional. And it is -- because any other modifications would be lost in the next theme upgrade.
(I like the theme because it is highly customizable, flexible and mobile-friendly, even without specific mobile modifications.)
This is what the theme author, Bruce Weaver, replied:
Well, I need to preach a bit here.
1. That approach is entirely unnecessary. The plugin should be written to use a filter for 'the_author'. That is how WordPress is supposed to work.
2. The replacement example will soon not work. The function 'the_author()' is deprecated - it will likely go away from WP soon. There is a replacement, 'get_the_author()', and that replacement will run the final output through the 'the_author' filter, where a plugin should be able to replace things.
I wonder whether you could do a little more work on the plugin to make it more stable through WP upgrades and theme upgrades.
Bruce provided a hint for stability through WP upgrades, and a child theme would make the plugin survive theme upgrades.
Not everyone who might want to use the plugin is familiar with child themes. Thus a sample child theme including only the necessary modifications for this plugin would be very helpful. I might have posted the instructions, except that, if the plugin uses deprecated functions, its usefulness is rather short-term.
Looking forward to your thoughts on this.