Title: comkapi's Replies | WordPress.org

---

# comkapi

  [  ](https://wordpress.org/support/users/comkapi/)

 *   [Profile](https://wordpress.org/support/users/comkapi/)
 *   [Topics Started](https://wordpress.org/support/users/comkapi/topics/)
 *   [Replies Created](https://wordpress.org/support/users/comkapi/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/comkapi/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/comkapi/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/comkapi/engagements/)
 *   [Favorites](https://wordpress.org/support/users/comkapi/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[The Events Calendar] Single Event Page not showing](https://wordpress.org/support/topic/single-event-page-not-showing-2/)
 *  [comkapi](https://wordpress.org/support/users/comkapi/)
 * (@comkapi)
 * [5 years, 2 months ago](https://wordpress.org/support/topic/single-event-page-not-showing-2/#post-14221971)
 * Hello,
 * same issue, i resolved it by unchecking the checkbox in Display/
    “Use updated
   calendar designs” – “Enable updated designs for all calendar views”
 * Best regards
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Wordfence wflogs files all have Backdoor:PHP/eawtliul infection](https://wordpress.org/support/topic/wordfence-wflogs-files-all-have-backdoorphpeawtliul-infection/)
 *  [comkapi](https://wordpress.org/support/users/comkapi/)
 * (@comkapi)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/wordfence-wflogs-files-all-have-backdoorphpeawtliul-infection/#post-8181074)
 * Hello,
    i had it myself, you can open files and remove the first long line injected.
   But before you have to find how they have been changed, for me it was a bruteforce
   attack by ftp till they find password, i had to ask to hosting support to change
   it, see in your logs Good luck
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [compromised by options.php and a user named backup](https://wordpress.org/support/topic/compromised-by-optionsphp-and-a-user-named-backup/)
 *  [comkapi](https://wordpress.org/support/users/comkapi/)
 * (@comkapi)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/compromised-by-optionsphp-and-a-user-named-backup/#post-6605433)
 * Hello,
    found a user named backup as well, everything is up to date… Found a 
   gwzpassthru.php in uploads/dynamic_avia folder, this folder was in 0777 instead
   of 0755 hope it’s fixed
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[TW Recent Posts Widget] Notice: WP_Widget is deprecated since version 4.3.0](https://wordpress.org/support/topic/notice-wp_widget-is-deprecated-since-version-430/)
 *  [comkapi](https://wordpress.org/support/users/comkapi/)
 * (@comkapi)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/notice-wp_widget-is-deprecated-since-version-430/#post-6449808)
 * Beaucoup de sites sont impactés par ce message d’erreur :
 * > Notice: La méthode constructor appelée pour WP_Widget est obsolète depuis la
   > version 4.3.0 ! Veuillez utiliser
   >  __construct() à la place. in /var/www/vhosts/
   > mode-et-fantaisie.com/httpdocs/wp-includes/functions.php on line 3457
 * Le pourquoi est expliqué dans les autres posts, pour s’en sortir :
    - déjà ce message n’apparait que si WP_DEBUG est à true dans wp_config, laissez
      à true pour chercher et corriger vos erreurs mais passez le à false en dehors
      de ce temps de développement pour éviter de le retrouver comme description
      de votre site dans Google
    - téléchargez en local votre répertoire plugins puis avec un éditeur utilisez
      la fonction rechercher dans ce répertoire pour trouver tous les appels de 
      WP_Widget et comparer les différentes syntaxes.
 * Ci-dessous un exemple trouvé dans le plugin “google-adsense-plug-and-play” :
 * Mauvaise syntaxe :
 *     ```
       class GoogleAdsensePlugAndPlayWidget extends WP_Widget
       {
         function GoogleAdsensePlugAndPlayWidget()
         {
           $widget_ops = array('classname' => 'GoogleAdsensePlugAndPlayWidget', 'description' => 'Adsense Plug & Play - Sidebar add' );
           $this->WP_Widget('GoogleAdsensePlugAndPlayWidget', 'Adsense Plug & Play - Sidebar add', $widget_ops);
         }
        // ...........
       }
       ```
   
 * Bonne syntaxe une fois corrigée :
 *     ```
       class GoogleAdsensePlugAndPlayWidget extends WP_Widget
       {
         function __construct()
         {
           $widget_ops = array('classname' => 'GoogleAdsensePlugAndPlayWidget', 'description' => 'Adsense Plug & Play - Sidebar add' );
           parent::__construct('GoogleAdsensePlugAndPlayWidget', 'Adsense Plug & Play - Sidebar add', $widget_ops);
         }
        // ...........
       }
       ```
   
 * Avec un exemple c’est toujours + concret
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Nobs • Share Buttons] Notice error](https://wordpress.org/support/topic/notice-error/)
 *  Thread Starter [comkapi](https://wordpress.org/support/users/comkapi/)
 * (@comkapi)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/notice-error/#post-4860703)
 * Thank you Geoffrey, that’s fixed,
    Cool

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