Join the community today
Register Now

Wordpress Plugin does not recognize new versions

Discussion in 'Blogs & CMS usage' started by Venucci, Jul 3, 2019.

  1. Venucci

    Venucci Member

    75
    8
    8
    Sep 25, 2018
    Ratings:
    +8
    Local Time:
    5:09 PM
    currentyl
    10
    I am using professional paid plugins and if there is a new version i could upgrade it normally after installing centminmod the new version does not appear and i can not upgrade the plugin . Is that behaviour normal ? How could be possible to solve it ? thanks

     
  2. eva2000

    eva2000 Administrator Staff Member

    55,234
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,831
    Local Time:
    1:09 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    how are you upgrading the plugin via wp-admin/admin plugin update or via wp-cli command line ? what wp plugin is this ? it's name ?
     
  3. Venucci

    Venucci Member

    75
    8
    8
    Sep 25, 2018
    Ratings:
    +8
    Local Time:
    5:09 PM
    currentyl
    10
    Hi Eva ! I wish to upgrade it going to plugin area and click over update button .

    Wordpress GDPR by welaunch paid version from codecanyon . My version is 1.8.8 and there is a new version 1.8.9 and 1.8.10 but i do not have the update button option so does not recognize the existence of the new version .

    Image Map Pro (codecanyon) paid plugin neither recognize the new version
     
    Last edited: Jul 3, 2019
  4. eva2000

    eva2000 Administrator Staff Member

    55,234
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,831
    Local Time:
    1:09 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    wouldn't you need to download updates from codecanyon ?
     
  5. Venucci

    Venucci Member

    75
    8
    8
    Sep 25, 2018
    Ratings:
    +8
    Local Time:
    5:09 PM
    currentyl
    10
    No when i was using apache there was an automatic update available after the appearance of new version of the plugin and it was just clicking over update the plugin that s all . But it seems that it does not work with centminmod may be some users who are using some of the codecanyon plugins would clarify how they update their plugins using centminmod , hopefully
     
  6. eva2000

    eva2000 Administrator Staff Member

    55,234
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,831
    Local Time:
    1:09 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Centmin Mod values security and puts additional measures in place so that end users are also mindful of security. So in your case, you might need to whitelist or unblock the WP plugins.

    If you used centmin.sh menu option 22 auto installer Wordpress Nginx Auto Installer, the default wpsecure conf file at /usr/local/nginx/conf/wpincludes/${vhostname}/wpsecure_${vhostname}.conf where vhostname is your domain name, blocks php scripts from executing in wp-content for security

    Below links you can see examples of setting up specific wordpress location matches to punch a hole in the wpsecure blocking to whitelist specific php files that need to be able to run.

    If on Centmin Mod 123.09beta01, you may have ran into the new tools/autoprotect.sh cronjob feature outlined at Beta Branch - autoprotect.sh - apache .htaccess check & migration to nginx deny all | Centmin Mod Community You uploaded scripts may have .htaccess deny from all type files in their directories which may need bypassing autoprotect. It's a security feature that no other nginx based stack has as far as I know :)

    So instead, all .htaccess 'deny from all' detected directories now get auto generated Nginx equivalent location match and deny all setups except if you want to manually bypass the directory from auto protection via a .autoprotect-bypass file - details below here.

    You can read a few threads below on how autoprotect.sh may have caught some folks web apps falsely and the workarounds or improvements made to autoprotect.sh with the help of users feedback and troubleshooting.
    Check if your nginx vhost at either or both /usr/local/nginx/conf/conf.d/domain.com.conf and/or /usr/local/nginx/conf/conf.d/domain.com.ssl.conf has include file for autoprotect example
    Code (Text):
    include /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf;
    

    see if your directory for the script which has issues is caught in an autoprotect include entry in /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf which has a deny all entry
    Code (Text):
    cat /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf
    

    i.e.
    Code (Text):
    # /home/nginx/domains/domain.com/public/subdirectory/js
    location ~* ^/subdirectory/js/ { allow 127.0.0.1; deny all; }
    

    If caught you can whitelist it by autoprotect bypass .autoprotect-bypass file - details below here. So if problem js file is at domain.com/subdirectory/js/file.js then it is likely /subdirectory/js has a .htaccess with deny all in it - make sure that directory is meant to be publicly accessible by contacting author of script and if so, you can whitelist it and re-run autoprotect script to regenerate your /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf include file
    Code (Text):
    cd /home/nginx/domains/domain.com/public/subdirectory/js
    touch .autoprotect-bypass
    /usr/local/src/centminmod/tools/autoprotect.sh
    nprestart
    

    it maybe you need to also whitelist /subdirectory then it would be as follows creating bypass files at /home/nginx/domains/domain.com/public/subdirectory/.autoprotect-bypass and /home/nginx/domains/domain.com/public/subdirectory/js/.autoprotect-bypass
    Code (Text):
    cd /home/nginx/domains/domain.com/public/subdirectory/
    touch .autoprotect-bypass
    cd /home/nginx/domains/domain.com/public/subdirectory/js
    touch .autoprotect-bypass
    /usr/local/src/centminmod/tools/autoprotect.sh
    nprestart
    

    then double check to see if updated /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf include file now doesn't show an entry for /subdirectory/js