Title: Terrible development practices
Last modified: March 26, 2026

---

# Terrible development practices

 *  [anu](https://wordpress.org/support/users/anugupta-1/)
 * (@anugupta-1)
 * [2 months, 2 weeks ago](https://wordpress.org/support/topic/terrible-development-practices/)
 * This plugin is absolutely not recommended – the documentation isn’t great, and
   the development process even worse – the devs recently pushed an update that 
   broke many many installations (critical error, sites completely down), because
   they changed a huge number of function names that user templates relied on – 
   WITHOUT ANY MENTION IN THE CHANGELOG that this was a breaking change.

Viewing 1 replies (of 1 total)

 *  Plugin Support [WPEM Support](https://wordpress.org/support/users/wpem/)
 * (@wpem)
 * [2 months, 2 weeks ago](https://wordpress.org/support/topic/terrible-development-practices/#post-18864578)
 * Hello,
 * Thank you for taking the time to share your feedback. we truly understand how
   frustrating this experience must have been, especially if it impacted your live
   site.
   First and foremost, we sincerely apologize for the disruption caused by
   the recent update. We completely recognize that breaking changes, especially 
   those affecting user templates, should always be clearly communicated, and we
   take your feedback on this very seriously.
 * 
   That said, we’d like to provide some context. The recent changes were driven
   by updated security and coding standards required by the WordPress.org ecosystem.
   As part of aligning with these stricter guidelines, we had to refactor several
   core parts of the plugin, including function names and internal structures. These
   changes were necessary to ensure long-term stability, security, and compliance,
   but unfortunately, they also introduced unintended side effects for some existing
   implementations.We acknowledge that the changelog should have more explicitly
   highlighted these as breaking changes, and we’re already improving our release
   and communication process to prevent this in the future.
 * 
   In the meantime, our team is actively working on stabilizing the plugin and 
   providing clearer upgrade paths, including documentation and backward compatibility
   guidance wherever possible.We truly value your feedback; it helps us improve 
   not only the product but also how we support our users. If you’re open to it,
   we’d be happy to assist you directly in resolving the issues you’re facing.
 * Regards,
 * WP Event Manager.

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fterrible-development-practices%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this review.

 * ![](https://ps.w.org/wp-event-manager/assets/icon-256x256.png?rev=1622826)
 * [WP Event Manager – Events Calendar, Registrations, Sell Tickets with WooCommerce](https://wordpress.org/plugins/wp-event-manager/)
 * [Support Threads](https://wordpress.org/support/plugin/wp-event-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-event-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-event-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-event-manager/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [WPEM Support](https://wordpress.org/support/users/wpem/)
 * Last activity: [2 months, 2 weeks ago](https://wordpress.org/support/topic/terrible-development-practices/#post-18864578)