WordPress.org
Get WordPress

Plugin Directory

Changeset 847590


Ignore:
Timestamp:
01/29/2014 10:51:42 AM (12 years ago)
Author:
belinde
Message:

Tagging 0.5

Location:
autochmod
Files:
1 deleted
2 edited
12 copied

Legend:

Unmodified
Added
Removed

  • autochmod/tags/0.5/autochmod.php

    r840396 r847590  
    55  Description: Protect folders and files from unhautorized changes managing filesystem permissions.
    66  Author: Franco Traversaro
    7   Version: 0.4.2
     7  Version: 0.5
    88  Author URI: mailto:franco.traversaro@e2net.it
    99  Text Domain: autochmod
    … …  
    3535        add_action( 'init', array( $this, 'init' ) );
    3636        add_action( 'plugins_loaded', array( $this, 'plugins_loaded' ) );
     37        add_action( 'update_option_auto_updater.lock', array( $this, 'update_option_auto_updater_lock' ) );
     38        add_action( 'delete_option_auto_updater.lock', array( $this, 'delete_option_auto_updater_lock' ) );
    3739        if ( is_admin() )
    3840            add_action( 'admin_bar_menu', array( $this, 'admin_bar_menu' ), 10000 );
    … …  
    4951            }
    5052        }
     53    }
     54
     55    public function update_option_auto_updater_lock( $old_value, $value ) {
     56        $this->metti_permessi( ABSPATH );
     57        $when = time() + HOUR_IN_SECONDS;
     58        wp_schedule_single_event( $when, 'rimuovi_permessi_scrittura' );
     59        update_option( 'autochmod_safe_again_at', $when );
     60        update_option( 'autochmod_protection_active', false );
     61    }
     62
     63    public function delete_option_auto_updater_lock( $option ) {
     64        $this->togli_permessi( ABSPATH );
     65        wp_unschedule_event( get_option('autochmod_safe_again_at'), 'rimuovi_permessi_scrittura' );
     66        delete_option( 'autochmod_safe_again_at' );
     67        update_option( 'autochmod_protection_active', true );
    5168    }
    5269

  • autochmod/tags/0.5/readme.txt

    r841832 r847590  
    44Tags: security, filesystem, permissions, chmod, folders, files
    55Requires at least: 3.1.0
    6 Tested up to: 3.8
    7 Stable tag: 0.4.2
     6Tested up to: 3.8.1
     7Stable tag: 0.5
    88License: GPLv2 or later
    99License URI: http://www.gnu.org/licenses/gpl-2.0.html
    … …  
    1818
    1919Pay attention: the suggested configuration is, obviously, only a suggestion: depending on various system configuration the detection could be suboptimal or erroneous.
     20
     21**New in 0.5:** automatic updates should work regularly; the protection will disabled and re-enabled, hopefully without pain. But this feature is still experimental and I can't debug it untill next minor release of WP.
    2022
    2123== Installation ==
    … …  
    4143
    4244== Changelog ==
     45
     46= 0.5 =
     47* Let the automatic updates happen!
    4348
    4449= 0.4 =
    … …  
    7984**0.4.1:** Minor bug fixes
    8085**0.4.2:** Minor bug fixes
     86
     87= 0.5 =
     88Experimental feature: disable protection at the start of an automatic WP upgrade and re-enable at upgrade finished (or after 60 minutes if anything goes wrong). I haven't been able to really test it, so cross your fingers and hope for the best! But the worst it could happen is that the protection remains disactivated, or that WP dosn't get upgraded at all. Please inform me if anything goes wrong!

  • autochmod/trunk/autochmod.php

    r840396 r847590  
    55  Description: Protect folders and files from unhautorized changes managing filesystem permissions.
    66  Author: Franco Traversaro
    7   Version: 0.4.2
     7  Version: 0.5
    88  Author URI: mailto:franco.traversaro@e2net.it
    99  Text Domain: autochmod
    … …  
    3535        add_action( 'init', array( $this, 'init' ) );
    3636        add_action( 'plugins_loaded', array( $this, 'plugins_loaded' ) );
     37        add_action( 'update_option_auto_updater.lock', array( $this, 'update_option_auto_updater_lock' ) );
     38        add_action( 'delete_option_auto_updater.lock', array( $this, 'delete_option_auto_updater_lock' ) );
    3739        if ( is_admin() )
    3840            add_action( 'admin_bar_menu', array( $this, 'admin_bar_menu' ), 10000 );
    … …  
    4951            }
    5052        }
     53    }
     54
     55    public function update_option_auto_updater_lock( $old_value, $value ) {
     56        $this->metti_permessi( ABSPATH );
     57        $when = time() + HOUR_IN_SECONDS;
     58        wp_schedule_single_event( $when, 'rimuovi_permessi_scrittura' );
     59        update_option( 'autochmod_safe_again_at', $when );
     60        update_option( 'autochmod_protection_active', false );
     61    }
     62
     63    public function delete_option_auto_updater_lock( $option ) {
     64        $this->togli_permessi( ABSPATH );
     65        wp_unschedule_event( get_option('autochmod_safe_again_at'), 'rimuovi_permessi_scrittura' );
     66        delete_option( 'autochmod_safe_again_at' );
     67        update_option( 'autochmod_protection_active', true );
    5168    }
    5269

  • autochmod/trunk/readme.txt

    r841832 r847590  
    44Tags: security, filesystem, permissions, chmod, folders, files
    55Requires at least: 3.1.0
    6 Tested up to: 3.8
    7 Stable tag: 0.4.2
     6Tested up to: 3.8.1
     7Stable tag: 0.5
    88License: GPLv2 or later
    99License URI: http://www.gnu.org/licenses/gpl-2.0.html
    … …  
    1818
    1919Pay attention: the suggested configuration is, obviously, only a suggestion: depending on various system configuration the detection could be suboptimal or erroneous.
     20
     21**New in 0.5:** automatic updates should work regularly; the protection will disabled and re-enabled, hopefully without pain. But this feature is still experimental and I can't debug it untill next minor release of WP.
    2022
    2123== Installation ==
    … …  
    4143
    4244== Changelog ==
     45
     46= 0.5 =
     47* Let the automatic updates happen!
    4348
    4449= 0.4 =
    … …  
    7984**0.4.1:** Minor bug fixes
    8085**0.4.2:** Minor bug fixes
     86
     87= 0.5 =
     88Experimental feature: disable protection at the start of an automatic WP upgrade and re-enable at upgrade finished (or after 60 minutes if anything goes wrong). I haven't been able to really test it, so cross your fingers and hope for the best! But the worst it could happen is that the protection remains disactivated, or that WP dosn't get upgraded at all. Please inform me if anything goes wrong!
Note: See TracChangeset for help on using the changeset viewer.