Title: Warning errors
Last modified: October 13, 2016

---

# Warning errors

 *  Resolved [swee10](https://wordpress.org/support/users/swee10/)
 * (@swee10)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/)
 * I activated your plug in and then did the google authentication. I am still receiving
   these errors:
 * Warning: call_user_func(CWS_Google_Picasa_Pro_Admin::section_reset_text) [function.
   call-user-func]: First argument is expected to be a valid callback in /home3/
   swee10/public_html/isingstravel.com/wp-admin/includes/template.php on line 1294
 * Warning: call_user_func_array() [function.call-user-func-array]: First argument
   is expected to be a valid callback, ‘section’ was given in /home3/swee10/public_html/
   isingstravel.com/wp-includes/plugin.php on line 524

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

 *  Plugin Author [nakunakifi](https://wordpress.org/support/users/nakunakifi/)
 * (@nakunakifi)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8297682)
 * Hello
 * These are ‘warnings’ not ‘errors’.
 * If they appearing in the front end of your site? Disable whatever it is that 
   is displaying them.
 *  Thread Starter [swee10](https://wordpress.org/support/users/swee10/)
 * (@swee10)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8318919)
 * I only get these warnings when I activate your plugin. At first I would get an
   error when I tried to delete your plugin, but I was just able to delete and reinstall–
   but I am still getting that warning. It seems to be combining multiple sites 
   that I own. CWS refers to a completely different WordPress site that I run. I
   did not even have your plugin on my other site. I did just install it to see 
   if it would clear things up but it has not. Any thoughts?
 *  Plugin Author [nakunakifi](https://wordpress.org/support/users/nakunakifi/)
 * (@nakunakifi)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8321079)
 * Hello
 * Turn off WP_DEBUG, simply by making sure the following line is in your wp-config.
   php file:
    define( ‘WP_DEBUG’, false );
 * Also, FTP into your web host and look in your plugins folder, if the plugin folder
   is still there delete it.
 * Do you have a link I can take a look at?
 *  Thread Starter [swee10](https://wordpress.org/support/users/swee10/)
 * (@swee10)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8326016)
 * I did what you suggested. I have to admit that you are talking above my understand.
   🙂
 * I changed it to true and then back to false again. The site is live and I can
   not have the warnings/notices up. I copied them below for you to see.
 * I also checked my plugin folder with my host and it was not there. Then I reinstalled
   your plugin again. Same result.
 * My plan was to upgrade to your Pro version, I just want to be sure I like the
   plugin. So, if that would fix it I will do that too.
 * Thank you for your time.
 * [http://www.isingstravel.com](http://www.isingstravel.com)
 * Notice: Use of undefined constant displayUpgradeID – assumed ‘displayUpgradeID’
   in /home3/swee10/public_html/isingstravel.com/wp-content/plugins/google-picasa-
   albums-viewer/cws-gpp-functions.php on line 105
 * Warning: Cannot modify header information – headers already sent by (output started
   at /home3/swee10/public_html/isingstravel.com/wp-content/plugins/google-picasa-
   albums-viewer/cws-gpp-functions.php:105) in /home3/swee10/public_html/isingstravel.
   com/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 62
 * Notice: add_custom_background is deprecated since version 3.4.0! Use add_theme_support(‘
   custom-background’, $args ) instead. in /home3/swee10/public_html/isingstravel.
   com/wp-includes/functions.php on line 3707
 * Notice: The called constructor method for WP_Widget in Widget_DisplayAlbums is
   deprecated since version 4.3.0! Use
    __construct() instead. in /home3/swee10/
   public_html/isingstravel.com/wp-includes/functions.php on line 3767
 * Notice: The called constructor method for WP_Widget in dc_jqverticalmegamenu_widget
   is deprecated since version 4.3.0! Use
    __construct() instead. in /home3/swee10/
   public_html/isingstravel.com/wp-includes/functions.php on line 3767
 * Notice: The called constructor method for WP_Widget in dc_jqverticalmegamenu_widget
   is deprecated since version 4.3.0! Use
    __construct() instead. in /home3/swee10/
   public_html/isingstravel.com/wp-includes/functions.php on line 3767
 * Notice: The called constructor method for WP_Widget in Admin_ShashinWidgetWp 
   is deprecated since version 4.3.0! Use
    __construct() instead. in /home3/swee10/
   public_html/isingstravel.com/wp-includes/functions.php on line 3767
 * Warning: call_user_func_array() [function.call-user-func-array]: First argument
   is expected to be a valid callback, ‘CWS_Google_Picasa_Pro_Admin::getCurrentUser’
   was given in /home3/swee10/public_html/isingstravel.com/wp-includes/plugin.php
   on line 524
 * Notice: Undefined variable: plugin_name in /home3/swee10/public_html/isingstravel.
   com/wp-content/plugins/google-picasa-albums-viewer/cws-gpp-functions.php on line
   97
 * Notice: Undefined variable: version in /home3/swee10/public_html/isingstravel.
   com/wp-content/plugins/google-picasa-albums-viewer/cws-gpp-functions.php on line
   97
 * Notice: Undefined variable: isPro in /home3/swee10/public_html/isingstravel.com/
   wp-content/plugins/google-picasa-albums-viewer/cws-gpp-functions.php on line 
   97
 *  Plugin Author [nakunakifi](https://wordpress.org/support/users/nakunakifi/)
 * (@nakunakifi)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8327320)
 * Hello
 * I have had a good look around your site and I cannot see any errors appearing!
 * Perhaps they only display when you are logged in as admin?
 * Some of the error notices you mention are created by my plugin, some are created
   by other plugins it looks like.
 * Soon I will be releasing v2.3.1 which will address the error notices created 
   by my plugin.
 *  Plugin Author [nakunakifi](https://wordpress.org/support/users/nakunakifi/)
 * (@nakunakifi)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8328240)
 * Hello
 * I have released v2.3.1 which greatly reduces the error warnings generated.
 * I am marking this as resolved as the display of error warnings is a web site 
   setup issue and not a plugin issue.
 * If you still want to discuss this please use email address on the plugin admin
   page.
 * Thanks
 *  Thread Starter [swee10](https://wordpress.org/support/users/swee10/)
 * (@swee10)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8328542)
 * This is now working perfectly! Thank you for your quick responses!
 *  Plugin Author [nakunakifi](https://wordpress.org/support/users/nakunakifi/)
 * (@nakunakifi)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8328798)
 * Hello
 * Great, thank you for letting me know.
 * If you are happy with it would you mind leaving a review? I am hoping to increase
   the number of reviews.
 * Thanks

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

The topic ‘Warning errors’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/google-picasa-albums-viewer_c6c0be.
   svg)
 * [Google Photos Gallery with Shortcodes](https://wordpress.org/plugins/google-picasa-albums-viewer/)
 * [Support Threads](https://wordpress.org/support/plugin/google-picasa-albums-viewer/)
 * [Active Topics](https://wordpress.org/support/plugin/google-picasa-albums-viewer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/google-picasa-albums-viewer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/google-picasa-albums-viewer/reviews/)

 * 8 replies
 * 2 participants
 * Last reply from: [nakunakifi](https://wordpress.org/support/users/nakunakifi/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/warning-errors-6/#post-8328798)
 * Status: resolved