Title: Deprecated issues causing problems for other plugins
Last modified: August 21, 2024

---

# Deprecated issues causing problems for other plugins

 *  Resolved [melcarthus](https://wordpress.org/support/users/melcarthus/)
 * (@melcarthus)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/deprecated-issues-causing-problems-for-other-plugins/)
 * I had an issue with polylang plugin. The translations per domain settings where
   not working as the actions the plugins makes came accross a 500 error caused 
   by this plugin.
   **Deprecated**: Creation of dynamic property Stop_Wp_Emails_Going_To_Spam\
   Admin\Admin_Settings::$donation is deprecated in **/home/sportver/public_html/
   wp-content/plugins/stop-wp-emails-going-to-spam/admin/class-admin-settings.php**
   on line **40**Please fix this issue as I will not downgrade my php version to
   solve this.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Alan Fuller](https://wordpress.org/support/users/alanfuller/)
 * (@alanfuller)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/deprecated-issues-causing-problems-for-other-plugins/#post-17966232)
 * Hi thanks for pointing that out
   Generally a Deprecation notice should not create
   a 500 error, as it is only a notice not a Fatal error so I’m surprised that you
   are experiencing any issue at all.If you edit the plugin fileadmin/class-admin-
   settings.phpand go line and correct
 *     ```wp-block-code
       protected $donations;
       ```
   
 * and remove the s
 *     ```wp-block-code
       protected $donation;
       ```
   
 * The notice will go. Although don’t be surpeised if you still have a 500 eror 
   but at least you will know to look elsewhere.
   I will fix this in the next release,
   so you are safe to edit your plugin files directly, but there is not timescale
   for the next release.
    -  This reply was modified 1 year, 9 months ago by [Alan Fuller](https://wordpress.org/support/users/alanfuller/).
 *  Thread Starter [melcarthus](https://wordpress.org/support/users/melcarthus/)
 * (@melcarthus)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/deprecated-issues-causing-problems-for-other-plugins/#post-17966348)
 * Yes you are correct I was thrown into a wrong direction by that. I was actually
   polylang itself. I forgot a check somewhere when I deactivated the plugin. Sorry
   for the inconvenience
 *  Plugin Author [Alan Fuller](https://wordpress.org/support/users/alanfuller/)
 * (@alanfuller)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/deprecated-issues-causing-problems-for-other-plugins/#post-17966396)
 * I’m glad you have got it sorted.
   A review of my support is always appreciated
   [https://wordpress.org/support/plugin/stop-wp-emails-going-to-spam/reviews/](https://wordpress.org/support/plugin/stop-wp-emails-going-to-spam/reviews/)
   Alan

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Deprecated issues causing problems for other plugins’ is closed to new
replies.

 * ![](https://ps.w.org/stop-wp-emails-going-to-spam/assets/icon-256x256.jpg?rev
   =2166277)
 * [Stop WP Emails Going to Spam](https://wordpress.org/plugins/stop-wp-emails-going-to-spam/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/stop-wp-emails-going-to-spam/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/stop-wp-emails-going-to-spam/)
 * [Active Topics](https://wordpress.org/support/plugin/stop-wp-emails-going-to-spam/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/stop-wp-emails-going-to-spam/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/stop-wp-emails-going-to-spam/reviews/)

## Tags

 * [deprecation](https://wordpress.org/support/topic-tag/deprecation/)
 * [server-error](https://wordpress.org/support/topic-tag/server-error/)

 * 3 replies
 * 2 participants
 * Last reply from: [Alan Fuller](https://wordpress.org/support/users/alanfuller/)
 * Last activity: [1 year, 9 months ago](https://wordpress.org/support/topic/deprecated-issues-causing-problems-for-other-plugins/#post-17966396)
 * Status: resolved