Support » Plugin: WP Email Template » Wreckless plugin developer

  • I’m not sure why this plugin is in our system as it doesn’t seem to do anything useful, but what’s worse is there seems to be a recent code refactor that has changed namespaces and class names causing code errors where custom code has referenced this plugin. It’s quite useful to offer a depreciation notice or fallback when plugin changes like this go through, but in this case I assume the plugin developer only really cares about selling licences rather than maintaining a well supported plugin. Rather spoon my eyes out than see this plugin in any of my future systems.

    • This topic was modified 4 months, 2 weeks ago by dsouzaj86.
Viewing 1 replies (of 1 total)
  • Plugin Author Steve Truman

    (@a3rev)

    Hello @dsouzaj86

    I am sorry that the February 2020 release broke your custom code.

    Re this:

    there seems to be a recent code refactor that has changed namespaces and class names causing code errors where custom code has referenced this plugin.

    A quick look at the Changelog will show you that the change in the namespaces was done over a 2 month period between December 2019 and February 2020. There have been 5 maintenance releases since then, none of which changed namespaces. These where changed as part of upgrading the plugin to use PHP Composer.

    The first release for this was done in December 2019 as a major version release upgrading the plugin PHP to Composer Dependency manger.

    2.4.0 – 2019/12/16
    This feature release is a major refactor of the plugins PHP to Composer PHP Dependency Manager, a Sparkpost bug fix and compatibility with WordPress 5.3.1 and WooCommerce 3.8.1
    * Feature – Plugin fully refactored to Composer for cleaner and faster PHP code

    The second stage of this release was done in February 2020 and Sure if you had used the old namespaces in custom code they would break.

    2.4.1 – 2020/02/15
    * This maintenance release includes the completion of conversion to PHP composer, a fix for smpt api custom header, a security upgrade for a dependency script and compatibility with WordPress 5.3.2 and WooCommerce 3.9.2

    There have been 5 Maintenance releases since that release.

    It would appear that you have only recently upgraded the plugin and it has broken your custom code. At that time we also upgraded all of our plugins to PHP Composer – yours is the only report we have had of it breaking developers custom code and I am sorry that it happened to you.

    We do not set out to break out users code or sites and in fact spend a lot of time trying to ensure it never happens – but of course it is not possible in all cases, all of the time.

    Steve

    • This reply was modified 4 months, 2 weeks ago by Steve Truman.
Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this review.