Conversation
supportIn Android browsers, I’m seeing this error message at the top of the page: /home/u182936292/domains/nccband.com/public_html/wp-content/plugins/flip-cards-module-divi/includes/modules/DiviFlipboxModule/DiviFlipboxModule.php on line 663. Line 663 is “public function render( $attrs, $content = null, $render_slug ) { “ This doesn’t occur on other devices or browsers. I have made sure that debug visibility is turned off. How can I remove this? Thanks in advance. The page I need help with: [ log in to see the link]
Hi @rwallis54 , The warning is caused by the plugin. You can disable warnings on your website to avoid seeing it by following the steps in this article: https://www.wpbeginner.com/wp-tutorials/how-to-turn-off-php-errors-in-wordpress/ It’s recommended to disable warnings on production sites. I will release a fix for this issue in the coming days. If you’d like to resolve it immediately, you can go to the file and line number mentioned in the error and replace the deprecated code. You need to replace the line public function render( $attrs, $content = null, $render_slug ) { with public function render( $attrs, $content, $render_slug ) { basically removing = null from the line. Let me know how it goes.
Thanks for your quick response! I have followed both sets of directions, and unfortunately still see the error message. I look forward to the updated plugin and hope that will resolve it. As mentioned previously, this only occurs on Android browsers. Others (Mac and iOS on Chrome and Safari, Windows Edge) don’t display it. This reply was modified 1 year, 9 months ago by rwallis54 .
Hi @rwallis54 , Can you verify that the changes you made to the plugin file were saved. Try opening the file again to check if you see $content = null , or $content If the change was saved then the error might still be showing due to caching. A cached version of the page being shown which contains the error. If you have any caching on the website then try clearing the cache. As that is the same change I am going to make in the updated plugin file. And making that change should remove the warning from the page.
Thanks! As those file changes were saved, it turned out to be the cache. Clearing it on the site fixed the issue. Thanks again!
Glad to know the issue has been fixed @rwallis54 . I would really appreciate it if you could leave a 5 star review for plugin.
I did so last week, and just updated it to reflect this interaction. Thanks again!
Hi @rwallis54 , The warning is caused by the plugin. You can disable warnings on your website to avoid seeing it by following the steps in this article: https://www.wpbeginner.com/wp-tutorials/how-to-turn-off-php-errors-in-wordpress/ It’s recommended to disable warnings on production sites. I will release a fix for this issue in the coming days. If you’d like to resolve it immediately, you can go to the file and line number mentioned in the error and replace the deprecated code. You need to replace the line public function render( $attrs, $content = null, $render_slug ) { with public function render( $attrs, $content, $render_slug ) { basically removing = null from the line. Let me know how it goes.
Thanks for your quick response! I have followed both sets of directions, and unfortunately still see the error message. I look forward to the updated plugin and hope that will resolve it. As mentioned previously, this only occurs on Android browsers. Others (Mac and iOS on Chrome and Safari, Windows Edge) don’t display it. This reply was modified 1 year, 9 months ago by rwallis54 .
Hi @rwallis54 , Can you verify that the changes you made to the plugin file were saved. Try opening the file again to check if you see $content = null , or $content If the change was saved then the error might still be showing due to caching. A cached version of the page being shown which contains the error. If you have any caching on the website then try clearing the cache. As that is the same change I am going to make in the updated plugin file. And making that change should remove the warning from the page.
Thanks! As those file changes were saved, it turned out to be the cache. Clearing it on the site fixed the issue. Thanks again!
Glad to know the issue has been fixed @rwallis54 . I would really appreciate it if you could leave a 5 star review for plugin.
I did so last week, and just updated it to reflect this interaction. Thanks again!