Title: Complianz causing WP error message Last modified: July 26, 2023 --- # Complianz causing WP error message * Resolved [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 11 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/) * THE ERROR MESSAGE IS Warning: Undefined property: stdClass::$thumbnail_url in/ home/httpd/vhosts/kinetizine.com/httpdocs/wp/wp-content/plugins/complianz-gdpr/ integrations/services/vimeo.php on line 35 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcomplianz-causing-wp-error-message%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 14 replies - 1 through 14 (of 14 total) * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [2 years, 11 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16924643) * Hello [@boxonline](https://wordpress.org/support/users/boxonline/), * It looks like this is just a warning (so, not an error) concerning a Vimeo placeholder that does not exist. In any case, such warnings should not be displayed on the front-end of your website. * PHP warnings like this usually only appear on the front-end of a site when you have [Debugging ](https://wordpress.org/documentation/article/debugging-in-wordpress/#example-wp-config-php-for-debugging) enabled on your WordPress site, which is not recommended for live websites. * You can check if your **wp-config.php **file contains a rule such as the below, which will activate the debugging mode. * `define('WP_DEBUG', true);` * If so, you can change `true` to `false` to disable debugging; this should get rid of the PHP warning about the placeholder. * Kind regards, Jarno * Thread Starter [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16926705) * I wish it were that simple Sorry, that does NOT seem to be the issue. * Below is the config file. * NOTE THAT DEBUG = FALSE * /** *  * For developers: WordPress debugging mode. *  * *  * Change this to true to enable the display of notices during development. *  * It is strongly recommended that plugin and theme developers use WP_DEBUG *  * in their development environments. *  */ * define(‘WP_DEBUG’, false); * /* That’s all, stop editing! Happy blogging. */ - This reply was modified 2 years, 10 months ago by [boxonline](https://wordpress.org/support/users/boxonline/). - This reply was modified 2 years, 10 months ago by [boxonline](https://wordpress.org/support/users/boxonline/). * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16929240) * Hi [@boxonline](https://wordpress.org/support/users/boxonline/), * You can use the below version of the plugin which should resolve this warning. I have uploaded the new plugin version on a WeTransfer link, so you can directly upload it as a new plugin under _Plugins > Add New > Upload Plugin_. * Download: [https://we.tl/t-mpC557RKuE](https://we.tl/t-mpC557RKuE) * Or obtain this version of the plugin manually from GitHub instead: [https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/check-if-vimeo-thumbnail-exists](https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/check-if-vimeo-thumbnail-exists) * Let me know if it resolves the warning. * Kind regards, Jarno * Thread Starter [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16929843) * done. * the new code resolved the issue. thanks. * saw this during the replace process [https://take.ms/rqTT8](https://take.ms/rqTT8) * and then this upon completion: Warning: get_headers([https://downloads.really-simple-security.com/rsssl/vulnerabilities/V1/plugin/contact-form-7.json](https://downloads.really-simple-security.com/rsssl/vulnerabilities/V1/plugin/contact-form-7.json)): Failed to open stream: Connection timed out in /home/httpd/vhosts/kinetizine. com/httpdocs/wp/wp-content/plugins/really-simple-ssl/security/wordpress/vulnerabilities. php on line 781 Warning: Trying to access array offset on value of type bool in /home/httpd/vhosts/kinetizine.com/httpdocs/wp/wp-content/plugins/really-simple- ssl/security/wordpress/vulnerabilities.php on line 782 Warning: get_headers([https://downloads.really-simple-security.com/rsssl/vulnerabilities/V1/plugin/mailchimp-for-wp.json](https://downloads.really-simple-security.com/rsssl/vulnerabilities/V1/plugin/mailchimp-for-wp.json)): Failed to open stream: Connection timed out in /home/httpd/vhosts/kinetizine. com/httpdocs/wp/wp-content/plugins/really-simple-ssl/security/wordpress/vulnerabilities. php on line 781 Warning: Trying to access array offset on value of type bool in /home/httpd/vhosts/kinetizine.com/httpdocs/wp/wp-content/plugins/really-simple- ssl/security/wordpress/vulnerabilities.php on line 782 * Should I be concerned about any of these warnings? * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16930023) * Hi [@boxonline](https://wordpress.org/support/users/boxonline/), * Glad to hear that the update fixed this warning! * As for the newly reported warning, it looks like the “Connection Timed Out” when _Really Simple SSL_ tried downloading vulnerability data from `downloads.really- simple-ssl.com`. I suspect that this server may have been down temporarily when the plugin tried to obtain that data, and the warning appeared as a result. * And this should not necessarily be a cause for concern, unless the warnings persist, of course! * Kind regards, Jarno * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16934747) * Hi [@boxonline](https://wordpress.org/support/users/boxonline/), * As a quick update regarding the Really Simple SSL warnings you posted, you may use the below version of the Really Simple SSL plugin, which contains improvements to catch these warnings and stop them from appearing. * You can download this plugin version from [this WeTransfer link,](https://we.tl/t-GAsDUiW0et) but you can find the branch on GitHub as well: * [https://github.com/Really-Simple-Plugins/really-simple-ssl/tree/improve-file-existence-check-json](https://github.com/Really-Simple-Plugins/really-simple-ssl/tree/improve-file-existence-check-json) * Kind regards, Jarno * Thread Starter [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16935239) * Thx Jarno * what do we need to do to ensure compatibility moving forward? * how can we easily update to future versions? * I noticed that deleting ‘really simple SSL’ has a significant impact on the pro version. Perhaps you can warn users before they delete the free plugin unwittingly 😜 * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16935247) * Hi [@boxonline](https://wordpress.org/support/users/boxonline/), * The above changes will be included in an upcoming Really Simple SSL update. * So, assuming that you already have auto-updates enabled for this plugin under _Plugins -> Installed Plugins_, you won’t have to do anything else to ensure compatibility. * Kind regards, Jarno * Thread Starter [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16935635) * super… thx * Thread Starter [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16935653) * how can I remove the URLs above from this public WP forum? * Plugin Author [Aert](https://wordpress.org/support/users/aahulsebos/) * (@aahulsebos) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16936692) * Hi [@boxonline](https://wordpress.org/support/users/boxonline/), * We can’t do it for you, and editing your first reply is probably no longer possible. The moderators rarely remove links; [https://wordpress.org/support/forum-user-guide/faq/#my-post-shows-up-on-a-search-for-my-domain-will-you-delete-my-post-or-my-my-link-within-my-post](https://wordpress.org/support/forum-user-guide/faq/#my-post-shows-up-on-a-search-for-my-domain-will-you-delete-my-post-or-my-my-link-within-my-post) * It’s only visible to logged-in users, if you’re concerned with bots for example. * regards Aert * Thread Starter [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/#post-16937412) * I’m unable to remove or edit any comments and that is concerning because I did NOT close this issue. The GDPR clearly states that users have the right to be forgotten. Are you saying that WP does not honor that right? * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/page/2/#post-16937449) * Hi [@boxonline](https://wordpress.org/support/users/boxonline/), * I’m afraid that we as plugin developers/support are unable to modify or adjust comments from other users on these forums. * As far as I know, comments on these forums can edited until ~30 minutes after posting. * Kind regards, Jarno * Thread Starter [boxonline](https://wordpress.org/support/users/boxonline/) * (@boxonline) * [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/page/2/#post-16938258) * Ok then. Time to move on. Nothing more to see here. * Thank you for your help and support. Viewing 14 replies - 1 through 14 (of 14 total) The topic ‘Complianz causing WP error message’ is closed to new replies. * ![](https://ps.w.org/complianz-gdpr/assets/icon-256x256.png?rev=2881064) * [Complianz - GDPR/CCPA Cookie Consent](https://wordpress.org/plugins/complianz-gdpr/) * [Frequently Asked Questions](https://wordpress.org/plugins/complianz-gdpr/#faq) * [Support Threads](https://wordpress.org/support/plugin/complianz-gdpr/) * [Active Topics](https://wordpress.org/support/plugin/complianz-gdpr/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/complianz-gdpr/unresolved/) * [Reviews](https://wordpress.org/support/plugin/complianz-gdpr/reviews/) ## Tags * [Undefined property](https://wordpress.org/support/topic-tag/undefined-property/) * [vimeo](https://wordpress.org/support/topic-tag/vimeo/) * 17 replies * 3 participants * Last reply from: [boxonline](https://wordpress.org/support/users/boxonline/) * Last activity: [2 years, 10 months ago](https://wordpress.org/support/topic/complianz-causing-wp-error-message/page/2/#post-16938258) * Status: resolved