wp-cache.php000066600000601503152133035240006753 0ustar00

' . __( 'Warning! PHP Safe Mode Enabled!', 'wp-super-cache' ) . '

' . __( 'You may experience problems running this plugin because SAFE MODE is enabled.', 'wp-super-cache' ) . ' '; if( !ini_get( 'safe_mode_gid' ) ) { _e( 'Your server is set up to check the owner of PHP scripts before allowing them to read and write files.', 'wp-super-cache' ) . " "; printf( __( 'You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.', 'wp-super-cache' ), WP_CONTENT_DIR ); } else { _e( 'You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.', 'wp-super-cache' ); } echo '

'; } if ( '' == get_option( 'permalink_structure' ) ) { echo '

' . __( 'Permlink Structure Error', 'wp-super-cache' ) . '

'; echo "

" . __( 'A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.' ) . "

"; echo '
'; return false; } if( $wp_cache_debug || !$wp_cache_cron_check ) { if( function_exists( "wp_remote_get" ) == false ) { $hostname = str_replace( 'http://', '', str_replace( 'https://', '', get_option( 'siteurl' ) ) ); if( strpos( $hostname, '/' ) ) $hostname = substr( $hostname, 0, strpos( $hostname, '/' ) ); $ip = gethostbyname( $hostname ); if( substr( $ip, 0, 3 ) == '127' || substr( $ip, 0, 7 ) == '192.168' ) { ?>

Troubleshooting section of the readme.txt', 'wp-super-cache' ), 'http://wordpress.org/plugins/wp-super-cache/faq/' ); ?>

0.01, 'blocking' => true)); if( is_array( $cron ) ) { if( $cron[ 'response' ][ 'code' ] == '404' ) { ?>

Warning! wp-cron.php not found!

Troubleshooting section of the readme.txt', 'wp-super-cache' ), 'http://wordpress.org/plugins/wp-super-cache/faq/' ); ?>

' . __( "Cannot continue... fix previous problems and retry.", 'wp-super-cache' ) . '

'; return false; } if (!wp_cache_check_global_config()) { return false; } if ( 1 == ini_get( 'zlib.output_compression' ) || "on" == strtolower( ini_get( 'zlib.output_compression' ) ) ) { ?>

this page for instructions on modifying your php.ini.', 'wp-super-cache' ); ?>

%s/wp-cache-config.php and cannot be modified. That file must be writeable by the web server to make any changes.', 'wp-super-cache' ), WP_CONTENT_DIR ); ?>

This page explains how to change file permissions.', 'wp-super-cache' ); ?>

chmod 666 /wp-cache-config.php chmod 644 /wp-cache-config.php

this form to enable it.', 'wp-super-cache' ); ?>

' />

chmod 755 /

This page explains how to change file permissions.', 'wp-super-cache' ); ?>

' />

' . __( 'Mobile rewrite rules detected', 'wp-super-cache' ) . "

"; echo "

" . __( 'For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.', 'wp-super-cache' ) . "

" . __( 'This will have no affect on ordinary users but mobile users will see uncached pages.', 'wp-super-cache' ) . "

"; } elseif ( $wp_cache_mod_rewrite && $cache_enabled && $wp_cache_mobile_enabled && $scrules != '' && ( ( false == empty( $wp_cache_mobile_prefixes ) && false === strpos( $scrules, addcslashes( implode( '|', $wp_cache_mobile_prefixes ), ' ' ) ) ) || ( false == empty( $wp_cache_mobile_browsers ) && false === strpos( $scrules, addcslashes( implode( '|', $wp_cache_mobile_browsers ), ' ' ) ) ) ) ) { ?>

  2. Update Mod_Rewrite Rules button.', 'wp-super-cache' ); ?>
  3. # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.', 'wp-super-cache' ), $home_path ); ?>
  4. # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|%s|wp-postpass_).*$ add these lines: (do it twice, once for each section)', 'wp-super-cache' ), $home_path, wpsc_get_logged_in_cookie() ); ?>

Update Mod_Rewrite Rules button.', 'wp-super-cache' ); ?>

__( 'Required to serve compressed supercache files properly.', 'wp-super-cache' ), 'mod_headers' => __( 'Required to set caching information on supercache pages. IE7 users will see old pages without this module.', 'wp-super-cache' ), 'mod_expires' => __( 'Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.', 'wp-super-cache' ) ); foreach( $required_modules as $req => $desc ) { if( !in_array( $req, $mods ) ) { $missing_mods[ $req ] = $desc; } } if( isset( $missing_mods) && is_array( $missing_mods ) ) { ?>

"; foreach( $missing_mods as $req => $desc ) { echo "
  • $req - $desc
    • "; } echo ""; echo "
    "; } } if ( $valid_nonce && isset( $_POST[ 'action' ] ) && $_POST[ 'action' ] == 'dismiss_htaccess_warning' ) { wp_cache_replace_line('^ *\$dismiss_htaccess_warning', "\$dismiss_htaccess_warning = 1;", $wp_cache_config_file); $dismiss_htaccess_warning = 1; } elseif ( !isset( $dismiss_htaccess_warning ) ) { $dismiss_htaccess_warning = 0; } if ( isset( $disable_supercache_htaccess_warning ) == false ) $disable_supercache_htaccess_warning = false; if ( $dismiss_htaccess_warning == 0 && $wp_cache_mod_rewrite && $super_cache_enabled && $disable_supercache_htaccess_warning == false && get_option( 'siteurl' ) != get_option( 'home' ) ) { $home_dir = str_replace( get_option( 'home' ), '', get_option( 'siteurl' ) ); ?>

    here. Unfortunately, WordPress writes to the .htaccess in the install directory, not where your site is served from.
    When you update the rewrite rules in this plugin you will have to copy the file to where your site is hosted. This will be fixed in the future.', 'wp-super-cache' ); ?>

    ' />

    \'\"\r\n\t\(\)]/', '', $_GET[ 'path' ] ) ); die(); } } if ( isset( $_GET[ 'action' ] ) && $_GET[ 'action' ] == 'delcachepage' ) add_action( 'admin_init', 'admin_bar_delete_page' ); function wp_cache_manager_updates() { global $wp_cache_mobile_enabled, $wp_cache_mfunc_enabled, $wp_supercache_cache_list, $wp_cache_config_file, $wp_cache_hello_world, $wp_cache_clear_on_post_edit, $cache_rebuild_files, $wp_cache_mutex_disabled, $wp_cache_not_logged_in, $wp_cache_make_known_anon, $cache_path, $wp_cache_object_cache, $_wp_using_ext_object_cache, $wp_cache_refresh_single_only, $cache_compression, $wp_cache_mod_rewrite, $wp_supercache_304, $wp_super_cache_late_init, $wp_cache_front_page_checks, $cache_page_secret, $wp_cache_disable_utf8, $wp_cache_no_cache_for_get; global $cache_schedule_type, $cache_scheduled_time, $cache_max_time, $cache_time_interval, $wp_cache_shutdown_gc; if ( !wpsupercache_site_admin() ) return false; if ( false == isset( $cache_page_secret ) ) { $cache_page_secret = md5( date( 'H:i:s' ) . mt_rand() ); wp_cache_replace_line('^ *\$cache_page_secret', "\$cache_page_secret = '" . $cache_page_secret . "';", $wp_cache_config_file); } $valid_nonce = isset($_REQUEST['_wpnonce']) ? wp_verify_nonce($_REQUEST['_wpnonce'], 'wp-cache') : false; if ( $valid_nonce == false ) return false; if ( isset( $_POST[ 'action' ] ) && $_POST[ 'action' ] == 'easysetup' ) { $_POST[ 'action' ] = 'scupdates'; if( isset( $_POST[ 'wp_cache_easy_on' ] ) && $_POST[ 'wp_cache_easy_on' ] == 1 ) { $_POST[ 'wp_cache_mobile_enabled' ] = 1; $_POST[ 'wp_cache_status' ] = 'all'; $_POST[ 'super_cache_enabled' ] = 2; // PHP $_POST[ 'cache_rebuild_files' ] = 1; unset( $_POST[ 'cache_compression' ] ); if ( $cache_path != WP_CONTENT_DIR . '/cache/' ) $_POST[ 'wp_cache_location' ] = $cache_path; // // set up garbage collection with some default settings if ( ( !isset( $wp_cache_shutdown_gc ) || $wp_cache_shutdown_gc == 0 ) && false == wp_next_scheduled( 'wp_cache_gc' ) ) { if ( false == isset( $cache_schedule_type ) ) { $cache_schedule_type = 'interval'; $cache_time_interval = 600; $cache_max_time = 1800; wp_cache_replace_line('^ *\$cache_schedule_type', "\$cache_schedule_type = '$cache_schedule_type';", $wp_cache_config_file); wp_cache_replace_line('^ *\$cache_time_interval', "\$cache_time_interval = '$cache_time_interval';", $wp_cache_config_file); wp_cache_replace_line('^ *\$cache_max_time', "\$cache_max_time = '$cache_max_time';", $wp_cache_config_file); } wp_schedule_single_event( time() + 600, 'wp_cache_gc' ); } } else { unset( $_POST[ 'wp_cache_status' ] ); $_POST[ 'super_cache_enabled' ] = 0; wp_clear_scheduled_hook( 'wp_cache_check_site_hook' ); wp_clear_scheduled_hook( 'wp_cache_gc' ); wp_clear_scheduled_hook( 'wp_cache_gc_watcher' ); } $advanced_settings = array( 'wp_super_cache_late_init', 'wp_cache_disable_utf8', 'wp_cache_no_cache_for_get', 'wp_supercache_304', 'wp_cache_mfunc_enabled', 'wp_cache_mobile_enabled', 'wp_cache_front_page_checks', 'wp_supercache_cache_list', 'wp_cache_hello_world', 'wp_cache_clear_on_post_edit', 'wp_cache_not_logged_in', 'wp_cache_make_known_anon','wp_cache_object_cache', 'wp_cache_refresh_single_only', 'cache_compression', 'wp_cache_mutex_disabled' ); foreach( $advanced_settings as $setting ) { if ( isset( $$setting ) && $$setting == 1 ) { $_POST[ $setting ] = 1; } } } if( isset( $_POST[ 'action' ] ) && $_POST[ 'action' ] == 'scupdates' ) { if( isset( $_POST[ 'wp_cache_location' ] ) && $_POST[ 'wp_cache_location' ] != '' && ( !isset( $cache_path ) || $_POST[ 'wp_cache_location' ] != $cache_path ) ) { $dir = realpath( trailingslashit( dirname( $_POST[ 'wp_cache_location' ] ) ) ); if ( $dir == false ) $dir = WP_CONTENT_DIR . '/cache/'; else $dir = trailingslashit( $dir ) . trailingslashit(wpsc_deep_replace( array( '..', '\\' ), basename( $_POST[ 'wp_cache_location' ] ) ) ); $new_cache_path = $dir; } else { $new_cache_path = WP_CONTENT_DIR . '/cache/'; } if ( $new_cache_path != $cache_path ) { if ( file_exists( $new_cache_path ) == false ) rename( $cache_path, $new_cache_path ); $cache_path = $new_cache_path; wp_cache_replace_line('^ *\$cache_path', "\$cache_path = '" . $cache_path . "';", $wp_cache_config_file); } if( isset( $_POST[ 'wp_super_cache_late_init' ] ) ) { $wp_super_cache_late_init = 1; } else { $wp_super_cache_late_init = 0; } wp_cache_replace_line('^ *\$wp_super_cache_late_init', "\$wp_super_cache_late_init = " . $wp_super_cache_late_init . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_disable_utf8' ] ) ) { $wp_cache_disable_utf8 = 1; } else { $wp_cache_disable_utf8 = 0; } wp_cache_replace_line('^ *\$wp_cache_disable_utf8', "\$wp_cache_disable_utf8 = " . $wp_cache_disable_utf8 . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_no_cache_for_get' ] ) ) { $wp_cache_no_cache_for_get = 1; } else { $wp_cache_no_cache_for_get = 0; } wp_cache_replace_line('^ *\$wp_cache_no_cache_for_get', "\$wp_cache_no_cache_for_get = " . $wp_cache_no_cache_for_get . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_supercache_304' ] ) ) { $wp_supercache_304 = 1; } else { $wp_supercache_304 = 0; } wp_cache_replace_line('^ *\$wp_supercache_304', "\$wp_supercache_304 = " . $wp_supercache_304 . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_mfunc_enabled' ] ) ) { $wp_cache_mfunc_enabled = 1; } else { $wp_cache_mfunc_enabled = 0; } wp_cache_replace_line('^ *\$wp_cache_mfunc_enabled', "\$wp_cache_mfunc_enabled = " . $wp_cache_mfunc_enabled . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_mobile_enabled' ] ) ) { $wp_cache_mobile_enabled = 1; } else { $wp_cache_mobile_enabled = 0; } wp_cache_replace_line('^ *\$wp_cache_mobile_enabled', "\$wp_cache_mobile_enabled = " . $wp_cache_mobile_enabled . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_front_page_checks' ] ) ) { $wp_cache_front_page_checks = 1; } else { $wp_cache_front_page_checks = 0; } wp_cache_replace_line('^ *\$wp_cache_front_page_checks', "\$wp_cache_front_page_checks = " . $wp_cache_front_page_checks . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_supercache_cache_list' ] ) ) { $wp_supercache_cache_list = 1; } else { $wp_supercache_cache_list = 0; } wp_cache_replace_line('^ *\$wp_supercache_cache_list', "\$wp_supercache_cache_list = " . $wp_supercache_cache_list . ";", $wp_cache_config_file); if ( isset( $_POST[ 'wp_cache_status' ] ) && 'all' == $_POST[ 'wp_cache_status' ] ) { if ( $_POST[ 'wp_cache_status' ] == 'all' ) wp_cache_enable(); if ( isset( $_POST[ 'super_cache_enabled' ] ) ) { if ( $_POST[ 'super_cache_enabled' ] == 0 ) { wp_cache_enable(); // logged in cache wp_super_cache_disable(); } if( $_POST[ 'super_cache_enabled' ] == 1 ) { $wp_cache_mod_rewrite = 1; // we need this because supercached files can be served by PHP too. } else { $wp_cache_mod_rewrite = 0; // cache files served by PHP } wp_cache_replace_line('^ *\$wp_cache_mod_rewrite', '$wp_cache_mod_rewrite = ' . $wp_cache_mod_rewrite . ";", $wp_cache_config_file); } } else { wp_cache_disable(); } if( isset( $_POST[ 'wp_cache_hello_world' ] ) ) { $wp_cache_hello_world = 1; } else { $wp_cache_hello_world = 0; } wp_cache_replace_line('^ *\$wp_cache_hello_world', '$wp_cache_hello_world = ' . $wp_cache_hello_world . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_clear_on_post_edit' ] ) ) { $wp_cache_clear_on_post_edit = 1; } else { $wp_cache_clear_on_post_edit = 0; } wp_cache_replace_line('^ *\$wp_cache_clear_on_post_edit', "\$wp_cache_clear_on_post_edit = " . $wp_cache_clear_on_post_edit . ";", $wp_cache_config_file); if( isset( $_POST[ 'cache_rebuild_files' ] ) ) { $cache_rebuild_files = 1; } else { $cache_rebuild_files = 0; } wp_cache_replace_line('^ *\$cache_rebuild_files', "\$cache_rebuild_files = " . $cache_rebuild_files . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_mutex_disabled' ] ) ) { $wp_cache_mutex_disabled = 0; } else { $wp_cache_mutex_disabled = 1; } if( defined( 'WPSC_DISABLE_LOCKING' ) ) { $wp_cache_mutex_disabled = 1; } wp_cache_replace_line('^ *\$wp_cache_mutex_disabled', "\$wp_cache_mutex_disabled = " . $wp_cache_mutex_disabled . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_not_logged_in' ] ) ) { if( $wp_cache_not_logged_in == 0 && function_exists( 'prune_super_cache' ) ) prune_super_cache ($cache_path, true); $wp_cache_not_logged_in = 1; } else { $wp_cache_not_logged_in = 0; } wp_cache_replace_line('^ *\$wp_cache_not_logged_in', "\$wp_cache_not_logged_in = " . $wp_cache_not_logged_in . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_make_known_anon' ] ) ) { if( $wp_cache_make_known_anon == 0 && function_exists( 'prune_super_cache' ) ) prune_super_cache ($cache_path, true); $wp_cache_make_known_anon = 1; } else { $wp_cache_make_known_anon = 0; } wp_cache_replace_line('^ *\$wp_cache_make_known_anon', "\$wp_cache_make_known_anon = " . $wp_cache_make_known_anon . ";", $wp_cache_config_file); if( $_wp_using_ext_object_cache && isset( $_POST[ 'wp_cache_object_cache' ] ) ) { if( $wp_cache_object_cache == 0 && function_exists( 'prune_super_cache' ) ) prune_super_cache( $cache_path, true ); $wp_cache_object_cache = 1; } else { $wp_cache_object_cache = 0; } wp_cache_replace_line('^ *\$wp_cache_object_cache', "\$wp_cache_object_cache = " . $wp_cache_object_cache . ";", $wp_cache_config_file); if( isset( $_POST[ 'wp_cache_refresh_single_only' ] ) ) { $wp_cache_refresh_single_only = 1; } else { $wp_cache_refresh_single_only = 0; } wp_cache_replace_line('^ *\$wp_cache_refresh_single_only', "\$wp_cache_refresh_single_only = '" . $wp_cache_refresh_single_only . "';", $wp_cache_config_file); if ( defined( 'WPSC_DISABLE_COMPRESSION' ) ) { $cache_compression = 0; wp_cache_replace_line('^ *\$cache_compression', "\$cache_compression = " . $cache_compression . ";", $wp_cache_config_file); } else { if ( isset( $_POST[ 'cache_compression' ] ) ) { $new_cache_compression = 1; } else { $new_cache_compression = 0; } if ( 1 == ini_get( 'zlib.output_compression' ) || "on" == strtolower( ini_get( 'zlib.output_compression' ) ) ) { echo '
    ' . __( "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.", 'wp-super-cache' ) . '
    '; } else { if ( $new_cache_compression != $cache_compression ) { $cache_compression = $new_cache_compression; wp_cache_replace_line('^ *\$cache_compression', "\$cache_compression = " . $cache_compression . ";", $wp_cache_config_file); if ( function_exists( 'prune_super_cache' ) ) prune_super_cache( $cache_path, true ); delete_option( 'super_cache_meta' ); } } } } } if ( isset( $_GET[ 'page' ] ) && $_GET[ 'page' ] == 'wpsupercache' ) add_action( 'admin_init', 'wp_cache_manager_updates' ); function wp_cache_manager() { global $wp_cache_config_file, $valid_nonce, $supercachedir, $cache_path, $cache_enabled, $cache_compression, $super_cache_enabled, $wp_cache_hello_world; global $wp_cache_clear_on_post_edit, $cache_rebuild_files, $wp_cache_mutex_disabled, $wp_cache_mobile_enabled, $wp_cache_mobile_browsers, $wp_cache_no_cache_for_get; global $wp_cache_cron_check, $wp_cache_debug, $wp_cache_not_logged_in, $wp_cache_make_known_anon, $wp_supercache_cache_list, $cache_page_secret, $cache_home_path; global $wp_super_cache_front_page_check, $wp_cache_object_cache, $_wp_using_ext_object_cache, $wp_cache_refresh_single_only, $wp_cache_mobile_prefixes; global $wpmu_version, $cache_max_time, $wp_cache_mod_rewrite, $wp_supercache_304, $wp_super_cache_late_init, $wp_cache_front_page_checks, $wp_cache_disable_utf8, $wp_cache_mfunc_enabled; if ( !wpsupercache_site_admin() ) return false; // used by mod_rewrite rules and config file if ( function_exists( "cfmobi_default_browsers" ) ) { $wp_cache_mobile_browsers = cfmobi_default_browsers( "mobile" ); $wp_cache_mobile_browsers = array_merge( $wp_cache_mobile_browsers, cfmobi_default_browsers( "touch" ) ); } elseif ( function_exists( 'lite_detection_ua_contains' ) ) { $wp_cache_mobile_browsers = explode( '|', lite_detection_ua_contains() ); } else { $wp_cache_mobile_browsers = array( '2.0 MMP', '240x320', '400X240', 'AvantGo', 'BlackBerry', 'Blazer', 'Cellphone', 'Danger', 'DoCoMo', 'Elaine/3.0', 'EudoraWeb', 'Googlebot-Mobile', 'hiptop', 'IEMobile', 'KYOCERA/WX310K', 'LG/U990', 'MIDP-2.', 'MMEF20', 'MOT-V', 'NetFront', 'Newt', 'Nintendo Wii', 'Nitro', 'Nokia', 'Opera Mini', 'Palm', 'PlayStation Portable', 'portalmmm', 'Proxinet', 'ProxiNet', 'SHARP-TQ-GX10', 'SHG-i900', 'Small', 'SonyEricsson', 'Symbian OS', 'SymbianOS', 'TS21i-10', 'UP.Browser', 'UP.Link', 'webOS', 'Windows CE', 'WinWAP', 'YahooSeeker/M1A1-R2D2', 'iPhone', 'iPod', 'Android', 'BlackBerry9530', 'LG-TU915 Obigo', 'LGE VX', 'webOS', 'Nokia5800' ); } if ( function_exists( "lite_detection_ua_prefixes" ) ) { $wp_cache_mobile_prefixes = lite_detection_ua_prefixes(); } else { $wp_cache_mobile_prefixes = array( 'w3c ', 'w3c-', 'acs-', 'alav', 'alca', 'amoi', 'audi', 'avan', 'benq', 'bird', 'blac', 'blaz', 'brew', 'cell', 'cldc', 'cmd-', 'dang', 'doco', 'eric', 'hipt', 'htc_', 'inno', 'ipaq', 'ipod', 'jigs', 'kddi', 'keji', 'leno', 'lg-c', 'lg-d', 'lg-g', 'lge-', 'lg/u', 'maui', 'maxo', 'midp', 'mits', 'mmef', 'mobi', 'mot-', 'moto', 'mwbp', 'nec-', 'newt', 'noki', 'palm', 'pana', 'pant', 'phil', 'play', 'port', 'prox', 'qwap', 'sage', 'sams', 'sany', 'sch-', 'sec-', 'send', 'seri', 'sgh-', 'shar', 'sie-', 'siem', 'smal', 'smar', 'sony', 'sph-', 'symb', 't-mo', 'teli', 'tim-', 'tosh', 'tsm-', 'upg1', 'upsi', 'vk-v', 'voda', 'wap-', 'wapa', 'wapi', 'wapp', 'wapr', 'webc', 'winw', 'winw', 'xda ', 'xda-' ); // from http://svn.wp-plugins.org/wordpress-mobile-pack/trunk/plugins/wpmp_switcher/lite_detection.php } $wp_cache_mobile_browsers = apply_filters( 'cached_mobile_browsers', $wp_cache_mobile_browsers ); // Allow mobile plugins access to modify the mobile UA list $wp_cache_mobile_prefixes = apply_filters( 'cached_mobile_prefixes', $wp_cache_mobile_prefixes ); // Allow mobile plugins access to modify the mobile UA prefix list if ( function_exists( 'do_cacheaction' ) ) { $wp_cache_mobile_browsers = do_cacheaction( 'wp_super_cache_mobile_browsers', $wp_cache_mobile_browsers ); $wp_cache_mobile_prefixes = do_cacheaction( 'wp_super_cache_mobile_prefixes', $wp_cache_mobile_prefixes ); } $mobile_groups = apply_filters( 'cached_mobile_groups', array() ); // Group mobile user agents by capabilities. Lump them all together by default // mobile_groups = array( 'apple' => array( 'ipod', 'iphone' ), 'nokia' => array( 'nokia5800', 'symbianos' ) ); if ( false == apply_filters( 'wp_super_cache_error_checking', true ) ) return false; if ( function_exists( 'get_supercache_dir' ) ) $supercachedir = get_supercache_dir(); if( get_option( 'gzipcompression' ) == 1 ) update_option( 'gzipcompression', 0 ); if( !isset( $cache_rebuild_files ) ) $cache_rebuild_files = 0; $valid_nonce = isset($_REQUEST['_wpnonce']) ? wp_verify_nonce($_REQUEST['_wpnonce'], 'wp-cache') : false; /* http://www.netlobo.com/div_hiding.html */ ?> '; echo '
    '; echo '

    ' . __( 'WP Super Cache Settings', 'wp-super-cache' ) . '

    '; // set a default if ( $cache_enabled == false && isset( $wp_cache_mod_rewrite ) == false ) { $wp_cache_mod_rewrite = 0; } elseif ( !isset( $wp_cache_mod_rewrite ) && $cache_enabled && $super_cache_enabled ) { $wp_cache_mod_rewrite = 1; } if ( !isset( $_GET[ 'tab' ] ) ) $_GET[ 'tab' ] = ''; if ( $_GET[ 'tab' ] == '' && $cache_enabled && ( $wp_cache_mod_rewrite || $super_cache_enabled == false ) ) { $_GET[ 'tab' ] = 'settings'; echo '

    ' . __( 'Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.', 'wp-super-cache' ) . '

    '; } wpsc_admin_tabs(); if ( isset( $wp_super_cache_front_page_check ) && $wp_super_cache_front_page_check == 1 && !wp_next_scheduled( 'wp_cache_check_site_hook' ) ) { wp_schedule_single_event( time() + 360 , 'wp_cache_check_site_hook' ); wp_cache_debug( 'scheduled wp_cache_check_site_hook for 360 seconds time.', 2 ); } if(isset($_REQUEST['wp_restore_config']) && $valid_nonce) { unlink($wp_cache_config_file); echo '' . __( 'Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.', 'wp-super-cache' ) . ''; } if ( substr( get_option( 'permalink_structure' ), -1 ) == '/' ) { wp_cache_replace_line('^ *\$wp_cache_slash_check', "\$wp_cache_slash_check = 1;", $wp_cache_config_file); } else { wp_cache_replace_line('^ *\$wp_cache_slash_check', "\$wp_cache_slash_check = 0;", $wp_cache_config_file); } $home_path = parse_url( site_url() ); $home_path = trailingslashit( array_key_exists( 'path', $home_path ) ? $home_path[ 'path' ] : '' ); if (! isset( $wp_cache_home_path ) ) $wp_cache_home_path = '/'; if ( "$home_path" != "$wp_cache_home_path" ) wp_cache_replace_line('^ *\$wp_cache_home_path', "\$wp_cache_home_path = '$home_path';", $wp_cache_config_file); if( $wp_cache_mobile_enabled == 1 ) { update_cached_mobile_ua_list( $wp_cache_mobile_browsers, $wp_cache_mobile_prefixes, $mobile_groups ); } ?>
    '; wp_cache_files(); break; case "preload": if ( !$cache_enabled ) wp_die( __( 'Caching must be enabled to use this feature', 'wp-super-cache' ) ); echo ''; if ( $super_cache_enabled == true && false == defined( 'DISABLESUPERCACHEPRELOADING' ) ) { global $wp_cache_preload_interval, $wp_cache_preload_on, $wp_cache_preload_taxonomies, $wp_cache_preload_email_me, $wp_cache_preload_email_volume, $wp_cache_preload_posts, $wpdb; $count = $wpdb->get_var( "SELECT count(*) FROM {$wpdb->posts} WHERE post_status = 'publish'" ); if ( $count > 1000 ) { $min_refresh_interval = 720; } else { $min_refresh_interval = 30; } if ( array_key_exists('action', $_POST) && $_POST[ 'action' ] == 'preload' && $valid_nonce ) { if ( $_POST[ 'posts_to_cache' ] == 'all' ) { $wp_cache_preload_posts = 'all'; } else { $wp_cache_preload_posts = (int)$_POST[ 'posts_to_cache' ]; } wp_cache_replace_line('^ *\$wp_cache_preload_posts', "\$wp_cache_preload_posts = '$wp_cache_preload_posts';", $wp_cache_config_file); if ( isset( $_POST[ 'preload' ] ) && $_POST[ 'preload' ] == __( 'Cancel Cache Preload', 'wp-super-cache' ) ) { $next_preload = wp_next_scheduled( 'wp_cache_preload_hook' ); if ( $next_preload ) { update_option( 'preload_cache_counter', array( 'c' => 0, 't' => time() ) ); wp_unschedule_event( $next_preload, 'wp_cache_preload_hook' ); } $fp = @fopen( $cache_path . "stop_preload.txt", 'w' ); @fclose( $fp ); echo "

    " . __( 'Scheduled preloading of cache almost cancelled. It may take up to a minute for it to cancel completely.', 'wp-super-cache' ) . "

    "; } elseif ( isset( $_POST[ 'custom_preload_interval' ] ) && ( $_POST[ 'custom_preload_interval' ] == 0 || $_POST[ 'custom_preload_interval' ] >= $min_refresh_interval ) ) { // if preload interval changes than unschedule any preload jobs and schedule any new one. $_POST[ 'custom_preload_interval' ] = (int)$_POST[ 'custom_preload_interval' ]; if ( $wp_cache_preload_interval != $_POST[ 'custom_preload_interval' ] ) { $next_preload = wp_next_scheduled( 'wp_cache_full_preload_hook' ); if ( $next_preload ) { update_option( 'preload_cache_counter', array( 'c' => 0, 't' => time() ) ); add_option( 'preload_cache_stop', 1 ); wp_unschedule_event( $next_preload, 'wp_cache_full_preload_hook' ); if ( $wp_cache_preload_interval == 0 ) { echo "

    " . __( 'Scheduled preloading of cache cancelled.', 'wp-super-cache' ) . "

    "; } } if ( $_POST[ 'custom_preload_interval' ] != 0 ) wp_schedule_single_event( time() + ( $_POST[ 'custom_preload_interval' ] * 60 ), 'wp_cache_full_preload_hook' ); } $wp_cache_preload_interval = (int)$_POST[ 'custom_preload_interval' ]; wp_cache_replace_line('^ *\$wp_cache_preload_interval', "\$wp_cache_preload_interval = $wp_cache_preload_interval;", $wp_cache_config_file); if ( isset( $_POST[ 'preload_email_me' ] ) ) { $wp_cache_preload_email_me = 1; } else { $wp_cache_preload_email_me = 0; } wp_cache_replace_line('^ *\$wp_cache_preload_email_me', "\$wp_cache_preload_email_me = $wp_cache_preload_email_me;", $wp_cache_config_file); if ( isset( $_POST[ 'wp_cache_preload_email_volume' ] ) && in_array( $_POST[ 'wp_cache_preload_email_volume' ], array( 'less', 'medium', 'many' ) ) ) { $wp_cache_preload_email_volume = $_POST[ 'wp_cache_preload_email_volume' ]; } else { $wp_cache_preload_email_volume = 'medium'; } wp_cache_replace_line('^ *\$wp_cache_preload_email_volume', "\$wp_cache_preload_email_volume = '$wp_cache_preload_email_volume';", $wp_cache_config_file); if ( isset( $_POST[ 'preload_taxonomies' ] ) ) { $wp_cache_preload_taxonomies = 1; } else { $wp_cache_preload_taxonomies = 0; } wp_cache_replace_line('^ *\$wp_cache_preload_taxonomies', "\$wp_cache_preload_taxonomies = $wp_cache_preload_taxonomies;", $wp_cache_config_file); if ( isset( $_POST[ 'preload_on' ] ) ) { $wp_cache_preload_on = 1; } else { $wp_cache_preload_on = 0; } wp_cache_replace_line('^ *\$wp_cache_preload_on', "\$wp_cache_preload_on = $wp_cache_preload_on;", $wp_cache_config_file); if ( isset( $_POST[ 'preload' ] ) && $_POST[ 'preload' ] == __( 'Preload Cache Now', 'wp-super-cache' ) ) { @unlink( $cache_path . "preload_mutex.tmp" ); update_option( 'preload_cache_counter', array( 'c' => 0, 't' => time() ) ); wp_schedule_single_event( time() + 10, 'wp_cache_preload_hook' ); echo "

    " . __( 'Scheduled preloading of cache in 10 seconds.' ) . "

    "; } elseif ( (int)$_POST[ 'custom_preload_interval' ] ) { @unlink( $cache_path . "preload_mutex.tmp" ); update_option( 'preload_cache_counter', array( 'c' => 0, 't' => time() ) ); wp_schedule_single_event( time() + ( (int)$_POST[ 'custom_preload_interval' ] * 60 ), 'wp_cache_full_preload_hook' ); echo "

    " . sprintf( __( 'Scheduled preloading of cache in %d minutes', 'wp-super-cache' ), (int)$_POST[ 'custom_preload_interval' ] ) . "

    "; } } } echo '

    ' . __( 'This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.', 'wp-super-cache' ) . '

    '; echo '

    ' . __( 'Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.', 'wp-super-cache' ) . '

    '; echo '

    ' . __( 'In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.', 'wp-super-cache' ) . '

    '; echo '
    '; echo ''; echo ''; echo '

    ' . sprintf( __( 'Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)', 'wp-super-cache' ), "", $min_refresh_interval ) . '

    '; if ( $count > 100 ) { $step = (int)( $count / 10 ); $select = ""; echo '

    ' . sprintf( __( 'Preload %s posts.', 'wp-super-cache' ), $select ) . '

    '; } else { echo ''; } echo ' ' . __( 'Preload mode (garbage collection only on legacy cache files. Recommended.)', 'wp-super-cache' ) . '
    '; echo ' ' . __( 'Preload tags, categories and other taxonomies.', 'wp-super-cache' ) . '
    '; echo ' ' . __( 'Send me status emails when files are refreshed.', 'wp-super-cache' ) . '
    '; if ( !isset( $wp_cache_preload_email_volume ) ) $wp_cache_preload_email_volume = 'many'; echo '     ' . __( 'Many emails, 2 emails per 100 posts.', 'wp-super-cache' ) . '
    '; echo '     ' . __( 'Medium, 1 email per 100 posts.', 'wp-super-cache' ) . '
    '; echo '     ' . __( 'Less emails, 1 at the start and 1 at the end of preloading all posts.', 'wp-super-cache' ) . '
    '; $currently_preloading = false; next_preload_message( 'wp_cache_preload_hook', __( 'Refresh of cache in %d hours %d minutes and %d seconds.', 'wp-super-cache' ), 60 ); next_preload_message( 'wp_cache_full_preload_hook', __( 'Full refresh of cache in %d hours %d minutes and %d seconds.', 'wp-super-cache' ) ); $preload_counter = get_option( 'preload_cache_counter' ); if ( isset( $preload_counter[ 'first' ] ) ) // converted from int to array update_option( 'preload_cache_counter', array( 'c' => $preload_counter[ 'c' ], 't' => time() ) ); if ( is_array( $preload_counter ) && $preload_counter[ 'c' ] > 0 ) { echo '

    ' . sprintf( __( 'Currently caching from post %d to %d.', 'wp-super-cache' ), ( $preload_counter[ 'c' ] - 100 ), $preload_counter[ 'c' ] ) . '

    '; $currently_preloading = true; if ( @file_exists( $cache_path . "preload_permalink.txt" ) ) { $url = file_get_contents( $cache_path . "preload_permalink.txt" ); echo "

    " . sprintf( __( "Page last cached: %s", 'wp-super-cache' ), $url ) . "

    "; } } echo '
     '; if ( $currently_preloading ) { echo ' '; } echo '
    '; wp_nonce_field('wp-cache'); echo '
    '; } else { echo '

    ' . __( 'Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.', 'wp-super-cache' ) . '

    '; } break; case 'plugins': wpsc_plugins_tab(); break; case 'debug': wp_cache_debug_settings(); break; case 'settings': if ( isset( $wp_cache_front_page_checks ) == false ) $wp_cache_front_page_checks = true; echo '
    '; wp_nonce_field('wp-cache'); echo ''; ?>





    "; ?>
    "; echo "

    " . __( 'Warning! 304 browser caching is only supported when mod_rewrite caching is not used.', 'wp-super-cache' ) . "

    "; } else { ?>


    ' . __( 'Mobile Browsers', 'wp-super-cache' ) . '

    ' . implode( ', ', $wp_cache_mobile_browsers ) . "

    " . __( 'Mobile Prefixes', 'wp-super-cache' ) . "

    " . implode( ', ', $wp_cache_mobile_prefixes ) . "
    "; } ?>

    (" . __( "Recommended", "wp-super-cache" ) . ")"; ?>




    DO NOT CACHE PAGE secret key: %s', 'wp-super-cache' ), trailingslashit( get_bloginfo( 'url' ) ) . "?donotcachepage={$cache_page_secret}", $cache_page_secret ); ?>

      5. strlen( ABSPATH ) && ABSPATH == substr( $cache_path, 0, strlen( ABSPATH ) ) ) { $msg = __( 'The plugin detected a bare directory index in your cache directory, which would let visitors see your cache files directly and might expose private posts.', 'wp-super-cache' ); if ( $super_cache_enabled && $wp_cache_mod_rewrite == 1 ) { $msg .= ' ' . __( 'You are using mod_rewrite to serve cache files so the plugin has added Options -Indexes to the .htaccess file in the cache directory to disable indexes. However, if that does not work, you should contact your system administrator or support and ask for them to be disabled, or use PHP mode and move the cache outside of the web root.' ); } else { $msg .= ' ' . sprintf( __( 'index.html files have been added in key directories, but unless directory indexes are disabled, it is probably better to store the cache files outside of the web root of %s' ), ABSPATH ) . ''; } echo "
    5. $msg
      6. "; } ?>
    6. %s and update the mod_rewrite rules in the .htaccess file.', 'wp-super-cache' ), ABSPATH ); ?>

    2. %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable is probably a good idea!)', 'wp-super-cache' ), WP_CONTENT_DIR ); ?>
    3. readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".', 'wp-super-cache' ), WP_PLUGIN_URL ); ?>
      4. " . sprintf( __( 'Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.', 'wp-super-cache' ), 'http://wordpress.org/plugins/wp-super-cache/', 'http://wordpress.org/tags/wp-super-cache?forum_id=10' ) . ""; echo "
    "; echo "
    "; wp_nonce_field('wp-cache'); ?>

    ' . __( 'Accepted Filenames & Rejected URIs', 'wp-super-cache' ) . '

    '; wp_cache_edit_rejected_pages(); echo "\n"; wp_cache_edit_rejected(); echo "\n"; wp_cache_edit_accepted(); echo '
    '; wp_cache_edit_rejected_ua(); wp_lock_down(); wp_cache_restore(); break; case "easy": default: echo '
    '; echo ''; wp_nonce_field('wp-cache'); ?>
    " . __( 'Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok, please ignore this message. Otherwise, you can edit the .htaccess file in the root of your install and remove the SuperCache rules.', 'wp-super-cache' ) . '

    '; } } echo "
    "; if ( $cache_enabled ) { echo "

    " . __( 'Cache Tester', 'wp-super-cache' ) . "

    "; echo '

    ' . __( 'Test your cached website by clicking the test button below.', 'wp-super-cache' ) . '

    '; if ( array_key_exists('action', $_POST) && $_POST[ 'action' ] == 'test' && $valid_nonce ) { $url = trailingslashit( get_bloginfo( 'url' ) ); if ( isset( $_POST[ 'httponly' ] ) ) $url = str_replace( 'https://', 'http://', $url ); // Prime the cache echo "

    " . sprintf( __( 'Fetching %s to prime cache: ', 'wp-super-cache' ), $url ); $page = wp_remote_get( $url, array('timeout' => 60, 'blocking' => true ) ); echo '' . __( 'OK', 'wp-super-cache' ) . '

    '; sleep( 1 ); // Get the first copy echo "

    " . sprintf( __( 'Fetching first copy of %s: ', 'wp-super-cache' ), $url ); $page = wp_remote_get( $url, array('timeout' => 60, 'blocking' => true ) ); if ( !is_wp_error( $page ) ) { $fp = fopen( $cache_path . "1.html", "w" ); fwrite( $fp, $page[ 'body' ] ); fclose( $fp ); echo '' . __( 'OK', 'wp-super-cache' ) . " (1.html)

    "; sleep( 1 ); } else { echo '' . __( 'FAILED', 'wp-super-cache' ) . "

    "; } // Get the second copy echo "

    " . sprintf( __( 'Fetching second copy of %s: ', 'wp-super-cache' ), $url ); $page2 = wp_remote_get( $url, array('timeout' => 60, 'blocking' => true ) ); if ( !is_wp_error( $page2 ) ) { $fp = fopen( $cache_path . "2.html", "w" ); fwrite( $fp, $page2[ 'body' ] ); fclose( $fp ); echo '' . __( 'OK', 'wp-super-cache' ) . " (2.html)

    "; } else { echo '' . __( 'FAILED', 'wp-super-cache' ) . "

    "; } if ( is_wp_error( $page ) || is_wp_error( $page2 ) || $page[ 'response' ][ 'code' ] != 200 || $page2[ 'response' ][ 'code' ] != 200 ) { echo '

    ' . __( 'One or more page requests failed:', 'wp-super-cache' ) . '

    '; $error = false; if ( is_wp_error( $page ) ) { $error = $page; } elseif ( is_wp_error( $page2 ) ) { $error = $page2; } if ( $error ) { $errors = ''; $messages = ''; foreach ( $error->get_error_codes() as $code ) { $severity = $error->get_error_data($code); foreach ( $error->get_error_messages( $code ) as $err ) { $errors .= ' ' . $err . "
    \n"; } } if ( !empty($err) ) echo '
    ' . $errors . "
    \n"; } else { echo '
    • ' . sprintf( __( 'Page %d: %d (%s)', 'wp-super-cache' ), 1, $page[ 'response' ][ 'code' ], $page[ 'response' ][ 'message' ] ) . '
      • '; echo '
    • ' . sprintf( __( 'Page %d: %d (%s)', 'wp-super-cache' ), 2, $page2[ 'response' ][ 'code' ], $page2[ 'response' ][ 'message' ] ) . '
    '; } } if ( ( !is_wp_error( $page ) && !is_wp_error( $page2 ) ) && preg_match( '/(Cached page generated by WP-Super-Cache on) ([0-9]*-[0-9]*-[0-9]* [0-9]*:[0-9]*:[0-9]*)/', $page[ 'body' ], $matches1 ) && preg_match( '/(Cached page generated by WP-Super-Cache on) ([0-9]*-[0-9]*-[0-9]* [0-9]*:[0-9]*:[0-9]*)/', $page2[ 'body' ], $matches2 ) && $matches1[2] == $matches2[2] ) { echo '

    ' . sprintf( __( 'Page 1: %s', 'wp-super-cache' ), $matches1[ 2 ] ) . '

    '; echo '

    ' . sprintf( __( 'Page 2: %s', 'wp-super-cache' ), $matches2[ 2 ] ) . '

    '; echo '

    ' . __( 'The timestamps on both pages match!', 'wp-super-cache' ) . '

    '; } else { echo '

    ' . __( 'The pages do not match! Timestamps differ or were not found!', 'wp-super-cache' ) . '

    '; echo '

    ' . __( 'Things you can do:', 'wp-super-cache' ) . '

    '; echo '
    1. ' . __( 'Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match.', 'wp-super-cache' ) . '
      2. '; echo '
    2. ' . __( 'Enable logging on the Debug page here. That should help you track down the problem.', 'wp-super-cache' ) . '
      3. '; echo '
    3. ' . __( 'You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.', 'wp-super-cache' ) . '
      4. '; echo "
    "; } } echo '
    '; echo ''; if ( isset( $_SERVER['HTTPS' ] ) && 'on' == strtolower( $_SERVER['HTTPS' ] ) ) echo " " . __( 'Send non-secure (non https) request for homepage', 'wp-super-cache' ); echo '
    '; wp_nonce_field('wp-cache'); echo '
    '; } echo "

    " . __( "Delete Cached Pages", 'wp-super-cache' ) . "

    "; echo "

    " . __( "Cached pages are stored on your server as html and PHP files. If you need to delete them, use the button below.", 'wp-super-cache' ) . "

    "; echo '
    '; echo ''; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; if ( ( defined( 'VHOST' ) || defined( 'SUBDOMAIN_INSTALL' ) || defined( 'SUNRISE' ) || ( defined( 'WP_ALLOW_MULTISITE' ) && constant( 'WP_ALLOW_MULTISITE' ) == true ) ) && wpsupercache_site_admin() ) { echo '
    '; echo ''; echo '
    '; wp_nonce_field('wp-cache'); echo "

    \n"; } ?>

  • Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.', 'wp-super-cache' ), 'http://developer.yahoo.com/yslow/', 'http://gtmetrix.com/' ); ?>
  • Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically, it may reduce your Yslow score.', 'wp-super-cache' ), 'http://wordpress.org/plugins/use-google-libraries/' ); ?>
  • Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.', 'wp-super-cache' ), 'http://wordpress.org/plugins/memcached/', 'http://neosmart.net/dl.php?id=12', 'http://neosmart.net/dl.php?id=13' ); ?>
  • Cron View is a useful plugin to use when trying to debug garbage collection and preload problems.', 'wp-super-cache' ), 'http://wordpress.org/plugins/cron-view/' ); ?>
    		•

    2. Installation Help', 'wp-super-cache' ), 'http://wordpress.org/plugins/wp-super-cache/installation/' ); ?>
    3. Frequently Asked Questions', 'wp-super-cache' ), 'http://wordpress.org/plugins/wp-super-cache/faq/' ); ?>
    4. Support Forum', 'wp-super-cache' ), 'http://wordpress.org/tags/wp-super-cache' ); ?>
    5. Development Version', 'wp-super-cache' ), 'http://ocaoimh.ie/y/2o' ); ?>

    rate this plugin and tell me if it works for you or not. It really helps development.', 'wp-super-cache' ), 'http://wordpress.org/plugins/wp-super-cache/' ); ?>

    %2$s', 'wp-super-cache' ), date( 'M j, Y', $start_date ), number_format( get_option( 'wpsupercache_count' ) ) ); ?>

      " . substr( $url[ 'url' ], 0, 20 ) . "\n"; } ?>

    \n"; } function wpsc_plugins_tab() { echo '

    ' . __( 'Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.', 'wp-super-cache' ) . '

    '; echo '

    ' . __( 'This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.', 'wp-super-cache' ) . '

    '; echo '

    ' . __( 'Warning! Due to the way WordPress upgrades plugins, the plugins you upload to wp-super-cache/plugins/ will be deleted when you upgrade WP Super Cache. You can avoid this by loading the plugins from elsewhere. Set $wp_cache_plugins_dir to the new location in wp-config.php and WP Super Cache will look there instead.
    More info available in the developer documentation.', 'wp-super-cache' ) . '

    '; ob_start(); if( defined( 'WP_CACHE' ) ) { if( function_exists( 'do_cacheaction' ) ) { do_cacheaction( 'cache_admin_page' ); } } $out = ob_get_contents(); ob_end_clean(); if( SUBMITDISABLED == ' ' && $out != '' ) { echo '

    ' . __( 'Available Plugins', 'wp-super-cache' ) . '

    '; echo "
      "; echo $out; echo "
    "; } } function wpsc_admin_tabs( $current = 0 ) { global $wp_db_version; if ( $current == 0 ) { if ( isset( $_GET[ 'tab' ] ) ) { $current = $_GET[ 'tab' ]; } else { $current = 'easy'; } } $tabs = array( 'easy' => __( 'Easy', 'wp-super-cache' ), 'settings' => __( 'Advanced', 'wp-super-cache' ), 'cdn' => __( 'CDN', 'wp-super-cache' ), 'contents' => __( 'Contents', 'wp-super-cache' ), 'preload' => __( 'Preload', 'wp-super-cache' ), 'plugins' => __( 'Plugins', 'wp-super-cache' ), 'debug' => __( 'Debug', 'wp-super-cache' ) ); $links = array(); foreach( $tabs as $tab => $name ) { if ( $current == $tab ) { $links[] = "$name"; } else { $links[] = "$name"; } } if ( $wp_db_version >= 15477 ) { echo ''; } else { echo implode( " | ", $links ); } } function wsc_mod_rewrite() { global $cache_enabled, $super_cache_enabled, $valid_nonce, $cache_path, $wp_cache_mod_rewrite, $wpmu_version; if ( defined( 'WPSC_DISABLE_HTACCESS_UPDATE' ) ) return false; if ( !$wp_cache_mod_rewrite ) return false; if ( isset( $wpmu_version ) || function_exists( 'is_multisite' ) && is_multisite() ) { if ( false == wpsupercache_site_admin() ) return false; if ( function_exists( "is_main_site" ) && false == is_main_site() ) { global $current_site; $protocol = ( 'on' == strtolower( $_SERVER['HTTPS' ] ) ) ? 'https://' : 'http://'; if ( isset( $wpmu_version ) ) { $link_to_admin = admin_url( "wpmu-admin.php?page=wpsupercache" ); } else { $link_to_admin = admin_url( "ms-admin.php?page=wpsupercache" ); } echo '

    ' . sprintf( __( 'Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.', 'wp-super-cache' ), $link_to_admin ) . '

    '; return false; } } if ( function_exists( "is_main_site" ) && false == is_main_site() ) return true; ?>

    " . __( 'WordPress MU Detected', 'wp-super-cache' ) . "

    " . __( "Unfortunately, the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.", 'wp-super-cache' ) . "

    "; } elseif( !$wprules || $wprules == '' ) { echo "

    " . __( 'Mod Rewrite rules cannot be updated!', 'wp-super-cache' ) . "

    "; echo "

    " . sprintf( __( "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:", 'wp-super-cache' ), $home_path ); echo "

    # BEGIN WordPress\n RewriteCond %{REQUEST_FILENAME} !-f\n RewriteCond %{REQUEST_FILENAME} !-d\n RewriteRule . /index.php [L]\n # END WordPress
    "; _e( 'Refresh this page when you have updated your .htaccess file.', 'wp-super-cache' ); echo "
    "; $dohtaccess = false; } elseif( strpos( $wprules, 'wordpressuser' ) ) { // Need to clear out old mod_rewrite rules echo "

    " . __( 'Thank you for upgrading.', 'wp-super-cache' ) . " " . sprintf( __( 'The mod_rewrite rules changed since you last installed this plugin. Unfortunately, you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.', 'wp-super-cache' ), '

    RewriteCond %{HTTP_COOKIE} !^.*wordpressuser.*$
    ', '
    RewriteCond %{HTTP:Cookie} !^.*wordpress.*$
    ' ) . "

    "; echo "
    "; return; } elseif( $scrules != '' && strpos( $scrules, '%{REQUEST_URI} !^.*[^/]$' ) === false && substr( get_option( 'permalink_structure' ), -1 ) == '/' ) { // permalink structure has a trailing slash, need slash check in rules. echo "

    " . __( 'Trailing slash check required.', 'wp-super-cache' ) . "

    " . __( 'It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:', 'wp-super-cache' ) . "

    "; echo "
    RewriteCond %{REQUEST_URI} !^.*[^/]$RewriteCond %{REQUEST_URI} !^.*//.*$
    "; echo "

    " . __( 'You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.', 'wp-super-cache' ) . "

    "; $dohtaccess = false; } elseif( strpos( $scrules, 'supercache' ) || strpos( $wprules, 'supercache' ) ) { // only write the rules once $dohtaccess = false; } if ( $dohtaccess && !isset( $_POST[ 'updatehtaccess' ] ) ){ if ( $scrules == '' ) { wpsc_update_htaccess_form( 0 ); // don't hide the update htaccess form } else { wpsc_update_htaccess_form(); } } elseif ( $valid_nonce && isset( $_POST[ 'updatehtaccess' ] ) ) { echo "
    "; if( wpsc_update_htaccess() ) { echo "

    " . __( 'Mod Rewrite rules updated!', 'wp-super-cache' ) . "

    "; echo "

    " . sprintf( __( '%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:', 'wp-super-cache' ), $home_path ) . "

    \n"; } else { echo "

    " . __( 'Mod Rewrite rules must be updated!', 'wp-super-cache' ) . "

    "; echo "

    " . sprintf( __( 'Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:', 'wp-super-cache' ), $home_path ) . "

    \n"; } echo "

    " . esc_html( $rules ) . "

    \n
    "; } else { ?>

    Click the following link to see the lines added to that file. If you have upgraded the plugin, make sure these rules match.', 'wp-super-cache' ), $home_path ); ?>

    "; if ( $rules != $scrules ) echo '
    ' . wp_text_diff( $scrules, $rules, array( 'title' => 'Rewrite Rules', 'title_left' => 'Current Rules', 'title_right' => 'New Rules' ) ) . "
    "; echo "

    # BEGIN WPSuperCache\n" . esc_html( $rules ) . "# END WPSuperCache

    \n"; echo "

    " . sprintf( __( 'Rules must be added to %s too:', 'wp-super-cache' ), WP_CONTENT_DIR . "/cache/.htaccess" ) . "

    "; echo "
    # BEGIN supercache\n" . esc_html( $gziprules ) . "# END supercache

    "; echo ''; } // http://allmybrain.com/2007/11/08/making-wp-super-cache-gzip-compression-work/ $gziprules = insert_with_markers( $cache_path . '.htaccess', 'supercache', explode( "\n", $gziprules ) ); echo "

    " . sprintf( __( 'Gzip encoding rules in %s.htaccess created.', 'wp-super-cache' ), $cache_path ) . "

    "; ?>

    ' . __( 'Fix Configuration', 'wp-super-cache' ) . '

    '; echo '
    '; echo ''; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; echo ''; } function comment_form_lockdown_message() { ?>

    ' . __( 'Disabled', 'wp-super-cache' ) . '' : '' . __( 'Enabled', 'wp-super-cache' ) . ''; ?>

    if( defined( 'WPLOCKDOWN' ) && constant( 'WPLOCKDOWN' ) ) {     echo ""; }

    '; echo ""; echo "
    "; wp_nonce_field('wp-cache'); echo "\n"; ?>

    \'\"\r\n\t\(\)]/', '', $_POST['deletepage'] ) ) . '/'; $pagefile = realpath( ABSPATH . $page . 'index.html' ); if ( substr( $pagefile, 0, strlen( ABSPATH ) ) != ABSPATH || false == wp_cache_confirm_delete( ABSPATH . $page ) ) { die( __( 'Cannot delete directory', 'wp-super-cache' ) ); } $firstfolder = explode( '/', $page ); $firstfolder = ABSPATH . $firstfolder[1]; $page = ABSPATH . $page; if( is_file( $pagefile ) && is_writeable_ACLSafe( $pagefile ) && is_writeable_ACLSafe( $firstfolder ) ) { @unlink( $pagefile ); @unlink( $pagefile . '.gz' ); RecursiveFolderDelete( $firstfolder ); echo "" . sprintf( __( '%s removed!', 'wp-super-cache' ), $pagefile ) . ""; prune_super_cache( $cache_path, true ); } } $readonly = ''; if( !is_writeable_ACLSafe( ABSPATH ) ) { $readonly = 'READONLY'; ?>

    '; if( is_array( $cached_direct_pages ) ) { $out = ''; foreach( $cached_direct_pages as $page ) { if( $page == '' ) continue; $generated = ''; if( is_file( ABSPATH . $page . '/index.html' ) ) $generated = ''; $out .= "$generated"; } if( $out != '' ) { ?>"; } } if( $readonly != 'READONLY' ) echo __( "Add direct page:", 'wp-super-cache' ) . ""; echo "

    " . sprintf( __( "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.", 'wp-super-cache' ), ABSPATH ) . "

    "; if( $readonly != 'READONLY' ) { echo "

    " . sprintf( __( 'For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.', 'wp-super-cache' ), trailingslashit( get_option( 'siteurl' ) ) ) . "

    "; echo "

    " . __( 'Make the textbox blank to remove it from the list of direct pages and delete the cached file.', 'wp-super-cache' ) . "

    "; } wp_nonce_field('wp-cache'); if( $readonly != 'READONLY' ) echo "
    "; echo "\n"; ?>

    UTC time is %s'), date_i18n($timezone_format, false, 'gmt')); ?>%1$s'), date_i18n($timezone_format)); ?>" . sprintf( __( 'Next scheduled garbage collection will be at %s UTC', 'wp-super-cache' ), date_i18n( $timezone_format, $next_gc, 'gmt' ) ) . "

    "; if ( $wp_cache_preload_on ) echo "

    " . __( 'Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age.' ) . "

    "; echo ""; echo '
    '; echo ''; echo '
    '; echo ''; echo "\n"; echo "\n"; echo ''; echo ''; echo "\n"; echo "
    " . __( "seconds", 'wp-super-cache' ) . "
    " . __( 'How long should cached pages remain fresh? Set to 0 to disable garbage collection. A good starting point is 3600 seconds.', 'wp-super-cache' ) . "
    ' . __( 'Scheduler', 'wp-super-cache' ) . ''; echo ""; echo ''; echo ""; $schedules = wp_get_schedules(); echo ""; echo '
    " . __( "seconds", 'wp-super-cache' ) . '
    ' . __( 'Check for stale cached files every interval seconds.', 'wp-super-cache' ) . "
    " . __( "HH:MM", 'wp-super-cache' ) . "
    " . __( 'Check for stale cached files at this time (UTC) or starting at this time every interval below.', 'wp-super-cache' ) . "

    " . __( 'Email me when the garbage collection runs.', 'wp-super-cache' ) . "
    \n"; echo "

    " . __( 'Garbage Collection', 'wp-super-cache' ) . "

    "; echo "
    1. " . __( 'Garbage collection is the simple act of throwing out your garbage. For this plugin that would be old or stale cached files that may be out of date. New cached files are described as fresh.', 'wp-super-cache' ) . "
      2. \n"; echo "
    2. " . __( 'Cached files are fresh for a limited length of time. You can set that time in the Cache Timeout text box on this page.', 'wp-super-cache' ) . "
      3. \n"; echo "
    3. " . __( 'Stale cached files are not removed as soon as they become stale. They have to be removed by the garbage collecter. That is why you have to tell the plugin when the garbage collector should run.', 'wp-super-cache' ) . "
      4. \n"; echo "
    4. " . __( 'Use the Timer or Clock schedulers to define when the garbage collector should run.', 'wp-super-cache' ) . "
      5. \n"; echo "
    5. " . __( 'The Timer scheduler tells the plugin to run the garbage collector at regular intervals. When one garbage collection is done, the next run is scheduled.', 'wp-super-cache' ) . "
      6. \n"; echo "
    6. " . __( 'Or, the Clock scheduler allows the garbage collection to run at specific times. If set to run hourly or twice daily, the garbage collector will be first scheduled for the time you enter here. It will then run again at the indicated interval. If set to run daily, it will run once a day at the time specified.', 'wp-super-cache' ) . "
      7. \n"; echo "
    "; echo "

    " . __( 'There are no best garbage collection settings but here are a few scenarios. Garbage collection is separate to other actions that clear our cached files like leaving a comment or publishing a post.', 'wp-super-cache' ) . "

    \n"; echo "
      "; echo "
    1. " . __( 'Sites that want to serve lots of newly generated data should set the Cache Timeout to 60 and use the Timer scheduler set to 90 seconds.', 'wp-super-cache' ) . "
      2. \n"; echo "
    2. " . __( 'Sites with widgets and rss feeds in their sidebar should probably use a timeout of 3600 seconds and set the timer to 600 seconds. Stale files will be caught within 10 minutes of going stale.', 'wp-super-cache' ) . "
      3. \n"; echo "
    3. " . __( 'Sites with lots of static content, no widgets or rss feeds in their sidebar can use a timeout of 86400 seconds or even more and set the timer to something equally long.', 'wp-super-cache' ) . "
      4. \n"; echo "
    4. " . __( 'Sites where an external data source updates at a particular time every day should set the timeout to 86400 seconds and use the Clock scheduler set appropriately.', 'wp-super-cache' ) . "
      5. \n"; echo "
    "; echo "

    " . __( 'Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site, you should set the expiry time to 600 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching, aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.', 'wp-super-cache' ) . "

    "; echo "

    " . __( 'Set the expiry time to 0 seconds to disable garbage collection.', 'wp-super-cache' ) . "

    "; echo '
    '; wp_nonce_field('wp-cache'); echo "\n"; ?>
    $ua ) { $cache_rejected_user_agent[ $k ] = str_replace( '___', ' ', $ua ); } reset( $cache_rejected_user_agent ); } echo '

    ' . __( 'Rejected User Agents', 'wp-super-cache' ) . '

    '; echo "

    " . __( 'Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.', 'wp-super-cache' ) . "

    \n"; echo '
    '; echo ' '; echo '
    '; wp_nonce_field('wp-cache'); echo '
    '; echo "
    \n"; } function wp_cache_edit_rejected_pages() { global $wp_cache_config_file, $valid_nonce, $wp_cache_pages; if ( isset( $_POST[ 'wp_edit_rejected_pages' ] ) && $valid_nonce ) { $pages = array( 'single', 'pages', 'archives', 'tag', 'frontpage', 'home', 'category', 'feed', 'author', 'search' ); foreach( $pages as $page ) { if ( isset( $_POST[ 'wp_cache_pages' ][ $page ] ) ) { $value = 1; } else { $value = 0; } wp_cache_replace_line('^ *\$wp_cache_pages\[ "' . $page . '" \]', "\$wp_cache_pages[ \"{$page}\" ] = $value;", $wp_cache_config_file); $wp_cache_pages[ $page ] = $value; } } echo ''; echo '

    ' . __( 'Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.', 'wp-super-cache' ) . '

    '; echo '
    '; echo ''; echo '
    '; echo '
    '; echo '
    '; echo '  
    '; echo '
    '; echo '  
    '; echo '  
    '; echo '
    '; echo '
    '; echo '
    '; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; } function wp_cache_edit_rejected() { global $cache_acceptable_files, $cache_rejected_uri, $wp_cache_config_file, $valid_nonce; if(isset($_REQUEST['wp_rejected_uri']) && $valid_nonce) { $text = wp_cache_sanitize_value( str_replace( '\\\\', '\\', $_REQUEST['wp_rejected_uri'] ), $cache_rejected_uri ); wp_cache_replace_line('^ *\$cache_rejected_uri', "\$cache_rejected_uri = $text;", $wp_cache_config_file); } echo ''; echo '
    '; echo "

    " . __( 'Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.', 'wp-super-cache' ) . "

    \n"; echo ' '; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; } function wp_cache_edit_accepted() { global $cache_acceptable_files, $cache_rejected_uri, $wp_cache_config_file, $valid_nonce; if(isset($_REQUEST['wp_accepted_files']) && $valid_nonce) { $text = wp_cache_sanitize_value($_REQUEST['wp_accepted_files'], $cache_acceptable_files); wp_cache_replace_line('^ *\$cache_acceptable_files', "\$cache_acceptable_files = $text;", $wp_cache_config_file); } echo ''; echo '
    '; echo "

    " . __( 'Add here those filenames that can be cached, even if they match one of the rejected substring specified above.', 'wp-super-cache' ) . "

    \n"; echo ' '; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; } function wp_cache_debug_settings() { global $wp_super_cache_debug, $wp_cache_debug_log, $wp_cache_debug_ip, $cache_path, $valid_nonce, $wp_cache_config_file, $wp_super_cache_comments; global $wp_super_cache_front_page_check, $wp_super_cache_front_page_clear, $wp_super_cache_front_page_text, $wp_super_cache_front_page_notification, $wp_super_cache_advanced_debug; if ( false == isset( $wp_super_cache_comments ) ) $wp_super_cache_comments = 1; if ( isset( $_POST[ 'wp_cache_debug' ] ) && $valid_nonce ) { if ( !isset( $_POST[ 'wp_super_cache_debug' ] ) ) $_POST[ 'wp_super_cache_debug' ] = 0; $wp_super_cache_debug = intval( $_POST[ 'wp_super_cache_debug' ] ); wp_cache_replace_line('^ *\$wp_super_cache_debug', "\$wp_super_cache_debug = '$wp_super_cache_debug';", $wp_cache_config_file); if ( $wp_super_cache_debug && ( ( isset( $wp_cache_debug_log ) && $wp_cache_debug_log == '' ) || !isset( $wp_cache_debug_log ) ) ) { $wp_cache_debug_log = md5( time() ) . ".txt"; } else { $wp_cache_debug_log = ""; } wp_cache_replace_line('^ *\$wp_cache_debug_log', "\$wp_cache_debug_log = '$wp_cache_debug_log';", $wp_cache_config_file); $wp_super_cache_comments = isset( $_POST[ 'wp_super_cache_comments' ] ) ? 1 : 0; wp_cache_replace_line('^ *\$wp_super_cache_comments', "\$wp_super_cache_comments = '$wp_super_cache_comments';", $wp_cache_config_file); $wp_cache_debug_ip = esc_html( $_POST[ 'wp_cache_debug_ip' ] ); wp_cache_replace_line('^ *\$wp_cache_debug_ip', "\$wp_cache_debug_ip = '$wp_cache_debug_ip';", $wp_cache_config_file); $wp_super_cache_front_page_check = isset( $_POST[ 'wp_super_cache_front_page_check' ] ) ? 1 : 0; wp_cache_replace_line('^ *\$wp_super_cache_front_page_check', "\$wp_super_cache_front_page_check = '$wp_super_cache_front_page_check';", $wp_cache_config_file); $wp_super_cache_front_page_clear = isset( $_POST[ 'wp_super_cache_front_page_clear' ] ) ? 1 : 0; wp_cache_replace_line('^ *\$wp_super_cache_front_page_clear', "\$wp_super_cache_front_page_clear = '$wp_super_cache_front_page_clear';", $wp_cache_config_file); $wp_super_cache_front_page_text = esc_html( $_POST[ 'wp_super_cache_front_page_text' ] ); wp_cache_replace_line('^ *\$wp_super_cache_front_page_text', "\$wp_super_cache_front_page_text = '$wp_super_cache_front_page_text';", $wp_cache_config_file); $wp_super_cache_front_page_notification = isset( $_POST[ 'wp_super_cache_front_page_notification' ] ) ? 1 : 0; wp_cache_replace_line('^ *\$wp_super_cache_front_page_notification', "\$wp_super_cache_front_page_notification = '$wp_super_cache_front_page_notification';", $wp_cache_config_file); if ( $wp_super_cache_front_page_check == 1 && !wp_next_scheduled( 'wp_cache_check_site_hook' ) ) { wp_schedule_single_event( time() + 360 , 'wp_cache_check_site_hook' ); wp_cache_debug( 'scheduled wp_cache_check_site_hook for 360 seconds time.', 2 ); } } echo ''; echo '
    '; if ( isset( $wp_cache_debug_log ) && $wp_cache_debug_log != '' ) echo "

    " . sprintf( __( 'Currently logging to: %s', 'wp-super-cache' ), "$cache_path{$wp_cache_debug_log}" ) . "

    "; echo '

    ' . __( 'Fix problems with the plugin by debugging it here. It can log them to a file in your cache directory.', 'wp-super-cache' ) . '

    '; echo '
    '; echo "
    "; echo ""; echo ""; echo ""; echo ""; echo "
    " . __( 'Debugging', 'wp-super-cache' ) . " " . __( 'enabled', 'wp-super-cache' ) . "
    " . __( 'IP Address', 'wp-super-cache' ) . " " . sprintf( __( '(only log requests from this IP address. Your IP is %s)', 'wp-super-cache' ), $_SERVER[ 'REMOTE_ADDR' ] ) . "
    " . __( 'Cache Status Messages', 'wp-super-cache' ) . " " . __( 'enabled', 'wp-super-cache' ) . "
    "; echo __( 'Display comments at the end of every page like this:', 'wp-super-cache' ) . "
    "; echo "
    <!-- Dynamic page generated in 0.450 seconds. -->
<!-- Cached page generated by WP-Super-Cache on " . date( "Y-m-d H:i:s", time() ) . " -->
<!-- super cache -->
    \n"; if ( isset( $wp_super_cache_advanced_debug ) ) { echo "

    " . __( 'Advanced', 'wp-super-cache' ) . "

    " . __( 'In very rare cases two problems may arise on some blogs:

    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    ', 'wp-super-cache' ) . '

    '; echo "

    " . __( 'I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.', 'wp-super-cache' ) . "

    "; echo ""; echo ""; echo ""; echo ""; echo ""; echo "
    " . __( 'Check front page every 5 minutes.', 'wp-super-cache' ) . "
    " . __( 'Front page text', 'wp-super-cache' ) . " (" . __( 'Text to search for on your front page. If this text is missing, the cache will be cleared. Leave blank to disable.', 'wp-super-cache' ) . ")
    " . __( 'Clear cache on error.', 'wp-super-cache' ) . "
    " . __( 'Email the blog admin when checks are made. (useful for testing)', 'wp-super-cache' ) . "
    \n"; } echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; echo '
    '; } function wp_cache_enable() { global $wp_cache_config_file, $cache_enabled, $supercachedir; if(get_option('gzipcompression')) { echo "" . __( 'Error: GZIP compression is enabled. Disable it if you want to enable wp-cache.', 'wp-super-cache' ) . ""; return false; } if( wp_cache_replace_line('^ *\$cache_enabled', '$cache_enabled = true;', $wp_cache_config_file) ) { $cache_enabled = true; } wp_super_cache_enable(); } function wp_cache_disable() { global $wp_cache_config_file, $cache_enabled; wp_clear_scheduled_hook( 'wp_cache_check_site_hook' ); wp_clear_scheduled_hook( 'wp_cache_gc' ); wp_clear_scheduled_hook( 'wp_cache_gc_watcher' ); if (wp_cache_replace_line('^ *\$cache_enabled', '$cache_enabled = false;', $wp_cache_config_file)) { $cache_enabled = false; } } function wp_super_cache_enable() { global $supercachedir, $wp_cache_config_file, $super_cache_enabled; if( is_dir( $supercachedir . ".disabled" ) ) if( is_dir( $supercachedir ) ) { prune_super_cache( $supercachedir . ".disabled", true ); @unlink( $supercachedir . ".disabled" ); } else { @rename( $supercachedir . ".disabled", $supercachedir ); } wp_cache_replace_line('^ *\$super_cache_enabled', '$super_cache_enabled = true;', $wp_cache_config_file); $super_cache_enabled = true; } function wp_super_cache_disable() { global $cache_path, $supercachedir, $wp_cache_config_file, $super_cache_enabled; wp_cache_replace_line('^ *\$super_cache_enabled', '$super_cache_enabled = false;', $wp_cache_config_file); if( is_dir( $supercachedir ) ) @rename( $supercachedir, $supercachedir . ".disabled" ); $super_cache_enabled = false; sleep( 1 ); // allow existing processes to write to the supercachedir and then delete it if (function_exists ('prune_super_cache') && is_dir( $supercachedir ) ) { prune_super_cache( $cache_path, true ); } } function wp_cache_is_enabled() { global $wp_cache_config_file; if(get_option('gzipcompression')) { echo "" . __( 'Warning', 'wp-super-cache' ) . ": " . __( "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.", 'wp-super-cache' ); return false; } $lines = file($wp_cache_config_file); foreach($lines as $line) { if (preg_match('/^ *\$cache_enabled *= *true *;/', $line)) return true; } return false; } function wp_cache_replace_line($old, $new, $my_file) { if ( @is_file( $my_file ) == false ) { return false; } if (!is_writeable_ACLSafe($my_file)) { echo "Error: file $my_file is not writable.\n"; return false; } $found = false; $lines = file($my_file); foreach( (array)$lines as $line ) { if ( preg_match("/$old/", $line)) { $found = true; break; } } if ($found) { $fd = fopen($my_file, 'w'); foreach( (array)$lines as $line ) { if ( !preg_match("/$old/", $line)) fputs($fd, $line); else { fputs($fd, "$new //Added by WP-Cache Manager\n"); } } fclose($fd); return true; } $fd = fopen($my_file, 'w'); $done = false; foreach( (array)$lines as $line ) { if ( $done || !preg_match('/^(if\ \(\ \!\ )?define|\$|\?>/', $line) ) { fputs($fd, $line); } else { fputs($fd, "$new //Added by WP-Cache Manager\n"); fputs($fd, $line); $done = true; } } fclose($fd); return true; } function wp_cache_remove_index() { global $cache_path; @unlink( $cache_path . "index.html" ); @unlink( $cache_path . "supercache/index.html" ); @unlink( $cache_path . "blogs/index.html" ); if ( is_dir( $cache_path . "blogs" ) ) { $dir = new DirectoryIterator( $cache_path . "blogs" ); foreach( $dir as $fileinfo ) { if ( $fileinfo->isDot() ) { continue; } if ( $fileinfo->isDir() ) { $directory = $cache_path . "blogs/" . $fileinfo->getFilename(); if ( is_file( $directory . "/index.html" ) ) { unlink( $directory . "/index.html" ); } if ( is_dir( $directory . "/meta" ) ) { if ( is_file( $directory . "/meta/index.html" ) ) { unlink( $directory . "/index.html" ); } } } } } } function wp_cache_index_notice() { global $current_user, $wp_version, $wp_cache_not_logged_in, $cache_path; if ( false == wpsupercache_site_admin() ) return false; if ( false == get_site_option( 'wp_super_cache_index_detected' ) ) return false; if ( strlen( $cache_path ) < strlen( ABSPATH ) || ABSPATH != substr( $cache_path, 0, strlen( ABSPATH ) ) ) return false; // cache stored outside web root if ( get_site_option( 'wp_super_cache_index_detected' ) == 2 ) { update_site_option( 'wp_super_cache_index_detected', 3 ); echo "
    "; echo "

    " . __( 'WP Super Cache Warning!', 'wp-super-cache' ) . '

    '; echo '

    ' . __( 'All users of this site have been logged out to refresh their login cookies.', 'wp-super-cache' ) . '

    '; echo '
    '; return false; } elseif ( get_site_option( 'wp_super_cache_index_detected' ) != 3 ) { echo "
    "; echo "

    " . __( 'WP Super Cache Warning!', 'wp-super-cache' ) . '

    '; echo '

    ' . __( 'Your server is configured to show files and directories, which may expose sensitive data such as login cookies to attackers in the cache directories. That has been fixed by adding a file named index.html to each directory. If you use PHP or legacy caching, consider moving the location of the cache directory on the Advanced Settings page.', 'wp-super-cache' ) . '

    '; echo "

    "; _e( 'If you just installed WP Super Cache for the first time, you can dismiss this message. Otherwise, you should probably refresh the login cookies of all logged in WordPress users here by clicking the logout link below.', 'wp-super-cache' ); echo "

    "; if ( -1 == version_compare( $wp_version, '4.0' ) ) { echo '

    ' . __( 'Your site is using a very old version of WordPress. When you update to the latest version everyone will be logged out and cookie information updated.', 'wp-super-cache' ) . '

    '; } else { echo '

    ' . __( 'The logout link will log out all WordPress users on this site except you. Your authentication cookie will be updated, but you will not be logged out.', 'wp-super-cache' ) . '

    '; } echo "" . __( 'Dismiss', 'wp-super-cache' ) . ""; if ( 1 == version_compare( $wp_version, '4.0' ) ) { echo " | " . __( 'Logout', 'wp-super-cache' ) . ""; } echo "
    "; ?> ID; WP_Session_Tokens::destroy_all_for_all_users(); wp_set_auth_cookie( $user_id, false, is_ssl() ); update_site_option( 'wp_super_cache_index_detected', 2 ); wp_redirect( admin_url() ); } } if ( isset( $_GET[ 'action' ] ) && $_GET[ 'action' ] == 'wpsclogout' ) add_action( 'admin_init', 'wp_cache_logout_all' ); function wp_cache_add_index_protection() { global $cache_path, $blog_cache_dir, $blogcacheid; if ( is_dir( $cache_path ) && false == is_file( "$cache_path/index.html" ) ) { $page = wp_remote_get( home_url( "/wp-content/cache/" ) ); if ( false == is_wp_error( $page ) ) { if ( false == get_site_option( 'wp_super_cache_index_detected' ) && $page[ 'response' ][ 'code' ] == 200 && stripos( $page[ 'body' ], 'index of' ) ) { add_site_option( 'wp_super_cache_index_detected', 1 ); // only show this once } } insert_with_markers( $cache_path . '.htaccess', "INDEX", array( 'Options -Indexes' ) ); } $directories = array( $cache_path, $cache_path . '/supercache/', $cache_path . '/blogs/', $blog_cache_dir, $blog_cache_dir . "/meta" ); foreach( $directories as $dir ) { if ( false == is_dir( $dir ) ) @mkdir( $dir ); if ( is_dir( $dir ) && false == is_file( "$dir/index.html" ) ) { $fp = @fopen( "$dir/index.html", 'w' ); if ( $fp ) fclose( $fp ); } } } function wp_cache_add_site_cache_index() { global $cache_path; wp_cache_add_index_protection(); // root and supercache if ( is_dir( $cache_path . "blogs" ) ) { $dir = new DirectoryIterator( $cache_path . "blogs" ); foreach( $dir as $fileinfo ) { if ( $fileinfo->isDot() ) { continue; } if ( $fileinfo->isDir() ) { $directory = $cache_path . "blogs/" . $fileinfo->getFilename(); if ( false == is_file( $directory . "/index.html" ) ) { $fp = @fopen( $directory . "/index.html", 'w' ); if ( $fp ) fclose( $fp ); } if ( is_dir( $directory . "/meta" ) ) { if ( false == is_file( $directory . "/meta/index.html" ) ) { $fp = @fopen( $directory . "/meta/index.html", 'w' ); if ( $fp ) fclose( $fp ); } } } } } } function wp_cache_verify_cache_dir() { global $cache_path, $blog_cache_dir, $blogcacheid; $dir = dirname($cache_path); if ( !file_exists($cache_path) ) { if ( !is_writeable_ACLSafe( $dir ) || !($dir = mkdir( $cache_path ) ) ) { echo "" . __( 'Error', 'wp-super-cache' ) . ": " . sprintf( __( 'Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions.', 'wp-super-cache' ), $dir ); return false; } } if ( !is_writeable_ACLSafe($cache_path)) { echo "" . __( 'Error', 'wp-super-cache' ) . ": " . sprintf( __( 'Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.', 'wp-super-cache' ), $cache_path, $dir ); return false; } if ( '/' != substr($cache_path, -1)) { $cache_path .= '/'; } if( false == is_dir( $blog_cache_dir ) ) { @mkdir( $cache_path . "blogs" ); if( $blog_cache_dir != $cache_path . "blogs/" ) @mkdir( $blog_cache_dir ); } if( false == is_dir( $blog_cache_dir . 'meta' ) ) @mkdir( $blog_cache_dir . 'meta' ); wp_cache_add_index_protection(); return true; } function wp_cache_verify_config_file() { global $wp_cache_config_file, $wp_cache_config_file_sample, $sem_id, $cache_path; global $WPSC_HTTP_HOST; $new = false; $dir = dirname($wp_cache_config_file); if ( file_exists($wp_cache_config_file) ) { $lines = join( ' ', file( $wp_cache_config_file ) ); if( strpos( $lines, 'WPCACHEHOME' ) === false ) { if( is_writeable_ACLSafe( $wp_cache_config_file ) ) { @unlink( $wp_cache_config_file ); } else { echo "" . __( 'Error', 'wp-super-cache' ) . ": " . sprintf( __( 'Your WP-Cache config file (%s) is out of date and not writable by the Web server. Please delete it and refresh this page.', 'wp-super-cache' ), $wp_cache_config_file ); return false; } } } elseif( !is_writeable_ACLSafe($dir)) { echo "" . __( 'Error', 'wp-super-cache' ) . ": " . sprintf( __( 'Configuration file missing and %1$s directory (%2$s) is not writable by the web server. Check its permissions.', 'wp-super-cache' ), WP_CONTENT_DIR, $dir ); return false; } if ( !file_exists($wp_cache_config_file) ) { if ( !file_exists($wp_cache_config_file_sample) ) { echo "" . __( 'Error', 'wp-super-cache' ) . ": " . sprintf( __( 'Sample WP-Cache config file (%s) does not exist. Verify your installation.', 'wp-super-cache' ), $wp_cache_config_file_sample ); return false; } copy($wp_cache_config_file_sample, $wp_cache_config_file); $dir = str_replace( str_replace( '\\', '/', WP_CONTENT_DIR ), '', str_replace( '\\', '/', dirname(__FILE__) ) ); if( is_file( dirname(__FILE__) . '/wp-cache-config-sample.php' ) ) { wp_cache_replace_line('define\(\ \'WPCACHEHOME', "\tdefine( 'WPCACHEHOME', WP_CONTENT_DIR . \"{$dir}/\" );", $wp_cache_config_file); } elseif( is_file( dirname(__FILE__) . '/wp-super-cache/wp-cache-config-sample.php' ) ) { wp_cache_replace_line('define\(\ \'WPCACHEHOME', "\tdefine( 'WPCACHEHOME', WP_CONTENT_DIR . \"{$dir}/wp-super-cache/\" );", $wp_cache_config_file); } $new = true; } if( $sem_id == 5419 && $cache_path != '' ) { $sem_id = crc32( $WPSC_HTTP_HOST . $cache_path ) & 0x7fffffff; wp_cache_replace_line('sem_id', '$sem_id = ' . $sem_id . ';', $wp_cache_config_file); } require($wp_cache_config_file); return true; } function wp_cache_create_advanced_cache() { global $wp_cache_link, $wp_cache_file; if ( file_exists( ABSPATH . 'wp-config.php') ) { $global_config_file = ABSPATH . 'wp-config.php'; } else { $global_config_file = dirname(ABSPATH) . '/wp-config.php'; } $line = 'define( \'WPCACHEHOME\', \'' . dirname( __FILE__ ) . '/\' );'; if ( !is_writeable_ACLSafe($global_config_file) || !wp_cache_replace_line('define *\( *\'WPCACHEHOME\'', $line, $global_config_file ) ) { echo '

    ' . __( 'Warning', 'wp-super-cache' ) . "! " . sprintf( __( 'Could not update %s! WPCACHEHOME must be set in config file.', 'wp-super-cache' ), $global_config_file ) . "

    "; return false; } $ret = true; $file = file_get_contents( $wp_cache_file ); $fp = @fopen( $wp_cache_link, 'w' ); if( $fp ) { fputs( $fp, $file ); fclose( $fp ); } else { $ret = false; } return $ret; } function wp_cache_check_link() { global $wp_cache_link, $wp_cache_file; $ret = true; if( file_exists($wp_cache_link) ) { $file = file_get_contents( $wp_cache_link ); if( strpos( $file, "WP SUPER CACHE 0.8.9.1" ) || strpos( $file, "WP SUPER CACHE 1.2" ) ) { return true; } else { if( !@unlink($wp_cache_link) ) { $ret = false; } else { $ret = wp_cache_create_advanced_cache(); } } } else { $ret = wp_cache_create_advanced_cache(); } if( false == $ret ) { echo '

    ' . __( 'Warning', 'wp-super-cache' ) . "! " . sprintf( __( '%s/advanced-cache.php does not exist or cannot be updated.', 'wp-super-cache' ), WP_CONTENT_DIR ) . "

    "; echo "

    "; echo sprintf( __( 'If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:', 'wp-super-cache' ), WP_CONTENT_DIR ) . "
      "; printf( __( '
    1. 1. Open %1$s$wp_cache_file in a text editor.
    2. 2. Change the text CACHEHOME to %2$s
    3. 3. Save the file and copy it to %3$s and refresh this page.
      4. ', 'wp-super-cache' ), $wp_cache_file, WPCACHEHOME, $wp_cache_link ); echo "
    "; return false; } return true; } function wp_cache_check_global_config() { global $wp_cache_check_wp_config; if ( !isset( $wp_cache_check_wp_config ) ) return true; if ( file_exists( ABSPATH . 'wp-config.php') ) { $global = ABSPATH . 'wp-config.php'; } else { $global = dirname(ABSPATH) . '/wp-config.php'; } $line = 'define(\'WP_CACHE\', true);'; if (!is_writeable_ACLSafe($global) || !wp_cache_replace_line('define *\( *\'WP_CACHE\'', $line, $global) ) { if ( defined( 'WP_CACHE' ) && constant( 'WP_CACHE' ) == false ) { echo '
    ' . __( "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately, it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    ", 'wp-super-cache' ) . "
    "; } else { echo "

    " . __( "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.", 'wp-super-cache' ) . "

    ";; echo "

    " . sprintf( __( "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. ", 'wp-super-cache' ), $global ) . "

    "; } return false; } else { echo "
    " . __( '

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the Troubleshooting Guide. The WP_CACHE line must be moved up.', 'wp-super-cache' ) . "

    "; } return true; } function wp_cache_files() { global $cache_path, $file_prefix, $cache_max_time, $valid_nonce, $supercachedir, $cache_enabled, $super_cache_enabled, $blog_cache_dir, $cache_compression; global $wp_cache_object_cache, $wp_cache_preload_on; if ( '/' != substr($cache_path, -1)) { $cache_path .= '/'; } if ( $valid_nonce ) { if(isset($_REQUEST['wp_delete_cache'])) { wp_cache_clean_cache($file_prefix); $_GET[ 'action' ] = 'regenerate_cache_stats'; } if ( isset( $_REQUEST[ 'wp_delete_all_cache' ] ) ) { wp_cache_clean_cache( $file_prefix, true ); $_GET[ 'action' ] = 'regenerate_cache_stats'; } if(isset($_REQUEST['wp_delete_expired'])) { wp_cache_clean_expired($file_prefix); $_GET[ 'action' ] = 'regenerate_cache_stats'; } } echo ""; echo '

    ' . __( 'Cache Contents', 'wp-super-cache' ) . '

    '; if ( $wp_cache_object_cache ) { echo "

    " . __( "Object cache in use. No cache listing available.", 'wp-super-cache' ) . "

    "; wp_cache_delete_buttons(); echo "
    "; return false; } $cache_stats = get_option( 'supercache_stats' ); if ( !is_array( $cache_stats ) || ( isset( $_GET[ 'listfiles' ] ) ) || ( $valid_nonce && array_key_exists('action', $_GET) && $_GET[ 'action' ] == 'regenerate_cache_stats' ) ) { $list_files = false; // it doesn't list supercached files, and removing single pages is buggy $count = 0; $expired = 0; $now = time(); if ( ( $handle = @opendir( $blog_cache_dir ) ) ) { $wp_cache_fsize = 0; if ( $valid_nonce && isset( $_GET[ 'action' ] ) && $_GET[ 'action' ] == 'deletewpcache' ) { $deleteuri = wpsc_deep_replace( array( '..', '\\', 'index.php' ), preg_replace( '/[ <>\'\"\r\n\t\(\)]/', '', base64_decode( $_GET[ 'uri' ] ) ) ); } else { $deleteuri = ''; } if ( $valid_nonce && isset( $_GET[ 'action' ] ) && $_GET[ 'action' ] == 'deletesupercache' ) { $supercacheuri = wpsc_deep_replace( array( '..', '\\', 'index.php' ), preg_replace( '/[ <>\'\"\r\n\t\(\)]/', '', preg_replace("/(\?.*)?$/", '', base64_decode( $_GET[ 'uri' ] ) ) ) ); $supercacheuri = trailingslashit( realpath( $cache_path . 'supercache/' . $supercacheuri ) ); if ( wp_cache_confirm_delete( $supercacheuri ) ) { printf( __( "Deleting supercache file: %s
    ", 'wp-super-cache' ), $supercacheuri ); @unlink( $supercacheuri . 'index.html' ); @unlink( $supercacheuri . 'index.html.gz' ); prune_super_cache( $supercacheuri . 'page', true ); @rmdir( $supercacheuri ); } } while( false !== ( $file = readdir( $handle ) ) ) { if ( strpos( $file, $file_prefix ) !== false && substr( $file, -4 ) == '.php' ) { if ( false == file_exists( $blog_cache_dir . 'meta/' . $file ) ) { @unlink( $blog_cache_dir . $file ); continue; // meta does not exist } $mtime = filemtime( $blog_cache_dir . 'meta/' . $file ); $fsize = @filesize( $blog_cache_dir . $file ); if ( $fsize > 0 ) $fsize = $fsize - 15; // die() command takes 15 bytes at the start of the file $age = $now - $mtime; if ( $valid_nonce && isset( $_GET[ 'listfiles' ] ) ) { $meta = json_decode( wp_cache_get_legacy_cache( $blog_cache_dir . 'meta/' . $file ), true ); if ( $deleteuri != '' && $meta[ 'uri' ] == $deleteuri ) { printf( __( "Deleting wp-cache file: %s
    ", 'wp-super-cache' ), esc_html( $deleteuri ) ); @unlink( $blog_cache_dir . 'meta/' . $file ); @unlink( $blog_cache_dir . $file ); continue; } $meta[ 'age' ] = $age; foreach( $meta as $key => $val ) $meta[ $key ] = esc_html( $val ); if ( $cache_max_time > 0 && $age > $cache_max_time ) { $expired_list[ $age ][] = $meta; } else { $cached_list[ $age ][] = $meta; } } if ( $cache_max_time > 0 && $age > $cache_max_time ) { $expired++; } else { $count++; } $wp_cache_fsize += $fsize; $fsize = intval($fsize/1024); } } closedir($handle); } if( $wp_cache_fsize != 0 ) { $wp_cache_fsize = $wp_cache_fsize/1024; } else { $wp_cache_fsize = 0; } if( $wp_cache_fsize > 1024 ) { $wp_cache_fsize = number_format( $wp_cache_fsize / 1024, 2 ) . "MB"; } elseif( $wp_cache_fsize != 0 ) { $wp_cache_fsize = number_format( $wp_cache_fsize, 2 ) . "KB"; } else { $wp_cache_fsize = '0KB'; } // Supercache files $now = time(); $sizes = array( 'expired' => 0, 'expired_list' => array(), 'cached' => 0, 'cached_list' => array(), 'ts' => 0 ); if (is_dir($supercachedir)) { if( $dh = opendir( $supercachedir ) ) { while( ( $entry = readdir( $dh ) ) !== false ) { if ($entry != '.' && $entry != '..') { $sizes = wpsc_dirsize( trailingslashit( $supercachedir ) . $entry, $sizes ); } } closedir($dh); } } else { $filem = @filemtime( $supercachedir ); if ( false == $wp_cache_preload_on && is_file( $supercachedir ) && $cache_max_time > 0 && $filem + $cache_max_time <= $now ) { $sizes[ 'expired' ] ++; if ( $valid_nonce && isset( $_GET[ 'listfiles' ] ) ) $sizes[ 'expired_list' ][ str_replace( $cache_path . 'supercache/' , '', $supercachedir ) ] = $now - $filem; } else { if ( $valid_nonce && isset( $_GET[ 'listfiles' ] ) && $filem ) $sizes[ 'cached_list' ][ str_replace( $cache_path . 'supercache/' , '', $supercachedir ) ] = $now - $filem; } } $sizes[ 'ts' ] = time(); $cache_stats = array( 'generated' => time(), 'supercache' => $sizes, 'wpcache' => array( 'cached' => $count, 'expired' => $expired, 'fsize' => $wp_cache_fsize ) ); update_option( 'supercache_stats', $cache_stats ); } else { echo "

    " . __( 'Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.', 'wp-super-cache' ) . "

    "; echo " 'wpsupercache', 'tab' => 'contents', 'action' => 'regenerate_cache_stats' ) ), 'wp-cache' ) . "'>" . __( 'Regenerate cache stats', 'wp-super-cache' ) . ""; if ( is_array( $cache_stats ) ) { echo "

    " . sprintf( __( 'Cache stats last generated: %s minutes ago.', 'wp-super-cache' ), number_format( ( time() - $cache_stats[ 'generated' ] ) / 60 ) ) . "

    "; } $cache_stats = get_option( 'supercache_stats' ); }// regerate stats cache if ( is_array( $cache_stats ) ) { echo "

    " . __( 'WP-Cache', 'wp-super-cache' ) . " ({$cache_stats[ 'wpcache' ][ 'fsize' ]})

    "; echo ""; $divisor = $cache_compression == 1 ? 2 : 1; if ( array_key_exists('fsize', (array)$cache_stats[ 'supercache' ]) ) $fsize = $cache_stats[ 'supercache' ][ 'fsize' ] / 1024; else $fsize = 0; if( $fsize > 1024 ) { $fsize = number_format( $fsize / 1024, 2 ) . "MB"; } elseif( $fsize != 0 ) { $fsize = number_format( $fsize, 2 ) . "KB"; } else { $fsize = "0KB"; } echo "

    " . __( 'WP-Super-Cache', 'wp-super-cache' ) . " ({$fsize})

    "; echo ""; if ( $valid_nonce && array_key_exists('listfiles', $_GET) && $_GET[ 'listfiles' ] ) { echo "
    "; if ( isset( $cached_list ) && is_array( $cached_list ) && !empty( $cached_list ) ) { echo "

    " . __( 'Fresh WP-Cached Files', 'wp-super-cache' ) . "

    "; echo ""; $c = 1; $flip = 1; ksort( $cached_list ); foreach( $cached_list as $age => $d ) { foreach( $d as $details ) { $bg = $flip ? 'style="background: #EAEAEA;"' : ''; echo "\n"; $flip = !$flip; $c++; } } echo "
    #" . __( 'URI', 'wp-super-cache' ) . "" . __( 'Key', 'wp-super-cache' ) . "" . __( 'Age', 'wp-super-cache' ) . "" . __( 'Delete', 'wp-super-cache' ) . "
    $c " . $details[ 'uri' ] . " " . str_replace( $details[ 'uri' ], '', $details[ 'key' ] ) . " {$age} 'wpsupercache', 'action' => 'deletewpcache', 'uri' => base64_encode( $details[ 'uri' ] ) ) ), 'wp-cache' ) . "#listfiles'>X
    "; } if ( isset( $expired_list ) && is_array( $expired_list ) && !empty( $expired_list ) ) { echo "

    " . __( 'Stale WP-Cached Files', 'wp-super-cache' ) . "

    "; echo ""; $c = 1; $flip = 1; ksort( $expired_list ); foreach( $expired_list as $age => $d ) { foreach( $d as $details ) { $bg = $flip ? 'style="background: #EAEAEA;"' : ''; echo "\n"; $flip = !$flip; $c++; } } echo "
    #" . __( 'URI', 'wp-super-cache' ) . "" . __( 'Key', 'wp-super-cache' ) . "" . __( 'Age', 'wp-super-cache' ) . "" . __( 'Delete', 'wp-super-cache' ) . "
    $c " . $details[ 'uri' ] . " " . str_replace( $details[ 'uri' ], '', $details[ 'key' ] ) . " {$age} 'wpsupercache', 'action' => 'deletewpcache', 'uri' => base64_encode( $details[ 'uri' ] ) ) ), 'wp-cache' ) . "#listfiles'>X
    "; } if ( is_array( $sizes[ 'cached_list' ] ) & !empty( $sizes[ 'cached_list' ] ) ) { echo "

    " . __( 'Fresh Super Cached Files', 'wp-super-cache' ) . "

    "; echo ""; $c = 1; $flip = 1; ksort( $sizes[ 'cached_list' ] ); foreach( $sizes[ 'cached_list' ] as $age => $d ) { foreach( $d as $uri => $n ) { $bg = $flip ? 'style="background: #EAEAEA;"' : ''; echo "\n"; $flip = !$flip; $c++; } } echo "
    #" . __( 'URI', 'wp-super-cache' ) . "" . __( 'Age', 'wp-super-cache' ) . "" . __( 'Delete', 'wp-super-cache' ) . "
    $c " . $uri . "$age 'wpsupercache', 'action' => 'deletesupercache', 'uri' => base64_encode( $uri ) ) ), 'wp-cache' ) . "#listfiles'>X
    "; } if ( is_array( $sizes[ 'expired_list' ] ) && !empty( $sizes[ 'expired_list' ] ) ) { echo "

    " . __( 'Stale Super Cached Files', 'wp-super-cache' ) . "

    "; echo ""; $c = 1; $flip = 1; ksort( $sizes[ 'expired_list' ] ); foreach( $sizes[ 'expired_list' ] as $age => $d ) { foreach( $d as $uri => $n ) { $bg = $flip ? 'style="background: #EAEAEA;"' : ''; echo "\n"; $flip = !$flip; $c++; } } echo "
    #" . __( 'URI', 'wp-super-cache' ) . "" . __( 'Age', 'wp-super-cache' ) . "" . __( 'Delete', 'wp-super-cache' ) . "
    $c " . $uri . "$age 'wpsupercache', 'action' => 'deletesupercache', 'uri' => base64_encode( $uri ) ) ), 'wp-cache' ) . "#listfiles'>X
    "; } echo "
    "; echo "

    " . __( 'Hide file list', 'wp-super-cache' ) . "

    "; } elseif ( $cache_stats[ 'supercache' ][ 'cached' ] > 500 || $cache_stats[ 'supercache' ][ 'expired' ] > 500 || ( $cache_stats[ 'wpcache' ][ 'cached' ] / $divisor ) > 500 || ( $cache_stats[ 'wpcache' ][ 'expired' ] / $divisor) > 500 ) { echo "

    " . __( 'Too many cached files, no listing possible.', 'wp-super-cache' ) . "

    "; } else { echo "

    'wpsupercache', 'listfiles' => '1' ) ), 'wp-cache' ) . "#listfiles'>" . __( 'List all cached files', 'wp-super-cache' ) . "

    "; } if ( $cache_max_time > 0 ) echo "

    " . sprintf( __( 'Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.', 'wp-super-cache' ), $cache_max_time ) . "

    "; } // cache_stats wp_cache_delete_buttons(); echo ''; } function wp_cache_delete_buttons() { echo '
    '; echo ''; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; echo '
    '; echo ''; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; if ( ( defined( 'VHOST' ) || defined( 'SUBDOMAIN_INSTALL' ) || defined( 'SUNRISE' ) || ( defined( 'WP_ALLOW_MULTISITE' ) && constant( 'WP_ALLOW_MULTISITE' ) == true ) ) && wpsupercache_site_admin() ) { echo '
    '; echo ''; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; } } function delete_cache_dashboard() { if ( false == wpsupercache_site_admin() ) return false; if ( function_exists('current_user_can') && !current_user_can('manage_options') ) return false; echo "
  • " . __( 'Delete Cache', 'wp-super-cache' ) . "
    • "; } add_action( 'dashmenu', 'delete_cache_dashboard' ); function wpsc_dirsize($directory, $sizes) { global $cache_max_time, $cache_path, $valid_nonce, $wp_cache_preload_on; $now = time(); if (is_dir($directory)) { if( $dh = opendir( $directory ) ) { while( ( $entry = readdir( $dh ) ) !== false ) { if ($entry != '.' && $entry != '..') { $sizes = wpsc_dirsize( trailingslashit( $directory ) . $entry, $sizes ); } } closedir($dh); } } else { if(is_file($directory) ) { $filem = filemtime( $directory ); if ( $wp_cache_preload_on == false && $cache_max_time > 0 && $filem + $cache_max_time <= $now ) { $sizes[ 'expired' ]+=1; if ( $valid_nonce && $_GET[ 'listfiles' ] ) $sizes[ 'expired_list' ][ $now - $filem ][ str_replace( $cache_path . 'supercache/' , '', str_replace( 'index.html', '', str_replace( 'index.html.gz', '', $directory ) ) ) ] = 1; } else { $sizes[ 'cached' ]+=1; if ( $valid_nonce && array_key_exists('listfiles', $_GET) && $_GET[ 'listfiles' ] ) $sizes[ 'cached_list' ][ $now - $filem ][ str_replace( $cache_path . 'supercache/' , '', str_replace( 'index.html', '', str_replace( 'index.html.gz', '', $directory ) ) ) ] = 1; } if ( ! isset( $sizes[ 'fsize' ] ) ) $sizes[ 'fsize' ] = @filesize( $directory ); else $sizes[ 'fsize' ] += @filesize( $directory ); } } return $sizes; } function wp_cache_clean_cache( $file_prefix, $all = false ) { global $wpdb, $cache_path, $supercachedir, $blog_cache_dir, $wp_cache_object_cache; if ( $wp_cache_object_cache && function_exists( "reset_oc_version" ) ) reset_oc_version(); if ( $all == true && wpsupercache_site_admin() && function_exists( 'prune_super_cache' ) ) { prune_super_cache( $cache_path, true ); return true; } if (function_exists ('prune_super_cache')) { if( is_dir( $supercachedir ) ) { prune_super_cache( $supercachedir, true ); } elseif( is_dir( $supercachedir . '.disabled' ) ) { prune_super_cache( $supercachedir . '.disabled', true ); } $_POST[ 'super_cache_stats' ] = 1; // regenerate super cache stats; } else { wp_cache_debug( 'Warning! prune_super_cache() not found in wp-cache.php', 1 ); } wp_cache_clean_legacy_files( $blog_cache_dir, $file_prefix ); wp_cache_clean_legacy_files( $cache_path, $file_prefix ); } function wp_cache_clean_legacy_files( $dir, $file_prefix ) { global $wpdb; $dir = trailingslashit( $dir ); if ( @is_dir( $dir . 'meta' ) == false ) return false; if ( $handle = @opendir( $dir ) ) { while ( false !== ( $file = readdir( $handle ) ) ) { if ( is_file( $dir . $file ) == false || $file == 'index.html' ) { continue; } if ( strpos( $file, $file_prefix ) !== false ) { if ( strpos( $file, '.html' ) ) { // delete old legacy files immediately @unlink( $dir . $file); @unlink( $dir . 'meta/' . str_replace( '.html', '.meta', $file ) ); } else { $meta = json_decode( wp_cache_get_legacy_cache( $dir . 'meta/' . $file ), true ); if ( ( defined( 'VHOST' ) || defined( 'SUBDOMAIN_INSTALL' ) || defined( 'SUNRISE' ) || ( defined( 'WP_ALLOW_MULTISITE' ) && constant( 'WP_ALLOW_MULTISITE' ) == true ) ) && $meta[ 'blog_id' ] != $wpdb->blogid ) continue; @unlink( $dir . $file); @unlink( $dir . 'meta/' . $file); } } } closedir($handle); } } function wp_cache_clean_expired($file_prefix) { global $cache_path, $cache_max_time, $blog_cache_dir, $wp_cache_preload_on; if ( $cache_max_time == 0 ) { return false; } // If phase2 was compiled, use its function to avoid race-conditions if(function_exists('wp_cache_phase2_clean_expired')) { if ( $wp_cache_preload_on != 1 && function_exists ('prune_super_cache')) { $dir = get_supercache_dir(); if( is_dir( $dir ) ) { prune_super_cache( $dir ); } elseif( is_dir( $dir . '.disabled' ) ) { prune_super_cache( $dir . '.disabled' ); } $_POST[ 'super_cache_stats' ] = 1; // regenerate super cache stats; } return wp_cache_phase2_clean_expired($file_prefix); } $now = time(); if ( $handle = @opendir( $blog_cache_dir ) ) { while ( false !== ( $file = readdir( $handle ) ) ) { if ( strpos( $file, $file_prefix ) !== false ) { if ( strpos( $file, '.html' ) ) { @unlink( $blog_cache_dir . $file); @unlink( $blog_cache_dir . 'meta/' . str_replace( '.html', '.meta', $file ) ); } elseif ( ( filemtime( $blog_cache_dir . $file ) + $cache_max_time ) <= $now ) { @unlink( $blog_cache_dir . $file ); @unlink( $blog_cache_dir . 'meta/' . $file ); } } } closedir($handle); } } function wpsc_remove_marker( $filename, $marker ) { if (!file_exists( $filename ) || is_writeable_ACLSafe( $filename ) ) { if (!file_exists( $filename ) ) { return ''; } else { $markerdata = explode( "\n", implode( '', file( $filename ) ) ); } $f = fopen( $filename, 'w' ); $foundit = false; if ( $markerdata ) { $state = true; foreach ( $markerdata as $n => $markerline ) { if (strpos($markerline, '# BEGIN ' . $marker) !== false) $state = false; if ( $state ) { if ( $n + 1 < count( $markerdata ) ) fwrite( $f, "{$markerline}\n" ); else fwrite( $f, "{$markerline}" ); } if (strpos($markerline, '# END ' . $marker) !== false) { $state = true; } } } return true; } else { return false; } } function wp_super_cache_footer() { ?>

    WP Super Cache' ); ?>

    is_404 function wp_cache_catch_404() { global $wp_cache_404; $wp_cache_404 = false; if( is_404() ) $wp_cache_404 = true; } add_action( 'template_redirect', 'wp_cache_catch_404' ); function wp_cache_favorite_action( $actions ) { if ( false == wpsupercache_site_admin() ) return $actions; if ( function_exists('current_user_can') && !current_user_can('manage_options') ) return $actions; $actions[ wp_nonce_url( 'options-general.php?page=wpsupercache&wp_delete_cache=1&tab=contents', 'wp-cache' ) ] = array( __( 'Delete Cache', 'wp-super-cache' ), 'manage_options' ); return $actions; } add_filter( 'favorite_actions', 'wp_cache_favorite_action' ); function wp_cache_plugin_notice( $plugin ) { global $cache_enabled; if( $plugin == 'wp-super-cache/wp-cache.php' && !$cache_enabled && function_exists( "admin_url" ) ) echo '' . sprintf( __( 'WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.' ), admin_url( 'options-general.php?page=wpsupercache' ) ) . ''; } add_action( 'after_plugin_row', 'wp_cache_plugin_notice' ); function wp_cache_plugin_actions( $links, $file ) { if( $file == 'wp-super-cache/wp-cache.php' && function_exists( "admin_url" ) ) { $settings_link = '' . __('Settings') . ''; array_unshift( $links, $settings_link ); // before other links } return $links; } add_filter( 'plugin_action_links', 'wp_cache_plugin_actions', 10, 2 ); function wp_cache_admin_notice() { global $cache_enabled, $wp_cache_phase1_loaded; if( substr( $_SERVER["PHP_SELF"], -11 ) == 'plugins.php' && !$cache_enabled && function_exists( "admin_url" ) ) echo '

    ' . sprintf( __('WP Super Cache is disabled. Please go to the plugin admin page to enable caching.', 'wp-super-cache' ), admin_url( 'options-general.php?page=wpsupercache' ) ) . '

    '; if ( defined( 'WP_CACHE' ) && WP_CACHE == true && ( defined( 'ADVANCEDCACHEPROBLEM' ) || ( $cache_enabled && false == isset( $wp_cache_phase1_loaded ) ) ) ) { echo '

    ' . sprintf( __( 'Warning! WP Super Cache caching was broken but has been fixed! The script advanced-cache.php could not load wp-cache-phase1.php.

    The file %1$s/advanced-cache.php has been recreated and WPCACHEHOME fixed in your wp-config.php. Reload to hide this message.', 'wp-super-cache' ), WP_CONTENT_DIR ) . '

    '; wp_cache_create_advanced_cache(); } } add_action( 'admin_notices', 'wp_cache_admin_notice' ); function wp_cache_check_site() { global $wp_super_cache_front_page_check, $wp_super_cache_front_page_clear, $wp_super_cache_front_page_text, $wp_super_cache_front_page_notification, $wpdb; if ( !isset( $wp_super_cache_front_page_check ) || ( isset( $wp_super_cache_front_page_check ) && $wp_super_cache_front_page_check == 0 ) ) { return false; } if ( function_exists( "wp_remote_get" ) == false ) { return false; } $front_page = wp_remote_get( site_url(), array('timeout' => 60, 'blocking' => true ) ); if( is_array( $front_page ) ) { // Check for gzipped front page if ( $front_page[ 'headers' ][ 'content-type' ] == 'application/x-gzip' ) { if ( !isset( $wp_super_cache_front_page_clear ) || ( isset( $wp_super_cache_front_page_clear ) && $wp_super_cache_front_page_clear == 0 ) ) { wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Front page is gzipped! Please clear cache!', 'wp-super-cache' ), home_url() ), sprintf( __( "Please visit %s to clear the cache as the front page of your site is now downloading!", 'wp-super-cache' ), admin_url( 'options-general.php?page=wpsupercache' ) ) ); } else { wp_cache_clear_cache( $wpdb->blogid ); wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Front page is gzipped! Cache Cleared!', 'wp-super-cache' ), home_url() ), sprintf( __( "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.", 'wp-super-cache' ), admin_url( 'options-general.php?page=wpsupercache' ) ) ); } } // Check for broken front page if ( isset( $wp_super_cache_front_page_text ) && $wp_super_cache_front_page_text != '' && false === strpos( $front_page[ 'body' ], $wp_super_cache_front_page_text ) ) { if ( !isset( $wp_super_cache_front_page_clear ) || ( isset( $wp_super_cache_front_page_clear ) && $wp_super_cache_front_page_clear == 0 ) ) { wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Front page is not correct! Please clear cache!', 'wp-super-cache' ), home_url() ), sprintf( __( 'Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!', 'wp-super-cache' ), admin_url( 'options-general.php?page=wpsupercache' ), $wp_super_cache_front_page_text ) ); } else { wp_cache_clear_cache( $wpdb->blogid ); wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Front page is not correct! Cache Cleared!', 'wp-super-cache' ), home_url() ), sprintf( __( 'The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.', 'wp-super-cache' ), admin_url( 'options-general.php?page=wpsupercache' ), $wp_super_cache_front_page_text ) ); } } } if ( isset( $wp_super_cache_front_page_notification ) && $wp_super_cache_front_page_notification == 1 ) { wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Front page check!', 'wp-super-cache' ), home_url() ), sprintf( __( "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.", 'wp-super-cache' ) . "\n\n", admin_url( 'options-general.php?page=wpsupercache' ) ) ); } if ( !wp_next_scheduled( 'wp_cache_check_site_hook' ) ) { wp_schedule_single_event( time() + 360 , 'wp_cache_check_site_hook' ); wp_cache_debug( 'scheduled wp_cache_check_site_hook for 360 seconds time.', 2 ); } } add_action( 'wp_cache_check_site_hook', 'wp_cache_check_site' ); function update_cached_mobile_ua_list( $mobile_browsers, $mobile_prefixes = 0, $mobile_groups = 0 ) { global $wp_cache_config_file, $wp_cache_mobile_browsers, $wp_cache_mobile_prefixes, $wp_cache_mobile_groups; if ( is_array( $mobile_browsers ) ) { $wp_cache_mobile_browsers = $mobile_browsers; wp_cache_replace_line('^ *\$wp_cache_mobile_browsers', "\$wp_cache_mobile_browsers = '" . implode( ', ', $mobile_browsers ) . "';", $wp_cache_config_file); } if ( is_array( $mobile_prefixes ) ) { $wp_cache_mobile_prefixes = $mobile_prefixes; wp_cache_replace_line('^ *\$wp_cache_mobile_prefixes', "\$wp_cache_mobile_prefixes = '" . implode( ', ', $mobile_prefixes ) . "';", $wp_cache_config_file); } if ( is_array( $mobile_groups ) ) { $wp_cache_mobile_groups = $mobile_groups; wp_cache_replace_line('^ *\$wp_cache_mobile_groups', "\$wp_cache_mobile_groups = '" . implode( ', ', $mobile_groups ) . "';", $wp_cache_config_file); } return true; } function wpsc_update_htaccess() { extract( wpsc_get_htaccess_info() ); wpsc_remove_marker( $home_path.'.htaccess', 'WordPress' ); // remove original WP rules so SuperCache rules go on top if( insert_with_markers( $home_path.'.htaccess', 'WPSuperCache', explode( "\n", $rules ) ) && insert_with_markers( $home_path.'.htaccess', 'WordPress', explode( "\n", $wprules ) ) ) { return true; } else { return false; } } function wpsc_update_htaccess_form( $short_form = true ) { global $wpmu_version; extract( wpsc_get_htaccess_info() ); if( !is_writeable_ACLSafe( $home_path . ".htaccess" ) ) { echo "

    " . __( 'Cannot update .htaccess', 'wp-super-cache' ) . "

    " . sprintf( __( 'The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.', 'wp-super-cache' ), $home_path ) . "

    " . __( 'Refresh this page when the file permissions have been modified.' ) . "

    " . sprintf( __( 'Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):', 'wp-super-cache' ), $home_path ) . "

    "; echo "

    # BEGIN WPSuperCache\n" . esc_html( $rules ) . "# END WPSuperCache

    "; } else { if ( $short_form == false ) { echo "

    " . sprintf( __( 'To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess', 'wp-super-cache' ), $home_path ) . " "; _e( "You can edit the file yourself. Add the following rules.", 'wp-super-cache' ); echo __( " Make sure they appear before any existing WordPress rules. ", 'wp-super-cache' ) . "

    "; echo "
    # BEGIN WPSuperCache\n" . esc_html( $rules ) . "# END WPSuperCache

    "; echo "

    " . sprintf( __( 'Rules must be added to %s too:', 'wp-super-cache' ), WP_CONTENT_DIR . "/cache/.htaccess" ) . "

    "; echo "
    # BEGIN supercache\n" . esc_html( $gziprules ) . "# END supercache

    "; } if ( !isset( $wpmu_version ) || $wpmu_version == '' ) { echo '
    '; echo ''; echo '
    '; wp_nonce_field('wp-cache'); echo "
    \n"; } } } /* * Return LOGGED_IN_COOKIE if it doesn't begin with wordpress_logged_in * to avoid having people update their .htaccess file */ function wpsc_get_logged_in_cookie() { $logged_in_cookie = 'wordpress_logged_in'; if ( defined( 'LOGGED_IN_COOKIE' ) && substr( constant( 'LOGGED_IN_COOKIE' ), 0, 19 ) != 'wordpress_logged_in' ) $logged_in_cookie = constant( 'LOGGED_IN_COOKIE' ); return $logged_in_cookie; } function wpsc_get_htaccess_info() { global $wp_cache_mobile_enabled, $wp_cache_mobile_prefixes, $wp_cache_mobile_browsers, $wp_cache_disable_utf8; if ( isset( $_SERVER[ "PHP_DOCUMENT_ROOT" ] ) ) { $document_root = $_SERVER[ "PHP_DOCUMENT_ROOT" ]; $apache_root = $_SERVER[ "PHP_DOCUMENT_ROOT" ]; } else { $document_root = $_SERVER[ "DOCUMENT_ROOT" ]; $apache_root = '%{DOCUMENT_ROOT}'; } $content_dir_root = $document_root; if ( strpos( $document_root, '/kunden/homepages/' ) === 0 ) { // http://wordpress.org/support/topic/plugin-wp-super-cache-how-to-get-mod_rewrite-working-on-1and1-shared-hosting?replies=1 // On 1and1, PHP's directory structure starts with '/homepages'. The // Apache directory structure has an extra '/kunden' before it. // Also 1and1 does not support the %{DOCUMENT_ROOT} variable in // .htaccess files. // This prevents the $inst_root from being calculated correctly and // means that the $apache_root is wrong. // // e.g. This is an example of how Apache and PHP see the directory // structure on 1and1: // Apache: /kunden/homepages/xx/dxxxxxxxx/htdocs/site1/index.html // PHP: /homepages/xx/dxxxxxxxx/htdocs/site1/index.html // Here we fix up the paths to make mode_rewrite work on 1and1 shared hosting. $content_dir_root = substr( $content_dir_root, 7 ); $apache_root = $document_root; } $home_path = get_home_path(); $home_root = parse_url(get_bloginfo('url')); $home_root = isset( $home_root['path'] ) ? trailingslashit( $home_root['path'] ) : '/'; $home_root_lc = str_replace( '//', '/', strtolower( $home_root ) ); $inst_root = str_replace( '//', '/', '/' . trailingslashit( str_replace( $content_dir_root, '', str_replace( '\\', '/', WP_CONTENT_DIR ) ) ) ); $wprules = implode( "\n", extract_from_markers( $home_path.'.htaccess', 'WordPress' ) ); $wprules = str_replace( "RewriteEngine On\n", '', $wprules ); $wprules = str_replace( "RewriteBase $home_root\n", '', $wprules ); $scrules = implode( "\n", extract_from_markers( $home_path.'.htaccess', 'WPSuperCache' ) ); if( substr( get_option( 'permalink_structure' ), -1 ) == '/' ) { $condition_rules[] = "RewriteCond %{REQUEST_URI} !^.*[^/]$"; $condition_rules[] = "RewriteCond %{REQUEST_URI} !^.*//.*$"; } $condition_rules[] = "RewriteCond %{REQUEST_METHOD} !POST"; $condition_rules[] = "RewriteCond %{QUERY_STRING} !.*=.*"; $condition_rules[] = "RewriteCond %{HTTP:Cookie} !^.*(comment_author_|" . wpsc_get_logged_in_cookie() . "|wp-postpass_).*$"; $condition_rules[] = "RewriteCond %{HTTP:X-Wap-Profile} !^[a-z0-9\\\"]+ [NC]"; $condition_rules[] = "RewriteCond %{HTTP:Profile} !^[a-z0-9\\\"]+ [NC]"; if ( $wp_cache_mobile_enabled ) { if ( false == empty( $wp_cache_mobile_browsers ) ) $condition_rules[] = "RewriteCond %{HTTP_USER_AGENT} !^.*(" . addcslashes( implode( '|', $wp_cache_mobile_browsers ), ' ' ) . ").* [NC]"; if ( false == empty( $wp_cache_mobile_prefixes ) ) $condition_rules[] = "RewriteCond %{HTTP_user_agent} !^(" . addcslashes( implode( '|', $wp_cache_mobile_prefixes ), ' ' ) . ").* [NC]"; } $condition_rules = apply_filters( 'supercacherewriteconditions', $condition_rules ); $rules = "\n"; $rules .= "RewriteEngine On\n"; $rules .= "RewriteBase $home_root\n"; // props Chris Messina $rules .= "#If you serve pages from behind a proxy you may want to change 'RewriteCond %{HTTPS} on' to something more sensible\n"; if ( isset( $wp_cache_disable_utf8 ) == false || $wp_cache_disable_utf8 == 0 ) { $charset = get_option('blog_charset') == '' ? 'UTF-8' : get_option('blog_charset'); $rules .= "AddDefaultCharset {$charset}\n"; } $rules .= "CONDITION_RULES"; $rules .= "RewriteCond %{HTTP:Accept-Encoding} gzip\n"; $rules .= "RewriteCond %{HTTPS} on\n"; $rules .= "RewriteCond {$apache_root}{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index-https.html.gz -f\n"; $rules .= "RewriteRule ^(.*) \"{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index-https.html.gz\" [L]\n\n"; $rules .= "CONDITION_RULES"; $rules .= "RewriteCond %{HTTP:Accept-Encoding} gzip\n"; $rules .= "RewriteCond %{HTTPS} !on\n"; $rules .= "RewriteCond {$apache_root}{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index.html.gz -f\n"; $rules .= "RewriteRule ^(.*) \"{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index.html.gz\" [L]\n\n"; $rules .= "CONDITION_RULES"; $rules .= "RewriteCond %{HTTPS} on\n"; $rules .= "RewriteCond {$apache_root}{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index-https.html -f\n"; $rules .= "RewriteRule ^(.*) \"{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index-https.html\" [L]\n\n"; $rules .= "CONDITION_RULES"; $rules .= "RewriteCond %{HTTPS} !on\n"; $rules .= "RewriteCond {$apache_root}{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index.html -f\n"; $rules .= "RewriteRule ^(.*) \"{$inst_root}cache/supercache/%{SERVER_NAME}{$home_root_lc}$1/index.html\" [L]\n"; $rules .= "\n"; $rules = apply_filters( 'supercacherewriterules', $rules ); $rules = str_replace( "CONDITION_RULES", implode( "\n", $condition_rules ) . "\n", $rules ); $gziprules = "\n \n ForceType text/html\n FileETag None\n \n AddEncoding gzip .gz\n AddType text/html .gz\n\n"; $gziprules .= "\n SetEnvIfNoCase Request_URI \.gz$ no-gzip\n\n"; $gziprules .= "\n Header set Vary \"Accept-Encoding, Cookie\"\n Header set Cache-Control 'max-age=3, must-revalidate'\n\n"; $gziprules .= "\n ExpiresActive On\n ExpiresByType text/html A3\n\n"; $gziprules .= "Options -Indexes\n"; return array( "document_root" => $document_root, "apache_root" => $apache_root, "home_path" => $home_path, "home_root" => $home_root, "home_root_lc" => $home_root_lc, "inst_root" => $inst_root, "wprules" => $wprules, "scrules" => $scrules, "condition_rules" => $condition_rules, "rules" => $rules, "gziprules" => $gziprules ); } function clear_post_supercache( $post_id ) { $dir = get_current_url_supercache_dir( $post_id ); if ( false == @is_dir( $dir ) ) return false; if ( !function_exists( 'prune_super_cache' ) ) include_once( 'wp-cache-phase2.php' ); wp_cache_debug( "clear_post_supercache: deleting $dir/index*.html files", 2 ); $files_to_check = get_all_supercache_filenames( $dir ); foreach( $files_to_check as $cache_file ) { prune_super_cache( $dir . $cache_file, true ); } } function wp_cron_preload_cache() { global $wpdb, $wp_cache_preload_interval, $wp_cache_preload_posts, $wp_cache_preload_email_me, $wp_cache_preload_email_volume, $cache_path, $wp_cache_preload_taxonomies; if ( get_option( 'preload_cache_stop' ) ) { delete_option( 'preload_cache_stop' ); wp_cache_debug( "wp_cron_preload_cache: preload cancelled", 1 ); return true; } $mutex = $cache_path . "preload_mutex.tmp"; sleep( 3 + mt_rand( 1, 5 ) ); if ( @file_exists( $mutex ) ) { if ( @filemtime( $mutex ) > ( time() - 600 ) ) { wp_cache_debug( "wp_cron_preload_cache: preload mutex found and less than 600 seconds old. Aborting preload.", 1 ); return true; } else { wp_cache_debug( "wp_cron_preload_cache: old preload mutex found and deleted. Preload continues.", 1 ); @unlink( $mutex ); } } $fp = @fopen( $mutex, 'w' ); @fclose( $fp ); $counter = get_option( 'preload_cache_counter' ); if ( is_array( $counter ) == false ) { wp_cache_debug( "wp_cron_preload_cache: setting up preload for the first time!", 5 ); $counter = array( 'c' => 0, 't' => time() ); update_option( 'preload_cache_counter', $counter ); } $c = $counter[ 'c' ]; update_option( 'preload_cache_counter', array( 'c' => ( $c + 100 ), 't' => time() ) ); if ( $wp_cache_preload_email_me && $c == 0 ) wp_mail( get_option( 'admin_email' ), sprintf( __( '[%1$s] Cache Preload Started', 'wp-super-cache' ), home_url(), '' ), ' ' ); if ( $wp_cache_preload_posts == 'all' || $c < $wp_cache_preload_posts ) { wp_cache_debug( "wp_cron_preload_cache: doing taxonomy preload.", 5 ); $permalink_counter_msg = $cache_path . "preload_permalink.txt"; if ( isset( $wp_cache_preload_taxonomies ) && $wp_cache_preload_taxonomies ) { $taxonomies = apply_filters( 'wp_cache_preload_taxonomies', array( 'post_tag' => 'tag', 'category' => 'category' ) ); foreach( $taxonomies as $taxonomy => $path ) { $taxonomy_filename = $cache_path . "taxonomy_" . $taxonomy . ".txt"; if ( $c == 0 ) @unlink( $taxonomy_filename ); if ( false == @file_exists( $taxonomy_filename ) ) { $out = ''; $records = get_terms( $taxonomy ); foreach( $records as $term ) { $out .= get_term_link( $term ). "\n"; } $fp = fopen( $taxonomy_filename, 'w' ); if ( $fp ) { fwrite( $fp, $out ); fclose( $fp ); } $details = explode( "\n", $out ); } else { $details = explode( "\n", file_get_contents( $taxonomy_filename ) ); } if ( count( $details ) != 1 && $details[ 0 ] != '' ) { $rows = array_splice( $details, 0, 50 ); if ( $wp_cache_preload_email_me && $wp_cache_preload_email_volume == 'many' ) wp_mail( get_option( 'admin_email' ), sprintf( __( '[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d', 'wp-super-cache' ), home_url(), $taxonomy, $c, ($c+100) ), 'Refreshing: ' . print_r( $rows, 1 ) ); foreach( (array)$rows as $url ) { set_time_limit( 60 ); if ( $url == '' ) continue; $url_info = parse_url( $url ); $dir = get_supercache_dir() . $url_info[ 'path' ]; wp_cache_debug( "wp_cron_preload_cache: delete $dir", 5 ); prune_super_cache( $dir ); $fp = @fopen( $permalink_counter_msg, 'w' ); if ( $fp ) { @fwrite( $fp, "$taxonomy: $url" ); @fclose( $fp ); } wp_remote_get( $url, array('timeout' => 60, 'blocking' => true ) ); wp_cache_debug( "wp_cron_preload_cache: fetched $url", 5 ); sleep( 1 ); } $fp = fopen( $taxonomy_filename, 'w' ); if ( $fp ) { fwrite( $fp, implode( "\n", $details ) ); fclose( $fp ); } } } } } if ( $wp_cache_preload_posts == 'all' || $c < $wp_cache_preload_posts ) { $types = get_post_types( array( 'public' => true, 'publicly_queryable' => true ), 'names', 'or' ); $types = array_map( 'esc_sql', $types ); $types = "'" . implode( "','", $types ) . "'"; $posts = $wpdb->get_col( "SELECT ID FROM {$wpdb->posts} WHERE ( post_type IN ( $types ) ) AND post_status = 'publish' ORDER BY ID ASC LIMIT $c, 100" ); wp_cache_debug( "wp_cron_preload_cache: got 100 posts from position $c.", 5 ); } else { wp_cache_debug( "wp_cron_preload_cache: no more posts to get. Limit ($wp_cache_preload_posts) reached.", 5 ); $posts = false; } if ( !isset( $wp_cache_preload_email_volume ) ) $wp_cache_preload_email_volume = 'medium'; if ( $posts ) { if ( get_option( 'show_on_front' ) == 'page' ) { $page_on_front = get_option( 'page_on_front' ); $page_for_posts = get_option( 'page_for_posts' ); } else { $page_on_front = $page_for_posts = 0; } if ( $wp_cache_preload_email_me && $wp_cache_preload_email_volume == 'many' ) wp_mail( get_option( 'admin_email' ), sprintf( __( '[%1$s] Refreshing posts from %2$d to %3$d', 'wp-super-cache' ), home_url(), $c, ($c+100) ), ' ' ); $msg = ''; $count = $c + 1; $permalink_counter_msg = $cache_path . "preload_permalink.txt"; foreach( $posts as $post_id ) { set_time_limit( 60 ); if ( $page_on_front != 0 && ( $post_id == $page_on_front || $post_id == $page_for_posts ) ) continue; clear_post_supercache( $post_id ); $url = get_permalink( $post_id ); $fp = @fopen( $permalink_counter_msg, 'w' ); if ( $fp ) { @fwrite( $fp, $count . " " . $url ); @fclose( $fp ); } if ( @file_exists( $cache_path . "stop_preload.txt" ) ) { wp_cache_debug( "wp_cron_preload_cache: cancelling preload. stop_preload.txt found.", 5 ); @unlink( $mutex ); @unlink( $cache_path . "stop_preload.txt" ); update_option( 'preload_cache_counter', array( 'c' => 0, 't' => time() ) ); if ( $wp_cache_preload_email_me ) wp_mail( get_option( 'admin_email' ), sprintf( __( '[%1$s] Cache Preload Stopped', 'wp-super-cache' ), home_url(), '' ), ' ' ); return true; } $msg .= "$url\n"; wp_remote_get( $url, array('timeout' => 60, 'blocking' => true ) ); wp_cache_debug( "wp_cron_preload_cache: fetched $url", 5 ); sleep( 1 ); $count++; } if ( $wp_cache_preload_email_me && $wp_cache_preload_email_volume != 'less' ) wp_mail( get_option( 'admin_email' ), sprintf( __( '[%1$s] %2$d posts refreshed', 'wp-super-cache' ), home_url(), ($c+100) ), __( "Refreshed the following posts:", 'wp-super-cache' ) . "\n$msg" ); if ( defined( 'DOING_CRON' ) ) { wp_cache_debug( "wp_cron_preload_cache: scheduling the next preload in 30 seconds.", 5 ); wp_schedule_single_event( time() + 30, 'wp_cache_preload_hook' ); } } else { $msg = ''; update_option( 'preload_cache_counter', array( 'c' => 0, 't' => time() ) ); if ( (int)$wp_cache_preload_interval && defined( 'DOING_CRON' ) ) { if ( $wp_cache_preload_email_me ) $msg = sprintf( __( 'Scheduling next preload refresh in %d minutes.', 'wp-super-cache' ), (int)$wp_cache_preload_interval ); wp_cache_debug( "wp_cron_preload_cache: no more posts. scheduling next preload in $wp_cache_preload_interval minutes.", 5 ); wp_schedule_single_event( time() + ( (int)$wp_cache_preload_interval * 60 ), 'wp_cache_full_preload_hook' ); } global $file_prefix, $cache_max_time; if ( $wp_cache_preload_interval > 0 ) { $cache_max_time = (int)$wp_cache_preload_interval * 60; // fool the GC into expiring really old files } else { $cache_max_time = 86400; // fool the GC into expiring really old files } if ( $wp_cache_preload_email_me ) wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Cache Preload Completed', 'wp-super-cache' ), home_url() ), __( "Cleaning up old supercache files.", 'wp-super-cache' ) . "\n" . $msg ); wp_cache_debug( "wp_cron_preload_cache: clean expired cache files older than $cache_max_time seconds.", 5 ); wp_cache_phase2_clean_expired( $file_prefix, true ); // force cleanup of old files. } @unlink( $mutex ); } add_action( 'wp_cache_preload_hook', 'wp_cron_preload_cache' ); add_action( 'wp_cache_full_preload_hook', 'wp_cron_preload_cache' ); function next_preload_message( $hook, $text, $limit = 0 ) { global $currently_preloading, $wp_cache_preload_interval; if ( $next_preload = wp_next_scheduled( $hook ) ) { $next_time = $next_preload - time(); if ( $limit != 0 && $next_time > $limit ) return false; $h = $m = $s = 0; if ( $next_time > 0 ) { $m = (int)($next_time / 60); $s = $next_time % 60; $h = (int)($m / 60); $m = $m % 60; } if ( $next_time > 0 && $next_time < ( 60 * $wp_cache_preload_interval ) ) echo '

    ' . sprintf( $text, $h, $m, $s ) . '

    '; if ( ( $next_preload - time() ) <= 60 ) $currently_preloading = true; } } function option_preload_cache_counter( $value ) { if ( false == is_array( $value ) ) { $ret = array( 'c' => $value, 't' => time(), 'first' => 1 ); return $ret; } return $value; } add_filter( 'option_preload_cache_counter', 'option_preload_cache_counter' ); function check_up_on_preloading() { $value = get_option( 'preload_cache_counter' ); if ( $value[ 'c' ] > 0 && ( time() - $value[ 't' ] ) > 3600 && false == wp_next_scheduled( 'wp_cache_preload_hook' ) ) { if ( is_admin() ) wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Preload may have stalled.', 'wp-super-cache' ), get_bloginfo( 'url' ) ), sprintf( __( "Preload has been restarted.\n%s", 'wp-super-cache' ), admin_url( "options-general.php?page=wpsupercache" ) ) ); wp_schedule_single_event( time() + 30, 'wp_cache_preload_hook' ); } } add_action( 'init', 'check_up_on_preloading' ); // sometimes preloading stops working. Kickstart it. function wp_cache_disable_plugin( $delete_config_file = true ) { global $wp_cache_config_file, $wp_rewrite; if ( file_exists( ABSPATH . 'wp-config.php') ) { $global_config_file = ABSPATH . 'wp-config.php'; } else { $global_config_file = dirname(ABSPATH) . '/wp-config.php'; } $line = 'define(\'WP_CACHE\', true);'; if ( strpos( file_get_contents( $global_config_file ), $line ) && ( !is_writeable_ACLSafe( $global_config_file ) || !wp_cache_replace_line( 'define *\( *\'WP_CACHE\'', '//' . $line, $global_config_file ) ) ) wp_die( "Could not remove WP_CACHE define from $global_config_file. Please edit that file and remove the line containing the text 'WP_CACHE'. Then refresh this page." ); uninstall_supercache( WP_CONTENT_DIR . '/cache' ); $file_not_deleted = false; if ( @file_exists( WP_CONTENT_DIR . "/advanced-cache.php" ) ) { if ( false == @unlink( WP_CONTENT_DIR . "/advanced-cache.php" ) ) $file_not_deleted[] = 'advanced-cache.php'; } if ( $delete_config_file && @file_exists( WP_CONTENT_DIR . "/wp-cache-config.php" ) ) { if ( false == unlink( WP_CONTENT_DIR . "/wp-cache-config.php" ) ) $file_not_deleted[] = 'wp-cache-config.php'; } if ( $file_not_deleted ) { $msg = "

    One or more files could not be deleted. These files and directories must be made writeable:

    \n
    1. " . WP_CONTENT_DIR . "
      2. \n"; $code = "\n"; $msg .= "
    \n

    First try fixing the directory permissions with this command and refresh this page:

    chmod 777 " . WP_CONTENT_DIR . "

    If you still see this error, you have to fix the permissions on the files themselves and refresh this page again:

    {$code}\n

    Don't forgot to fix things later:
    chmod 755 " . WP_CONTENT_DIR . "

    If you don't know what chmod is use this Google search to find out all about it.

    Please refresh this page when the permissions have been modified.

    "; wp_die( $msg ); } extract( wpsc_get_htaccess_info() ); if ( $scrules != '' && insert_with_markers( $home_path.'.htaccess', 'WPSuperCache', array() ) ) { $wp_rewrite->flush_rules(); } elseif( $scrules != '' ) { wp_mail( get_option( 'admin_email' ), __( 'Supercache Uninstall Problems', 'wp-super-cache' ), sprintf( __( "Dear User,\n\nWP Super Cache was removed from your blog but the mod_rewrite rules\nin your .htaccess were not.\n\nPlease edit the following file and remove the code\nbetween 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!\n\n%s\n\nRegards,\nWP Super Cache Plugin\nhttp://wordpress.org/plugins/wp-super-cache/", 'wp-super-cache' ), ABSPATH . '/.htaccess' ) ); } } function uninstall_supercache( $folderPath ) { // from http://www.php.net/manual/en/function.rmdir.php if ( trailingslashit( constant( 'ABSPATH' ) ) == trailingslashit( $folderPath ) ) return false; if ( @is_dir ( $folderPath ) ) { $dh = @opendir($folderPath); while( false !== ( $value = @readdir( $dh ) ) ) { if ( $value != "." && $value != ".." ) { $value = $folderPath . "/" . $value; if ( @is_dir ( $value ) ) { uninstall_supercache( $value ); } else { @unlink( $value ); } } } return @rmdir( $folderPath ); } else { return false; } } function supercache_admin_bar_render() { global $wp_admin_bar, $wp_cache_not_logged_in; if ( !is_user_logged_in() || !$wp_cache_not_logged_in ) return false; if ( function_exists('current_user_can') && false == current_user_can('delete_others_posts') ) return false; $wp_admin_bar->add_menu( array( 'parent' => '', 'id' => 'delete-cache', 'title' => __( 'Delete Cache', 'wp-super-cache' ), 'meta' => array( 'title' => __( 'Delete cache of the current page', 'wp-super-cache' ) ), 'href' => wp_nonce_url( admin_url( 'index.php?action=delcachepage&path=' . urlencode( preg_replace( '/[ <>\'\"\r\n\t\(\)]/', '', $_SERVER[ 'REQUEST_URI' ] ) ) ), 'delete-cache' ) ) ); } add_action( 'wp_before_admin_bar_render', 'supercache_admin_bar_render' ); ?> wp-cache-phase1.php000066600000063061152133035240010133 0ustar00 $header) { // godaddy fix, via http://blog.gneu.org/2008/05/wp-supercache-on-godaddy/ and http://www.littleredrails.com/blog/2007/09/08/using-wp-cache-on-godaddy-500-error/ if( strpos( $header, 'Last-Modified:' ) === false ) header($header); } header( 'WP-Super-Cache: Served legacy cache file' ); if ( $wp_cache_object_cache ) { if ( $cache ) { if ( $ungzip ) { // attempt to uncompress the cached file just in case it's gzipped $uncompressed = gzuncompress( $cache ); if ( $uncompressed ) { wp_cache_debug( "Uncompressed gzipped cache file from object cache", 1 ); $cache = $uncompressed; unset( $uncompressed ); } } if ( isset( $meta[ 'dynamic' ] ) && $meta[ 'dynamic' ] ) { wp_cache_debug( "Serving wp-cache dynamic file from object cache", 5 ); echo do_cacheaction( 'wpsc_cachedata', $cache ); } else { wp_cache_debug( "Serving wp-cache static file from object cache", 5 ); echo $cache; } wp_cache_debug( "exit request", 5 ); die(); } } else { if ( isset( $meta[ 'dynamic' ] ) ) { wp_cache_debug( "Serving wp-cache dynamic file", 5 ); if ( $ungzip ) { // attempt to uncompress the cached file just in case it's gzipped $cache = wp_cache_get_legacy_cache( $cache_file ); $uncompressed = @gzuncompress( $cache ); if ( $uncompressed ) { wp_cache_debug( "Uncompressed gzipped cache file from wp-cache", 1 ); unset( $cache ); echo do_cacheaction( 'wpsc_cachedata', $uncompressed ); } else { echo do_cacheaction( 'wpsc_cachedata', $cache ); } } else { echo do_cacheaction( 'wpsc_cachedata', wp_cache_get_legacy_cache( $cache_file ) ); } } else { wp_cache_debug( "Serving wp-cache static file", 5 ); if ( $ungzip ) { $cache = wp_cache_get_legacy_cache( $cache_file ); $uncompressed = gzuncompress( $cache ); if ( $uncompressed ) { wp_cache_debug( "Uncompressed gzipped cache file from wp-cache", 1 ); echo $uncompressed; } else { echo $cache; } } else { echo( wp_cache_get_legacy_cache( $cache_file ) ); } } wp_cache_debug( "exit request", 5 ); die(); } } function wp_cache_get_legacy_cache( $cache_file ) { return substr( @file_get_contents( $cache_file ), 15 ); } if(defined('DOING_CRON')) { extract( wp_super_cache_init() ); return true; } if ( !isset( $wp_super_cache_late_init ) || ( isset( $wp_super_cache_late_init ) && false == $wp_super_cache_late_init ) ) { wp_cache_serve_cache_file(); } function wp_cache_postload() { global $cache_enabled, $wp_super_cache_late_init; if ( !$cache_enabled ) return true; if ( isset( $wp_super_cache_late_init ) && true == $wp_super_cache_late_init ) { wp_cache_debug( "Supercache Late Init: add wp_cache_serve_cache_file to init", 3 ); add_action( 'init', 'wp_cache_late_loader', 9999 ); } else { wp_super_cache_init(); wp_cache_phase2(); } } function wp_cache_late_loader() { wp_cache_debug( "Supercache Late Loader running on init", 3 ); wp_cache_serve_cache_file(); wp_cache_phase2(); } function wp_cache_get_cookies_values() { static $string = ''; if ( $string != '' ) { wp_cache_debug( "wp_cache_get_cookies_values: cached: $string" ); return $string; } $regex = "/^wp-postpass|^comment_author_"; if ( defined( 'LOGGED_IN_COOKIE' ) ) $regex .= "|^" . preg_quote( constant( 'LOGGED_IN_COOKIE' ) ); else $regex .= "|^wordpress_logged_in_"; $regex .= "/"; while ($key = key($_COOKIE)) { if ( preg_match( $regex, $key ) ) { wp_cache_debug( "wp_cache_get_cookies_values: $regex Cookie detected: $key", 5 ); $string .= $_COOKIE[ $key ] . ","; } next($_COOKIE); } reset($_COOKIE); // If you use this hook, make sure you update your .htaccess rules with the same conditions $string = do_cacheaction( 'wp_cache_get_cookies_values', $string ); if ( $string != '' ) $string = md5( $string ); wp_cache_debug( "wp_cache_get_cookies_values: return: $string", 5 ); return $string; } function add_cacheaction( $action, $func ) { global $wp_supercache_actions; $wp_supercache_actions[ $action ][] = $func; } function do_cacheaction( $action, $value = '' ) { global $wp_supercache_actions; if ( !isset( $wp_supercache_actions ) || !is_array( $wp_supercache_actions ) ) return $value; if( array_key_exists($action, $wp_supercache_actions) && is_array( $wp_supercache_actions[ $action ] ) ) { $actions = $wp_supercache_actions[ $action ]; foreach( $actions as $func ) { if ( is_array( $func ) ) { $value = $func[0]->{$func[1]}( $value ); } else { $value = $func( $value ); } } } return $value; } function wp_cache_mobile_group( $user_agent ) { global $wp_cache_mobile_groups; foreach( (array)$wp_cache_mobile_groups as $name => $group ) { foreach( (array)$group as $browser ) { $browser = trim( strtolower( $browser ) ); if ( $browser != '' && strstr( $user_agent, $browser ) ) { return $browser; } } } return "mobile"; } // From http://wordpress.org/plugins/wordpress-mobile-edition/ by Alex King function wp_cache_check_mobile( $cache_key ) { global $wp_cache_mobile_enabled, $wp_cache_mobile_browsers, $wp_cache_mobile_prefixes; if ( !isset( $wp_cache_mobile_enabled ) || false == $wp_cache_mobile_enabled ) return $cache_key; wp_cache_debug( "wp_cache_check_mobile: $cache_key" ); // allow plugins to short circuit mobile check. Cookie, extra UA checks? switch( do_cacheaction( 'wp_cache_check_mobile', $cache_key ) ) { case "normal": wp_cache_debug( "wp_cache_check_mobile: desktop user agent detected by wp_cache_check_mobile action" ); return $cache_key; break; case "mobile": wp_cache_debug( "wp_cache_check_mobile: mobile user agent detected by wp_cache_check_mobile action" ); return $cache_key . "-mobile"; break; } if ( !isset( $_SERVER[ "HTTP_USER_AGENT" ] ) ) { return $cache_key; } if ( do_cacheaction( 'disable_mobile_check', false ) ) { wp_cache_debug( "wp_cache_check_mobile: disable_mobile_check disabled mobile check" ); return $cache_key; } $browsers = explode( ',', $wp_cache_mobile_browsers ); $user_agent = strtolower( $_SERVER['HTTP_USER_AGENT'] ); foreach ($browsers as $browser) { if ( strstr( $user_agent, trim( strtolower( $browser ) ) ) ) { wp_cache_debug( "mobile browser detected: " . $_SERVER[ "HTTP_USER_AGENT" ], 5 ); return $cache_key . '-' . wp_cache_mobile_group( $user_agent ); } } if (isset($_SERVER['HTTP_X_WAP_PROFILE']) ) return $cache_key . '-' . $_SERVER['HTTP_X_WAP_PROFILE']; if (isset($_SERVER['HTTP_PROFILE']) ) return $cache_key . '-' . $_SERVER['HTTP_PROFILE']; if ( isset( $wp_cache_mobile_prefixes ) ) { $browsers = explode( ',', $wp_cache_mobile_prefixes ); foreach ($browsers as $browser_prefix) { if ( substr($user_agent, 0, 4) == $browser_prefix ) { wp_cache_debug( "mobile browser (prefix) detected: " . $_SERVER[ "HTTP_USER_AGENT" ], 5 ); return $cache_key . '-' . $browser_prefix; } } } $accept = isset( $_SERVER[ 'HTTP_ACCEPT' ] ) ? strtolower( $_SERVER[ 'HTTP_ACCEPT' ] ) : ''; if (strpos($accept, 'wap') !== false) { return $cache_key . '-' . 'wap'; } if (isset($_SERVER['ALL_HTTP']) && strpos(strtolower($_SERVER['ALL_HTTP']), 'operamini') !== false) { return $cache_key . '-' . 'operamini'; } return $cache_key; } /** * Add a log message to the file, if debugging is turned on * * @param $message string The message that should be added to the log * @param $level int */ function wp_cache_debug( $message, $level = 1 ) { global $wp_cache_debug_log, $cache_path, $wp_cache_debug_ip, $wp_super_cache_debug; // If either of the debug or log globals aren't set, then we can stop if ( !isset($wp_super_cache_debug) || !isset($wp_cache_debug_log) ) return false; // If either the debug or log globals are false or empty, we can stop if ( $wp_super_cache_debug == false || $wp_cache_debug_log == '' ) return false; // If the debug_ip has been set, but it doesn't match the ip of the requester // then we can stop. if ( isset($wp_cache_debug_ip) && $wp_cache_debug_ip != '' && $wp_cache_debug_ip != $_SERVER[ 'REMOTE_ADDR' ] ) return false; // Log message: Date URI Message $log_message = date('H:i:s') . " " . getmypid() . " {$_SERVER['REQUEST_URI']} {$message}\n\r"; // path to the log file in the cache folder $log_file = $cache_path . str_replace('/', '', str_replace('..', '', $wp_cache_debug_log)); error_log( $log_message, 3, $log_file ); } function wp_cache_user_agent_is_rejected() { global $cache_rejected_user_agent; if (!function_exists('apache_request_headers')) return false; $headers = apache_request_headers(); if (!isset($headers["User-Agent"])) return false; if ( false == is_array( $cache_rejected_user_agent ) ) return false; foreach ($cache_rejected_user_agent as $expr) { if (strlen($expr) > 0 && stristr($headers["User-Agent"], $expr)) return true; } return false; } function get_supercache_dir( $blog_id = 0 ) { global $cache_path; if ( $blog_id == 0 ) { $home = get_option( 'home' ); } else { $home = get_blog_option( $blog_id, 'home' ); } return trailingslashit( apply_filters( 'wp_super_cache_supercachedir', $cache_path . 'supercache/' . trailingslashit( strtolower( preg_replace( '/:.*$/', '', str_replace( 'http://', '', str_replace( 'https://', '', $home ) ) ) ) ) ) ); } function get_current_url_supercache_dir( $post_id = 0 ) { global $cached_direct_pages, $cache_path, $wp_cache_request_uri, $WPSC_HTTP_HOST, $wp_cache_home_path; static $saved_supercache_dir = array(); if ( isset( $saved_supercache_dir[ $post_id ] ) ) { return $saved_supercache_dir[ $post_id ]; } $DONOTREMEMBER = 0; if ( $post_id != 0 ) { $site_url = site_url(); $permalink = get_permalink( $post_id ); if ( false === strpos( $permalink, $site_url ) ) { /* * Sometimes site_url doesn't return the siteurl. See http://wordpress.org/support/topic/wp-super-cache-not-refreshing-post-after-comments-made */ $DONOTREMEMBER = 1; wp_cache_debug( "get_current_url_supercache_dir: warning! site_url ($site_url) not found in permalink ($permalink).", 1 ); if ( false === strpos( $permalink, $WPSC_HTTP_HOST ) ) { wp_cache_debug( "get_current_url_supercache_dir: WARNING! SERVER_NAME ({$WPSC_HTTP_HOST}) not found in permalink ($permalink). ", 1 ); $p = parse_url( $permalink ); if ( is_array( $p ) ) { $uri = $p[ 'path' ]; wp_cache_debug( "get_current_url_supercache_dir: WARNING! Using $uri as permalink. Used parse_url.", 1 ); } else { wp_cache_debug( "get_current_url_supercache_dir: WARNING! Permalink ($permalink) could not be understood by parse_url. Using front page.", 1 ); $uri = ''; } } else { wp_cache_debug( "get_current_url_supercache_dir: Removing SERVER_NAME ({$WPSC_HTTP_HOST}) from permalink ($permalink). Is the url right?", 1 ); $uri = str_replace( $WPSC_HTTP_HOST, '', $permalink ); $uri = str_replace( 'http://', '', $uri ); $uri = str_replace( 'https://', '', $uri ); } } else { $uri = str_replace( $site_url, '', $permalink ); if ( strpos( $uri, $wp_cache_home_path ) !== 0 ) $uri = rtrim( $wp_cache_home_path, '/' ) . $uri; } } else { $uri = strtolower( $wp_cache_request_uri ); } $uri = wpsc_deep_replace( array( '..', '\\', 'index.php', ), preg_replace( '/[ <>\'\"\r\n\t\(\)]/', '', preg_replace( "/(\?.*)?$/", '', $uri ) ) ); $dir = preg_replace( '/:.*$/', '', $WPSC_HTTP_HOST ) . $uri; // To avoid XSS attacks if ( function_exists( "apply_filters" ) ) { $dir = apply_filters( 'supercache_dir', $dir ); } else { $dir = do_cacheaction( 'supercache_dir', $dir ); } $dir = $cache_path . 'supercache/' . $dir . '/'; if( is_array( $cached_direct_pages ) && in_array( $_SERVER[ 'REQUEST_URI' ], $cached_direct_pages ) ) { $dir = ABSPATH . $uri . '/'; } $dir = str_replace( '..', '', str_replace( '//', '/', $dir ) ); wp_cache_debug( "supercache dir: $dir", 5 ); if ( $DONOTREMEMBER == 0 ) $saved_supercache_dir[ $post_id ] = $dir; return $dir; } function get_all_supercache_filenames( $dir = '' ) { global $wp_cache_mobile_enabled, $cache_path; $dir = realpath( $dir ); if ( substr( $dir, 0, strlen( $cache_path ) ) != $cache_path ) return array(); $filenames = array( 'index.html', 'index-https.html', 'index.html.php' ); if ( $dir != '' && isset( $wp_cache_mobile_enabled ) && $wp_cache_mobile_enabled ) { // open directory and look for index-*.html files if ( is_dir( $dir ) && $dh = @opendir( $dir ) ) { while ( ( $file = readdir( $dh ) ) !== false ) { if ( substr( $file, 0, 6 ) == 'index-' && strpos( $file, '.html' ) ) $filenames[] = $file; } closedir( $dh ); } } if ( function_exists( "apply_filters" ) ) { $filenames = apply_filters( 'all_supercache_filenames', $filenames ); } else { $filenames = do_cacheaction( 'all_supercache_filenames', $filenames ); } foreach( $filenames as $file ) { $out[] = $file; $out[] = $file . '.gz'; } return $out; } function supercache_filename() { //Add support for https and http caching $is_https = ( ( isset( $_SERVER[ 'HTTPS' ] ) && 'on' == strtolower( $_SERVER[ 'HTTPS' ] ) ) || ( isset( $_SERVER[ 'HTTP_X_FORWARDED_PROTO' ] ) && 'https' == strtolower( $_SERVER[ 'HTTP_X_FORWARDED_PROTO' ] ) ) ); //Also supports https requests coming from an nginx reverse proxy $extra_str = $is_https ? '-https' : ''; if ( function_exists( "apply_filters" ) ) { $extra_str = apply_filters( 'supercache_filename_str', $extra_str ); } else { $extra_str = do_cacheaction( 'supercache_filename_str', $extra_str ); } $filename = 'index' . $extra_str . '.html'; return $filename; } function get_oc_version() { $wp_cache_oc_key = wp_cache_get( "wp_cache_oc_key" ); if ( ! $wp_cache_oc_key ) { $wp_cache_oc_key[ 'key' ] = reset_oc_version(); } elseif ( $wp_cache_oc_key[ 'ts' ] < time() - 600 ) wp_cache_set( "wp_cache_oc_key", array( 'ts' => time(), 'key' => $wp_cache_oc_key[ 'key' ] ) ); return $wp_cache_oc_key[ 'key' ]; } function reset_oc_version( $version = 1 ) { if ( $version == 1 ) $version = mt_rand(); wp_cache_set( "wp_cache_oc_key", array( 'ts' => time(), 'key' => $version ) ); return $version; } function get_oc_key( $url = false ) { global $wp_cache_gzip_encoding, $WPSC_HTTP_HOST; if ( $url ) { $key = intval( $_SERVER[ 'SERVER_PORT' ] ) . strtolower( preg_replace( '/:.*$/', '', $WPSC_HTTP_HOST ) ) . $url; } else { $key = get_current_url_supercache_dir(); } return $key . $wp_cache_gzip_encoding . get_oc_version(); } function wp_supercache_cache_for_admins() { if ( isset( $_GET[ 'preview' ] ) || function_exists( "is_admin" ) && is_admin() ) return true; if ( false == do_cacheaction( 'wp_supercache_remove_cookies', true ) ) return true; $cookie_keys = array( 'wordpress_logged_in', 'comment_author_' ); if ( defined( 'LOGGED_IN_COOKIE' ) ) $cookie_keys[] = constant( 'LOGGED_IN_COOKIE' ); reset( $_COOKIE ); foreach( $_COOKIE as $cookie => $val ) { reset( $cookie_keys ); foreach( $cookie_keys as $key ) { if ( strpos( $cookie, $key ) !== FALSE ) { wp_cache_debug( 'Removing auth from $_COOKIE to allow caching for logged in user (' . $cookie . ')', 5 ); unset( $_COOKIE[ $cookie ] ); } } } } /* returns true/false depending on location of $dir. */ function wp_cache_confirm_delete( $dir ) { global $cache_path, $blog_cache_dir; // don't allow cache_path, blog cache dir, blog meta dir, supercache. $dir = realpath( $dir ); if ( $dir == $cache_path || $dir == $blog_cache_dir || $dir == $blog_cache_dir . "meta/" || $dir == $cache_path . "supercache" ) { return false; } else { return true; } } // copy of _deep_replace() to be used before WordPress loads function wpsc_deep_replace( $search, $subject ) { $subject = (string) $subject; $count = 1; while ( $count ) { $subject = str_replace( $search, '', $subject, $count ); } return $subject; } ?> readme.txt000066600000135200152133035240006545 0ustar00=== WP Super Cache === Contributors: donncha, automattic, kraftbj Tags: performance,caching,wp-cache,wp-super-cache,cache Tested up to: 4.7.3 Stable tag: 1.4.9 Requires at least: 3.0 A very fast caching engine for WordPress that produces static html files. == Description == This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts. The static html files will be served to the vast majority of your users, but because a user's details are displayed in the comment form after they leave a comment those requests are handled by the legacy caching engine. Static files are served to: 1. Users who are not logged in. 2. Users who have not left a comment on your blog. 3. Or users who have not viewed a password protected post. 99% of your visitors will be served static html files. Those users who don't see the static files will still benefit because they will see different cached files that aren't quite as efficient but still better than uncached. This plugin will help your server cope with a front page appearance on digg.com or other social networking site. If for some reason "supercaching" doesn't work on your server then don't worry. Caching will still be performed, but every request will require loading the PHP engine. In normal circumstances this isn't bad at all. Visitors to your site will notice no slowdown or difference. Supercache really comes into it's own if your server is underpowered, or you're experiencing heavy traffic. Super Cached html files will be served more quickly than PHP generated cached files but in every day use, the difference isn't noticeable. The plugin serves cached files in 3 ways (ranked by speed): 1. Mod_Rewrite. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve "supercached" static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are "lighter". This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file. Visits by anonymous or unknown users will be served this way. 2. PHP. Supercached static files can now be served by PHP. The plugin will serve a "supercached" file if it exists and it's almost as fast as the mod_rewrite method. It's easier to configure as the .htaccess file doesn't need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode. Your server may not cope as well with a really large amount of traffic. (You're gaming Digg aren't you? You'll need mod_rewrite, the rest of us are ok with PHP!) 3. Legacy caching. This is mainly used to cache pages for known users. These are logged in users, visitors who leave comments or those who should be shown custom per-user data. It's the most flexible caching method but also the slowest. As each page is different it's often better not to cache pages for these users at all and avoid legacy caching. Legacy caching will also cache visits by unknown users if this caching mode is selected. You can have dynamic parts to your page in this mode too. If you're new to caching use PHP caching. It's easy to set up and very fast. Avoid legacy caching if you can. = Recommended Settings = Advanced users will probably want to use mod_rewrite caching, but PHP caching is almost as good and recommended for everyone else. Enable the following: 1. PHP caching. 2. Compress pages. 3. Don't cache pages for known users. 4. Cache rebuild. 5. CDN support. 6. Extra homepage checks. Garbage collection is the act of cleaning up cache files that are out of date and stale. There's no correct value for the expiry time but a good starting point is 1800 seconds if you're not using legacy mode. If you are using that mode start with an expiry time of 600 seconds. If you are not using legacy mode caching consider deleting the contents of the "Rejected User Agents" text box and allow search engines to create supercache static files. Likewise, preload as many posts as you can and enable "Preload Mode". Garbage collection will still occur but it won't affect the preloaded files. If you don't care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren't recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files. With preloading on cached files will still be deleted when posts are made or edited or comments made. See the [WP Super Cache homepage](https://wordpress.org/plugins/wp-super-cache/) for further information. [Developer documentation](http://z9.io/wp-super-cache-developers/) is also available for those who need to interact with the cache or write plugins. There's a [GIT repository](https://github.com/Automattic/wp-super-cache) too if you want to contribute a patch. The [changelog](http://svn.wp-plugins.org/wp-super-cache/trunk/Changelog.txt) is a good place to start if you want to know what has changed since you last downloaded the plugin. Interested in translating WP Super Cache to your language? Grab the [development version](http://downloads.wordpress.org/plugin/wp-super-cache.zip) where you will find an up to date wp-super-cache.pot. Send any translation files to donncha @ ocaoimh.ie and thank you! The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them. == Upgrade Notice == = 1.4.9 = Fixed XSS on the settings page, settings page updates, file locking fixes and PHP 7.1 fix, caching fixes on static homepage blogs and more. == Changelog == = 1.4.9 = * Fixed bug when not running sem_remove after sem_release. See https://github.com/Automattic/wp-super-cache/issues/85 * Fixed a PHP error impacting PHP 7.1. * Fixed a bug where we cached PUT and DELETE requests. We're treating them like POST requests now. * Delete supercache cache files, even when supercache is disabled, because mod_rewrite rules might still be active. * Updated the settings page, moving things around. [#173](https://github.com/Automattic/wp-super-cache/pull/173) * Make file locking less attractive on the settings page and fixed the WPSC_DISABLE_LOCKING constant so it really disables file locking even if the user has enabled it already. * Added a WPSC_REMOVE_SEMAPHORE constant that must be defined if sem_remove() is to be used as it may cause problems. [#174](https://github.com/Automattic/wp-super-cache/pull/174) * Added a "wpsc_delete_related_pages_on_edit" filter that on returning 0 will disable deletion of pages outside of page being edited. [#175](https://github.com/Automattic/wp-super-cache/pull/175) * Fixed plugin deleting all cached pages when a site had a static homepage. [#175](https://github.com/Automattic/wp-super-cache/pull/175) * Make sure $cache_path has a trailing slash [#177](https://github.com/Automattic/wp-super-cache/pull/77) * Remove flush() [#127](https://github.com/Automattic/wp-super-cache/pull/127) but also check if headers are empty and flush and get headers again. [#179](https://github.com/Automattic/wp-super-cache/pull/179) * Add fix for customizer [#161](https://github.com/Automattic/wp-super-cache/pull/161) and don't cache PUT AND DELETE requests [#178](https://github.com/Automattic/wp-super-cache/pull/178) * Check for superglobals before using them. [#131](https://github.com/Automattic/wp-super-cache/pull/131) = 1.4.8 = * Removed malware URL in a code comment. (harmless to operation of plugin but gets flagged by A/V software) * Updated translation file. = 1.4.7 = * Update the settings page for WordPress 4.4. layout changes. = 1.4.6 = * Generate the file cache/.htaccess even when one exists so gzip rules are created and gzipped pages are served correctly. Props Tigertech. https://wordpress.org/support/topic/all-website-pages-downloading-gz-file-after-latest-update?replies=36#post-7494087 = 1.4.5 = * Enhancement: Only preload public post types. Props webaware. * Added an uninstall function that deletes the config file. Deactivate function doesn't delete it any more. * Possible to deactivate the plugin without visiting the settings page now. * Fixed the cache rebuild system. Rebuild files now survive longer than the request that generate them. * Minor optimisations: prune_super_cache() exits immediately if the file doesn't exist. The output of wp_cache_get_cookies_values() is now cached. * Added PHP pid to the debug log to aid debugging. * Various small bug fixes. * Fixed reset of expiry time and GC settings when updating advanced settings. * Removed CacheMeta class to avoid APC errors. It's not used any more. * Fixed reset of advanced settings when using "easy" settings page. * Fixed XSS in settings page. * Hide cache files when servers display directory indexes. * Prevent PHP object injection through use of serialize(). = 1.4.4 = * Fixed fatal error in output handler if GET parameters present in query. Props webaware. * Fixed debug log. It wasn't logging the right message. = 1.4.3 = * Security release fixing an XSS bug in the settings page. Props Marc Montpas from Sucuri. * Added wp_debug_log(). Props Jen Heilemann. * Minor fixes. = 1.4.2 = * Fixed "acceptable file list". * Fixed "Don't cache GET requests" feature. * Maybe fixed "304 not modified" problem for some users. * Fixed some PHP warnings. = 1.4.1 = * Fixed XSS in settings page. Props Simon Waters, Surevine Limited. * Fix to object cache so entries may now be deleted when posts updated. (object cache still experimental) * Documentation updates and cleanup of settings page. = 1.4 = * Replace legacy mfunc/mnclude/dynamic-cached-content functionality with a "wpsc_cachedata" cacheaction filter. * Added dynamic-cache-test.php plugin example wpsc_cachedata filter plugin. * Delete post, tag and category cache when a post changes from draft to publish or vice versa. Props @Biranit. * Update advanced-cache.php and wp-config.php if wp-cache-phase1.php doesn't load, usually happening after migrating to a new hosting service. * Misc bugfixes. = 1.3.2 = * Any mfunc/mclude/dynamic-cached-content tags in comments are now removed. * Dynamic cached content feature disabled by default and must be enabled on the Advanced Settings page. * Support for the mobile theme in Jetpack via helper plugin on script's Plugins tab. = 1.3.1 = * Minor updates to documentation * Fixed XSS in settings page. = 1.3 = * mfunc tags could be executed in comments. Fixed. * More support for sites that use the LOGGED_IN_COOKIE constant and custom cookies. = 1.2 = * Garbage collection of old cache files is significantly improved. I added a scheduled job that keeps an eye on things and restarts the job if necessary. Also, if you enable caching from the Easy page garbage collection will be enabled too. * Editors can delete single cached files from the admin bar now. * Fixed the cached page counter on the settings page. * Some sites that updated to 1.0 experienced too much garbage collection. There are still stragglers out there who haven't upgraded but that's fixed now! * Supercached mobile files are now used as there was a tiny little typo that needed fixing. * If your site is in a directory and you saw problems updating a page then that should be fixed now. * The deactivate hook has been changed so your configuration isn.t hosed when you upgrade. Unfortunately this will only happen after you do this upgrade. * Some sites use custom cookies with the LOGGED_IN_COOKIE constant. Added support for that. * Added support for WPTouch Pro, but it appears to be flaky still. Anyone have time to work on that? I don.t. * Some sites had problems with scheduled posts. For some reason the plugin thought the post was in draft mode and then because it only checked the same post once, when the post magically became published the cache wasn.t cleared. That.s fixed, thanks to the debug logging of several patient users. * And more bug fixes and translation updates. = 1.1 = * Use $_SERVER[ 'SERVER_NAME' ] to create cache directories. * Only create blogs cached directories if valid requests and blogs exist. * Only clear current blog's cache files if navigation menu is modified * Added clean_post_cache action to clear cache on post actions * Removed garbage collection details on Contents tab * Added wp_cache_check_mobile cacheaction filter to shortcircuit mobile device check. * Don't delete cache files for draft posts * Added action on wp_trash_post to clear the cache when trashed posts are deleted * Show a warning when 304 browser caching is disabled (because mod_rewrite caching is on) * New check for safe mode if using less that PHP 5.3.0 * Added wp_supercache_remove_cookies filter to disable anonymous browsing mode. * Fixed garbage collection schedule dropdown * Fixed preload problem clearing site's cache on "page on front" sites. * Fix for PHP variable not defined warnings * Fixed problem refreshing cache when comments made as siteurl() sometimes didn't work * Preloading of taxonomies is now optional * Domain mapping fixes. * Better support for https sites. Remove https:// to get cache paths. * Added AddDefaultCharset .htaccess rule back in and added an option to remove it if required. * Added multisite plugin that adds a "Cached" column to Network->Sites to disable caching on a per site basis. * Added WPTouch plugin to modify browser and prefix list in mobile detection code. Added support for that plugin's exclude list. * Fixed cache tester * Filter the tags that are used to detect end-of-page using the wp_cache_eof_tags filter. * Removed debug level from logging as it wasn't helpful. * Removed mention of wp-minify. = 1.0 = * Removed AddDefaultCharset .htaccess rule * Fixed problem with blogs in a folder and don't have a trailing slash * New scheduling of garbage collection * Added a "Delete cache" link to admin bar to delete cache of current page. * Updated documentation * Sorry Digg, Stephen Fry power now! * Updated translations * Preload taxonomies and all post types except revisionsand nav menu items * Fixed previews by logged in users. * Added option to make logged in users anonymous * Use WP 3.0 variables to detect multisite installs * Hash filenames so files are served from the same CDNs = 0.9.9.9 = * Fixed typo, is_front_page. * Serve repeated static files from the same CDN hostname. * Updated translations. * Make supercache dir lowercase to avoid problems with unicode URLs. * Add option to skip https loaded static content. * Remove 5 second check on age of existing cache files. Should help with posts that get lots of comments and traffic. * Lots of bugs fixed. = 0.9.9.8 = * CDN updates: can be switched off, multiple CNAMEs. * Uninstall process improved. It removes generated files and fixes edited files. * Cached dynamic pages can now be stored in Supercache files and compressed. * 1and1 Webhosting fix (/kunden/) * Remove log by email functionality as it caused problems for users who were inundated by email * Many more minor fixes and changes. = 0.9.9.6 = * Fixed problem serving cached files with PHP * Added support for 304 "file not modified" header to help browser caching. (PHP caching only) * Added French & German translations, updated Italian translation and fixed translation strings. * Sleep 4 seconds between preload urls to reduce load on the server * Updated docs and FAQs. = 0.9.9.5 = * Disable compression on on easy setup page. Still causes problems on some hosts. * Remove footerlink on easy setup page. * Don't delete mod_rewrite rules when caching is disabled. * Don't stop users using settings page when in safe mode. = 0.9.9.4 = * Settings page split into tabbed pages. * Added new "Easy" settings page for new users. * New PHP caching mode to serve supercached files. * Mobile support fixes. * Added Domain mapping support plugin. * Added "awaiting moderation" plugin that removes that text from posts. * Terminology change. Changed "half on" to "legacy caching". * Fixed cache tester on some installs of WordPress. * Updated documentation * Added $wp_super_cache_lock_down config variable to hide lockdown and directly cached pages admin items. * Preloaded checks if it has stalled and reschedules the job to continue. * Serve the gzipped page when first cached if the client supports compression. * Lots more bug fixes.. = 0.9.9.3 = * Fixed division by zero error in half on mode. * Always show "delete cache" button. * Fixed "Update mod_rewrite rules" button. * Minor text changes to admin page. = 0.9.9.2 = * Forgot to change version number in wp-cache.php = 0.9.9.1 = * Added preloading of static cache. * Better mobile plugin support * .htaccess rules can be updated now. Added wpsc_update_htaccess(). * Fixed "page on front" cache clearing bug. * Check for wordpress_logged_in cookie so test cookie isn't detected. * Added clear_post_supercache() to clear supercache for a single post. * Put quotes around rewrite rules in case paths have spaces. = 0.9.9 = * Added experimental object cache support. * Added Chinese(Traditional) translation by Pseric. * Added FAQ on WP-Cache vs Supercache files. * Use Supercache file if WP-Cache file not found. Useful if mod_rewrite rules are broken or not working. * Get mobile browser list from WP Mobile Edition if found. Warn user if .htaccess out of date. * Make sure writer lock is unlocked after writing cache files. * Added link to developer docs in readme. * Added Ukranian translation by Vitaly Mylo. * Added Upgrade Notice section to readme. * Warn if zlib compression in PHP is enabled. * Added compression troubleshooting answer. Props Vladimir (http://blog.sjinks.pro/) * Added Japanese translation by Tai (http://tekapo.com/) * Updated Italian translation. * Link to WP Mobile Edition from admin page for mobile support. = 0.9.8 = * Added Spanish translation by Omi. * Added Italian translation by Gianni Diurno. * Addded advanced debug code to check front page for category problem. Enable by setting $wp_super_cache_advanced_debug to 1 in the config file. * Fixed wordpress vs wordpress_logged_in cookie mismatch in cookie checking function. * Correctly check if WP_CACHE is set or not. PHP is weird. * Added wp_cache_clear_cache() to clear out cache directory. * Only show logged in message when debugging enabled. * Added troubleshooting point 20. PHP vs Apache user. * Fixed problem deleting cache file. * Don't delete cache files when moderated comments are deleted. = 0.9.7 = * Fixed problem with blogs in folders. * Added cache file listing and delete links to admin page. * Added "Newest Cached Pages" listing in sidebox. * Made admin page translatable. * Added "How do I make certain parts of the page stay dynamic?" to FAQ. * Advanced: added "late init" feature so that plugin activates on "init". Set $wp_super_cache_late_init to true in config file to use. * Disable supercaching when GET parameters present instead of disabling all caching. Disable on POST (as normal) and preview. * Fixed problem with cron job and mutex filename. * Warn users they must enable mobile device support if rewrite rules detected. Better detection of when to warn that .htaccess rules must be updated (no need when rewrite rules not present) * Advanced: Added "wpsupercache_404" filter. Return true to cache 404 error pages. * Use the wordpress_test_cookie in the cache key. * Show correct number of cache files when compression off. * Fixed problem with PHP safe_mode detection. * Various bugfixes and documentation updates. See Changelog.txt = 0.9.6.1 = * Move "not logged in" message init below check for POST. * Add is_admin() check so plugin definitely can't cache the backend. * Add "do not cache" page type to admin page. = 0.9.6 = * Add uninstall.php uninstall script. * Updated cache/.htaccess rules (option to upgrade that) * Added FAQ about category and static homepage problem. * Add wp_cache_user_agent_is_rejected() back to wp-cache-phase2.php * Show message for logged in users when caching disable for them. * Check filemtime on correct supercache file = 0.9.5 = * Show next and last GC times in minutes, not local time. * Don't serve wp_cache cache files to rejected user agents. Supercache files are still served to them. * If enabled, mobile support now serves php cached files to mobile clients and static cached files to everyone else. * Added checks for "WPSC_DISABLE_COMPRESSION" and "WPSC_DISABLE_LOCKING" constants to disable compression and file locking. For hosting companies primarily. * Added check for DONOTCACHEPAGE constant to avoid caching a page. * Use PHP_DOCUMENT_ROOT when creating .htaccess if necessary. = 0.9.4.3 = 1. Added "Don't cache for logged in users" option. 2. Display file size stats on admin page. 3. Clear the cache when profile page is updated. 4. Don't cache post previews. 5. Added backslashes to rejected URI regex list. 6. Fixed problems with posts and comments not refreshing. == Installation == Install like any other plugin, directly from your plugins page but make sure you have custom permalinks enabled. Go to the plugin settings page at Settings->WP Super Cache and enable caching. == How to uninstall WP Super Cache == Almost all you have to do is deactivate the plugin on the plugins page. The plugin should clean up most of the files it created and modified, but it doesn't as yet remove the mod_rewrite rules from the .htaccess file. Look for the section in that file marked by SuperCache BEGIN and END tags. The plugin doesn't remove those because some people add the WordPress rules in that block too. To manually uninstall: 1. Turn off caching on the plugin settings page and clear the cache. 2. Deactivate the plugin on the plugins page. 3. Remove the WP_CACHE define from wp-config.php. It looks like `define( 'WP_CACHE', true );` 4. Remove the Super Cache mod_rewrite rules from your .htaccess file. 5. Remove the files wp-content/advanced-cache.php and wp-content/wp-cache-config.php 6. Remove the directory wp-content/cache/ 7. Remove the directory wp-super-cache from your plugins directory. == If all else fails and your site is broken == 1. Remove the WP_CACHE define from wp-config.php. It looks like `define( 'WP_CACHE', true );` 2. Remove the rules (see above) that the plugin wrote to the .htaccess file in your root directory. 3. Delete the wp-super-cache folder in the plugins folder. 4. Optionally delete advanced-cache.php, wp-cache-config.php and the cache folder in wp-content/. == Frequently Asked Questions == = How do I know my blog is being cached? = Go to Settings->WP Super Cache and look for the "Cache Tester" form on the easy settings page. Click "Test Cache" and the plugin will request the front page of the site twice, comparing a timestamp on each to make sure they match. If you want to do it manually, enable debugging in the plugin settings page and load the log file in a new browser tab. Then view your blog while logged in and logged out. You should see activity in the log. View the source of any page on your site. When a page is first created, you'll see the text "Dynamic page generated in XXXX seconds." and "Cached page generated by WP-Super-Cache on YYYY-MM-DD HH:MM:SS" at the end of the source code. On reload, a cached page will show the same timestamp so wait a few seconds before checking. In legacy caching mode, if you have compression enabled, the text "Compression = gzip" will be added. If compression is disabled and the page is served as a static html file, the text "super cache" will be added. The only other way to check if your cached file was served by PHP script or from the static cache is by looking at the HTTP headers. PHP cached pages will have the header "WP-Super-Cache: Served supercache file from PHP". Legacy cached files will have the header, "WP-Super-Cache: Served legacy cache file". I used the Live HTTP Headers extension for Firefox to examine the headers. You should also check your cache directory in wp-content/cache/supercache/hostname/ for static cache files. If the plugin rules are missing from your .htaccess file, the plugin will attempt to serve the super cached page if it's found. The header "WP-Super-Cache: Served supercache file from PHP" if this happens. = Legacy (WP-Cache) vs Supercache files = WP-Cache files are stored in wp-content/cache/ (or on MU sites in a blogs sub directory) and are named wp-cache-XXXXXXXXXXXXXXXXX.html. Associated meta files are stored in a meta sub directory. Those files contain information about the cached file. These files are generated by the "legacy caching" code in the plugin. Supercache files are stored in wp-content/cache/supercache/HOSTNAME/ where HOSTNAME is your domain name. The files are stored in directories matching your site's permalink structure. = Will comments and other dynamic parts of my blog update immediately? = Comments will show as soon as they are moderated, depending on the comment policy of the blog owner. Other dynamic elements on a page may not update unless they are written in Javascript, Flash, Java or another client side browser language. The plugin really produces static html pages. No PHP is executed when those pages are served. "Popularity Contest" is one such plugin that will not work. = Will the Super Cache compression slow down my server? = No, it will do the opposite. Super Cache files are compressed and stored that way so the heavy compression is done only once. These files are generally much smaller and are sent to a visitor's browser much more quickly than uncompressed html. As a result, your server spends less time talking over the network which saves CPU time and bandwidth, and can also serve the next request much more quickly. = How do I make certain parts of the page stay dynamic? = Note: this functionality is disabled by default. You will have to enable it on the Advanced Settings page. There are 2 ways of doing this. You can use Javascript to draw the part of the page you want to keep dynamic. That's what Google Adsense and many widgets from external sites do and is the recommended way. Or you can use a WP Super Cache filter to do the job but you can't use mod_rewrite mode caching. You have to switch to PHP or legacy caching. WP Super Cache 1.4 introduced a cacheaction filter called wpsc_cachedata. The cached page to be displayed goes through this filter and allows modification of the page. If the page contains a placeholder tag the filter can be used to replace that tag with your dynamically generated html. The function that hooks on to the wpsc_cachedata filter should be put in a file in the WP Super Cache plugins folder unless you use the late_init feature. An example plugin is included. Edit [dynamic-cache-test.php](http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php) to see the example code. There are two example functions there. There's a simple function that replaces a string (or tag) you define when the cached page is served. The other example function uses an output buffer to generate the dynamic content. Due to a limitation in how PHP works the output buffer code MUST run before the wpsc_cachedata filter is hit, at least for when a page is cached. It doesn't matter when serving cached pages. See [this post](http://z9.io/y/6j) for a more technical and longer explanation. To execute WordPress functions you must enable the 'Late init' feature on the advanced settings page. = How do I use WordPress functions in cached dynamic pages? = = How do I delay serving the cache until the "init" action fires? = Cached files are served before almost all of WordPress is loaded. While that's great for performance it's a pain when you want to extend the plugin using a core part of WordPress. Enable 'Late init' mode on the Advanced settings page and cached files will be served when "init" fires. WordPress and it's plugins will be loaded now. = Why don't WP UserOnline, Popularity Contest, WP Postratings or plugin X not work or update on my blog now? = This plugin caches entire pages but some plugins think they can run PHP code every time a page loads. To fix this, the plugin needs to use Javascript/AJAX methods or the wpsc_cachedata filter described in the previous answer to update or display dynamic information. = Why do my WP Super Cache plugin disappear when I upgrade the plugin? = WordPress deletes the plugin folder when it updates a plugin. This is the same with WP Super Cache so any modified files in wp-super-cache/plugins/ will be deleted. You can define the variable $wp_cache_plugins_dir in wp-config.php or wp-content/wp-cache-config.php and point it at a directory outside of the wp-super-cache folder. The plugin will look there for it's plugins. = What does the Cache Rebuild feature do? = When a visitor leaves a comment the cached file for that page is deleted and the next visitor recreates the cached page. A page takes time to load so what happens if it receives 100 visitors during this time? There won't be a cached page so WordPress will serve a fresh page for each user and the plugin will try to create a cached page for each of those 100 visitors causing a huge load on your server. This feature stops this happening. The cached page is not cleared when a comment is left. It is marked for rebuilding instead. The next visitor within the next 10 seconds will regenerate the cached page while the old page is served to the other 99 visitors. The page is eventually loaded by the first visitor and the cached page updated. See [this post](http://z9.io/2009/01/23/wp-super-cache-089/) for more. = Why doesn't the plugin cache requests by search engine bots by default? = Those bots usually only visit each page once and if the page is not popular there's no point creating a cache file that will sit idle on your server. However if you're not using legacy caching you can allow these visits to be cached by removing the list of bots from "Rejected User Agents" on the Advanced settings page. = A category page is showing instead of my homepage = A tiny proportion of websites will have problems with the following configuration: 1. Uses a static page for the front page. 2. Uses /%category%/%postname%/ permalink structure. Sometimes a category page is cached as the homepage of the site instead of the static page. I can't [replicate the problem](http://wordpress.org/support/topic/237415/page/2?replies=38) but a simple solution is to switch the plugin to PHP mode. For normal traffic you will see no difference in the speed of your site. You can also enable "Extra homepage checks" on the Advanced Settings page. = Why do I get warnings about caching from http://ismyblogworking.com/ = "Your blog doesn't support client caching (no 304 response to If-modified-since)." "Your feed doesn't support caching (no 304 response to If-modified-since)" Supercache doesn't support 304 header checks in mod_rewrite mode but does support it in PHP mode. This is caching done by your browser, not the server. It is a check your browser does to ask the server if an updated version of the current page is available. If not, it doesn't download the old version again. The page is still cached by your server, just not by your visitors' browsers. Try the Cacheability Engine at http://www.ircache.net/cgi-bin/cacheability.py or http://redbot.org/ for further analysis. = How should I best use the utm_source tracking tools in Google Analytics with this plugin? = That tracking adds a query string to each url linked from various sources like Twitter and feedreaders. Unfortunately it stops pages being supercached. See [Joost's comment here](http://z9.io/remove-unused-utmsource-urls/#comment-672813) for how to turn it into an anchor tag which can be supercached. = The plugin complains that wp-content is writable! htdocs is writable! = It's not good when the web server can write to these directories but sometimes shared hosting accounts are set up in this way to make administration easier. Use `chmod 755 directory` to fix the permissions or find the permissions section of your ftp client. This [Google search](http://www.google.ie/search?sourceid=chrome&ie=UTF-8&q=ftp+fix+directory+permissions+755) will lead you to more information on this topic and there's also [this codex page](http://codex.wordpress.org/Changing_File_Permissions) too. Unfortunately some hosts require that those directories be writable. If that's the case just ignore this warning. = How do I delete the WP_CACHE define from wp-config.php? = Load your desktop ftp client and connect to your site. Navigate to the root (or the directory below it) of your site where you'll find wp-config.php. Download that file and edit it in a text editor. Delete the line `define( 'WP_CACHE', true );` and save the file. Now upload it, overwriting the wp-config.php on your server. = How do I delete the Super Cache rules from the .htaccess file? = Load your desktop ftp client and connect to your site. You may need to enable "Show hidden files" in the preferences of the ftp client. Navigate to the root of your site where you'll find the .htaccess file. Download that file and edit it in a text editor. Delete the lines between "# BEGIN WPSuperCache" and "# END WPSuperCache" and save the file. Now upload it, overwriting the .htaccess file on your server. = How do I change file permissions? = This [page](http://codex.wordpress.org/Changing_File_Permissions) on the WordPress Codex explains everything you need to know about file permissions on your server and various ways of changing them. = Why do I get load spikes when new posts are made? = You may have the "clear all cached files when new posts are made" option set. Clearing those files can take time plus your visitors will now be visiting uncached pages. Are you using Google Analytics campaign tracking with utm_source in the url? Those pages aren't cached. See the question, "How should I best use the utm_source tracking tools in Google Analytics with this plugin" above for how to use them properly. Cached pages have to be refreshed when posts are made. Perhaps your server just isn't up to the job of serving the amount of traffic you get. Enable the "cache rebuild" feature as that may help. = How many pages can I cache? = The only real limit are limits defined by your server. For example, EXT2 and EXT3 allow a maximum of 31,999 sub directories so if you have a flat permalink structure (like /%POSTNAME%/) and more than 32,000 posts you may run into problems. Likewise, if you run a multisite network and have more than 31,999 sites (blogs) you won't be able to cache all of them. Realistically if you had that many active sites you wouldn't be running on one server. = How do I serve cached mobile pages to clients on small screens like phones and tablets? = You'll have to use a separate mobile plugin to render a page formatted for those visitors. The following plugins have been tested but YMMV depending on mobile client. * [Jetpack's Mobile Theme Module](http://wordpress.org/plugins/jetpack) * [WPTouch](http://wordpress.org/plugins/wptouch/) * [WordPress Mobile Edition](http://wordpress.org/plugins/wordpress-mobile-edition/) * [WordPress Mobile Pack](http://wordpress.org/plugins/wordpress-mobile-pack/) (can't have "Don't cache pages for known users." enabled) = Troubleshooting = If things don't work when you installed the plugin here are a few things to check: 1. Is wp-content writable by the web server? 2. Is there a wp-content/wp-cache-config.php ? If not, copy the file wp-super-cache/wp-cache-config-sample.php to wp-content/wp-cache-config.php and make sure WPCACHEHOME points at the right place. 3. Is there a wp-content/advanced-cache.php ? If not, then you must copy wp-super-cache/advanced-cache.php into wp-content/. You must edit the file and change the path so it points at the wp-super-cache folder. 4. If pages are not cached at all, remove wp-content/advanced-cache.php and recreate it, following the advice above. 5. Make sure the following line is in wp-config.php and it is ABOVE the "require_once(ABSPATH.'wp-settings.php');" line: `define( 'WP_CACHE', true );` 6. Try the Settings->WP Super Cache page again and enable cache. 7. Look in wp-content/cache/supercache/. Are there directories and files there? 8. Anything in your php error_log? 9. If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there. 10. The plugin does not work very well when PHP's safe mode is active. This must be disabled by your administrator. 11. If pages are randomly super cached and sometimes not, your blog can probably be viewed with and without the "www" prefix on the URL. You should choose one way and install the [Enforce www preference](http://txfx.net/code/wordpress/enforce-www-preference/) plugin if you are using an old WordPress install. The latest versions redirect themselves (you should always be running the latest version of WordPress anyway!) 12. Private Server users at Dreamhost should edit wp-content/wp-cache-config.php and set the cache dir to "/tmp/" if they are getting errors about increasing CPU usage. See this [discussion](http://wordpress.org/support/topic/145895?replies=42) for more. 13. File locking errors such as "failed to acquire key 0x152b: Permission denied in..." or "Page not cached by WP Super Cache. Could not get mutex lock." are a sign that you may have to use file locking. Edit wp-content/wp-cache-config.php and uncomment "$use_flock = true" or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort. 14. Make sure cache/wp_cache_mutex.lock is writable by the web server if using coarse file locking. 15. The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine. 16. Garbage collection of old cache files won't work if WordPress can't find wp-cron.php. If your hostname resolves to 127.0.0.1 it could be preventing the garbage collection from working. Check your access_logs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code? If it's 404 or you don't see wp-cron.php anywhere WordPress may be looking for that script in the wrong place. You should speak to your server administator to correct this or edit /etc/hosts on Unix servers and remove the following line. Your hostname must resolve to the external IP address other servers on the network/Internet use. See http://yoast.com/wp-cron-issues/ for more. A line like "127.0.0.1 localhost localhost.localdomain" is ok. `127.0.0.1 myhostname.com` 17. If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don't use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site. 18. The error message, "WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed!" appears at the end of every page. Open the file wp-content/advanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content/plugins/wp-super-cache/. If it is not correct the caching engine will not load. 19. Caching doesn't work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Or use the plugin in PHP or legacy caching mode. 20. If supercache cache files are generated but not served, check the permissions on all your wp-content/cache/supercache folders (and each of wp-content cache and supercache folders) and wp-content/cache/.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache. `umask( 0022 );` 21. If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it's "Off" or add this line to your .htaccess: `php_flag zlib.output_compression off` If that doesn't work, add this line to your wp-config.php: `ini_set('zlib.output_compression', 0);` 22. The "white screen of death" or a blank page when you visit your site is almost always caused by a PHP error but [it may also be caused by APC](http://www.johnberns.com/2010/03/19/wp-super-cache-blank-page-problem-fixed/). Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache. 23. After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again. 24. If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag? 25. Your front page is ok but posts and pages give a 404? Go to Settings->permalinks and click "Save" once you've selected a custom permalink structure. You may need to manually update your .htaccess file. 26. If certain characters do not appear correctly on your website your server may not be configured correctly. You need to tell visitors what character set is used. Go to Settings->Reading and copy the 'Encoding for pages and feeds' value. Edit the .htaccess file with all your Supercache and WordPress rewrite rules and add this at the top, replacing CHARSET with the copied value. (for example, 'UTF-8') `AddDefaultCharset CHARSET` 27. Use [Cron View](http://wordpress.org/plugins/cron-view/) to help diagnose garbage collection and preload problems. Use the plugin to make sure jobs are scheduled and for what time. Look for the wp_cache_gc and wp_cache_full_preload_hook jobs. 18. The error message, "WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory." appears at the end of every page. You can delete wp-content/advanced-cache.php and reload the plugin settings page or edit wp-config.php and look for WPCACHEHOME and make sure it points at the wp-super-cache folder. This will normally be wp-content/plugins/wp-super-cache/ but you'll likely need the full path to that file (so it's easier to let the settings page fix it). If it is not correct the caching engine will not load. 19. If your server is running into trouble because of the number of semaphores used by the plugin it's because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it. == CDN == A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a "poor man's CDN" by using a sub domain of your domain to serve static files too. [OSSDL CDN off-linker](http://wordpress.org/plugins/ossdl-cdn-off-linker/) has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support [origin pull](http://www.google.com/search?hl=en&q=%22origin+pull%22). This means the CDN will download the file automatically from your server when it's first requested, and will continue to serve it for a configurable length of time before downloading it again from your server. Configure this on the "CDN" tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN. == Custom Caching == It is now possible to hook into the caching process using the add_cacheaction() function. Three hooks are available: 1. 'wp_cache_get_cookies_values' - modify the key used by WP Cache. 2. 'add_cacheaction' - runs in phase2. Allows a plugin to add WordPress hooks. 3. 'cache_admin_page' - runs in the admin page. Use it to modify that page, perhaps by adding new configuration options. There is one regular WordPress filter too. Use the "do_createsupercache" filter to customize the checks made before caching. The filter accepts one parameter. The output of WP-Cache's wp_cache_get_cookies_values() function. See plugins/searchengine.php as an example I use for my [No Adverts for Friends](http://z9.io/no-adverts-for-friends/) plugin. == Links == [WP Widget Cache](http://wordpress.org/plugins/wp-widget-cache/) is another caching plugin for WordPress. This plugin caches the output of widgets and may significantly speed up dynamic page generation times. == Updates == Updates to the plugin will be posted here, to [Holy Shmoly!](http://z9.io/) and the [WP Super Cache homepage](https://wordpress.org/plugins/wp-super-cache/) will always link to the newest version. == Thanks == I would sincerely like to thank [John Pozadzides](http://onemansblog.com/) for giving me the idea for this, for writing the "How it works" section and for testing the plugin through 2 front page appearances on digg.com Thanks to James Farmer and Andrew Billits of [Edu Blogs](http://edublogs.org/) fame who helped me make this more WordPress MU friendly. Translators who did a great job converting the text of the plugin to their native language. Thank you! * [Gianni Diurno](http://gidibao.net/) (Italian) * [Omi](http://equipajedemano.info/) (Spanish) * [tomchen1989](http://emule-fans.com/) and [Christopher Meng](http://cicku.me) (Simplified Chinese) * Tai (Japanese) * [Vitaly](http://pressword.com.ua/wordpress/) (Ukranian) * [Pseric](http://pseric.com/) and [Priv](http://priv.tw/blog) (Traditional Chinese) * [Ma�tre M�](http://maitremo.fr/) (French) * [Mathias Roth](http://trade-service.eu/) (German) * Bar�� �nver (Turkish) * [Elvis Fweb](http://wp.turkenichev.ru/) (Russian) * Fredrik Fors�ll (Swedish) * [Alyona Lompar](http://wwww.webhostinggeeks.com/) (Ukranian) * [Nata Strazda](http://www.webhostingrating.com/) (Lithuanian) * [Alexander Alexandrov](http://www.designcontest.com/) (Belarusian) * [Michail Bogdanov](http://www.webhostinghub.com/) (Romanian) * [Anja Skrba](http://science.webhostinggeeks.com/wordpress-super-cache) (Serbo-Croatian) plugins/badbehaviour.php000066600000006656152133035240011410 0ustar00

    ' . sprintf( __( '(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") ', 'wp-super-cache' ), WP_CONTENT_DIR ) . '

    '; if ( isset( $changed ) && $changed ) { if ( $cache_badbehaviour ) $status = __( "enabled" ); else $status = __( "disabled" ); echo "

    " . sprintf( __( "Bad Behavior support is now %s", 'wp-super-cache' ), $status ) . "

    "; } echo '
    '; wp_nonce_field('wp-cache'); ?>
    " . __( 'Warning!', 'wp-super-cache' ) . " $err

    "; } add_cacheaction( 'cache_admin_page', 'wp_supercache_badbehaviour_admin' ); ?> plugins/dynamic-cache-test.php000066600000017373152133035240012415 0ustar00", $cachedata ); } add_cacheaction( 'wpsc_cachedata', 'dynamic_cache_test_filter' ); function dynamic_cache_test_template_tag() { echo DYNAMIC_CACHE_TEST_TAG; // This is the template tag } function dynamic_cache_test_init() { add_action( 'wp_footer', 'dynamic_cache_test_template_tag' ); } add_cacheaction( 'add_cacheaction', 'dynamic_cache_test_init' ); } /* * EXAMPLE 2 * * This is going to be complicated. Hang on! * * When the cache file for a new page is generated the plugin uses an output * buffer to capture the page. A callback function processes the buffer and * writes to the cache file. The placeholder tag for any dynamic content has * to be written to that cache file but also, it has to be replaced with * dynamic content before the page is shown to the user. * More on output buffers here: http://php.net/ob_start * * Unfortunately an extra output buffer is often required when capturing dynamic * content such as sidebar widgets. Due to a quirk of the way PHP works it's * not possible to have an output buffer run in an output buffer callback. That * dynamic content has to be generated before the callback function is reached. * The following error occurs when an output buffer is created in the * callback function of another output buffer: * "PHP Fatal error: ob_start(): Cannot use output buffering in output buffering display handlers in..." * * In this example the function add_action() isn't available when this file is * loaded so dynamic_output_buffer_init() is hooked on to the "add_cacheaction" * cacheaction. That function then hooks dynamic_output_buffer_test() on to the * familiar wp_footer action. * * The first time dynamic_output_buffer_test() runs it generates the dynamic * content and captures it with ob_start() in the DYNAMIC_OB_TEXT constant. * * When the main WP Super Cache output buffer is ready the callback is called. * This fires the wpsc_cachedata_safety filter. If the DYNAMIC_OB_TEXT constant * is set, which means dynamic content is ready, then it returns 1, a signal * that everything is ok. * Finally, the wpsc_cachedata filter is run. The function * dynamic_output_buffer_test() is hooked on to it. Since DYNAMIC_OB_TEXT is * set it replaces the placeholder text with that constant. * The resulting html is then sent to the browser. * * Already cached pages call the safety filter, and then the wpsc_cachedata * filter so any hooked function must be ready to generate dynamic content. The * very last line of dynamic_output_buffer_test() replaces the placeholder tag * with the dynamic content in the cache file. * * * Use an output buffer to capture dynamic content while the page is generated * and insert into the right place: * Remember to add the DYNAMIC_OUTPUT_BUFFER_TAG text (as defined below) to * your theme where the dynamic content should be. * * dynamic_output_buffer_test() is a function that uses the wpsc_cachedata * filter to add a small message and the current server time to every web * page. The time increments on every reload. * */ define( 'DYNAMIC_OUTPUT_BUFFER_TAG', '' ); // Change this to a secret placeholder tag if ( DYNAMIC_OUTPUT_BUFFER_TAG != '' ) { function dynamic_output_buffer_test( &$cachedata = 0 ) { if ( defined( 'DYNAMIC_OB_TEXT' ) ) return str_replace( DYNAMIC_OUTPUT_BUFFER_TAG, DYNAMIC_OB_TEXT, $cachedata ); ob_start(); // call the sidebar function, do something dynamic echo "

    This is a test. The current time on the server is: " . date( 'H:i:s' ) . "

    "; $text = ob_get_contents(); ob_end_clean(); if ( $cachedata === 0 ) { // called directly from the theme so store the output define( 'DYNAMIC_OB_TEXT', $text ); } else // called via the wpsc_cachedata filter. We only get here in cached pages in wp-cache-phase1.php return str_replace( DYNAMIC_OUTPUT_BUFFER_TAG, $text, $cachedata ); } add_cacheaction( 'wpsc_cachedata', 'dynamic_output_buffer_test' ); function dynamic_output_buffer_init() { add_action( 'wp_footer', 'dynamic_output_buffer_test' ); } add_cacheaction( 'add_cacheaction', 'dynamic_output_buffer_init' ); function dynamic_output_buffer_test_safety( $safety ) { if ( defined( 'DYNAMIC_OB_TEXT' ) ) // this is set when you call dynamic_output_buffer_test() from the theme return 1; // ready to replace tag with dynamic content. else return 0; // tag cannot be replaced. } add_cacheaction( 'wpsc_cachedata_safety', 'dynamic_output_buffer_test_safety' ); } ?> plugins/jetpack.php000066600000006161152133035240010365 0ustar00

    " . sprintf( __( "Jetpack not found in %s. Install it and enable the mobile theme and this helper plugin to cache visits by mobile visitors." ), dirname( WPCACHEHOME ) ) . ""; } else { ?>
    ' . __( 'Provides support for the Jetpack mobile theme and plugin. PHP caching mode and mobile support will be enabled too.', 'wp-super-cache' ) . '

    '; if ( isset( $changed ) && $changed ) { if ( $cache_jetpack ) $status = __( "enabled" ); else $status = __( "disabled" ); echo "

    " . sprintf( __( "Jetpack Mobile Theme support is now %s", 'wp-super-cache' ), $status ) . "

    "; } echo '
    '; wp_nonce_field('wp-cache'); ?>
    plugins/searchengine.php000066600000006772152133035240011407 0ustar00

    ' . __( 'Provides support for No Adverts for Friends.', 'wp-super-cache' ) . '

    '; if ( isset( $changed ) && $changed ) { if ( 'yes' == $cache_no_adverts_for_friends ) $status = __( "enabled" ); else $status = __( "disabled" ); echo "

    " . sprintf( __( "No Adverts for Friends support is now %s", 'wp-super-cache' ), $status ) . "

    "; } echo '
    '; wp_nonce_field('wp-cache'); ?>
    plugins/awaitingmoderation.php000066600000004453152133035240012633 0ustar00

    " . sprintf( __( "Awaiting Moderation is now %s", 'wp-super-cache' ), $status ) . "

    "; } echo '
    '; wp_nonce_field('wp-cache'); ?>
    plugins/wptouch.php000066600000011200152133035240010423 0ustar00

    ' . __( 'Provides support for WPTouch mobile theme and plugin.', 'wp-super-cache' ) . '

    '; if ( isset( $changed ) && $changed ) { if ( $cache_wptouch ) $status = __( "enabled" ); else $status = __( "disabled" ); echo "

    " . sprintf( __( "WPTouch support is now %s", 'wp-super-cache' ), $status ) . "

    "; } echo '
    '; wp_nonce_field('wp-cache'); ?>

    ' . __('WPTouch plugin detected! Please go to the Supercache plugins page and enable the WPTouch helper plugin.', 'wp-super-cache' ) . '

    '; } function wp_super_cache_wptouch_exists() { global $cache_wptouch; if ( $cache_wptouch == 1 ) return false; if ( is_admin() && function_exists( 'wptouch_get_plugin_dir_name' ) ) add_action( 'admin_notices', 'wp_super_cache_wptouch_notice' ); } if ( isset( $_GET[ 'page' ] ) && $_GET[ 'page' ] == 'wpsupercache' ) { add_cacheaction( 'add_cacheaction', 'wp_super_cache_wptouch_exists' ); } // disable mobile checking if function wp_super_cache_maybe_disable_wptouch( $t ) { global $cache_wptouch, $wptouch_exclude_ua; if ( $cache_wptouch != 1 ) return false; if ( ( isset( $_COOKIE[ 'wptouch_switch_toggle' ] ) && $_COOKIE[ 'wptouch_switch_toggle' ] == 'normal' ) || ( isset( $_COOKIE[ 'wptouch-pro-view' ] ) && $_COOKIE[ 'wptouch-pro-view' ] == 'desktop' ) ) return true; $ua = explode( ",", $wptouch_exclude_ua ); foreach( $ua as $agent ) { if ( preg_match( "#$agent#i", $_SERVER[ 'HTTP_HOST' ] ) ) return true; // disable mobile ua check if matches the exclude list in wptouch } return false; } add_cacheaction( 'disable_mobile_check', 'wp_super_cache_maybe_disable_wptouch' ); function wp_super_cache_wptouch_browsers( $browsers ) { global $cache_wptouch, $wptouch_exclude_ua, $wp_cache_config_file; if ( false == function_exists( 'bnc_wptouch_get_exclude_user_agents' ) || false == function_exists( 'bnc_wptouch_get_user_agents' ) ) return $browsers; $browsers = implode( ',', bnc_wptouch_get_exclude_user_agents() ); // hack, support exclude agents too if ( $browsers != $wptouch_exclude_ua ) { wp_cache_replace_line('^ *\$wptouch_exclude_ua', "\$wptouch_exclude_ua = '$browsers';", $wp_cache_config_file); $wptouch_exclude_ua = $browsers; } return bnc_wptouch_get_user_agents(); } function wp_super_cache_wptouch_prefixes( $prefixes ) { return array(); // wptouch doesn't support UA prefixes } function wp_super_cache_wptouch_cookie_check( $cache_key ) { if ( false == isset( $_COOKIE[ 'wptouch_switch_toggle' ] ) ) return $cache_key; if ( $_COOKIE[ 'wptouch_switch_toggle' ] == 'normal' || $_COOKIE[ 'wptouch_switch_toggle' ] == 'mobile' ) return $_COOKIE[ 'wptouch_switch_toggle' ]; if ( isset( $_COOKIE[ 'wptouch-pro-view' ] ) ) { if ( $_COOKIE[ 'wptouch-pro-view' ] == 'desktop' ) return 'normal'; else return $_COOKIE[ 'wptouch-pro-view' ]; } return $cache_key; } if ( isset( $cache_wptouch ) && $cache_wptouch == 1 ) { add_cacheaction( 'wp_super_cache_mobile_browsers', 'wp_super_cache_wptouch_browsers' ); add_cacheaction( 'wp_super_cache_mobile_prefixes', 'wp_super_cache_wptouch_prefixes' ); add_cacheaction( 'wp_cache_check_mobile', 'wp_super_cache_wptouch_cookie_check' ); } ?> plugins/multisite.php000066600000004574152133035240010771 0ustar00 'enable_cache', 'id' => $blog_id ) ), 'wp-cache' . $blog_id ) . "'>" . __( 'Enable', 'wp-super-cache' ) . ""; } else { echo " 'disable_cache', 'id' => $blog_id ) ), 'wp-cache' . $blog_id ) . "'>" . __( 'Disable', 'wp-super-cache' ) . ""; } } function wp_super_cache_multisite_notice() { if ( isset( $_GET[ 'page' ] ) && $_GET[ 'page' ] == 'wpsupercache' ) echo '

    ' . __( 'Caching has been disabled on this blog on the Network Admin Sites page.', 'wp-super-cache' ) . '

    '; } function wp_super_cache_override_on_flag() { global $cache_enabled, $super_cache_enabled; if ( $cache_enabled != true ) return false; if ( get_option( 'wp_super_cache_disabled' ) ) { $cache_enabled = false; $super_cache_enabled = false; define( 'DONOTCACHEPAGE', 1 ); define( "SUBMITDISABLED", 'disabled style="color: #aaa" ' ); if ( is_admin() ) add_action( 'admin_notices', 'wp_super_cache_multisite_notice' ); } } ?> plugins/domain-mapping.php000066600000010651152133035240011643 0ustar00

    ' . __( 'Provides support for Domain Mapping plugin to map multiple domains to a blog.', 'wp-super-cache' ) . '

    '; if ( isset( $changed ) && $changed ) { if ( $cache_domain_mapping ) $status = __( "enabled" ); else $status = __( "disabled" ); echo "

    " . sprintf( __( "Domain Mapping support is now %s", 'wp-super-cache' ), $status ) . "

    "; } echo '
    '; wp_nonce_field('wp-cache'); ?>

    ' . __('Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.', 'wp-super-cache' ) . '

    '; } function wp_supercache_domain_mapping_exists() { global $cache_domain_mapping; if ( $cache_domain_mapping == 1 ) return false; if ( is_admin() && function_exists( 'domain_mapping_warning' ) ) add_action( 'admin_notices', 'wp_supercache_domain_mapping_notice' ); } if ( isset( $_GET[ 'page' ] ) && $_GET[ 'page' ] == 'wpsupercache' ) { add_cacheaction( 'add_cacheaction', 'wp_supercache_domain_mapping_exists' ); } ?> ossdl-cdn.php000066600000024014152133035240007146 0ustar00

    wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.', 'wp-super-cache' ); ?>

    WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.', 'wp-super-cache' ), '' . $example_cdn_uri . '' ); ?>

    />

    / please.
    Example: %2$s.', 'wp-super-cache' ), get_option( 'siteurl' ), $example_cdn_uri ); ?>

    wp-content, wp-includes, which will be enforced if this field is left empty.', 'wp-super-cache' ); ?>

    .php, .flv, .do, and always include .php (default).', 'wp-super-cache' ); ?>

    CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$s', 'wp-super-cache' ), get_option( 'siteurl' ), $example_cnames ); ?>

    OSSDL CDN Off Linker by Mark Kubacki', 'wp-super-cache' ); ?>

    wp-cache-config-sample.php000066600000005572152133035240011501 0ustar00 'bot', 1 => 'ia_archive', 2 => 'slurp', 3 => 'crawl', 4 => 'spider', 5 => 'Yandex' ); $cache_rebuild_files = 1; // Disable the file locking system. // If you are experiencing problems with clearing or creating cache files // uncommenting this may help. $wp_cache_mutex_disabled = 1; // Just modify it if you have conflicts with semaphores $sem_id = 5419; if ( '/' != substr($cache_path, -1)) { $cache_path .= '/'; } $wp_cache_mobile = 0; $wp_cache_mobile_whitelist = 'Stand Alone/QNws'; $wp_cache_mobile_browsers = 'Android, 2.0 MMP, 240x320, AvantGo, BlackBerry, Blazer, Cellphone, Danger, DoCoMo, Elaine/3.0, EudoraWeb, hiptop, IEMobile, iPhone, iPod, KYOCERA/WX310K, LG/U990, MIDP-2.0, MMEF20, MOT-V, NetFront, Newt, Nintendo Wii, Nitro, Nokia, Opera Mini, Palm, Playstation Portable, portalmmm, Proxinet, ProxiNet, SHARP-TQ-GX10, Small, SonyEricsson, Symbian OS, SymbianOS, TS21i-10, UP.Browser, UP.Link, Windows CE, WinWAP'; // change to relocate the supercache plugins directory $wp_cache_plugins_dir = WPCACHEHOME . 'plugins'; // set to 1 to do garbage collection during normal process shutdown instead of wp-cron $wp_cache_shutdown_gc = 0; $wp_super_cache_late_init = 0; // uncomment the next line to enable advanced debugging features $wp_super_cache_advanced_debug = 0; $wp_super_cache_front_page_text = ''; $wp_super_cache_front_page_clear = 0; $wp_super_cache_front_page_check = 0; $wp_super_cache_front_page_notification = '0'; $wp_cache_object_cache = 0; $wp_cache_anon_only = 0; $wp_supercache_cache_list = 0; $wp_cache_debug_to_file = 0; $wp_super_cache_debug = 0; $wp_cache_debug_level = 5; $wp_cache_debug_ip = ''; $wp_cache_debug_log = ''; $wp_cache_debug_email = ''; $wp_cache_pages[ "search" ] = 0; $wp_cache_pages[ "feed" ] = 0; $wp_cache_pages[ "category" ] = 0; $wp_cache_pages[ "home" ] = 0; $wp_cache_pages[ "frontpage" ] = 0; $wp_cache_pages[ "tag" ] = 0; $wp_cache_pages[ "archives" ] = 0; $wp_cache_pages[ "pages" ] = 0; $wp_cache_pages[ "single" ] = 0; $wp_cache_pages[ "author" ] = 0; $wp_cache_hide_donation = 0; $wp_cache_not_logged_in = 0; $wp_cache_clear_on_post_edit = 0; $wp_cache_hello_world = 0; $wp_cache_mobile_enabled = 0; $wp_cache_cron_check = 0; ?> advanced-cache.php000066600000002003152133035240010060 0ustar00"; } } if ( false == defined( 'WPCACHEHOME' ) ) { define( 'ADVANCEDCACHEPROBLEM', 1 ); } elseif ( !include_once( WPCACHEHOME . 'wp-cache-phase1.php' ) ) { if ( !@is_file( WPCACHEHOME . 'wp-cache-phase1.php' ) ) { define( 'ADVANCEDCACHEPROBLEM', 1 ); } } if ( defined( 'ADVANCEDCACHEPROBLEM' ) ) register_shutdown_function( 'wpcache_broken_message' ); ?> wp-cache-phase2.php000066600000161032152133035240010131 0ustar00'; } if ( !function_exists( 'wp_cache_user_agent_is_rejected' ) ) { function wp_cache_user_agent_is_rejected() { global $cache_rejected_user_agent; if (!function_exists('apache_request_headers')) return false; $headers = apache_request_headers(); if (!isset($headers["User-Agent"])) return false; if ( false == is_array( $cache_rejected_user_agent ) ) return false; foreach ($cache_rejected_user_agent as $expr) { if (strlen($expr) > 0 && stristr($headers["User-Agent"], $expr)) return true; } return false; } } function wp_cache_get_response_headers() { if(function_exists('apache_response_headers')) { $headers = apache_response_headers(); if ( empty( $headers ) ) { flush(); $headers = apache_response_headers(); } } else if(function_exists('headers_list')) { $headers = array(); foreach(headers_list() as $hdr) { $header_parts = explode( ':', $hdr, 2 ); $header_name = isset( $header_parts[0] ) ? trim( $header_parts[0] ) : ''; $header_value = isset( $header_parts[1] ) ? trim( $header_parts[1] ) : ''; $headers[$header_name] = $header_value; } } else $headers = null; return $headers; } function wp_cache_is_rejected($uri) { global $cache_rejected_uri; $auto_rejected = array( '/wp-admin/', 'xmlrpc.php', 'wp-app.php' ); foreach( $auto_rejected as $u ) { if( strstr( $uri, $u ) ) return true; // we don't allow caching of wp-admin for security reasons } if ( false == is_array( $cache_rejected_uri ) ) return false; foreach ( $cache_rejected_uri as $expr ) { if( $expr != '' && @preg_match( "~$expr~", $uri ) ) return true; } return false; } function wp_cache_mutex_init() { global $mutex, $wp_cache_mutex_disabled, $use_flock, $blog_cache_dir, $mutex_filename, $sem_id; if ( defined( 'WPSC_DISABLE_LOCKING' ) || ( isset( $wp_cache_mutex_disabled ) && $wp_cache_mutex_disabled ) ) return true; if( !is_bool( $use_flock ) ) { if(function_exists('sem_get')) $use_flock = false; else $use_flock = true; } $mutex = false; if ($use_flock ) { setup_blog_cache_dir(); wp_cache_debug( "Created mutex lock on filename: {$blog_cache_dir}{$mutex_filename}", 5 ); $mutex = @fopen( $blog_cache_dir . $mutex_filename, 'w' ); } else { wp_cache_debug( "Created mutex lock on semaphore: {$sem_id}", 5 ); $mutex = @sem_get( $sem_id, 1, 0666, 1 ); } } function wp_cache_writers_entry() { global $mutex, $wp_cache_mutex_disabled, $use_flock; if ( defined( 'WPSC_DISABLE_LOCKING' ) || ( isset( $wp_cache_mutex_disabled ) && $wp_cache_mutex_disabled ) ) return true; if( !$mutex ) { wp_cache_debug( "(writers entry) mutex lock not created. not caching.", 2 ); return false; } if ( $use_flock ) { wp_cache_debug( "grabbing lock using flock()", 5 ); flock($mutex, LOCK_EX); } else { wp_cache_debug( "grabbing lock using sem_acquire()", 5 ); @sem_acquire($mutex); } return true; } function wp_cache_writers_exit() { global $mutex, $wp_cache_mutex_disabled, $use_flock; if ( defined( 'WPSC_DISABLE_LOCKING' ) || ( isset( $wp_cache_mutex_disabled ) && $wp_cache_mutex_disabled ) ) return true; if( !$mutex ) { wp_cache_debug( "(writers exit) mutex lock not created. not caching.", 2 ); return false; } if ( $use_flock ) { wp_cache_debug( "releasing lock using flock()", 5 ); flock( $mutex, LOCK_UN ); } else { wp_cache_debug( "releasing lock using sem_release() and sem_remove()", 5 ); @sem_release( $mutex ); if ( defined( "WPSC_REMOVE_SEMAPHORE" ) ) @sem_remove( $mutex ); } } function wp_super_cache_query_vars() { global $wp_super_cache_query; if ( is_search() ) $wp_super_cache_query[ 'is_search' ] = 1; if ( is_page() ) $wp_super_cache_query[ 'is_page' ] = 1; if ( is_archive() ) $wp_super_cache_query[ 'is_archive' ] = 1; if ( is_tag() ) $wp_super_cache_query[ 'is_tag' ] = 1; if ( is_single() ) $wp_super_cache_query[ 'is_single' ] = 1; if ( is_category() ) $wp_super_cache_query[ 'is_category' ] = 1; if ( is_front_page() ) $wp_super_cache_query[ 'is_front_page' ] = 1; if ( is_home() ) $wp_super_cache_query[ 'is_home' ] = 1; if ( is_author() ) $wp_super_cache_query[ 'is_author' ] = 1; if ( is_feed() ) $wp_super_cache_query[ 'is_feed' ] = 1; } function wp_cache_ob_callback( $buffer ) { global $wp_cache_pages, $wp_query, $wp_super_cache_query, $cache_acceptable_files, $wp_cache_no_cache_for_get, $wp_cache_object_cache, $wp_cache_request_uri, $do_rebuild_list; $buffer = apply_filters( 'wp_cache_ob_callback_filter', $buffer ); $script = basename($_SERVER['PHP_SELF']); // All the things that can stop a page being cached $cache_this_page = true; if ( defined( 'DONOTCACHEPAGE' ) ) { wp_cache_debug( 'DONOTCACHEPAGE defined. Caching disabled.', 2 ); $cache_this_page = false; } elseif ( $wp_cache_no_cache_for_get && false == empty( $_GET ) && false == defined( 'DOING_CRON' ) ) { wp_cache_debug( "Non empty GET request. Caching disabled on settings page. " . json_encode( $_GET ), 1 ); $cache_this_page = false; } elseif ( $_SERVER["REQUEST_METHOD"] == 'POST' || !empty( $_POST ) || get_option( 'gzipcompression' ) ) { wp_cache_debug( 'Not caching POST request.', 5 ); $cache_this_page = false; } elseif ( $_SERVER["REQUEST_METHOD"] == 'PUT' ) { wp_cache_debug( 'Not caching PUT request.', 5 ); $cache_this_page = false; } elseif ( $_SERVER["REQUEST_METHOD"] == 'DELETE' ) { wp_cache_debug( 'Not caching DELETE request.', 5 ); $cache_this_page = false; } elseif ( $wp_cache_object_cache && !empty( $_GET ) ) { wp_cache_debug( 'Not caching GET request while object cache storage enabled.', 5 ); $cache_this_page = false; } elseif ( isset( $_GET[ 'preview' ] ) ) { wp_cache_debug( 'Not caching preview post.', 2 ); $cache_this_page = false; } elseif ( !in_array($script, $cache_acceptable_files) && wp_cache_is_rejected( $wp_cache_request_uri ) ) { wp_cache_debug( 'URI rejected. Not Caching', 2 ); $cache_this_page = false; } elseif ( wp_cache_user_agent_is_rejected() ) { wp_cache_debug( "USER AGENT ({$_SERVER[ 'HTTP_USER_AGENT' ]}) rejected. Not Caching", 4 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'single' ] ) && $wp_cache_pages[ 'single' ] == 1 && isset( $wp_super_cache_query[ 'is_single' ] ) ) { wp_cache_debug( 'Not caching single post.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'pages' ] ) && $wp_cache_pages[ 'pages' ] == 1 && isset( $wp_super_cache_query[ 'is_page' ] ) ) { wp_cache_debug( 'Not caching single page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'archives' ] ) && $wp_cache_pages[ 'archives' ] == 1 && isset( $wp_super_cache_query[ 'is_archive' ] ) ) { wp_cache_debug( 'Not caching archive page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'tag' ] ) && $wp_cache_pages[ 'tag' ] == 1 && isset( $wp_super_cache_query[ 'is_tag' ] ) ) { wp_cache_debug( 'Not caching tag page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'category' ] ) && $wp_cache_pages[ 'category' ] == 1 && isset( $wp_super_cache_query[ 'is_category' ] ) ) { wp_cache_debug( 'Not caching category page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'frontpage' ] ) && $wp_cache_pages[ 'frontpage' ] == 1 && isset( $wp_super_cache_query[ 'is_front_page' ] ) ) { wp_cache_debug( 'Not caching front page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'home' ] ) && $wp_cache_pages[ 'home' ] == 1 && isset( $wp_super_cache_query[ 'is_home' ] ) ) { wp_cache_debug( 'Not caching home page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'search' ] ) && $wp_cache_pages[ 'search' ] == 1 && isset( $wp_super_cache_query[ 'is_search' ] ) ) { wp_cache_debug( 'Not caching search page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'author' ] ) && $wp_cache_pages[ 'author' ] == 1 && isset( $wp_super_cache_query[ 'is_author' ] ) ) { wp_cache_debug( 'Not caching author page.', 2 ); $cache_this_page = false; } elseif ( isset( $wp_cache_pages[ 'feed' ] ) && $wp_cache_pages[ 'feed' ] == 1 && isset( $wp_super_cache_query[ 'is_feed' ] ) ) { wp_cache_debug( 'Not caching feed.', 2 ); $cache_this_page = false; } if ( !isset( $wp_query ) ) wp_cache_debug( 'wp_cache_ob_callback: WARNING! $query not defined but the plugin has worked around that problem.', 4 ); if ( $cache_this_page ) { wp_cache_debug( 'Output buffer callback', 4 ); $buffer = wp_cache_get_ob( $buffer ); wp_cache_shutdown_callback(); return $buffer; } else { if ( is_array( $do_rebuild_list ) && false == empty( $do_rebuild_list ) ) { foreach( $do_rebuild_list as $dir => $n ) { if ( wp_cache_confirm_delete( $dir ) ) { wp_cache_debug( 'wp_cache_ob_callback clearing rebuilt files in ' . $dir ); $files_to_check = get_all_supercache_filenames( $dir ); foreach( $files_to_check as $cache_file ) { $cache_file = $dir . $cache_file; @unlink( $cache_file ); } } } } return wp_cache_maybe_dynamic( $buffer ); } } function wp_cache_append_tag( &$buffer ) { global $wp_cache_gmt_offset, $wp_super_cache_comments; global $cache_enabled, $super_cache_enabled; if ( false == isset( $wp_super_cache_comments ) ) $wp_super_cache_comments = 1; if ( $wp_super_cache_comments == 0 ) return false; $timestamp = gmdate('Y-m-d H:i:s', (time() + ( $wp_cache_gmt_offset * 3600))); if ( $cache_enabled || $super_cache_enabled ) { $buffer .= "\n\n"; } else { $buffer .= "\n\n"; } } function wp_cache_add_to_buffer( &$buffer, $text ) { global $wp_super_cache_comments; if ( false == isset( $wp_super_cache_comments ) ) $wp_super_cache_comments = 1; if ( $wp_super_cache_comments == 0 ) return false; $buffer .= "\n"; } /* * If dynamic caching is enabled then run buffer through wpsc_cachedata filter before returning it. * or we'll return template tags to visitors. */ function wp_cache_maybe_dynamic( &$buffer ) { global $wp_cache_mfunc_enabled; if ( $wp_cache_mfunc_enabled == 1 && do_cacheaction( 'wpsc_cachedata_safety', 0 ) === 1 ) { wp_cache_debug( 'wp_cache_maybe_dynamic: filtered $buffer through wpsc_cachedata', 4 ); return do_cacheaction( 'wpsc_cachedata', $buffer ); // dynamic content for display } else { wp_cache_debug( 'wp_cache_maybe_dynamic: returned $buffer', 4 ); return $buffer; } } function wp_cache_get_ob(&$buffer) { global $cache_enabled, $cache_path, $cache_filename, $meta_file, $wp_start_time, $supercachedir; global $new_cache, $wp_cache_meta, $file_expired, $blog_id, $cache_compression; global $wp_cache_gzip_encoding, $super_cache_enabled, $cached_direct_pages; global $wp_cache_404, $gzsize, $supercacheonly; global $blog_cache_dir, $wp_cache_request_uri, $wp_supercache_cache_list; global $wp_cache_not_logged_in, $wp_cache_object_cache, $cache_max_time; global $wp_cache_is_home, $wp_cache_front_page_checks, $wp_cache_mfunc_enabled; if ( isset( $wp_cache_mfunc_enabled ) == false ) $wp_cache_mfunc_enabled = 0; $new_cache = true; $wp_cache_meta = array(); /* Mode paranoic, check for closing tags * we avoid caching incomplete files */ if ( $buffer == '' ) { $new_cache = false; if ( isset( $GLOBALS[ 'wp_super_cache_debug' ] ) && $GLOBALS[ 'wp_super_cache_debug' ] ) { wp_cache_debug( "Buffer is blank. Output buffer may have been corrupted by another plugin or this is a redirected URL. Look for text 'ob_start' in the files of your plugins directory.", 2 ); wp_cache_add_to_buffer( $buffer, "Page not cached by WP Super Cache. Blank Page. Check output buffer usage by plugins." ); } } if ( $wp_cache_404 && false == apply_filters( 'wpsupercache_404', false ) ) { $new_cache = false; if ( isset( $GLOBALS[ 'wp_super_cache_debug' ] ) && $GLOBALS[ 'wp_super_cache_debug' ] ) { wp_cache_debug( "404 file not found not cached", 2 ); wp_cache_add_to_buffer( $buffer, "Page not cached by WP Super Cache. 404." ); } } if ( !preg_match( apply_filters( 'wp_cache_eof_tags', '/(<\/html>|<\/rss>|<\/feed>|<\/urlset|<\?xml)/i' ), $buffer ) ) { $new_cache = false; if( false === strpos( $_SERVER[ 'REQUEST_URI' ], 'robots.txt' ) ) { if ( isset( $GLOBALS[ 'wp_super_cache_debug' ] ) && $GLOBALS[ 'wp_super_cache_debug' ] ) { wp_cache_debug( "No closing html tag. Not caching.", 2 ); wp_cache_add_to_buffer( $buffer, "Page not cached by WP Super Cache. No closing HTML tag. Check your theme." ); } } else { wp_cache_debug( "robots.txt detected. Not caching.", 2 ); } } if( !$new_cache ) return wp_cache_maybe_dynamic( $buffer ); $duration = wp_cache_microtime_diff($wp_start_time, microtime()); $duration = sprintf("%0.3f", $duration); wp_cache_add_to_buffer( $buffer, "Dynamic page generated in $duration seconds." ); if( !wp_cache_writers_entry() ) { wp_cache_add_to_buffer( $buffer, "Page not cached by WP Super Cache. Could not get mutex lock." ); wp_cache_debug( "Could not get mutex lock. Not caching.", 1 ); return wp_cache_maybe_dynamic( $buffer ); } if ( $wp_cache_not_logged_in && is_feed() ) { wp_cache_debug( "Feed detected. Writing legacy cache files.", 5 ); $wp_cache_not_logged_in = false; } $home_url = parse_url( trailingslashit( get_bloginfo( 'url' ) ) ); $dir = get_current_url_supercache_dir(); $supercachedir = $cache_path . 'supercache/' . preg_replace('/:.*$/', '', $home_url[ 'host' ]); if( !empty( $_GET ) || is_feed() || ( $super_cache_enabled == true && is_dir( substr( $supercachedir, 0, -1 ) . '.disabled' ) ) ) { wp_cache_debug( "Supercache disabled: GET or feed detected or disabled by config.", 2 ); $super_cache_enabled = false; } $tmp_wpcache_filename = $cache_path . uniqid( mt_rand(), true ) . '.tmp'; $supercacheonly = false; if( $super_cache_enabled ) { if ( wp_cache_get_cookies_values() == '' && empty( $_GET ) ) { wp_cache_debug( "Anonymous user detected. Only creating Supercache file.", 3 ); $supercacheonly = true; } } $cache_error = ''; if ( $wp_cache_not_logged_in && wp_cache_get_cookies_values() != '' ) { $super_cache_enabled = false; $cache_enabled = false; $cache_error = 'Not caching requests by known users. (See Advanced Settings page)'; wp_cache_debug( 'Not caching for known user.', 5 ); } if ( $wp_cache_object_cache ) { // half on mode when using the object cache if ( wp_cache_get_cookies_values() != '' ) { $cache_enabled = false; $cache_error = 'Known User and using object. Only anonymous users cached.'; } $super_cache_enabled = false; $supercacheonly = false; wp_cache_init(); // PHP5 destroys objects during shutdown } if ( !$cache_enabled ) { wp_cache_debug( 'Cache is not enabled. Sending buffer to browser.', 5 ); wp_cache_writers_exit(); wp_cache_add_to_buffer( $buffer, "Page not cached by WP Super Cache. Check your settings page. $cache_error" ); if ( $wp_cache_mfunc_enabled == 1 ) { global $wp_super_cache_late_init; if ( false == isset( $wp_super_cache_late_init ) || ( isset( $wp_super_cache_late_init ) && $wp_super_cache_late_init == 0 ) ) wp_cache_add_to_buffer( $buffer, 'Super Cache dynamic page detected but $wp_super_cache_late_init not set. See the readme.txt for further details.' ); } return wp_cache_maybe_dynamic( $buffer ); } if( @is_dir( $dir ) == false ) @wp_mkdir_p( $dir ); $fr = $fr2 = $gz = false; // Open wp-cache cache file if ( false == $wp_cache_object_cache ) { if ( !$supercacheonly ) { $fr = @fopen($tmp_wpcache_filename, 'w'); if (!$fr) { wp_cache_debug( "Error. Supercache could not write to " . str_replace( ABSPATH, '', $cache_path ) . $cache_filename, 1 ); wp_cache_add_to_buffer( $buffer, "File not cached! Super Cache Couldn't write to: " . str_replace( ABSPATH, '', $cache_path ) . $cache_filename ); wp_cache_writers_exit(); return wp_cache_maybe_dynamic( $buffer ); } } else { $user_info = wp_cache_get_cookies_values(); $do_cache = apply_filters( 'do_createsupercache', $user_info ); if ( $super_cache_enabled && ( $user_info == '' || $do_cache === true ) ) { $cache_fname = $dir . supercache_filename(); $tmp_cache_filename = $dir . uniqid( mt_rand(), true ) . '.tmp'; $fr2 = @fopen( $tmp_cache_filename, 'w' ); if ( !$fr2 ) { wp_cache_debug( "Error. Supercache could not write to " . str_replace( ABSPATH, '', $tmp_cache_filename ), 1 ); wp_cache_add_to_buffer( $buffer, "File not cached! Super Cache Couldn't write to: " . str_replace( ABSPATH, '', $tmp_cache_filename ) ); @fclose( $fr ); @unlink( $tmp_wpcache_filename ); wp_cache_writers_exit(); return wp_cache_maybe_dynamic( $buffer ); } elseif ( ( !isset( $wp_cache_mfunc_enabled ) || $wp_cache_mfunc_enabled == 0 ) && $cache_compression ) { // don't want to store compressed files if using dynamic content $gz = @fopen( $tmp_cache_filename . ".gz", 'w'); if (!$gz) { wp_cache_debug( "Error. Supercache could not write to " . str_replace( ABSPATH, '', $tmp_cache_filename ) . ".gz", 1 ); wp_cache_add_to_buffer( $buffer, "File not cached! Super Cache Couldn't write to: " . str_replace( ABSPATH, '', $tmp_cache_filename ) . ".gz" ); @fclose( $fr ); @unlink( $tmp_wpcache_filename ); @fclose( $fr2 ); @unlink( $tmp_cache_filename ); wp_cache_writers_exit(); return wp_cache_maybe_dynamic( $buffer ); } } } } } $added_cache = 0; $oc_key = get_oc_key(); $buffer = apply_filters( 'wpsupercache_buffer', $buffer ); wp_cache_append_tag( $buffer ); /* * Dynamic content enabled: write the buffer to a file and then process any templates found using * the wpsc_cachedata filter. Buffer is then returned to the visitor. */ if ( $wp_cache_mfunc_enabled == 1 ) { if ( preg_match( '//', $buffer ) ) { //Dynamic content wp_cache_debug( "mfunc/mclude/dynamic-cached-content tags have been retired. Please update your theme. See docs for updates." ); wp_cache_add_to_buffer( $buffer, "Warning! Obsolete mfunc/mclude/dynamic-cached-content tags found. Please update your theme. See http://ocaoimh.ie/y/5b for more information." ); } global $wp_super_cache_late_init; if ( false == isset( $wp_super_cache_late_init ) || ( isset( $wp_super_cache_late_init ) && $wp_super_cache_late_init == 0 ) ) wp_cache_add_to_buffer( $buffer, 'Super Cache dynamic page detected but late init not set. See the readme.txt for further details.' ); if ( $fr ) { // legacy caching wp_cache_debug( "Writing dynamic buffer to legacy file." ); wp_cache_add_to_buffer( $buffer, "Dynamic Legacy Super Cache" ); fputs( $fr, '' . $buffer ); } elseif ( isset( $fr2 ) ) { // supercache active wp_cache_debug( "Writing dynamic buffer to supercache file." ); wp_cache_add_to_buffer( $buffer, "Dynamic Super Cache" ); fputs( $fr2, $buffer ); } elseif ( true == $wp_cache_object_cache ) { wp_cache_set( $oc_key, $buffer, 'supercache', $cache_max_time ); } $wp_cache_meta[ 'dynamic' ] = true; if ( do_cacheaction( 'wpsc_cachedata_safety', 0 ) === 1 ) $buffer = do_cacheaction( 'wpsc_cachedata', $buffer ); // dynamic content for display if ( $cache_compression && $wp_cache_gzip_encoding ) { wp_cache_debug( "Gzipping dynamic buffer for display.", 5 ); wp_cache_add_to_buffer( $buffer, "Compression = gzip" ); $gzdata = gzencode( $buffer, 6, FORCE_GZIP ); $gzsize = function_exists( 'mb_strlen' ) ? mb_strlen( $gzdata, '8bit' ) : strlen( $gzdata ); } } else { if ( $gz || $wp_cache_gzip_encoding ) { wp_cache_debug( "Gzipping buffer.", 5 ); wp_cache_add_to_buffer( $buffer, "Compression = gzip" ); $gzdata = gzencode( $buffer, 6, FORCE_GZIP ); $gzsize = function_exists( 'mb_strlen' ) ? mb_strlen( $gzdata, '8bit' ) : strlen( $gzdata ); $wp_cache_meta[ 'headers' ][ 'Content-Encoding' ] = 'Content-Encoding: ' . $wp_cache_gzip_encoding; $wp_cache_meta[ 'headers' ][ 'Vary' ] = 'Vary: Accept-Encoding, Cookie'; // Return uncompressed data & store compressed for later use if ( $fr ) { wp_cache_debug( "Writing gzipped buffer to wp-cache cache file.", 5 ); fputs($fr, '' . $gzdata); } elseif ( $cache_enabled && $wp_cache_object_cache ) { wp_cache_set( $oc_key . ".gz", $gzdata, 'supercache', $cache_max_time ); $added_cache = 1; } } else { // no compression $wp_cache_meta[ 'headers' ][ 'Vary' ] = 'Vary: Cookie'; if ( $cache_enabled && $wp_cache_object_cache ) { wp_cache_set( $oc_key, $buffer, 'supercache', $cache_max_time ); $added_cache = 1; } elseif ( $fr ) { wp_cache_debug( "Writing non-gzipped buffer to wp-cache cache file." ); fputs($fr, '' . $buffer); } } if ( $fr2 ) { wp_cache_debug( "Writing non-gzipped buffer to supercache file." ); wp_cache_add_to_buffer( $buffer, "super cache" ); fputs($fr2, $buffer ); } if ( isset( $gzdata ) && $gz ) { wp_cache_debug( "Writing gzipped buffer to supercache file." ); fwrite($gz, $gzdata ); } } $new_cache = true; if ( false == $wp_cache_object_cache ) { if( $fr ) { $supercacheonly = false; fclose($fr); if ( filesize( $tmp_wpcache_filename ) == 0 ) { wp_cache_debug( "Warning! The file $tmp_wpcache_filename was empty. Did not rename to {$blog_cache_dir}{$cache_filename}", 5 ); @unlink( $tmp_wpcache_filename ); } else { if ( !@rename( $tmp_wpcache_filename, $blog_cache_dir . $cache_filename ) ) { if ( false == is_dir( $blog_cache_dir ) ) @wp_mkdir_p( $blog_cache_dir ); @unlink( $blog_cache_dir . $cache_filename ); @rename( $tmp_wpcache_filename, $blog_cache_dir . $cache_filename ); } wp_cache_debug( "Renamed temp wp-cache file to {$blog_cache_dir}$cache_filename", 5 ); $added_cache = 1; } } if( $fr2 ) { fclose($fr2); if ( $wp_cache_front_page_checks && $cache_fname == $supercachedir . $home_url[ 'path' ] . supercache_filename() && !( $wp_cache_is_home ) ) { wp_cache_writers_exit(); wp_cache_debug( "Warning! Not writing another page to front page cache.", 1 ); return $buffer; } elseif ( filesize( $tmp_cache_filename ) == 0 ) { wp_cache_debug( "Warning! The file $tmp_cache_filename was empty. Did not rename to {$cache_fname}", 5 ); @unlink( $tmp_cache_filename ); } else { if ( !@rename( $tmp_cache_filename, $cache_fname ) ) { @unlink( $cache_fname ); @rename( $tmp_cache_filename, $cache_fname ); } wp_cache_debug( "Renamed temp supercache file to $cache_fname", 5 ); $added_cache = 1; } } if( $gz ) { fclose($gz); if ( filesize( $tmp_cache_filename . '.gz' ) == 0 ) { wp_cache_debug( "Warning! The file {$tmp_cache_filename}.gz was empty. Did not rename to {$cache_fname}.gz", 5 ); @unlink( $tmp_cache_filename . '.gz' ); } else { if ( !@rename( $tmp_cache_filename . '.gz', $cache_fname . '.gz' ) ) { @unlink( $cache_fname . '.gz' ); @rename( $tmp_cache_filename . '.gz', $cache_fname . '.gz' ); } wp_cache_debug( "Renamed temp supercache gz file to {$cache_fname}.gz", 5 ); $added_cache = 1; } } } if ( $added_cache && isset( $wp_supercache_cache_list ) && $wp_supercache_cache_list ) { update_option( 'wpsupercache_count', ( get_option( 'wpsupercache_count' ) + 1 ) ); $last_urls = (array)get_option( 'supercache_last_cached' ); if ( count( $last_urls ) >= 10 ) $last_urls = array_slice( $last_urls, 1, 9 ); $last_urls[] = array( 'url' => preg_replace( '/[ <>\'\"\r\n\t\(\)]/', '', $_SERVER[ 'REQUEST_URI' ] ), 'date' => date( 'Y-m-d H:i:s' ) ); update_option( 'supercache_last_cached', $last_urls ); } wp_cache_writers_exit(); if ( !headers_sent() && $wp_cache_gzip_encoding && $gzdata) { wp_cache_debug( "Writing gzip content headers. Sending buffer to browser", 5 ); header( 'Content-Encoding: ' . $wp_cache_gzip_encoding ); header( 'Vary: Accept-Encoding, Cookie' ); header( 'Content-Length: ' . $gzsize ); return $gzdata; } else { wp_cache_debug( "Sending buffer to browser", 5 ); return $buffer; } } function wp_cache_phase2_clean_cache($file_prefix) { global $cache_path, $blog_cache_dir; if( !wp_cache_writers_entry() ) return false; wp_cache_debug( "wp_cache_phase2_clean_cache: Cleaning cache in $blog_cache_dir" ); if ( $handle = @opendir( $blog_cache_dir ) ) { while ( false !== ($file = @readdir($handle))) { if ( strpos( $file, $file_prefix ) !== false ) { if ( strpos( $file, '.html' ) ) { // delete old legacy files immediately wp_cache_debug( "wp_cache_phase2_clean_cache: Deleting obsolete legacy cache+meta files: $file" ); @unlink( $blog_cache_dir . $file); @unlink( $blog_cache_dir . 'meta/' . str_replace( '.html', '.meta', $file ) ); } else { $meta = json_decode( wp_cache_get_legacy_cache( $blog_cache_dir . 'meta/' . $file ), true ); if ( $meta[ 'blog_id' ] == $wpdb->blogid ) { @unlink( $blog_cache_dir . $file ); @unlink( $blog_cache_dir . 'meta/' . $file ); } } } } closedir($handle); } wp_cache_writers_exit(); } function prune_super_cache( $directory, $force = false, $rename = false ) { global $cache_max_time, $cache_path, $cache_rebuild_files, $blog_cache_dir; static $log = 0; if ( false == @file_exists( $directory ) ) { wp_cache_debug( "prune_super_cache: exiting as file/dir does not exist: $directory" ); return $log; } if( !isset( $cache_max_time ) ) $cache_max_time = 3600; $now = time(); $protected_directories = array( $cache_path . '.htaccess', $cache_path . "index.html", $cache_path . $blog_cache_dir, $cache_path . $blog_cache_dir . "index.html", $cache_path . $blog_cache_dir . 'meta', $cache_path . $blog_cache_dir . 'meta/index.html', $cache_path . 'supercache/index.html', $cache_path . 'supercache' ); $oktodelete = false; if (is_dir($directory)) { if( $dh = @opendir( $directory ) ) { $directory = trailingslashit( $directory ); while( ( $entry = @readdir( $dh ) ) !== false ) { if ($entry == '.' || $entry == '..') continue; $entry = $directory . $entry; prune_super_cache( $entry, $force, $rename ); // If entry is a directory, AND it's not a protected one, AND we're either forcing the delete, OR the file is out of date, if( is_dir( $entry ) && !in_array( $entry, $protected_directories ) && ( $force || @filemtime( $entry ) + $cache_max_time <= $now ) ) { // if the directory isn't empty can't delete it if( $handle = @opendir( $entry ) ) { $donotdelete = false; while( !$donotdelete && ( $file = @readdir( $handle ) ) !== false ) { if ($file == '.' || $file == '..') continue; $donotdelete = true; wp_cache_debug( "gc: could not delete $entry as it's not empty: $file", 2 ); } closedir($handle); } if( $donotdelete ) continue; if( !$rename ) { @rmdir( $entry ); $log++; if ( $force ) { wp_cache_debug( "gc: deleted $entry, forced delete", 2 ); } else { wp_cache_debug( "gc: deleted $entry, older than $cache_max_time seconds", 2 ); } } } elseif ( in_array( $entry, $protected_directories ) ) { wp_cache_debug( "gc: could not delete $entry as it's protected.", 2 ); } } closedir($dh); } } elseif( is_file($directory) && ($force || @filemtime( $directory ) + $cache_max_time <= $now ) ) { $oktodelete = true; if ( in_array( $directory, $protected_directories ) ) { wp_cache_debug( "gc: could not delete $directory as it's protected.", 2 ); $oktodelete = false; } if( $oktodelete && !$rename ) { wp_cache_debug( "prune_super_cache: deleted $directory", 5 ); @unlink( $directory ); $log++; } elseif( $oktodelete && $rename ) { wp_cache_debug( "prune_super_cache: wp_cache_rebuild_or_delete( $directory )", 5 ); wp_cache_rebuild_or_delete( $directory ); $log++; } else { wp_cache_debug( "prune_super_cache: did not delete file: $directory" ); } } else { wp_cache_debug( "prune_super_cache: did not delete file as it wasn't a directory or file and not forced to delete new file: $directory" ); } return $log; } function wp_cache_rebuild_or_delete( $file ) { global $cache_rebuild_files; if( strpos( $file, '?' ) !== false ) $file = substr( $file, 0, strpos( $file, '?' ) ); if( $cache_rebuild_files && substr( $file, -14 ) != '.needs-rebuild' ) { if( @rename($file, $file . '.needs-rebuild') ) { @touch( $file . '.needs-rebuild' ); wp_cache_debug( "rebuild_or_gc: rename file to {$file}.needs-rebuild", 2 ); } else { @unlink( $file ); wp_cache_debug( "rebuild_or_gc: deleted $file", 2 ); } } else { @unlink( $file ); wp_cache_debug( "rebuild_or_gc: deleted $file", 2 ); } } function wp_cache_phase2_clean_expired( $file_prefix, $force = false ) { global $cache_path, $cache_max_time, $blog_cache_dir, $wp_cache_preload_on; clearstatcache(); if( !wp_cache_writers_entry() ) return false; $now = time(); wp_cache_debug( "Cleaning expired cache files in $blog_cache_dir", 2 ); $deleted = 0; if ( ( $handle = @opendir( $blog_cache_dir ) ) ) { while ( false !== ($file = readdir($handle))) { if ( preg_match("/^$file_prefix/", $file) && (@filemtime( $blog_cache_dir . $file) + $cache_max_time) <= $now ) { @unlink( $blog_cache_dir . $file ); @unlink( $blog_cache_dir . 'meta/' . str_replace( '.html', '.meta', $file ) ); wp_cache_debug( "wp_cache_phase2_clean_expired: Deleting obsolete legacy cache+meta files: $file" ); continue; } if($file != '.' && $file != '..') { if( is_dir( $blog_cache_dir . $file ) == false && (@filemtime($blog_cache_dir . $file) + $cache_max_time) <= $now ) { if ( substr( $file, -9 ) != '.htaccess' && $file != 'index.html' ) { @unlink($blog_cache_dir . $file); wp_cache_debug( "Deleting $blog_cache_dir{$file}, older than $cache_max_time seconds", 5 ); } } } } closedir($handle); if ( false == $wp_cache_preload_on || true == $force ) { wp_cache_debug( "Doing GC on supercache dir: {$cache_path}supercache", 2 ); $deleted = prune_super_cache( $cache_path . 'supercache', false, false ); } } wp_cache_writers_exit(); return $deleted; } function wp_cache_shutdown_callback() { global $cache_path, $cache_max_time, $file_expired, $file_prefix, $meta_file, $new_cache, $wp_cache_meta, $known_headers, $blog_id, $wp_cache_gzip_encoding, $gzsize, $cache_filename, $supercacheonly, $blog_cache_dir; global $wp_cache_request_uri, $wp_cache_key, $wp_cache_object_cache, $cache_enabled, $wp_cache_blog_charset, $wp_cache_not_logged_in; global $WPSC_HTTP_HOST; $wp_cache_meta[ 'uri' ] = $WPSC_HTTP_HOST . preg_replace('/[ <>\'\"\r\n\t\(\)]/', '', $wp_cache_request_uri); // To avoid XSS attacks $wp_cache_meta[ 'blog_id' ] = $blog_id; $wp_cache_meta[ 'post' ] = wp_cache_post_id(); $wp_cache_meta[ 'key' ] = $wp_cache_key; $wp_cache_meta = apply_filters( 'wp_cache_meta', $wp_cache_meta ); $response = wp_cache_get_response_headers(); foreach ($known_headers as $key) { if(isset($response[$key])) { $wp_cache_meta[ 'headers' ][ $key ] = "$key: " . $response[$key]; } } wp_cache_debug( "wp_cache_shutdown_callback: collecting meta data.", 2 ); if (!isset( $response['Last-Modified'] )) { $value = gmdate('D, d M Y H:i:s') . ' GMT'; /* Dont send this the first time */ /* @header('Last-Modified: ' . $value); */ $wp_cache_meta[ 'headers' ][ 'Last-Modified' ] = "Last-Modified: $value"; } if ( !isset( $response[ 'Content-Type' ] ) && !isset( $response[ 'Content-type' ] ) ) { // On some systems, headers set by PHP can't be fetched from // the output buffer. This is a last ditch effort to set the // correct Content-Type header for feeds, if we didn't see // it in the response headers already. -- dougal if (is_feed()) { $type = get_query_var('feed'); $type = str_replace('/','',$type); switch ($type) { case 'atom': $value = "application/atom+xml"; break; case 'rdf': $value = "application/rdf+xml"; break; case 'rss': case 'rss2': default: $value = "application/rss+xml"; } } else { // not a feed $value = get_option( 'html_type' ); if( $value == '' ) $value = 'text/html'; } $value .= "; charset=\"" . $wp_cache_blog_charset . "\""; wp_cache_debug( "Sending 'Content-Type: $value' header.", 2 ); @header("Content-Type: $value"); $wp_cache_meta[ 'headers' ][ 'Content-Type' ] = "Content-Type: $value"; } if ( $cache_enabled && !$supercacheonly && $new_cache ) { if( !isset( $wp_cache_meta[ 'dynamic' ] ) && $wp_cache_gzip_encoding && !in_array( 'Content-Encoding: ' . $wp_cache_gzip_encoding, $wp_cache_meta[ 'headers' ] ) ) { wp_cache_debug( "Sending gzip headers.", 2 ); $wp_cache_meta[ 'headers' ][ 'Content-Encoding' ] = 'Content-Encoding: ' . $wp_cache_gzip_encoding; $wp_cache_meta[ 'headers' ][ 'Vary' ] = 'Vary: Accept-Encoding, Cookie'; } $serial = '' . json_encode( $wp_cache_meta ); if( wp_cache_writers_entry() ) { wp_cache_debug( "Writing meta file: {$blog_cache_dir}meta/{$meta_file}", 2 ); if ( false == $wp_cache_object_cache ) { $tmp_meta_filename = $blog_cache_dir . 'meta/' . uniqid( mt_rand(), true ) . '.tmp'; $fr = @fopen( $tmp_meta_filename, 'w'); if( !$fr ) @wp_mkdir_p( $blog_cache_dir . 'meta' ); $fr = @fopen( $tmp_meta_filename, 'w'); if ( $fr ) { fputs($fr, $serial); fclose($fr); @chmod( $tmp_meta_filename, 0666 & ~umask()); if( !@rename( $tmp_meta_filename, $blog_cache_dir . 'meta/' . $meta_file ) ) { @unlink( $blog_cache_dir . 'meta/' . $meta_file ); @rename( $tmp_meta_filename, $blog_cache_dir . 'meta/' . $meta_file ); } } else { wp_cache_debug( "Problem writing meta file: {$blog_cache_dir}meta/{$meta_file}", 2 ); } } elseif ( $cache_enabled ) { $oc_key = get_oc_key() . ".meta"; if ( gzip_accepted() ) $oc_key .= ".gz"; wp_cache_set( $oc_key, $serial, 'supercache', $cache_max_time ); } wp_cache_writers_exit(); } } else { wp_cache_debug( "Did not write meta file: $meta_file *$supercacheonly* *$wp_cache_not_logged_in* *$new_cache*", 2 ); } global $time_to_gc_cache; if( isset( $time_to_gc_cache ) && $time_to_gc_cache == 1 ) { wp_cache_debug( "Executing wp_cache_gc action.", 3 ); do_action( 'wp_cache_gc' ); } } function wp_cache_no_postid($id) { return wp_cache_post_change(wp_cache_post_id()); } function wp_cache_get_postid_from_comment( $comment_id, $status = 'NA' ) { global $super_cache_enabled, $wp_cache_request_uri; $comment = get_comment($comment_id, ARRAY_A); if ( $status != 'NA' ) { $comment[ 'old_comment_approved' ] = $comment[ 'comment_approved' ]; $comment[ 'comment_approved' ] = $status; } if ( ( $status == 'trash' || $status == 'spam' ) && $comment[ 'old_comment_approved' ] != 1 ) { // don't modify cache if moderated comments are trashed or spammed wp_cache_debug( "Moderated comment deleted or spammed. Don't delete any cache files.", 4 ); define( 'DONOTDELETECACHE', 1 ); return wp_cache_post_id(); } $postid = $comment['comment_post_ID']; // Do nothing if comment is not moderated // http://ocaoimh.ie/2006/12/05/caching-wordpress-with-wp-cache-in-a-spam-filled-world if ( !preg_match('/wp-admin\//', $wp_cache_request_uri) ) { if ( $comment['comment_approved'] == 'delete' && ( isset( $comment[ 'old_comment_approved' ] ) && $comment[ 'old_comment_approved' ] == 0 ) ) { // do nothing if moderated comments are deleted wp_cache_debug( "Moderated comment deleted. Don't delete any cache files.", 4 ); define( 'DONOTDELETECACHE', 1 ); return $postid; } elseif ( $comment['comment_approved'] == 'spam' ) { wp_cache_debug( "Spam comment. Don't delete any cache files.", 4 ); define( 'DONOTDELETECACHE', 1 ); return $postid; } elseif( $comment['comment_approved'] == '0' ) { if ( $comment[ 'content_type' ] == '' ) { wp_cache_debug( "Moderated comment. Don't delete supercache file until comment approved.", 4 ); $super_cache_enabled = 0; // don't remove the super cache static file until comment is approved define( 'DONOTDELETECACHE', 1 ); } else { wp_cache_debug( "Moderated ping or trackback. Not deleting cache files..", 4 ); define( 'DONOTDELETECACHE', 1 ); return $postid; } } } // We must check it up again due to WP bugs calling two different actions // for delete, for example both wp_set_comment_status and delete_comment // are called when deleting a comment if ($postid > 0) { wp_cache_debug( "Post $postid changed. Update cache.", 4 ); return wp_cache_post_change( $postid ); } elseif ( $_GET[ 'delete_all' ] != 'Empty Trash' && $_GET[ 'delete_all2' ] != 'Empty Spam' ) { wp_cache_debug( "Unknown post changed. Update cache.", 4 ); return wp_cache_post_change( wp_cache_post_id() ); } } /* Used by wp_update_nav_menu action to clear current blog's cache files when navigation menu is modified */ function wp_cache_clear_cache_on_menu() { global $wpdb; wp_cache_clear_cache( $wpdb->blogid ); } /* Clear out the cache directory. */ function wp_cache_clear_cache( $blog_id = 0 ) { global $cache_path, $wp_cache_object_cache; if ( $wp_cache_object_cache ) { reset_oc_version(); } else { if ( $blog_id == 0 ) { wp_cache_debug( "Clearing all cached files in wp_cache_clear_cache()", 4 ); prune_super_cache( $cache_path . 'supercache/', true ); prune_super_cache( $cache_path, true ); } else { wp_cache_debug( "Clearing all cached files for blog $blog_id in wp_cache_clear_cache()", 4 ); prune_super_cache( get_supercache_dir( $blog_id ), true ); prune_super_cache( $cache_path . 'blogs/', true ); } } } function wpsc_delete_cats_tags( $post ) { $post = get_post($post); $categories = get_the_category($post->ID); if ( $categories ) { $category_base = get_option( 'category_base'); if ( $category_base == '' ) $category_base = '/category/'; $category_base = trailingslashit( $category_base ); // paranoid much? foreach ($categories as $cat) { prune_super_cache ( get_supercache_dir() . $category_base . $cat->slug . '/', true ); wp_cache_debug( "wpsc_post_transition: deleting category: " . get_supercache_dir() . $category_base . $cat->slug . '/' ); } } $posttags = get_the_tags($post->ID); if ( $posttags ) { $tag_base = get_option( 'tag_base' ); if ( $tag_base == '' ) $tag_base = '/tag/'; $tag_base = trailingslashit( str_replace( '..', '', $tag_base ) ); // maybe! foreach ($posttags as $tag) { prune_super_cache( get_supercache_dir() . $tag_base . $tag->slug . '/', true ); wp_cache_debug( "wpsc_post_transition: deleting tag: " . get_supercache_dir() . $tag_base . $tag->slug . '/' ); } } } function wpsc_post_transition( $new_status, $old_status, $post ) { if ( ($old_status == 'publish' && $new_status != 'publish' ) // post unpublished || ($old_status != 'publish' && $new_status == 'publish') // post published ) { wpsc_delete_cats_tags( $post ); prune_super_cache( get_supercache_dir() . '/' . $post->post_name . '/', true ); wp_cache_debug( "wpsc_post_transition: deleting post: " . get_supercache_dir() . '/' . $post->post_name . '/' ); } } /* check if we want to clear out all cached files on post updates, otherwise call standard wp_cache_post_change() */ function wp_cache_post_edit($post_id) { global $wp_cache_clear_on_post_edit, $cache_path, $blog_cache_dir, $wp_cache_object_cache; static $last_post_edited = -1; if ( $post_id == $last_post_edited ) { wp_cache_debug( "wp_cache_post_edit: Already processed post $post_id.", 4 ); return $post_id; } $post = get_post( $post_id ); if ( is_object( $post ) == false ) return $post_id; // Some users are inexplicibly seeing this error on scheduled posts. // define this constant to disable the post status check. if ( false == defined( 'WPSCFORCEUPDATE' ) && $post->post_status != 'publish' ) { wp_cache_debug( "wp_cache_post_edit: draft post, not deleting any cache files. status: " . $post->post_status, 4 ); return $post_id; } // we want to process the post again just in case it becomes published before the second time this function is called. $last_post_edited = $post_id; if( $wp_cache_clear_on_post_edit ) { wp_cache_debug( "wp_cache_post_edit: Clearing cache $blog_cache_dir and {$cache_path}supercache/ on post edit per config.", 2 ); if ( $wp_cache_object_cache ) { reset_oc_version(); } else { prune_super_cache( $blog_cache_dir, true ); prune_super_cache( get_supercache_dir(), true ); } } else { wp_cache_debug( "wp_cache_post_edit: Clearing cache for post $post_id on post edit.", 2 ); wp_cache_post_change( $post_id ); } } function wp_cache_post_id_gc( $siteurl, $post_id, $all = 'all' ) { global $cache_path, $wp_cache_object_cache, $wp_cache_refresh_single_only; if ( $wp_cache_object_cache ) reset_oc_version(); $post_id = intval( $post_id ); if( $post_id == 0 ) return; $permalink = trailingslashit( str_replace( get_option( 'home' ), '', get_permalink( $post_id ) ) ); $dir = get_current_url_supercache_dir( $post_id ); wp_cache_debug( "wp_cache_post_id_gc post_id: $post_id " . get_permalink( $post_id ) . " clearing cache in $dir.", 4 ); if ( $all ) { prune_super_cache( $dir, true, true ); do_action( 'gc_cache', 'prune', $permalink ); @rmdir( $dir ); wp_cache_debug( "wp_cache_post_id_gc clearing cache in {$supercache_home}page/." ); $supercache_home = get_supercache_dir(); prune_super_cache( $supercache_home . 'page/', true ); do_action( 'gc_cache', 'prune', 'page/' ); } else { wp_cache_debug( "wp_cache_post_id_gc clearing cached index files in $dir.", 4 ); prune_super_cache( $dir, true, true ); do_action( 'gc_cache', 'prune', $permalink ); } } function wp_cache_post_change( $post_id ) { global $file_prefix, $cache_path, $blog_id, $super_cache_enabled, $blog_cache_dir, $blogcacheid, $wp_cache_refresh_single_only, $wp_cache_object_cache; static $last_processed = -1; if ( $post_id == $last_processed ) { wp_cache_debug( "wp_cache_post_change: Already processed post $post_id.", 4 ); return $post_id; } $post = get_post( $post_id ); // Some users are inexplicibly seeing this error on scheduled posts. // define this constant to disable the post status check. if ( false == defined( 'WPSCFORCEUPDATE' ) && is_object( $post ) && $post->post_status != 'publish' ) { wp_cache_debug( "wp_cache_post_change: draft post, not deleting any cache files.", 4 ); return $post_id; } $last_processed = $post_id; if( !wp_cache_writers_entry() ) return $post_id; if ( isset( $wp_cache_refresh_single_only ) && $wp_cache_refresh_single_only && ( strpos( $_SERVER[ 'HTTP_REFERER' ], 'edit-comments.php' ) || strpos( $_SERVER[ 'REQUEST_URI' ], 'wp-comments-post.php' ) ) ) { if ( defined( 'DONOTDELETECACHE' ) ) { wp_cache_debug( "wp_cache_post_change: comment detected and it's moderated or spam. Not deleting cached files.", 4 ); return $post_id; } else { wp_cache_debug( "wp_cache_post_change: comment detected. only deleting post page.", 4 ); $all = false; } } else { $all = true; } $all_backup = $all; $all = apply_filters( 'wpsc_delete_related_pages_on_edit', $all ); // return 0 to disable deleting homepage and other pages. if ( $all != $all_backup ) wp_cache_debug( 'wp_cache_post_change: $all changed by wpsc_delete_related_pages_on_edit filter: ' . intval( $all ) ); if ( $wp_cache_object_cache ) reset_oc_version(); $permalink = trailingslashit( str_replace( get_option( 'siteurl' ), '', get_permalink( $post_id ) ) ); // Delete supercache files whenever a post change event occurs, even if supercache is currently disabled. $dir = get_supercache_dir(); $siteurl = trailingslashit( strtolower( preg_replace( '/:.*$/', '', str_replace( 'https://', '', str_replace( 'http://', '', get_option( 'home' ) ) ) ) ) ); // make sure the front page has a rebuild file wp_cache_post_id_gc( $siteurl, $post_id, $all ); if ( $all == true ) { wp_cache_debug( "Post change: supercache enabled: deleting cache files in " . $cache_path . 'supercache/' . $siteurl, 4 ); $files_to_check = get_all_supercache_filenames( $dir ); foreach( $files_to_check as $cache_file ) { wp_cache_debug( "Post change: deleting cache file: " . $dir . $cache_file, 4 ); prune_super_cache( $dir . $cache_file, true, true ); } do_action( 'gc_cache', 'prune', 'homepage' ); } else { wp_cache_debug( "wp_cache_post_change: not deleting all pages.", 4 ); } if( $all == true && get_option( 'show_on_front' ) == 'page' ) { wp_cache_debug( "Post change: deleting page_on_front and page_for_posts pages.", 4 ); wp_cache_debug( "Post change: page_on_front " . get_option( 'page_on_front' ), 4 ); $permalink = trailingslashit( str_replace( get_option( 'home' ), '', get_permalink( get_option( 'page_for_posts' ) ) ) ); $files_to_check = get_all_supercache_filenames( $dir . $permalink ); foreach( $files_to_check as $cache_file ) { prune_super_cache( $dir . $permalink . $cache_file, true, true ); } do_action( 'gc_cache', 'prune', $permalink ); } else { wp_cache_debug( "wp_cache_post_change: not deleting front static page.", 4 ); } wp_cache_debug( "wp_cache_post_change: checking {$blog_cache_dir}meta/", 4 ); $supercache_files_deleted = false; if ( $handle = @opendir( $blog_cache_dir ) ) { while ( false !== ($file = readdir($handle))) { if ( strpos( $file, $file_prefix ) !== false ) { if ( strpos( $file, '.html' ) ) { // delete old legacy files immediately wp_cache_debug( "wp_cache_post_change: Deleting obsolete legacy cache+meta files: $file" ); @unlink( $blog_cache_dir . $file); @unlink( $blog_cache_dir . 'meta/' . str_replace( '.html', '.meta', $file ) ); continue; } else { $meta = json_decode( wp_cache_get_legacy_cache( $blog_cache_dir . 'meta/' . $file ), true ); if( false == is_array( $meta ) ) { wp_cache_debug( "Post change cleaning up stray file: $file", 4 ); @unlink( $blog_cache_dir . 'meta/' . $file ); @unlink( $blog_cache_dir . $file ); continue; } if ( $post_id > 0 && $meta ) { $permalink = trailingslashit( str_replace( get_option( 'home' ), '', get_permalink( $post_id ) ) ); if ( $meta[ 'blog_id' ] == $blog_id && ( ( $all == true && !$meta[ 'post' ] ) || $meta[ 'post' ] == $post_id) ) { wp_cache_debug( "Post change: deleting post wp-cache files for {$meta[ 'uri' ]}: $file", 4 ); @unlink( $blog_cache_dir . 'meta/' . $file ); @unlink( $blog_cache_dir . $file ); if ( false == $supercache_files_deleted && $super_cache_enabled == true ) { $files_to_check = get_all_supercache_filenames( $dir . $permalink ); wp_cache_debug( "Post change: deleting supercache files for {$permalink}: $file " . print_r( $files_to_check, 1 ), 4 ); foreach( $files_to_check as $cache_file ) { @wp_cache_rebuild_or_delete( $dir . trailingslashit( $permalink ) . $cache_file ); } $supercache_files_deleted = true; do_action( 'gc_cache', 'rebuild', $permalink ); } } } elseif ( $meta[ 'blog_id' ] == $blog_id ) { wp_cache_debug( "Post change: deleting wp-cache files for {$meta[ 'uri' ]}: $file", 4 ); @unlink( $blog_cache_dir . 'meta/' . $file ); @unlink( $blog_cache_dir . $file ); if ( $super_cache_enabled == true ) { $files_to_check = get_all_supercache_filenames( $dir . $meta[ 'uri' ] ); wp_cache_debug( "Post change: deleting supercache files for {$meta[ 'uri' ]}: $file " . print_r( $files_to_check, 1 ), 4 ); foreach( $files_to_check as $cache_file ) { @wp_cache_rebuild_or_delete( $dir . trailingslashit( $meta[ 'uri' ] ) . $cache_file ); } do_action( 'gc_cache', 'rebuild', trailingslashit( $meta[ 'uri' ] ) ); } } } } } closedir($handle); } wp_cache_writers_exit(); return $post_id; } function wp_cache_microtime_diff($a, $b) { list($a_dec, $a_sec) = explode(' ', $a); list($b_dec, $b_sec) = explode(' ', $b); return $b_sec - $a_sec + $b_dec - $a_dec; } function wp_cache_post_id() { global $posts, $comment_post_ID, $post_ID; // We try hard all options. More frequent first. if ($post_ID > 0 ) return $post_ID; if ($comment_post_ID > 0 ) return $comment_post_ID; if (is_single() || is_page()) return $posts[0]->ID; if (isset( $_GET[ 'p' ] ) && $_GET['p'] > 0) return $_GET['p']; if (isset( $_POST[ 'p' ] ) && $_POST['p'] > 0) return $_POST['p']; return 0; } function maybe_stop_gc( $flag ) { if ( @file_exists( $flag ) ) { if ( time() - filemtime( $flag ) > 3600 ) { @unlink( $flag ); wp_cache_debug( "maybe_stop_gc: GC flag found but deleted because it's older than 3600 seconds.", 5 ); return false; } else { wp_cache_debug( 'maybe_stop_gc: GC flag found. GC cancelled.', 5 ); return true; } } else { wp_cache_debug( 'maybe_stop_gc: GC flag not found. GC will go ahead..', 5 ); return false; } } function get_gc_flag() { global $cache_path; return $cache_path . strtolower( preg_replace( '!/:.*$!', '', str_replace( 'http://', '', str_replace( 'https://', '', get_option( 'home' ) ) ) ) ) . "_wp_cache_gc.txt"; } function wp_cache_gc_cron() { global $file_prefix, $cache_max_time, $cache_gc_email_me, $cache_time_interval; $msg = ''; if ( $cache_max_time == 0 ) { wp_cache_debug( 'Cache garbage collection disabled because cache expiry time is zero.', 5 ); return false; } $gc_flag = get_gc_flag(); if ( maybe_stop_gc( $gc_flag ) ) { wp_cache_debug( 'GC flag found. GC cancelled.', 5 ); return false; } update_option( 'wpsupercache_gc_time', time() ); wp_cache_debug( "wp_cache_gc_cron: Set GC Flag. ($gc_flag)", 5 ); $fp = @fopen( $gc_flag, 'w' ); @fclose( $fp ); wp_cache_debug( 'Cache garbage collection.', 5 ); if( !isset( $cache_max_time ) ) $cache_max_time = 600; $start = time(); $num = 0; if( false === ( $num = wp_cache_phase2_clean_expired( $file_prefix ) ) ) { wp_cache_debug( 'Cache Expiry cron job failed. Probably mutex locked.', 1 ); update_option( 'wpsupercache_gc_time', time() - ( $cache_time_interval - 10 ) ); // if GC failed then run it again in one minute $msg .= __( 'Cache expiry cron job failed. Job will run again in 10 seconds.', 'wp-super-cache' ) . "\n"; } if( time() - $start > 30 ) { wp_cache_debug( "Cache Expiry cron job took more than 30 seconds to execute.\nYou should reduce the Expiry Time in the WP Super Cache admin page\nas you probably have more cache files than your server can handle efficiently.", 1 ); $msg .= __( 'Cache expiry cron job took more than 30 seconds. You should probably run the garbage collector more often.', 'wp-super-cache' ) . "\n"; } if ( $cache_gc_email_me ) { if ( $msg != '' ) $msg = "The following warnings were generated by the WP Super Cache Garbage Collector:\n" . $msg; $msg = "Hi,\n\nThe WP Super Cache Garbage Collector has now run, deleting " . (int)$num . " files and directories.\nIf you want to switch off these emails please see the WP Super Cache Advanced Settings\npage on your blog.\n\n{$msg}\nRegards,\nThe Garbage Collector."; wp_mail( get_option( 'admin_email' ), sprintf( __( '[%1$s] WP Super Cache GC Report', 'wp-super-cache' ), home_url() ), $msg ); } @unlink( $gc_flag ); wp_cache_debug( 'GC completed. GC flag deleted.', 5 ); schedule_wp_gc( 1 ); } function schedule_wp_gc( $forced = 0 ) { global $cache_schedule_type, $cache_max_time, $cache_time_interval, $cache_scheduled_time, $cache_schedule_interval; if ( false == isset( $cache_time_interval ) ) $cache_time_interval = 3600; if ( false == isset( $cache_schedule_type ) ) { $cache_schedule_type = 'interval'; $cache_schedule_interval = $cache_max_time; } if ( $cache_schedule_type == 'interval' ) { if ( !isset( $cache_max_time ) ) $cache_max_time = 600; if ( $cache_max_time == 0 ) return false; $last_gc = get_option( "wpsupercache_gc_time" ); if ( !$last_gc ) { update_option( 'wpsupercache_gc_time', time() ); $last_gc = get_option( "wpsupercache_gc_time" ); } if ( $forced || ( $last_gc < ( time() - 60 ) ) ) { // Allow up to 60 seconds for the previous job to run global $wp_cache_shutdown_gc; if ( !isset( $wp_cache_shutdown_gc ) || $wp_cache_shutdown_gc == 0 ) { if ( !($t = wp_next_scheduled( 'wp_cache_gc' ) ) ) { wp_clear_scheduled_hook( 'wp_cache_gc' ); wp_schedule_single_event( time() + $cache_time_interval, 'wp_cache_gc' ); wp_cache_debug( 'scheduled wp_cache_gc for 10 seconds time.', 5 ); } } else { global $time_to_gc_cache; $time_to_gc_cache = 1; // tell the "shutdown gc" to run! } } } elseif ( $cache_schedule_type == 'time' && !wp_next_scheduled( 'wp_cache_gc' ) ) { wp_schedule_event( strtotime( $cache_scheduled_time ), $cache_schedule_interval, 'wp_cache_gc' ); } return true; } function wp_cache_gc_watcher() { if ( false == wp_next_scheduled( 'wp_cache_gc' ) ) { wp_cache_debug( 'GC Watcher: scheduled new gc cron.', 5 ); schedule_wp_gc(); } } ?> Changelog.txt000066600000044000152133035240007174 0ustar002017-02-03 17:17 donncha * readme.txt, wp-cache.php: Bump version number to 1.4.9 and update changelog 2017-02-03 17:11 donncha * wp-cache-phase1.php, wp-cache-phase2.php, wp-cache.php: * Github merge: * Make sure $cache_path has a trailing slash (https://github.com/Automattic/wp-super-cache/pull/77) * Remove flush() (https://github.com/Automattic/wp-super-cache/pull/127) but also check if headers are empty and flush and get headers again. (https://github.com/Automattic/wp-super-cache/pull/179) * Add fix for customizer (https://github.com/Automattic/wp-super-cache/pull/161) and don't cache PUT AND DELETE requests (https://github.com/Automattic/wp-super-cache/pull/178) * Check for superglobals before using them. (https://github.com/Automattic/wp-super-cache/pull/131) 2017-02-03 16:54 donncha * plugins/multisite.php, wp-cache-base.php, wp-cache.php: Github merge: Need to check more than WP_ALLOW_MULTISITE to detect multisite installs. https://github.com/Automattic/wp-super-cache/issues/97 2017-02-03 15:07 donncha * wp-cache-phase1.php: Github merge: https://github.com/Automattic/wp-super-cache/pull/161 and also don't cache PUT and DELETE requests (caught earlier than before) 2017-02-03 14:45 donncha * plugins/jetpack.php: Remove extra ">", props @dd32 https://github.com/Automattic/wp-super-cache/pull/168 2017-02-03 14:37 donncha * wp-super-cache.pot: Updated translation file 2017-02-03 14:33 donncha * wp-cache.php: github merge: some of the changes that were supposed to be checked in the previous merge didn't make it. 2017-02-03 10:18 donncha * readme.txt: * Bump the tested version. * Update the changelog 2017-02-03 10:13 donncha * Changelog.txt: Updated changelog 2017-02-02 18:14 donncha * readme.txt: Updated readme.txt changelog and docs 2017-02-02 18:08 donncha * ossdl-cdn.php, readme.txt, wp-cache-phase2.php, wp-cache.php: Sync with GITHUB: * Don't delete so many files on blogs with static homepages. https://github.com/Automattic/wp-super-cache/pull/175 * Discourage use of file locking because semaphores cause problems and it's not needed. https://github.com/Automattic/wp-super-cache/pull/174 * Reorganise the settings page in small ways https://github.com/Automattic/wp-super-cache/pull/173 * Fixed XSS in settings page. Props @jaypatel https://github.com/Automattic/wp-super-cache/pull/172 2017-01-11 16:58 kraftbj * readme.txt, wp-cache-phase2.php: Github #138: Do not cache PUT/DELETE requests 2016-12-09 15:38 kraftbj * wp-cache-phase2.php: Check that header parts exist to avoid `Undefined Index` notices 2016-12-09 15:37 kraftbj * wp-cache-phase2.php: Update to Git master 2016-12-09 10:25 donncha * readme.txt: Bump the "tested up to" value 2016-08-01 20:39 kraftbj * readme.txt: Bump tested version to 4.6 2016-05-09 14:56 kraftbj * readme.txt: Bump tested version 2016-03-07 15:24 kraftbj * readme.txt: Update readme for previous commit 2016-03-07 15:20 kraftbj * wp-cache-phase2.php: Catch up SVN to GH 2016-03-07 13:46 donncha * readme.txt, wp-cache.php: Bumped version to 1.4.8 and updated changelog 2016-03-07 13:39 donncha * wp-super-cache.pot: Updated translation pot file 2016-03-07 12:37 donncha * wp-cache.php: Remove this link as Google is reporting it as malware. It's still available at https://web.archive.org/web/20150914095007/http://bytes.com/topic/php/answers/3917-seconds-converted-hh-mm-ss. Ref: https://github.com/Automattic/wp-super-cache/issues/106 2015-12-16 18:14 kraftbj * readme.txt, wp-cache.php: Update readme for 1.4.7 2015-12-16 16:59 kraftbj * wp-cache.php: Fix settings page layout breakage in 4.4. 2015-12-02 15:50 kraftbj * ossdl-cdn.php, wp-cache.php: Corrects typos. See https://github.com/Automattic/wp-super-cache/issues/81 props https://github.com/christophherr 2015-10-21 19:54 kraftbj * wp-cache-phase1.php: Remove variable no longer defined after previous update. 2015-10-09 18:06 donncha * Changelog.txt, readme.txt, wp-cache.php: Bump version to 1.4.6 and update changelog 2015-10-08 17:14 donncha * wp-cache.php: Don't check if .htaccess already created as the index check already created it. Props Tigertech. Ref: https://wordpress.org/support/topic/all-website-pages-downloading-gz-file-after-latest-update?replies=28#post-7494087 2015-09-25 11:20 donncha * Changelog.txt: Updated changelog 2015-09-25 10:55 donncha * readme.txt, wp-cache.php: Bump version to release 1.4.5 and add changelog 2015-09-24 15:37 donncha * wp-cache-base.php, wp-cache-phase1.php, wp-cache-phase2.php, wp-cache.php: * Add index.html files and "-index" directives to stop indexing of directories * Sanitise input on settings page * MD5 the cookie, use JSON to encode meta files, and rename them to .php 2015-09-24 11:37 donncha * readme.txt: Changed homepage link and ocaoimh.ie to z9.io 2015-09-24 11:33 donncha * readme.txt: Minor update to the description of cache rebuild feature. 2015-09-24 10:39 donncha * wp-cache-phase2.php: Reduce "needs rebuild" time to 10 seconds, so those pages refresh faster. 2015-08-28 16:28 donncha * wp-cache-phase1.php: Because sometimes your editing in HTTPS while your site is on HTTP. Thanks kraftbj 2015-08-25 21:42 kraftbj * wp-cache-phase2.php: Swap post_permalink with get_permalink. Both are exactly the same and old enough to not impact any users. post_permalink slated for deprecation in 4.4. 2015-08-10 14:06 donncha * wp-cache-phase2.php: Avoid PHP warnings, props @daneodekirk 2015-08-10 13:25 donncha * wp-cache.php: Use $wpdb->blogid rather than get_current_blog_id as the former returns 0 on single site installs. Props @daneodekirk 2015-07-30 10:13 donncha * Changelog.txt, readme.txt: Updated changelog 2015-07-29 13:08 donncha * wp-cache-phase2.php: Remove this function call as it's not defined. Ref: https://github.com/Automattic/wp-super-cache/commit/4f3229009e5c6c8487dd883910ea076a8e3b7e26 2015-07-27 16:36 kraftbj * wp-cache.php: Don't flush settings for expiry time and garbage collection. See https://github.com/Automattic/wp-super-cache/pull/49 2015-07-27 16:28 donncha * wp-cache-base.php: Remove CacheMeta class as it's not used any more and caused APC errors. Ref: https://github.com/Automattic/wp-super-cache/pull/21 2015-07-24 15:21 kraftbj * wp-cache.php: Check if listfile isset to prevent PHP warning. 2015-07-23 13:56 donncha * wp-cache.php: Remember the settings on the advanced settings page when submitting the easy settings form. Thanks Jeremy Herve for the bug report! 2015-07-22 15:52 donncha * Changelog.txt, readme.txt: Updated changelog 2015-07-22 11:25 donncha * wp-cache-phase2.php: Fixed typo in debug log entry 2015-07-15 11:56 donncha * wp-cache.php: * Added uninstall function as well as deactivate function. The deactivate function does not delete the config file but it does disable caching because scheduled jobs must be enabled in the settings page when the config file is used on activation again. * Fixed a bug where deactivating the plugin without visiting the settings page causes a fatal error so the plugin can't be deactivated 2015-07-02 14:19 donncha * wp-cache-phase2.php: Minor changes to debugging 2015-07-02 13:58 donncha * wp-cache-phase2.php: * prune_super_cache: exit immediately if the file to be deleted doesn't exist * Add extra debugging 2015-07-02 12:10 donncha * wp-cache-phase2.php: Remove https from the home url as well 2015-07-01 16:37 donncha * wp-cache-phase2.php: As so many checks for "should we cache this page?" were put to the end of page generation the rebuild system was broken. This fixes it by deleting the rebuild files created earlier if the current page isn't to be cached (and thus creating new cache files) 2015-07-01 15:46 donncha * wp-cache-phase1.php: Always make sure supercachedirs have trailing slashes 2015-07-01 15:30 donncha * wp-cache-phase1.php: Cache the output of wp_cache_get_cookies_values() for repeat calls 2015-07-01 14:59 donncha * wp-cache-phase1.php: Use the pid to help logging on busy servers 2015-07-01 14:51 donncha * plugins/domain-mapping.php: Suercache urls end in slashes 2015-06-23 15:32 kraftbj * wp-cache-phase1.php: Check for If-Modified-Since before using it as it is not always defined. 2015-06-03 02:36 kraftbj * advanced-cache.php: Do not display broken messages for XMLRPC, REST, AJAX requests. 2015-05-15 14:12 kraftbj * wp-cache-phase2.php, wp-cache.php: Fix improper site_url usage * Update site_url to home_url in another e-mail subject * Use admin_url instead of constructing URL from site_url 2015-05-15 14:08 kraftbj * wp-cache.php: Use home_url in Preload Cron e-mails. 2015-05-15 11:13 donncha * wp-cache-phase1.php, wp-cache-phase2.php: Revert 1149165 as it's not needed any more. 2015-05-15 11:02 donncha * readme.txt: Bump the tested to version number to 4.2.2 2015-05-13 21:01 kraftbj * wp-cache.php: Improve the 1&1 hosting workaround to reduce false positives. 2015-05-01 13:53 donncha * wp-cache.php: Check if it's an array to avoid PHP warning 2015-05-01 13:51 donncha * wp-cache-phase2.php: Added some extra debugging 2015-04-29 16:55 kraftbj * readme.txt: Condense changelog to keep it nice and short :) 2015-04-29 15:58 kraftbj * readme.txt: Update changelog to keep pace with trunk. 2015-04-29 15:45 donncha * wp-cache-phase1.php, wp-cache-phase2.php: Check if mb_strlen() exists before WordPress loads so it doesn't use the limited mb_strlen compat function in WordPress 4.2. Ref: https://wordpress.org/support/topic/421-initial-blank-page-load?replies=11 2015-04-28 15:53 kraftbj * readme.txt: Add previous commits to readme.txt as a running changelog to make it easier to compile for next release. 2015-04-28 15:24 kraftbj * wp-cache.php: Preload Cron E-mail Updates 2015-04-28 15:17 kraftbj * wp-cache.php: Preload only public post types. See https://github.com/Automattic/wp-super-cache/pull/18 2015-04-21 18:22 kraftbj * readme.txt: Tested to tag bump to 4.2 2015-04-07 16:00 donncha * wp-cache-phase2.php: Don't disable supercache caching on CRON requests. Fixes problems clearing front page cache on scheduled posts 2015-04-04 22:57 donncha * wp-cache-phase1.php: Fix the log_message, finally. Props webaware. 2015-04-04 12:17 donncha * Changelog.txt: Updated changelog 2015-04-04 12:13 donncha * readme.txt: Updated changelog 2015-04-04 12:12 donncha * wp-cache-phase1.php: Make sure we log the actual message in the debug log. 2015-04-04 12:00 donncha * Changelog.txt: Updated changelog 2015-04-04 11:55 donncha * readme.txt, wp-cache.php: Bump version to 1.4.4 and update changelog 2015-04-04 11:47 donncha * wp-cache-phase1.php, wp-cache-phase2.php: Don't use print_r to view GET variables as it causes a fatal PHP error in the output buffer handler. Props webaware https://wordpress.org/support/topic/print_r-debug-messages-break-pages-with-query-args?replies=2 2015-04-03 16:51 donncha * Changelog.txt: Updated changelog 2015-04-03 16:44 donncha * readme.txt, wp-cache.php: Bump version to 1.4.3, update changelog, and add link to GIT repo. 2015-04-03 15:37 donncha * wp-cache.php: Escape the contents of the cache list to avoid surprises. Props Marc Montpas from Sucuri. 2014-12-18 10:55 jeherve * readme.txt: Bump testing to 4.1 2014-10-10 14:07 kraftbj * plugins/jetpack.php, wp-cache-phase1.php, wp-cache-phase2.php, wp-cache.php: Removing variable checks since wp_cache_debug does it already. Ref: https://github.com/Automattic/wp-super-cache/pull/15 2014-10-10 14:06 kraftbj * readme.txt: Catch up to SVN 2014-10-10 14:06 kraftbj * readme.txt: Add Jetpack to mobile FAQ. 2014-09-04 14:16 kraftbj * readme.txt: Bumped testing to 4.0 2014-08-11 19:06 donncha * plugins/dynamic-cache-test.php: Because without a h we'd have time keeping. Fixed a typo. 2014-08-11 18:44 donncha * plugins/dynamic-cache-test.php: Added cronology of a request 2014-08-11 18:22 donncha * plugins/dynamic-cache-test.php: Fixed the safety function in the first example test function 2014-08-08 16:27 donncha * Changelog.txt, readme.txt, wp-cache.php: Bump version to 1.4.2 and update changelog 2014-08-08 13:07 donncha * wp-cache-phase1.php: Just in case the local modified time of a file is 0, disable the "last modified time" check. 2014-08-08 11:32 donncha * plugins/domain-mapping.php: Check if HTTPS exists before checking it's value to avoid warnings 2014-08-08 11:24 donncha * wp-cache.php: Replace wpdb->escape with esc_sql() as it's deprecated. 2014-08-08 11:21 donncha * wp-cache-phase2.php: Make sure $wp_cache_no_cache_for_get, $wp_cache_object_cache, $wp_cache_request_uri are visible to the OB callback to avoid warnings and fix functionality 2014-08-07 14:00 donncha * Changelog.txt, readme.txt, wp-cache.php: Updated changelog, documentation, bumped version number to 1.4.1 and tested version. 2014-08-07 12:45 donncha * wp-cache.php: Removed author information 2014-08-06 12:41 kraftbj * plugins/awaitingmoderation.php, plugins/badbehaviour.php, plugins/domain-mapping.php, plugins/jetpack.php, plugins/searchengine.php, plugins/wptouch.php, wp-cache.php: PR #13: Added .button-primary and .button-secondary classes to and removed »'s from buttons throughout the admin for consistency. Ref: https://github.com/Automattic/wp-super-cache/pull/13 Props: rcowles 2014-08-05 20:00 kraftbj * ossdl-cdn.php, readme.txt, wp-cache.php: Fix bad merge. 2014-08-05 19:56 kraftbj * readme.txt: Add Jetpack to mobile FAQ. 2014-08-05 19:56 kraftbj * wp-cache.php: Remove CDN Sync Tools. No longer in WP.org repo 2014-08-05 19:55 kraftbj * ossdl-cdn.php, readme.txt, wp-cache.php: Update wordpress.org/extend URLs 2014-08-05 12:42 donncha * wp-cache.php: Fix to avoid an XSS in the settings page. Props Simon Waters, Surevine Limited. 2014-08-04 22:04 kraftbj * ossdl-cdn.php: Remove reference to CDN Sync. Plugin no longer in repo. 2014-07-31 21:09 kraftbj * readme.txt: Add Jetpack to mobile FAQ. 2014-07-31 21:09 kraftbj * wp-cache.php: Remove CDN Sync Tools. No longer in WP.org repo 2014-07-31 21:08 kraftbj * ossdl-cdn.php, readme.txt, wp-cache-phase1.php, wp-cache.php: Update wordpress.org/extend URLs 2014-07-31 21:08 kraftbj * plugins/awaitingmoderation.php, plugins/badbehaviour.php, plugins/domain-mapping.php, plugins/dynamic-cache-test.php, plugins/jetpack.php, plugins/searchengine.php, plugins/wptouch.php: Trim whitespace 2014-07-31 21:07 kraftbj * wp-cache-config-sample.php, wp-cache-phase1.php, wp-cache.php: Trim whitespace 2014-07-31 21:06 kraftbj * wp-cache.php: Admin: Add clear to h3 to pretify Recommended Links title 2014-07-31 20:51 donncha * wp-cache-phase2.php: Make sure these are global so the function knows about them. Props JoHenton and richardmtl http://wordpress.org/support/topic/notices-appearing-above-site-pages-how-do-i-get-rid-of-them?replies=2 2014-04-17 16:21 donncha * readme.txt: Bump tested version to 3.9 2014-03-11 17:58 donncha * wp-cache.php: Fix undefined variables warnings. Ref: http://wordpress.org/support/topic/plugin-wp-super-cache-lot-of-undefined-variables-and-couple-of-warnings?replies=4 2014-03-07 18:00 donncha * plugins/dynamic-cache-test.php: Better comments and rearrange example scripts 2014-03-05 12:37 donncha * wp-cache-phase1.php: HTTP_IF_MODIFIED_SINCE isn't always defined, so check first. http://wordpress.org/support/topic/undefined-index-http_if_modified_since?replies=1 2014-03-05 11:54 donncha * wp-cache-phase1.php, wp-cache-phase2.php: Don't check "do not cache" conditions until after page buffer has been filled. Ref: http://wordpress.org/support/topic/bug-dynamic-cache-tags-are-not-replaced-because-of-wp_cache_phase2-conditions 2014-03-04 17:26 donncha * wp-cache-phase2.php: Added the function wp_cache_maybe_dynamic() to run buffer through the dynamic cache filter if callback returned early. Ref: http://wordpress.org/support/topic/bug-dynamic-cache-tags-are-not-replaced-because-of-wp_cache_phase2-conditions?replies=1 2014-03-04 16:27 donncha * wp-cache-phase1.php: Hide any warnings from this opendir() as it somehow fails occasionally. 2014-02-25 17:48 donncha * wp-cache.php: Clear the cache for the current blog only, don't want to mess with other multisite blogs 2014-02-25 16:24 donncha * readme.txt: Bump tested version to current WP version 2013-11-29 15:34 donncha * wp-cache-phase2.php: Check that $post is an object as this function is used for more than just post changes. http://wordpress.org/support/topic/error-switching-themes?replies=2 2013-11-12 09:55 donncha * advanced-cache.php: Don't show the "advanced-cache.php warning" when the plugin isn't loaded, props RobertHarm, http://wordpress.org/support/topic/wp-super-cache-breaks-leaflet-maps-marker-plugin 2013-10-25 14:37 donncha * wp-cache.php: Define $disable_supercache_htaccess_warning if not set to avoid PHP warnings, ref: http://wordpress.org/support/topic/just-a-few-notices-non-critical?replies=1, props @mattV 2013-10-25 14:33 donncha * wp-cache-base.php: Avoid a PHP warning if $base is not set. Ref: http://wordpress.org/support/topic/just-a-few-notices-non-critical?replies=1 2013-10-25 09:29 donncha * wp-cache.php: Only display the WPCACHEHOME warning if WP_CACHE is defined and true. Warning won't show until settings page loaded that WP_CACHE added to wp-config.php 2013-10-24 11:23 donncha * wp-cache.php: Add trailing slashes to the admin bar path, to fix the path when no trailing slash is used. Props @gonperesgmailcom http://wordpress.org/support/topic/fixed-delete-individual-pages-from-cache?replies=2 2013-10-23 10:56 donncha * readme.txt, wp-cache.php: Bump version to 1.4 and tested version to 3.6.1 wp-super-cache.pot000066600000161424152133035240010125 0ustar00# Copyright (C) 2017 WP Super Cache # This file is distributed under the same license as the WP Super Cache package. msgid "" msgstr "" "Project-Id-Version: WP Super Cache 1.4.8\n" "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-super-cache\n" "POT-Creation-Date: 2017-02-03 14:34:28+00:00\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "PO-Revision-Date: 2017-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" #: ossdl-cdn.php:153 msgid "" "Your website probably uses lots of static files. Image, Javascript and CSS " "files are usually static files that could just as easily be served from " "another site or CDN. Therefore, this plugin replaces any links in the " "wp-content and wp-includes directories (except for " "PHP files) on your site with the URL you provide below. That way you can " "either copy all the static content to a dedicated host or mirror the files " "to a CDN by origin pull." msgstr "" #: ossdl-cdn.php:154 msgid "" "WARNING: Test some static urls e.g., " "%s to ensure your CDN service is fully working before saving changes." msgstr "" #: ossdl-cdn.php:155 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "" #: ossdl-cdn.php:163 msgid "Enable CDN Support" msgstr "" #: ossdl-cdn.php:166 msgid "Off-site URL" msgstr "" #: ossdl-cdn.php:169 msgid "" "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "" #: ossdl-cdn.php:173 msgid "Include directories" msgstr "" #: ossdl-cdn.php:176 msgid "" "Directories to include in static file matching. Use a comma as the " "delimiter. Default is wp-content, wp-includes, which will be " "enforced if this field is left empty." msgstr "" #: ossdl-cdn.php:180 msgid "Exclude if substring" msgstr "" #: ossdl-cdn.php:183 msgid "" "Excludes something from being rewritten if one of the above strings is found " "in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "" #: ossdl-cdn.php:187 msgid "Additional CNAMES" msgstr "" #: ossdl-cdn.php:190 msgid "" "These CNAMES will " "be used in place of %1$s for rewriting (in addition to the off-site URL " "above). Use a comma as the delimiter. For pages with a large number of " "static files, this can improve browser performance. CNAMEs may also need to " "be configured on your CDN.
    Example: %2$s" msgstr "" #: ossdl-cdn.php:194 msgid "Skip https URLs to avoid \"mixed content\" errors" msgstr "" #: ossdl-cdn.php:198 msgid "Save Changes" msgstr "" #: ossdl-cdn.php:200 msgid "" "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "" #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "" #: plugins/awaitingmoderation.php:34 plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:75 plugins/jetpack.php:31 #: plugins/searchengine.php:69 plugins/wptouch.php:22 wp-cache.php:1501 msgid "Enabled" msgstr "" #: plugins/awaitingmoderation.php:35 plugins/badbehaviour.php:66 #: plugins/domain-mapping.php:76 plugins/jetpack.php:32 #: plugins/searchengine.php:70 plugins/wptouch.php:23 wp-cache.php:1501 msgid "Disabled" msgstr "" #: plugins/awaitingmoderation.php:36 msgid "" "Enables or disables plugin to Remove the text \"Your comment is awaiting " "moderation.\" when someone leaves a moderated comment." msgstr "" #: plugins/awaitingmoderation.php:40 plugins/badbehaviour.php:71 #: plugins/domain-mapping.php:81 plugins/jetpack.php:37 #: plugins/searchengine.php:75 plugins/wptouch.php:28 wp-cache.php:1978 #: wp-cache.php:1980 msgid "enabled" msgstr "" #: plugins/awaitingmoderation.php:42 plugins/badbehaviour.php:73 #: plugins/domain-mapping.php:83 plugins/jetpack.php:39 #: plugins/searchengine.php:77 plugins/wptouch.php:30 msgid "disabled" msgstr "" #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "" #: plugins/awaitingmoderation.php:45 plugins/badbehaviour.php:76 #: plugins/domain-mapping.php:86 plugins/jetpack.php:42 #: plugins/searchengine.php:80 plugins/wptouch.php:33 msgid "Update" msgstr "" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "" #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "" #: plugins/badbehaviour.php:68 msgid "" "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-" "behavior/\") " msgstr "" #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "" #: plugins/badbehaviour.php:83 wp-cache.php:1594 wp-cache.php:1599 msgid "Warning!" msgstr "" #: plugins/domain-mapping.php:73 msgid "Domain Mapping" msgstr "" #: plugins/domain-mapping.php:78 msgid "" "Provides support for Domain Mapping plugin to map multiple domains to a " "blog." msgstr "" #: plugins/domain-mapping.php:84 msgid "Domain Mapping support is now %s" msgstr "" #: plugins/domain-mapping.php:98 msgid "" "Domain Mapping plugin detected! Please go to the Supercache plugins page and " "enable the domain mapping helper plugin." msgstr "" #: plugins/jetpack.php:25 msgid "Jetpack Mobile Theme" msgstr "" #: plugins/jetpack.php:28 msgid "" "Jetpack not found in %s. Install it and enable the mobile theme and this " "helper plugin to cache visits by mobile visitors." msgstr "" #: plugins/jetpack.php:34 msgid "" "Provides support for the Jetpack mobile theme and plugin. PHP caching mode and mobile " "support will be enabled too." msgstr "" #: plugins/jetpack.php:40 msgid "Jetpack Mobile Theme support is now %s" msgstr "" #: plugins/multisite.php:13 msgid "Cached" msgstr "" #: plugins/multisite.php:31 wp-cache.php:1514 msgid "Enable" msgstr "" #: plugins/multisite.php:33 plugins/searchengine.php:61 wp-cache.php:1514 msgid "Disable" msgstr "" #: plugins/multisite.php:39 msgid "Caching has been disabled on this blog on the Network Admin Sites page." msgstr "" #: plugins/searchengine.php:67 msgid "No Adverts for Friends" msgstr "" #: plugins/searchengine.php:72 msgid "" "Provides support for No Adverts for Friends." msgstr "" #: plugins/searchengine.php:78 msgid "No Adverts for Friends support is now %s" msgstr "" #: plugins/wptouch.php:20 msgid "WPTouch" msgstr "" #: plugins/wptouch.php:25 msgid "" "Provides support for WPTouch mobile theme and plugin." msgstr "" #: plugins/wptouch.php:31 msgid "WPTouch support is now %s" msgstr "" #: plugins/wptouch.php:45 msgid "" "WPTouch plugin detected! Please go to the Supercache plugins page and enable " "the WPTouch helper plugin." msgstr "" #: wp-cache-phase2.php:1347 msgid "Cache expiry cron job failed. Job will run again in 10 seconds." msgstr "" #: wp-cache-phase2.php:1351 msgid "" "Cache expiry cron job took more than 30 seconds. You should probably run the " "garbage collector more often." msgstr "" #: wp-cache-phase2.php:1360 msgid "[%1$s] WP Super Cache GC Report" msgstr "" #: wp-cache.php:111 msgid "" "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-" "sample.php" msgstr "" #: wp-cache.php:203 msgid "Warning! PHP Safe Mode Enabled!" msgstr "" #: wp-cache.php:204 msgid "" "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "" #: wp-cache.php:208 msgid "" "Your server is set up to check the owner of PHP scripts before allowing them " "to read and write files." msgstr "" #: wp-cache.php:209 msgid "" "You or an administrator may be able to make it work by changing the group " "owner of the plugin scripts to match that of the web server user. The group " "owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further " "details." msgstr "" #: wp-cache.php:211 msgid "" "You or an administrator must disable this. See the safe mode manual page for further details. This " "cannot be disabled in a .htaccess file unfortunately. It must be done in the " "php.ini config file." msgstr "" #: wp-cache.php:217 msgid "Permlink Structure Error" msgstr "" #: wp-cache.php:218 msgid "" "A custom url or permalink structure is required for this plugin to work " "correctly. Please go to the Permalinks " "Options Page to configure your permalinks." msgstr "" #: wp-cache.php:230 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "" #: wp-cache.php:231 msgid "" "Your server thinks your hostname resolves to %s. Some services such as " "garbage collection by this plugin, and WordPress scheduled posts may not " "operate correctly." msgstr "" #: wp-cache.php:232 wp-cache.php:246 msgid "" "Please see entry 16 in the Troubleshooting section of the " "readme.txt" msgstr "" #: wp-cache.php:245 msgid "" "Unfortunately, WordPress cannot find the file wp-cron.php. This script is " "required for the correct operation of garbage collection by this plugin, " "WordPress scheduled posts as well as other critical activities." msgstr "" #: wp-cache.php:259 msgid "Cannot continue... fix previous problems and retry." msgstr "" #: wp-cache.php:268 msgid "Zlib Output Compression Enabled!" msgstr "" #: wp-cache.php:269 msgid "" "PHP is compressing the data sent to the visitors of your site. Disabling " "this is recommended as the plugin caches the compressed output once instead " "of compressing the same page over and over again. Also see #21 in the " "Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "" #: wp-cache.php:273 msgid "Mod rewrite may not be installed!" msgstr "" #: wp-cache.php:274 msgid "" "It appears that mod_rewrite is not installed. Sometimes this check isn’" "t 100% reliable, especially if you are not using Apache. Please verify that " "the mod_rewrite module is loaded. It is required for serving Super Cache " "static files. You will still be able to use legacy or PHP modes." msgstr "" #: wp-cache.php:280 msgid "Read Only Mode. Configuration cannot be changed." msgstr "" #: wp-cache.php:281 msgid "" "The WP Super Cache configuration file is %s/wp-cache-config.php " "and cannot be modified. That file must be writeable by the web server to " "make any changes." msgstr "" #: wp-cache.php:282 msgid "" "A simple way of doing that is by changing the permissions temporarily using " "the CHMOD command or through your ftp client. Make sure it’s globally " "writeable and it should be fine." msgstr "" #: wp-cache.php:283 wp-cache.php:332 msgid "" "This page explains how to change file permissions." msgstr "" #: wp-cache.php:284 msgid "Writeable:" msgstr "" #: wp-cache.php:285 msgid "Read-only:" msgstr "" #: wp-cache.php:303 msgid "Warning! Garbage collection is not scheduled!" msgstr "" #: wp-cache.php:304 msgid "" "Garbage collection by this plugin clears out expired and old cached pages on " "a regular basis. Use this form to enable it." msgstr "" #: wp-cache.php:309 wp-cache.php:337 wp-cache.php:409 wp-cache.php:2170 msgid "Dismiss" msgstr "" #: wp-cache.php:330 msgid "Warning! %s is writeable!" msgstr "" #: wp-cache.php:331 msgid "" "You should change the permissions on %s and make it more restrictive. Use " "your ftp client, or the following command to fix things:" msgstr "" #: wp-cache.php:349 msgid "Mobile rewrite rules detected" msgstr "" #: wp-cache.php:350 msgid "" "For best performance you should enable \"Mobile device support\" or delete " "the mobile rewrite rules in your .htaccess. Look for the 2 lines with the " "text \"2.0\\ MMP|240x320\" and delete those." msgstr "" #: wp-cache.php:350 msgid "" "This will have no affect on ordinary users but mobile users will see " "uncached pages." msgstr "" #: wp-cache.php:356 wp-cache.php:367 msgid "Rewrite rules must be updated" msgstr "" #: wp-cache.php:357 wp-cache.php:368 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "" #: wp-cache.php:358 msgid "" "Mobile support requires extra rules in your .htaccess file, or you can set " "the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "" #: wp-cache.php:359 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "" #: wp-cache.php:360 wp-cache.php:369 msgid "" "Scroll down the Advanced Settings page and click the Update " "Mod_Rewrite Rules button." msgstr "" #: wp-cache.php:361 msgid "" "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN " "WPSuperCache and # END WPSuperCache and let the plugin " "regenerate them by reloading this page." msgstr "" #: wp-cache.php:362 msgid "" "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed " "by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line " "%%{HTTP:Cookie} !^.*(comment_author_|%s|wp-postpass_).*$ add " "these lines: (do it twice, once for each section)" msgstr "" #: wp-cache.php:375 msgid "Required to serve compressed supercache files properly." msgstr "" #: wp-cache.php:375 msgid "" "Required to set caching information on supercache pages. IE7 users will see " "old pages without this module." msgstr "" #: wp-cache.php:375 msgid "" "Set the expiry date on supercached pages. Visitors may not see new pages " "when they refresh or leave comments without this module." msgstr "" #: wp-cache.php:382 msgid "Missing Apache Modules" msgstr "" #: wp-cache.php:383 msgid "" "The following Apache modules are missing. The plugin will work in legacy " "mode without them. In full Supercache mode, your visitors may see corrupted " "pages or out of date content however." msgstr "" #: wp-cache.php:403 msgid ".htaccess file may need to be moved" msgstr "" #: wp-cache.php:404 msgid "" "It appears you have WordPress installed in a sub directory as described here. Unfortunately, WordPress writes to the .htaccess in the install " "directory, not where your site is served from.
    When you update the " "rewrite rules in this plugin you will have to copy the file to where your " "site is hosted. This will be fixed in the future." msgstr "" #: wp-cache.php:665 msgid "" "Warning! You attempted to enable compression but zlib." "output_compression is enabled. See #21 in the Troubleshooting section " "of the readme file." msgstr "" #: wp-cache.php:764 msgid "WP Super Cache Settings" msgstr "" #: wp-cache.php:778 msgid "" "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced " "Settings Page by default." msgstr "" #: wp-cache.php:789 msgid "" "Configuration file changed, some values might be wrong. Load the page again " "from the \"Settings\" menu to reset them." msgstr "" #: wp-cache.php:821 msgid "Caching must be enabled to use this feature" msgstr "" #: wp-cache.php:839 wp-cache.php:979 msgid "Cancel Cache Preload" msgstr "" #: wp-cache.php:847 msgid "" "Scheduled preloading of cache almost cancelled. It may take up to a minute " "for it to cancel completely." msgstr "" #: wp-cache.php:858 msgid "Scheduled preloading of cache cancelled." msgstr "" #: wp-cache.php:890 wp-cache.php:977 msgid "Preload Cache Now" msgstr "" #: wp-cache.php:894 msgid "Scheduled preloading of cache in 10 seconds." msgstr "" #: wp-cache.php:899 msgid "Scheduled preloading of cache in %d minutes" msgstr "" #: wp-cache.php:903 msgid "" "This will cache every published post and page on your site. It will create " "supercache static files so unknown visitors (including bots) will hit a " "cached page. This will probably help your Google ranking as they are using " "speed as a metric when judging websites now." msgstr "" #: wp-cache.php:904 msgid "" "Preloading creates lots of files however. Caching is done from the newest " "post to the oldest so please consider only caching the newest if you have " "lots (10,000+) of posts. This is especially important on shared hosting." msgstr "" #: wp-cache.php:905 msgid "" "In ’Preload Mode’ regular garbage collection will only clean out " "old legacy files for known users, not the preloaded supercache files. This " "is a recommended setting when the cache is preloaded." msgstr "" #: wp-cache.php:909 msgid "" "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d " "minutes.)" msgstr "" #: wp-cache.php:922 msgid "all" msgstr "" #: wp-cache.php:935 msgid "Preload %s posts." msgstr "" #: wp-cache.php:942 msgid "" "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "" #: wp-cache.php:945 msgid "Preload tags, categories and other taxonomies." msgstr "" #: wp-cache.php:948 msgid "Send me status emails when files are refreshed." msgstr "" #: wp-cache.php:953 msgid "Many emails, 2 emails per 100 posts." msgstr "" #: wp-cache.php:956 msgid "Medium, 1 email per 100 posts." msgstr "" #: wp-cache.php:959 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "" #: wp-cache.php:963 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "" #: wp-cache.php:964 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "" #: wp-cache.php:970 msgid "Currently caching from post %d to %d." msgstr "" #: wp-cache.php:974 msgid "Page last cached: %s" msgstr "" #: wp-cache.php:977 msgid "Update Settings" msgstr "" #: wp-cache.php:985 msgid "" "Preloading of cache disabled. Please disable legacy page caching or talk to " "your host administrator." msgstr "" #: wp-cache.php:1002 wp-cache.php:1147 msgid "Caching" msgstr "" #: wp-cache.php:1006 wp-cache.php:1150 msgid "Caching On" msgstr "" #: wp-cache.php:1006 wp-cache.php:1009 wp-cache.php:1025 wp-cache.php:1030 #: wp-cache.php:1031 wp-cache.php:1038 wp-cache.php:1065 wp-cache.php:1150 msgid "Recommended" msgstr "" #: wp-cache.php:1007 wp-cache.php:1151 msgid "Caching Off" msgstr "" #: wp-cache.php:1008 msgid "Use mod_rewrite to serve cache files." msgstr "" #: wp-cache.php:1009 msgid "Use PHP to serve cache files." msgstr "" #: wp-cache.php:1010 msgid "Legacy page caching." msgstr "" #: wp-cache.php:1011 msgid "" "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, " "while legacy caching is slower again, but more flexible and also easy to get " "working. New users should use PHP caching." msgstr "" #: wp-cache.php:1017 msgid "Miscellaneous" msgstr "" #: wp-cache.php:1023 msgid "Warning! Compression is disabled as gzencode() function was not found." msgstr "" #: wp-cache.php:1025 msgid "Compress pages so they’re served more quickly to visitors." msgstr "" #: wp-cache.php:1026 msgid "" "Compression is disabled by default because some hosts have problems with " "compressed files. Switching it on and off clears the cache." msgstr "" #: wp-cache.php:1030 msgid "" "Don’t cache pages for known users." msgstr "" #: wp-cache.php:1031 msgid "" "Cache rebuild. Serve a supercache file to anonymous users while a new file " "is being generated." msgstr "" #: wp-cache.php:1038 msgid "" "304 Not Modified browser caching. Indicate when a page has not been modified " "since it was last requested." msgstr "" #: wp-cache.php:1041 msgid "" "Warning! 304 browser caching is only supported when mod_rewrite caching is " "not used." msgstr "" #: wp-cache.php:1043 msgid "" "304 support is disabled by default because some hosts have had problems with " "the headers used in the past." msgstr "" #: wp-cache.php:1046 msgid "Don’t cache pages with GET parameters. (?x=y at the end of a url)" msgstr "" #: wp-cache.php:1047 msgid "" "Make known users anonymous so they’re served supercached static files." msgstr "" #: wp-cache.php:1048 msgid "" "Proudly tell the world your server is     Stephen Fry proof! " "(places a message in your blog’s footer)" msgstr "" #: wp-cache.php:1054 wp-cache.php:1351 wp-cache.php:1987 msgid "Advanced" msgstr "" #: wp-cache.php:1058 msgid "" "Enable dynamic caching. Requires PHP or legacy caching. (See FAQ or wp-super-" "cache/plugins/dynamic-cache-test.php for example code.)" msgstr "" #: wp-cache.php:1059 msgid "" "Mobile device support. (External plugin or theme required. See the FAQ for further " "details.)" msgstr "" #: wp-cache.php:1061 msgid "Mobile Browsers" msgstr "" #: wp-cache.php:1061 msgid "Mobile Prefixes" msgstr "" #: wp-cache.php:1063 msgid "" "Remove UTF8/blog charset support from .htaccess file. Only necessary if you " "see odd characters or punctuation looks incorrect. Requires rewrite rules " "update." msgstr "" #: wp-cache.php:1064 msgid "Clear all cache files when a post or page is published or updated." msgstr "" #: wp-cache.php:1065 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "" #: wp-cache.php:1066 msgid "Only refresh current page when comments made." msgstr "" #: wp-cache.php:1067 msgid "List the newest cached pages on this page." msgstr "" #: wp-cache.php:1069 msgid "" "Coarse file locking. You do not need this as it will slow down your website." msgstr "" #: wp-cache.php:1071 msgid "" "Late init. Display cached files after WordPress has loaded. Most useful in " "legacy mode." msgstr "" #: wp-cache.php:1073 msgid "Use object cache to store cached files." msgstr "" #: wp-cache.php:1073 msgid "(Experimental)" msgstr "" #: wp-cache.php:1075 msgid "DO NOT CACHE PAGE secret key: %s" msgstr "" #: wp-cache.php:1080 msgid "Cache Location" msgstr "" #: wp-cache.php:1085 msgid "" "Change the location of your cache files. The default is WP_CONTENT_DIR . /" "cache/ which translates to %s." msgstr "" #: wp-cache.php:1086 msgid "You must give the full path to the directory." msgstr "" #: wp-cache.php:1087 msgid "" "If the directory does not exist, it will be created. Please make sure your " "web server user has write access to the parent directory. The parent " "directory must exist." msgstr "" #: wp-cache.php:1088 msgid "" "If the new cache directory does not exist, it will be created and the " "contents of the old cache directory will be moved there. Otherwise, the old " "cache directory will be left where it is." msgstr "" #: wp-cache.php:1089 msgid "" "Submit a blank entry to set it to the default directory, WP_CONTENT_DIR . /" "cache/." msgstr "" #: wp-cache.php:1091 msgid "" "The plugin detected a bare directory index in your cache directory, which " "would let visitors see your cache files directly and might expose private " "posts." msgstr "" #: wp-cache.php:1093 msgid "" "You are using mod_rewrite to serve cache files so the plugin has added " "Options -Indexes to the .htaccess file in the cache directory to " "disable indexes. However, if that does not work, you should contact your " "system administrator or support and ask for them to be disabled, or use PHP " "mode and move the cache outside of the web root." msgstr "" #: wp-cache.php:1095 msgid "" "index.html files have been added in key directories, but unless directory " "indexes are disabled, it is probably better to store the cache files outside " "of the web root of %s" msgstr "" #: wp-cache.php:1102 msgid "" "Since you are using mod_rewrite to serve cache files, you must choose a " "directory in your web root which is %s and update the mod_rewrite " "rules in the .htaccess file." msgstr "" #: wp-cache.php:1110 msgid "Note:" msgstr "" #: wp-cache.php:1112 msgid "" "Uninstall this plugin on the plugins page. It will automatically clean up " "after itself. If manual intervention is required, then simple instructions " "are provided." msgstr "" #: wp-cache.php:1113 msgid "" "If uninstalling this plugin, make sure the directory %s is " "writeable by the webserver so the files advanced-cache.php and " "cache-config.php can be deleted automatically. (Making sure those " "files are writeable is probably a good idea!)" msgstr "" #: wp-cache.php:1114 msgid "" "Please see the readme.txt for " "instructions on uninstalling this script. Look for the heading, \"How to " "uninstall WP Super Cache\"." msgstr "" #: wp-cache.php:1115 msgid "" "Need help? Check the Super Cache readme file. It " "includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already " "have been answered." msgstr "" #: wp-cache.php:1118 wp-cache.php:1163 msgid "Update Status" msgstr "" #: wp-cache.php:1125 msgid "Accepted Filenames & Rejected URIs" msgstr "" #: wp-cache.php:1160 msgid "" "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. " "Cached files will be served using those rules. If your site is working ok, " "please ignore this message. Otherwise, you can edit the .htaccess file in " "the root of your install and remove the SuperCache rules." msgstr "" #: wp-cache.php:1165 msgid "Cache Tester" msgstr "" #: wp-cache.php:1166 msgid "Test your cached website by clicking the test button below." msgstr "" #: wp-cache.php:1172 msgid "Fetching %s to prime cache: " msgstr "" #: wp-cache.php:1174 wp-cache.php:1183 wp-cache.php:1195 msgid "OK" msgstr "" #: wp-cache.php:1177 msgid "Fetching first copy of %s: " msgstr "" #: wp-cache.php:1186 wp-cache.php:1197 msgid "FAILED" msgstr "" #: wp-cache.php:1189 msgid "Fetching second copy of %s: " msgstr "" #: wp-cache.php:1201 msgid "One or more page requests failed:" msgstr "" #: wp-cache.php:1220 wp-cache.php:1221 msgid "Page %d: %d (%s)" msgstr "" #: wp-cache.php:1227 msgid "Page 1: %s" msgstr "" #: wp-cache.php:1228 msgid "Page 2: %s" msgstr "" #: wp-cache.php:1229 msgid "The timestamps on both pages match!" msgstr "" #: wp-cache.php:1231 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "" #: wp-cache.php:1232 msgid "Things you can do:" msgstr "" #: wp-cache.php:1233 msgid "" "Load your homepage in a logged out browser, check the timestamp at the end " "of the html source. Load the page again and compare the timestamp. Caching " "is working if the timestamps match." msgstr "" #: wp-cache.php:1234 msgid "" "Enable logging on the Debug page here. That should help you track down the " "problem." msgstr "" #: wp-cache.php:1235 msgid "" "You should check Page 1 and Page 2 above for errors. Your local server " "configuration may not allow your website to access itself." msgstr "" #: wp-cache.php:1243 msgid "Send non-secure (non https) request for homepage" msgstr "" #: wp-cache.php:1244 msgid "Test Cache" msgstr "" #: wp-cache.php:1248 msgid "Delete Cached Pages" msgstr "" #: wp-cache.php:1249 msgid "" "Cached pages are stored on your server as html and PHP files. If you need to " "delete them, use the button below." msgstr "" #: wp-cache.php:1252 wp-cache.php:2693 wp-cache.php:2712 wp-cache.php:2903 #: wp-cache.php:3442 msgid "Delete Cache" msgstr "" #: wp-cache.php:1259 wp-cache.php:2699 msgid "Delete Cache On All Blogs" msgstr "" #: wp-cache.php:1264 msgid "Recommended Links and Plugins" msgstr "" #: wp-cache.php:1265 msgid "" "Caching is only one part of making a website faster. Here are some other " "plugins that will help:" msgstr "" #: wp-cache.php:1266 msgid "" "Yahoo! Yslow is an extension for the Firefox add-on " "Firebug. It analyzes web pages and suggests ways to improve their " "performance based on a set of rules for high performance web pages. Also try " "the performance tools online at GTMetrix." msgstr "" #: wp-cache.php:1267 msgid "" "Use Google Libraries allows you to load some commonly " "used Javascript libraries from Google webservers. Ironically, it may reduce " "your Yslow score." msgstr "" #: wp-cache.php:1268 msgid "" "Advanced users only: Install an object cache. Choose from " "Memcached, XCache, eAcccelerator and others." msgstr "" #: wp-cache.php:1269 msgid "" "Cron View is a useful plugin to use when trying to debug " "garbage collection and preload problems." msgstr "" #: wp-cache.php:1280 msgid "Need Help?" msgstr "" #: wp-cache.php:1282 msgid "" "Use the debug system in the Debug tab above. It will tell you what the " "plugin is doing." msgstr "" #: wp-cache.php:1283 msgid "Installation Help" msgstr "" #: wp-cache.php:1284 msgid "Frequently Asked Questions" msgstr "" #: wp-cache.php:1285 msgid "Support Forum" msgstr "" #: wp-cache.php:1286 msgid "Development Version" msgstr "" #: wp-cache.php:1288 msgid "Rate This Plugin!" msgstr "" #: wp-cache.php:1289 msgid "" "Please rate this plugin and tell me if it works for you " "or not. It really helps development." msgstr "" #: wp-cache.php:1298 msgid "Cached pages since %1$s : %2$s" msgstr "" #: wp-cache.php:1299 msgid "Newest Cached Pages:" msgstr "" #: wp-cache.php:1303 msgid "Cached %s seconds ago" msgstr "" #: wp-cache.php:1306 msgid "(may not always be accurate on busy sites)" msgstr "" #: wp-cache.php:1322 msgid "" "Cache plugins are PHP scripts that live in a plugins folder inside the wp-" "super-cache folder. They are loaded when Supercache loads, much sooner than " "regular WordPress plugins." msgstr "" #: wp-cache.php:1323 msgid "" "This is strictly an advanced feature only and knowledge of both PHP and " "WordPress actions is required to create them." msgstr "" #: wp-cache.php:1324 msgid "" "Warning! Due to the way WordPress upgrades plugins, the " "plugins you upload to wp-super-cache/plugins/ will be deleted when you " "upgrade WP Super Cache. You can avoid this by loading the plugins from " "elsewhere. Set $wp_cache_plugins_dir to the new location in " "wp-config.php and WP Super Cache will look there instead.
    More info " "available in the developer documentation." msgstr "" #: wp-cache.php:1334 msgid "Available Plugins" msgstr "" #: wp-cache.php:1351 msgid "Easy" msgstr "" #: wp-cache.php:1351 msgid "CDN" msgstr "" #: wp-cache.php:1351 msgid "Contents" msgstr "" #: wp-cache.php:1351 msgid "Preload" msgstr "" #: wp-cache.php:1351 msgid "Plugins" msgstr "" #: wp-cache.php:1351 msgid "Debug" msgstr "" #: wp-cache.php:1389 msgid "" "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "" #: wp-cache.php:1398 msgid "Mod Rewrite Rules" msgstr "" #: wp-cache.php:1404 msgid "WordPress MU Detected" msgstr "" #: wp-cache.php:1404 msgid "" "Unfortunately, the rewrite rules cannot be updated automatically when " "running WordPress MU. Please open your .htaccess and add the following " "mod_rewrite rules above any other rules in that file." msgstr "" #: wp-cache.php:1406 msgid "Mod Rewrite rules cannot be updated!" msgstr "" #: wp-cache.php:1407 msgid "" "You must have BEGIN and END markers in %s." "htaccess for the auto update to work. They look like this and surround the " "main WordPress mod_rewrite rules:" msgstr "" #: wp-cache.php:1409 msgid "Refresh this page when you have updated your .htaccess file." msgstr "" #: wp-cache.php:1413 msgid "Thank you for upgrading." msgstr "" #: wp-cache.php:1413 msgid "" "The mod_rewrite rules changed since you last installed this plugin. " "Unfortunately, you must remove the old supercache rules before the new ones " "are updated. Refresh this page when you have edited your .htaccess file. If " "you wish to manually upgrade, change the following line: %1$s so it looks " "like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" " "and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change " "but it’s backwards compatible with older versions if you’re " "brave enough to use them." msgstr "" #: wp-cache.php:1417 msgid "Trailing slash check required." msgstr "" #: wp-cache.php:1417 msgid "" "It looks like your blog has URLs that end with a \"/\". Unfortunately since " "you installed this plugin a duplicate content bug has been found where URLs " "not ending in a \"/\" end serve the same content as those with the \"/\" and " "do not redirect to the proper URL. To fix, you must edit your .htaccess file " "and add these two rules to the two groups of Super Cache rules:" msgstr "" #: wp-cache.php:1419 msgid "" "You can see where the rules go and examine the complete rules by clicking " "the \"View mod_rewrite rules\" link below." msgstr "" #: wp-cache.php:1433 msgid "Mod Rewrite rules updated!" msgstr "" #: wp-cache.php:1434 msgid "" "%s.htaccess has been updated with the necessary mod_rewrite rules. Please " "verify they are correct. They should look like this:" msgstr "" #: wp-cache.php:1436 msgid "Mod Rewrite rules must be updated!" msgstr "" #: wp-cache.php:1437 msgid "" "Your %s.htaccess is not writable by the webserver and must be updated with " "the necessary mod_rewrite rules. The new rules go above the regular " "WordPress rules as shown in the code below:" msgstr "" #: wp-cache.php:1442 msgid "" "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have " "upgraded the plugin, make sure these rules match." msgstr "" #: wp-cache.php:1445 msgid "" "A difference between the rules in your .htaccess file and the plugin rewrite " "rules has been found. This could be simple whitespace differences, but you " "should compare the rules in the file with those below as soon as possible. " "Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "" #: wp-cache.php:1447 msgid "View Mod_Rewrite Rules" msgstr "" #: wp-cache.php:1453 wp-cache.php:3021 msgid "Rules must be added to %s too:" msgstr "" #: wp-cache.php:1459 msgid "Gzip encoding rules in %s.htaccess created." msgstr "" #: wp-cache.php:1465 msgid "Fix Configuration" msgstr "" #: wp-cache.php:1468 msgid "Restore Default Configuration" msgstr "" #: wp-cache.php:1476 msgid "" "Comment moderation is enabled. Your comment may take some time to appear." msgstr "" #: wp-cache.php:1501 msgid "Lock Down:" msgstr "" #: wp-cache.php:1502 msgid "" "Prepare your server for an expected spike in traffic by enabling the lock " "down. When this is enabled, new comments on a post will not refresh the " "cached static files." msgstr "" #: wp-cache.php:1503 msgid "" "Developers: Make your plugin lock down compatible by checking the " "\"WPLOCKDOWN\" constant. The following code will make sure your plugin " "respects the WPLOCKDOWN setting." msgstr "" #: wp-cache.php:1505 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "" #: wp-cache.php:1509 msgid "" "WordPress is locked down. Super Cache static files will not be deleted when " "new comments are made." msgstr "" #: wp-cache.php:1511 msgid "" "WordPress is not locked down. New comments will refresh Super Cache static " "files as normal." msgstr "" #: wp-cache.php:1517 msgid "Lock Down" msgstr "" #: wp-cache.php:1525 msgid "Directly Cached Files" msgstr "" #: wp-cache.php:1577 msgid "Cannot delete directory" msgstr "" #: wp-cache.php:1586 msgid "%s removed!" msgstr "" #: wp-cache.php:1594 msgid "" "You must make %s writable to enable this feature. As this is a security " "risk, please make it read-only after your page is generated." msgstr "" #: wp-cache.php:1599 msgid "" "%s is writable. Please make it readonly after your page is generated as this " "is a security risk." msgstr "" #: wp-cache.php:1614 msgid "Existing direct page" msgstr "" #: wp-cache.php:1614 msgid "Delete cached file" msgstr "" #: wp-cache.php:1619 msgid "Add direct page:" msgstr "" #: wp-cache.php:1621 msgid "" "Directly cached files are files created directly off %s where your blog " "lives. This feature is only useful if you are expecting a major Digg or " "Slashdot level of traffic to one post or page." msgstr "" #: wp-cache.php:1623 msgid "" "For example: to cache %1$sabout/, you would enter %1$sabout/ or /" "about/. The cached file will be generated the next time an anonymous user " "visits that page." msgstr "" #: wp-cache.php:1624 msgid "" "Make the textbox blank to remove it from the list of direct pages and delete " "the cached file." msgstr "" #: wp-cache.php:1629 msgid "Update Direct Pages" msgstr "" #: wp-cache.php:1657 msgctxt "timezone date format" msgid "Y-m-d G:i:s" msgstr "" #: wp-cache.php:1729 msgid "Expiry Time & Garbage Collection" msgstr "" #: wp-cache.php:1731 msgid "" "UTC time is %s" msgstr "" #: wp-cache.php:1734 msgid "Local time is %1$s" msgstr "" #: wp-cache.php:1738 msgid "Next scheduled garbage collection will be at %s UTC" msgstr "" #: wp-cache.php:1742 msgid "" "Warning! PRELOAD MODE activated. Supercache files will not " "be deleted regardless of age." msgstr "" #: wp-cache.php:1760 msgid "Cache Timeout" msgstr "" #: wp-cache.php:1761 wp-cache.php:1764 msgid "seconds" msgstr "" #: wp-cache.php:1762 msgid "" "How long should cached pages remain fresh? Set to 0 to disable garbage " "collection. A good starting point is 3600 seconds." msgstr "" #: wp-cache.php:1763 msgid "Scheduler" msgstr "" #: wp-cache.php:1763 msgid "Timer:" msgstr "" #: wp-cache.php:1764 msgid "Check for stale cached files every interval seconds." msgstr "" #: wp-cache.php:1765 msgid "Clock:" msgstr "" #: wp-cache.php:1766 msgid "HH:MM" msgstr "" #: wp-cache.php:1766 msgid "" "Check for stale cached files at this time (UTC) or starting " "at this time every interval below." msgstr "" #: wp-cache.php:1768 msgid "Interval:" msgstr "" #: wp-cache.php:1774 msgid "Notification Emails" msgstr "" #: wp-cache.php:1775 msgid "Email me when the garbage collection runs." msgstr "" #: wp-cache.php:1777 msgid "Garbage Collection" msgstr "" #: wp-cache.php:1778 msgid "" "Garbage collection is the simple act of throwing out your garbage. " "For this plugin that would be old or stale cached files that may be " "out of date. New cached files are described as fresh." msgstr "" #: wp-cache.php:1779 msgid "" "Cached files are fresh for a limited length of time. You can set that time " "in the Cache Timeout text box on this page." msgstr "" #: wp-cache.php:1780 msgid "" "Stale cached files are not removed as soon as they become stale. They have " "to be removed by the garbage collecter. That is why you have to tell the " "plugin when the garbage collector should run." msgstr "" #: wp-cache.php:1781 msgid "" "Use the Timer or Clock schedulers to define when the " "garbage collector should run." msgstr "" #: wp-cache.php:1782 msgid "" "The Timer scheduler tells the plugin to run the garbage collector " "at regular intervals. When one garbage collection is done, the next run is " "scheduled." msgstr "" #: wp-cache.php:1783 msgid "" "Or, the Clock scheduler allows the garbage collection to run at " "specific times. If set to run hourly or twice daily, the garbage collector " "will be first scheduled for the time you enter here. It will then run again " "at the indicated interval. If set to run daily, it will run once a day at " "the time specified." msgstr "" #: wp-cache.php:1785 msgid "" "There are no best garbage collection settings but here are a few scenarios. " "Garbage collection is separate to other actions that clear our cached files " "like leaving a comment or publishing a post." msgstr "" #: wp-cache.php:1787 msgid "" "Sites that want to serve lots of newly generated data should set the " "Cache Timeout to 60 and use the Timer scheduler set to 90 " "seconds." msgstr "" #: wp-cache.php:1788 msgid "" "Sites with widgets and rss feeds in their sidebar should probably use a " "timeout of 3600 seconds and set the timer to 600 seconds. Stale files will " "be caught within 10 minutes of going stale." msgstr "" #: wp-cache.php:1789 msgid "" "Sites with lots of static content, no widgets or rss feeds in their sidebar " "can use a timeout of 86400 seconds or even more and set the timer to " "something equally long." msgstr "" #: wp-cache.php:1790 msgid "" "Sites where an external data source updates at a particular time every day " "should set the timeout to 86400 seconds and use the Clock scheduler set " "appropriately." msgstr "" #: wp-cache.php:1792 msgid "" "Checking for and deleting expired files is expensive, but it’s " "expensive leaving them there too. On a very busy site, you should set the " "expiry time to 600 seconds. Experiment with different values and " "visit this page to see how many expired files remain at different times " "during the day. If you are using legacy caching, aim to have less than 500 " "cached files if possible. You can have many times more cached files when " "using mod_rewrite or PHP caching." msgstr "" #: wp-cache.php:1793 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "" #: wp-cache.php:1794 msgid "Change Expiration" msgstr "" #: wp-cache.php:1838 msgid "Rejected User Agents" msgstr "" #: wp-cache.php:1839 msgid "" "Strings in the HTTP ’User Agent’ header that prevent WP-Cache " "from caching bot, spiders, and crawlers’ requests. Note that super " "cached files are still sent to these agents if they already exists." msgstr "" #: wp-cache.php:1846 msgid "Save UA Strings" msgstr "" #: wp-cache.php:1869 msgid "" "Do not cache the following page types. See the Conditional Tags documentation for a " "complete discussion on each type." msgstr "" #: wp-cache.php:1872 msgid "Single Posts" msgstr "" #: wp-cache.php:1873 msgid "Pages" msgstr "" #: wp-cache.php:1874 msgid "Front Page" msgstr "" #: wp-cache.php:1875 msgid "Home" msgstr "" #: wp-cache.php:1876 msgid "Archives" msgstr "" #: wp-cache.php:1877 msgid "Tags" msgstr "" #: wp-cache.php:1878 msgid "Category" msgstr "" #: wp-cache.php:1879 msgid "Feeds" msgstr "" #: wp-cache.php:1880 msgid "Search Pages" msgstr "" #: wp-cache.php:1881 msgid "Author Pages" msgstr "" #: wp-cache.php:1883 wp-cache.php:1997 msgid "Save" msgstr "" #: wp-cache.php:1900 msgid "" "Add here strings (not a filename) that forces a page not to be cached. For " "example, if your URLs include year and you dont want to cache last year " "posts, it’s enough to specify the year, i.e. ’/2004/’. WP-" "Cache will search if that string is part of the URI and if so, it will not " "cache that page." msgstr "" #: wp-cache.php:1906 msgid "Save Strings" msgstr "" #: wp-cache.php:1922 msgid "" "Add here those filenames that can be cached, even if they match one of the " "rejected substring specified above." msgstr "" #: wp-cache.php:1928 msgid "Save Files" msgstr "" #: wp-cache.php:1971 msgid "Currently logging to: %s" msgstr "" #: wp-cache.php:1974 msgid "" "Fix problems with the plugin by debugging it here. It can log them to a file " "in your cache directory." msgstr "" #: wp-cache.php:1978 msgid "Debugging" msgstr "" #: wp-cache.php:1979 msgid "IP Address" msgstr "" #: wp-cache.php:1979 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "" #: wp-cache.php:1980 msgid "Cache Status Messages" msgstr "" #: wp-cache.php:1981 msgid "Display comments at the end of every page like this:" msgstr "" #: wp-cache.php:1987 msgid "" "In very rare cases two problems may arise on some blogs:
    1. The front " "page may start downloading as a zip file.
    2. The wrong page is " "occasionally cached as the front page if your blog uses a static front page " "and the permalink structure is /%category%/%postname%/.
    " msgstr "" #: wp-cache.php:1988 msgid "" "I’m 99% certain that they aren’t bugs in WP Super Cache and they " "only happen in very rare cases but you can run a simple check once every 5 " "minutes to verify that your site is ok if you’re worried. You will be " "emailed if there is a problem." msgstr "" #: wp-cache.php:1990 msgid "Check front page every 5 minutes." msgstr "" #: wp-cache.php:1991 msgid "Front page text" msgstr "" #: wp-cache.php:1991 msgid "" "Text to search for on your front page. If this text is missing, the cache " "will be cleared. Leave blank to disable." msgstr "" #: wp-cache.php:1992 msgid "Clear cache on error." msgstr "" #: wp-cache.php:1993 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "" #: wp-cache.php:2007 msgid "" "Error: GZIP compression is enabled. Disable it if you want to enable wp-" "cache." msgstr "" #: wp-cache.php:2057 wp-cache.php:2356 wp-cache.php:2392 msgid "Warning" msgstr "" #: wp-cache.php:2057 msgid "" "GZIP compression is enabled in WordPress, wp-cache will be bypassed until " "you disable gzip compression." msgstr "" #: wp-cache.php:2154 wp-cache.php:2160 msgid "WP Super Cache Warning!" msgstr "" #: wp-cache.php:2155 msgid "" "All users of this site have been logged out to refresh their login cookies." msgstr "" #: wp-cache.php:2161 msgid "" "Your server is configured to show files and directories, which may expose " "sensitive data such as login cookies to attackers in the cache directories. " "That has been fixed by adding a file named index.html to each directory. If " "you use PHP or legacy caching, consider moving the location of the cache " "directory on the Advanced Settings page." msgstr "" #: wp-cache.php:2163 msgid "" "If you just installed WP Super Cache for the first time, you can dismiss " "this message. Otherwise, you should probably refresh the login cookies of " "all logged in WordPress users here by clicking the logout link below." msgstr "" #: wp-cache.php:2166 msgid "" "Your site is using a very old version of WordPress. When you update to the " "latest version everyone will be logged out and cookie information updated." msgstr "" #: wp-cache.php:2168 msgid "" "The logout link will log out all WordPress users on this site except you. " "Your authentication cookie will be updated, but you will not be logged out." msgstr "" #: wp-cache.php:2172 msgid "Logout" msgstr "" #: wp-cache.php:2276 wp-cache.php:2281 wp-cache.php:2315 wp-cache.php:2320 #: wp-cache.php:2326 msgid "Error" msgstr "" #: wp-cache.php:2276 msgid "" "Your cache directory (%1$s) did not exist and couldn’" "t be created by the web server. Check %1$s permissions." msgstr "" #: wp-cache.php:2281 msgid "" "Your cache directory (%1$s) or %2$s need " "to be writable for this plugin to work. Double-check it." msgstr "" #: wp-cache.php:2315 msgid "" "Your WP-Cache config file (%s) is out of date and not " "writable by the Web server. Please delete it and refresh this page." msgstr "" #: wp-cache.php:2320 msgid "" "Configuration file missing and %1$s directory (%2$s) is " "not writable by the web server. Check its permissions." msgstr "" #: wp-cache.php:2326 msgid "" "Sample WP-Cache config file (%s) does not exist. Verify " "your installation." msgstr "" #: wp-cache.php:2356 msgid "Could not update %s! WPCACHEHOME must be set in config file." msgstr "" #: wp-cache.php:2392 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "" #: wp-cache.php:2393 msgid "1. If it already exists, please delete the file first." msgstr "" #: wp-cache.php:2394 msgid "" "2. Make %1$s writable using the chmod command through your ftp or server " "software. (chmod 777 %1$s) and refresh this page. This is only a " "temporary measure and you’ll have to make it read only afterwards " "again. (Change 777 to 755 in the previous command)" msgstr "" #: wp-cache.php:2395 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "" #: wp-cache.php:2396 msgid "" "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "" #: wp-cache.php:2397 msgid "" "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change " "the text CACHEHOME to %2$s
  • 3. Save the file and " "copy it to %3$s and refresh this page.
    • " msgstr "" #: wp-cache.php:2420 msgid "" "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by " "WordPress to load the code that serves cached pages. Unfortunately, it is " "set to false. Please edit your wp-config.php and add or edit the following " "line above the final require_once command:

    define" "('WP_CACHE', true);

    " msgstr "" #: wp-cache.php:2422 msgid "" "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "" #: wp-cache.php:2423 msgid "" "Edit %s and add the following line:
    define" "('WP_CACHE', true);
    Otherwise, WP-Cache will not be " "executed by WordPress core. " msgstr "" #: wp-cache.php:2427 msgid "" "

    WP_CACHE constant added to wp-config.php

    If you continue to see " "this warning message please see point 5 of the Troubleshooting Guide. The WP_CACHE " "line must be moved up." msgstr "" #: wp-cache.php:2455 msgid "Cache Contents" msgstr "" #: wp-cache.php:2458 msgid "Object cache in use. No cache listing available." msgstr "" #: wp-cache.php:2482 msgid "Deleting supercache file: %s
    " msgstr "" #: wp-cache.php:2504 msgid "Deleting wp-cache file: %s
    " msgstr "" #: wp-cache.php:2571 msgid "" "Cache stats are not automatically generated. You must click the link below " "to regenerate the stats on this page." msgstr "" #: wp-cache.php:2572 msgid "Regenerate cache stats" msgstr "" #: wp-cache.php:2574 msgid "Cache stats last generated: %s minutes ago." msgstr "" #: wp-cache.php:2580 msgid "WP-Cache" msgstr "" #: wp-cache.php:2581 wp-cache.php:2596 msgid "%s Cached Pages" msgstr "" #: wp-cache.php:2582 wp-cache.php:2601 msgid "%s Expired Pages" msgstr "" #: wp-cache.php:2595 msgid "WP-Super-Cache" msgstr "" #: wp-cache.php:2605 msgid "Fresh WP-Cached Files" msgstr "" #: wp-cache.php:2606 wp-cache.php:2622 wp-cache.php:2638 wp-cache.php:2654 msgid "URI" msgstr "" #: wp-cache.php:2606 wp-cache.php:2622 msgid "Key" msgstr "" #: wp-cache.php:2606 wp-cache.php:2622 wp-cache.php:2638 wp-cache.php:2654 msgid "Age" msgstr "" #: wp-cache.php:2606 wp-cache.php:2622 wp-cache.php:2638 wp-cache.php:2654 msgid "Delete" msgstr "" #: wp-cache.php:2621 msgid "Stale WP-Cached Files" msgstr "" #: wp-cache.php:2637 msgid "Fresh Super Cached Files" msgstr "" #: wp-cache.php:2653 msgid "Stale Super Cached Files" msgstr "" #: wp-cache.php:2669 msgid "Hide file list" msgstr "" #: wp-cache.php:2671 msgid "Too many cached files, no listing possible." msgstr "" #: wp-cache.php:2673 msgid "List all cached files" msgstr "" #: wp-cache.php:2676 msgid "" "Expired files are files older than %s seconds. They are still used by the " "plugin and are deleted periodically." msgstr "" #: wp-cache.php:2687 msgid "Delete Expired" msgstr "" #: wp-cache.php:2712 msgid "Delete Super Cache cached files (opens in new window)" msgstr "" #: wp-cache.php:2879 msgid "%1$s is Stephen Fry proof thanks to caching by %2$s" msgstr "" #: wp-cache.php:2912 msgid "" "WP Super Cache must be configured. Go to the admin page " "to enable and configure the plugin." msgstr "" #: wp-cache.php:2918 msgid "Settings" msgstr "" #: wp-cache.php:2928 msgid "" "WP Super Cache is disabled. Please go to the plugin admin " "page to enable caching." msgstr "" #: wp-cache.php:2931 msgid "" "Warning! WP Super Cache caching was broken but has been " "fixed! The script advanced-cache.php could not load wp-" "cache-phase1.php.

    The file %1$s/advanced-cache.php has been " "recreated and WPCACHEHOME fixed in your wp-config.php. Reload to hide this " "message." msgstr "" #: wp-cache.php:2952 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "" #: wp-cache.php:2952 msgid "" "Please visit %s to clear the cache as the front page of your site is now " "downloading!" msgstr "" #: wp-cache.php:2955 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "" #: wp-cache.php:2955 msgid "" "The cache on your blog has been cleared because the front page of your site " "is now downloading. Please visit %s to verify the cache has been cleared." msgstr "" #: wp-cache.php:2962 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "" #: wp-cache.php:2962 msgid "" "Please visit %1$s to clear the cache as the front page of your site is not " "correct and missing the text, \"%2$s\"!" msgstr "" #: wp-cache.php:2965 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "" #: wp-cache.php:2965 msgid "" "The cache on your blog has been cleared because the front page of your site " "is missing the text \"%2$s\". Please visit %1$s to verify the cache has been " "cleared." msgstr "" #: wp-cache.php:2970 msgid "[%s] Front page check!" msgstr "" #: wp-cache.php:2970 msgid "" "WP Super Cache has checked the front page of your blog. Please visit %s if " "you would like to disable this." msgstr "" #: wp-cache.php:3013 msgid "Cannot update .htaccess" msgstr "" #: wp-cache.php:3013 msgid "" "The file %s.htaccess cannot be modified by the web server. " "Please correct this using the chmod command or your ftp client." msgstr "" #: wp-cache.php:3013 msgid "Refresh this page when the file permissions have been modified." msgstr "" #: wp-cache.php:3013 msgid "" "Alternatively, you can edit your %s.htaccess file manually and " "add the following code (before any WordPress rules):" msgstr "" #: wp-cache.php:3017 msgid "" "To serve static html files your server must have the correct mod_rewrite " "rules added to a file called %s.htaccess" msgstr "" #: wp-cache.php:3018 msgid "You can edit the file yourself. Add the following rules." msgstr "" #: wp-cache.php:3019 msgid " Make sure they appear before any existing WordPress rules. " msgstr "" #: wp-cache.php:3027 msgid "Update Mod_Rewrite Rules" msgstr "" #: wp-cache.php:3190 msgid "[%1$s] Cache Preload Started" msgstr "" #: wp-cache.php:3220 msgid "[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d" msgstr "" #: wp-cache.php:3269 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "" #: wp-cache.php:3290 msgid "[%1$s] Cache Preload Stopped" msgstr "" #: wp-cache.php:3300 msgid "[%1$s] %2$d posts refreshed" msgstr "" #: wp-cache.php:3300 msgid "Refreshed the following posts:" msgstr "" #: wp-cache.php:3310 msgid "Scheduling next preload refresh in %d minutes." msgstr "" #: wp-cache.php:3321 msgid "[%s] Cache Preload Completed" msgstr "" #: wp-cache.php:3321 msgid "Cleaning up old supercache files." msgstr "" #: wp-cache.php:3363 msgid "[%s] Preload may have stalled." msgstr "" #: wp-cache.php:3363 msgid "" "Preload has been restarted.\n" "%s" msgstr "" #: wp-cache.php:3406 msgid "Supercache Uninstall Problems" msgstr "" #: wp-cache.php:3406 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file " "first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/plugins/wp-super-cache/" msgstr "" #: wp-cache.php:3443 msgid "Delete cache of the current page" msgstr "" #. Plugin Name of the plugin/theme msgid "WP Super Cache" msgstr "" #. Plugin URI of the plugin/theme msgid "https://wordpress.org/plugins/wp-super-cache/" msgstr "" #. Description of the plugin/theme msgid "Very fast caching plugin for WordPress." msgstr "" #. Author of the plugin/theme msgid "Automattic" msgstr "" #. Author URI of the plugin/theme msgid "https://automattic.com/" msgstr "" languages/wp-super-cache-uk.mo000066600000163030152133035240012314 0ustar00=<,.M[jz` ~?w3*7Z5K =[)wZU&i:ncK  =!3F!z!! !!"/"3" ###,#!>#c`#k$0%F%I%?&@&s'{''( !(+( 2(?(5N(((3W)1))e*{*:+B+K+,+(,H,,?,?-F-N-NT-- -n-$4.Y._.~q../00 00g011+D1p1hx11111 233bG44&56k7b9f9W|9 9 9 9 9b:c:]y:::;#;;$;";<!/<Q<&f<<<<U<<T<K=Uk=p=U2>>`/?0? ???< @H@7]@j@AAY=AA A AA AA9SBB B:BBB CC3C(0D'YDDqDDE$EEkFGGEHT]J~J1KPKTK*LLMMN +N9N!PN rNNNjNb+OOlXPPPPPPQ*(QSQ)WQQbQ[Q VR7aRrRM S8ZSSLT/TUVwW2XXEYeY/ZZ*Z/[.D[3s[[[[[[j]_]Y^G^*,`2W``uaa\dbhb*c]!dXdkddDee_ugugeKh1ijk+lOJm'm8mo[pIs\scs It}Vt7t u u?u8*wEcww+/x[x"nxOxx{.|S|+~~wmm-F3tÂԂ-|0nȃX7C6ԅ: F ^#91%ڌ$&Ս.ގ +GB7,1d;ғ,ǔKݔ')Q ,Ll|ilz֚Q)!9*dAay.>m*L?wZOb:}=,7#3[k 1̫jݫ8Hʭ@ȯ`'l\|.ٱKB3J2}4жxoCIc0PO02Ѻ " 0J EO0c@' huB}K(e))1PRe;/$tO;"S v ?MQmMv&%iuw/"aR6WErI :XToTkr  5)Tup^Jq'`&!ez01Zl- 2QyAC98mb+ nFDr=YxNH@$~gsk]|d:ijo{h,3? _GEK}.B SLV\%6X7c( f/["<ORWvI4w>;aMPU#t* Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%1$s really makes your blog go faster. Make it go faster* by buying me an Amazon gift card! Make it out to "%3$s" for whatever amount you want. Every penny helps!%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php     does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Only half-on caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.phpNo Adverts for Friends plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ add this line: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesBad Behaviour not found. Please check your install.Bad Behaviour support is %sCache ContentsCache PluginsCache rebuild. Serve a supercache file to anonymous users while a new file is being generated. Recommended for very busy websites with lots of comments. Makes "directly cached pages" and "Lockdown mode" obsolete.Cached %s seconds agoCached pages since %1$s : %2$sCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. Aim to have less than 500 cached files if possible.Clear all cache files when a post or page is published. (This may significantly slow down saving of posts.)Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compression is disabled by default because some hosts have problems with compressed files. Switching this on and off clears the cache.Compression is enabled by default when in HALF ON mode.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently logging to: Debug SettingsDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Don’t cache pages for logged in users.Don’t show me this again.Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by Wordpress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "Android|2.0\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textGZIP compression is enabled in Wordpress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.HALF ONHe blogs at %1$s, posts photos at %2$s and wishes he had more time to read and relax.HideHide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf Amazon isn’t your thing, there’s also PayPal. Click the "Donate" button below or take a quick peek at my wishlist.If expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use half-on mode.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyList all cached filesList the newest cached pages (may be expensive to run on busy sites, use with caution.)Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Missing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to half-on mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Newest Cached Pages:Next GC in %s minutesNote:OFFONOk, it won’t go any faster but you’ll make this plugin author very happy!PagesPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Rejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsSearch PagesSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the plugin to half on mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Super Cache CompressionSuper Cache Disabled, only legacy WP-Cache caching.Super Cache compression is now disabled.Super Cache compression is now enabled.TagsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.Thanks in advance!The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in half-on mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessTrailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall using the uninstall script to remove files and directories created by the plugin. (Please see readme.txt for instructions on uninstalling this script.)Update CompressionUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate StatusView Mod_Rewrite RulesWP Cache and Super Cache disabledWP Cache and Super Cache enabledWP Super Cache ManagerWP Super Cache StatusWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWhyWhy your configuration may not be changedWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must edit the file yourself add the following rules.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache!disabledenabledfilesecondsProject-Id-Version: wp-super-cache Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2009-11-13 10:27+0000 PO-Revision-Date: Last-Translator: Vitaly Language-Team: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Ukrainian X-Poedit-Country: UKRAINE X-Poedit-SourceCharset: utf-8 Переконайтеся, що вони розміщені перед будь-яким з існуючих правил Вордпресу.%1$s підтверджено Діггом і закешовано за допомогою %2$s%1$s підтримується та розроблено %2$s за сприянням багатьох інших розробників.%1$s справді робить Ваш сайт швидшим. Зробіть його ще швидшим*, купивши мені вітальну листівку на Амазоні! Зробити її у "%3$s" з будь-якою сумою. Кожна копійка допоможе!%s закешованих сторінок%s протермінованих сторінокПапка %s доступна для запису. Будь ласка, зробіть її доступною для читання після того, як сторінка згенерується, бо це небезпечно.%s видалено!У %s.htaccess було додано необхідні правила mod_rewrite. Будь ласка, перевірте їх правильність. Вони повинні бути подібними на ці:%s/advanced-cache.php не існує або не може бути оновленим.(1 = менше, 5 = більше, може викликати навантаження сервера.) (Підтримується тільки напів-кешування, стиснення ввимкнено та потребує ПОГАНУ ПОВЕДІНКУ у "%s/plugins/bad-behavior/") (може бути не завжди точним на завантажених сайтах)(з цієї IP-адреси лише лог запити. Ваша IP-адреса: %s)(необхідно також friendsadverts.php) 1. Якщо це вже існує, будь ласка, видаліть спочатку файл.2. Зробіть %1$s доступною для запису, використовуючи команди CHMOD або Ваш ftp-клієнт. (chmod 777 %1$s) та оновіть цю сторінку. Це лише тимчасова поправка, і Вам необхідно зробити цю папку доступною для читання вкінці знову. (Змініть 777 на 755 у попередній команді)3. Обновіть цю сторінку, щоб оновити %s/advanced-cache.phpПлаґін Нема посилань для друзів %s

    Константа WP_CACHE додана у файл wp-config.php

    Якщо Ви продовжуєте бачити це попередження, тоді дивіться пункт 5 у FAQ. Стрічка WP_CACHE повинна бути переміщена вгору.

  • 1. Вдкрийте %1$s$wp_cache_file у текстовому редакторі.
  • 2. Змініть текст CACHEHOME на %2$s
  • 3. Збережіть файл і скопіюйте його в %3$s та оновіть цю сторінку.
    • Помилка: WP_CACHE не ввімкнено у Вашому wp-config.php файлі і я не зміг відредагувати його.Збір Сміття
    Останній Збір Сміття був %s хвилин тому
    Щоб це зробити, необхідно тимчасово змінити права доступу, використовуючи команду CHMOD або за допомогою вашого ftp-клієнту. Запевніться у тому, що є доступ для запису.Прийняті імена файлів та відхилені URI-шляхиДодати дану сторінку:Додати стрічки (не і’мя файлу), що примушують сторінки не кешувати. Наприклад, якщо Ваші URL-адреси містять рік і Ви не хочете кешувати останній рік статей, тоді достатньо вказати рік, наприклад ’/2004/’. Вордпрес Кеш перевірить чи ця стрічка є частиною URI-шляху. Якщо так, тоді ця сторінка не буде закешованою.Додайте сюди імена файлів, які можуть бути закешованими, навіть якщо вони відповідають одній з відхилених стрічок, зазначених вище.Додати правила самостійно. Відредагуйте %s.htaccess та знайдіть фрагмент коду, що починається зі стрічки # BEGIN WPSuperCache та закінчується стрічкою # END WPSuperCache. Є два подібні між собою фрагменти коду. Одразу під стрічкою %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ додайте цей код: (зробіть це двічі, тобто для кожного з фрагментів)РозширенеВікКрім того, Ви можете редагувати свій %s.htaccess файл вручну та додати наступний код (перед будь-якими правилами Вордпресу):АрхівиПОГАНУ ПОВЕДІНКУ не знайдено. Будь ласка, перевірте Вашу інсталяцію.Підтримку ПОГАНОЇ ПОВЕДІНКИ %sВміст КешуПлаґіни для КешуОновлення кешу. Видавати супер-кешований файл для анонімних користувачів, поки не згенерується новий файл. Рекомендовано для дуже завантажених сайтів з великою кількістю коментарів. Робить "безпосередньо закешовані сторінки" та "Режим блокування" непотрібними.Закешовано %s секунд тому назадСторінки закешовано з %1$s : %2$sПродовження неможливе... виправте попередні проблеми та спробуйте знову.Неможливо оновити .htaccessКатегоріїЗмінити термін діїПеревіряти головну сторінку кожні 5 хвилин.Перевірка та видалення протермінованих файлів є ресурсоємкою процедурою, але залишати їх там було би неправильно. На дуже завантаженому сайті Ви повинні встановити термін дії на 300 секунд. Поекспериментуйте з різними значеннями та відвідайте цю сторінку, щоб дізнатися, скільки протермінованих файлів залишилося у різний час протягом дня. Прагніть до того, щоб залишилось менше ніж 500 закешованих файлів.Видалити всі закешовані файли, якщо стаття або сторінка оновилась. (Це може значно сповільнити збереження сторінок.)Очистити кеш при помилці.Блокування великих файлів. Вам це напевне не потрібно, але це може допомогти, якщо у Вас не дуже потужний сервер. Увага! Може спричинити блокування Вашого сервера у рідких випадках! Модерацію коментарів ввімкнено. Можливо знадобиться трохи часу, щоб Ваш коментар з’явився.Стиск вимкнено за замовчуванням, тому що деякі хости мають проблеми зі стиснутими файлами. Вмикання та вимикання цього пункту призводить до очищення кешу.У режимі Напів-Кешування стиск ввіммкнено за замовчуванням.Змінено файл налаштувань, деякі змінні можуть бути неправильними. Щоб обнулити їх, завантажте сторінку знову з розділу меню "Налаштування".Конфігураційний файл відсутній та папка %1$s (%2$s) не доступна для запису веб-сервером. Перевірте права доступу.Зараз лог записується у: Налаштування відлагодженняВідлагодженняВидалитиОчистити кешВидалити протермінованеВидалити закешовані файли Супер Кешу (завантажиться у новому вікні)Видалити закешований файлВидалити mod_rewrite правила плаґіну у %s.htaccess, що починається зі стрічки # BEGIN WPSuperCache та закінчується # END WPSuperCache та дозволити плаґіну перегенерувати їх за допомогою перезавантаження сторінки.Видаляється супер-кешований файл: %s
    Видаляється файл wp-cache: %s
    Розробники: Зробіть Ваш плаґін сумісним для блокування, перевіривши константу "WPLOCKDOWN". Наступний код буде переконаний у тому, що Ваш плаґін перевіряє налаштування WPLOCKDOWN.Безпосередньо закешовані файлиБезпосередньо закешовані файли - це файли, створені безпосередньо у %s, де розміщено Ваш сайт. Ця опція корисна лише тоді, якщо Ви очікуєте значного збільшення трафіку з Діггу або Слешдоту на одну зі своїх статей або сторінок.ВимкнутиВимкненоНе кешувати наступні типи сторінок. Відвідайте сторінку документації умовні теги для повного роз’яснення по кожному типу.Не кешувати сторінки для залогованих користувачів.Не показувати мені цього знову.Відредагуйте код %s та додайте наступну стрічку:
    define('WP_CACHE', true);
    В іншому випадку Вордпрес-Кеш не виконається за допомогою ядра Вордпресу.Електронна скринькаНадіслати електронного листа адміністратору сайту, коли перевірку буде завершено. (корисно для тестування)ВвімкнутиВвімкненоПомилкаПомилка: стиск GZIP ввімкнено. Якщо Ви хочете, щоб Вордпрес-Кеш працював, тоді вимкніть це.Дана сторінка існуєЧас протермінування:Протерміновані файли - це файли, що старші за %s секунд. Вони все рівно використовуються плаґіном та видаляються періодично.Термін дії та збір сміттяФідиВиправити налаштуванняВиправіть проблеми з плаґіном, відлагоджуючи його тут. Він може надсилати Вам відгоджувальні листи на електротронну скриньку або зберігати інформацію у лог-файл у каталозі кешу.Для кращої роботи Вам необхідно ввімкнути "Підтримку стільникових пристроїв" або видалити правило mod_rewrite для стільникових пристроїв у файлі .htaccess. Знайдіть дві стрічки з текстом "Android|2.0\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone" та видаліть їх.Наприклад: щоб закешувати %1$sabout/, Вам необхідно ввести %1$sabout/ або /about/. Закешований файл буде створено наступного разу коли анонімний користувач відвідає цю сторінку.Свіжі Супер Кешовані файлиСвіжі Вордпрес-Закешовані файлиГоловна сторінкаТекст головної сторінкиСтиск GZIP ввімкнено у Вордпресі, Вордпрес-Кеш буде пропущено, поки Ви не відключите стиск GZIP.Збір СміттяСтворено правила Gzip декодування у %s.htaccess.Ввімкнено наполовинуВін має блог на %1$s, публікує фото на %2$s та якби він мав більше часу почитати та розслабитись.ПриховатиПриховати список файлівДомашня сторінкаНа 99%c я впевнений, що ці помилки не стосуються плаґіну Вордпрес Супер Кеш і вони трапляються у дуже рідких випадках, але Ви можете провести просту перевірку кожних 5 хвилин, щоб запевнитися, що Ваш сайт функціонує добре. Якщо виникнуть якісь проблеми, Ви отримаєте електронне повідомлення.IP-адресаЯкщо Амазон не для Вас, є також PayPal. Клікніть внизу на кнопку "Пожертвувати" або перегляньте список моїх побажань.Якщо час протермінування більш ніж 1800 секунд (півгодини), тоді збір сміття буде здійснюватися кожні 10 хвилин, в іншому випадку це відбудеться через 10 секунд після закінчення часу, що зазначено вище.Якщо це не працює, переконайтесь, що файл %s/advanced-cache.php не існує:Якщо Ви деінсталюєте цей плаґін, переконайтесь, що папка %s є доступною для запису веб-сервером і файли advanced-cache.php та cache-config.php можуть бути видалені автоматично. (Переконайтесь, що ці файли доступні для запису також!)У дуже рідкісних випадках на деяких сайтах, можуть виникнути дві проблеми:
    1. Головна сторінка може почати завантажуватись як Zip-файл.
    2. Випадково кешується не та сторінка як головна, якщо Ваш сайт використовує наступну структуру постійних посилань /%category%/%postname%/.
    Здається, що mod_rewrite не встановлено. Іноді ця перевірка не є на 100% достовірною, особливо якщо Ви використовуєте не Apache. Будь ласка, переконайтесь у тому, що модуль mod_rewrite завантажено. Це необхідно для видачі статичних файлів Супер Кешу. Ви всерівно будете мати змогу використовувати режим напів-кешування.Схоже на те, що Ваш сайт має URL-адреси, що закінчуються символом "/". На жаль, з того часу, як Ви інсталювали цей плаґін, виникла помилка дублювання вмісту, при якій URL-адреси, що не закінчуються символом "/" видають той самий вміст, що і сторінки з символом "/" у кінці та не перенаправляються на правильну URL-адресу. Щоб це виправити, Вам необхідно відредагувати Ваш .htaccess файл та додати ці два правила до двох груп правил Супер Кешу:КлючСписок всіх закешованих файлівСписок найновіших закешованих сторінок (може довго виконуватися на завантажених сайтах, використовуйте з обережністю.)режим блокуванняЗаблоковано:Рівень логуТип логуВедення лог-файлу простіше, але виникає проблема - очищення кешу буде очищати лог-файл.Зробити Вордпрес швидшимОчистіть текстове поле, щоб знищити сторінку зі списку безпосередньо закешованих сторінок та видалити закешований файл.Невистачає модулів ApacheПідтримка стільникових пристроїв.Знайдено правила rewrite для стільникових пристроївПідтримка мобільних пристроїв потребує додаткових правил у Вашому .htaccess файлі або Ви можете налаштувати плаґін у режим напів-кешування. Ось Ваші налаштування (у порядку ускладнення):Правила Mod RewriteПравила Mod Rewrite не можна оновити!Правила Mod Rewrite необхідно оновити!Правила Mod Rewrite оновлено!Можливо Mod_rewrite не встановлено!Новіші закешовані сторінки:Наступний збір сміття відбудеться через %s хвилинПримітка:ВимкненоВвімкненоНу добре, воно не запрацює швидше, але Ви зробите автора цього плаґіну дуже щасливим!СторінкиБудь ласка, створіть %s /wp-cache-config.php з wp-super-cache/wp-cache-config-sample.phpСказати йому "привіт" у %s також!Будь ласка, перегляньте пункт 16 у Розділі проблем у файлі readme.txtВідвідайте %1$s, щоб очистити кеш, тому що головна сторінка Вашого сайту неправильна та відсутній текст, "%2$s"!Будь ласка, відвідайте %s, щоб очистити кеш, тому що головна сторінка Вашого сайту зараз завантажується!Підготуйте свій сервер для очікуваного збільшення трафіка, дозволяючи блокування. Коли ця опція ввімкнена, нові коментарі не будуть оновлювати закешованих статичних файлів.Скажіть гордо світу, що Ваш сервер підтверджено Діггом! (розмістити повідомлення у підвал Вашого сайту)Режим лише читання. Налаштування не можливо змінити.Доступне для читання:Оновіть цю сторінку, якщо права доступу файлу було змінено.Оновіть цю сторінку коли Ви оновите Ваш .htaccess файл.Відхилені броузери (боти)Необхідне для того, щоб правильно видавати стиснуті супер-кешовані файли.Необхідне для того, щоб налаштувати інформацію щодо кешування на супер-кешованих сторінках. Без цього модуля користувачі ІЕ7 побачать старі сторінки.Відновити налаштування за замовчуваннямПравила необхідно додати до %s також:Не знайдено зразку конфігураційного файлу Вордпрес Кешу (%s). Перевірте Вашу інсталяцію.ЗберегтиЗберегти файлиЗберегти стрічкиЗберегти назви ботів (пошукових павуків)Сторінки пошукуВстановити термін дії для супер-кешованих сторінок. Без цього модуля відвідувачі можливо не побачать нових сторінок коли вони оновлять сторінку або залишать коментар.Налаштувати плаґін у режим напів-кешування та ввімкнути підтримку стільникових пристроїв.НалаштуванняОдинарні статтіВибачте. Мій сайт заблоковано. Оновлення скоро з’являтьсяПротерміновані Супер Кешовані файлиПротерміновані Вордпрес-Кешовані файлиСтрічки у HTTP-запитах для браузерів (ботів), що забороняють Вордпрес Кешу кешувати запити ботів та пошукових павуків. Зауважте, що супер-кешовані файли все ще видаються цим браузерам (ботам), якщо вони вже існують.Стиск Супер КешуСупер Кеш вимкнено, кешує лише Вордпрес Кеш.Стиск Супер Кешу вимкнено.Стиск Супер Кешу ввімкнено.ТегиТекст для пошуку на головній сторінці. Якщо цей текст відсутній, тоді кеш буде очищено. Залиште порожнім, щоб відключити.Дякую за оновленняДякую!Вордпрес Супер Кеш файл з налаштуваннями: %s/wp-cache-config.php і не може бути відредагованим. Щоб внести зміни, цей файл повинен бути доступним для запису веб-сервером.Кеш на Вашому сайті було очищено, тому що на головній сторінці відсутній текст "%2$s". Відвідайте %1$s для перевірки того, що кеш було очищено.Кеш на Вашому сайті була очищено, тому що головна сторінка зараз завантажується. Будь ласка, відвідайте %s для перевірки того, що кеш було очищено.Файл %s.htaccess не може бути змінений веб-сервером. Будь ласка, виправте це, використовуючи команду CHMOD або Ваш FTP-клієнт.Наступні Apache модулі відсутні. Без них плаґін буде працювати у режимі напів-кешування. У режимі повного супер-кешування Ваші відвідувачі можливо побачать зіпсовані сторінки або протермінований вміст сторінок.Правила mod_rewrite змінилися з того часу, коли Ви інсталювали цей плаґін. На жаль, Ви повинні видалити старі правила для Супер Кешу перед тим, як додати нові. Оновіть цю сторінку, коли відредагуєте Ваш .htaccess файл. Якщо Ви бажаєте додати оновлення вручну, змініть наступну стрічку: %1$s щоб вона виглядала приблизно ось так: %2$s Необхідно внести наступні зміни: "HTTP_COOKIE" замінити на "HTTP:Cookie" та "wordpressuser" замінити на "wordpress". Це зміна для Вордпресу 2.5, але це зворотня сумісність зі старішими версіями, якщо Ви достатньо хоробрий, щоб їх використовувати.Це не спричинить ніякого ефекту на звичайних користувачів, але стільникові користувачі побачать незакешовані сторінки.Щоб видавати статичні HTML-файли сервер повинен мати правильні правила mod_rewrite, що додані у файл %s.htaccessНеобхідна перевірка першого слешу.URI-шляхНажаль, Вордпрес не може знайти файл wp-cron.php. Скрипт потребує правильних дій збору сміття цим плаґіном, WordPress scheduled posts такий самий як і інші критичні дії.Нажаль, коли працює Вордпрес МЮ, правила rewrite не можуть бути оновлені автоматично. Будь ласка, відкрийте Ваш .htaccess файл та додайте наступні правила mod_rewrite з самого початку файлу.Деінсталювати, використовуючи скрипт деінсталяції, щоб видалити файли та папки, створені плаґіном. (Будь ласка, перегляньте readme.txt для порад по деінсталяції.)Оновити стискОновити дані сторінкиОновити правили Mod_RewriteЗберегти налаштуванняПереглянути правила Mod_RewriteВордпрес Кеш та Вордпрес Супер Кеш вимкненоВордпрес Кеш та Вордпрес Супер Кеш ввімкненоУправління Вордпрес Супер КешемСтатус Вордпрес Супер КешВордпрес Супер Кеш перевірив головну сторінку Вашого сайту. Будь ласка, відвідайте %s, якщо Ви хочете це відключити.Вордпрес Супер Кеш ввімкнено. Будь ласка, перейдіть на сторінку адміністрування плаґіну, щоб ввімкнути кешування.Знайдено mod_rewrite правила Вордпрес Супер Кешу у Вашому %s.htaccess файлі.
    Відвідайте наступне посилання, щоб побачити додані у цей файл стрічки. Якщо Ви оновили плаґін, переконайтесь, що ці правила підходять.Вордпрес Супер Кеш необхідно налаштувати. Перейдіть на сторінку адміністрування, щоб ввімкнути та налаштувати плаґін.Вордпрес-КешВордпрес-Супер-КешУвагаУвага!Увага! Папка %s доступна для запису!Увага! Ввімкнено PHP Безпечний Режим (Safe Mode)!Увага! Ваше ім’я хосту "%s" прікріплено до %sЧомуЧому Ваші налаштування не можливо змінитиВиявлено Вордпрес МЮВордпрес заблоковано. Статичні файли Супер Кешу не будуть видалені коли з’являться нові коментарі.Вордпрес не заблоковано. Нові коментарі будуть оновлювати статичні файли Супер Кешу у звичайному режимі.Доступне для запису:Ви можете редагувати файл самостійно, додаючи наступні правила.Ви можете побачити, де правила виконуються та дослідити повні правила, відвідавши посилання "Переглянути правила mod_rewrite", що розміщено нижче.Ви можете відчувати проблеми у роботі плаґіну, тому що ввімкнено Безпечний Режим (Safe Mode).Ви повинні редагувати файл самостійно, додаючи наступні правила.Ви повинні мати маркери BEGIN та END у %s.htaccess файлі для того, щоб працювало автооновлення. Вони схожі на це та оточують головні mod_rewrite правила Вордпресу:Ви повинні зробити %s доступною для запису для ввімкнення цієї функції. Оскільки це ризиковано, будь ласка, зробіть її знову доступною лише для читання після того, як Ваша сторінка згенерується.Ви або Адміністратор можете виправити роботу, змінивши власника групи скриптів плаґіну. Необхідно також змінити власника групи папки %s/cache/. Додаткові деталі Ви можете переглянути на сторінці документації безпечного режиму.Ви або Адміністратор повинні вимкнути це. Додаткові деталі Ви можете переглянути на сторінці документації безпечного режиму. На жаль, це не можна вимкнути у фалі .htaccess. Це можна поправити у файлі налаштувань php.ini.Вам необхідно змінити права доступу для папки %s та зробити їх більш обмеженими. Використовуйте Ваш ftp-клієнт або наступні команди, щоб це виправити:Ваш %s.htaccess недоступний для запису веб-сервером, і повинен бути оновлений необхідними правилами mod_rewrite. Нові правила розміщуються вище звичайних правил Вордпресу, як показано в коді нижче:Ваш конфігураційний файл Вордпрес-Кешу (%s) застарів та не доступний для запису веб-сервером. Будь ласка, видаліть його та оновіть цю сторінку.Ваш каталог кешу ($cache_path) не існує і не може бути створений веб-сервер. Перевірте %s права доступу.Ваш каталог кешу (%1$s) або %2$s повинен мати дозвіл на запис щоб плаґін запрацював. Двічі це перевірте.Ваш сервер налаштований на перевірку власника PHP скриптів перед тим, як дозволити їм читати та писати файли.Ваш сервер думає, що ім’я хосту прікріплено до %s. Деякі служби, такі як збір сміття цим плаґіном та WordPress scheduled posts можуть працювати неправильно.[%s] Перевірка головної сторінки![%s] Головну сторінку стиснено gzipp-ом! Кеш очищено![%s] Головну сторінку стиснено gzipp-ом! Будь ласка, очистіть кеш![%s] Головна сторінка не правильна! Кеш очищено![%s] Головна сторінка не правильна! Будь ласка, очистіть кеш!вимкненоввімкненофайлсекундlanguages/wp-super-cache-es_ES.po000066600000146045152133035240012705 0ustar00msgid "" msgstr "" "Project-Id-Version: WP Super Cache 0.9.7\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2009-11-13 10:27+0000\n" "PO-Revision-Date: \n" "Last-Translator: Omi \n" "Language-Team: Omi \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Poedit-Language: Spanish\n" "X-Poedit-Country: Spain\n" "X-Poedit-SourceCharset: utf-8\n" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "No se encuentra Bad Behaviour. Por favor, revise su instalación." #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:66 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:709 msgid "Disable" msgstr "Desactivar" #: plugins/badbehaviour.php:55 #: plugins/searchengine.php:67 msgid "disabled" msgstr "desactivado" #: plugins/badbehaviour.php:57 #: plugins/searchengine.php:69 #: wp-cache.php:1052 msgid "enabled" msgstr "activado" #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s" msgstr "El soporte de Bad Behaviour está %s" #: plugins/badbehaviour.php:62 #, php-format msgid "(Only half-on caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Sólo se soporta caché \"a medias\", se desactiva la compresión y requiere instalar Bad Behavior en \"%s/plugins/bad-behavior/\") " #: plugins/badbehaviour.php:64 #: plugins/searchengine.php:74 #: wp-cache.php:709 msgid "Enable" msgstr "Activar" #: plugins/badbehaviour.php:70 #: wp-cache.php:786 #: wp-cache.php:788 msgid "Warning!" msgstr "¡Atención!" #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s" msgstr "El plugin No Adverts for Friends está %s" #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(Necesita también friendsadverts.php) " #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Por favor, cree %s /wp-cache-config.php desde wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:170 msgid "WP Super Cache Manager" msgstr "Gestión de WP Super Cache" #: wp-cache.php:172 msgid "Warning! PHP Safe Mode Enabled!" msgstr "¡Atención, modo PHP Safe activo!" #: wp-cache.php:173 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Podría experimentar problemas ejecutando este plugin con el modo PHP SAFE activo." #: wp-cache.php:175 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Su servidor está configurado para comprobar el propietario de los scripts PHP antes de permitirles escribir y leer archivos." #: wp-cache.php:176 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Usted, o un administrador, debería ser capaz de hacerlo funcionar cambiando el propietario del grupo de los scripts para que coincidan con el del usuario web del servidor. El propietario del grupo del directorio %s/cache/ también deberá cambiarse. Revise la página sobre safe mode en el manual para obtener más información." #: wp-cache.php:178 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Usted, o un administrador, deberán desactivar esto. Revise la página sobre safe mode en el manual para obtener más información. Desafortunadamente, esto no puede ser desactivado desde un fichero .htaccess sino que debe hacerse desde el fichero de configuración php.ini" #: wp-cache.php:189 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "El archivo de configuración ha cambiado, algunos valores pueden ser incorrectos. Recargue de nuevo la página desde el menú \"Opciones\" para reestablecerlos." #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "No puedo continuar...solucione los problemas descritos y reintente." #: wp-cache.php:211 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "¡Atención! Su hostname \"%s\" resuelve como %s" #: wp-cache.php:213 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Su servidor cree que su hostname resuelve como %s. Algunos servicios, como la recolección de basura de este plugin o la publicación diferida de WordPress, podrían no funcionar correctamente." #: wp-cache.php:214 #: wp-cache.php:228 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Por favor, revise la entrada nº 16 de la sección Troubleshooting del fichero readme.txt" #: wp-cache.php:227 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Desafortunadamente WordPress no puede localizar el fichero wp-cron.php. Este script es necesario para el funcionamiento de la función de recolección de basura que realiza este, plugin así como para la publicación diferida de WordPress y otras actividades críticas." #: wp-cache.php:239 msgid "Mod rewrite may not be installed!" msgstr "¡Mod rewrite puede no estar instalado!" #: wp-cache.php:240 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use half-on mode." msgstr "Parece que mod_rewrite no está instalado. Algunas veces esto no es 100% preciso, especialmente si no está utilizando Apache. Por favor, compruebe que el módulo mod_rewrite se encuentra cargado. Es necesario para servir los ficheros estáticos del Super Cache. No obstante, debería ser capaz de poder usar el modo de caché \"a medias\"." #: wp-cache.php:245 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Modo de Solo Lectura. La configuración no puede cambiarse." #: wp-cache.php:245 msgid "Why your configuration may not be changed" msgstr "¿Por qué no puede cambiarse su configuración?" #: wp-cache.php:245 msgid "Why" msgstr "¿Por qué?" #: wp-cache.php:247 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "El archivo de configuración de WP Super Cache es %s/wp-cache-config.php y no puede modificarse. Dicho archivo debe tener permisos de escritura para que pueda ser modificado." #: wp-cache.php:248 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "La forma más sencilla es cambiar temporalmente los permisos utilizando el comando CHMOD de su cliente FTP. Asegúrese de que puede ser globalmente editado y todo debería ir bien." #: wp-cache.php:249 msgid "Writeable:" msgstr "Editable:" #: wp-cache.php:250 msgid "Readonly:" msgstr "Sólo lectura:" #: wp-cache.php:262 #, php-format msgid "Warning! %s is writeable!" msgstr "¡Atención, %s es editable!" #: wp-cache.php:263 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Debería cambiar los permisos de %s y hacerlos más restrictivos. Utilice su cliente de FTP o el siguiente comando para resolver cosas:" #: wp-cache.php:354 msgid "WP Super Cache Status" msgstr "Estado WP Super Cache" #: wp-cache.php:357 msgid "ON" msgstr "ACTIVADO" #: wp-cache.php:357 msgid "WP Cache and Super Cache enabled" msgstr "WP Cache y Super Cache activos" #: wp-cache.php:358 msgid "HALF ON" msgstr "A MEDIAS" #: wp-cache.php:358 msgid "Super Cache Disabled, only legacy WP-Cache caching." msgstr "Super Cache desactivado, sólo caché WP-Cache." #: wp-cache.php:359 msgid "OFF" msgstr "DESACTIVADO" #: wp-cache.php:359 msgid "WP Cache and Super Cache disabled" msgstr "WP Cache y Super Cache desactivados" #: wp-cache.php:360 msgid "Don’t cache pages for logged in users." msgstr "No hacer caché de páginas para usuarios autentificados." #: wp-cache.php:361 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "¡Dígale al mundo que su servidor está a prueba de Digg! (pone un mensaje en el pie de su blog)" #: wp-cache.php:362 msgid "Clear all cache files when a post or page is published. (This may significantly slow down saving of posts.)" msgstr "Limpiar la caché cuando se publique un artículo o página (esto puede ralentizar bastante el proceso de guardado)." #: wp-cache.php:363 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated. Recommended for very busy websites with lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" obsolete." msgstr "Reconstruir caché. Sirve un fichero supercaché a los usuarios anónimos mientras que el nuevo está siendo generado. Recomendado para sitios muy activos con muchos comentarios. Hace que \"páginas directamente en caché\" y \"modo Confinamiento\" queden obsoletos." #: wp-cache.php:365 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Bloquear ficheros toscamente. Normalmente no necesitará esto, pero podría serle de ayuda si su servidor tiene poca potencia. ¡Aviso, es muy poco probable, pero podría ocasionar que su servidor se bloquease!" #: wp-cache.php:367 msgid "List the newest cached pages (may be expensive to run on busy sites, use with caution.)" msgstr "Listar las nuevas páginas en caché (puede ser costoso de ejecutar en sitios muy activos, utilizar con precaución)." #: wp-cache.php:368 msgid "Mobile device support." msgstr "Soporte para dispositivos móviles." #: wp-cache.php:373 msgid "Mobile rewrite rules detected" msgstr "Reglas Mobile rewrite detectadas" #: wp-cache.php:374 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"Android|2.0\\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone\" and delete those." msgstr "Para un mejor rendimiento debería activar \"Soporte para dispositivos móviles\" o borrar las reglas mobile rewrite rules de su archivo .htaccess. Localice las 2 líneas con el texto \"Android|2.0\\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone\" y elimínelas." #: wp-cache.php:374 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Esto no tendrá repercusión sobre los usuarios normales pero los usuarios de móviles verán las páginas sin usar la caché." #: wp-cache.php:377 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to half-on mode. Here are your options (in order of difficulty):" msgstr "El soporte para móviles requiere de reglas extra en su archivo .htaccess. También puede seleccionar el modo \"A medias\". Aquí se muestran sus opciones (en orden de dificultad):" #: wp-cache.php:378 msgid "Set the plugin to half on mode and enable mobile support." msgstr "Establecer este plugin en el modo \"A medias\" y activar el soporte para móviles." #: wp-cache.php:379 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Eliminar las reglas mod_rewrite del plugin en %s.htaccess que estén entre # BEGIN WPSuperCache y # END WPSuperCache y permitir que el plugin vuelva a generarlas recargando esta página." #: wp-cache.php:380 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ add this line: (do it twice, once for each section)" msgstr "Añadir las reglas manualmente. Edite el fichero %s.htaccess y localice el bloque de código encerrado entre las líneas # BEGIN WPSuperCache y # END WPSuperCache. Hay dos secciones que parecen muy similares. Justo debajo de la línea %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ añada esta otra línea: (deberá hacerlo dos veces, una para cada sección)" #: wp-cache.php:383 msgid "Note:" msgstr "Nota:" #: wp-cache.php:383 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Si desinstala este plugin asegúrese de que el directorio %s es editable por el servidor web para que los archivos advanced-cache.php y cache-config.php puedan eliminarse automáticamente (asegurarse de que esos archivos son editables es también una buena idea!)" #: wp-cache.php:384 #, php-format msgid "Uninstall using the uninstall script to remove files and directories created by the plugin. (Please see readme.txt for instructions on uninstalling this script.)" msgstr "Desinstale utilizando el script de desinstalación para eliminar los archivos y directorios creados por el plugin. (Por favor, eche un vistazo al archivo readme.txt para obtener instrucciones sobre como desinstalar este script)" #: wp-cache.php:386 msgid "Update Status" msgstr "Actualizar Estado" #: wp-cache.php:393 msgid "Required to serve compressed supercache files properly." msgstr "Requerido para servir archivos de supercache correctamente." #: wp-cache.php:393 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Requerido para establecer la información en las páginas de supercache. Los usuarios de IE7 verán páginas antiguas sin este módulo." #: wp-cache.php:393 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Establece la fecha de caducidad en las páginas de supercache. Los visitantes puede que no vean las nuevas páginas al refrescar o que no puedan dejar comentarios sin este modulo." #: wp-cache.php:400 msgid "Missing Apache Modules" msgstr "Módulos de Apache Ausentes" #: wp-cache.php:401 msgid "The following Apache modules are missing. The plugin will work in half-on mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Faltan los siguientes módulos de Apache. El plugin trabajará en modo \"A Medias\" sin ellos. En el modo Supercache sus visitantes podrían ver páginas corruptas o contenido desactualizado." #: wp-cache.php:413 msgid "Make WordPress Faster" msgstr "Hace WordPress Veloz" #: wp-cache.php:415 #, php-format msgid "%1$s really makes your blog go faster. Make it go faster* by buying me an Amazon gift card! Make it out to \"%3$s\" for whatever amount you want. Every penny helps!" msgstr "%1$s realmente consigue que su blog sea más veloz. Puede acelerarlo todavía más* comprándome una tarjeta regalo de Amazon! Hágalo para \"%3$s\" por la cantidad que quiera. Cada céntimo ayuda!" #: wp-cache.php:416 #, php-format msgid "If Amazon isn’t your thing, there’s also PayPal. Click the \"Donate\" button below or take a quick peek at my wishlist." msgstr "Si Amazon no es su sitio preferido, también puede ayudarme a través de PayPal. Pinche sobre el botón \"Donate\" que está un poco más abajo o eche un rápido vistazo a mi lista de deseos." #: wp-cache.php:417 msgid "Thanks in advance!" msgstr "¡Gracias por adelantado!" #: wp-cache.php:418 msgid "Ok, it won’t go any faster but you’ll make this plugin author very happy!" msgstr "Ok, no conseguirá que vaya más rápido, ¡pero hará muy feliz al autor de este plugin!" #: wp-cache.php:426 msgid "Don’t show me this again." msgstr "No mostrar esto nuevamente." #: wp-cache.php:426 msgid "Hide" msgstr "Ocultar" #: wp-cache.php:429 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s es mantenido y desarrollado por %2$s con la colaboración de muchos otros." #: wp-cache.php:430 #, php-format msgid "He blogs at %1$s, posts photos at %2$s and wishes he had more time to read and relax." msgstr "El escribe en %1$s, publica fotos en %2$s y desearía tener más tiempo para leer y relajarse." #: wp-cache.php:431 #, php-format msgid "Please say hi to him on %s too!" msgstr "Por favor, dígale hola también en %s!" #: wp-cache.php:440 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Páginas en caché desde %1$s : %2$s" #: wp-cache.php:441 msgid "Newest Cached Pages:" msgstr "Nuevas páginas en caché:" #: wp-cache.php:445 #, php-format msgid "Cached %s seconds ago" msgstr "En caché desde hace %s segundos" #: wp-cache.php:448 msgid "(may not always be accurate on busy sites)" msgstr "(puede no ser siempre preciso en sitios muy concurridos)" #: wp-cache.php:469 msgid "Accepted Filenames & Rejected URIs" msgstr "Nombres de archivos aceptados y URIs rechazadas" #: wp-cache.php:494 msgid "Cache Plugins" msgstr "Caché de Plugins " #: wp-cache.php:505 #: wp-cache.php:516 msgid "Super Cache Compression" msgstr "Compresión Super Caché" #: wp-cache.php:506 msgid "Compression is enabled by default when in HALF ON mode." msgstr "La compresión está activa por defecto cuando se ejecuta el modo A MEDIAS." #: wp-cache.php:518 #: wp-cache.php:696 msgid "Enabled" msgstr "Activado" #: wp-cache.php:519 #: wp-cache.php:696 msgid "Disabled" msgstr "Desactivado" #: wp-cache.php:520 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching this on and off clears the cache." msgstr "La compresión está desactivada por defecto debido a que algunos servidores tienen problemas con los archivos comprimidos. Activar o desactivar esta opción limpiará la caché." #: wp-cache.php:523 msgid "Super Cache compression is now disabled." msgstr "La Compresión Super Caché se ha desactivado." #: wp-cache.php:525 msgid "Super Cache compression is now enabled." msgstr "La Compresión Super Caché se ha activado." #: wp-cache.php:527 msgid "Update Compression" msgstr "Actualizar compresión" #: wp-cache.php:534 msgid "Mod Rewrite Rules" msgstr "Reglas Mod Rewrite" #: wp-cache.php:581 msgid "WordPress MU Detected" msgstr "Se ha detectado WordPress MU" #: wp-cache.php:581 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Desafortunadamente las reglas \"rewrite\" no pueden actualizarse de forma automática cuando se ejecuta WordPress MU. Por favir, abra su archivo .htaccess y añada las siguientes reglas mod_rewrite por debajo de otras reglas existentes en dicho fichero." #: wp-cache.php:583 msgid "Mod Rewrite rules cannot be updated!" msgstr "¡Las reglas Mod Rewrite no pueden actualizarse!" #: wp-cache.php:584 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Debe tener marcadores BEGIN y END dentro de su fichero %s.htaccess para que funcione la actualización automática. Se parecen a lo siguiente y rodean a las reglas mod_rewrite principales de WordPress:" #: wp-cache.php:586 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Recargue esta página después de que haya actualizado su fichero .htaccess" #: wp-cache.php:590 msgid "Thank you for upgrading." msgstr "Gracias por actualizar." #: wp-cache.php:590 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Las reglas mod_rewrite han cambiado desde que instaló este plugin. Desafortunadamente, deberá eliminar las antiguas reglas de supercache antes de que puedan instalarse las nuevas. Recargue esta página después de que haya editado su fichero .htaccess file. Si desea realizar una actualización manual, cambie la siguiente línea: %1$s para que quede como la siguiente: %2$s Los únicos cambios son que\"HTTP_COOKIE\" pasa a ser \"HTTP:Cookie\" y \"wordpressuser\" se convierte en \"wordpress\". Este es un cambio de WordPress 2.5 aunque sigue siendo compatible con versiones anteriores (si tiene valor para usarlas)" #: wp-cache.php:594 msgid "Trailing slash check required." msgstr "Comprobación de \"trailing slash\" (barra al final de una dirección) requerida" #: wp-cache.php:594 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Parece que su blog tiene URLs que terminan con \"/\". Desafortunadamente, desde que instaló este plugin, se ha encontrado un fallo de contenido duplicado para las URLs que no terminan en \"/\" y de aquellas que sí lo hacen y que provoca que no se llame a la URL correcta. Para resolverlo, deberá editar su fichero .htaccess y añadir las dos siguientes reglas a los dos grupos de Super Caché:" #: wp-cache.php:596 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Puede ver dónde van las reglas y examinar todas ellas pinchando sobre el enlace \"Ver reglas mod_rewrite\" que se muestra abajo." #: wp-cache.php:608 msgid "Cannot update .htaccess" msgstr "No se pudo actualizar el fichero .htaccess" #: wp-cache.php:608 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "El fichero %s.htaccess no puede ser modificado por el servidor. Por favor, resuélvalo mediante el comando CHMOD de su cliente de FTP." #: wp-cache.php:608 msgid "Refresh this page when the file permissions have been modified." msgstr "Recargue esta página cuando los permisos hayan sido modificados." #: wp-cache.php:608 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Alternativamente, puede editar manualmente su fichero %s.htaccess y añadir el siguiente código (antes de cualquier regla de WordPress):" #: wp-cache.php:611 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Para servir archivos html estáticos, su servidor debe tener las reglas mod_rewrite correctas añadidas a un fichero llamado %s.htaccess" #: wp-cache.php:613 msgid "You must edit the file yourself add the following rules." msgstr "Deberá editar manualmente el fichero para añadir las siguientes reglas." #: wp-cache.php:615 msgid "You can edit the file yourself add the following rules." msgstr "Puede editar manualmente el archivo y añadir las siguientes reglas." #: wp-cache.php:617 msgid " Make sure they appear before any existing WordPress rules. " msgstr " Asegúrese de que se muestran antes de cualquier regla de WordPress existente. " #: wp-cache.php:619 #: wp-cache.php:646 #, php-format msgid "Rules must be added to %s too:" msgstr "Las reglas deben añadirse también a %s:" #: wp-cache.php:624 msgid "Update Mod_Rewrite Rules" msgstr "Actualizar reglas Mod_Rewrite" #: wp-cache.php:633 msgid "Mod Rewrite rules updated!" msgstr "¡Las reglas Mod Rewrite se han actualizado!" #: wp-cache.php:634 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "El fichero %s.htaccess ha sido actualizado con las reglas mod_rewrite necesarias. Por favor, verifique que son correctas. Deberían parecerse a lo siguiente:" #: wp-cache.php:636 msgid "Mod Rewrite rules must be updated!" msgstr "¡Las reglas Mod Rewrite deben actualizarse!" #: wp-cache.php:637 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Su fichero %s.htaccess no puede ser editado por el servidor y debe actualizarse con las reglas mod_rewrite necesarias. Las nuevas reglas van encima de las reglas normales de WordPress, como se muestra en el siguiente código:" #: wp-cache.php:642 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Se han detectado reglas mod rewrite de WP Super Cache en su fichero %s.htaccess.
    Pinche sobre el siguiente enlace para ver las líneas añadidas a dicho fichero. Si ha actualizado el plugin, asegúrese de que dichas reglas coinciden." #: wp-cache.php:643 msgid "View Mod_Rewrite Rules" msgstr "Ver reglas Mod_Rewrite" #: wp-cache.php:654 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Reglas de codificación Gzip creadas en %s.htaccess" #: wp-cache.php:661 msgid "Fix Configuration" msgstr "Arreglar configuración" #: wp-cache.php:664 msgid "Restore Default Configuration" msgstr "Volver a la configuración por defecto" #: wp-cache.php:672 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "La moderación de comentarios está activada. Su comentario podría tardar cierto tiempo en aparecer." #: wp-cache.php:696 msgid "Lock Down:" msgstr "Modo Confinamiento:" #: wp-cache.php:697 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Prepare su servidor para un pico de tráfico no esperado activando el modo \"confinamiento\". Cuando está activo, los nuevos comentarios de un artículo no provocarán que se refresquen los archivos estáticos de la caché." #: wp-cache.php:698 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Atención desarrolladores: hagan su plugin compatible con el modo \"confinamiento\" comprobando la constante \"WPLOCKDOWN\". El siguiente código hará que su plugin respete la configuración WPLOCKDOWN." #: wp-cache.php:700 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Lo siento, mi blog está en modo confinamiento. Las actualizaciones aparecerán en breve." #: wp-cache.php:704 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress está en modo confinamiento. Los ficheros estáticos de Super Caché no se borrarán cuando se hagan nuevos comentarios." #: wp-cache.php:706 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress no está en modo confinamiento. Los nuevos comentarios refrescarán los ficheros estáticos de Super Caché con normalidad." #: wp-cache.php:712 msgid "Lock Down" msgstr "Confinamiento" #: wp-cache.php:720 msgid "Directly Cached Files" msgstr "Archivos directos en caché" #: wp-cache.php:778 #, php-format msgid "%s removed!" msgstr "%s eliminado!" #: wp-cache.php:786 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Debe hacer que %s pueda editarse para activar esta opción. Como es un riesgo para la seguridad, asegúrese de volverlo a dejar como solo lectura después de que se haya generado la página." #: wp-cache.php:788 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s es editable. Como es un riesgo para la seguridad, asegúrese de dejarlo como solo lectura después de que se haya generado la página." #: wp-cache.php:802 msgid "Existing direct page" msgstr "Página directa existente" #: wp-cache.php:802 msgid "Delete cached file" msgstr "Archivo de caché borrado" #: wp-cache.php:807 msgid "Add direct page:" msgstr "Añadir página directa:" #: wp-cache.php:809 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Los archivos directos a caché son archivos creados directamente fuera de %s donde reside su blog. Esta opción sólo es útil si esta experimentando problemas de mucho tráfico en un artículo o página concreta desde sitios del estilo a Digg o Menéame." #: wp-cache.php:811 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Por ejemplo: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." #: wp-cache.php:812 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Deje el cuadro en blanco para eliminarla de la lista de páginas directas en caché y borrar así el fichero de caché." #: wp-cache.php:817 msgid "Update Direct Pages" msgstr "Actualizar páginas directas" #: wp-cache.php:857 msgid "Expiry Time & Garbage Collection" msgstr "Tiempo de caducidad y Recogida de basura" #: wp-cache.php:859 msgid "Expire time:" msgstr "Tiempo de caducidad:" #: wp-cache.php:860 msgid "seconds" msgstr "segundos" #: wp-cache.php:861 msgid "Garbage Collection" msgstr "Recolección de basura" #: wp-cache.php:861 msgid "If expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Si el tiempo de caducidad es mayor a 1800 segundos (media hora), la recolección de basura se hará cada 10 minutos; en otro caso, se hará 10 segundos después del tiempo de caducidad indicado arriba." #: wp-cache.php:862 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. Aim to have less than 500 cached files if possible." msgstr "Comprobar y eliminar archivos caducados es costoso, pero dejarlos ahí lo es más. En un sitio con mucho tráfico debería establecer el tiempo de caducidad a 300 segundos. Experimente con diferentes valores y visite regularmente esta página para comprobar cuantos ficheros caducados aparecen a diferentes horas del día. El objetivo está en tener menos de 500 archivos en caché siempre que sea posible." #: wp-cache.php:863 msgid "Change Expiration" msgstr "Cambiar caducidad" #: wp-cache.php:902 msgid "Rejected User Agents" msgstr "Agentes de usuario rechazados" #: wp-cache.php:903 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Cadenas en la cabecera HTTP ’User Agent’ que previenen que WP-Cache almacene peticiones de robots de búsqueda. Tenga en cuenta que los archivos de Super Caché se siguen enviando a esos agentes si ya existen." #: wp-cache.php:910 msgid "Save UA Strings" msgstr "Grabar cadenas User Agent" #: wp-cache.php:933 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "No almacenar en caché los siguientes tipos de páginas. Revise el apartado Conditional Tags de la documentación para acceder a un completo argumento sobre cada uno de los tipos." #: wp-cache.php:936 msgid "Single Posts" msgstr "Artículos individuales" #: wp-cache.php:937 msgid "Pages" msgstr "Páginas" #: wp-cache.php:938 msgid "Front Page" msgstr "Página principal" #: wp-cache.php:939 msgid "Home" msgstr "Home" #: wp-cache.php:940 msgid "Archives" msgstr "Archivos" #: wp-cache.php:941 msgid "Tags" msgstr "Etiquetas (tags)" #: wp-cache.php:942 msgid "Category" msgstr "Categorías" #: wp-cache.php:943 msgid "Feeds" msgstr "Feeds" #: wp-cache.php:944 msgid "Search Pages" msgstr "Páginas de búsqueda" #: wp-cache.php:946 #: wp-cache.php:1073 msgid "Save" msgstr "Grabar" #: wp-cache.php:963 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Añada aquí las cadenas (no el nombre del fichero) que forzará que una página no entre en caché. Por ejemplo, si su URL incluye un año y no quiere que los artículos del último año entren en caché, bastará con especificar el año, por ejemplo:’/2004/’. WP-Cache buscará si esa cadena forma parte de la URI para, de ser así, no alojar dicha página en la caché." #: wp-cache.php:969 msgid "Save Strings" msgstr "Grabar cadenas" #: wp-cache.php:985 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Añada aquí aquellos nombres de archivos que pueden ser almacenados en caché, incluso si coinciden con alguna de las subcadenas especificadas arriba." #: wp-cache.php:991 msgid "Save Files" msgstr "Grabar archivos" #: wp-cache.php:1035 msgid "Debug Settings" msgstr "Depurar opciones" #: wp-cache.php:1037 msgid "Currently logging to: " msgstr "Actualmente registrando datos (log) en:" #: wp-cache.php:1047 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Solucione problemas con el plugin depurándolos aquí. Podrá recibir emails de depuración o guardar los registros en un fichero de su directorio caché." #: wp-cache.php:1048 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Guardar los registros en un fichero es más sencillo, pero limpiar la caché provocará que se borren dichos archivos de registro." #: wp-cache.php:1052 msgid "Debugging" msgstr "Modo depuración" #: wp-cache.php:1053 msgid "Logging Type" msgstr "Tipo de registro" #: wp-cache.php:1053 msgid "Email" msgstr "Email" #: wp-cache.php:1054 msgid "file" msgstr "archivo" #: wp-cache.php:1055 msgid "IP Address" msgstr "Dirección IP" #: wp-cache.php:1055 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(depurar sólo peticiones desde esta dirección IP. Su IP es %s)" #: wp-cache.php:1056 msgid "Log level" msgstr "Nivel de registro" #: wp-cache.php:1062 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = menor, 5 = mayor, puede provocar una gran carga al servidor)" #: wp-cache.php:1064 msgid "Advanced" msgstr "Avanzado" #: wp-cache.php:1064 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "En algún caso bastante excepcional pueden ocurrir dos problemas en algunos blogs:
    1. La página principal puede empezar a descargarse como un archivo zip.
    2. Ocasionalmente, una página incorrecta se almacena en caché como si fuese la página principal si su blog utiliza una página principal estática y la estructura de enlaces permanentes es /%categoría%/%artículo%/.
    " #: wp-cache.php:1065 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "Estoy seguro al 99% de que no son fallos de WP Super Cache y de que tan sólo ocurren en casos muy excepcionales, pero si esto le preocupa puede ejecutar un sencillo test cada 5 minutos para verificar que su sitio esta bien. Recibirá un correo en caso de problemas." #: wp-cache.php:1067 msgid "Check front page every 5 minutes." msgstr "Comprobar la página principal cada 5 minutos." #: wp-cache.php:1068 msgid "Front page text" msgstr "Texto página principal" #: wp-cache.php:1068 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Texto a buscar en su página principal. Si se detecta que falta este texto, la caché se limpiará. Déjelo en blanco para desactivar esta opción" #: wp-cache.php:1069 msgid "Clear cache on error." msgstr "Limpiar la caché en caso de error." #: wp-cache.php:1070 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Enviar un email al administrador del blog cuando se hagan comprobaciones (útil para pruebas)" #: wp-cache.php:1083 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Error: la compresión GZIP está activada; debe desactivarla si quiere activar wp-cache." #: wp-cache.php:1131 #: wp-cache.php:1293 msgid "Warning" msgstr "Aviso" #: wp-cache.php:1131 msgid "GZIP compression is enabled in Wordpress, wp-cache will be bypassed until you disable gzip compression." msgstr "La compresión GZIP está activa en WordPress, wp-cache se omitirá hasta que desactive dicha compresión." #: wp-cache.php:1189 #: wp-cache.php:1194 #: wp-cache.php:1226 #: wp-cache.php:1231 #: wp-cache.php:1237 msgid "Error" msgstr "Error" #: wp-cache.php:1189 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Si directorio caché ($cache_path) no existe y no puede ser creado por el servidor. Compruebe los permisos de %s." #: wp-cache.php:1194 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Su directorio caché (%1$s) o %2$s necesita tener permisos de escritura para que este plugin funcione. Verifíquelo bien." #: wp-cache.php:1226 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "El archivo de configuración de WP-Cache (%s) está desactualizado y no puede editarse por el servidor. Por favor, bórrelo y recargue esta página." #: wp-cache.php:1231 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Falta el archivo de configuración y %1$s el directorio (%2$s) no puede editarse por el servidor. Compruebe sus permisos." #: wp-cache.php:1237 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "El archivo de ejemplo de configuración WP-Cache (%s) no existe. Verifique su instalación." #: wp-cache.php:1293 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php no existe o no puede ser actualizado." #: wp-cache.php:1294 msgid "1. If it already exists please delete the file first." msgstr "1. Si existe, por favor, borre primero el fichero." #: wp-cache.php:1295 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Proporcione permisos de escritura a %1$s utilizando el comando CHMOD de su cliente de FTP. (chmod 777 %1$s) y recargue esta página. Esto sólo es una medida temporal: terminado el proceso deberá volver a dejarlo como de sólo lectura (cambiar de 777 a 755 en el comando anterior)" #: wp-cache.php:1296 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Recargue esta página para actualizar %s/advanced-cache.php" #: wp-cache.php:1297 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Si eso no funciona, asegúrese de que el archivo %s/advanced-cache.php no existe:" #: wp-cache.php:1298 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Abra el fichero %1$s$wp_cache_file en un editor de texto.
  • 2. Cambie el texto CACHEHOME por %2$s
  • 3. Guarde los cambios y salve el fichero en %3$s; luego recargue esta página.
    • " #: wp-cache.php:1318 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Error: WP_CACHE no está activo en su fichero wp-config.php y no puedo modificarlo." #: wp-cache.php:1319 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by Wordpress core. " msgstr "Edite el fichero %s y añada la siguiente línea:
    define('WP_CACHE', true);
    En caso contrario, WP-Cache no será ejecutado por el núcleo de Wordpress." #: wp-cache.php:1322 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    Constante WP_CACHE añadida al fichero wp-config.php

    Si sigue viendo este mensaje de aviso, revise por favor el punto 5 del FAQ. La línea WP_CACHE debe subirse sobre otras líneas." #: wp-cache.php:1343 msgid "Cache Contents" msgstr "Contenidos en caché" #: wp-cache.php:1362 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Borrando archivo supercache: %s
    " #: wp-cache.php:1379 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Borrando archivo wp-cache: %s
    " #: wp-cache.php:1443 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:1444 #: wp-cache.php:1457 #, php-format msgid "%s Cached Pages" msgstr "%s Páginas en caché" #: wp-cache.php:1445 #: wp-cache.php:1459 #, php-format msgid "%s Expired Pages" msgstr "%s Páginas caducadas" #: wp-cache.php:1456 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1464 msgid "Fresh WP-Cached Files" msgstr "Archivos recientes en caché" #: wp-cache.php:1465 #: wp-cache.php:1481 #: wp-cache.php:1497 #: wp-cache.php:1513 msgid "URI" msgstr "URI" #: wp-cache.php:1465 #: wp-cache.php:1481 msgid "Key" msgstr "Clave" #: wp-cache.php:1465 #: wp-cache.php:1481 #: wp-cache.php:1497 #: wp-cache.php:1513 msgid "Age" msgstr "Edad" #: wp-cache.php:1465 #: wp-cache.php:1481 #: wp-cache.php:1497 #: wp-cache.php:1513 msgid "Delete" msgstr "Borrar" #: wp-cache.php:1480 msgid "Stale WP-Cached Files" msgstr "Archivos anticuados en caché" #: wp-cache.php:1496 msgid "Fresh Super Cached Files" msgstr "Archivos recientes en Super Caché" #: wp-cache.php:1512 msgid "Stale Super Cached Files" msgstr "Archivos anticuados en Super Caché" #: wp-cache.php:1528 msgid "Hide file list" msgstr "Ocultar lista de archivos" #: wp-cache.php:1530 msgid "List all cached files" msgstr "Mostrar archivos en caché" #: wp-cache.php:1536 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Recolección de Basura
    La última \"RdB\" se hizo hace %s minutos
    " #: wp-cache.php:1537 #, php-format msgid "Next GC in %s minutes" msgstr "La siguiente \"RdB\" se hará en %s minutos" #: wp-cache.php:1540 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Los ficheros caducados son aquellos superiores a %s segundos. Todavía están en uso por el plugin y son borrados periódicamente." #: wp-cache.php:1543 msgid "Delete Expired" msgstr "Borrar caducados" #: wp-cache.php:1549 #: wp-cache.php:1563 #: wp-cache.php:1719 msgid "Delete Cache" msgstr "Borrar caché" #: wp-cache.php:1563 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Borrar archivos de Super Caché (se abrirá una nueva ventana)" #: wp-cache.php:1695 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s está orgullosamente a prueba de Digg gracias a la caché que proporciona %2$s" #: wp-cache.php:1728 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache debe configurarse. Vaya a la página de administración para activar y configurar el plugin." #: wp-cache.php:1734 msgid "Settings" msgstr "Configuraciones" #: wp-cache.php:1744 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache está desactivado. Por favor, vaya a la página de administración del plugin para activar la caché." #: wp-cache.php:1763 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] La página principal esta comprimida con Gzip! Debe limpiar la caché." #: wp-cache.php:1763 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Por favor, visite %s para limpiar la caché ya que la página principal de su sitio esta ahora descargándose!" #: wp-cache.php:1766 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] La página principal esta comprimida con Gzip! Caché eliminada!" #: wp-cache.php:1766 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "La caché de su blog se ha limpiado ya que la página principal de su sitio se está descargando. Por favor, visite %s para comprobar que la caché se ha limpiado correctamente." #: wp-cache.php:1773 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] La página principal esta comprimida con Gzip! Por favor, limpie la caché." #: wp-cache.php:1773 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Por favor, visite %1$s para limpiar la caché, ya que la página principal de su sitio no es correcta y falta el texto , \"%2$s\"!" #: wp-cache.php:1776 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] La página principal no es correcta, caché eliminada!" #: wp-cache.php:1776 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Se ha limpiado la caché de su blog debido a que la página principal de su sitio carece del texto \"%2$s\". Por favor, visite %1$s para comprobar que la caché se ha limpiado correctamente." #: wp-cache.php:1781 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Comprobar página principal!" #: wp-cache.php:1781 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache ha comprobado la página principal de su blog. Por favor, visite %s si quiere desactivar esto." languages/wp-super-cache-ua_UA.mo000066600000223226152133035240012673 0ustar009 8<9,vM` s~?3>rb"*7Z5C5y =bj^ \ r&!!?"#w$Z%`%&.&'&((:(n'*p*,,,,, ,3,-"- 1-,>-k-^.p{.+.//./^/ f/ r/+}//3// 00!%0G0!27>2v22I;3@33sK44%?5e5|5 55 5555553616777888u\9j9=:B::?:9;@;H;NN;; ;n;$.<S<Y<v<<<~<@==>> >><>g*??+?*?? @@ AbAA1B:C&D"/EkRFGGEGH*3H ^H hH sH }HbHH]I$aII IIIIIJ$J"JJ! K,KKL&LM<"Mb_MM|uNyNlO0oO!O-OkO\Q mQ xQQQTQQURmRpSUSSSSTTJ5TTd]UU`iV0V V W7WSIW?W<WX9XPX7eXjXY&YDYYcYY Y YY(YZ+Z,Z.Zf![ [/[0[[?x\8\\ \:]B][]q]H^ M^;X^^q^_1__x`aaQb<idGd#due eTf~f+ggggghNibi{i ii%i'ijjj4jbjklk9lBlQlYlbl|l*llbl[@m m7mrmMRnnYo/o qrr?ssRt$tetau v%vAv)^vvv*v/v.w3FwzwwwwwwwdyRyHzz*z{{{|.}5}"} SQnT<Àhiia˃rq |8rT$$ '.VER(Ö 5ʗ1Ę%֘RnOpD5;'#G#k6Q.+ OL;?آf.x'Nե:$_PI#Y}% ѩ0D#'hGCT0.8M^p[bHN -"Ҵ$Kf3o..Ҷ:7<gt'ܹ$AaY}׻Shn%]ZQnZ$c`,n*PBR $8IOh6DR,Gw JU`83lF 7#@[kQZw2s:]=#ZV~!5 IVCU/eNkBtk /u,'QLK^CG6*I )SQ}UVtos|qhrp h!: q-'qbk.Bh5#  Y f nB  ) !  P, X} r /I !y  Jo  ?8,?eq%$uJw$"G+.?gb_' @ !!0"4#;P#C#;#: $oG$o$o'%e%O%M&V&m&& &G>L(+3uTk$^&  9b!8j _#`%v6ip4Q*+0!;KgW@DI  )&r:$8H"=' {c*A2oZM~.5haC,1 E2U6[yS(lq4YP s9]0/'VBFN /X ,3t 5-w1}|xe\?O"#%Jmd)<zR7.7-n f Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.) (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) (support for multiple domains on multisite websites) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.No Adverts for Friends plugin is %s.Domain Mapping support plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting Moderation plugin is %sBad Behaviour not found. Please check your install.Bad Behaviour support is %s.Cache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Don’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLegacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching.Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.One or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Update Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: WP Super Cache Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-09-27 13:58+0000 PO-Revision-Date: 2011-07-24 13:13+0200 Last-Translator: Alexandr Language-Team: Alyona Lompar MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Ukrainian X-Poedit-Country: UKRAINE Перевірте, що вони йдуть перед всіма вже існуючими в документі правилами WordPress.%1$s вдячний плагіну %2$s за проделаннную роботуДодаток %1$s створений і оновлюється автором %2$s за підтримки багатьох інших.%s сторінок в кеші%s сторінок простроченоДіректрія %s доступна для запису. Вам слід змінити її права на "Тільки читання".%s знищений!Файл %s.htaccess був успішно оновлений, необхідні правила mod_rewrite були додані. Будь ласка, перевірте їх. Вони повинні виглядати так:%s/advanced-cache.php не існує або не може бути оновлений в автоматичному режимі.(1 = найменший, 5 = найбільший, може викликати болше навантаження на сервер)(Експериментальні установки)(Даний плагін буде функціонувати лише в режимі середнього кешування, вимкніть стиск і встановіть плагін "Bad Behavior" в "%s/ plugins/bad-behavior/ ") (Прибирає текст " Ваш коментар очікує перевірки" коли хтось розміщує коментар до запису)(Список не рекомендований для великих сайтів)(Записує звернення тільки з цього IP. Ваш IP - %s)(Вимагає установки friendsadverts.php)(Підтримка для MU - сервісу блогів)1. Якщо він вже існує в папках Вашого блога, видаліть його.2. Змініть права доступу до %1$s, щоб можна було записати дані в автоматичному режимі (права повинні бути: chmod 777 %1$s) перевірте правильність заданих прав і обновіть сторінку. Це тимчасове умова, після оновлення сторінки права доступу потрібно повернути на колишні (з 777 на 755). 3. Оновлення сторінку, файл %s/advanced-cache.php оновиться самПомилка 304. Дана помилка виникає тоді, коли сторінка не була змінена з часу минулого запиту.Підтримка помилки 304 відключена за замовчуванням (через проблеми деяких сервісів).Статус плагіна "No Adverts for Friends": %s.Статус плагіна "Domain Mapping": %s

    Мінлива WP_CACHE добавлена в файл конфігурацій wp-config.php

    Якщо Ви досі бачите це повідомлення, то звіртеся з пунктом 5 ЧАВО (на англ.). Рядок із WP_CACHE повинна бути розміщена вище.

    Параметр WP_CACHE не активований

    Даний параметр повинен бути активований для того, щоб WordPress міг коректно працювати з файлами кеша. В даний момент він відключений. Щоб включити його, відкрийте файл wp-config.php і додайте в нього наступний рядок:

    define('WP_CACHE', true);

  • 1. Відкрийте файл %1$s$wp_cache_file в текстовому редакторі.
  • 2. Змініть рядок CACHEHOME на %2$s
  • 3. Збережіть файл і скопіюйте в %3$s, потім оновіть сторінку.
    • Помилка: Мінлива WP_CACHE не активована у файлі загальних конфігурацій wp-config.php.Очищення сміття
    Попереднє очищення було%s хвилин тому
    "Увага! Ви намагаєтеся включити стиск, але модуль zlib.output_compression відключений. Дивіться пункт номер 21 розділу "Опис проблем" у файлі readme.txt (на англ.)Для коректної роботи плагіна необхідна коректна настройка структури посилань. Щоб налаштувати їх, відвідайте сторінку Постійні посилання.Між правилами у Вашому файлі. Htaccess і правилами самого плагіна виявлені невідповідності. Це може бути просто зайвий символ у рядку, але Ви повинні особисто порівняти оригінальні правила зі своїми якомога швидше. Натисніть на кнопку ’Оновити правила Mod_Rewrite’, щоб зробити це в автоматичному режимі.Найпростіший спосіб виправити це - змінити права доступу, використовуючи CHMOD, через FTP-клієнт. Досить встановити глобальні права на запис.Допустимі імена & Заборонені адресиДодати сторінку в кеш:Поле нижче Ви також можете заповнити фрагментами адрес сторінок (або груп сторінок, наприклад, архів за рік/місяць і т.д.), які не будуть кешуватися. Плагін буде сканувати адреси сторінок на предмет наявності в них фрагментів, зазначених нижче, перед кешуванням. Поле нижче Ви можете заповнити назвами файлів які будуть кешованими, навіть якщо у їх назві є заборонених до кешуванню фрагменти.Додайте правила самостійно. Для цього відкрийте в редакторі файл %s.htaccess і знайдіть код між # BEGIN WPSuperCache і # END WPSuperCache . Ви побачите два схожих блоки коду. Відразу після рядка %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ додайте наступне (таких рядків дві, додайте код і після другої):НастройкиВікВи також можете редагувати файл %s.htaccess вручну і особисто додати необхідні правила (до наявних там правил WordPress): АрхівиДоступні плагіниСтатус плагіна "Awaiting Moderation": %sПлагін " Bad Behaviour" не був знайдений. Перевірте, чи завершили Ви його встановлення.Статус плагіна " Bad Behaviour": %s.Стан кешуПеревірка кешуванняКешувати хіти сайту для прискорення доступу.Кешування відбувається за рахунок PHP файлів, що зберігаються в папці плагіна. Вони завантажуються при включенні режиму Supercache. Завантаження відбувається набагато частіше, ніж для решти плагінів WordPress.Авто перебудова кеша. Гості блогу побачать застарілі версії сторінок кеша поки нові будуть генеруватися.Статистика об'єктів в кеші НЕ створюється автоматично. Щоб оновити її вручну натисніть на посилання нижче.Статистика об'єктів в кеші останній раз створено: %s мин назад.Написано в кеш %s секунд назадСторінок в кеші з %1$s: %2$sСтатус кешуванняКешування вимкненоКешування включеноКешування повинно бути включено, якщо Ви хочете використовувати дану опціюСкасувати загальне кешуванняНеможливо продовжити ... перш ніж повторити спробу, виправте попередні помилки.Не можу оновити файл.HtaccessРубрикиЗмінити час життя копіїПеревіряти головну сторінку кожні 5 хвилин.Повірка та видалення прострочених сторінок кеша займає час, але й залишати такі файли в системі не варто. На великих блогах потрібно виставляти "час життя" кожної копії 300 секунд. Ви можете поекспериментувати з налаштуванням і подивитися, скільки прострочених копій сторінок залишається в кеші протягом дня. Оптимальне число таких сторінок не більше 500. Використовуючи кешування з mod_rewrite або PHP, Ви зможете збільшити кількість кешируємой сторінок.Видаляти старі файли з кешу Super Cache.Очищати кеш коли новий запис або сторінка опублікована.Очищати кеш при помильці.Блокування файлів. Вам швидше за все не знадобиться ця опція, але вона може вирішити проблему малопотужних хостингів. Увага! Включення опції, в окремих випадках, може викликати проблеми в роботі блогу!Перевірка коментарів включена. Перш ніж Ваші коментарі будуть опубліковані пройде якийсь час.Стискати файли кешу щоб прискорити роботу.Стиснення кешу вимкнено за замовчуванням, так як може некоректно працювати на деяких хостингах. Включення або Відключення даної опції автоматично чистить тимчасовий кеш.Файл конфігурацій був змінений, деякі настройки не відповідають вимогам плагіна. Відвідайте сторінку "Настройки" щоб виправити це.Конфігураційний файл відсутній, а папка %1$s (%2$s) недоступна для запису. Перевірте права доступу.В даний моменти кешуються записи з %d з %d.Режим записаний на:ОбслуговуванняРежим відлагодженняВидалитиВидалити весь кешВидалити прострочений кешВидалити файли Super Cache (у новому вікні)Видалити файли з кешуВидаліть всі правила mod_rewrite з файлу %s.htaccess, між # BEGIN WPSuperCache і # END WPSuperCache і обновіть сторінку (відновлення правил запуститься автоматично).Видалення файлів Super Cache:%s
    Видалення файлів WP-Cache: %s
    Розробникам: Зробіть свій власний плагін закритого режиму сумісним з нашим, додавши змінну "WPLOCKDOWN". Наведений нижче код допоможе Вам адоптувати свій плагін до налаштувань нашого Режиму.Пряме кешування сторінокДаний кеш створюється прямо з папки, де знаходиться Ваш блог (папка %s). Ця опція корисна тільки тоді, коли очікується великий приплив відвідувачів з більш популярного сайту на конкретну сторінку або запис Вашого.ВідключитиВимкнутоНе кешувати сторінки наступних типів. Перевірте Статтею Кодексу WP (англ.), щоб дізнатися докладніше про типи сторінок.Виявлена ​​підтримка сервісу мультіблогов! Щоб полегшити і прискорити роботу плагіна, Вам потрібно включити підтримку мультіблогов в налаштуваннях.Не кешувати сторінки для відомих користувачів.КешВідредагуйте код %s і додайте наступну строчку:
    define('WP_CACHE', true);
    Інакше, WP-Cache не зможе запуститися..EmailПовідомити адміністратора блогу по завершенню перевірки (корисно при тестуванні на помилки).ВключитиВключенийПомилкаПомилка: стиснення GZIP увімкнено, вимкніть його якщо хочете запустити wp-cache.Сторінка існуєАктуальність кешу:Прострочений кеш - це сторінки, створені більш ніж %s секунд тому. Не дивлячись на свій статус, вони використовуються в загальному кеші і періодично видаляються.Прострочені сторінки & Очищення сміттяФідиПеревірка сторінки %s в кеші:Перевірка першої копії %s:Перевірка другої копії %s:Відновити стандартні настройкиТут можна вирішити деякі проблеми, що виникають при роботі з плагіном, за допомогою налагодження. Ви можете записувати службову інформацію (логи) у файли директорії кешу.Для більш продуктивної роботи сайту, Вам варто включити опцію "Підтримка мобільних пристроїв" або видалити цей запис із правил ст. Htaccess. Знайдіть такий текст (дві строчки) "2.0\MMP|240x320" і видаліть його.Наприклад: щоб додати в кеш сторінку%1$sabout/, потрібно прописати %1$sabout/ або /about/. Кеш для сторінки буде створено відразу ж після першого до неї звернення гостем.Нові файли Super CacheНові файли WP-CacheОсновна сторінкаКлючовий текстПовне кешування проіхойдет через %d ч %d хв і %d сек.Стиснення GZIP включено в настройках WordPress, плагін не буде працювати до тих пір, поки Ви не відключите gzip.Очищення сміттяПравила для Gzip-стиснення додані в файл %s.htaccess.Відвідайте блог автора плагіна %1$s та його фотоблог на %2$s.Прибрати списокДомашня сторінкаII’m 99% certain! Помилки, які можуть виникнути при роботі з WP Super Cache, не пов'язані з самим плагіном. Вони виникають в окремих випадках, але Ви можете підстрахуватися, запустивши автоматичну перевірку блогу кожні 5 хвилин. У разі помилки, Вам буде надіслано повідомлення. Адреса IPЯкщо це не спрацювало, переконайтеся що %s/advanced-cache.php точно не існує:Якщо час актуальності кешу більше 1800 секунд (півгодини), то очищення сміття буде запускатися кожні 10 хвилин.Деактивувавши плагін, переконайтеся що папка %s доступна для запису в настройках Вашого сервера, щоб файли плагіна advanced-cache.php і cache-config.php були вилучені в автоматичному режимі (також перевірте наявність прав на запис для цих двох файлів).В режимі ’Загальних кешування’ запланована очистка сміття буде видаляти тільки кеш записів простого типу (кеш з Super Cache не буде вилучено). Дана настройка рекомендована для використання.В особливо рідкісних випадках на блозі можуть статися дві проблеми:
    1. Замість головної сторінки користувачі будуть бачити пропозицію завантажити. Zip архів з нею
    2. Замість головної сторінки може бути додана в кеш зовсім інша (тільки у випадку, якщо Ваш бог використовує наступну структуру посилань /%category%/%postname%/).
    Виникла помилка, пов'язана з тим, що модуль mod_rewrite відсутній або не встановлений. Будь ласка, перевірте наявність модуля mod_rewrite в конфігураціях сервера. Модуль необхідний для коректної роботи плагіна з статичними файлами. Без підключеного mod_rewrite Ви можете використовувати тільки режими з підтримкою PHP або середню кешування.Здається, всі посилання Вашого блогу закінчуються символом "/". На жаль, як тільки Ви встановили даний плагін, спрацювала опція, що виявила копії посилань без символу "/" на кінці, і тепер вона не може здійснити перенаправлення на вірний адресу. Щоб це виправити це, Ви повинні відредагувати файл.htaccess і додати два нових правила до групи основних правил плагіна Supercache:КлючСпрощене кешування.Низький рівень: 1 e-mail на початку і 1 в кінці кешування.Список кешованих файлівСтворити список сторінок в кеші (виводиться на цій сторінці)Закритий режимЗакритий режим:Рівень логуТип входуОтримати доступ до файлу лога просто, але при очищенні кешу лог також буде видалено.Зроби свій блог швидше!Щоб видалити сторінку з такого кеша, очистіть текстове поле і видаліть файли кешу.Високий рівень: 2 повідомлення на 100 записів.Середній рівень: 1 повідомлення на 100 записів.РізнеВідсутні модулі ApacheПідтримка мобільних пристроївВиявлена підтримка мобільних пристроївПідтримка блогом мобільних пристроїв вимагає присутності особливих правил у файлі. Htaccess, інакше Ви не зможете використовувати цю опцію. Нижче представлені можливий способи (в порядку складності):Модуль Mod RewriteMod Rewrite не може бути оновлений!Правила mod_rewrite повинні бути оновлені!Правила mod_rewrite оновлені!Здається, модуль mod_rewrite не встановлено!Використання mod_rewrite допоможе зробити роботу блога швидше, ніж PHP (хоча і цей варіант теж не такий повільний). Цей режим простіше і зручніше, але починаючому користувачеві краще використовувати кешування PHP.Все ще потрібна допомога? Дивіться офіційний ЧАВО по плагіну Super Cache (англ.). Також, Ви можете задати своє питання на форумах тех. підтримки (англ.), або ознайомитися з проблемами інших користувачів і запропонованими їм рішеннями. Нове в кеші:Наступне очищення буде через%s хвилинВажливо:Важливо: рекомендується включити PHP кешування, авто перебудову кешу і підтримку для мобільних пристроївВажливо: Mod_rewrite або Legacy caching відключені. Типово буде завантажуватися сторінка "Настройки".Увага: Серед правил mod_rewrite виявлені правила від Supercache. Для роботи з кешем будуть використані саме ці правила. Щоб видалити їх, Вам потрібно вручну відредагувати файл. Htaccess.Увага: Перевірка правил WP Super Cache mod_rewrite відключена для блогів мережі поки не буде запущена на головному блозі.Увага: Перевірка правил WP Super Cache mod_rewrite відключена для блогів мережі поки не буде запущена на головному блозі.ЄСписок кешування недоступний.При роботі з кешем сталися помилки:Оновлювати сторінку при додаванні нового коментаря до неїPHP використовує стиснення для стислих сторінки Вашого сайту. Відключення даної опції рекомендується, щоб уникнути багаторазового стиснення сторінок плагіном. Дізнатися більше, відвідавши розділ 16 в "Опис проблем" у файлі readme.txt (на англ.). Також ознайомтеся з цієї сторінкою (на англ.) по php.ini.Сторінка %d: %d (%s)Сторінка 1: %sСторінка 2 :%sСторінкиПомилка структури посиланьБудь ласка, створіть файл %s /wp-cache-config.php з wp-super-cache/wp-cache-config-sample.phpБудь ласка, відвідайте %s автора!Щоб дізнатися більше, відвідайте розділ 16 в Описі проблем у файлі readme.txt (на англ.)Для довідки дивіться readme.txt (документ на англ.). Там Ви знайдете корисну інформацію щодо використання та видалення плагіна WP Super Cache. Сталася помилка, на головній сторінці Вашого блогу не був виявлений ключовою текст "%2$s"! Щоб виправити помилку, відвідайте цю сторінку %1$s і уручну очистити кеш.Сталася помилка! Відвідайте %s щоб видалити кеш!ДодаткиЗагальний кешКешувати %s записи.Створити загальний кеш заразЗагальне кешування було перезапущенe. %sПопередній режим (очищення сміття працює не повністю, опція рекомендована до включення.)Проте, при використанні даного виду кешу створюється набагато більше файлів. Рекомендується використовувати такий тип, якщо у Вас дуже багато записів (10 тисяч і більше) на блозі. Особливо це важливо, якщо Ви користуєтеся послугами віртуального хостингу.Загальне кешування відключено. Будь повний режим роботи плагіна або зверніться до адміністратора сервера.Підготуйте свій блог до запланованих сплесків відвідуваності, активувавши даний режим. В активному стані розміщення нових коментарів і записів НЕ буде оновлювати статичні файли в кеші.Розповісти усім, що Ви користуєтеся плагіном WP Super Cache (повідомлення буде розміщено в "підвалі" сайту)!Режим "только_чтеніе". Настройки не можуть бути змінені.Тільки читання:РекомендованоОновлення кешу через %d ч %d хв і %d сек.Оновлювати загальний кеш кожні %s хвилин (введіть 0, щоб відключити, мінімальний допустимий кількість хвилин %d).Оновлення сторінку коли необхідні права доступу будуть задані.Оновлення сторінку коли закінчите редагування файлу.Htaccess.Наступні записи оновлені:Оновити статистику кешаПошукові та інші ботиНеобхідно для правильного стиснення файлів.Необхідно налаштувати кешування на сторінці плагіна. Користувачі браузера IE7 будуть бачити неоновленою сторінки з кеша без підтримки даного модуля.Відновити налаштування за замовчуваннямПрава на запис повинні бути оновленіПравила повинні бути також додані до %s:Файл WP-Cache (%s) не був знайдений. Перевірте, завершили Ви установку плагіна.ЗберегтиЗберегти список файлівЗберегти список заборонених фрагментівЗберегти налаштуванняЗагальне кешування за розкладом відключено.Загальне кешування за розкладом відключено. Якщо служба зараз запущена, вона не буде завершена поки поточні 100 сторінок Не кешувати.Загальне кешування відбудеться через %d хвилинЗагальне кешування відбудеться через 10 секунд.Наступне заплановане оновлення загального кешу через %d хвилин.Прокрутіть сторінку вниз і натисніть кнопку Оновити правила Mod_Rewrite..Сторінки пошукуВідправляти мені повідомлення з повідомленнями про оновлення кешу.Відправити незахищений (не по https) запит для головної сторінкиВстановіть дату закінчення актуальності сторінок. Користувачі можуть не побачити нову версію кешовані сторінки без даного модуля.Встановіть значення на 0, щоб відключити Очищення сміття.Переведіть плагін в режим середнього кешування і активуйте мобільних пристроїв.НастройкиЗаписиВибачте, мій блог тимчасово недоступний. Зайдіть пізнішеСтарі файли Super CacheСтарі файли WP-CacheЩоб заборонити плагіну кешувати запити від пошукових ботів і інших мережевих роботів, введіть їх назви в поле нижче (по одному в рядку). Якщо копія сторінки вже існує в кеші Super Cache, то вона все одно буде відправлена боту.МіткиПеревіритиПеревірте налаштування кешування свого блога натисканням однієї кнопки.ПеревіркаВведіть текст який плагін буде шукати на головній сторінці. Якщо текст не буде виявлений, то кеш автоматично очиститься. Залиште поле порожнім щоб відключити опцію.Спасибі за оновлення.Конфігураційний файл плагіна WP Super Cache %s/wp-cache-config.php не може бути змінений. Щоб продовжити, Ви повинні встановити права на запис для файлу.Сталася помилка, на головній сторінці Вашого блогу не був виявлений ключовою текст "%2$s"! Відвідайте цю сторінку %1$s щоб перевірити кеш.Весь кеш для Вашого блогу був очищений, так як плагін помітив помилку на головній сторінці (вона Викачуємо архів). Для перевірки кеш, відвідайте цю стрніцу %s.Файл %s.htaccess не може бути оновлений в автоматичному режимі. Щоб виправити це задайте необхідні для запису права доступу до нього. Наступні модулі Apache відсутні на Вашому сервері. Без них плагін зможе працювати тільки в режимі середнього кешування. У режимі з підтримкою Super Cache Ваші користувачі можуть бачити пошкоджені сторінки або прострочені їх копії.З моменту останньої встановленої версії плагіна правила mod_rewrite були змінені. На жаль, Вам доведеться вручну видалити старі правила перш ніж нові зароблять. Оновлення цю сторінку коли закінчите редагувати файл.Htaccess. Якщо Ви хочете повністю оновити все самі, то замініть наступний рядок: %1$s на цю: %2$s. Єдина відмінність - це заміна "HTTP_COOKIE" на "HTTP: Cookie" і "wordpressuser" на "wordpress". Ці зміни пов'язані з новою версією WordPress 2.5 . Звичайно Ви можете продовжувати працювати зі старими версіями, якщо вистачить сміливості;) Сторінки не збігаються! Тимчасової штамп відрізняється або не було знайдено!Необхідні для роботи плагіна права були змінені або відсутні.Тимчасові штампи обох варіантів сторінки збігаються!Для використання даної опції потрібно знати не тільки PHP, але і WordPress (не на початковому рівні).При активації загального кешування, буде створено копію для кожного запису і сторінки Вашого блогу. В цьому режимі створюються статичні сторінки, які потім будуть бачити "непізнані" відвідувачі (наприклад, пошукові боти та інші). Це може допомогти в поліпшенні рівня PR Google, так як в основі їх алгоритму лежить і швидкість відгуку веб-сайту.На Ваших звичайних відвідувачів це ніяк не відіб'ється, а ось використовують мобільні пристрої для веб-серфінгу не будуть отримувати кешовані сторінки (якщо опція відключена).Щоб плагін міг правильно працювати з статичними html файлами, Ви повинні додати в файл %s.htaccess правила модуля mod_rewrite Надто багато об'єктів в кеші, створення списку неможливо.Необхідна перевірка trailing slash.АДРЕСАНа жаль, файл wp-cron.php не було виявлено. Цей скрипт необхідний для коректної роботи опцііі "Очищення сміття" і самого WordPress.На жаль, mod_rewrite неможливо оновити в автоматичному режимі в WordPress MU. Вам доведеться вручну зробити це: відкрийте файл. Htaccess (розташований в кореневій директорії блога) і додайте наступні правила в нього.Оновити сторінкиОновити правила mod_rewriteОновити настройкиОновитиВикористовувати PHP для обслуговування кешу.Використовувати mod_rewrite для обслуговування кешу.Використовувати об'єкти кеша для зберігання кешованих файлів.Подивитися правила mod_rewriteУстановки WP Super CacheДодаток WP Super Cache щойно перевірив головну сторінку Вашого блогу на предмет помилок. Щоб відключити повідомлення та перевірку відвідайте цю сторінку %s.Додаток WP Super Cache не активовано. Щоб активувати його, перейдіть на сторінку управління плагіном.Правила mod_rewrite для плагіна WP Super Cache були виявлені у файлі %s.htaccess.
    Натисніть на відповідну кнопку, щоб подивитися строчки. Якщо Ви тільки що оновили плагін, перевірте всі правила. Додаток WP Super Cache повинен бути налаштований! Щоб активувати його і налаштувати, перейдіть на сторінку управління плагіном.Стан WP-CacheСтан WP-Super-CacheУвагаУвага!Увага! Папка %s доступна для запису!Увага! Включений режим PHP Safe Mode!Увага! Ваше hostname "%s" перетворено у %sВиявлено WordPress MU!Ваш блог використовує Закритий режим. Нові коментарі не оновлюють всі статичні елементи кешу.Ваш блог не використовує Закритий режим. Останні коментарі оновлюють всі статичні елементи кешу.Доступно для запису:Ви можете вручну відредагувати файл і додати необхідні правила.Щоб подивитися повний список працюючих правил, натисніть кнопку нижче "Переглянути правила mod_rewrite".При роботі з плагіном можуть виникнути проблеми, тому що PHP Safe Mode включений на Вашому сервері.Для коректної роботи, у Вашому файлі %s.htaccess повинні бути прописані маркери BEGIN і END. Між ними знаходяться основні правила WordPress mod_rewrite, приклад:Ви повинні дозволити запис для %s. Але так як це потенційна уразливість, після оновлення сторінки поверніть права на читання.Ви або Адміністратор можете виправити помилки, змінивши групу власника скриптів плагіна через налаштування веб-сервера. Також потрібно змінити власника для папки %s/cache/. Для більш детальної інформації дивіться сторінку допомоги по режиму safe mode (на англ.).Ви або Адміністратор повинні відключити це. Для більш детальної інформації дивіться сторінку допомоги по режиму safe mode (на англ.). Ці налаштування НЕ можуть бути відключені через файл. htaccess, для вирішення проблеми потрібно редагувати php.ini в настройках веб-сервера.Ви повинні змінити права на папку %s. Щоб зробити це - скористайтеся FTP-клієнтом або наступною командою:Ваш файл %s.htaccess недоступний для запису (в настройках сервера) і не може бути оновлений в автоматичному режимі. Ви повинні вручну додати нові правила до основних правил WordPress так, як зазначено нижче:Конфігураційний файл WP-Cache (%s) може бути недійсний і недоступний для запису. Будь ласка, видаліть його вручну і обновіть сторінку.Папка ($ cache_path) не існує і не може бути створена в автоматичному режимі. Перевірте права доступу до %s.Папка (%1$s) або %2$s повинна бути доступна для запису. Перевірте права доступу.Ваш коментар очікує підтвердження.Ваш сервер налаштований так, що перевіряє власника для всіх PHP скриптів перед тим як дозволити їм читання або запис в файл.Ваш веб-сервер вирішив, що hostname змінено на %s. Деякі опції плагіна (наприклад, "Очищення сміття") і сам WordPress можуть працювати некоректно.Стиснення Zlib Output включено![%1$s] %2$d кеш записів оновлений[%1$s] Загальне кешування почалося[%1$s] Оновлення кеша записів з %2$d до %3$d[%s] Загальне кешування завершено[%s] Головна сторінка перевірена![%s] Головна сторінка стиснута за допомогою gzipped! Кеш знищений![%s] Головна сторінка стиснута за допомогою gzipped! Видаліть кеш![%s] Головна сторінка відображається з помилкою! Кеш знищений![%s] Кеш головної сторінки містить помилку! Видаліть кеш![%s] Загальнe кешування могло бути перервано.ВесьВідключенийВключенийФайлСекундlanguages/wp-super-cache-tr_TR.mo000066600000212163152133035240012731 0ustar00` <,MQa`r ~?^3* 7 Z 5@! v!="b"j%#-#$# #$$%\&''?(P)**X+w,Z{,%,,-.h./&P0w0:0n1p223333C4L4^4r4 4434445 5,55^6p6+m77n7/8N8 V8 b8`m8+8839C9[9d9!v99!m;7;;;I<@<=s=>>%>>J>#@ )@3@ :@G@[@5j@@@3sA1AABBVC DDDDuD OEjpEEE?FFFF}FqGNwGGGH HnH$=IAbIIIIIJeJxJ5KKK LL<%LgbLL+L* M4MCMHM KNbVNNiOrP&@QgR"{RkS UWUfUE{UU*U V V V!V]7V$VV VVVW3WW$W"X#X!>X`X !Y,YZ&0ZWZ<]ZbZ Z| \y\]0] 4]!A]-c]k]^ _ _$_*_mC_T_`U&`|`p*aUaaabb%bJDbbdlcc`xddve0e e ee7eS%f?yf<ffg,g7Agjyggh hY?hh h h hh(h+h,(i.Uifi i/i0(jYj?j8kTk ]k:jkkkkll l;lqmmmn,oobppqzs<8tGut#tRtu4v vTw~ x+xxxxypz{{-{F{ V{d{%{'{{{j{bj||l}~ ~~$~-~BG~~~*b[% F7Ӏr M~́/8-k~$e'>0 oɋ)-*D/o.3Ό!%.6>HЎ1mKΏn=4[ =_^U/RWxpДA'ƕ$ 48[әKEj"f2's̢@3$XkiD U bmr ( CQAkzJb@B Ԯ D/B)l)(=޲9VN >\o?Զqet"!L-F<e:ݺӻȽþ LXmƿ̿cu f *"I (.+W6  G%em :2Oe$n bP?sRP{X5.(1WW13O=(&$#;_ PFq6 _vqOz8z.84m1~1z] o {$nE0`F|`| .%APghsPz?*\ *<t5{B$ 01Jb!v%$gKRj|6EF 1g!921lIfLV+s$ J%%8`.%TSW;*>(ud: +Frx #08"@[&pM%oen}J+*B~Yp IXWN[!G#   |   B}[#/S&r)8(%0?:p3=,JQflN y.Z8Y-"MK ;<(DpK6He?^[X%Cwq|EJ+,0)  XZP=:!{ VA^7r3UtSHMQ!A_j#11D$?]IOC@T2f W<#bm_J&O@>kcUN.L93*68*\R&5h $E%YaSv4B/]~L"(/'zFWG-+;ox\0n7}dQT > R)F'`,s 9[PlV`24Ig :=Bui 5G Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumUse Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together.Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.No Adverts for Friends plugin is %s.

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages are stored on your server as html and PHP files. If you need to delete them use the button below.Cached pages since %1$s : %2$sCachingCaching OffCaching OnCaching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.ContentsCurrently caching from post %d to %d.Currently logging to: %sDear User, WP Super Cache was removed from your blog but the mod_rewrite rules in your .htaccess were not. Please edit the following file and remove the code between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first! %s Regards, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggingDeleteDelete CacheDelete Cached PagesDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. Email the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExcludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default).Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionExtra homepage checks. (Very occasionally stops homepage caching)FeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesIt appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelMake WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Provides support for Domain Mapping plugin to map multiple domains to a blog.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Supercache Uninstall ProblemsTagsTest CacheTest your cached website by clicking the test button below.Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$sThis is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledsecondsProject-Id-Version: WP Super Cache Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2011-01-05 14:52:03+00:00 PO-Revision-Date: Last-Translator: Language-Team: Baris Unver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Turkish X-Poedit-Country: TURKEY X-Poedit-SourceCharset: utf-8 WordPress'in oluşturduğu kuralların üstünde durmasına dikkat edin.%1$s, %2$s eklentisi sayesinde dağ gibi sağlam!%1$s, %2$s tarafından geliştirilmiştir ve diğer birçok kullanıcının katkısıyla hala gelişmektedir.%s Önbellekli Dosya%s Süresi Dolmuş Sayfa%s yazılabilir durumda. Güvenlik açısından sayfanız oluşturulduktan sonra yazılabilirlik ayarlarını geri almanız önerilir.%s kaldırıldı!%s.htaccess dosyası, uygun mod_rewrite kuralları eklenecek şekilde düzenlendi. Lütfen aşağıdakiyle karşılaştırıp doğru olduğunu kontrol edin:%s/advanced-cache.php bulunamadı veya güncellenemiyor.(1 = hafif, 5 = ağır - sunucuya yük bindirebilir)(Deneysel)(Sadece eski tarz önbellekleme desteklenir, sıkıştırma etkin değildir ve "%s/plugins/bad-behavior/" dizininde Bad Behavior olması gerekir)(çok ziyaret edilen sitelerde tam olarak doğru olmayabilir)(yalnızca bu IP adresinden yapılan raporlama isteklerini kabul et. Şu anki IP adresiniz %s)(friendsadverts.php gerekir) 1. Eğer hala varsa lütfen ilk satırı silin.2. %1$s dizinini, FTP veya sunucu yazılımınızla yazılabilir hale getirin (chmod 777 %1$s) ve sayfayı yenileyin. Bu yalnızca geçici bir işlem; sonrasında ayarı geri almanız gerekecek (bu sefer 777 yerine 755 ile chmod'layın)3. %s/advanced-cache.php dosyasını güncellemek için bu sayfayı yenileyin.304 Not Modified tarayıcı önbelleklemesi. Son gösterimden beri sayfada bir değişiklik olmadıysa belirtir.304 desteği varsayılan olarak devre dışıdır çünkü geçmişte GoDaddy, kullanılan header'larla ilgili sorun çıkarıyordu.Sık Sorulan SorularKurulum YardımıDestek ForumuGoogle Kütüphanelerini kullanarak sık kullanılan JavaScript kütüphanelerini oradan yükletebilirsiniz. İlginçtir, bu YSlow skorunuzu düşürebilir.WP Minify, CSS ve JavaScript dosyalarını birleştirerek sitenize yapılan HTTP sorgularını azaltır. Alternatif olarak, önbelleklenen sayfaları sıkıştıran bir Super Cache eklentisi olan WPSCMin'i kullanabilirsiniz. Ama bu eklenti JS ve CSS dosyalarını birleştirmez.Yahoo! Yslow, Firefox'un Firebug eklentisinin bir alt eklentisidir. Sayfaları analiz etmeye yarar ve yüksek performanslı sayfalarda kullanılan bazı kurallara dayanarak sitenizi hızlandırmak için öneriler sunar. Alternatif olarak, YSlow testi de içeren GTMetrix performans araçlarını deneyebilirsiniz.No Adverts for Friends eklentisi %s

    WP_CACHE sabiti, wp-config.php dosyasına eklendi

    Bu uyarı mesajını görmeye devam ederseniz lütfen FAQ sayfasındaki 5. maddeye bakın. WP_CACHE ile ilgili satır yukarı kaymış olmalı.

    WP_CACHE sabiti 'false' değerinde

    WP_CACHE sabiti, önbelleklenmiş dosyaları sunmak için gerekli kodun sağlanıp sağlanmayacağına karar verir. Ne yazık ki bu şu anda 'false' konumunda. Lütfen wp-config.php dosyanızı açın ve require_once diye başlayan son satırdan hemen önce bu kodu ekleyin (veya bu kodun bir benzeri varsa onu bu şekilde düzenleyin) :

    define('WP_CACHE', true);

  • 1. %1$s$wp_cache_file dosyasını bir düzenleyicide açın.
  • 2. CACHEHOME metnini %2$s ile değiştirin.
  • 3. Dosyayı kaydedin ve %3$s dizinine aktarın; sonra sayfayı yenileyin.
    • UYARI: CDN hizmetinizin düzgün şekilde çalışıp çalışmadığını, %s gibi statik dosyaları önce bir test ederek anlayabilirsiniz.Yalnızca ileri düzey kullanıcılar için: "Speed up your site with Caching and cache-control" isimli belge (İngilizce), sitenizin önbelleklenme sürecini geliştirmek için .htaccess önerileri barındırıyor.Yalnızca ileri düzey kullanıcılar için: Bir obje önbellekleme yöntemi kullanın. Memcached, XCache, eAcccelerator ve benzeri örnekler mevcuttur.Hata: WP_CACHE, wp-config.php dosyanızda etkin değil ve ben dosyayı düzenleyemiyorum.Çöp Toplama
    Son çöp toplama %s dakika önce yapıldı
    Son önbelleğe alınan sayfa: %sDikkat! Sıkıştırmayı etkinleştirmek istediniz fakat zlib.output_compression etkin durumda. Beni Oku dosyasının 'Hata Giderme' sayfasında 21 numaralı maddeye göz atın.Bu eklentinin çalışabilmesi için özel bir adres sisteminin ayarlı olması gerekiyor. Kalıcı Bağlantı Ayarları sayfasına gidip adres sisteminizi ayarlamalısınız.Eklentinin yazmış olması gereken ile .htaccess dosyanızda var olan mod_rewrite kurallarının birbirinden farklı olduğu saptandı. Arada boşluk veya boş satır farkları da olsa, dosyada yazılı kurallarla olması gereken kuralları karşılaştırmanızı öneririz. "Mod_rewrite Kurallarını Güncelle" düğmesine tıklayıp kuralları güncelleyebilirsiniz.Bunu yapmanın basit bir yolu, dosyanın CHMOD izinlerini kısa bir süreliğine değiştirmektir. CHMOD 777 yapmanız yeterlidir ama sonrasında işlemi geri almayı, izinleri eski haline getirmeyi unutmayın.Kabul Edilecek Dosyalar & Reddedilecek AdreslerDirekt sayfa ekle:Buraya, içeren sayfaları önbelleğe alınmamasını sağlayacak metinler (dosyalar DEĞİL) ekleyin. Örneğin, kalıcı bağlantı yapınızda yıl değişkeni kullandıysanız (yani yazı adreslerinizde yıllar varsa) ve geçen yılın yazılarını önbelleğe almak istemiyorsanız, örneğin '2004' yazmanız yeterli olacaktır. Eklenti, adresin içerisinde bu metinlerin varlığını kontrol edecek ve varsa o sayfayı önbelleğe almayacaktır.Yukarıda belirtilen kurallara uysa da önbelleklenebilmesi için buraya dosya isimleri ekleyebilirsiniz.Kuralları kendiniz ekleyin. %s.htaccess dosyasını düzenlemek için açın ve # BEGIN WPSuperCache ile # END WPSuperCache arasındaki satırları bulun. Birbirine çok benzeyen iki bölüm olacaktır. %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ satırının hemen altına şu satırları ekleyin: (iki bölüm için de birer defa yapmayı unutmayın)Ek CNAME'lerGelişmişYaşVeya, %s.htaccess dosyanızı, dosyaya aşağıdaki kodları ekleyerek düzenleyin (en sona yeni bir satır açıp eklein):ArşivlerMevcut EklentilerOnay KuyruğundaOnay Kuyruğu Eklentisi %sBad BehaviourBad Behaviour desteği %sBad Behaviour eklentisi bulunamadı. Lütfen tekrar kontrol edin.CDNCDN kullanımı, Mark Kubacki tarafından yazılan OSSDL CDN Off Linker ile sağlanmaktadırÖnbellek İçeriğiÖnbellek TestiBu siteye gelen ziyaretleri, daha hızlı erişim için önbelleğe alın.Bu eklentiler, WP Super Cache eklenti dizininin içerisinde bir başka eklentiler klasöründe bulunan PHP betikleridir. Etkinleştirildiğinde, WP Super Cache yüklendikten hemen sonra yüklenirler.Önbellek yenileme. Yeni bir önbellek dosyası oluşturulurken ziyaretçilere eskisi gösterilir.Önbellek istatistikleri otomatik olarak üretilmez. Aşağıdaki bağlantıya tıklayarak istatistikleri bu sayfaya yeniden yüklemelisiniz.Önbellek istatistiklerinin son güncellenişi: %s dakika önce.%s saniye önce önbelleklendiÖnbelleklenen sayfalar, sunucunuzda HTML ve PHP sayfaları halinde depolanır. Bunları silmek isterseniz aşağıdaki düğmeye tıklayın.%1$s 'den/'dan beri önbelleklenen sayfalar: %2$sÖnbelleklemeÖnbellekleme KapalıÖnbellekleme AçıkÖnbellekleme, bir siteyi hızlandırmak için atılan adımlardan yalnızca bir tanesidir. Sitenizi hızlandırmaya yardımcı olacak başka eklentiler de mevcuttur:Bu özelliği kullanabilmeniz için önbellekleme etkin olmalıdır.Önbellek Önyüklemesi'ni Devre Dışı BırakDevam edilemiyor... önceki sorunları çözün ve tekrar deneyin..htaccess güncellenemiyorKategori sayfalarıZaman Aşımını Değiştir5 dakikada bir ön sayfayı kontrol edin.Süresi dolmuş önbellek sayfalarının silinmesi sunucuyu biraz yorar ama silinmemesi de yorar. Kalabalık bir sitede 300 saniye değeri uygundur. Farklı farklı süreleri test edip, süresi dolan sayfaların ne kadar durduğunu görebilirsiniz. Eski tarz önbelleklemeyi kullanıyorsanız, 500 önbellek sayfasını aşmamaya dikkat edin. PHP veya mod_rewrite ile önbellekleme yapıyorsanız, birkaç kat daha fazla dosya olmasının bir önemi yoktur.Eski supercache dosyaları temizleniyor.Bir yazı veya sayfa yayınlandığında önbelleği temizle.Bir hatayla karşılaşıldığında önbelleği temizle.Kabaca dosya kilitleme. Muhtemelen buna ihtiyacınız olmayacaktır ama eğer sunucunuz güçsüzse yardımcı olabilir. UYARI: Çok nadir de olsa sunucunuzu kilitleyebilir!Yorum onaylama sistemi etkin; yorumunuzun yayınlanması biraz zaman alabilir.Sayfalar daha hızlı yüklensin diye sayfaları sıkıştır.Sıkıştırma varsayılan olarak devre dışıdır çünkü bazı barındırıcılar (hosting firmaları) sıkıştırılmış dosyalarla sorun yaşarlar. Bu özelliği açmak veya kapamak önbelleği temizler.Ayarların bulunduğu dosya değiştirildi, bazı değerler yanlış olabilir. "Ayarlar" menüsünden sayfayı tekrar yükleyip ayarları sıfırlayın.Ayar dosyası bulunamıyor ve %1$s dizini (%2$s) sunucu tarafından yazılamıyor. Lütfen izinleri kontrol edin.İçerikŞu anda %d ile %d arasındaki yazılar önbelleğe alınıyor.Şuraya kayıt yapılıyor: %sDeğerli Kullanıcı, WP Super Cache blogunuzdan kaldırıldı fakat .htaccess dosyanızdaki mod_rewrite kuralları silinmedi. Lütfen aşağıdaki dosyayı düzenleyerek 'BEGIN WPSuperCache' ile 'END WPSuperCache' arasındaki kodları temizleyin. Yedek almayı unutmayın! %s Saygılar, WP Super Cache Eklentisi http://wordpress.org/extend/plugins/wp-super-cache/Hata AyıklamaHata AyıklamaSilÖnbelleği TemizleÖnbelleğe Alınan Sayfaları SilSüresi Dolan Önbelleği TemizleSuper Cache ile önbelleklenmiş dosyaları silin (yeni pencerede açılır)Önbellekli dosyayı sil%s.htaccess dosyanızda, # BEGIN WPSuperCache ile # END WPSuperCache arasındaki satırları (bu iki satır da dahil olmak üzere) silerek eklentinin ürettiği mod_rewrite kurallarını silebilirsiniz. Sayfayı yenilediğinizde eklenti yenisini üretecektir.Şu supercache dosyası siliniyor: %s
    Şu wp-cache dosyası siliniyor: %s
    Eklenti Geliştiricilerine: Eklentinizin tecrit moduyla uyum sağlaması için "WPLOCKDOWN" sabitini inceleyin. Aşağıdaki kodu eklentinize eklediğinizde eklentiniz WPLOCKDOWN ayarlarıyla uyumlu davranacaktır.Direkt Önbelleklenen DosyalarDirekt olarak önbelleklenen dosyalar %s dizininden, blogunuzun yaşadığı yerden yaratılmıştır. Bu özellik sadece bir anda çok yüksek trafik almayı beklediğiniz zamanlarda işe yarar. (örn. Ekşi Sözlük, İnci Sözlük gibi yerlerden gelen toplu ziyaretler)Statik dosya eşlemesinde kullanılacak dizinler. Dizinleri virgüllerle ayırabilirsiniz. Varsayılan wp-content, wp-includes şeklindedir, kutu boş bırakılırsa bunlar kullanılacaktır.EtksizileştirEtkisizAşağıdaki sayfa türlerini hiçbir zaman önbellekleme. (Koşul Etiketleri (İngilizce) sayfasını ziyaret ederek tüm sayfa türleri hakkında bilgi edinebilirsiniz.)Alan Adı HaritalamaAlan Adı Haritalama eklentisi tespit edildi! Lütfen WP Super Cache eklenti ayarları sayfasına gidip ilgili eklentiyi etkinleştirin.Alan Adı Haritalama desteği %sGiriş yapmış kullanıcılar veya düzenli yorumcular için sayfaların önbellekleme.Kolay%s kodunu düzenleyin ve şu satırı ekleyin:
    define('WP_CACHE', true);
    Bu olmadan, WP-Cache çalışmayacaktır.Kontroller yapıldığında blog sahibine e-posta gönder. (test etmek için yararlı bir özellik)EtkinleştirCDN Desteğini EtkinleştirEtkinBir yorum gönderildiğinde, "Yorumunuz onay kuyruğuna alındı." yazısını yorumun içinden kaldıran eklentiyi açıp kapatır.HataHata: GZIP sıkıştırması etkin; wp-cache'i kullanabilmek için lütfen bu ayarı etkisizleştirin.Hariç tutulacaklarHariç tutulacak dosyaların uzantılarını buraya girin ve uzantıları virgülle ayırın. (örn. .php, .flv, .do) .php her zaman olmalıdır (ve varsayılandır).Var olan direkt sayfaÖnbelleklenen dosyaların zaman aşımı:Zaman aşımına uğrayan sayfalar %s saniyeden daha eski. Hala eklenti tarafından kullanılıyorlar ve düzenli aralıklarla siliniyor.Zaman Aşımı & Çöp ToplamaFazladan anasayfa kontrolü. (Sık sık anasayfa önbelleklenmesi durur.)BeslemelerFetching %s to prime cache: %s dosyasının ilk kopyası alınıyor:%s dosyasının ikinci kopyası alınıyor:Ayarları DüzeltEklentiyle ilgili sorunları, hata ayıklama modunu açarak buraya kaydettirebilirsiniz. Önbellek dizininizde oluşturulacak bir dosyaya kayıt yapılacaktır.En iyi performans için "Mobil cihaz desteği"ni etkinleştirin veya .htaccess dosyasındaki mobil cihazlarla ilgili satırları kaldırın. Bunu yapmak için "2.0\ MMP|240x320" ile başlayan iki satırı silmeniz yeterlidir.Örnek: %1$sabout/ sayfasını önbelleklemek için, %1$shakkinda/ veya /hakkinda/ yazmalısınız. Sayfa, bir sonraki ziyaretçinin ziyaretinde önbelleğe alınacaktır.Yeni Süper-Önbellekli DosyalarYeni Önbellekli DosyalarÖn SayfaÖn sayfa yazısıÖnbelleğin tamamı %d saat, %d dakika ve %d saniye sonra yenilenecek.GZIP sıkıştırması Wordpress için etkin durumda, onu etkisizleştirene kadar wp-cache atlanacak.Çöp Toplama%s.htaccess dosyasında gzip'leme kuralları oluşturuldu.Blogu %1$s ve fotoğrafları %2$s adreslerindedir.Dosya listesini gizleAnasayfaWP Super Cache eklentisinde hata bulunmadığından aşağı yukarı eminim, varsa da çok nadir durumlarda görülüyordur ama bu konuda endişeleriniz varsa 5 dakikada bir kontrol edip sitenizin çalışır durumda olduğunu görebilirsiniz. Bir sorun çıkarsa size e-posta yollanacaktır.IP AdresiEğer bu çalışmazsa, %s/advanced-cache.php dosyasının var olmadığından emin olun:Zaman aşımını 1800 saniyeden (yarım saat) fazla olacak şekilde ayarladıysanız, çöp toplama 10 dakikada bir yapılır. Yarım saatten daha az ise, zaman aşımı süresinden 10 saniye sonra yapılır.Bu eklentiyi kaldırıyorsanız, %sadvanced-cache.php ve cache-config.php dosyaları otomatik olarak kaldırılabilsin. (O dosyaların da yazılabilirliğini kontrol etmek de iyi olur!)Önyükleme Modu'nda düzenli çöp toplama yalnızca bilinen kullanıcılar için eski önbellek dosyalarını temizlemede kullanılır, Super Cache'li dosyalar etkilenmez. Önbellek önyüklemesi yapıldığında bu seçeneğin etkinleştirilmesi önerilir.Çok nadir durumlarda, bloglarda iki farklı problem baş gösterebiliyor:
    1. Anasayfanın bir zip dosyası halinde inebilir.
    2. Anasayfa olarak sabit bir sayfa göstermeyi seçtiyseniz ve kalıcı bağlantı yapınız /%category%/%postname%/ şeklindeyse, anasayfa diye başka bir sayfa önbelleklenebilir.
    Dizinleri dahil etMod_rewrite yüklü değil gibi gözüküyor. Bazen bu kontrol kesin değildir, özellikle Apache kullanmıyorsanız. Lütfen mümkünse mod_rewrite'ın yüklü olup olmadığını doğrulayın. Eklentinin önbellek dosyalarını sunabilmesi için bu özelliğin bulunması şarttır ama yoksa, eski tarz önbelleklemeyi veya PHP ile önbelleklemeyi de kullanabilirsiniz.Anlaşılan blog sayfalarınızın adreslerinin sonu "/" ile bitiyor (buna son taksim denir). Maalesef siz bu eklentiyi yükledikten sonra WordPress içerisinde, "/" ile bitmeyen adreslerin "/" ile biten sayfalara yönlenmediği bir bug bulundu. Bunu düzeltmek için, .htaccess dosyanızı açıp aşağıdaki kuralları, orada iki grup halinde bulunan Super Cache kurallarına eklemelisiniz:AnahtarGeç başlatma: WordPress yüklendikten sonra önbellek dosyalarını gösterme. Eski tarz önbelleklemede çok işe yarar.Eski tarz sayfa önbelleklemeAz: Önyüklemenin başında ve sonunda 1'er e-posta.Önbelleğe alınmış tüm dosyaları gösterBu sayfada son önbelleklenen sayfaları listele.TecritTecrit:Raporlama aşamasıWordPress'i hızlandır!Direkt sayfaları silmek ve önbelleği boşaltmak için metin kutusunu boş bırakın.Çok: 100 yazı önyüklemesi başına 2 e-posta.Orta: 100 yazı önyüklemesi başına bir e-posta.DiğerKayıp Apache ModülleriMobil aygıt desteği.Tespit edilen mobil yeniden yazım kuralları (rewrite rules)Mobil cihaz desteği, .htaccess dosyanıza fazladan kural eklenmesini gerektirir. Veya eski tarz önbelleklemeyi kullanabilirsiniz. Seçenekleriniz (zorluk sırasına göre) şunlar:Mod_Rewrite KurallarıMod_Rewrite kuralları güncellenemiyor!Mod_Rewrite kuralları güncellenmeli!Mod_Rewrite kuralları güncellendi!Mod rewrite yüklenmemiş olabilir!Mod_rewrite en hızlısıdır. PHP önbellekleme de çok hızlıdır ve kullanımı kolaydır. Eski tarz önbellekleme daha yavaştır ama daha esnektir ve bunun da kullanımı kolaydır. Yeni kullanıcılar PHP önbelleklemeyi denemelidir.Yardıma mı İhtiyacınız Var?Yardıma ihtiyacınız mı var? Super Cache BeniOku dosyasını inceleyin. Bu belge; eklentiyi yüklemek için gerekli dokümantasyonu, Sık Sorulan Sorular'ı ve Hata Anlama ipuçlarını içerir. Yardım forumu (İngilizce) de mevcuttur, burada sorununuzun çözümünü bulabilirsiniz.Son Önbelleklenen Sayfalar:Sonraki çöp toplama %s dakika sonraNot:Not: PHP önbelleklemeyi, önbelleğin yenilemeyi ve mobil tarayıcı desteğini etkinleştirirNot: Mod_rewrite veya eski tarz önbellekleme etkin. Varsayılan olarak Gelişmiş Ayarlar görüntüleniyor.Not: PHP önbellekleme aktif durumda ama Super Cache için var olan mod_rewrite kuralları mevcut ve önbelleklenen sayfalar bu kurallara göre sunulacak. Eğer siteniz düzgün çalışıyorsa bu mesajı dikkate almanıza gerek yok ama .htaccess dosyasından Super Cache önbelleklemeyi sağlayan kuralları kaldırmanızda fayda var.Not: WP Super Cache mod_rewrite kural kontrolleri, blog ağının ana sitesi haricinde devre dışıdır.Not: WP Super Cache mod_rewrite kural kontrolleri, blog ağının ana sitesi haricinde devre dışıdır.TamamNesne önbellekleme devrede, listelenecek önbellek yok.Site dışı URLBir veya birden fazla sayfa sorgusu başarısız:Sadece yorum yapıldığında sayfayı güncelle.PHP, ziyaretçilerinizin gördüğü verileri sıkıştırıyor. Bunu devre dışı bırakmak, eklentinin önbelleğe aldığı sayfaların tekrar tekrar sıkıştırılmaması için tavsiye edilir. (Hata Giderme bölümünde 21. maddeyi okuyun.) PHP.ini dosyanızı düzenleme yönergeleri için bu sayfayı okuyun.Sayfa %d: %d (%s)Sayfa 1: %sSayfa 2: %sSayfalarKalıcı Bağlantı Yapısı HatasıLütfen eklentinin işinize yarayıp yaramadığını derecelendirin. Eklentinin gelişimine katkıda bulunmuş olacaksınız.Lütfen wp-super-cache/wp-cache-config-sample.php dosyasından %s /wp-cache-config.php dosyasını oluşturun.%s adresinden bi' selam çakmayı da unutmayın!Lütfen readme.txt dosyasında, hata çözme bölümündeki 16. girdiyi okuyun.Lütfen eklentiyi kaldırmak için readme.txt dosyasındaki yönergelere başvurun. "How to uninstall WP Super Cache" bölümünü arayın.Lütfen %1$s sayfasına gidip önbelleğinizi temizleyin çünkü ön sayfanız doğru değil ve "%2$s" metni gözükmüyor!Lütfen sitenizin indirdiği önbellekli ön sayfayı temizlemek için şurayı ziyaret edin: %sEklentilerÖnyükleme%s yazıyı önyüklemeye al.Önbellek Önyüklemesi'ni Şimdi ÇalıştırÖnyükleme yeniden başlatıldı. %sÖnyükleme modu (çöp toplama yalnızca eski tarz önbelleklemede. Önerilir.)Yalnız önyükleme çok sayıda dosya oluşturur. Önbellekleme de en yeni yazıdan en eskisine kadar yapılır, dolayısıyla lütfen çok fazla (10 binden fazla) yazınız varsa yalnızca en yeni yazıları önyüklemeye alın. Paylaşımlı hosting'lerde bu özellikle önemlidir.Önbellek önyüklemesi devre dışı. Lütfen eski tarz önbellekleme seçeneğini etkisizleştirin veya barındırıcı firmanızla görüşün.Büyük ziyaretçi akınları için tecrit modunu etkinleştirebilirsiniz. Etkinleştirildiğinde; yeni yorum girilse bile sayfa, önbellekli haliyle sunulur yani yeni yorumlar gözükmez, önbellekteki sabit dosya görüntülenir.Ziyaretçilerinize bu blog'un ne kadar dayanıklı olduğunu duyurun! (blog'un footer kısmına bir mesaj eklenir.)Alan Adı Haritalama eklentisini destekler.Bu Eklentiyi Derecelendirin!Salt Okunur Mod. Ayarlar değiştirilemez.Salt Okunur:ÖnerilenTavsiye Edilen Bağlantılar ve EklentilerÖnbellek %d saat, %d dakika ve %d saniye sonra yenilenecek.Önyüklenmiş önbelleği her %s dakikada bir yenile. (0 devre dışı bırakır, en az %d dakika yazılmalıdır.)İzinleri düzenledikten sonra bu sayfayı yenileyin..htaccess dosyanızı güncelledikten sonra bu sayfayı yenileyin.Şu yazılar yenilendi:Önbellek istatistiklerini güncelleReddedilecek Kullanıcı Temsilcisi (User Agent)Sıkıştırılmış supercache dosyalarını sunabilmek için gereklidir.Super Cache ile önbelleklenmiş sayfalarda, önbellekleme bilgilerinin girilmesi için gereklidir. IE7 kullanıcıları bu olmadan, önbelleğe alınmamış sayfaları görüntülemeye devam ederler.Varsayılan Ayarları Geri YükleMod_Rewrite kuralları güncellenmeliKurallar %s dosyasına da eklenmeli:Örnek WP-Cache ayar dosyası (%s) yerinde yok. Lütfen yüklemenizi gözden geçirin.KaydetDeğişiklikleri KaydetDosyaları kaydetDizgileri KaydetKT Dizgilerini KaydetÖnbellek önyüklemesinin zamanlanması iptal edildi.Önbellek önyüklemesinin zamanlanması %d dakika içinde başlıyorÖnbellek önyüklemesinin zamanlanması 10 saniye içinde başlıyor.Yeniden önyükleme %d dakika içinde yapılacak.Gelişmiş Ayarlar sayfasında aşağılara doğru gidin ve Mod_Rewrite Kurallarını Güncelle düğmesine tıkayın.Arama sayfalarıDosyalar yenilendiğinde bana durum e-postaları gönder.Güvenliksiz (https'siz) anasayfa sorgusu gönderSuper Cache ile önbelleklenmiş sayfalarda son kullanma tarihini belirleyin. Bu modül olmadan ziyaretçiler, sayfayı yenilediklerinde veya yorum bıraktıklarında yeni sayfayı göremeyebilirler.Çöp toplamayı devre dışı bırakmak için bitiş süresini 0 yapın.Eklentiyi Eski Tarz moduna getirin ve mobil cihaz desteğini aktifleştirin.AyarlarTekil yazı sayfalarıÜzgünüm; blog'umu kilit altına aldım. Güncellemeler sonra görüntülenebilecek.Süresi Dolmuş Süper-Önbellekli DosyalarSüresi Dolmuş Önbellekli DosyalarStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Super Cache Kaldırma SorunlarıEtiketlerÖnbelleği Test EtÖnbelleklenmiş sitenizi aşağıdaki test düğmesine basarak sınayın.Anasayfanızda aranacak metin - eğer bu metin anasayfada bulunamazsa önbellek temizlenir. Devre dışı bırakmak için boş bırakın.Yükselttiğiniz için teşekkürler.CDN Eşleme Aracı eklentisi, eğer "origin pull" yöntemini istemezseniz Amazon S3/Cloudfront sistemlerine dosyaları otomatik olarak yükleyecektir. Yardıma ihtiyacınız olursa, eklenti destek forumunu kullanabilirsiniz (İngilizcedir).WP Super Cache ayar dosyası %s/wp-cache-config.php düzenlenemiyor. Düzenleme yapılabilmesi için dosyanın sunucu tarafından yazılabilir olması gerekiyor.Önbelleğiniz temizlendi çünkü ana sayfanızda "%2$s" metni bulunmuyor. Lütfen %1$s sayfasını ziyaret edip önbelleğin temizlendiğini doğrulayın.Sitenizin anasayfası şu anda indirildiği için önbelleğiniz temizlendi. Lütfen önbelleğin temizlendiğini doğrulamak için %s sayfasını ziyaret edin.%s.htaccess dosyası sunucu tarafından düzenlenemiyor. Lütfen bu hatayı, chmod kullanarak FTP istemcinizle düzeltin.Aşağıdaki Apache modülleri eksik. Onlar olmadan eklenti eski tarz önbelleklemeyle çalışacaktır. Super Cache modunda ziyaretçileriniz, eski içerikle veya bozuk veriyle karşılaşabilir.Eklentiyi yüklediğinizden beri mod_rewrite kuralları değişti. Yenilerinin konabilmesi için öncekileri kaldırmanız gerekiyor. .htaccess dosyanızı düzenledikten sonra bu sayfayı yenileyin. Elle düzenlemek isterseniz, şu satırı şu şekilde değiştirin: %1$s ki şu şekilde gözüksün: %2$s Yapılan değişiklikler şöyle: "HTTP_COOKIE" yerine "HTTP:Cookie" yazılıyor ve "wordpressuser" yerine de "wordpress" geliyor. Bu WordPress 2.5 ile ilgili bir değişikliktir ama kendinizi cesur hissediyorsanız önceki sürümlerle de uyumludur.Yeniden yazım için %1$s yerine kullanılacak yeni adres. Adresin sonuna taksim (/ karakteri) koymayın lütfen..
    Örnek: %2$s.Sayfalar birbirini tutmuyor! Zaman damgaları birbirinden farklı veya bulunamadı!Bu eklentinin ihtiyaç duyduğum yeniden yazım kuralları değişmiş veya yok olmuş.İki sayfanın zaman damgaları uyuşuyor!Bu CNAME'ler, yeniden yazım için %1$s yerine kullanılacaktır (yukarıda belirlediğiniz site dışı adrese ek olarak). Virgülle ayırın. Fazlaca statik dosyaya sahip sayfalar için bu seçenek tarayıcı performansını artırabilir. CNAME'lerin bazen CDN hizmetiniz için de ayarlanması gerekebilir.
    Example: %2$sBu ileri düzey bir özelliktir ve PHP ile WordPress konusunda engin bilgi ve tecrübeye sahip kişiler tarafından yaratılmalıdır.Bu, site içerisindeki tüm yazı ve sayfaları tek tek önbelleğe alacaktır ve (botlar da dahil olmak üzere) ziyaretçiler bu oluşturulmuş Super Cache'li sayfaları görecektir. Google'daki sıralamanızı yükseltme açısından hız da önemli olduğu için bu seçenek faydalı olabilir.Normal ziyaretçilere bir etkisi olmayacaktır ama mobil kullanıcılar önbelleklenmemiş sayfaları göreceklerdir.Statik HTML dosyalarını sunabilmek için sunucunuzda doğru mod_rewrite kurallarının bulunması ve %s.htaccess adlı bir dosyanın olması gerekiyor.Çok fazla önbelleklenen sayfa var, listeleme yapılamaz.Son taksim (/ karakteri) kontrolü gerekli.AdresNe yazık ki WordPress, wp-cron.php dosyasını bulamadı. Bu dosya, çöp toplama, yazı zamanlama gibi işlevleri yerine getirmesi için şarttır.Ne yazık ki, WordPress MU ile çalışırken mod_rewrite kuralları otomatik olarak güncellenememektedir. Lütfen .htaccess dosyanızı açın ve aşağıdaki mod_rewrite kurallarını, diğer kuralların üstüne yerleştirin.Bu eklentiyi kaldır: Otomatik olarak kendi artıklarını temizler. Eğer elle müdahale gerektirirse, basit bir yönerge ile yol gösterir.GüncelleDirekt Sayfaları GüncelleMod_Rewrite Kurallarını GüncelleAyarları GüncelleDurumu GüncelleÖnbellek dosyalarını sunmak için PHP kullan.Önbellek dosyalarını sunmak için mod_rewrite kullan.Önbellek dosyalarını depolamak için "object cache"yi kullan.Mod_Rewrite Kurallarını GörüntüleWP Super Cache AyarlarıWP Super Cache anasayfanızı kontrol etti. Bu özelliği devre dışı bırakmak için lütfen %s ziyaret edin.WP Super Cache pasif durumda. Önbelleklemeye devam etmek için lütfen ayarlar sayfasına gidip etkinleştirin.%s.htaccess dosyanızda WP Super Cache'nin mod_rewrite kuralları saptandı.
    Aşağıdaki bağlantıya tıklayarak dosyaya hangi satırların eklendiğini görüntüleyebilirsiniz. Eğer eklentinin sürümünü güncellediyseniz, bu kuralların eklenip eklenmediğini kontrol etmelisiniz.WP Super Cache ayarları yapılmamış. Ayarlar sayfasına gidip ayarlarını yapmalısınız.WP-CacheWP-Super-CacheUyarıUyarı!Uyarı! %s yazılabilir!Uyarı! Sıkıştırma devre dışı ve gzencode() fonksiyonu bulunamadı.Uyarı! PHP Güvenli Mod (Safe Mode) Etkin!Uyarı! WP Super Cache önbellekleme bozuk! advanced-cache.php betiği wp-cache-phase1.php dosyasını yükleyemiyor.

    Lütfen %1$s/advanced-cache.php dosyasını düzenleyin ve %2$swp-cache-phase1.php yolunun doğru olduğundan emin olun.Warning! Your hostname "%s" resolves to %sWordPress MU SaptandıBlog'unuz tecrit moduna alındı. Yeni yorumlar gelse bile yalnızca Super Cache'nin önbellekli sayfaları görüntülenecek.Blog'unuz tecrit modunda değil. Yeni yorumlar her zamanki gibi Super Cache önbellek dosyalarını yenileyecek.Yazılabilir:Çok siteli bir yapıya sahipseniz, her site için farklı CDN adresleri verebilirsiniz.Dosyayı kendiniz düzenleyebilir ve aşağıdaki kuralları ekleyebilirsiniz.Kuralların nereye konacağını ve tüm kuralları, aşağıdaki "mod_rewrite kurallarını görüntüle" düğmesine tıklayarak görebilirsiniz.SAFE MODE açık olduğu için bu eklentiyi kullanırken sorunlarla karşılaşabilirsiniz.Kuralların otomatik olarak güncellenebilmesi için %s.htaccess dosyası içerisindeki kurallar BEGIN ve END yorum satırlarının arasında bulunmalıdır. Aşağıdaki gibi gözükürler ve WordPress'in kendi mod_rewrite kurallarının üstündedirler:Bu ayarı etkinleştirebilmeniz için %s yazılabilir olmalı. Güvenlik açısından sayfanız oluşturulduğunda lütfen yazma ayarlarını geri alın.Siz veya bir yönetici, eklenti betiklerini çalıştıran kullanıcıyı sunucu kullanıcısıyla aynı yaparak sorunu çözebilirsiniz. %s/cache/ dizininin grup sahibi de aynı şekilde değişmelidir. Güvenli Mod yardım sayfasına bakarak ayrıntılı bilgi edinebilirsiniz.Siz veya başka bir yönetici bunu etkisizleştirmeli. "güvenli mod" bilgilendirme sayfasına gidip ayrıntılı bilgi alabilirsiniz. Ne yazık ki, bu ayar .htaccess ile etkisizleştirilemez; php.ini ayar dosyasının düzenlenmesi gerekiyor.%s izinlerini düzenlemeli ve daha kısıtlayıcı hale getirmelisiniz. FTP istemcinizi kullanın veya aşağıdaki komutu uygulayın:%s.htaccess dosyanız sunucunuz tarafından düzenlenemiyor ama gerekli mod_rewrite kurallarının düzenlenmesi şart. Dosya içerisindeki normal WordPress kurallarının üstüne yazılması gereken kodlar şu şekilde:WP-Cache ayar dosyanız (%s) çok eski ve yenisi de sunucu tarafından oluşturulamıyor. Lütfen dosyayı silip bu sayfayı yenileyin.Önbellek dizininiz ($cache_path) bulunamadı ve sunucu tarafından da oluşturulamadı. %s dosya izinlerini kontrol edin.Önbellek dizininiz (%1$s) veya %2$s, eklentinin çalışabilmesi için yazılabilir olmalıdır. Lütfen tekrar kontrol edin.Yorumunuz onay bekliyor.Sunucunuz, dosya okuma/yazma işlemlerine izin verilmeden önce PHP betiğinin sahibini kontrol edecek şekilde ayarlanmış.Sunucunuz, hostname'inizin %s şeklinde çözümlendiğini sanıyor. Bu eklentinin çöp toplama gibi bazı işlevleri (ve WordPress'in yazı zamanlama işlevi) bu şekilde düzgün çalışmayabilir.Siteniz muhtemelen çok fazla statik dosya kullanıyordur. Görsel, JavaScript ve CSS dosyaları genellikle başka bir siteden veya bir CDN sisteminden kolayca sunabileceğiniz statik dosyalardır. Bu yüzden bu eklenti wp-content ve wp-includes dizinleri içerisindeki (PHP dosyaları haricindeki) tüm bağlantıları, aşağıda belirleyeceğiniz URL üzerinden sunacaktır. Bu şekilde tüm statik dosyalarınız sanal sunucunuza veya satın aldığınız CDN sistemine "origin pull" tekniğiyle aktarılacaktır.Zlib Çıktı Sıkıştırma Etkin![%1$s] %2$d yazı güncellendi[%1$s] Önbellek Önyükleme Başladı[%1$s] Önbellek Önyüklemesi Durduruldu[%1$s] %2$d ile %3$d arasındaki yazılar güncelleniyor[%s] Önbellek Önyüklemesi Tamamlandı[%s] Ön sayfa kontrolü![%s] Ön sayfa gzip'lendi, Önbellek Temizlendi![%s] Ön sayfa gzip'lendi, lütfen önbelleği boşaltın![%s] Ön sayfa doğru değil! Önbellek Temizlendi![%s] Ön sayfa doğru değil! Lütfen önbelleği temizleyin![%s] Önyükleme takılı kalmış olabilir.tümüektisizleştirilmişetkinsaniyelanguages/wp-super-cache-fr_FR.po000066600000223650152133035240012703 0ustar00msgid "" msgstr "" "Project-Id-Version: WP Super Cache fr\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2010-06-16 10:25+0000\n" "PO-Revision-Date: \n" "Last-Translator: Maître Mô \n" "Language-Team: Maître Mô \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Poedit-Language: French\n" "X-Poedit-Country: France\n" "X-Poedit-SourceCharset: utf-8\n" "X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;_n_noop:1,2;_c,_nc:4c,1,2;_x:1,2c;_ex:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2\n" "X-Poedit-Basepath: .\n" "X-Textdomain-Support: yes\n" "X-Poedit-SearchPath-0: .\n" #@ wp-super-cache #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "Bad Behaviour n'a pas été trouvé. Merci de vérifier votre installation." #@ wp-super-cache #: plugins/awaitingmoderation.php:23 #: plugins/awaitingmoderation.php:38 #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:47 #: plugins/domain-mapping.php:62 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1103 msgid "Disable" msgstr "Désactiver" #@ wp-super-cache #: plugins/awaitingmoderation.php:29 #: plugins/badbehaviour.php:55 #: plugins/domain-mapping.php:53 #: plugins/searchengine.php:67 msgid "disabled" msgstr "désactivé" #@ wp-super-cache #: plugins/awaitingmoderation.php:31 #: plugins/badbehaviour.php:57 #: plugins/domain-mapping.php:55 #: plugins/searchengine.php:69 #: wp-cache.php:1449 msgid "enabled" msgstr "activé" #@ wp-super-cache #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s." msgstr "Le support de Bad Behaviour est %s." #@ wp-super-cache #: plugins/awaitingmoderation.php:36 #: plugins/badbehaviour.php:63 #: plugins/domain-mapping.php:60 #: plugins/searchengine.php:74 #: wp-cache.php:1103 msgid "Enable" msgstr "Activer" #@ wp-super-cache #: plugins/badbehaviour.php:69 #: wp-cache.php:1180 #: wp-cache.php:1182 msgid "Warning!" msgstr "Attention!" #@ wp-super-cache #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s." msgstr "L'extension Pas de pub pour les amis est %s." #@ wp-super-cache #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(nécessite également friendsadverts.php) " #@ wp-super-cache #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Merci de créer %s /wp-cache-config.php à partir de wp-super-cache/wp-cache-config-sample.php" #@ wp-super-cache #: wp-cache.php:138 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Attention ! Le Mode Sécurité PHP est activé !" #@ wp-super-cache #: wp-cache.php:139 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Vous pourriez rencontrer certains problèmes en exécutant cette extension, car le Mode de Sécurité PHP est activés." #@ wp-super-cache #: wp-cache.php:143 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Votre serveur est configuré pour vérifier le propriétaire des scripts PHP avant de les autoriser à lire et écrire les fichiers." #@ wp-super-cache #: wp-cache.php:144 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Vous ou un administrateur pouvez être en mesure de le faire fonctionner en modifiant le groupe du propriétaire des scripts de l'extension pour le faire correspondre à celui de l'utilisateur du serveur web. Le groupe du propriétaire du répertoire de %s/cache/ doit également être modifié. Voir la page du manuel du Mode Sécurité pour plus de détails." #@ wp-super-cache #: wp-cache.php:146 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Vous ou un administrateur devez désactiver ceci. Voir la page du manuel du Mode Sécurité pour plus de détails. Ça ne peut malheureusement pas être désactivé dans un fichier .htaccess. Ça doit l'être dans le fichier de configuration php.ini." #@ wp-super-cache #: wp-cache.php:152 msgid "Permlink Structure Error" msgstr "Erreur de Structure des PermaLiens" #@ default #: wp-cache.php:153 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Une URL personnalisée ou une structure de permaliens est nécessaire pour que ce plugin fonctionne correctement. S’il vous plaît, aller sur la page Options permaliens pour configurer vos permaliens." #@ wp-super-cache #: wp-cache.php:516 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Le fichier de configuration a été modifié, certaines valeurs peuvent-être erronées. Rechargez la page depuis le menu \"Réglages\" pour les remettre à zéro." #@ wp-super-cache #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "Impossible de continuer... Résolvez les problèmes susmentionnés et réessayez." #@ wp-super-cache #: wp-cache.php:165 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Attention ! Votre nom de domaine \"%s\" se traduit par %s" #@ wp-super-cache #: wp-cache.php:166 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Votre serveur pense que votre nom de domaine se traduit en tant que %s. Certains services comme l'éboueur de cette extension, et la publication différée de WordPress, peuvent ne pas fonctionner correctement." #@ wp-super-cache #: wp-cache.php:167 #: wp-cache.php:181 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Veuillez lire l'entrée 16 de la section Troubleshooting (dysfonctionnements) du fichier readme.txt" #@ wp-super-cache #: wp-cache.php:180 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Malheureusement, WordPress n'arrive pas à trouver le fichier wp-cron.php. Ce script est requis pour un fonctionnement correct de l'éboueur de cette extension, ainsi d'ailleurs que de la publication différée de WordPress et d'autres fonctions critiques." #@ wp-super-cache #: wp-cache.php:204 msgid "Zlib Output Compression Enabled!" msgstr "Compression Zlib Output activée !" #@ wp-super-cache #: wp-cache.php:205 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP compresse les données envoyées aux visiteurs de votre site. Il est recommandé de désactiver ceci car l'extension met en cache la sortie compressée une seule fois, au lieu de compresser la même page encore et encore. Voir également le #21 dans la section Dépannage. Voir cette page pour obtenir des instructions pour la modification de votre fichier php.ini." #@ wp-super-cache #: wp-cache.php:209 msgid "Mod rewrite may not be installed!" msgstr "Le mode Réécriture ne doit pas être installé !" #@ wp-super-cache #: wp-cache.php:215 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Mode Lecture Seule. La configuration ne peut pas être modifiée." #@ wp-super-cache #: wp-cache.php:216 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Le fichier de configuration de WP Super Cache est %s/wp-cache-config.php et ne peut pas être modifié. Ce fichier doit pouvoir être écrit par votre serveur web pour effectuer des modifications." #@ wp-super-cache #: wp-cache.php:217 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Un moyen simple de faire ceci est de modifier temporairement les permissions en utilisant la commande CHMOD, ou via votre client FTP. Assurez-vous que l'ensemble peut être écrit, et cela devrait fonctionner." #@ wp-super-cache #: wp-cache.php:218 msgid "Writeable:" msgstr "Peut être écrit :" #@ wp-super-cache #: wp-cache.php:219 msgid "Readonly:" msgstr "Lecture Seule :" #@ wp-super-cache #: wp-cache.php:231 #, php-format msgid "Warning! %s is writeable!" msgstr "Attention ! %s peut être écrit !" #@ wp-super-cache #: wp-cache.php:232 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Vous devriez modifier les permissions sur %s et les rendre plus restrictives. Utilisez votre client FTP, ou la commande ci-dessous, pour résoudre ces choses :" #@ wp-super-cache #: wp-cache.php:406 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Attention ! Vous avez tenté d'activer la compression mais zlib.output_compression est activée. Voir le #21 dans la section Dépannage du fichier readme." #@ wp-super-cache #: wp-cache.php:793 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Annoncez fièrement au Monde que votre serveur est compatible avec Digg ! (affiche un message dans le pied-de-page de votre blog)" #@ wp-super-cache #: wp-cache.php:808 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Verrouillage Majeur de fichier. Vous n'avez probablement pas besoin de ça, mais ça peut aider si votre serveur est peu puissant. Attention ! Peut bloquer votre serveur dans de très rares cas !" #@ wp-super-cache #: wp-cache.php:803 msgid "Mobile device support." msgstr "Support des systèmes mobiles." #@ wp-super-cache #: wp-cache.php:240 msgid "Mobile rewrite rules detected" msgstr "Règles de réécriture pour mobiles détectées" #@ wp-super-cache #: wp-cache.php:241 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Pour des performances optimales, vous devriez activer le \"Support des systèmes de mobiles\" ou supprimer les règles de réécriture pour mobiles dans votre .htaccess. Localisez les 2 lignes avec le texte \"2.0\\ MMP|240x320\" et supprimez-les." #@ wp-super-cache #: wp-cache.php:241 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Cela n'affectera pas les utilisateurs ordinaires, mais les utilisateurs de mobiles verront des pages non mises en cache." #@ wp-super-cache #: wp-cache.php:247 #: wp-cache.php:258 msgid "Rewrite rules must be updated" msgstr "Les règles de Réécriture doivent être mises à jour" #@ wp-super-cache #: wp-cache.php:248 #: wp-cache.php:259 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Les règles de réécriture nécessitées par cette extension ont changé ou sont manquantes." #@ wp-super-cache #: wp-cache.php:252 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Supprimez les règles de Réécriture de l'extension dans %s.htaccess situées entre # BEGIN WPSuperCache et # END WPSuperCache et laissez laissez l'extension les régénérer en rechargeant cette page." #@ wp-super-cache #: wp-cache.php:253 #, php-format msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Ajoutez les règles vous-même. Éditez %s.htaccess et trouvez le bloc de code situé entre les lignes # BEGIN WPSuperCache et # END WPSuperCache. Il existe deux sections, qui se ressemblent beaucoup. Juste en dessous de la ligne %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$, ajoutez ces lignes (faites-le deux fois, une par section) :" #@ wp-super-cache #: wp-cache.php:811 msgid "Use object cache to store cached files." msgstr "Utilisez un objet mis en cache pour stocker les fichiers mis en cache." #@ wp-super-cache #: wp-cache.php:811 msgid "(Experimental)" msgstr "(Expérimental)" #@ wp-super-cache #: wp-cache.php:805 msgid "Only refresh current page when comments made." msgstr "Rafraîchir uniquement la page courante lorsqu'un commentaire est effectué." #@ wp-super-cache #: wp-cache.php:818 msgid "Note:" msgstr "Note :" #@ wp-super-cache #: wp-cache.php:820 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Si vous désinstallez cette extension, assurez-vous que le répertoire %s peut être écrit par le serveur Web, de façon que les fichiers advanced-cache.php et cache-config.php puissent être automatiquement détruits. (S'assurer que ces fichiers peuvent également être écrits est probablement une bonne idée !)" #@ wp-super-cache #: wp-cache.php:821 #, php-format msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Merci de lire le fichier readme.txt pour les instructions relatives à la désinstallation de ce script. Cherchez le titre \"How to uninstall WP Super Cache\"(\\\"Comment désinstaller WP Super Cache\\\" -en anglais)." #@ wp-super-cache #: wp-cache.php:822 #, php-format msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Besoin d'aide ? Lisez le fichier readme de Super Cache. Il inclut une documentation pour l'installation, une FAQ, et des conseils de dépannage. Le forum de support est également disponible. Il a peut-être déjà été répondu à votre question." #@ wp-super-cache #: wp-cache.php:825 #: wp-cache.php:872 msgid "Update Status" msgstr "Mettre à jour les Statuts" #@ wp-super-cache #: wp-cache.php:535 msgid "Cache Tester" msgstr "Testeur du Cache" #@ wp-super-cache #: wp-cache.php:536 msgid "Test your cached website by clicking the test button below." msgstr "Testez votre site web mis en cache en cliquant sur le bouton de test ci-dessous." #@ wp-super-cache #: wp-cache.php:543 #, php-format msgid "Fetching %s to prime cache: " msgstr "Récupération de %s pour la première mise en cache." #@ wp-super-cache #: wp-cache.php:545 #: wp-cache.php:552 #: wp-cache.php:559 msgid "OK" msgstr "OK" #@ wp-super-cache #: wp-cache.php:550 #, php-format msgid "Fetching first copy of %s: " msgstr "Récupération de la première copie de %s :" #@ wp-super-cache #: wp-cache.php:557 #, php-format msgid "Fetching second copy of %s: " msgstr "Récupération de la deuxième copie de %s :" #@ wp-super-cache #: wp-cache.php:589 #, php-format msgid "Page 1: %s" msgstr "Page 1 : %s" #@ wp-super-cache #: wp-cache.php:590 #, php-format msgid "Page 2: %s" msgstr "Page 2 : %s" #@ wp-super-cache #: wp-cache.php:591 msgid "The timestamps on both pages match!" msgstr "Les horodateurs des deux pages correspondent !" #@ wp-super-cache #: wp-cache.php:593 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Les pages ne correspondent pas ! Les horodateurs sont différents ou n'ont pas été trouvés !" #@ wp-super-cache #: wp-cache.php:600 msgid "Test Cache" msgstr "Test du Cache" #@ wp-super-cache #: wp-cache.php:625 #: wp-cache.php:748 msgid "Cancel Cache Preload" msgstr "Annuler le Préchargement du Cache" #@ wp-super-cache #: wp-cache.php:631 msgid "Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete." msgstr "Préchargement programmé du cache annulé. Si un travail est actuellement en cours, il ne s'arrêtera pas jusqu'à ce que les 100 pages en cours soit terminées." #@ wp-super-cache #: wp-cache.php:642 msgid "Scheduled preloading of cache cancelled." msgstr "Préchargement programmé du cache annulé." #@ wp-super-cache #: wp-cache.php:668 #: wp-cache.php:746 msgid "Preload Cache Now" msgstr "Précharger le Cache Maintenant" #@ default #: wp-cache.php:671 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Préchargement programmé du cache dans 10 secondes." #@ wp-super-cache #: wp-cache.php:675 #, php-format msgid "Scheduled preloading of cache in %d minutes" msgstr "Préchargement programmé du cache dans %d minutes" #@ wp-super-cache #: wp-cache.php:679 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Ceci mettra en cache tous les articles et pages publiés sur votre site. Ça créera des fichiers statiques SuperCache de façon que les visiteurs inconnus (y compris les robots) reçoivent une page mise en cache. Ce qui améliorera probablement votre classement Google, du fait qu'il utilise désormais la vitesse dans ses mesures pour classer les sites Web." #@ wp-super-cache #: wp-cache.php:680 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Le préchargement crée cependant un nombre important de fichiers. La mise en cache est effectuée des articles les plus récents au plus anciens, donc merci d'envisager de ne mettre en cache que les plus récents, si vous avez un nombre important (10.000 +) d'articles. Ceci est spécialement important pour les hébergements mutualisés." #@ wp-super-cache #: wp-cache.php:685 #, php-format msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Rafraîchir les fichiers de préchargement du cache toutes les %s minutes. (0 pour désactiver, au minimum %d minutes.)" #@ wp-super-cache #: wp-cache.php:698 msgid "all" msgstr "tous" #@ wp-super-cache #: wp-cache.php:711 #, php-format msgid "Preload %s posts." msgstr "Précharger %s articles." #@ wp-super-cache #: wp-cache.php:721 msgid "Send me status emails when files are refreshed." msgstr "M'envoyer un mail d'état de statuts lorsque les fichiers sont rafraîchis." #@ default #: wp-cache.php:726 msgid "Many emails, 2 emails per 100 posts." msgstr "De nombreux e-mails, 2 e-mails pour 100 commentaires." #@ default #: wp-cache.php:729 msgid "Medium, 1 email per 100 posts." msgstr "Moyen, 1 e-mail pour 100 commentaires." #@ wp-super-cache #: wp-cache.php:732 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Moins de mails, 1 au début et 1 à la fin du préchargement de tous les articles." #@ wp-super-cache #: wp-cache.php:743 #, php-format msgid "Currently caching from post %d to %d." msgstr "Mise en cache actuelle des articles de %d à %d." #@ wp-super-cache #: wp-cache.php:746 msgid "Update Settings" msgstr "Mettre à jour les Réglages" #@ wp-super-cache #: wp-cache.php:266 msgid "Required to serve compressed supercache files properly." msgstr "Requis pour servir les fichier compressés Supercache proprement." #@ wp-super-cache #: wp-cache.php:266 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Requis pour attacher les informations de mise en cache aux pages SuperCache. Les utilisateurs d'IE7 ne verront que les anciennes pages sans ce module." #@ wp-super-cache #: wp-cache.php:266 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Règle la date d'expiration sur les pages mises en cache par Supercache. Les visiteurs ne pourront pas voir les nouvelles pages lorsqu'ils rafraîchiront, ou lorsqu'ils laisseront des commentaires, sans ce module." #@ wp-super-cache #: wp-cache.php:273 msgid "Missing Apache Modules" msgstr "Modules Apache manquants" #@ wp-super-cache #: wp-cache.php:881 msgid "Make WordPress Faster" msgstr "Accélérez WordPress" #@ wp-super-cache #: wp-cache.php:882 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s est maintenu et développé par %2$s avec les contributions de beaucoup d'autres personnes." #@ wp-super-cache #: wp-cache.php:884 #, php-format msgid "Please say hi to him on %s too!" msgstr "Merci de lui adresser aussi un petit \"salut !\" sur %s !" #@ wp-super-cache #: wp-cache.php:892 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Pages mise en cache depuis %1$s : %2$s" #@ wp-super-cache #: wp-cache.php:893 msgid "Newest Cached Pages:" msgstr "Plus Récentes Pages Mises en Cache :" #@ wp-super-cache #: wp-cache.php:897 #, php-format msgid "Cached %s seconds ago" msgstr "Mise en cache il y a %s secondes" #@ wp-super-cache #: wp-cache.php:900 msgid "(may not always be accurate on busy sites)" msgstr "(peut ne pas être toujours exact sur des sites fort occupés)" #@ wp-super-cache #: wp-cache.php:832 msgid "Accepted Filenames & Rejected URIs" msgstr "Noms de fichiers acceptés & URIs rejetées" #@ wp-super-cache #: wp-cache.php:1090 msgid "Enabled" msgstr "Activé" #@ wp-super-cache #: wp-cache.php:1090 msgid "Disabled" msgstr "Désactivé" #@ wp-super-cache #: wp-cache.php:985 msgid "Mod Rewrite Rules" msgstr "Règles du Mode Réécriture" #@ wp-super-cache #: wp-cache.php:991 msgid "WordPress MU Detected" msgstr "WordPress MU Détecté" #@ wp-super-cache #: wp-cache.php:991 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Malheureusement, les règles de réécriture ne peuvent pas être mises à jour automatiquement lorsque WordPress MU s'exécute. Merci d'ouvrir votre fichier .htaccess et d'y ajouter les règles de Mode Réécriture suivantes, au-dessus de toutes les autres règles de ce fichier." #@ wp-super-cache #: wp-cache.php:993 msgid "Mod Rewrite rules cannot be updated!" msgstr "Les règles du Mode Réécriture ne peuvent pas être mises à jour !" #@ wp-super-cache #: wp-cache.php:994 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Vous devez avoir les marqueurs BEGIN et END dans %s.htaccess pour que la mise à jour automatique fonctionne. Ils ressemblent à ceci, et entourent les règles principales du mode réécriture de WordPress :" #@ wp-super-cache #: wp-cache.php:996 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Rafraichissez cette page après avoir mis à jour votre fichier .htaccess." #@ wp-super-cache #: wp-cache.php:1000 msgid "Thank you for upgrading." msgstr "Merci d'avoir effectué la mise à jour." #@ wp-super-cache #: wp-cache.php:1000 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Les règles du Mode Réécriture ont changé depuis votre dernère installation de cette extension. Malheureusement, vous devez supprimer les anciennes règles de SuperCache avant que les nouvelles soient mises à jour. Rafraîchissez cette page après avoir édité votre fichier .htaccess. Si vous souhaitez mettre à jour manuellement, modifiez la ligne suivante : %1$s de façon qu'elle ressemble à ceci : %2$s. Les seuls changements sont \"HTTP_COOKIE\", devenant \"HTTP:Cookie\", et \"wordpressuser \", devenant \"wordpress\". C'est une modification de WordPress 2.5, mais il est rétrocompatible avec les anciennes versions, si vous êtes assez courageux pour utiliser celles-ci." #@ wp-super-cache #: wp-cache.php:1004 msgid "Trailing slash check required." msgstr "Le slash final est requis." #@ wp-super-cache #: wp-cache.php:1004 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Il semble que votre blog possède des URLs qui se terminent par un \"/\". Malheureusement, depuis que vous avez installé cette extension, un bug de duplicate content a été découvert, dans lequel les URLs ne se terminant pas par un \"/\" servent le même contenu que celles finissant par le \"/\", et ne redirigent pas vers la bonne URL. Pour le résoudre, vous devez éditer votre fichier .htaccess et ajouter ces deux règles aux deux groupes de règles de Super Cache :" #@ wp-super-cache #: wp-cache.php:1006 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Vous pouvez aller regarder là où sont les règles et examiner les règles complètes en cliquant sur le lien \"Voir les règles du Mode Réécriture\" ci-dessous." #@ wp-super-cache #: wp-cache.php:1020 msgid "Mod Rewrite rules updated!" msgstr "Règles du Mode Réécriture mises à jour !" #@ wp-super-cache #: wp-cache.php:1021 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "Le fichier %s.htaccess a été mis à jour avec les règles de Mode Réécriture nécessaires. Merci de vérifier qu'elles sont correctes. Elles devraient ressembler à ceci :" #@ wp-super-cache #: wp-cache.php:1023 msgid "Mod Rewrite rules must be updated!" msgstr "Les règles du Mode Réécriture doivent être mises à jour !" #@ wp-super-cache #: wp-cache.php:1024 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Votre fichier %s.htaccess ne peut pas être écrit par le serveur Web et doivent être mises à jour avec les règles du Mode Réécriture nécessaires. Les nouvelles règles se placent au-dessus des règles standard de WordPress comme montré dans le code suivant :" #@ wp-super-cache #: wp-cache.php:1029 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Les règles du Mode Réécriture de WP Super Cache ont été détectées dans votre fichier %s.htaccess.
    Cliquez sur le lien ci-dessous pour voir les lignes ajoutées à ce fichier. Si vous avez mis à jour l'extension, assurez-vous que ces règles correspondent." #@ wp-super-cache #: wp-cache.php:1032 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "Une différence entre les règles dans votre fichier .htaccess et celles de réécriture dans l'extension a été découverte. Il peut ne s'agir que d'une différence d'espace blanc, mais vous devriez comparer les règles du fichier avec celles ci-dessous aussi vite que possible. Cliquez sur le bouton ’Actualiser les Règles du Mode Réécriture’ pour mettre à jour les règles." #@ wp-super-cache #: wp-cache.php:1035 msgid "View Mod_Rewrite Rules" msgstr "Voir les règles du Mode Réécriture" #@ wp-super-cache #: wp-cache.php:1039 #: wp-cache.php:2276 #, php-format msgid "Rules must be added to %s too:" msgstr "Les règles. doivent également être ajoutées à %s :" #@ wp-super-cache #: wp-cache.php:1047 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Règles d'encodage Gzip dans %s.htaccess créées. " #@ wp-super-cache #: wp-cache.php:1054 msgid "Fix Configuration" msgstr "Correction de la Configuration" #@ wp-super-cache #: wp-cache.php:1057 msgid "Restore Default Configuration" msgstr "Restaurer la Configuration par Défaut" #@ wp-super-cache #: wp-cache.php:1065 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "La modération des commentaires est activée. Votre commentaire peut prendre un certain temps avant d'apparaître." #@ wp-super-cache #: wp-cache.php:1090 msgid "Lock Down:" msgstr "Verrouillage :" #@ wp-super-cache #: wp-cache.php:1091 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Prépare votre serveur pour un pic de trafic attendu en activant le mode de verrouillage. Lorsqu'il est activé, les nouveaux commentaires sur un article ne rafraîchissent pas les fichiers statiques du cache." #@ wp-super-cache #: wp-cache.php:1092 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Développeurs : Rendez vos extensions compatibles avec le mode Verrouillage en vérifiant la constante \"WPLOCKDOWN\". Le code suivant vous assurera que votre extension respecte les réglages de WPLOCKDOWN." #@ wp-super-cache #: wp-cache.php:1094 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Désolé. Mon blog est verrouillé. Les mises à jours vont apparaître rapidement." #@ wp-super-cache #: wp-cache.php:1098 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress est verrouillé. Les fichiers statiques Super Cache ne seront pas supprimés lorsque de nouveaux commentaires sont effectués." #@ wp-super-cache #: wp-cache.php:1100 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress n'est pas verrouillé. Les nouveaux commentaires rafraîchiront normalement les fichier statiques Super Cache." #@ wp-super-cache #: wp-cache.php:1106 msgid "Lock Down" msgstr "Verrouillage" #@ wp-super-cache #: wp-cache.php:1114 msgid "Directly Cached Files" msgstr "Fichiers Directement Mis en Cache" #@ wp-super-cache #: wp-cache.php:1172 #, php-format msgid "%s removed!" msgstr "%s supprimé !" #@ wp-super-cache #: wp-cache.php:1180 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Vous devez rendre %s apte à être écrit pour activer cette fonction. Comme il s'agit d'un risque de sécurité, veuillez le remettre en mode lecture seule après que votre page ait été générée." #@ wp-super-cache #: wp-cache.php:1182 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s peut être écrit. Merci de le remettre en mode lecture seule après que votre page ait été générée, dans la mesure où il s'agit d'un risque de sécurité." #@ wp-super-cache #: wp-cache.php:1196 msgid "Existing direct page" msgstr "Page directe existante" #@ wp-super-cache #: wp-cache.php:1196 msgid "Delete cached file" msgstr "Suppression de fichier mis en cache" #@ wp-super-cache #: wp-cache.php:1201 msgid "Add direct page:" msgstr "Ajouter une page directe :" #@ wp-super-cache #: wp-cache.php:1203 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Les fichiers directement mis en cache sont des fichiers créés directement à partir de %s, où se trouve votre blog. Cette fonction n'est utile que si vous vous attendez à un niveau de trafic majeur de Digg ou Slashdot sur un article ou une page." #@ wp-super-cache #: wp-cache.php:1205 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Par exemple: pour mettre en cache %1$sabout/, vous entrez %1$sabout/ ou /about/. Le fichier de cache sera généré à la prochaine visite d'un utilisateur anonyme sur cette page." #@ wp-super-cache #: wp-cache.php:1206 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Laissez en blanc la zone de texte pour la supprimer de la liste des pages directes et supprimer le fichier mis en cache." #@ wp-super-cache #: wp-cache.php:1211 msgid "Update Direct Pages" msgstr "Mettre à jour les Pages Directes" #@ wp-super-cache #: wp-cache.php:1249 msgid "Expiry Time & Garbage Collection" msgstr "Date d'Expiration & Éboueur" #@ wp-super-cache #: wp-cache.php:1251 msgid "Expire time:" msgstr "Date d'expiration :" #@ wp-super-cache #: wp-cache.php:1252 msgid "seconds" msgstr "secondes" #@ wp-super-cache #: wp-cache.php:1253 msgid "Garbage Collection" msgstr "Éboueur" #@ wp-super-cache #: wp-cache.php:1255 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Réglez le délai d'expiration à 0 secondes pour désactiver l'éboueur." #@ wp-super-cache #: wp-cache.php:1256 msgid "Change Expiration" msgstr "Modifier le Délai d'Expiration" #@ wp-super-cache #: wp-cache.php:1300 msgid "Rejected User Agents" msgstr "User Agents rejetés" #@ wp-super-cache #: wp-cache.php:1301 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Chaines de caractères dans l'en-tête HTTP ’User Agents’ qui empêchent WP-Cache de mette en cache les requêtes des robots, spiders et crawlers’. Notez que les fichiers mis en cache par SuperCache sont encore envoyés à ces agents s'ils existent toujours." #@ wp-super-cache #: wp-cache.php:1308 msgid "Save UA Strings" msgstr "Sauvegarder les Listes d'User Agents" #@ wp-super-cache #: wp-cache.php:1331 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Ne pas mettre en cache les types de page suivants. Voir la documentation Marqueurs Conditionnelspour un exposé complet sur chaque type." #@ wp-super-cache #: wp-cache.php:1334 msgid "Single Posts" msgstr "Articles Simples" #@ wp-super-cache #: wp-cache.php:1335 msgid "Pages" msgstr "Pages" #@ wp-super-cache #: wp-cache.php:1336 msgid "Front Page" msgstr "Page de Garde" #@ wp-super-cache #: wp-cache.php:1337 msgid "Home" msgstr "Accueil" #@ wp-super-cache #: wp-cache.php:1338 msgid "Archives" msgstr "Archives" #@ wp-super-cache #: wp-cache.php:1339 msgid "Tags" msgstr "Tags" #@ wp-super-cache #: wp-cache.php:1340 msgid "Category" msgstr "Catégories" #@ wp-super-cache #: wp-cache.php:1341 msgid "Feeds" msgstr "Flux" #@ wp-super-cache #: wp-cache.php:1342 msgid "Search Pages" msgstr "Page de Recherche" #@ default #@ wp-super-cache #: wp-cache.php:1344 #: wp-cache.php:1472 msgid "Save" msgstr "Sauvegarder" #@ wp-super-cache #: wp-cache.php:1361 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Ajoutez ici les chaînes (pas un nom de fichier) qui forcent une page à ne pas être mise en cache. Par exemple, si vos URLs incluent l'année et que vous ne voulez pas mettre en cache les articles de l'année dernière, il suffit de préciser l'année, c-à-d ’/2004/’. WP-Cache recherchera si cette chaîne fait partie de l'URI et dans l'affirmative, ne mettra pas cette page en cache." #@ wp-super-cache #: wp-cache.php:1367 msgid "Save Strings" msgstr "Sauvegarder les Chaînes" #@ wp-super-cache #: wp-cache.php:1383 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Ajouter ici les noms des fichiers qui peuvent être mis en cache, même s'ils correspondent à l'une des sous-chaînes rejetées spécifiées ci-dessus." #@ wp-super-cache #: wp-cache.php:1389 msgid "Save Files" msgstr "Sauvegarder les Fichiers" #@ wp-super-cache #: wp-cache.php:1434 msgid "Currently logging to: " msgstr "Actuellement connecté à :" #@ wp-super-cache #: wp-cache.php:1444 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Résout les problèmes de l'extension en la déboguant ici. Peut vous adresser des mails de débogage ou les enregistrer dans un fichier de votre répertoire de cache." #@ wp-super-cache #: wp-cache.php:1445 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Se connecter à un fichier est plus facile, mais se heurte au problème qu'effacer le cache effacera le fichier des enregistrements." #@ wp-super-cache #: wp-cache.php:1449 msgid "Debugging" msgstr "Débogage" #@ wp-super-cache #: wp-cache.php:1450 msgid "Logging Type" msgstr "Type d'Enregistrement" #@ wp-super-cache #: wp-cache.php:1450 msgid "Email" msgstr "Mail" #@ wp-super-cache #: wp-cache.php:1451 msgid "file" msgstr "fichier" #@ wp-super-cache #: wp-cache.php:1452 msgid "IP Address" msgstr "Adresse IP" #@ wp-super-cache #: wp-cache.php:1452 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(N'enregistrer que les requêtes de cette adresse IP. Votre IP est %s)" #@ wp-super-cache #: wp-cache.php:1453 msgid "Log level" msgstr "Niveau d'enregistrement" #@ wp-super-cache #: wp-cache.php:1459 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = le plus bas, 5 = le plus haut, peut sévèrement surcharger le serveur.)" #@ wp-super-cache #: wp-cache.php:799 #: wp-cache.php:946 #: wp-cache.php:1462 msgid "Advanced" msgstr "Avancé" #@ wp-super-cache #: wp-cache.php:1462 #, php-format msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "Dans de très rares cas, deux problèmes peuvent survenir sur certains blogs:
    1. La page de garde peut commencer à se télécharger comme un fichier zip.
    2. Une mauvaise page est parfois mise en cache en tant que page de garde si votre blog utilise une page de garde statique et que la structure des permaliens est /%category%/%postname%/.
    " #@ wp-super-cache #: wp-cache.php:1463 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "Je suis certain à 99% qu'il ne s''agit pas de bugs de WP Super Cache et qu'ils ne surviennent que très rarement, mais vous pouvez exécuter une vérification simple, une fois toutes les 5 minutes, pour vérifier que votre site est OK, si vous avez peur. Vous recevrez un mail s'il survient un problème." #@ wp-super-cache #: wp-cache.php:1465 msgid "Check front page every 5 minutes." msgstr "Vérifier la page de garde toute les 5 minutes." #@ wp-super-cache #: wp-cache.php:1466 msgid "Front page text" msgstr "Texte de la page de garde" #@ wp-super-cache #: wp-cache.php:1466 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Texte à rechercher sur votre page de garde. Si ce texte est manquant, le cache sera effacé. Laissez en blanc pour désactiver." #@ wp-super-cache #: wp-cache.php:1467 msgid "Clear cache on error." msgstr "Effacer le cache en cas d'erreur." #@ wp-super-cache #: wp-cache.php:1468 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Envoi d'un mai à l'administrateur du blog lorsque les contrôles sont effectués. (Utile pour le test)" #@ wp-super-cache #: wp-cache.php:1482 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Erreur : la compression GZIP est activée, la désactiver si vous souhaitez activer wp-cache." #@ wp-super-cache #: wp-cache.php:1529 #: wp-cache.php:1691 msgid "Warning" msgstr "Attention" #@ wp-super-cache #: wp-cache.php:1529 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "La compression GZIP est activée dans WordPress, wp-cache sera outrepassé jusqu'à ce que vous la désactiviez." #@ wp-super-cache #: wp-cache.php:1587 #: wp-cache.php:1592 #: wp-cache.php:1624 #: wp-cache.php:1629 #: wp-cache.php:1635 msgid "Error" msgstr "Erreur" #@ wp-super-cache #: wp-cache.php:1587 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Votre répertoire de cache ($cache_path) n'existe pas et n'a pas pu être créé par le serveur web. Vérifiez les permissions %s." #@ wp-super-cache #: wp-cache.php:1592 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Votre répertoire de cache (%1$s) ou %2$s) doit pouvoir être écrit pour que cette extension fonctionne. Vérifiez doublement." #@ wp-super-cache #: wp-cache.php:1624 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Votre fichier de configuration WP-Cache (%s) est obsolète et ne peut pas être écrit par le serveur Web. Veuillez le détruire et rafraîchir cette page." #@ wp-super-cache #: wp-cache.php:1629 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Le fichier de configuration est manquant et le répertoire %1$s (%2$s) ne peut pas être écrit par le serveur Web. Vérifiez ses permissions." #@ wp-super-cache #: wp-cache.php:1635 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Le fichier d'exemple de configuration de WP-Cache (%s) n'existe pas. Vérifiez votre installation." #@ wp-super-cache #: wp-cache.php:1691 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php n'existe pas ou ne peut pas être mis à jour." #@ wp-super-cache #: wp-cache.php:1692 msgid "1. If it already exists please delete the file first." msgstr "1. S'il existe déjà, veuillez supprimer le fichier d'abord." #@ wp-super-cache #: wp-cache.php:1693 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Permettez à %1$s d'être écrit en utilisant la commande chmod via votre logiciel ftp ou serveur. (chmod 777 %1$s) et rafraîchissez cette page. Il ne s'agit que d'une mesure temporaire, et vous devrez le repasser en lecture seule ensuite. (Passez de 777 à 755 dans la commande précitée)" #@ wp-super-cache #: wp-cache.php:1694 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Rafraîchissez cette page pour mettre à jour %s/advanced-cache.php" #@ wp-super-cache #: wp-cache.php:1695 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Si ça ne fonctionnait pas, assurez vous que le fichier %s/advanced-cache.php n'existe pas :" #@ wp-super-cache #: wp-cache.php:1696 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Ouvrez le fichier %1$s$wp_cache_file dans un éditeur de texte.
  • 2. Remplacez le texte CACHEHOME par %2$s
  • 3. Sauvegardez le fichier et copiez-le dans %3$s, puis rafraîchissez cette page.
    • " #@ wp-super-cache #: wp-cache.php:1721 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Erreur : WP_CACHE n'est pas activé dans votre fichier wp-config.php et je ne peux pas le modifier." #@ wp-super-cache #: wp-cache.php:1726 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    Constante WP_CACHE ajoutée à wp-config.php

    Si vous continuez à voir s'afficher ce message d'avertissement, merci de lire le point 5 de laFAQ. La ligne WP_CACHE doit être déplacée." #@ wp-super-cache #: wp-cache.php:1748 msgid "Cache Contents" msgstr "Contenus du Cache" #@ wp-super-cache #: wp-cache.php:1751 msgid "Object cache in use. No cache listing available." msgstr "Objet du cache en cours d'utilisation. Pas de liste de cache disponible." #@ wp-super-cache #: wp-cache.php:1775 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Suppression du fichier supercache : %s
    " #@ wp-super-cache #: wp-cache.php:1792 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Suppression du fichier wp-cache : %s
    " #@ wp-super-cache #: wp-cache.php:1857 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Les statistiques de mise en cache ne sont pas générées automatiquement. Vous devez cliquer sur le lien ci-dessous pour régénérer les statistiques sur cette page." #@ default #: wp-cache.php:1858 msgid "Regenerate cache stats" msgstr "Regénérer les statistiques du cache" #@ wp-super-cache #: wp-cache.php:1860 #, php-format msgid "Cache stats last generated: %s minutes ago." msgstr "Dernière statistiques de mise en cache générées il y a %s minutes." #@ wp-super-cache #: wp-cache.php:1866 msgid "WP-Cache" msgstr "WP-Cache" #@ wp-super-cache #: wp-cache.php:1867 #: wp-cache.php:1883 #, php-format msgid "%s Cached Pages" msgstr "%s Pages Mises en Cache" #@ wp-super-cache #: wp-cache.php:1868 #: wp-cache.php:1888 #, php-format msgid "%s Expired Pages" msgstr "%s Pages Expirées" #@ wp-super-cache #: wp-cache.php:1882 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #@ wp-super-cache #: wp-cache.php:1893 msgid "Fresh WP-Cached Files" msgstr "Fichiers Récemment Mis en Cache par WP-Cache" #@ wp-super-cache #: wp-cache.php:1894 #: wp-cache.php:1910 #: wp-cache.php:1926 #: wp-cache.php:1942 msgid "URI" msgstr "URI" #@ wp-super-cache #: wp-cache.php:1894 #: wp-cache.php:1910 msgid "Key" msgstr "Clé" #@ wp-super-cache #: wp-cache.php:1894 #: wp-cache.php:1910 #: wp-cache.php:1926 #: wp-cache.php:1942 msgid "Age" msgstr "Âge" #@ wp-super-cache #: wp-cache.php:1894 #: wp-cache.php:1910 #: wp-cache.php:1926 #: wp-cache.php:1942 msgid "Delete" msgstr "Supprimer" #@ wp-super-cache #: wp-cache.php:1909 msgid "Stale WP-Cached Files" msgstr "Fichiers Périmés mis en cache par WP-Cache" #@ wp-super-cache #: wp-cache.php:1925 msgid "Fresh Super Cached Files" msgstr "Fichiers Récemment Mis en Cache par Super Cache" #@ wp-super-cache #: wp-cache.php:1941 msgid "Stale Super Cached Files" msgstr "Vieux Fichiers Mis en Cache par Super Cache" #@ wp-super-cache #: wp-cache.php:1957 msgid "Hide file list" msgstr "Masquer la liste des fichiers" #@ wp-super-cache #: wp-cache.php:1959 msgid "Too many cached files, no listing possible." msgstr "Trop de fichiers mis en cache, pas de liste possible." #@ wp-super-cache #: wp-cache.php:1967 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Éboueur
    Le dernier éboueur est passé il y a %s minutes
    " #@ wp-super-cache #: wp-cache.php:1968 #, php-format msgid "Next GC in %s minutes" msgstr "Le prochain éboueur passera dans %s minutes" #@ wp-super-cache #: wp-cache.php:1971 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Les fichiers périmés sont ceux remontant à plus de %s secondes. Ils sont encore utilisés par l'extension et sont détruits périodiquement." #@ wp-super-cache #: wp-cache.php:1982 msgid "Delete Expired" msgstr "Supprimer les Fichiers Périmés " #@ wp-super-cache #: wp-cache.php:1988 #: wp-cache.php:2000 #: wp-cache.php:2163 msgid "Delete Cache" msgstr "Supprimer le Cache" #@ wp-super-cache #: wp-cache.php:2000 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Supprimer les fichiers mis en cache par Super Cache (s'ouvre dans une nouvelle fenêtre)" #@ wp-super-cache #: wp-cache.php:2139 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s est compatible avec Digg grâce à la mise en cache par %2$s" #@ default #: wp-cache.php:2172 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache doit être configuré. Allez sur La page d’administration pour activer et configurer le plugin." #@ default #: wp-cache.php:2178 msgid "Settings" msgstr "Options" #@ wp-super-cache #: wp-cache.php:2188 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache est désactivé. Merci de vous rendre sur la page d'administration de l'extension pour activer la mise en cache." #@ wp-super-cache #: wp-cache.php:2207 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] La page de garde est \\\"gzipée\\\" ! Merci d'effacer le cache !" #@ wp-super-cache #: wp-cache.php:2207 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Merci de visiter %s pour effacer le cache, car la page de garde de votre site est en cours de téléchargement !" #@ wp-super-cache #: wp-cache.php:2210 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] La page de garde est \\\"gzippée\\\" ! Cache effacé !" #@ wp-super-cache #: wp-cache.php:2210 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Le cache de votre blog a été effacé car la page de garde de votre site est en cours de téléchargement. Merci de visiter %s pour vérifier que le cache a bien été effacé." #@ wp-super-cache #: wp-cache.php:2217 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] La page de garde n'est pas correcte ! Merci d'effacer le cache !" #@ wp-super-cache #: wp-cache.php:2217 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Merci de visiter %1$s pour effacer le cache, car la page de garde de votre site n'est pas correcte et il y manque le texte , \"%2$s\" !" #@ wp-super-cache #: wp-cache.php:2220 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] La page de garde n'est pas correcte ! Cache effacé !" #@ wp-super-cache #: wp-cache.php:2220 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Le cache de votre blog a été effacé parce qu'il manque le texte \"%2$s\" à la page de garde de votre site. Merci de visiter %1$s pour vérifier le bon effacement du cache." #@ wp-super-cache #: wp-cache.php:2225 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Vérification de la Page de garde !" #@ wp-super-cache #: wp-cache.php:2225 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache a vérifié la page de garde de votre blog. Merci de visiter %s si vous souhaitez désactiver ceci." #@ wp-super-cache #: wp-cache.php:2268 msgid "Cannot update .htaccess" msgstr "Impossible de mettre à jour le fichier .htaccess" #@ wp-super-cache #: wp-cache.php:2268 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Le fichier %s.htaccess ne peut pas être modifié par le serveur web. Merci de corriger ça en utilisant la commande chmod ou votre client ftp." #@ default #: wp-cache.php:2268 msgid "Refresh this page when the file permissions have been modified." msgstr "Rafraîchissez cette page lorsque les autorisations de fichiers auront été modifiées." #@ wp-super-cache #: wp-cache.php:2268 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Alternativement, vous pouvez éditer votre fichier %s.htaccess manuellement et y ajouter le code suivant (devant toute règle WordPress) :" #@ wp-super-cache #: wp-cache.php:2272 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Pour servir les fichiers HTML statiques, votre serveur doit avoir les règles de mode de réécriture correctes ajoutées à un fichier nommé %s.htaccess" #@ wp-super-cache #: wp-cache.php:2273 msgid "You can edit the file yourself add the following rules." msgstr "Vous pouvez éditer vous-même le fichier pour y ajouter les règles suivantes." #@ wp-super-cache #: wp-cache.php:2274 msgid " Make sure they appear before any existing WordPress rules. " msgstr "Assurez-vous qu'elles apparaissent avant les règles existantes WordPress. " #@ wp-super-cache #: wp-cache.php:2282 msgid "Update Mod_Rewrite Rules" msgstr "Mettre à jour les Règles du Mode Réécriture" #@ wp-super-cache #: wp-cache.php:2378 #, php-format msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Préchargement du Cache Démarré" #@ wp-super-cache #: wp-cache.php:2380 #, php-format msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Rafraîchissement des articles de %2$d à %3$d." #@ wp-super-cache #: wp-cache.php:2391 #, php-format msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d articles rafraîchis" #@ wp-super-cache #: wp-cache.php:2391 msgid "Refreshed the following posts:" msgstr "Rafraîchissement des articles suivants :" #@ wp-super-cache #: wp-cache.php:2400 #, php-format msgid "Scheduling next preload refresh in %d minutes." msgstr "Prochain rafraîchissement de préchargement programmé dans %d minutes." #@ wp-super-cache #: wp-cache.php:2410 #, php-format msgid "[%s] Cache Preload Completed" msgstr "[%s] Préchargement du Cache Terminé" #@ wp-super-cache #: wp-cache.php:2410 msgid "Cleaning up old supercache files." msgstr "Nettoyage des anciens fichiers supercache." #@ default #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Votre commentaire est en attente de modération." #@ wp-super-cache #: plugins/awaitingmoderation.php:33 #, php-format msgid "Awaiting Moderation plugin is %s" msgstr "L'extension Awaiting Moderation est %s" #@ wp-super-cache #: plugins/awaitingmoderation.php:34 msgid "(Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment.) " msgstr "(Supprime le texte \"Votre commentaire est en attente de modération.\" lorsque quelqu'un laisse un commentaire à modérer.)" #@ wp-super-cache #: plugins/badbehaviour.php:61 #, php-format msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Seule la mise en cache par héritage est prise en charge, la compression est désactivée ; nécessite Bad Behavior dans \"%s/plugins/bad-behavior/\")" #@ wp-super-cache #: plugins/domain-mapping.php:57 #, php-format msgid "Domain Mapping support plugin is %s" msgstr "Le support de l'extension Domain Mapping est %s" #@ wp-super-cache #: plugins/domain-mapping.php:58 msgid "(support for multiple domains on multisite websites) " msgstr "(Prise en charge de plusieurs domaines sur les sites Web multisites)" #@ wp-super-cache #: plugins/domain-mapping.php:72 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Extension Domain Mapping détectée ! Merci d'aller sur la page Extensions SuperCache et d'y activer l'extension assistant de Domain Mapping." #@ wp-super-cache #: wp-cache.php:210 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Il semble que le Mode Réécriture ne soit pas installé. Parfois, cette vérification n'est pas fiable à 100%, surtout si vous n'utilisez pas Apache. Merci de vérifier que le module mode réécriture est chargé. Il est nécessaire pour se servir des fichiers statiques Super Cache. Vous serez toujours en mesure d'utiliser des modes Héritage ou PHP." #@ wp-super-cache #: wp-cache.php:249 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Le support de mobiles requiert des règles supplémentaires dans votre fichier .htaccess, ou vous pouvez régler l'extension en Mode Héritage. Voici vos options (par ordre de difficulté) :" #@ wp-super-cache #: wp-cache.php:250 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Règle l'extension en Mode Héritage et active le support pour mobiles." #@ wp-super-cache #: wp-cache.php:251 #: wp-cache.php:260 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Défilez jusqu'à la page Paramètres Avancés et cliquez sur le bouton Mise à Jour des Règles du Mode Réécriture." #@ wp-super-cache #: wp-cache.php:274 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Les modules Apache suivants sont manquants. L'extension fonctionne sans eux en mode héritage. En mode complet SuperCache, vos visiteurs pourront cependant voir les pages endommagées ou du contenu non mis à jour." #@ wp-super-cache #: wp-cache.php:494 msgid "WP Super Cache Settings" msgstr "Réglages WP Super Cache" #@ wp-super-cache #: wp-cache.php:505 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Avis : Le mode de mise en cache réécriture ou héritage est activé. Affichage de la page des Paramètres Avancés par défaut." #@ wp-super-cache #: wp-cache.php:533 #: wp-cache.php:607 msgid "Caching must be enabled to use this feature" msgstr "La mise en cache doit être activée pour utiliser cette fonctionnalité" #@ wp-super-cache #: wp-cache.php:563 msgid "One or more page requests failed:" msgstr "Un ou plusieurs requête(s) de page a/ont échoué :" #@ wp-super-cache #: wp-cache.php:582 #: wp-cache.php:583 #, php-format msgid "Page %d: %d (%s)" msgstr "Page% d:% d (% s)" #@ wp-super-cache #: wp-cache.php:599 msgid "Send non-secure (non https) request for homepage" msgstr "Envoi d'une requête non-sécurisée ( non-https) pour la page d'accueil" #@ wp-super-cache #: wp-cache.php:681 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "En \\\"Mode Préchargement\\\", la collecte régulière des poubelles ne nettoiera que les anciens fichiers héritage pour les utilisateurs connus, pas les fichiers préchargés SuperCache. Ce paramètre est recommandé lorsque le cache est préchargé." #@ wp-super-cache #: wp-cache.php:718 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "mode de Préchargement (collecte des poubelles uniquement sur les fichiers cache héritage. Recommandé.)" #@ wp-super-cache #: wp-cache.php:754 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Le Préchargement du cache est désactivé. Merci de désactiver la mise en cache des pages par Héritage, ou parlez-en à l'administrateur de votre hébergement." #@ wp-super-cache #: wp-cache.php:769 #: wp-cache.php:854 msgid "Caching" msgstr "Mise en cache" #@ wp-super-cache #: wp-cache.php:773 msgid "Cache hits to this website for quick access." msgstr "Mise en cache des connexions à ce site pour un accès rapide." #@ wp-super-cache #: wp-cache.php:773 #: wp-cache.php:774 #: wp-cache.php:788 #: wp-cache.php:791 #: wp-cache.php:792 #: wp-cache.php:857 msgid "Recommended" msgstr "Recommandé" #@ wp-super-cache #: wp-cache.php:774 msgid "Use mod_rewrite to serve cache files." msgstr "Utiliser le Mode Réécriture pour servir les fichiers de cache." #@ wp-super-cache #: wp-cache.php:775 msgid "Use PHP to serve cache files." msgstr "Utiliser le mode PHP pour servir les fichiers de cache." #@ wp-super-cache #: wp-cache.php:776 msgid "Legacy page caching." msgstr "Mise en cache de page Héritée." #@ wp-super-cache #: wp-cache.php:777 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching." msgstr "Le Mode Réécriture est le plus rapide, le Mode PHP est presque aussi rapide et plus facile à faire fonctionner, tandis que le mode Mise en Cache Héritée est plus lent encore, mais plus souple et plus facile à faire fonctionner. Les nouveaux utilisateurs devraient utiliser la mise en cache PHP." #@ wp-super-cache #: wp-cache.php:783 msgid "Miscellaneous" msgstr "Divers" #@ wp-super-cache #: wp-cache.php:788 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Compresse les pages afin qu'elles soient servies plus rapidement aux visiteurs." #@ wp-super-cache #: wp-cache.php:789 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "La compression est désactivée par défaut parce que certains hébergements ont des problèmes avec des fichiers compressés. Le mettre en marche/arrêt efface le cache." #@ wp-super-cache #: wp-cache.php:791 msgid "Don’t cache pages for known users." msgstr "Ne pas mettre en cache les pages pour les utilisateurs connus." #@ wp-super-cache #: wp-cache.php:792 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Reconstruction du cache. Sert un fichier SuperCache aux utilisateurs anonymes pendant qu'un nouveau fichier est généré." #@ wp-super-cache #: wp-cache.php:804 msgid "Clear all cache files when a post or page is published." msgstr "Effacer tous les fichiers de cache quand un article ou une page est publié." #@ wp-super-cache #: wp-cache.php:806 msgid "List the newest cached pages on this page." msgstr "Liste les pages les plus récemment mises en cache sur cette page." #@ wp-super-cache #: wp-cache.php:857 msgid "Caching On" msgstr "Mise en cache Activée" #@ wp-super-cache #: wp-cache.php:858 msgid "Caching Off" msgstr "Mise en cache désactivée" #@ wp-super-cache #: wp-cache.php:859 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Note : active la mise en cache PHP, la reconstruction du cache, et le support des mobiles" #@ wp-super-cache #: wp-cache.php:869 msgid "Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Avis : règles du mode réécriture SuperCache détectées. Les fichiers mis en cache seront servis à l'aide de ces règles. Editer le fichier .htaccess à la racine de votre installation et supprimer les règles SuperCache." #@ wp-super-cache #: wp-cache.php:883 #, php-format msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Il blogue sur %1$s et poste des photos sur %2$s." #@ wp-super-cache #: wp-cache.php:919 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Les extensions de Cache sont des scripts PHP qui vivent dans un dossier d'extensions à l'intérieur du dossier wp-super-cache. Ils sont chargés lorsque SuperCache se charge, beaucoup plus tôt que les extensions WordPress classiques." #@ wp-super-cache #: wp-cache.php:920 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Il s'agit d'une fonctionnalité avancée seulement, au sens strict : la connaissance à la fois des actions PHP et de celles de WordPress est nécessaire pour la créer." #@ wp-super-cache #: wp-cache.php:930 msgid "Available Plugins" msgstr "Extensions Disponibles" #@ wp-super-cache #: wp-cache.php:946 msgid "Tester & Contents" msgstr "Testeur & Contenus" #@ wp-super-cache #: wp-cache.php:946 msgid "Preload" msgstr "Préchargement" #@ wp-super-cache #: wp-cache.php:946 msgid "Plugins" msgstr "Extensions" #@ wp-super-cache #: wp-cache.php:946 msgid "Debug" msgstr "Débogage" #@ wp-super-cache #: wp-cache.php:973 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Avis : Les contrôles des règles du mode réécriture de WP Super Cache est désactivé, à moins qu'il ne s'exécute sur le site principal de ce réseau." #@ wp-super-cache #: wp-cache.php:975 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Avis : les contrôles des règles du mode réécriture de WP Super Cache sont désactivés, à moins qu'ils ne s'exécutent sur le site principal de ce réseau." #@ wp-super-cache #: wp-cache.php:1253 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Si le délai d'expiration est supérieur à 1800 secondes (une demi-heure), la collecte des ordures sera effectuée toutes les 10 minutes ; sinon, elle s'effectuera 10 secondes après le délai d'expiration ci-dessus." #@ wp-super-cache #: wp-cache.php:1254 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "La vérification et la suppression des fichiers périmés coûte cher, mais il coûte également cher de les laisser là. Sur un site très occupé, vous devriez définir le délai d'expiration à 300 secondes. Essayez avec différentes valeurs, et visitez cette page pour voir combien de fichiers expirés demeurent à différents moments de la journée. Si vous utilisez la mise en cache Héritée, ayez pour objectif d'avoir moins de 500 fichiers mis en cache, si possible. Vous pouvez avoir infiniment plus de fichiers mis en cache en utilisant les modes de mise en cache Réécriture ou PHP." #@ wp-super-cache #: wp-cache.php:1719 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    Constante WP_CACHE réglée sur \\\"false\\\"

    La constante WP_CACHE est utilisée par WordPress pour charger le code qui fournit des pages mises en cache. Malheureusement, elle est réglée sur \\\"false\\\". Merci de modifier votre fichier wp-config.php, et d'y ajouter ou modifier la ligne suivante, au-dessus de la commande finale require_once :

    define('WP_CACHE', true);

    " #@ wp-super-cache #: wp-cache.php:1722 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Éditez %s et ajoutez-y la ligne suivante:
    define('WP_CACHE', true);
    , sinon WP-Cache ne sera pas exécuté par le noyau WordPress." #@ wp-super-cache #: wp-cache.php:1961 msgid "List all cached files" msgstr "Liste de tous les fichiers mis en cache" #@ wp-super-cache #: wp-cache.php:2451 #, php-format msgid "[%s] Preload may have stalled." msgstr "[%s] Le préchargement peut avoir décroché." #@ wp-super-cache #: wp-cache.php:2451 #, php-format msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Le préchargement a été redémarré.\n" "%s" languages/wp-super-cache-ja.mo000066600000232701152133035240012271 0ustar00a$ ,<,Maq` ~?n3* 7 Z 5P! !="b"j5#-#$# #$$%u&\P''?()*1++w,Z-%\--0...0&00:1nI2p2)4;4D4H44444 5#53B5v5z5)6 86,E6r6^#7p7+78n58/88 8 8`8+T9939999!9:!;7<M<c<I=@\==s">>?%?E?J^?@ @@ @@@5@&A9A3A1-B_BCCCDDDPEu_E EjEaFfF?GWG^GqG}yGGNGLHaH2I GInTI$IAI*J0JMJiJJeJJKaLzL LL<LgLPM+cM*MMMM NbN?OOP&QR"Sk$TUWUUEVGV*]V V V VV]V$W@W _WmWWWWOX$aX"XX!XX YYZ&ZZ<Zb [ [y\ ]0 ] =]!J]-l]k]_ _ "_-_3_mL_T_`U/``p3aUaab bb.bJMbbducc`dde0e e ee7eS.f?f<ffg5g7Jgjgg h)hYHhh h h hh(h+i,1i.^ifi i/j01jbj?j8$k]k fk/sk:kkk llm m;mqNmmmneopp#qqzs<qtGt#tRuumv vTw~Cx+xx yyyzK{R{f{{ {{%{'{ | |j8|b|}l}=~F~U~]~f~B~~~*b[^ Fŀ7 rDM/Aqf.$;e`ƈ>i ɋ)If*}/.،3;Z^gowM"Ypkʏ6Vs4Bߑ^" Yct]2oTaU}5.1.".QlC1ԡo6?Ѧ֧e1^"m  ɮcs  0ʯb^b*IQeײL*[>gҵT0ضQ "[~;<̺` 9joK_PԿ21  %2:0S$c$ 2J,Hw/*B^ `mt<X>-lM BOls Pg[!! 0 6&)'7"!Q y]!EM? rS ; &}-<fj0BEXl|>EJ &6V;/Q;,A#,Pk+.@oowgc~1Z0@ P!Z|g! V7$031edU21>x?*K:i_{4**;Wf^5}8szZB$BgFNX>lQRfL// PWls6a4    u  \EcDKHN3P0T|R!Y{>FZI$[u,39<Mv? = "!;" | WB_8s4VuTINR"B`k$22E%@^JPDAU3g X=$cn`K'PA?ldVO/M:4+79+]S'6i%F&ZbTw5C0^M#)0({GX H.,<py]1o8~eRU ? S*G(a-t!:\QWa35Jh ;>Cvj 6H Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumUse Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together.Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.This page explains how to change file permissions.No Adverts for Friends plugin is %s.

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages are stored on your server as html and PHP files. If you need to delete them use the button below.Cached pages since %1$s : %2$sCachingCaching OffCaching OnCaching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.ContentsCurrently caching from post %d to %d.Currently logging to: %sDear User, WP Super Cache was removed from your blog but the mod_rewrite rules in your .htaccess were not. Please edit the following file and remove the code between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first! %s Regards, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggingDeleteDelete CacheDelete Cached PagesDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. Email the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExcludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default).Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionExtra homepage checks. (Very occasionally stops homepage caching)FeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesIt appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelMake WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Provides support for Domain Mapping plugin to map multiple domains to a blog.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSkip https URLs to avoid "mixed content" errorsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Supercache Uninstall ProblemsTagsTest CacheTest your cached website by clicking the test button below.Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$sThis is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledsecondsProject-Id-Version: ja Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2011-02-23 17:57:46+00:00 PO-Revision-Date: Last-Translator: JOTAKI, Taisuke Language-Team: ja MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Language: X-Poedit-Language: Japanese X-Poedit-Country: JAPAN X-Poedit-SourceCharset: utf-8 かならず WordPress の既存のルールの前に入れてください。%1$s は %2$s でキャッシングされているおかげで Digg に耐えられます%1$s は %2$s と他の多く方の貢献によってメンテナンスされ、開発されています。キャッシュページ数: %s期限切れページ数: %s%s を書き込み可能です。これにはセキュリティリスクを伴いますので、ページ生成後には読み込みのみにしてください。%s 個を削除しました !%s.htaccess が必要な mod_rewrite ルールで更新されました。正しく更新されたか確認してください。次のようになっているはずです:%s/advanced-cache.php がないか、更新できません。(1 = 小、5 = 大、大きなサーバーのロードを引き起こすかもしれません)(実験的)(レガシーキャッシングのみサポートしています。圧縮が無効になっていて、"%s/plugins/bad-behavior/" に Bad Behavior が必要です)(アクセスの多いサイトでは必ずしも正確ではないかもしれません)(この IP アドレスからのリクエストだけを記録します。あなたの IP アドレスは %s です)(friendsadverts.php も必要です) 1. もしこのファイルがすでにあれば、まず最初にこのファイルを削除してください2. ftp やサーバーソフトウェアで chmod コマンドを使用して %1$s を書き込み可能にし、(chmod 777 %1$s) このページを再読込みします。これは一時的な処置で、この後、読み込みのみに再度する必要があります。(前述のコマンドで 777 を 755 に変更します)3. %s/advanced-cache.php を更新するためにこのページを再読込みします304 Not Modified ブラウザーキャッシング。最後にリクエストされてから変更がないことを示す。304 サポートはデフォルトでは無効にしています。過去に GoDaddy で問題が発生したことがあるためです。よくある質問と答えインストールのヘルプサポートフォーラムUse Google Libraries プラグインにより、一般的に利用されている JavaScript のライブラリのいくつかを Google のウェブサーバーから読み込むようにします。皮肉にも、これにより Yslow のスコアが下がることもあります。WP Minify は JavaScript と CSS ファイルを結合させることによりウェブサーバーから送信されるファイルの数を減らします。別の手段としては WPSCMin があります。これは Supercache のプラグインで、JS/CSS ファイルの結合は行ないませんが、キャッシュされたページを小さくします。Yahoo! Yslow は Firefox のアドオンの Firebug の拡張機能です。これはウェブページを分析し、ハイパフォーマンスウェブページ用のルールセットをベースにパフォーマンス改善方法を提案します。また、オンラインのパフォーマンスツールの GTMetrix 試してみるといいでしょう。ファイルパーミッションの変更はこのページを参考にしてください。No Adverts for Friends プラグインは%sです。

    WP_CACHE 定数の wp-config.php への追加

    もしこの警告メッセージが表示され続けるのなら、FAQ のポイント 5 を参照してください。WP_CACHE の行を上に上げる必要があります。

    WP_CACHE 定数が false に設定されています

    WP_CACHE 定数はキャッシュされたページを提供するためのコードを読み込むために WordPress によって利用される定数です。残念ながらこの定数が false に設定されています。wp-config.php を開いて、最後の require_once コマンドの上に次の行を追加もしくは編集してください。

    define('WP_CACHE', true);

  • 1. テキストエディターで %1$s$wp_cache_file を開きます
  • 2. テキスト CACHEHOME を %2$s に変更します
  • 3. ファイルを保存し、%3$s へコピーしてこのページを再読込みします
    • 注意: 変更を保存する前に静的な URL、%s などで CDN サービスが完全に動作していることを確認してください。上級者のみ: Speed up your site with Caching and cache-control (キャッシングと cache-control によるサイトのスピードアップ) では .htaccess ルールでサイトをよりキャッシュする方法を説明しています。上級者のみ: オブジェクトキャッシュのインストール。Memcached、XCache、eAcccelerator、もしくは他から選択してください。エラー: wp-config.php ファイルの WP_CACHE が有効になっていません。このプラグインから修正はできません。ガーベージコレクション
    最後の GC は %s 分前です
    最後にキャッシュされたページ: %s警告 ! 圧縮を有効にしようとしましたが、zlib.output_compression が有効になっています。readme ファイルのトラブルシューティング #21 を参照してください。このプラグインが正しく動作するためにはカスタムな URL (もしくはパーマリンク) 構造が必要です。パーマリンク設定画面を開いてパーマリンクを設定してください。現在の .htaccess ファイルと、このプラグインの rewrite ルールに差異が見つかりました。この差異は単純にスペースの数の違いかもしれませんが、できるだけ早くこのファイル内のルールと以下を比較確認してください。’Mod_Rewrite ルールを更新’ をクリックするとこのルールを更新します。これを行なう簡単な方法としては、CHMOD コマンドや ftp クライントを使用して一時的に権限を変更する方法があります。グローバルに書き込み可能で問題ないことを確認してください。受け付けるファイル名と除外する URIダイレクトページを追加:ここにキャッシュしないようにするページの文字列 (ファイル名ではなく) を追加します。例えば、URL に「西暦」を含んでいて昨年の投稿をキャッシュしたくない場合は西暦 ’/2004/’ だけを入力すれば十分です。WP-Chache は URI にその文字列が含まれているか検索し、含まれていた場合はそのページをキャッシュしません。上で指定した除外文字列にマッチしてもキャッシュするファイル名をここに追加してください。自分でルールを追加する。%s.htaccess を開いて # BEGIN WPSuperCache と # END WPSuperCache で囲まれているコードブロックを探します。とてもよく似ているセクションが 2 箇所あります。code>%%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$     の下に次の行を追加します: (これを 2 回、各セクションで実施します)追加 CNAME詳細経過時間もしくは、%s.htaccess ファイルを手動で編集して次のコードを追加してください (WordPress のルールの前に):アーカイブ利用可能なプラグイン承認待ち承認待ちは%s件です。Bad BehaviorBad Behavior のサポートは現在%sです。Bad Behaviour が見つかりませんでした。インストールを確認してください。CDNCDN 機能は Mark Kubacki の OSSDL CDN Off Linker によって提供されています。キャッシュコンテンツキャッシュテスターヒットしたページをキャッシュし、素早くアクセスさせる。キャッシュプラグインは PHP のスクリプトで wp-super-cache フォルダ内の plugins フォルダ内にあります。これは Supercache の読み込み時に読み込まれ、通常の WordPress プラグインよりもかなり早い段階で読み込まれます。キャッシュリビルド。新しいファイルの生成中にこのサイトの登録ユーザー以外のユーザーに supercache のファイルを供給する。キャッシュ統計値は自動的には生成されません。再生成するには下のリンクをクリックしてください。キャッシュ統計値が最後に生成されたのは %s 分前です。%s 秒前にキャッシュされましたキャシュされたページはお使いのサーバー上に html と PHP ファイルとして保存されます。キャッシュされたページを削除するには下のボタンをクリックしてください。%1$s 以降のキャッシュページ : %2$sキャッシングキャッシング停止キャッシング利用キャッシングはウェブサイトを高速化する手段のひとつに過ぎません。役に立つ他のプラグインをご紹介します:この機能を利用するにはキャッシングを有効にしてください。キャッシュプリロードをキャンセル継続できません…前の問題を修正して再度お試しください。.htaccess を更新できませんカテゴリー有効時間を変更5 分ごとにフロントページをチェックする。期限切れファイルのチェックや削除はそれなりの負荷がかかりますが、そのまま残しておくのも負荷になります。アクセスがかなり多いサイトの場合、有効期限を 300 秒に設定するといいでしょう。いろいろな値でこのページを表示させ、時間帯によってどのくらいの期限切れファイルが残るのかを試してみるといいでしょう。レガシーキャッシュ機能を使用している場合は、できればキャッシュファイルの数は 500 以下になるようにしましょう。mod_rewrite や PHP キャッシングを利用している場合はその何倍ものキャッシュファイルを保持できます。古い supercache のファイルを片付けています。投稿や固定ページの公開時にすべてのキャッシュファイルを削除する。エラー発生時にキャッシュをクリアする。荒削りなファイルロック。おそらく必要ないですが、使用しているサーバーが非力な場合には役に立つかもしれません。警告 ! まれにですがサーバーを止めてしまうことがあります !コメントは承認待ちです。表示されるまでしばらく時間がかかるかもしれません。ページを圧縮し、訪問者により速くページを供給する。ホストによっては圧縮されたファイルで問題が発生する場合があるので、デフォルトでは無効にしています。この機能を有効にして無効にすると、キャッシュがクリアされます。設定ファイルが変更され、いくつかの値が誤っています。"設定"メニューからページを再読込みしてリセットしてください。設定ファイルが見つかりません。%1$s ディレクトリ (%2$s) がウェブサーバーによる書き込みを許可していません。パーミッションを確認してください。コンテンツ投稿 %d から %d のキャッシュを作成中現在ログ取得中: %sユーザー様へ あなたのブログから WP Super Cache が削除されましたが、mod_rewrite ルールは .htaccess から削除されていません。 次のファイルを開いて 'BEGIN WPSuperCache' と 'END WPSuperCache' の あいだのコードを取り除いてください。最初にこのファイルのバックアップを忘れずに ! %s よろしくお願いします。 WP Super Cache プラグイン http://wordpress.org/extend/plugins/wp-super-cache/デバッグデバッグ削除 キャッシュを削除キャッシュされているページの削除期限切れキャッシュを削除Super Cache のキャッシュファイルを削除する (新しいウインドウで開きます)キャッシュファイルを削除%s.htaccess 内の # BEGIN WPSuperCache と # END WPSuperCache で囲まれたこのプラグインの mod_rewrite ルールを削除して、ページを再読込みしてプラグインに再生成させてください。supercache ファイルを削除しています: %s
    wp-cache ファイルを削除しています: %s
    開発者のみなさんへ: "WPLOCKDOWN" 定数をチェックすることにより、あなたのプラグインにロックダウンとの互換性を持たせることができます。次のコードにより、あなたのプラグインが WPLOCKDOWN 設置を考慮するようになります。ダイレクトキャッシュファイルダイレクトキャッシュファイルはブログのある %s からダイレクトに生成されたファイルです。この機能は Digg やスラッシュドットなど巨大レベルのトラフィックがひとつの投稿やページに集中することが予想されるときだけ役に立ちます。静的ファイルマッチングに含むディレクトリです。コンマで区切ってください。デフォルトは wp-content, wp-includes で、この欄が空欄の場合は強制的にこのデフォルトが使用されます。停止する無効次のページタイプはキャッシュしません。各タイプについての詳細は Conditional Tags を参照してください。ドメインマッピングドメインマッピングプラグインを検知しました ! Supercache プラグインの設定ページを開いてドメインマッピングのヘルパープラグインを有効化してください。ドメインマッピングのサポートは現在%sです。既知のユーザー向けにはページをキャッシュしない。簡易%s を編集して次の行を追加してください:
    define('WP_CACHE', true);
    追加しないと WordPress コアによる WP-Cache の実行ができません。確認時にブログ管理者にメールを送る。(テスト時に有益)使用するCDN サポートを有効化有効モデレートされたコメントが残されたときに表示されるテキスト "あなたのコメントはモデレーション待ちです。" を取り除くプラグインの有効化もしくは無効化。エラー エラー: GZIP 圧縮が有効です。wp-cache を使用する場合は無効にしてください。除外するサブストリング上記文字列にマッチするファイルはrewriteから除外されます。複数の場合は .php, .flv, .do のようにコンマで区切ってください。.php は常に含めてください。(デフォルト)既存のダイレクトページ有効時間:期限切れファイルとは %s 秒より古くなったファイルです。こうしたファイルはこのプラグインによってまだ使用されますが、定期的に削除されます。有効時間とガーベージコレクション追加のホームページチェック。(非常にまれにホームページのキャッシングを止めることがあります)フィードキャッシュを準備するために %s を取得: %s の最初のコピーを取得中: %s の二つめのコピーを取得中: 設定の修正このデバッグ設定でプラグインの問題を修正します。キャッシュディレクトリのファイルにログを記録します。パフォーマンスを最大にするには "モバイル機器サポート"を使用するか、.htaccess の mobile rewrite ルールを削除してください。"2.0\ MMP|240x320" の 2 行を探して削除してください。例: %1$sabout/ をキャッシュするには %1$sabout/ もしくは /about/ を入力します。このキャッシュファイルは次に該当のページに誰かが来た時に生成されます。新しい Super Cache ファイル新しい WP-Cache ファイルフロントページフロントページテキストキャッシュの完全リフレッシュは %d 時間 %d 分 %d 秒後です。WordPress の GZIP 圧縮が有効です。GZIP 圧縮が無効にされるまで wp-cache はバイパスされます。ガーベージコレクションGzip エンコードルール %s.htaccess に作成されました。彼は %1$s でブログを書き、%2$s に写真を投稿しています。ファイルリストを隠すホームWP Super Cache のバグではないと 99% 思いますし、発生するのはごくごく稀ですが、もし心配なら 5 分ごとにサイトが問題ないか確認するよう簡単なチェックができます。もし問題が発生すればメールが届きます。IP アドレスもし動作しなければ %s/advanced-cache.php ファイルが存在するか確認してください:有効期限が 1800 秒 (30 分) 以上の場合、ガーベージコレクションは 10 分ごとに実行されます。それ以外の場合は期限切れ時間の 10 秒後に実行されます。このプラグインをアンインストールする場合、%s ディレクトリがウェブサーバーによる書き込みを許可していることを確認してください。許可してあれば advanced-cache.php と cache-config.php は自動的に削除されます。(これらのファイルも書き込み可能になっているかも確認したほうがいいかもしれません !)’プリロードモード’ では、定期ガーベージコレクションは既存ユーザー用の古いレガシーファイルのみ削除し、プリロードされた supercache ファイルは削除しません。これはキャッシュがプリロードされたときの推奨設定です。とてもまれなケースですが、2 つの問題が発生することがあります:
    1. フロントページが zip ファイルとしてダウンロードされることがある
    2. 静的なフロントページを使用していてパーマリンク構造が /%category%/%postname%/ の場合にフロントページとして誤ったページがキャッシュされてしまう
    含めるディレクトリmod_rewrite がインストールされていないようです。このチェックは、特に Apache を使用していない場合、100% 信用できないことがあります。mod_rewrite モジュールが読み込まれているかよく確認してください。このモジュールは Super Cache 静的ファイルの提供に不可欠です。ただし、レガシーもしくは PHP モードは使用できます。あなたのブログの URL は最後が "/" になっているようです。残念ながら、このプラグインをインストールした後に重複コンテンツのバグが見つかりました。"/" で終わっていない URL は "/" で終わっている URL を同じコンテンツとして提供し、正しい URL にリダイレクトしません。これを修正するには .htaccess ファイルを編集してこれら 2 つのルールを Super Cache ルールの 2 つのグループに追加する必要があります。キー遅延 init。WordPress が読み込んだ後にキャッシュされたファイルを表示します。レガシーモードで有益です。レガシーなページキャッシング。メール少数。すべての投稿のプリロードの最初と最後に 1 件づつのメール。すべてのキャッシュファイルを表示キャッシュされた最新のページを一覧表示する。ロックダウンロックダウン:ログレベルWordPress を速くするダイレクトページのこのリストから取り除くには、テキストボックスをブランクにしてキャッシュファイルを削除してください。メール多数。投稿数 100 につき 2 件のメール。中くらいのメール数。投稿数 100 につき 1 件のメール。その他欠けている Apache モジュールモバイル機器サポートモバイル用 rewrite ルールを検知しましたモバイルサポートには .htaccess ファイルにルールを追加する必要があります。もしくはプラグインをレガシーモードに設定します。次のオプションがあります (難しい順):Mod Rewrite ルールMod Rewrite ルールを更新できません !Mod Rewrite ルールを更新する必要があります !Mod Rewrite ルールを更新しました !Mod rewrite がインストールされていないようです !Mod_rewrite が最速で、PHP はほぼ同じ速さで動作させるのがより簡単です。レガシーキャッシングは遅いですが、より柔軟で動作させるのが簡単です。新しいユーザーは PHP キャッシングを利用するようにしてください。助けが必要ですか ?お困りですか ? Super Cache readme ファイルを読んでみてください。このファイルにはインストールのドキュメント、よくある質問とその答え、トラブルシューティングのヒントが含まれています。また、サポートフォーラム も利用可能です。あなたの問題の答がすでにあるかもしれません。キャッシュされた最新のページ:次の GC は %s 分後ですメモ:メモ: PHP キャッシング、キャッシュリビルド、モバイルサポートを有効化します。お知らせ: Mod_rewrite もしくはレガシーキャッシングが有効になっています。詳細設定ページをデフォルトで表示します。お知らせ: PHP キャッシングが有効化されていますが Supercache mod_rewrite ルールが検知されました。キャッシュされているファイルはこのルールを利用して提供されます。サイトの表示に問題がなければこのメッセージは無視してください。もし問題があれば、WordPress のルートにある .htaccess ファイルを開いて SuperCache のルールを取り除いてください。お知らせ: WP Super Cache mod_rewrite ルールチェックは、このネットワークのメインサイトで動作していなければ無効です。OKオブジェクトキャッシュを使用中です。キャッシュリストはありません。オフサイト URLページのリクエストに失敗しました:コメントが投稿されたときに該当のページだけリフレッシュする。PHP がサイト訪問者に送るデータを圧縮しています。このプラグインは同じページを何度も圧縮するのではなく、圧縮した出力をキャッシュするだけなので、この機能は無効にすることをおすすめします。また、トラブルシューティングの #21 も参考にしてください。 php.ini の修正については「実行時設定」の説明をご覧ください。ページ %d: %d (%s)ページ 1: %sページ 2: %sページパーマリンク構造エラーこのプラグインをレーティングして、動作しているかどうかをお知らせください。開発に非常に役立ちます。wp-super-cache/wp-cache-config-sample.php から %s /wp-cache-config.php を作成してください。%s でも彼に一言どうぞ !readme.txt Troubleshooting section の 16 を参照してくださいアンインストールの説明は readme.txt の "How to uninstall WP Super Cache" を参照してください。フロントページが不正でテキスト "%2$s" が見つからないので、%1$s を開いてキャッシュをクリアしてください !フロントページがダウンロードされる状態なので、%s を開いてキャッシュをクリアしてください !プラグインプリロード%s 件の投稿をプリロード。キャッシュプリロードをすぐに実行プリロードを再スタートしました。 %sプリロードモード (レガシーなキャッシュファイルに対してのみガーベージコレクションを実行。推奨)プリロード機能は大量のファイルを生成します。キャッシュは新しい投稿から先に生成するので、投稿記事がたくさん (1万ページ以上) ある場合は新しい投稿記事だけをキャッシュするようにしてください。これは共有サーバーを使用しているときは特に重要です。キャッシュのプリロードは停止しています。レガシーなページキャッシングを無効にするかホスト管理者に伝えてください。ロックダウンを有効にすることにより、予想されるトラフィックの激増に対してサーバーが対処できるようにします。この機能が有効になると、新しいコメントが投稿されてもキャッシュされた静的ファイルは更新されません。使用しているサーバーが Digg に耐えられることを誇らしげに表示する (フッターにメッセージを表示する)ドメインマッピングをサポートしてブログに複数のドメインをマップします。このプラグインをレーティングしてください !読み込み専用モード。設定は変更できません。読込みのみ:推奨おすすめのリンクとプラグインキャッシュのリフレッシュは %d 時間 %d 分 %d 秒後です。プリロードされたキャッシュファイルは %s 分毎にリフレッシュされます。(0 にすると無効、最小 %d 分)ファイルのパーミッションを変更したらこのページを再読込みしてください。 .htaccess ファイルを更新したら、このページを再読込みしてください。以下の投稿がリフレッシュされました:キャッシュ状況データを再生成除外するユーザーエージェント正しく圧縮された supercache ファイルを提供する必要があります。supercache のページでキャッシングの設定が必要です。IE7 ユーザーはこのモジュールがないと古いページを参照します。デフォルト設定を復元Rewrite ルールを更新する必要がありますルールは %s にも追加する必要があります:WP-Cache の設定サンプルファイル (%s) がありません。インストールを確認してください。保存変更を保存ファイルを保存文字列を保存UA 文字列を保存予定されていたキャッシュのプリロードがキャンセルされました。%d 分後にキャッシュのプリロードを開始します。10 秒後にキャッシュのプリロードを開始します。次のプレロードリフレッシュは %d 分後の予定です。詳細設定ページでスクロールダウンして Mod_Rewrite ルールを更新 ボタンをクリックしてください。検索ページファイルリフレッシュ時にステータスメールを送信する。非セキュア (https ではない) なホームページへのリクエストを送信supercached ページで有効期限を設定してください。このモジュールがないと、読者は再読込みしたりコメントを残しても新しいページを参照できないかもしれません。ガーベージコレクションを無効にするには有効時間を 0 秒に設定してください。レガシーモードに設定し、モバイルサポートを使用します。設定シングルページ"mixed content" エラーを避けるために https の URL をスキップするすみませんが、このブログは一時的に停止中です。間もなく更新されます。古い Super Cache ファイル古い WP-Cache ファイルWP-Cache が bot、spider、クローラーのリクエストをキャッシュしないようにする HTTP ’User Agent’ ヘッダー内の文字列です。すでにキャッシュが存在する場合はこれらのエージェントに Super Cache のファイルが送信されます。Supercache アンインストール時の問題タグキャッシュをテスト下のテストボタンをクリックするとキャッシュされたページをテストできます。フロントページで検索するテキスト。もしこのテキストがなければキャッシュがクリアされます。無効するにはブランクにしてください。アップグレードありがとうございます。origin pull に頼りたくない場合は、Amazon S3/Cloudfront へのファイルのアップロードをサポートする CDN Sync Tool プラグインが役に立つでしょう。このプラグインに関して質問がある場合はプラグインサポートフォーラムを参照してください。WP Super Cache 設定ファイルは %s/wp-cache-config.php で、変更できません。変更するにはこのファイルにウェブサーバーが書き込みできるようにする必要があります。フロントページにテキスト "%2$s" が見つからなかったのでブログのキャッシュをクリアしました。%1$s を開いてキャッシュがクリアされたことを確認してください。フロントページがダウンロードされる状態だったのでブログのキャッシュをクリアしました。%s を開いてキャッシュがクリアされたことを確認してください。%s.htaccessファイルがウェブサーバーによって変更できません。chmod コマンドや ftp クライアントで修正してください。次の Apache モジュールが見つかりません。これらのモジュールがなしの場合、レガシーモードで動作します。フル Supercache モードでは、閲覧者は壊れたページや古いデータを閲覧するかもしれません。mod_rewrite ルールは最後にこのプラグインがインストールされてから変更されています。残念ながら、新しいルールを更新する前に古い supercache のルールを取り除く必要があります。.htaccess ファイルを編集したら、このページを再読込みしてください。もし手動でアップグレードしたいならば、次の行を変更してください: %1$s は次に似ています: %2$s 違いは "HTTP_COOKIE" が "HTTP:Cookie" になり、"wordpressuser" が "wordpress" になったことだけです。これは WordPress 2.5 での変更ですが、これ以前のバージョンとの後方互換性があります。もしそれほど古いバージョンを使用する勇気があればの話ですが。%1$s の代わりに新しい URL がrewriteに使われます。最後の / は付けないようにしてください。
    例: %2$s。ページがマッチしません ! タイムスタンプが違うか見つかりません !このプラグインに必要な rewrite ルールが変更されたか無くなっています。両方のページのタイムスタンプがマッチしました !上記 CNAME は %1$s の代わりに (さらに上のオフサイト URL に加えて) rewriteで使用されます。複数の場合はコンマで区切ってください。静的ファイルが多数あるページの場合にブラウザーのパフォーマンスを改善できます。CNAME は CDN で設定する必要があるかもしれません。
    例: %2$sこれは厳密に言えば拡張機能だけで、作成には PHP と WordPress アクションの両方の知識が必要です。この機能はこのサイトで公開されているすべての投稿と固定ページをキャッシュします。Super Cache の静的ファイルが生成されるので、訪問者 (botも含む) はキャッシュされたページを閲覧することになります。これにより、ウェブサイトの測定基準のひとつとして「速さ」を採用している Google ランキングの改善に役立つかもしれません。この機能は通常のユーザーには何も影響ありませんが、モバイルユーザーにはキャッシュされたページを表示します。静的 html ファイルを利用できるようにするには、お使いのサーバーで %s.htaccess と呼ばれるファイルに正しい mod_rewrite ルールが追加されている必要があります。キャッシュファイルが多すぎるため一覧表示できません。最後のスラッシュの確認が必要です。URI残念ながら WordPress が wp-cron.php ファイルを見つけられません。WordPress による予約投稿やその他の重要な活動だけでなく、このプラグインによるガベージコレクションの正常なオペレーションにもこのスクリプトが不可欠です。残念ながら、WordPress MU が稼働中は rewrite ルールを自動的に更新できません。.htaccess を開いて次の mod_rewrite ルールをこのファイルの中の他のすべてのルールの上に追加してください。アンインストールはプラグインページから行ないます。不要なものは自動的に除去されますが、もし手動での操作が必要な場合は簡単な説明が表示されます。更新ダイレクトページを更新Mod_Rewrite ルールを更新設定を更新ステータスを更新キャッシュファイルの提供に PHP を利用する。キャッシュファイルの提供に mod_rewrite を利用する。キャッシュファイルの保存にオブジェクトキャッシュを使用する。Mod_Rewrite ルールを参照するWP Super Cache 設定WP Super Cache はあなたのブログのフロントページをチェックしました。この機能の使用を停止するには %s を開いてください。WP Super Cache は停止中です。プラグイン管理ページを開いてキャッシングを有効にしてください。WP Super Cache mod rewrite ルールが %s.htaccess ファイル内に検知されました。
    次のリンクをクリックしてこのファイルに追加された行を確認してください。プラグインをアップグレードをしたのなら、これらのルールがマッチしていることを確認してください。WP Super Cache の設定が必要です。管理ページを開いてこのプラグインの有効化と設定を行なってください。WP-CacheWP-Super-Cache警告警告 !警告 ! %s が書き込み可能になっています！注意 ! gzencode() 関数が見つからないため圧縮は無効です。警告 ! PHP セーフモードが有効になっています !Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.警告 ! ホスト名 "%s" が %s に設定されていますWordPress MU を検知しましたWordPress はロックダウンされています。Super Cache の静的ファイルは新しいコメントが投稿されても削除されません。WordPress はロックダウンされていません。新しいコメントが投稿されると Super Cache の静的ファイルは通常通りにリフレッシュされます。書き込み可能:マルチサイトネットワーク上の場合は各サイトに別々の CDN URL を設定することができます。このファイルをご自分で編集して次のルールを追加できます。下の "mod_rewrite ルールを表示する" リンクをクリックするとルールを参照して問題ないか確認することができます。セーフモードが有効なため、このプラグインの動作に問題が発生するかもしれません。自動更新を作動させるには BEGIN と END マーカーが %s.htaccess 内に必ず必要です。これは次のようになっていて、WordPress のメインの mod_rewrite ルールを囲んでいます:この機能を利用するには %s を書き込み可能にする必要があります。これにはセキュリティリスクを伴いますので、ページ生成後には読み込みのみにしてください。あなたもしくは管理者が、このプラグインスクリプトのグループオーナーをウェブサーバーのユーザーと一致するように変更すれば動作するようになるかもしれません。%s/cache/ ディレクトリのグループオーナーは変更する必要があります。詳細は safe mode manual page を参照してください。あなたもしくは管理者がこの機能を無効にする必要があります。詳細は safe mode manual page をご覧ください。残念ながら .htaccess ファイル内では無効にできません。php.ini 設定ファイルで無効にする必要があります。%s の権限を変更して、より限定されたものにしてください。ftp クライアントもしくは次のコマンドを使用して修正してください:%s.htaccess はウェブサーバーによる書き込みができません。必要な mod_rewrite ルールで更新する必要があります。新しいルールは以下のコードのように通常の WordPress ルールの上に追加します:WP-Cache 設定ファイル (%s) は古いもので、ウェブサーバーによる書き込みを許可していません。このファイルを削除してこのページを再読込みしてください。キャッシュディレクトリ ($cache_path) がなく、ウェブサーバーによって作成することもできませんでした。%s のパーミッションを確認してください。このプラグインを動作させるにはキャッシュディレクトリ (%1$s) もしくは %2$s に書き込める必要があります。よく確認してください。あなたのコメントは管理者の承認待ちです。お使いのサーバーではファイルの読み書きの許可の前に PHP スクリプトのオーナーを確認するように設定されています。お使いのサーバーはホスト名が %s に設定されています。このプラグインのガーベージコレクションや WordPress の予約投稿などのサービスが正しく動作しないかもしれません。おそらく、あなたのサイトでもたくさんの静的ファイルを使用していると思います。画像、JavaScript、CSS のファイルは通常は静的なファイルで、別サイトもしくはCDN から提供させるようにするのはとても簡単です。そのため、このプラグインでは wp-content と wp-includes ディレクトリ内の PHP ファイルを除くすべてのリンクを以下で指定している URL に入れ替える機能があります。すべての静的コンテンツを専用サーバーにコピーするか、origin pull で CDN にファイルをミラーすることができます。Zlib アウトプット圧縮を有効にしました ![%1$s] %2$d の投稿をリフレッシュ[%1$s] キャッシュのプリロードが開始されました[%1$s] キャッシュプリロード停止[%1$s] %2$d から %3$d の投稿をリフレッシュ中[%s] キャッシュのプリロードを完了[%s] フロントページチェック ![%s] フロントページが gzip 圧縮されました ! キャッシュがクリアされました ![%s] フロントページが gzip で圧縮されました ! キャッシュをクリアしてください ![%s] フロントページが不正です ! キャッシュがクリアされました ![%s] フロントページが不正です ! キャッシュをクリアしてください ![%s] プリロードは停滞しています。すべて停止中使用中秒languages/wp-super-cache-be_BY.po000066600000260723152133035240012667 0ustar00# Translation of the WordPress plugin by . # Copyright (C) 2010 # This file is distributed under the same license as the package. # FIRST AUTHOR , 2010. # msgid "" msgstr "" "Project-Id-Version: WP Super Cache\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2010-09-27 13:58+0000\n" "PO-Revision-Date: 2011-08-10 18:25+0200\n" "Last-Translator: \n" "Language-Team: Alexandr Alexandrov \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Belarusian\n" "X-Poedit-Country: BELARUS\n" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Ваш каментар чакае пацверджання." #: plugins/awaitingmoderation.php:23 #: plugins/awaitingmoderation.php:38 #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:47 #: plugins/domain-mapping.php:62 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1114 msgid "Disable" msgstr "Адключыць" #: plugins/awaitingmoderation.php:29 #: plugins/badbehaviour.php:55 #: plugins/domain-mapping.php:53 #: plugins/searchengine.php:67 msgid "disabled" msgstr "Адключаны" #: plugins/awaitingmoderation.php:31 #: plugins/badbehaviour.php:57 #: plugins/domain-mapping.php:55 #: plugins/searchengine.php:69 #: wp-cache.php:1460 msgid "enabled" msgstr "Уключаны" #: plugins/awaitingmoderation.php:33 #, php-format msgid "Awaiting Moderation plugin is %s" msgstr "Статут ўбудовы \" Awaiting Moderation\": %s" #: plugins/awaitingmoderation.php:34 msgid "(Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment.) " msgstr "(Прыбірае тэкст \" Ваш каментар чакае праверкі\" калі хто-то размяшчае каментар да запісу)" #: plugins/awaitingmoderation.php:36 #: plugins/badbehaviour.php:63 #: plugins/domain-mapping.php:60 #: plugins/searchengine.php:74 #: wp-cache.php:1114 msgid "Enable" msgstr "Дазволіць" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "Плагін \" Bad Behaviour\" не быў знойдзены. Праверце, завяршылі Ці Вы яго ўстаноўку." #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s." msgstr "Статут ўбудовы \" Bad Behaviour\": %s." #: plugins/badbehaviour.php:61 #, php-format msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Гэты дадатковы модуль будзе функцыянаваць толькі ў рэжыме сярэдняга кэшавання, адключыце сціск і ўсталюйце ўбудова \"Bad Behavior\" у \"%s/plugins/bad-behavior/\")" #: plugins/badbehaviour.php:69 #: wp-cache.php:1191 #: wp-cache.php:1193 msgid "Warning!" msgstr "Увага!" #: plugins/domain-mapping.php:57 #, php-format msgid "Domain Mapping support plugin is %s" msgstr "Статут ўбудовы \" Domain Mapping\": %s" #: plugins/domain-mapping.php:58 msgid "(support for multiple domains on multisite websites) " msgstr "(Падтрымка для MU - сэрвісу блогаў)" #: plugins/domain-mapping.php:72 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Выяўленая падтрымка сэрвісу мультиблогов! Каб палегчыць і паскорыць працу плагіна, Вам трэба ўключыць падтрымку мультиблогов ў наладах." #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s." msgstr "Статут ўбудовы \" No Adverts for Friends\":% s." #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(Патрабуе ўсталёўкі friendsadverts.php ) " #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Калі ласка, стварыце файл% s / wp-cache-config.php з wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:138 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Увага! Уключаны рэжым PHP Safe Mode!" #: wp-cache.php:139 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Пры працы з убудовай могуць узнікнуць праблемы, так як PHP Safe Mode уключаны на Вашым серверы." #: wp-cache.php:143 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Ваш сервер настроены так, што правярае ўладальніка для ўсіх PHP скрыптоў перад тым як дазволіць ім чытанне або запіс у файл." #: wp-cache.php:144 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Вы або Адміністратар можаце выправіць памылкі, змяніўшы групу ўладальніка скрыптоў плагіна праз налады вэб-сервера. Таксама трэба змяніць уладальніка для тэчкі% s / cache /. Для больш падрабязнай інфармацыі глядзіце старонку дапамогі па рэжыму safe mode (на англ.). " #: wp-cache.php:146 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Вы або Адміністратар павінны адключыць гэта. Для больш падрабязнай інфармацыі глядзіце старонку дапамогі па рэжыму safe mode (на англ.). Дадзеныя налады НЕ могуць быць адключаныя праз файл. htaccess, для вырашэння праблемы трэба рэдагаваць php.ini ў наладах вэб-сервера. " #: wp-cache.php:152 msgid "Permlink Structure Error" msgstr "Памылка структуры спасылак" #: wp-cache.php:153 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Для карэктнай працы ўбудовы неабходная карэктная налада структуры спасылак. Каб наладзіць іх, наведайце старонку Сталыя спасылкі . " #: wp-cache.php:165 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Увага! Ваша hostname \"% s\"пераўтворана ў% s" #: wp-cache.php:166 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Ваш вэб-сервер вырашыў, што hostname зменена на% s. Некаторыя опцыі ўбудовы (напрыклад, \" Ачыстка смецця \") і сам WordPress могуць працаваць некарэктна." #: wp-cache.php:167 #: wp-cache.php:181 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Каб даведацца больш, наведайце раздзел 16 ст Апісанні праблем у файле readme.txt (на англ.) " #: wp-cache.php:180 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "На жаль, файл wp-cron.php не быў знойдзены. Гэты скрыпт неабходны для карэктнай працы опциии \" Ачыстка смецця \"і самога WordPress." #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "Немагчыма працягнуць ... перш чым паўтарыць спробу, выпраўце папярэднія памылкі." #: wp-cache.php:204 msgid "Zlib Output Compression Enabled!" msgstr "Сціск Zlib Output ўключана!" #: wp-cache.php:205 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP выкарыстоўвае сціск для сціснутых старонкі Вашага сайта. Адключэнне дадзенай опцыі рэкамендуецца, каб пазбегнуць шматразовага сціску старонак убудовай. Даведацца больш, наведаўшы профіль 16 ст \" Апісанне праблем \"у файле readme.txt (на англ.). Таксама азнаёмцеся з гэтай старонкай (на англ.) па php.ini. " #: wp-cache.php:209 msgid "Mod rewrite may not be installed!" msgstr "Здаецца, модуль mod_rewrite не ўстаноўлены!" #: wp-cache.php:210 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Узнікла памылка, звязаная з тым, што модуль mod_rewrite адсутнічае ці не ўсталяваны. Калі ласка, праверце наяўнасць модуля mod_rewrite ў канфігурацыях сервера. Модуль неабходны для карэктнай працы ўбудовы з статычнымі файламі. Без падлучанага mod_rewrite Вы можаце выкарыстоўваць толькі рэжымы з падтрымкай PHP або сярэднюю кэшаванне . " #: wp-cache.php:215 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Рэжым \" только_чтение \". Налады не могуць быць зменены." #: wp-cache.php:216 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Канфігурацыйны файл плагіна WP Super Cache %s/wp-cache-config.php не можа быць зменены. Каб працягнуць, Вы павінны ўсталяваць правы на запіс для файла. " #: wp-cache.php:217 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Самы просты спосаб выправіць гэта - змяніць правы доступу, выкарыстоўваючы CHMOD, праз FTP-кліент. Дастаткова ўсталяваць глабальныя правы на запіс." #: wp-cache.php:218 msgid "Writeable:" msgstr "Даступна для запісу:" #: wp-cache.php:219 msgid "Readonly:" msgstr "Толькі чытанне:" #: wp-cache.php:231 #, php-format msgid "Warning! %s is writeable!" msgstr "Увага! Тэчка% s даступная для запісу!" #: wp-cache.php:232 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Вы павінны змяніць правы на тэчку% s. Каб зрабіць гэта - скарыстайцеся FTP-кліента або наступнай камандай:" #: wp-cache.php:240 msgid "Mobile rewrite rules detected" msgstr "Выяўленая падтрымка мабільных прылад" #: wp-cache.php:241 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Для больш прадуктыўнай працы сайта, Вам варта ўключыць опцыю \" Падтрымка мабільных прылад \"або выдаліць гэтую запіс з правілаў ст. Htaccess. Знайдзіце наступны тэкст (два радкі) \"2.0\\ MMP|240x320\" і выдаліце яго." #: wp-cache.php:241 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "На Вашых звычайных наведвальніках гэта ніяк не адаб'ецца, а вось якія выкарыстоўваюць мабільныя прылады для вэб-серфінгу не будуць атрымліваць кэшаваныя старонкі (калі опцыя адключаная)." #: wp-cache.php:247 #: wp-cache.php:258 msgid "Rewrite rules must be updated" msgstr "Правы на запіс павінны быць абноўленыя" #: wp-cache.php:248 #: wp-cache.php:259 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Неабходныя для працы ўбудовы правы былі змененыя або отсуствіі." #: wp-cache.php:249 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Падтрымка блогам мабільных прылад патрабуе прысутнасці асаблівых правілаў у файле. Htaccess, інакш Вы не зможаце выкарыстоўваць гэтую опцыю. Ніжэй прадстаўлены магчымы спосабы (у парадку складанасці):" #: wp-cache.php:250 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Перакладзіце убудова ў рэжым сярэдняга кэшавання і ўключыце падтрымку мобмльных прылад." #: wp-cache.php:251 #: wp-cache.php:260 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Пракруціць старонку ўніз і націсніце кнопку Абнавіць правілы Mod_Rewrite.\"" #: wp-cache.php:252 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Выдаліце ​​ўсе правілы mod_rewrite з файла% s.htaccess, паміж # BEGIN WPSuperCache і # END WPSuperCache і абновіце старонку (аднаўленне правілаў запусціцца аўтаматычна). " #: wp-cache.php:253 #, php-format msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Дадайце правілы самастойна. Для гэтага адкрыйце у рэдактары файл% s.htaccess і знайдзіце код паміж # BEGIN WPSuperCache і # END WPSuperCache . Вы ўбачыце два падобных блока кода. Адразу пасля радка %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ дадайце наступнае (такіх радкоў дзве, дадайце код і пасля другой): " #: wp-cache.php:266 msgid "Required to serve compressed supercache files properly." msgstr "Неабходна для правільнага сціску файлаў." #: wp-cache.php:266 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Неабходна наладзіць кэшаванне на старонцы ўбудовы. Карыстальнікі браўзэра IE7 будуць бачыць необновленные старонкі з кэша без падтрымкі дадзенага модуля." #: wp-cache.php:266 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Усталюйце дату заканчэння актуальнасці старонак. Карыстальнікі могуць не ўбачыць новую версію кэшаваныя старонкі без дадзенага модуля." #: wp-cache.php:273 msgid "Missing Apache Modules" msgstr "Адсутныя модулі Apache" #: wp-cache.php:274 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Наступныя модулі Apache адсутнічаюць на Вашым серверы. Без іх убудова зможа працаваць толькі ў рэжыме сярэдняга кэшавання. У рэжыме з падтрымкай Super Cache Вашы карыстальнікі могуць бачыць пашкоджаныя старонкі або пратэрмінаваныя іх копіі." #: wp-cache.php:413 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "\"Увага! Вы спрабуеце ўключыць сціск, але модуль zlib.output_compression адключаны. Глядзіце пункт нумар 21 падзелу \"Апісанне праблем \" у файле readme.txt (на англ.) " #: wp-cache.php:501 msgid "WP Super Cache Settings" msgstr "Налады WP Super Cache" #: wp-cache.php:512 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Важна: Mod_rewrite або Legacy caching адключаныя. Па змаўчанні будзе загружацца старонка \" Налады \"." #: wp-cache.php:523 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Файл канфігурацый быў зменены, некаторыя налады не адпавядаюць патрабаванням ўбудовы. Наведайце старонку \" Налады \"каб выправіць гэта." #: wp-cache.php:540 #: wp-cache.php:614 msgid "Caching must be enabled to use this feature" msgstr "Кэшаванне павінна быць уключана, калі Вы хочаце выкарыстоўваць дадзеную опцыю" #: wp-cache.php:542 msgid "Cache Tester" msgstr "Праверка кэшавання" #: wp-cache.php:543 msgid "Test your cached website by clicking the test button below." msgstr "Праверце наладкі кэшавання свайго блога націскам адной кнопкі." #: wp-cache.php:550 #, php-format msgid "Fetching %s to prime cache: " msgstr "Праверка старонкі% s у кэшы:" #: wp-cache.php:552 #: wp-cache.php:559 #: wp-cache.php:566 msgid "OK" msgstr "ЁСЦЬ" #: wp-cache.php:557 #, php-format msgid "Fetching first copy of %s: " msgstr "Праверка першай копіі% s:" #: wp-cache.php:564 #, php-format msgid "Fetching second copy of %s: " msgstr "Праверка второй копіі% s:" #: wp-cache.php:570 msgid "One or more page requests failed:" msgstr "Пры працы з кэшам адбыліся памылкі:" #: wp-cache.php:589 #: wp-cache.php:590 #, php-format msgid "Page %d: %d (%s)" msgstr "Старонка% d:% d (% s)" #: wp-cache.php:596 #, php-format msgid "Page 1: %s" msgstr "Старонка 1:% s" #: wp-cache.php:597 #, php-format msgid "Page 2: %s" msgstr "Старонка 2:% s" #: wp-cache.php:598 msgid "The timestamps on both pages match!" msgstr "Часовыя штампы абодвух варыянтаў старонкі супадаюць!" #: wp-cache.php:600 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Старонкі не супадаюць! Часавы штамп адрозніваецца ці не быў знойдзены!" #: wp-cache.php:606 msgid "Send non-secure (non https) request for homepage" msgstr "Даслаць неабаронены (не па https) запыт для галоўнай старонкі" #: wp-cache.php:607 msgid "Test Cache" msgstr "Праверыць" #: wp-cache.php:632 #: wp-cache.php:755 msgid "Cancel Cache Preload" msgstr "Адмяніць агульнае кэшаванне" #: wp-cache.php:638 msgid "Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete." msgstr "Агульнае кэшаванне па раскладзе адключана. Калі служба цяпер запушчана, яна не будзе завершана пакуль бягучыя 100 старонак не кэшаваць." #: wp-cache.php:649 msgid "Scheduled preloading of cache cancelled." msgstr "Агульнае кэшаванне па раскладзе адключана." #: wp-cache.php:675 #: wp-cache.php:753 msgid "Preload Cache Now" msgstr "Стварыць агульны кэш цяпер" #: wp-cache.php:678 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Агульная кэшаванне адбудзецца праз 10 секунд." #: wp-cache.php:682 #, php-format msgid "Scheduled preloading of cache in %d minutes" msgstr "Агульнае кэшаванне адбудзецца праз% d хвілін" #: wp-cache.php:686 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Пры актывацыі агульнага кэшавання, будзе створана копія для кожнай запісу і старонкі Вашага блога. У гэтым рэжыме ствараюцца статычныя старонкі, якія затым будуць бачыць \" неапазнаныя \"наведвальнікі (напрыклад, пошукавыя боты і іншыя). Гэта можа дапамагчы ў паляпшэнні ўзроўню PR Google, так як у аснове іх алгарытму ляжыць і хуткасць водгуку вэб-сайта. " #: wp-cache.php:687 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Аднак, пры выкарыстанні дадзенага віду кэша ствараецца нашмат больш файлаў. Рэкамендуецца выкарыстоўваць такі тып, калі ў Вас вельмі шмат запісаў (10 тысяч і больш) на блогу. Асабліва гэта важна, калі Вы карыстаецеся паслугамі віртуальнага хостынгу." #: wp-cache.php:688 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "У рэжыме 'Агульнага кэшавання' запланаваная ачыстка смецця будзе выдаляць толькі кэш запісаў простага тыпу (кэш з Super Cache не будзе выдалены). Дадзеная налада рэкамендавана для выкарыстання." #: wp-cache.php:692 #, php-format msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Перагружаць агульны кэш кожныя% s хвілін (ўвядзіце 0, каб адключыць, мінімальнае дапушчальнае кол-у хвілін% d)." #: wp-cache.php:705 msgid "all" msgstr "Ўвесь" #: wp-cache.php:718 #, php-format msgid "Preload %s posts." msgstr "Кэшаваць% s запісу." #: wp-cache.php:725 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Папярэдні рэжым (ачыстка смецця працуе не цалкам, опцыя рэкамендавана да ўключэння.)" #: wp-cache.php:728 msgid "Send me status emails when files are refreshed." msgstr "Адпраўляць мне паведамленні з апавяшчэннямі аб абнаўленні кэша." #: wp-cache.php:733 msgid "Many emails, 2 emails per 100 posts." msgstr "Высокі ўзровень: 2 паведамленні на 100 запісаў." #: wp-cache.php:736 msgid "Medium, 1 email per 100 posts." msgstr "Сярэдні ўзровень: 1 паведамленне на 100 запісаў." #: wp-cache.php:739 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Нізкі ўзровень: 1 e-mail ў пачатку і 1 у канцы кэшавання." #: wp-cache.php:743 #, php-format msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Абнаўленне кэша праз% d г% d мін і% d сек." #: wp-cache.php:744 #, php-format msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Поўнае кэшаванне проихойдет праз% d г% d мін і% d сек." #: wp-cache.php:750 #, php-format msgid "Currently caching from post %d to %d." msgstr "У дадзены моманты кэшуюцца запісы з% d па% d." #: wp-cache.php:753 msgid "Update Settings" msgstr "Абнавіць налады" #: wp-cache.php:761 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Агульнае кэшаванне адключана. Калі ласка, уключыце поўны рэжым працы ўбудовы або звернецеся да адміністратара сервера." #: wp-cache.php:776 #: wp-cache.php:865 msgid "Caching" msgstr "Статут кэшавання" #: wp-cache.php:780 msgid "Cache hits to this website for quick access." msgstr "Кэшаваць хіты сайта для паскарэння доступу." #: wp-cache.php:780 #: wp-cache.php:781 #: wp-cache.php:795 #: wp-cache.php:799 #: wp-cache.php:802 #: wp-cache.php:803 #: wp-cache.php:868 msgid "Recommended" msgstr "Рэкамендавана" #: wp-cache.php:781 msgid "Use mod_rewrite to serve cache files." msgstr "Выкарыстоўваць mod_rewrite для абслугоўвання кэша." #: wp-cache.php:782 msgid "Use PHP to serve cache files." msgstr "Выкарыстоўваць PHP для абслугоўвання кэша." #: wp-cache.php:783 msgid "Legacy page caching." msgstr "Спрошчанае кэшаванне." #: wp-cache.php:784 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching." msgstr "Выкарыстанне mod_rewrite дапаможа зрабіць працу блога хутчэй, чым PHP (хоць і гэты варыянт таксама не такі павольны). Гэты рэжым прасцей і зручней, але пачаткоўцу карыстачу лепш выкарыстоўваць кэшаванне PHP." #: wp-cache.php:790 msgid "Miscellaneous" msgstr "Рознае" #: wp-cache.php:795 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Сціскаць файлы кэша каб паскорыць працу." #: wp-cache.php:796 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Сціск кэша адключана па змаўчанні, так як можа некарэктна працаваць на некаторых хостынгах. Уключэнне або Адключэнне дадзенай опцыі аўтаматычна чысціць часовы кэш." #: wp-cache.php:799 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "Памылка 304. Дадзеная памылка ўзнікае тады, калі старонка не была зменена з часу мінулага запыту." #: wp-cache.php:800 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "Падтрымка памылкі 304 адключаная па змаўчанні (з-за праблем некаторых сэрвісаў)." #: wp-cache.php:802 msgid "Don’t cache pages for known users." msgstr "Не кэшаваць старонкі для вядомых карыстальнікаў.\"" #: wp-cache.php:803 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Аўта перабудова кэшу. Госці блога ўбачаць састарэлыя версіі старонак кэша пакуль новыя будуць генеравацца." #: wp-cache.php:804 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Расказаць ўсім, што Вы карыстаецеся убудовай WP Super Cache (паведамленне будзе размешчана ў \" склепе \"сайта)!" #: wp-cache.php:810 #: wp-cache.php:957 #: wp-cache.php:1473 msgid "Advanced" msgstr "Налады" #: wp-cache.php:814 msgid "Mobile device support." msgstr "Падтрымка мабільных прылад" #: wp-cache.php:815 msgid "Clear all cache files when a post or page is published." msgstr "Ачышчаць кэш калі новая запіс або старонка апублікаваная." #: wp-cache.php:816 msgid "Only refresh current page when comments made." msgstr "Перагружаць старонку пры даданні новага каментара да яе" #: wp-cache.php:817 msgid "List the newest cached pages on this page." msgstr "Стварыць спіс старонак у кэшы (выводзіцца на гэтай старонцы)" #: wp-cache.php:819 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Блакаванне файлаў. Вам хутчэй за ўсё не спатрэбіцца дадзеная опцыя, але яна можа вырашыць праблему маламагутных хостынгаў. Увага! Уключэнне опцыі, у рэдкіх выпадках, можа выклікаць праблемы ў працы блога!\"" #: wp-cache.php:822 msgid "Use object cache to store cached files." msgstr "Выкарыстоўваць аб'екты кэша для захоўвання кэшаваных файлаў." #: wp-cache.php:822 msgid "(Experimental)" msgstr "(Эксперыментальныя налады)" #: wp-cache.php:829 msgid "Note:" msgstr "Важна:" #: wp-cache.php:831 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Деактивируя убудова, пераканайцеся што тэчка% s даступная для запісу ў наладах Вашага сервера, каб файлы плагіна advanced-cache.php і cache-config.php былі выдаленыя ў аўтаматычным рэжыме (таксама праверце наяўнасць правоў на запіс для гэтых двух файлаў)." #: wp-cache.php:832 #, php-format msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Для даведкі глядзіце readme.txt (дакумент на англ.). Там Вы знойдзеце карысную інфармацыю па выкарыстанню і выдаленню плагіна WP Super Cache. " #: wp-cache.php:833 #, php-format msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Усё яшчэ патрэбна дапамога? Глядзіце афіцыйны чаво па плагіна Super Cache (па-ангельску). Таксама, Вы можаце задаць сваё пытанне на форумах тых. падтрымкі (па-ангельску), або азнаёміцца ​​з праблемамі іншых карыстальнікаў і прапанаванымі ім рашэннямі. " #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "Абнавіць" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "Дапушчальныя імёны & Забароненыя адрасы" #: wp-cache.php:868 msgid "Caching On" msgstr "Кэшаванне ўключана" #: wp-cache.php:869 msgid "Caching Off" msgstr "Кэшаванне выключана" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Важна: рэкамендуецца ўключыць PHP кэшаванне, аўто перабудову кэша і падтрымку для мабільных прылад" #: wp-cache.php:880 msgid "Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Увага: Сярод правілаў mod_rewrite выяўленыя правілы ад Supercache. Для працы з кэшам будуць выкарыстаны менавіта гэтыя правілы. Каб выдаліць іх, Вам трэба ўручную адрэдагаваць файл. Htaccess." #: wp-cache.php:892 msgid "Make WordPress Faster" msgstr "Зрабі свой блог хутчэй!" #: wp-cache.php:893 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "Дадатковы модуль %1$s створаны і абнаўляецца аўтарам %2$s пры падтрымцы многіх іншых." #: wp-cache.php:894 #, php-format msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Наведайце блог аўтара плагіна %1$s і яго фотаблог на %2$s." #: wp-cache.php:895 #, php-format msgid "Please say hi to him on %s too!" msgstr "Калі ласка, наведайце% s аўтара!" #: wp-cache.php:903 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Старонак ў кэшы з %1$s: %2$s" #: wp-cache.php:904 msgid "Newest Cached Pages:" msgstr "Новае ў кэшы:" #: wp-cache.php:908 #, php-format msgid "Cached %s seconds ago" msgstr "Паведамленні ў кэш% s секунд назад" #: wp-cache.php:911 msgid "(may not always be accurate on busy sites)" msgstr "(Спіс не рэкамендаваны для вялікіх сайтаў)" #: wp-cache.php:930 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Кэшаванне адбываецца за кошт PHP файлаў, якія захоўваюцца ў тэчцы ўбудовы. Яны загружаюцца пры ўключэнні рэжыму Supercache. Загрузка адбываецца нашмат часцей, чым для астатніх убудоў WordPress." #: wp-cache.php:931 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Для выкарыстання дадзенай опцыі трэба ведаць не толькі PHP, але і WordPress (не на пачатковым узроўні)." #: wp-cache.php:941 msgid "Available Plugins" msgstr "Даступныя ўбудовы" #: wp-cache.php:957 msgid "Easy" msgstr "Кэш" #: wp-cache.php:957 msgid "Tester & Contents" msgstr "Праверка" #: wp-cache.php:957 msgid "Preload" msgstr "Агульны кэш" #: wp-cache.php:957 msgid "Plugins" msgstr "Даданыя модулі" #: wp-cache.php:957 msgid "Debug" msgstr "Абслугоўванне" #: wp-cache.php:984 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Увага: Праверка правілаў WP Super Cache mod_rewrite адключаная для блогаў сеткі пакуль не будзе запушчана на галоўным блогу . " #: wp-cache.php:986 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Увага: Праверка правілаў WP Super Cache mod_rewrite адключаная для блогаў сеткі пакуль не будзе запушчана на галоўным блогу . " #: wp-cache.php:996 msgid "Mod Rewrite Rules" msgstr "Модуль Mod Rewrite" #: wp-cache.php:1002 msgid "WordPress MU Detected" msgstr "Знойдзены WordPress MU!" #: wp-cache.php:1002 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "На жаль, mod_rewrite немагчыма абнавіць у аўтаматычным рэжыме ў WordPress MU. Вам прыйдзецца ўручную зрабіць гэта: адкрыйце файл. Htaccess (размешчаны ў каранёвай дырэкторыі блога) і дадайце наступныя правілы ў яго." #: wp-cache.php:1004 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite не можа быць абноўлены!" #: wp-cache.php:1005 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Для карэктнай працы, у Вашым файле% s.htaccess павінны быць прапісаны маркеры BEGIN, і END. Паміж імі знаходзяцца асноўныя правілы WordPress mod_rewrite, прыклад:" #: wp-cache.php:1007 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Абнавіце старонку калі скончыце рэдагаванне файла. Htaccess." #: wp-cache.php:1011 msgid "Thank you for upgrading." msgstr "Дзякуй за абнаўленне." #: wp-cache.php:1011 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "З моманту апошняй усталяванай версіі плагіна правілы mod_rewrite былі змененыя. На жаль, Вам давядзецца ўручную выдаліць старыя правілы перш чым новыя запрацуюць. Абнавіце гэтую старонку калі скончыце рэдагаваць файл. Htaccess. Калі Вы жадаеце цалкам абнавіць усе самі, то заменіце наступны радок:%1$s на гэтую:%2$s. Адзінае адрозненне - гэта замена \"HTTP_COOKIE \" на \"HTTP: Cookie \" і \"wordpressuser \" на \"wordpress \". Гэтыя перамены звязаны з новай версіяй WordPress 02/05 . Вядома Вы можаце працягваць працаваць са старымі версіямі, калі хопіць адвагі;) " #: wp-cache.php:1015 msgid "Trailing slash check required." msgstr "Патрабуецца праверка trailing slash." #: wp-cache.php:1015 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Здаецца, усе спасылкі Вашага блога заканчваюцца сімвалам \"/\". На жаль, як толькі Вы ўсталявалі гэты дадатковы модуль, спрацавала опцыя, выявілая копіі спасылак без знака \"/\" на канцы, і цяпер яна не можа ажыццявіць перанакіраванне на верны адрас. Каб гэта выправіць гэта, Вы павінны адрэдагаваць файл. htaccess і дадаць два новыя правілы да групы асноўных правілаў плагіна Supercache: " #: wp-cache.php:1017 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Каб паглядзець поўны спіс якія працуюць правілаў, націсніце кнопку ніжэй \" Паглядзець правілы mod_rewrite \"." #: wp-cache.php:1031 msgid "Mod Rewrite rules updated!" msgstr "Правілы mod_rewrite абноўлены!" #: wp-cache.php:1032 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "Файл% s.htaccess быў паспяхова абноўлены, неабходныя правілы mod_rewrite былі дададзеныя. Калі ласка, праверце іх. Яны павінны выглядаць так:" #: wp-cache.php:1034 msgid "Mod Rewrite rules must be updated!" msgstr "Правілы mod_rewrite павінны быць абноўлены!" #: wp-cache.php:1035 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Ваш файл% s.htaccess недаступны для запісу (у наладах сервера) і не можа быць абноўлены ў аўтаматычным рэжыме. Вы павінны ўручную дадаць новыя правілы да асноўных правілах WordPress так, як паказана ніжэй:" #: wp-cache.php:1040 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Правілы mod_rewrite для плагіна WP Super Cache былі выяўленыя ў файле% s.htaccess.
    Націсніце на адпаведную кнопку, каб паглядзець радкі. Калі Вы толькі што абнавілі убудова, праверце ўсе правілы. " #: wp-cache.php:1043 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "Паміж правіламі ў Вашым файле. Htaccess і правіламі самога плагіна выяўленыя неадпаведнасці. Гэта можа быць проста лішні сімвал ў радку, але Вы павінны асабіста параўнаць арыгінальныя правілы са сваімі як мага хутчэй. Націсніце на кнопку 'Абнавіць правілы Mod_Rewrite', каб зрабіць гэта ў аўтаматычным рэжыме. " #: wp-cache.php:1046 msgid "View Mod_Rewrite Rules" msgstr "Паглядзець правілы mod_rewrite" #: wp-cache.php:1050 #: wp-cache.php:2287 #, php-format msgid "Rules must be added to %s too:" msgstr "Правілы павінны быць таксама дададзены да% s:" #: wp-cache.php:1058 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Правілы для Gzip-сціску дададзеныя ў файл% s.htaccess." #: wp-cache.php:1065 msgid "Fix Configuration" msgstr "Аднавіць стандартныя налады" #: wp-cache.php:1068 msgid "Restore Default Configuration" msgstr "Аднавіць налады па змаўчанні" #: wp-cache.php:1076 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Праверка каментарыяў ўключана. Перш чым Вашы каментары будуць апублікаваныя пройдзе нейкі час." #: wp-cache.php:1101 msgid "Lock Down:" msgstr "Закрыты рэжым:" #: wp-cache.php:1101 msgid "Disabled" msgstr "Адключаны" #: wp-cache.php:1101 msgid "Enabled" msgstr "Уключаны" #: wp-cache.php:1102 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Падрыхтуйце свой блог да запланаваных усплёскаў наведвальнасці, актываваўшы дадзены рэжым. У актыўным стане размяшчэнне новых каментароў і запісаў НЕ будзе абнаўляць статычныя файлы ў кэшы." #: wp-cache.php:1103 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Распрацоўнікам: Зрабіце свой уласны убудова закрытага рэжыму сумяшчальным з нашым, дадаўшы зменную \" WPLOCKDOWN\". Прыведзены ніжэй код дапаможа Вам адаптаваць свой ўбудова да налад нашага Рэжыму." #: wp-cache.php:1105 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Выбачайце, мой блог часова недаступны. Зайдзіце пазней" #: wp-cache.php:1109 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "Ваш блог выкарыстоўвае Закрыты рэжым. Новыя каментары не абнаўляюць ўсе статычныя элементы кэша." #: wp-cache.php:1111 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "Ваш блог не выкарыстоўвае Закрыты рэжым. Апошнія каментарыі абнаўляюць ўсе статычныя элементы кэша." #: wp-cache.php:1117 msgid "Lock Down" msgstr "Закрыты рэжым" #: wp-cache.php:1125 msgid "Directly Cached Files" msgstr "Прамое кэшаванне старонак" #: wp-cache.php:1183 #, php-format msgid "%s removed!" msgstr "%s выдалены!" #: wp-cache.php:1191 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Вы павінны дазволіць запіс для% s. Але так як гэта патэнцыйная ўразлівасць, пасля абнаўлення старонкі вярніце правы на чытанне." #: wp-cache.php:1193 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "Директрия% s даступная для запісу. Вам варта змяніць яе права на \" Толькі чытанне \"." #: wp-cache.php:1207 msgid "Existing direct page" msgstr "Старонка існуе" #: wp-cache.php:1207 msgid "Delete cached file" msgstr "Выдаліць файлы з кэша" #: wp-cache.php:1212 msgid "Add direct page:" msgstr "Дадаць старонку ў кэш:" #: wp-cache.php:1214 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Дадзены кэш ствараецца прама з папкі, дзе знаходзіцца Ваш блог (тэчка% s). Гэтая опцыя карысная толькі тады, калі чакаецца вялікі прыток наведвальнікаў з больш папулярнага сайта на пэўную старонку або запіс Вашага." #: wp-cache.php:1216 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Напрыклад: каб дадаць у кэш старонцы на %1$s about /, трэба прапісаць %1$s about / ці / about /. Кэш для старонкі будзе створаны адразу ж пасля першага да яе звароту госцем." #: wp-cache.php:1217 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Каб выдаліць старонку з такога кэша, ачысціце тэкставае поле і выдаліце ​​файлы кэша." #: wp-cache.php:1222 msgid "Update Direct Pages" msgstr "Абнавіць стрницы" #: wp-cache.php:1260 msgid "Expiry Time & Garbage Collection" msgstr "Пратэрмінаваныя старонкі & Ачыстка смецця" #: wp-cache.php:1262 msgid "Expire time:" msgstr "Актуальнасць кэшу:" #: wp-cache.php:1263 msgid "seconds" msgstr "Секунд" #: wp-cache.php:1264 msgid "Garbage Collection" msgstr "Ачыстка смецця" #: wp-cache.php:1264 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Калі час актуальнасці кэша больш за 1800 секунд (паўгадзіны), то ачыстка смецця будзе запускацца кожныя 10 хвілін." #: wp-cache.php:1265 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Паверка і выдаленне пратэрмінаваных старонак кэша займае час, але і пакідаць такія файлы ў сістэме не варта. На вялікіх блогах трэба выстаўляць \" час жыцця \" кожнай копіі 300 секунд. Вы можаце паэксперыментаваць з наладай і паглядзець, колькі пратэрмінаваных копій старонак застаецца ў кэшы на працягу дня. Аптымальнае лік такіх старонак не больш за 500. Выкарыстоўваючы кэшаванне з mod_rewrite або PHP, Вы зможаце павялічыць колькасць кэшируемых старонак. " #: wp-cache.php:1266 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Усталюйце значэнне на 0, каб адключыць Ачыстку смецця." #: wp-cache.php:1267 msgid "Change Expiration" msgstr "Змяніць час жыцця копіі" #: wp-cache.php:1311 msgid "Rejected User Agents" msgstr "Пошукавыя і іншыя боты" #: wp-cache.php:1312 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Каб забараніць плагіна кэшаваць запыты ад пошукавых ботаў і іншых сеткавых робатаў, увядзіце іх назвы ў полі ніжэй (па адным у радку). Калі копія старонкі ўжо існуе ў кэшы Super Cache, то яна ўсё роўна будзе адпраўлена боту." #: wp-cache.php:1319 msgid "Save UA Strings" msgstr "Захаваць наладкі" #: wp-cache.php:1342 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Не кэшаваць старонкі наступных тыпаў. Паспрабуйцце звярнуцца да Артыкулам Кодэкса WP (па-ангельску), каб даведацца больш падрабязна пра тыпы старонак. " #: wp-cache.php:1345 msgid "Single Posts" msgstr "Запісы" #: wp-cache.php:1346 msgid "Pages" msgstr "Старонкі" #: wp-cache.php:1347 msgid "Front Page" msgstr "Асноўная старонка" #: wp-cache.php:1348 msgid "Home" msgstr "Хатняя старонка" #: wp-cache.php:1349 msgid "Archives" msgstr "Архівы" #: wp-cache.php:1350 msgid "Tags" msgstr "Пазнакі" #: wp-cache.php:1351 msgid "Category" msgstr "Рубрыкі" #: wp-cache.php:1352 msgid "Feeds" msgstr "Фиды" #: wp-cache.php:1353 msgid "Search Pages" msgstr "Старонкі пошуку" #: wp-cache.php:1355 #: wp-cache.php:1483 msgid "Save" msgstr "Захаваць" #: wp-cache.php:1372 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Поле ніжэй Вы таксама можаце запоўніць фрагментамі адрасоў старонак (або груп старонак, напрыклад, архіў за год / месяц і г.д.), якія не будуць кэшавацца. Плагін будзе сканаваць адрасы старонак на прадмет наяўнасці ў іх фрагментаў, указаных ніжэй, перад кэшаваннем. " #: wp-cache.php:1378 msgid "Save Strings" msgstr "Захаваць спіс забароненых фрагментаў" #: wp-cache.php:1394 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Поле ніжэй Вы можаце запоўніць назвамі файлаў якія будуць кэшаваць, нават калі ў іх назве ёсць забароненых да кэшавання фрагменты." #: wp-cache.php:1400 msgid "Save Files" msgstr "Захаваць спіс файлаў" #: wp-cache.php:1445 msgid "Currently logging to: " msgstr "Рэжым запісаны на:" #: wp-cache.php:1455 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Тут Вы можаце вырашыць некаторыя праблемы, якія ўзнікаюць пры працы з убудовай, з дапамогай адладкі. Вы можаце запісваць службовую інфармацыю (логі) у файлы дырэкторыі кэша." #: wp-cache.php:1456 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Атрымаць доступ да файла лога проста, але пры ачыстцы кэша лог таксама будзе выдалены." #: wp-cache.php:1460 msgid "Debugging" msgstr "Рэжым адладкі" #: wp-cache.php:1461 msgid "Logging Type" msgstr "Тып ўваходу" #: wp-cache.php:1461 msgid "Email" msgstr "Email" #: wp-cache.php:1462 msgid "file" msgstr "Файл" #: wp-cache.php:1463 msgid "IP Address" msgstr "Адрас IP" #: wp-cache.php:1463 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(Запісвае звароту толькі з гэтага IP. Ваш IP -% s)" #: wp-cache.php:1464 msgid "Log level" msgstr "Узровень логу" #: wp-cache.php:1470 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = найменшы, 5 = найбольшы, можа выклікаць болшую нагрузку на сервер)" #: wp-cache.php:1473 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "У асабліва рэдкіх выпадках на блогу могуць здарыцца дзве праблемы:
    1. Замест галоўнай старонкі карыстальнікі будуць бачыць прапанову загрузіць. Zip архіў з ёй
    2. Замест галоўнай старонкі можа быць дададзеная ў кэш зусім іншая (толькі ў выпадку, калі Ваш бог выкарыстоўвае наступную структуру спасылак /% category% /% postname% /).
    " #: wp-cache.php:1474 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "I'm 99% certain! Памылкі, якія могуць паўстаць пры працы з WP Super Cache, не звязаныя з самім убудовай. Яны ўзнікаюць у рэдкіх выпадках, але Вы можаце падстрахавацца, запусціўшы аўтаматычную праверку блога кожныя 5 хвілін. У выпадку памылкі, Вам будзе адпраўлена паведамленне. " #: wp-cache.php:1476 msgid "Check front page every 5 minutes." msgstr "Правяраць галоўную старонку кожныя 5 хвілін." #: wp-cache.php:1477 msgid "Front page text" msgstr "Ключавой тэкст" #: wp-cache.php:1477 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Калі ласка, увядзіце тэкст які ўбудова будзе шукаць на галоўнай старонцы. Калі тэкст не будзе знойдзены, то кэш аўтаматычна ачысціцца. Пакіньце поле пустым каб адключыць опцыю." #: wp-cache.php:1478 msgid "Clear cache on error." msgstr "Ачышчаць кэш пры памылцы." #: wp-cache.php:1479 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Паведаміць адміністратару блога па завяршэння праверкі (карысна пры тэставанні на памылкі)." #: wp-cache.php:1493 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Памылка: сціск GZIP ўключана, адключыце яго калі хочаце запусціць wp-cache." #: wp-cache.php:1540 #: wp-cache.php:1702 msgid "Warning" msgstr "Увага" #: wp-cache.php:1540 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "Сціск GZIP ўключана ў наладах WordPress, убудова не будзе працаваць да таго часу, пакуль Вы не адключыце gzip." #: wp-cache.php:1598 #: wp-cache.php:1603 #: wp-cache.php:1635 #: wp-cache.php:1640 #: wp-cache.php:1646 msgid "Error" msgstr "Памылка" #: wp-cache.php:1598 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Тэчка ($ cache_path) не існуе і не можа быць створана ў аўтаматычным рэжыме. Праверце правы доступу да% s." #: wp-cache.php:1603 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Тэчка (%1$s) або %2$s павінна быць даступная для запісу. Перепроверьте правы доступу." #: wp-cache.php:1635 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Канфігурацыйны файл WP-Cache (% s) можа быць ня дзейнічае і недаступны для запісу. Калі ласка, выдаліце яго ўручную і абновіце старонку." #: wp-cache.php:1640 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Канфігурацыйны файл адсутнічае, а тэчка %1$s (%2$s) недаступная для запісу. Праверце правы доступу." #: wp-cache.php:1646 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Файл WP-Cache (% s) не быў знойдзены. Праверце, завяршылі Вы ўстаноўку ўбудовы." #: wp-cache.php:1702 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php не існуе або не можа быць абноўлены ў аўтаматычным рэжыме." #: wp-cache.php:1703 msgid "1. If it already exists please delete the file first." msgstr "1. Калі ён ужо існуе ў тэчках Вашага блога, выдаліце ​​яго." #: wp-cache.php:1704 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Зменіце правы доступу да %1$s, каб можна было запісаць дадзеныя ў аўтаматычным рэжыме (правы павінны быць: chmod 777 %1$s), праверце правільнасць зададзеных правоў і абновіце старонку. Гэта часовае ўмова, пасля абнаўлення старонкі правы доступу трэба вярнуць на ранейшыя (з 777 на 755). " #: wp-cache.php:1705 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Абнавіце старонку, файл% s / advanced-cache.php абновіцца сам" #: wp-cache.php:1706 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Калі гэта не спрацавала, пераканайцеся што% s / advanced-cache.php сапраўды не існуе:" #: wp-cache.php:1707 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Адкрыйце файл %1$s$wp_cache_file ў тэкставым рэдактары.
  • 2. Зменіце радок CACHEHOME на %2$s
  • 3. Захавайце файл і скапіруйце ў %3$s, затым абновіце старонку.
    • " #: wp-cache.php:1730 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    Параметр WP_CACHE не актываваны

    Дадзены параметр павінен быць актываваны для таго, каб WordPress мог карэктна працаваць з файламі кэша. У дадзены момант ён адключаны. Каб уключыць яго, адкрыйце файл wp-config.php і дадайце ў яго наступны радок:

    define('WP_CACHE', true);

    " #: wp-cache.php:1732 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "\"Памылка: Зменная WP_CACHE ня актываваная ў файле агульных канфігурацый wp-config.php . " #: wp-cache.php:1733 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Выпраўце файл наладак код %s і дадайце наступную пункту:
    define('WP_CACHE', true);
    Інакш, WP-Cache не зможа запусціцца. " #: wp-cache.php:1737 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    Пераменная WP_CACHE дададзеная ў файл канфігурацый wp-config.php

    Калі Вы да гэтага часу бачыце дадзенае паведамленне, то паспрабуйцце звярнуцца з пунктам 5 чаво (на англ.). Радок з WP_CACHE павінна быць размешчаная вышэй. " #: wp-cache.php:1759 msgid "Cache Contents" msgstr "Стан кэша" #: wp-cache.php:1762 msgid "Object cache in use. No cache listing available." msgstr "Спіс кэшавання недаступны." #: wp-cache.php:1786 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Выдаленне файлаў Super Cache:% s
    " #: wp-cache.php:1803 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Выдаленне файлаў WP-Cache:% s
    " #: wp-cache.php:1868 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Статыстыка аб'ектыў ў кэшы НЕ ствараецца аўтаматычна. Каб абнавіць яе ўручную націсніце на спасылку ніжэй." #: wp-cache.php:1869 msgid "Regenerate cache stats" msgstr "Абнавіць статыстыку кэша" #: wp-cache.php:1871 #, php-format msgid "Cache stats last generated: %s minutes ago." msgstr "Статыстыка аб'ектаў у кэшы апошні раз створана:% s мін таму." #: wp-cache.php:1877 msgid "WP-Cache" msgstr "Стан WP-Cache" #: wp-cache.php:1878 #: wp-cache.php:1894 #, php-format msgid "%s Cached Pages" msgstr "%s старонак у кэшы" #: wp-cache.php:1879 #: wp-cache.php:1899 #, php-format msgid "%s Expired Pages" msgstr "%s старонак пратэрмінаваны" #: wp-cache.php:1893 msgid "WP-Super-Cache" msgstr "Стан WP-Super-Cache" #: wp-cache.php:1904 msgid "Fresh WP-Cached Files" msgstr "Новыя файлы WP-Cache" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "URI" msgstr "АДРАС" #: wp-cache.php:1905 #: wp-cache.php:1921 msgid "Key" msgstr "Ключ" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Age" msgstr "Узрост" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Delete" msgstr "Выдаліць" #: wp-cache.php:1920 msgid "Stale WP-Cached Files" msgstr "Старыя файлы WP-Cache" #: wp-cache.php:1936 msgid "Fresh Super Cached Files" msgstr "Новыя файлы Super Cache" #: wp-cache.php:1952 msgid "Stale Super Cached Files" msgstr "Старыя файлы Super Cache" #: wp-cache.php:1968 msgid "Hide file list" msgstr "Прыбраць спіс" #: wp-cache.php:1970 msgid "Too many cached files, no listing possible." msgstr "Занадта шмат аб'ектаў у кэшы, стварэнне спісу немагчыма." #: wp-cache.php:1972 msgid "List all cached files" msgstr "Спіс кэшаваных файлаў" #: wp-cache.php:1978 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "\"Ачыстка смецця
    Папярэдняя ачыстка была% s хвілін назад
    " #: wp-cache.php:1979 #, php-format msgid "Next GC in %s minutes" msgstr "Наступная ачыстка будзе праз% s хвілін" #: wp-cache.php:1982 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Пратэрмінаваны кэш - гэта старонкі, створаныя больш чым% s секунд таму. Не гледзячы на ​​свой статус, яны выкарыстоўваюцца ў агульным кэшы і перыядычна выдаляюцца." #: wp-cache.php:1993 msgid "Delete Expired" msgstr "Выдаліць пратэрмінаваны кэш" #: wp-cache.php:1999 #: wp-cache.php:2011 #: wp-cache.php:2174 msgid "Delete Cache" msgstr "Выдаліць увесь кэш" #: wp-cache.php:2011 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Выдаліць файлы Super Cache (у новым акне)" #: wp-cache.php:2150 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s ўдзячны плагіна %2$s за проделаннную працу" #: wp-cache.php:2183 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "Плагін WP Super Cache павінен быць наладжаны! Каб актываваць яго і наладзіць, перайдзіце на старонку кіравання убудовай. " #: wp-cache.php:2189 msgid "Settings" msgstr "Налады" #: wp-cache.php:2199 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "Плагін WP Super Cache не актываваны. Каб актываваць яго, перайдзіце на старонку кіравання убудовай. " #: wp-cache.php:2218 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Галоўная старонка сціснута з дапамогай gzipped! Выдаліце ​​кэш!" #: wp-cache.php:2218 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Адбылася памылка! Наведайце% s каб выдаліць кэш!" #: wp-cache.php:2221 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Галоўная старонка сціснута з дапамогай gzipped! Кэш выдалены!" #: wp-cache.php:2221 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Увесь кэш для Вашага блога быў ачышчаны, так як убудова заўважыў памылку на галоўнай старонцы (яна запампоўваліся архівам). Каб праверыць кэш, наведайце гэтую стрницу% s." #: wp-cache.php:2228 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Кэш галоўнай старонкі змяшчае памылку! Выдаліце ​​кэш!" #: wp-cache.php:2228 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Адбылася памылка, на галоўнай старонцы Вашага блога не быў выяўлены ключавой тэкст \"%2$s\"! Каб выправіць памылку, наведайце гэтую старонку %1$s і ўручную ачысьціць кэш." #: wp-cache.php:2231 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Галоўная старонка адлюстроўваецца з памылкай! Кэш выдалены!" #: wp-cache.php:2231 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Адбылася памылка, на галоўнай старонцы Вашага блога не быў выяўлены ключавой тэкст \"%2$s\"! Наведайце гэтую старонку %1$s каб праверыць кэш." #: wp-cache.php:2236 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Галоўная старонка праверана!" #: wp-cache.php:2236 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "Плагін WP Super Cache толькі што праверыў галоўную старонку Вашага блога на прадмет памылак. Каб адключыць апавяшчэння і праверку наведаеце гэтую старонку% s." #: wp-cache.php:2279 msgid "Cannot update .htaccess" msgstr "Не магу абнавіць файл. Htaccess" #: wp-cache.php:2279 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Файл %s.htaccess не можа быць абноўлены ў аўтаматычным рэжыме. Каб выправіць гэта задайце неабходныя для запісу правы доступу да яго. " #: wp-cache.php:2279 msgid "Refresh this page when the file permissions have been modified." msgstr "Абнавіце старонку калі неабходныя правы доступу будуць зададзены." #: wp-cache.php:2279 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Вы таксама можаце рэдагаваць файл %s.htaccess ўручную і асабіста дадаць неабходныя правілы (да наяўных там правілаў WordPress): " #: wp-cache.php:2283 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Каб убудова мог правільна працаваць з статычнымі html файламі, Вы павінны дадаць у файл %s.htaccess правілы модуля mod_rewrite " #: wp-cache.php:2284 msgid "You can edit the file yourself add the following rules." msgstr "Вы можаце ўручную адрэдагаваць файл і дадаць неабходныя правілы." #: wp-cache.php:2285 msgid " Make sure they appear before any existing WordPress rules. " msgstr "Праверце што яны ідуць перад усімі ўжо існуючымі ў дакуменце правіламі WordPress." #: wp-cache.php:2293 msgid "Update Mod_Rewrite Rules" msgstr "Абнавіць правілы mod_rewrite" #: wp-cache.php:2389 #, php-format msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Агульная кэшаванне пачалося" #: wp-cache.php:2391 #, php-format msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Абнаўленне кэша запісаў з %2$d па %3$d" #: wp-cache.php:2402 #, php-format msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d кэш запісаў абноўлены" #: wp-cache.php:2402 msgid "Refreshed the following posts:" msgstr "Наступныя запісы абноўлены:" #: wp-cache.php:2411 #, php-format msgid "Scheduling next preload refresh in %d minutes." msgstr "Наступнае запланаванае абнаўленне агульнага кэша праз% d хвілін." #: wp-cache.php:2421 #, php-format msgid "[%s] Cache Preload Completed" msgstr "[%s] Агульная кэшаванне завершана" #: wp-cache.php:2421 msgid "Cleaning up old supercache files." msgstr "Выдаляць старыя файлы з кэша Super Cache." #: wp-cache.php:2462 #, php-format msgid "[%s] Preload may have stalled." msgstr "[%s] Агульная кэшаванне магло быць спынена." #: wp-cache.php:2462 #, php-format msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Агульнае кэшаванне было перазапушчаныя. \n" "%s" #~ msgid "" #~ "Scroll down this page and click the Update Mod_Rewrite Rules button." #~ msgstr "" #~ "Пролистайте страницу вних и нажмите кнопку Обновить правила " #~ "Mod_Rewrite." #~ msgid "WP Super Cache Manager" #~ msgstr "Управление плагином WP Super Cache" #~ msgid "Why your configuration may not be changed" #~ msgstr "Почему конфигурации не могут быть изменены" #~ msgid "Why" #~ msgstr "Почему" #~ msgid "ON" #~ msgstr "ВКЛ" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "Плагины WP Cache и Super Cache включены" #~ msgid "HALF ON" #~ msgstr "РАБОТАЕТ НАПОЛОВИНУ" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Плагин Super Cache отключен, работает только кэшировани WP-Cache" #~ msgid "OFF" #~ msgstr "ВЫКЛ" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "Плагины WP Cache и Super Cache отключены" #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "Восстановление кэша. При включенной опции, гости сайта будут получать " #~ "старые страницы из плагина Super Cache, пока формируются новые. " #~ "Рекомендуется использовать данную опцию только для очень " #~ "посещаемых блогов, где много комментариев. После включения опции в " #~ "настройках \"прямое кэширование страниц\" и \"закрытый режим\" нет нужды " #~ "(они устаревают)" #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "Создавать список новых кэшированных страниц (использовать на свой страх и " #~ "риск, может затормозить сайты с большим количеством посетителей)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s действительно ускоряет Ваш блог. Вы можете сделать его еще " #~ "быстрее*, купив мне подарочную карту сервиса " #~ "Amazon! Можете выбрать \"%3$s\" любое значение, какое хотите. Каждая " #~ "копейка поможет мне!" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "Если Вы не хотите иметь дело с Amazon , то можно сделать пожертвование " #~ "через PayPal. Нажмите кнопку \"Пожертвовать\" или выберите подарок для " #~ "меня из моего списка желаний." #~ msgid "Thanks in advance!" #~ msgstr "Заранее благодарю!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Ладно, он не будет быстрее, но Вы все равно сделаете автора плагина очень " #~ "счастливым!" #~ msgid "Don’t show me this again." #~ msgstr "Не показывать больше это сообщение." #~ msgid "Hide" #~ msgstr "Спрятать" #~ msgid "" #~ "He blogs at %1$s and posts photos at %2$s. He would really appreciate a " #~ "donation to encourage development of this plugin." #~ "
    Even a penny will help." #~ msgstr "" #~ "Блог автора - %1$s, фотоблог - %2$s. Автор плагина будет благодарен любой " #~ "поддержке от Вас.
    Даже копейка может помочь в " #~ "его работе." #~ msgid "Super Cache Compression" #~ msgstr "Сжатие кэша Super Cache" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "" #~ "Сжатие кэша отключено по умолчанию в режиме РАБОТАЕТ НАПОЛОВИНУ." #~ msgid "Super Cache compression is now disabled." #~ msgstr "Сжатие кэша Super Cache теперь отключено." #~ msgid "Super Cache compression is now enabled." #~ msgstr "Сжатие кэша Super Cache теперь включено." #~ msgid "Update Compression" #~ msgstr "Обновить настройки сжатия" #~ msgid "Debug Settings" #~ msgstr "Параметры отладки" #~ msgid "" #~ "

    WP_CACHE constant in wp-config.php set to false

    The WP_CACHE " #~ "constant is defined in your wp-config.php but must be set to true, not " #~ "false for this plugin to work correctly.

    " #~ msgstr "" #~ "

    Значение для WP_CACHE в конфигурационном файле WordPrees wp-config." #~ "php установлено на \"false\"

    Чтобы плагин заработал, значение " #~ "WP_CACHE в wp-config.php нужно поставить на \"true\".

    " #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "" #~ "Вы должны вручную отредактировать файл и добавить необходимые правила." languages/wp-super-cache-ru_RU.po000066600000315033152133035240012736 0ustar00# Translation of the WordPress plugin by . # Copyright (C) 2010 # This file is distributed under the same license as the package. # FIRST AUTHOR , 2010. # msgid "" msgstr "" "Project-Id-Version: WP Super Cache\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2011-02-28 22:08:12+00:00\n" "PO-Revision-Date: 2011-03-15 23:04+0300\n" "Last-Translator: Elvis \n" "Language-Team: Elvis \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Russian\n" "X-Poedit-Country: RUSSIAN FEDERATION\n" #: ossdl-cdn.php:146 msgid "Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull." msgstr "Скорее всего, на Вашем блоге очень много статичных файлов: изображений, файлов JS и CSS. Для улучшения работы блога, стоит загружать данные файлы с другого сайта или CDN. Данный плагина позволит изменить ссылки на все статичные файлы в wp-content и wp-includes (кроме файлов .php) на указанные ниже. Вы также можете скопировать все статичные файлы на любой другой хост или создать их копии на CDN. Подробнее об этом узнайте тут (англ.)." #: ossdl-cdn.php:147 #: wp-cache.php:968 msgid "The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin." msgstr "" #: ossdl-cdn.php:148 msgid "WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes." msgstr "ВНИМАНИЕ: Прежде всего, протестируйте адреса CDN, например: %s - чтобы убедиться в корректной работе серверов." #: ossdl-cdn.php:149 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "Вы можете использовать различные адреса CDN для каждого блога (если у Вас мультиблог)." #: ossdl-cdn.php:157 msgid "Enable CDN Support" msgstr "Включить поддержку CDN" #: ossdl-cdn.php:160 msgid "Off-site URL" msgstr "Основной URL" #: ossdl-cdn.php:163 msgid "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "Новый адрес будет использован вместо старого %1$s. Не используйте символ / на конце адреса.
    Пример: %2$s." #: ossdl-cdn.php:167 msgid "Include directories" msgstr "Включить директории" #: ossdl-cdn.php:170 msgid "Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty." msgstr "Включить следующие директории со статичными файлами для перезаписи при совпадении. Используйте запятую (,) для разделения. По умолчанию будут добавлены директории wp-content и wp-includes." #: ossdl-cdn.php:174 msgid "Exclude if substring" msgstr "Исключить форматы" #: ossdl-cdn.php:177 msgid "Excludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "Исключить следующие форматы для перезаписи, если найдено совпадение. Используйте запятую (,) для разделения исключений, например: .php, .flv, .do - не забывайте включать .php (по умолчанию)." #: ossdl-cdn.php:181 msgid "Additional CNAMES" msgstr "Дополнительные CNAME (канонические имена)" #: ossdl-cdn.php:184 msgid "These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$s" msgstr "Эти записи CNAME будут использованы вместо %1$s (в дополнении к основному URL). Используйте запятую (,) для разделения записей. Для страниц с большим количеством статичных файлов данная опция может уменьшить время загрузки. Записи CNAME также могут быть использованы для конфигурации CDN.
    Пример: %2$s" #: ossdl-cdn.php:188 msgid "Skip https URLs to avoid \"mixed content\" errors" msgstr "Пропустить адреса типа https чтобы избежать ошибок, связанных с использование защищенных и незащищенных узлов" #: ossdl-cdn.php:192 msgid "Save Changes" msgstr "Сохранить все изменения" #: ossdl-cdn.php:194 msgid "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "Данные настройки CDN предоставлены плагином OSSDL CDN Off Linker от Mark Kubacki" #: wp-cache.php:99 msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Пожалуйста, создайте файл %s /wp-cache-config.php из wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:162 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Внимание! Включен режим PHP Safe Mode!" #: wp-cache.php:163 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "При работе с плагином могут возникнуть проблемы, так как PHP Safe Mode включен на Вашем сервере." #: wp-cache.php:167 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Ваш сервер настроен так, что проверяет владельца для всех PHP скриптов перед тем как разрешить им чтение или запись в файл." #: wp-cache.php:168 msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Вы или Администратор можете исправить ошибки, изменив группу владельца скриптов плагина через настройки веб-сервера. Также нужно изменить владельца для папки %s/cache/. Для более подробной информации смотрите страницу помощи по режиму safe mode (на англ.)." #: wp-cache.php:170 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Вы или Администратор должны отключить это. Для более подробной информации смотрите страницу помощи по режиму safe mode (на англ.). Данные настройки НЕ могут быть отключены через файл .htaccess, для решения проблемы нужно редактировать php.ini в настройках веб-сервера." #: wp-cache.php:176 msgid "Permlink Structure Error" msgstr "Ошибка структуры ссылок" #: wp-cache.php:177 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Для работы плагина необходима корректная настройка структуры ссылок. Чтобы настроить их, посетите страницу Постоянные ссылки." #: wp-cache.php:189 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Внимание! Ваше hostname \"%s\" преобразовано в %s" #: wp-cache.php:190 msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Ваш веб-сервер решил, что hostname изменено на %s. Некоторые опции плагина (например, \"Очистка мусора\") и сам WordPress могут работать некорректно." #: wp-cache.php:191 #: wp-cache.php:205 msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Чтобы узнать больше, посетите раздел 16 в Описании проблем в файле readme.txt (на англ.)" #: wp-cache.php:204 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "К сожалению, файл wp-cron.php не был обнаружен. Этот скрипт необходим для корректной работы опциии \"Очистка мусора\" и самого WordPress." #: wp-cache.php:219 msgid "Cannot continue... fix previous problems and retry." msgstr "Невозможно продолжить... прежде чем повторить попытку, исправьте предыдущие ошибки." #: wp-cache.php:228 msgid "Zlib Output Compression Enabled!" msgstr "Сжатие Zlib Output включено!" #: wp-cache.php:229 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP использует сжатие для сжатых страницы Вашего сайта. Отключение данной опции рекомендуется, чтобы избежать многократного сжатия страниц плагином. Узнать больше, посетив раздел 16 в \"Описание проблем\" в файле readme.txt (на англ.). Также ознакомьтесь с этой страницей (на англ.) по php.ini." #: wp-cache.php:233 msgid "Mod rewrite may not be installed!" msgstr "Кажется, модуль mod_rewrite не установлен!" #: wp-cache.php:234 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Возникла ошибка, связанная с тем, что модуль mod_rewrite отсутствует или не установлен. Пожалуйста, проверьте наличие модуля mod_rewrite в конфигурациях сервера. Модуль необходим для корректной работы плагина с статичными файлами. Без подключенного mod_rewrite Вы можете использовать только режимы с поддержкой PHP или среднее кэширование." #: wp-cache.php:239 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Режим \"только_чтение\". Настройки не могут быть изменены." #: wp-cache.php:240 msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Конфигурационный файл плагина WP Super Cache %s/wp-cache-config.php не может быть изменен. Чтобы продолжить, Вы должны установить права на запись для файла." #: wp-cache.php:241 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Самый простой способ исправить это - изменить права доступа, используя CHMOD, через FTP-клиент. Достаточно установить глобальные права на запись." #: wp-cache.php:242 #: wp-cache.php:258 msgid "This page explains how to change file permissions." msgstr "Здесь (англ. статья) подробно описано как изменить права доступа к файлам на сервере." #: wp-cache.php:243 msgid "Writeable:" msgstr "Доступно для записи:" #: wp-cache.php:244 msgid "Readonly:" msgstr "Только чтение:" #: wp-cache.php:256 msgid "Warning! %s is writeable!" msgstr "Внимание! Папка %s доступна для записи!" #: wp-cache.php:257 msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Вы должны изменить права на папку %s. Чтобы сделать это - воспользуйтесь FTP-клиентом или следующей командой:" #: wp-cache.php:267 msgid "Mobile rewrite rules detected" msgstr "Обнаружена поддержка мобильных устройств" #: wp-cache.php:268 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Для более продуктивной работы сайта, Вам стоит включить опцию \"Поддержка мобильных устройств\" или удалить эту запись из правил в .htaccess. Найдите следующий текст (две строчки) \"2.0\\ MMP|240x320\" и удалите его." #: wp-cache.php:268 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "На Ваших обычных посетителях это никак не отразится, а вот использующие мобильные устройства для веб-серфинга не будут получать кэшированные страницы (если опция отключена)." #: wp-cache.php:274 #: wp-cache.php:285 msgid "Rewrite rules must be updated" msgstr "Права на запись должны быть обновлены" #: wp-cache.php:275 #: wp-cache.php:286 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Необходимые для работы плагина права были изменены или отсуствуют." #: wp-cache.php:276 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Поддержка блогом мобильных устройств требует присутствия особых правил в файле .htaccess, иначе Вы не сможете использовать эту опцию. Ниже представлены возможые способы (в порядке сложности):" #: wp-cache.php:277 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Переведите плагин в режим среднего кэширования и включите поддержку мобмльных устройств." #: wp-cache.php:278 #: wp-cache.php:287 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Прокрутите страницу вниз и нажмите кнопку Обновить правила Mod_Rewrite." #: wp-cache.php:279 msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Удалите все правила mod_rewrite из файла %s.htaccess, между # BEGIN WPSuperCache и # END WPSuperCache и обновите страницу (восстановление правил запустится автоматически)." #: wp-cache.php:280 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Добавьте правила самостоятельно. Для этого откройте в редакторе файл %s.htaccess и найдите код между # BEGIN WPSuperCache и # END WPSuperCache. Вы увидите два похожих блока кода. Сразу после строки %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ добавьте следующее (таких строк две, добавьте код и после второй):" #: wp-cache.php:293 msgid "Required to serve compressed supercache files properly." msgstr "Необходимо для правильного сжатия файлов." #: wp-cache.php:293 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Необходимо настроить кэширование на странице плагина. Пользователи браузера IE7 будут видеть необновленные страницы из кэша без поддержки данного модуля." #: wp-cache.php:293 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Установите дату истечения актуальности страниц. Пользователи могут не увидеть новую версию кэшированной страницы без данного модуля." #: wp-cache.php:300 msgid "Missing Apache Modules" msgstr "Отсутствующие модули Apache" #: wp-cache.php:301 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Следующие модули Apache отсутствуют на Вашем сервере. Без них плагин сможет работать только в режиме среднего кэширования. В режиме с поддержкой Super Cache Ваши пользователи могут видеть поврежденные страницы или просроченные их копии." #: wp-cache.php:459 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Внимание! Вы пытаетесь включить сжатие, но модуль zlib.output_compression отключен. Смотрите пункт номер 21 раздела \"Описание проблем\" в файле readme.txt (на англ.)" #: wp-cache.php:550 msgid "WP Super Cache Settings" msgstr "Настройки WP Super Cache" #: wp-cache.php:561 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Важно: Mod_rewrite или Legacy caching отключены. По умолчанию будет загружаться страница \"Настройки\"." #: wp-cache.php:572 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Файл конфигураций был изменен, некоторые настройки не соответствуют требованиям плагина. Посетите страницу \"Настройки\" чтобы исправить это." #: wp-cache.php:597 msgid "Caching must be enabled to use this feature" msgstr "Кэширование должно быть включено, если Вы хотите использовать данную опцию" #: wp-cache.php:615 #: wp-cache.php:746 msgid "Cancel Cache Preload" msgstr "Отменить общее кэширование" #: wp-cache.php:623 #: wp-cache.php:634 msgid "Scheduled preloading of cache cancelled." msgstr "Общее кэширование по расписанию отключено." #: wp-cache.php:660 #: wp-cache.php:744 msgid "Preload Cache Now" msgstr "Создать общий кэш сейчас" #: wp-cache.php:664 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Общее кэширование произойдет через 10 секунд." #: wp-cache.php:669 msgid "Scheduled preloading of cache in %d minutes" msgstr "Общее кэширование произойдет через %d минут" #: wp-cache.php:673 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "При активации общего кэширования, будет создана копия для каждой записи и страницы Вашего блога. В этом режиме создаются статичные страницы, которые затем будут видеть \"неопознанные\" посетители (например, поисковые боты и другие). Это может помочь в улучшении уровня PR Google, так как в основе их алгоритма лежит и скорость отклика веб-сайта." #: wp-cache.php:674 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Однако, при использовании данного вида кэша создается намного больше файлов. Рекомендуется использовать такой тип, если у Вас очень много записей (10 тысяч и более) на блоге. Особенно это важно, если Вы пользуетесь услугами виртуального хостинга." #: wp-cache.php:675 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "В режиме ’Общего кэширования’ запланированная очистка мусора будет удалять только кэш записей простого типа (кэш из Super Cache не будет удален). Данная настройка рекомендована для использования." #: wp-cache.php:679 msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Обновлять общий кэш каждые %s минут (введите 0, чтобы отключить, минимальное допустимое кол-во минут %d)." #: wp-cache.php:692 msgid "all" msgstr "весь" #: wp-cache.php:705 msgid "Preload %s posts." msgstr "Кэшировать %s записи." #: wp-cache.php:712 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Предварительный режим (очистка мусора работает не полностью, опция рекомендована к включению.)" #: wp-cache.php:715 msgid "Send me status emails when files are refreshed." msgstr "Отправлять мне сообщения с уведомлениями об обновлении кэша." #: wp-cache.php:720 msgid "Many emails, 2 emails per 100 posts." msgstr "Высокий уровень: 2 сообщения на 100 записей." #: wp-cache.php:723 msgid "Medium, 1 email per 100 posts." msgstr "Средний уровень: 1 сообщение на 100 записей." #: wp-cache.php:726 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Низкий уровень: 1 e-mail в начале и 1 в конце кэширования." #: wp-cache.php:730 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Обновление кэша через %d ч %d мин и %d сек." #: wp-cache.php:731 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Полное кэширование проихойдет через %d ч %d мин и %d сек." #: wp-cache.php:737 msgid "Currently caching from post %d to %d." msgstr "В данный моменты кэшируются записи с %d по %d." #: wp-cache.php:741 msgid "Page last cached: %s" msgstr "Последний раз страница была кэширована: %s" #: wp-cache.php:744 msgid "Update Settings" msgstr "Обновить настройки" #: wp-cache.php:752 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Общее кэширование отключено. Пожалуйста, включите полный режим работы плагина или обратитесь к администратору сервера." #: wp-cache.php:769 #: wp-cache.php:865 msgid "Caching" msgstr "Статус кэширования" #: wp-cache.php:773 msgid "Cache hits to this website for quick access." msgstr "Кэшировать сессии просмотров для быстрого доступа." #: wp-cache.php:773 #: wp-cache.php:774 #: wp-cache.php:791 #: wp-cache.php:796 #: wp-cache.php:799 #: wp-cache.php:800 #: wp-cache.php:813 #: wp-cache.php:868 msgid "Recommended" msgstr "Рекомендовано" #: wp-cache.php:774 msgid "Use mod_rewrite to serve cache files." msgstr "Использовать mod_rewrite для обслуживания кэша." #: wp-cache.php:775 msgid "Use PHP to serve cache files." msgstr "Использовать PHP для обслуживания кэша." #: wp-cache.php:776 msgid "Legacy page caching." msgstr "Упрощенное кэширование." #: wp-cache.php:777 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching." msgstr "Использование mod_rewrite поможет сделать работу блога быстрее, чем PHP (хотя и этот вариант тоже не такой медленный). Этот режим проще и удобнее, но начинающему пользователю лучше использовать кэширование PHP." #: wp-cache.php:783 msgid "Miscellaneous" msgstr "Разное" #: wp-cache.php:789 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "Внимание! Функция gzencode() не найдена, сжатие отключено." #: wp-cache.php:791 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Сжимать файлы кэша чтобы ускорить работу." #: wp-cache.php:792 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Сжатие кэша отключено по умолчанию, так как может некорректно работать на некоторых хостингах. Включение или Отключение данной опции автоматически чистит временный кэш." #: wp-cache.php:796 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "Ошибка 304. Данная ошибка возникает тогда, когда страница не была изменена со времени прошлого запроса." #: wp-cache.php:797 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "Поддержка ошибки 304 отключена по умолчанию (из-за проблем некоторых сервисов)." #: wp-cache.php:799 msgid "Don’t cache pages for known users." msgstr "Не кэшировать страницы для известных пользователей." #: wp-cache.php:800 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Авто перестройка кэша. Гости блога увидят устаревшие версии страниц кэша пока новые будут генерироваться." #: wp-cache.php:801 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Рассказать всем, что Вы пользуетесь плагином WP Super Cache (сообщение будет размещено в \"подвале\" сайта)!" #: wp-cache.php:807 #: wp-cache.php:1056 #: wp-cache.php:1563 msgid "Advanced" msgstr "Настройки" #: wp-cache.php:811 msgid "Mobile device support." msgstr "Поддержка мобильных устройств" #: wp-cache.php:812 msgid "Clear all cache files when a post or page is published." msgstr "Очищать кэш когда новая запись или страница опубликована." #: wp-cache.php:813 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "Дополнительная сверка кэша (очень редко может нарушить работу кэширования)." #: wp-cache.php:814 msgid "Only refresh current page when comments made." msgstr "Обновлять страницу при добавлении нового комментария к ней" #: wp-cache.php:815 msgid "List the newest cached pages on this page." msgstr "Создать список страниц в кэше (выводится на этой странице)" #: wp-cache.php:817 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Блокировка файлов. Вам скорее всего не понадобится данная опция, но она может решить проблему маломощных хостингов. Внимание! Включение опции, в редких случаях, может вызвать проблемы в работе блога!" #: wp-cache.php:819 msgid "Late init. Display cached files after WordPress has loaded. Most useful in legacy mode." msgstr "\"Поздняя\" инициализация. Плагин будет отображать кэшированные страницы после загрузки WordPress. Опция полезна при режиме совместимости." #: wp-cache.php:821 msgid "Use object cache to store cached files." msgstr "Использовать объекты кэша для хранения кэшированных файлов." #: wp-cache.php:821 msgid "(Experimental)" msgstr "(экспериментальные настройки)" #: wp-cache.php:828 msgid "Note:" msgstr "Важно:" #: wp-cache.php:830 msgid "Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided." msgstr "Удаляйте плагин только со специальной страницы. Все лишние файлы будут удалены автоматически (некоторые файлы нужно будет редактировать вручную)." #: wp-cache.php:831 msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Деактивируя плагин, убедитесь что папка %s доступна для записи в настройках Вашего сервера, чтобы файлы плагина advanced-cache.php и cache-config.php были удалены в автоматическом режиме (также проверьте наличие прав на запись для этих двух файлов)." #: wp-cache.php:832 msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Для справки смотрите readme.txt (документ на англ.). Там Вы найдете полезную информацию по использованию и удалению плагина WP Super Cache." #: wp-cache.php:833 msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Все еще нужна помощь? Смотрите официальный ЧАВО по плагину Super Cache (англ.). Также, Вы можете задать свой вопрос на форумах тех. поддержки (англ.), или ознакомиться с проблемами других пользователей и предложенными им решениями." #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "Обновить" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "Допустимые имена & Запрещенные адреса" #: wp-cache.php:868 msgid "Caching On" msgstr "Кэширование включено" #: wp-cache.php:869 msgid "Caching Off" msgstr "Кэширование выключено" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Важно: рекомендуется включить PHP кэширование, авто перестройку кэша и поддержку для мобильных устройств" #: wp-cache.php:880 msgid "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Внимание: Среди правил mod_rewrite обнаружены правила от Supercache. Для работы с кэшем будут использоваться они. Чтобы удалить эти правила, Вам нужно вручную отредактировать файл .htaccess." #: wp-cache.php:885 msgid "Cache Tester" msgstr "Проверка кэширования" #: wp-cache.php:886 msgid "Test your cached website by clicking the test button below." msgstr "Здесь можно проверить правильность кэширования страниц Вашего блога одним нажатием." #: wp-cache.php:892 msgid "Fetching %s to prime cache: " msgstr "Проверка страницы %s в кэше: " #: wp-cache.php:894 #: wp-cache.php:902 #: wp-cache.php:910 msgid "OK" msgstr "ЕСТЬ" #: wp-cache.php:897 msgid "Fetching first copy of %s: " msgstr "Проверка первой копии %s: " #: wp-cache.php:905 msgid "Fetching second copy of %s: " msgstr "Проверка второй копии %s: " #: wp-cache.php:913 msgid "One or more page requests failed:" msgstr "При работе с кэшем произошли ошибки:" #: wp-cache.php:932 #: wp-cache.php:933 msgid "Page %d: %d (%s)" msgstr "Страница %d: %d (%s)" #: wp-cache.php:939 msgid "Page 1: %s" msgstr "Страница 1: %s" #: wp-cache.php:940 msgid "Page 2: %s" msgstr "Страница 2: %s" #: wp-cache.php:941 msgid "The timestamps on both pages match!" msgstr "Временные штампы обоих вариантов страницы совпадают!" #: wp-cache.php:943 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Страницы не совпадают! Временной штамп отличается или не был найден!" #: wp-cache.php:950 msgid "Send non-secure (non https) request for homepage" msgstr "Отправить незащищенный (не по https) запрос для главной страницы" #: wp-cache.php:951 msgid "Test Cache" msgstr "Проверить" #: wp-cache.php:955 msgid "Delete Cached Pages" msgstr "Удалить страницы из кэша" #: wp-cache.php:956 msgid "Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below." msgstr "Кэшированные страницы Вашего блога хранятся на сервере в виде .php и .html файлов. Чтобы удалить их, нажмите на кнопку ниже." #: wp-cache.php:959 #: wp-cache.php:2093 #: wp-cache.php:2105 #: wp-cache.php:2268 msgid "Delete Cache" msgstr "Удалить весь кэш" #: wp-cache.php:963 msgid "Recommended Links and Plugins" msgstr "Рекомендованные для ускорения блога плагины и полезные материалы" #: wp-cache.php:964 msgid "Caching is only one part of making a website faster. Here are some other plugins that will help:" msgstr "Кэширование страниц - лишь первый шаг на пути ускорения блога! Ниже приведены пару советов по оптимизации Вашего блога:" #: wp-cache.php:965 msgid "WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together." msgstr "Плагин WP Minify уменьшает нагрузку на сервер за счет объединения CSS и JS файлов. Также можно использовать и WPSCMin для уменьшени объема кэшированных страниц. Однако он не может объединять JS и CSS файлы." #: wp-cache.php:966 msgid "Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix." msgstr "Дополнение Yahoo! Yslow прекрасно подойдет для владельцев браузера Firefox. Yslow успешно анализирует страницы Вашего блога и предлагает оптимальные решения для оптимизации и ускорения. Также стоит попробовать онлайн-утилиту GTMetrix." #: wp-cache.php:967 msgid "Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score." msgstr "Библиотека JS от Google позволит использовать оптимизированные файлы Javascript с сервера Google (некоторые плагины уже используют эти библиотеки)." #: wp-cache.php:969 msgid "Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules." msgstr "Только для понимающих пользователей: Ускорьте свой блог, используя дополнительные возможности контроля кэша за счет правил .htaccess." #: wp-cache.php:970 msgid "Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others." msgstr "Только для понимающих пользователей: Установите дополнительное кэшировани объектов, используя Memcached, XCache или eAcccelerator." #: wp-cache.php:981 msgid "Make WordPress Faster" msgstr "Сделай свой блог быстрее!" #: wp-cache.php:982 msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "Плагин %1$s создан и обновляется автором %2$s при поддержке многих других." #: wp-cache.php:983 msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Посетите блог автора плагина %1$s и его фотоблог на %2$s." #: wp-cache.php:984 msgid "Please say hi to him on %s too!" msgstr "Пожалуйста, посетите %s автора!" #: wp-cache.php:985 msgid "Need Help?" msgstr "Нужна помощь?" #: wp-cache.php:987 msgid "Installation Help" msgstr "Помощь по установке (англ.)" #: wp-cache.php:988 msgid "Frequently Asked Questions" msgstr "ЧАВО (англ.)" #: wp-cache.php:989 msgid "Support Forum" msgstr "Форум поддержки (англ.)" #: wp-cache.php:991 msgid "Rate This Plugin!" msgstr "Оцените плагин!" #: wp-cache.php:992 msgid "Please rate this plugin and tell me if it works for you or not. It really helps development." msgstr "Пожалуйста, оцените этот плагин или расскажите о своей проблеме. Этим вы поможете развивать WP Super Cache дальше." #: wp-cache.php:1001 msgid "Cached pages since %1$s : %2$s" msgstr "Страниц в кэше с %1$s : %2$s" #: wp-cache.php:1002 msgid "Newest Cached Pages:" msgstr "Новое в кэше:" #: wp-cache.php:1006 msgid "Cached %s seconds ago" msgstr "Добавлено в кэш %s секунд назад" #: wp-cache.php:1009 msgid "(may not always be accurate on busy sites)" msgstr "(список не рекомендован для больших сайтов)" #: wp-cache.php:1028 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Кэширование происходит за счет PHP файлов, хранящихся в папке плагина. Они загружаются при включении режима Supercache. Загрузка происходит намного чаще, чем для остальных плагинов WordPress." #: wp-cache.php:1029 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Для использования данной опции нужно знать PHP, и свободно разбираться в устройстве WordPress." #: wp-cache.php:1039 msgid "Available Plugins" msgstr "Доступные плагины" #: wp-cache.php:1056 msgid "Easy" msgstr "Кэш" #: wp-cache.php:1056 msgid "CDN" msgstr "Настройка CDN" #: wp-cache.php:1056 msgid "Contents" msgstr "Состояние кэша" #: wp-cache.php:1056 msgid "Preload" msgstr "Общий кэш" #: wp-cache.php:1056 msgid "Plugins" msgstr "Плагины" #: wp-cache.php:1056 msgid "Debug" msgstr "Обслуживание" #: wp-cache.php:1091 msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Внимание: проверка правил WP Super Cache mod_rewrite отключена для блогов сети пока не будет запущена на главном блоге." #: wp-cache.php:1100 msgid "Mod Rewrite Rules" msgstr "Модуль Mod Rewrite" #: wp-cache.php:1106 msgid "WordPress MU Detected" msgstr "Обнаружен WordPress MU!" #: wp-cache.php:1106 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "К сожалению, mod_rewrite невозможно обновить в автоматическом режиме в WordPress MU. Вам придется вручную сделать это: откройте файл .htaccess (расположен в корневой директории блога) и добавьте следующие правила в него." #: wp-cache.php:1108 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite не может быть обновлен!" #: wp-cache.php:1109 msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Для корректной работы в Вашем файле %s.htaccess должны быть прописаны маркеры BEGIN, и END. Между ними находятся основные правила WordPress mod_rewrite, пример:" #: wp-cache.php:1111 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Обновите страницу когда закончите редактирование файла .htaccess." #: wp-cache.php:1115 msgid "Thank you for upgrading." msgstr "Спасибо за обновление." #: wp-cache.php:1115 msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "С момента последней установленной версии плагина правила mod_rewrite были изменены. К сожалению, Вам придется вручную удалить старые правила прежде чем новые заработают. Обновите эту страницу когда закончите редактировать файл .htaccess. Если Вы хотите полностью обновить все сами, то замените следующую строку: %1$s на эту: %2$s . Единственное отличие - это замена \"HTTP_COOKIE\" на \"HTTP:Cookie\" и \"wordpressuser\" на \"wordpress\". Эти перемены связаны с новой версией WordPress 2.5. Конечно Вы можете продолжать работать со старыми версиями, если хватит смелости ;)" #: wp-cache.php:1119 msgid "Trailing slash check required." msgstr "Требуется проверка ссылок на слеш (\"/\")." #: wp-cache.php:1119 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Кажется, все ссылки Вашего блога заканчиваются символом \"/\". К сожалению, как только Вы установили данный плагин, сработала опция, обнаружившая копии ссылок без символа \"/\" на конце, и теперь она не может осуществить перенаправление на верный адрес. Чтобы это исправить это, Вы должны отредактировать файл .htaccess и добавить два новых правила к группе основных правил плагина Supercache:" #: wp-cache.php:1121 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Чтобы посмотреть полный список работающих правил, нажмите кнопку \"Посмотреть правила mod_rewrite\"." #: wp-cache.php:1135 msgid "Mod Rewrite rules updated!" msgstr "Правила mod_rewrite обновлены!" #: wp-cache.php:1136 msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "Файл %s.htaccess был успешно обновлен, необходимые правила mod_rewrite были добавлены. Пожалуйста, проверьте их. Они должны выглядеть так:" #: wp-cache.php:1138 msgid "Mod Rewrite rules must be updated!" msgstr "Правила mod_rewrite должны быть обновлены!" #: wp-cache.php:1139 msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Ваш файл %s.htaccess недоступен для записи (в настройках сервера) и не может быть обновлен в автоматическом режиме. Вы должны вручную добавить новые правила к основным так, как указано ниже:" #: wp-cache.php:1144 msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Правила mod_rewrite для плагина WP Super Cache были обнаружены в файле %s.htaccess.
    Нажмите на соответствующую кнопку, чтобы посмотреть строчки. Если Вы только что обновили плагин, проверьте все правила." #: wp-cache.php:1147 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "Между правилами в Вашем файле .htaccess и правилами самого плагина обнаружены несоответствия. Это может быть просто лишний символ в строке, но Вы должны лично сравнить оригинальные правила со своими как можно скорее. Нажмите на кнопку ’Обновить правила Mod_Rewrite’, чтобы сделать это в автоматическом режиме." #: wp-cache.php:1150 msgid "View Mod_Rewrite Rules" msgstr "Посмотреть правила mod_rewrite" #: wp-cache.php:1154 #: wp-cache.php:2384 msgid "Rules must be added to %s too:" msgstr "Правила должны быть также добавлены к %s:" #: wp-cache.php:1162 msgid "Gzip encoding rules in %s.htaccess created." msgstr "Правила для Gzip-сжатия добавлены в файл %s.htaccess." #: wp-cache.php:1169 msgid "Fix Configuration" msgstr "Восстановить стандартные настройки" #: wp-cache.php:1172 msgid "Restore Default Configuration" msgstr "Восстановить настройки по умолчанию" #: wp-cache.php:1180 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Проверка комментариев включена. Прежде чем Ваши комментарии будут опубликованы пройдет какое-то время." #: wp-cache.php:1205 msgid "Lock Down:" msgstr "Закрытый режим:" #: wp-cache.php:1205 #: plugins/awaitingmoderation.php:35 #: plugins/badbehaviour.php:66 #: plugins/domain-mapping.php:61 msgid "Disabled" msgstr "Отключен" #: wp-cache.php:1205 #: plugins/awaitingmoderation.php:34 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:60 msgid "Enabled" msgstr "Включен" #: wp-cache.php:1206 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Подготовьте свой блог к запланированным всплескам посещаемости, активировав данный режим. В активном состоянии размещение новых комментариев и записей НЕ будет обновлять статичные файлы в кэше." #: wp-cache.php:1207 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Разработчикам: сделайте свой собственный плагин закрытого режима совместимым с нашим, добавив переменную \"WPLOCKDOWN\". Приведенный ниже код поможет Вам адоптировать свой плагин к настройкам нашего Режима." #: wp-cache.php:1209 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Извините, мой блог временно недоступен. Зайдите попозже..." #: wp-cache.php:1213 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "Ваш блог использует Закрытый режим. Новые комментарии не обновляют все статичные элементы кэша." #: wp-cache.php:1215 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "Ваш блог не использует Закрытый режим. Новые комментарии обновляют все статичные элементы кэша." #: wp-cache.php:1218 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 msgid "Disable" msgstr "Отключить" #: wp-cache.php:1218 #: plugins/searchengine.php:74 msgid "Enable" msgstr "Включить" #: wp-cache.php:1221 msgid "Lock Down" msgstr "Закрытый режим" #: wp-cache.php:1229 msgid "Directly Cached Files" msgstr "Прямое кэширование страниц" #: wp-cache.php:1287 msgid "%s removed!" msgstr "%s удален!" #: wp-cache.php:1295 #: wp-cache.php:1297 #: plugins/badbehaviour.php:83 msgid "Warning!" msgstr "Внимание!" #: wp-cache.php:1295 msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Вы должны разрешить запись для %s. Но так как это потенциальная уязвимость, после обновления страницы верните права на чтение." #: wp-cache.php:1297 msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "Директрия %s доступна для записи. Вам следует изменить ее права на \"Только чтение\"." #: wp-cache.php:1311 msgid "Existing direct page" msgstr "Страница существует" #: wp-cache.php:1311 msgid "Delete cached file" msgstr "Удалить файлы из кэша" #: wp-cache.php:1316 msgid "Add direct page:" msgstr "Добавить страницу в кэш:" #: wp-cache.php:1318 msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Данный кэш создается прямо из папки, где находится Ваш блог (папка %s). Эта опция полезна только тогда, когда ожидается большой приток посетителей с более популярного ресурса на конкретную страницу или запись Вашего." #: wp-cache.php:1320 msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Например: чтобы добавить в кэш страницу %1$sabout/, нужно прописать %1$sabout/ или /about/. Кэш для страницы будет создан сразу же после первого к ней обращения гостем." #: wp-cache.php:1321 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Чтобы удалить страницу из такого кэша, очистите текстовое поле и удалите файлы кэша." #: wp-cache.php:1326 msgid "Update Direct Pages" msgstr "Обновить стрницы" #: wp-cache.php:1364 msgid "Expiry Time & Garbage Collection" msgstr "Просроченные страницы & Очистка мусора" #: wp-cache.php:1366 msgid "Expire time:" msgstr "Актуальность кэша:" #: wp-cache.php:1367 msgid "seconds" msgstr "секунд" #: wp-cache.php:1368 msgid "Garbage Collection" msgstr "Очистка мусора" #: wp-cache.php:1368 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Если время актуальности кэша более 1800 секунд (полчаса), то очистка мусора будет запускаться каждые 10 минут." #: wp-cache.php:1369 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Поверка и удаление просроченных страниц кэша занимает время, но и оставлять такие файлы в системе не стоит. На больших блогах нужно выставлять \"время жизни\" каждой копии 300 секунд. Вы можете поэкспериментировать с настройкой и посмотреть, сколько просроченных копий остается в кэше в течение дня. Оптимальное число - не более 500. Используя mod_rewrite или PHP, Вы сможете увеличить количество кэшируемых страниц." #: wp-cache.php:1370 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Установите значение 0 чтобы отключить Очистку мусора." #: wp-cache.php:1371 msgid "Change Expiration" msgstr "Изменить время жизни копии" #: wp-cache.php:1415 msgid "Rejected User Agents" msgstr "Поисковые и другие боты" #: wp-cache.php:1416 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Чтобы запретить плагину кэшировать запросы от поисковых ботов и других сетевых роботов, введите их названия в поле ниже (по одному в строке). Если копия страницы уже существует в кэше Super Cache, то она все равно будет отправлена боту." #: wp-cache.php:1423 msgid "Save UA Strings" msgstr "Сохранить настройки" #: wp-cache.php:1446 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Не кэшировать страницы следующих типов. Сверьтесь с Статьей Кодекса WP (англ.), чтобы узнать подробнее о типах страниц." #: wp-cache.php:1449 msgid "Single Posts" msgstr "Записи" #: wp-cache.php:1450 msgid "Pages" msgstr "Страницы" #: wp-cache.php:1451 msgid "Front Page" msgstr "Основная страница" #: wp-cache.php:1452 msgid "Home" msgstr "Домашняя страница" #: wp-cache.php:1453 msgid "Archives" msgstr "Архивы" #: wp-cache.php:1454 msgid "Tags" msgstr "Метки" #: wp-cache.php:1455 msgid "Category" msgstr "Рубрики" #: wp-cache.php:1456 msgid "Feeds" msgstr "Фиды" #: wp-cache.php:1457 msgid "Search Pages" msgstr "Страницы поиска" #: wp-cache.php:1459 #: wp-cache.php:1573 msgid "Save" msgstr "Сохранить" #: wp-cache.php:1476 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Поле ниже Вы также можете заполнить фрагментами адресов страниц (или групп страниц, например, архив за год/месяц и т.д.), которые не будут кэшироваться. Плагин будет сканировать адреса страниц на предмет наличая в них фрагментов, указанных ниже, перед кэшированием." #: wp-cache.php:1482 msgid "Save Strings" msgstr "Сохранить список запрещенных фрагментов" #: wp-cache.php:1498 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Поле ниже Вы можете заполнить названиями файлов которые будут кэшированы, даже если в их названии есть запрещенных к кэшированию фрагменты." #: wp-cache.php:1504 msgid "Save Files" msgstr "Сохранить список файлов" #: wp-cache.php:1545 msgid "Currently logging to: %s" msgstr "Currently logging to: %s" #: wp-cache.php:1548 msgid "Fix problems with the plugin by debugging it here. It can log them to a file in your cache directory." msgstr "Здесь Вы можете решить некоторые проблемы, возникающие при работе с плагином, с помощью отладки. Вся служебная информацию (логи) будет записана в файлы директории кэша." #: wp-cache.php:1552 msgid "Debugging" msgstr "Отладка" #: wp-cache.php:1552 #: plugins/awaitingmoderation.php:40 #: plugins/badbehaviour.php:71 #: plugins/searchengine.php:69 #: plugins/domain-mapping.php:66 msgid "enabled" msgstr "включен" #: wp-cache.php:1553 msgid "IP Address" msgstr "Адрес IP" #: wp-cache.php:1553 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(записывает обращения только с этого IP. Ваш IP - %s)" #: wp-cache.php:1554 msgid "Log level" msgstr "Уровень лога" #: wp-cache.php:1560 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = наименьший, 5 = наибольший, может вызвать большую нагрузку на сервер)" #: wp-cache.php:1563 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "В особо редких случаях на блоге могут случиться две проблемы:
    1. Вместо главной страницы пользователи будут видеть предложение загрузить .zip архив с ней
    2. Вместо главной страницы может быть добавлена в кэш совершенно другая (только в случае, если Ваш бог использует следующую структуру ссылок /%category%/%postname%/).
    " #: wp-cache.php:1564 msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "Ошибки, которые могут возникнуть при работе с WP Super Cache, не связаны с плагином. Они появляются лишь в редких случаях (и то из-за проблем с хостингом или другими плагинами), но Вы можете подстраховаться, запустив автоматическую сверку кэша каждые 5 минут. В случае ошибки, Вам будет отправлено сообщение." #: wp-cache.php:1566 msgid "Check front page every 5 minutes." msgstr "Проверять главную страницу каждые 5 минут." #: wp-cache.php:1567 msgid "Front page text" msgstr "Ключевой текст" #: wp-cache.php:1567 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Введите текст который плагин будет искать на главной странице. Если текст не будет обнаружен, то кэш автоматически очистится. Оставьте поле пустым чтобы отключить опцию." #: wp-cache.php:1568 msgid "Clear cache on error." msgstr "Очищать кэш при ошибке." #: wp-cache.php:1569 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Сообщить администратору блога по завершению проверки (полезно при тестировании на ошибки)." #: wp-cache.php:1583 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Ошибка: сжатие GZIP включено, отключите его если хотите запустить wp-cache." #: wp-cache.php:1630 #: wp-cache.php:1796 msgid "Warning" msgstr "Внимание" #: wp-cache.php:1630 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "Сжатие GZIP включено в настройках WordPress, плагин не будет работать до тех пор, пока Вы не отключите gzip." #: wp-cache.php:1692 #: wp-cache.php:1697 #: wp-cache.php:1729 #: wp-cache.php:1734 #: wp-cache.php:1740 msgid "Error" msgstr "Ошибка" #: wp-cache.php:1692 msgid "Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions." msgstr "Папка для хранения кэша ($cache_path) не существует и не может быть создана в автоматическом режиме. Проверьте права доступа к %s." #: wp-cache.php:1697 msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Папка (%1$s) или %2$s должна быть доступна для записи. Перепроверьте права доступа." #: wp-cache.php:1729 msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Конфигурационный файл WP-Cache (%s) может быть недоступен для записи. Пожалуйста, удалите его вручную и обновите страницу." #: wp-cache.php:1734 msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Конфигурационный файл отсутствует, а папка %1$s (%2$s) недоступна для записи. Проверьте права доступа." #: wp-cache.php:1740 msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Файл WP-Cache (%s) не был найден. Проверьте, завершена ли установка плагина." #: wp-cache.php:1796 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php не существует или не может быть обновлен в автоматическом режиме." #: wp-cache.php:1797 msgid "1. If it already exists please delete the file first." msgstr "1. Если он уже существует в папках Вашего блога, удалите его." #: wp-cache.php:1798 msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Измените права доступа к %1$s, чтобы можно было записать данные в автоматическом режиме (права должны быть: chmod 777 %1$s), проверьте правильность заданных прав и обновите страницу. Это временное условие, после обновления страницы права доступа нужно вернуть на прежние (с 777 на 755)." #: wp-cache.php:1799 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Перезагрузите страницу, файл %s/advanced-cache.php обновится сам" #: wp-cache.php:1800 msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Если это не сработало, убедитесь что файл %s/advanced-cache.php не существует:" #: wp-cache.php:1801 msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Откройте файл %1$s$wp_cache_file в текстовом редакторе.
  • 2. Измените строчку CACHEHOME на %2$s
  • 3. Сохраните файл и скопируйте в %3$s, затем перезагрузите страницу.
    • " #: wp-cache.php:1824 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    Параметр WP_CACHE не активирован

    Данный параметр должен быть активирован для того, чтобы WordPress мог корректно работать с файлами кэша. В данный момент он отключен. Чтобы включить его, откройте файл wp-config.php и добавьте в него следующую строчку:

    define('WP_CACHE', true);

    " #: wp-cache.php:1826 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Ошибка: Переменная WP_CACHE не была найдена в файле общих конфигураций wp-config.php." #: wp-cache.php:1827 msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Отредактируйте код %s и добавьте следующую сточку:
    define('WP_CACHE', true);
    Иначе WP-Cache не сможет запуститься. " #: wp-cache.php:1831 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    Переменная WP_CACHE добавлена в файл конфигураций wp-config.php

    Если Вы до сих пор видите данное сообщение, то сверьтесь с пунктом 5 ЧАВО (на англ.). Строка с WP_CACHE должна быть размещена выше." #: wp-cache.php:1855 msgid "Cache Contents" msgstr "Состояние кэша" #: wp-cache.php:1858 msgid "Object cache in use. No cache listing available." msgstr "Список кэширования недоступен." #: wp-cache.php:1882 msgid "Deleting supercache file: %s
    " msgstr "Удаление файлов Super Cache: %s
    " #: wp-cache.php:1899 msgid "Deleting wp-cache file: %s
    " msgstr "Удаление файлов WP-Cache: %s
    " #: wp-cache.php:1964 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Статистика объектов в кэше НЕ создается автоматически. Чтобы обновить ее вручную нажмите на ссылку ниже." #: wp-cache.php:1965 msgid "Regenerate cache stats" msgstr "Обновить статистику кэша" #: wp-cache.php:1967 msgid "Cache stats last generated: %s minutes ago." msgstr "Статистика объектов в кэше последний раз создана: %s мин назад." #: wp-cache.php:1973 msgid "WP-Cache" msgstr "Состояние WP-Cache" #: wp-cache.php:1974 #: wp-cache.php:1989 msgid "%s Cached Pages" msgstr "%s страниц в кэше" #: wp-cache.php:1975 #: wp-cache.php:1994 msgid "%s Expired Pages" msgstr "%s страниц просрочено" #: wp-cache.php:1988 msgid "WP-Super-Cache" msgstr "Состояние WP-Super-Cache" #: wp-cache.php:1998 msgid "Fresh WP-Cached Files" msgstr "Новые файлы WP-Cache" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "URI" msgstr "АДРЕС" #: wp-cache.php:1999 #: wp-cache.php:2015 msgid "Key" msgstr "Ключ" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "Age" msgstr "Возраст" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "Delete" msgstr "Удалить" #: wp-cache.php:2014 msgid "Stale WP-Cached Files" msgstr "Старые файлы WP-Cache" #: wp-cache.php:2030 msgid "Fresh Super Cached Files" msgstr "Новые файлы Super Cache" #: wp-cache.php:2046 msgid "Stale Super Cached Files" msgstr "Старые файлы Super Cache" #: wp-cache.php:2062 msgid "Hide file list" msgstr "Убрать список" #: wp-cache.php:2064 msgid "Too many cached files, no listing possible." msgstr "Слишком много объектов в кэше, создание списка невозможно." #: wp-cache.php:2066 msgid "List all cached files" msgstr "Список кэшированных файлов" #: wp-cache.php:2072 msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Очистка мусора
    Предыдущая очистка была %s минут назад
    " #: wp-cache.php:2073 msgid "Next GC in %s minutes" msgstr "Следующая очистка будет через %s минут" #: wp-cache.php:2076 msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Просроченный кэш - это страницы, созданные более чем %s секунд назад. Не смотря на свой статус, они используются в общем кэше и периодически удаляются." #: wp-cache.php:2087 msgid "Delete Expired" msgstr "Удалить просроченный кэш" #: wp-cache.php:2105 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Удалить файлы Super Cache (в новом окне)" #: wp-cache.php:2244 msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s благодарен плагину %2$s за проделаннную работу" #: wp-cache.php:2277 msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "Плагин WP Super Cache должен быть настроен! Чтобы включить его и настроить, перейдите на страницу управления." #: wp-cache.php:2283 msgid "Settings" msgstr "Настройки" #: wp-cache.php:2293 msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "Плагин WP Super Cache не активирован! Чтобы включить его, перейдите на страницу управления." #: wp-cache.php:2296 msgid "Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct." msgstr "ВНИМАНИЕ! Кэширование отключено, плагин поврежден! WP Super Cache не может загрузить скрипт wp-cache-phase1.php.

    Чтобы исправить ошибку, откройте файл %1$s/advanced-cache.php и проверьте строчку, указывающую на %2$swp-cache-phase1.php." #: wp-cache.php:2315 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Главная страница сжата с помощью gzipped! Удалите кэш!" #: wp-cache.php:2315 msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Произошла ошибка! Посетите %s чтобы удалить кэш!" #: wp-cache.php:2318 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Главная страница сжата с помощью gzipped! Кэш удален!" #: wp-cache.php:2318 msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Весь кэш для Вашего блога был очищен, так как плагин заметил ошибку на главной странице (она скачивалась архивом). Чтобы проверить кэш, посетите эту стрницу %s." #: wp-cache.php:2325 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Кэш главной страницы содержит ошибку! Удалите кэш!" #: wp-cache.php:2325 msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Произошла ошибка, на главной странице Вашего блога не был обнаружен ключевой текст \"%2$s\"! Чтобы исправить ошибку, посетите эту страницу %1$s и вручную очистие кэш." #: wp-cache.php:2328 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Главная страница отображается с ошибкой! Кэш удален!" #: wp-cache.php:2328 msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Произошла ошибка, на главной странице Вашего блога не был обнаружен ключевой текст \"%2$s\"! Посетите эту страницу %1$s чтобы проверить кэш." #: wp-cache.php:2333 msgid "[%s] Front page check!" msgstr "[%s] Главная страница проверена!" #: wp-cache.php:2333 msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "Плагин WP Super Cache только что проверил главную страницу Вашего блога на предмет ошибок. Чтобы отключить уведомления и проверку посетите эту страницу %s." #: wp-cache.php:2376 msgid "Cannot update .htaccess" msgstr "Не могу обновить файл .htaccess" #: wp-cache.php:2376 msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Файл %s.htaccess не может быть обновлен в автоматическом режиме. Чтобы исправить это задайте необходимые для записи права доступа к нему." #: wp-cache.php:2376 msgid "Refresh this page when the file permissions have been modified." msgstr "Обновите страницу когда необходимые права доступа будут заданы." #: wp-cache.php:2376 msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Вы также можете отредактировать файл %s.htaccess вручную и лично добавить необходимые правила:" #: wp-cache.php:2380 msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Чтобы плагин мог правильно работать со статичными html файлами, Вы должны добавить в файл %s.htaccess правила модуля mod_rewrite" #: wp-cache.php:2381 msgid "You can edit the file yourself add the following rules." msgstr "Вы можете вручную отредактировать файл и добавить необходимые правила." #: wp-cache.php:2382 msgid " Make sure they appear before any existing WordPress rules. " msgstr " Убедитесь что они идут перед всеми уже существующими в документе правилами WordPress. " #: wp-cache.php:2390 msgid "Update Mod_Rewrite Rules" msgstr "Обновить правила mod_rewrite" #: wp-cache.php:2515 msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Общее кэширование началось" #: wp-cache.php:2517 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Обновление кэша записей с %2$d по %3$d" #: wp-cache.php:2535 msgid "[%1$s] Cache Preload Stopped" msgstr "[%1$s] Общее кэширование остановлено" #: wp-cache.php:2544 msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d кэш записей обновлен" #: wp-cache.php:2544 msgid "Refreshed the following posts:" msgstr "Следующие записи обновлены:" #: wp-cache.php:2553 msgid "Scheduling next preload refresh in %d minutes." msgstr "Следующее запланированное обновление общего кэша через %d минут." #: wp-cache.php:2563 msgid "[%s] Cache Preload Completed" msgstr "[%s] Общее кэширование завершено" #: wp-cache.php:2563 msgid "Cleaning up old supercache files." msgstr "Удалять старые файлы из кэша Super Cache." #: wp-cache.php:2605 msgid "[%s] Preload may have stalled." msgstr "[%s] Общее кэширование могло быть прервано." #: wp-cache.php:2605 msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Общее кэширование было перезапущено.\n" "%s" #: wp-cache.php:2648 msgid "Supercache Uninstall Problems" msgstr "Проблемы при удалении плагина" #: wp-cache.php:2648 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" msgstr "" "Уважаемый пользователь,\n" "\n" "плагин WP Super Cache был успешно удален с Вашего блога, но правила mod_rewrite\n" "в файле .htaccess не были приведены в исходное состояние.\n" "\n" "Пожалуйста, отредактируйте даный файл вручную, используя текстовый редактор,\n" "удалив строчки между 'BEGIN WPSuperCache' и 'END WPSuperCache'. Но сначала создайте резервную копию файла!\n" "\n" "%s\n" "\n" "Успехов,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Ваш комментарий ожидает подтверждения." #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "Плагин \"Awaiting Moderation\"" #: plugins/awaitingmoderation.php:36 msgid "Enables or disables plugin to Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment." msgstr "Включите или выключите плагин, чтобы убрать надпись \"Ваш комментарий ожидает проверки\" когда кто-то размещает комментарий к записи." #: plugins/awaitingmoderation.php:42 #: plugins/badbehaviour.php:73 #: plugins/searchengine.php:67 #: plugins/domain-mapping.php:68 msgid "disabled" msgstr "отключен" #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "Плагин \"Awaiting Moderation\" сейчас %s" #: plugins/awaitingmoderation.php:45 #: plugins/badbehaviour.php:76 #: plugins/domain-mapping.php:71 msgid "Update" msgstr "Обновить" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "Плагин \"Bad Behaviour\" не был найден. Проверьте, завершили ли Вы его установку." #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "Плагин \"Bad Behaviour\" " #: plugins/badbehaviour.php:68 msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr " (данный плагин может работать только в режиме среднего кэширования, отключите сжатие и установите плагин \"Bad Behavior\" в \"%s/plugins/bad-behavior/\") " #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "Статус плагина \"Bad Behaviour\": %s. " #: plugins/searchengine.php:71 msgid "No Adverts for Friends plugin is %s." msgstr "Статус плагина \"No Adverts for Friends\": %s." #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(требуется установка friendsadverts.php) " #: plugins/domain-mapping.php:58 msgid "Domain Mapping" msgstr "Плагин \"МультиБлог\"" #: plugins/domain-mapping.php:63 msgid "Provides support for Domain Mapping plugin to map multiple domains to a blog." msgstr "Помогите улучшить плагин \"Domain Mapping\"!" #: plugins/domain-mapping.php:69 msgid "Domain Mapping support is now %s" msgstr "Статус плагина \"Domain Mapping\": %s. " #: plugins/domain-mapping.php:83 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Обнаружен плагин \"Domain Mapping\"! Чтобы облегчить и ускорить его работу, Вам нужно включить поддержку мультиблогов в настройках." #~ msgid "" #~ "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on " #~ "on the main site of this network." #~ msgstr "" #~ "Внимание: Проверка правил WP Super Cache mod_rewrite отключена для блогов " #~ "сети пока не будет запущена на главном блоге." #~ msgid "Tester & Contents" #~ msgstr "Проверка" #~ msgid "" #~ "Logging to a file is easier but faces the problem that clearing the cache " #~ "will clear the log file." #~ msgstr "" #~ "Получить доступ к файлу лога просто, но при очистке кэша лог также будет " #~ "удален." #~ msgid "Logging Type" #~ msgstr "Тип входа" #~ msgid "Email" #~ msgstr "Email" #~ msgid "file" #~ msgstr "файл" #~ msgid "(support for multiple domains on multisite websites) " #~ msgstr "(поддержка для MU - сервиса блогов)" #~ msgid "" #~ "Scheduled preloading of cache cancelled. If a job is currently running it " #~ "will not shutdown until the current 100 pages are complete." #~ msgstr "" #~ "Общее кэширование по расписанию отключено. Если служба сейчас запущена, " #~ "она не будет завершена пока текущие 100 страниц не кэшированы." #~ msgid "" #~ "Scroll down this page and click the Update Mod_Rewrite Rules button." #~ msgstr "" #~ "Пролистайте страницу вних и нажмите кнопку Обновить правила " #~ "Mod_Rewrite." #~ msgid "WP Super Cache Manager" #~ msgstr "Управление плагином WP Super Cache" #~ msgid "Why your configuration may not be changed" #~ msgstr "Почему конфигурации не могут быть изменены" #~ msgid "Why" #~ msgstr "Почему" #~ msgid "ON" #~ msgstr "ВКЛ" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "Плагины WP Cache и Super Cache включены" #~ msgid "HALF ON" #~ msgstr "РАБОТАЕТ НАПОЛОВИНУ" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Плагин Super Cache отключен, работает только кэшировани WP-Cache" #~ msgid "OFF" #~ msgstr "ВЫКЛ" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "Плагины WP Cache и Super Cache отключены" #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "Восстановление кэша. При включенной опции, гости сайта будут получать " #~ "старые страницы из плагина Super Cache, пока формируются новые. " #~ "Рекомендуется использовать данную опцию только для очень " #~ "посещаемых блогов, где много комментариев. После включения опции в " #~ "настройках \"прямое кэширование страниц\" и \"закрытый режим\" нет нужды " #~ "(они устаревают)" #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "Создавать список новых кэшированных страниц (использовать на свой страх и " #~ "риск, может затормозить сайты с большим количеством посетителей)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s действительно ускоряет Ваш блог. Вы можете сделать его еще " #~ "быстрее*, купив мне подарочную карту сервиса " #~ "Amazon! Можете выбрать \"%3$s\" любое значение, какое хотите. Каждая " #~ "копейка поможет мне!" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "Если Вы не хотите иметь дело с Amazon , то можно сделать пожертвование " #~ "через PayPal. Нажмите кнопку \"Пожертвовать\" или выберите подарок для " #~ "меня из моего списка желаний." #~ msgid "Thanks in advance!" #~ msgstr "Заранее благодарю!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Ладно, он не будет быстрее, но Вы все равно сделаете автора плагина очень " #~ "счастливым!" #~ msgid "Don’t show me this again." #~ msgstr "Не показывать больше это сообщение." #~ msgid "Hide" #~ msgstr "Спрятать" #~ msgid "" #~ "He blogs at %1$s and posts photos at %2$s. He would really appreciate a " #~ "donation to encourage development of this plugin." #~ "
    Even a penny will help." #~ msgstr "" #~ "Блог автора - %1$s, фотоблог - %2$s. Автор плагина будет благодарен любой " #~ "поддержке от Вас.
    Даже копейка может помочь в " #~ "его работе." #~ msgid "Super Cache Compression" #~ msgstr "Сжатие кэша Super Cache" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "" #~ "Сжатие кэша отключено по умолчанию в режиме РАБОТАЕТ НАПОЛОВИНУ." #~ msgid "Super Cache compression is now disabled." #~ msgstr "Сжатие кэша Super Cache теперь отключено." #~ msgid "Super Cache compression is now enabled." #~ msgstr "Сжатие кэша Super Cache теперь включено." #~ msgid "Update Compression" #~ msgstr "Обновить настройки сжатия" #~ msgid "Debug Settings" #~ msgstr "Параметры отладки" #~ msgid "" #~ "

    WP_CACHE constant in wp-config.php set to false

    The WP_CACHE " #~ "constant is defined in your wp-config.php but must be set to true, not " #~ "false for this plugin to work correctly.

    " #~ msgstr "" #~ "

    Значение для WP_CACHE в конфигурационном файле WordPrees wp-config." #~ "php установлено на \"false\"

    Чтобы плагин заработал, значение " #~ "WP_CACHE в wp-config.php нужно поставить на \"true\".

    " #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "" #~ "Вы должны вручную отредактировать файл и добавить необходимые правила." languages/wp-super-cache-sv_SE.mo000066600000157326152133035240012727 0ustar009 8<9,vM` s~?3>rb"*7Z5C5y =bj^ \ r&!!?"#w$Z%`%&.&'&((:(n'*p*,,,,, ,3,-"- 1-,>-k-^.p{.+.//./^/ f/ r/+}//3// 00!%0G0!27>2v22I;3@33sK44%?5e5|5 55 5555553616777888u\9j9=:B::?:9;@;H;NN;; ;n;$.<S<Y<v<<<~<@==>> >><>g*??+?*?? @@ AbAA1B:C&D"/EkRFGGEGH*3H ^H hH sH }HbHH]I$aII IIIIIJ$J"JJ! K,KKL&LM<"Mb_MM|uNyNlO0oO!O-OkO\Q mQ xQQQTQQURmRpSUSSSSTTJ5TTd]UU`iV0V V W7WSIW?W<WX9XPX7eXjXY&YDYYcYY Y YY(YZ+Z,Z.Zf![ [/[0[[?x\8\\ \:]B][]q]H^ M^;X^^q^_1__x`aaQb<idGd#due eTf~f+ggggghNibi{i ii%i'ijjj4jbjklk9lBlQlYlbl|l*llbl[@m m7mrmMRnnYo/o qrr?ssRt$tetau v%vAv)^vvv*v/v.w3Fwzwwwwwww@y/yHzOz`z|rz zz@{<{||d|8}FV}\}1}6,~(c~LkuE`nf~uc7@!@) 4RLj %%<Fbō Ս<_Î#8܏0- 6 BDOF$*O!`=ՓS@ޔ91  ,:=x3Y1o X coo œ\ɜ& /9R= o'F$NsžZ"Ԡ A!wc ۡ*4GW [ gVqȣl&^F̨elJΪ3  % 0;aKaū&'Nnv!ɬ~)%(* ( 2O:s±G̲2ϲ/:2}m Y6.Ny[4  ̷F4yiR5 =YL=B'F`;u}"/$R'wc %+8d014?fw 5(2^D*EoB1H 2 <KHz#A #kDJ$kD[c p/%(NR(&?.P.1mhq!/dbz >x&^"r#~%w?" 0.Q*618P$ G>L(+3uTk$^&  9b!8j _#`%v6ip4Q*+0!;KgW@DI  )&r:$8H"=' {c*A2oZM~.5haC,1 E2U6[yS(lq4YP s9]0/'VBFN /X ,3t 5-w1}|xe\?O"#%Jmd)<zR7.7-n f Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.) (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) (support for multiple domains on multisite websites) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.No Adverts for Friends plugin is %s.Domain Mapping support plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting Moderation plugin is %sBad Behaviour not found. Please check your install.Bad Behaviour support is %s.Cache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Don’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLegacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching.Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.One or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Update Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: wp-super-cache 0.9.9.6 Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-09-27 13:58+0000 PO-Revision-Date: Last-Translator: Fredrik Forséll Language-Team: Faffe MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Swedish X-Poedit-Country: SWEDEN X-Poedit-SourceCharset: utf-8 Plural-Forms: nplurals=2; plural=n != 1; Kontrollera att de syns före alla existerande WordPress regler.%1$s är Digg säker tack vare cachning av %2$s%1$s underhålls och är utvecklat av %2$s med stöd från många andra.%s Cachade sidor%s Utgågna sidor%s är skrivbar. Var vänlig gör den skrivskyddad efter att din sida är genererad eftersom det här är en säkerhetsrisk.%s borttaget!%s.htaccess har uppdaterats med dom nödvändiga mod_rewrite reglerna. Var vänlig kontrollera att dom är rätt. Dom ska se ut såhär:%s/advanced-cache.php finns inte eller kan inte uppdateras.(1 = mindre, 5 = mer, kan orsaka tyngre server belastning.) (Experimentellt)(endast föråldrad cache stöds, inaktiverad kompression och kräver Bad Behavior i "%s/plugins/bad-behavior/")(Ta bort texten "Din kommentar väntar på moderering." när någon lämnar en modererad kommentar.)(kanske inte alltid är helt korrekt på upptagna sidor)(logga bara förfrågningar från den här IP adressen. Din IP är %s)(kräver friendsadverts.php också) (stöd för flera domäner på flera webbplatser)1. Om den redan finns var vänlig radera filen först.2. Gör %1$s skrivbar genom att använda chmod kommandot genom din ftp eller server programvara. (chmod 777 %1$s) och uppdatera den här sidan. Det här är endast en tillfällig åtgärd och du måste göra den read only igen efteråt. (Ändra 777 till 755 i det föregående kommandot)3. Ladda om den här sidan för att uppdatera %s/advanced-cache.php304 Not Modified webbläsarcaching. Indikerar när en sida inte har modifierats sedan den senast hämtades.304-stöd är avstängt som standard eftersom GoDaddy förut har haft problem med några av sidhuvudena som använts.No Adverts for Friends-tillägget är %sDomain Mapping-tilläget är %s

    WP_CACHE konstant tillagd i wp-config.php

    Om du fortsätter att se det här varningsmeddelandetvar vänlig läs punkt 5 i FAQ. WP_CACHE raden måste flyttas upp.

    WP_CACHE-konstanten är sat till falskt

    WP_CACHE-konstanten används av WordPress för att ladda koden som presenteras cachade sidor. Tyvärr är den satt till falskt. Var vänlig redigera din wp-config.php och lägg till eller redigera följande rad ovanför det sista require_once-kommandot:

    define('WP_CACHE', true);

  • 1. Öppna %1$s$wp_cache_file i en text redigerare.
  • 2. Ändra texten CACHEHOME till %2$s
  • 3. Spara filen och kopiera den till %3$s och ladda om den här sidan.
    • Fel: WP_CACHE är inte aktiverad i din wp-config.php fil och jag kunde inte ändra den.Garbage Collection
    Senaste GC gjordes %s minuter sedan
    Varning! Du försökte aktivera komprimering men zlib.output_compression är aktiverad. Se #21 i felsökningssektionen i readme-filen.En anpassad url- eller permalänkstruktur behövs för att detta tillägg ska fungera korrekt. Var vänlig gå till Inställningssidan för Permalänkar och ställ in dina permalänkar.En skillnad mellan reglerna i din .htaccess-fil och tilläggets omskrivningsregler har hittats. Det kan bero på enkla blankstegsfel men du bör kontrollera reglerna i filen mot de nedan snarast. Clicka på ’Uppdatera Mod_Rewrite-reglerna’-knappen för att uppdaterna reglerna.Ett enkelt sätt att göra detta är att ändra rättigheterna tillfälligt genom att använda CHMOD kommandot eller genom din ftp-klient. Kontrolllera att den är globalt skrivbar och det ska gå bra.Accepterade filnamn & Avvisade URI:erLägg till direkt sida:Lägg till strängar (inte ett filnamn) som tvingar en sida att inte vara cachad. Som exempel, om dina URL:er innehåller år och du vill inte cacha föregående års inlägg, räcker det med att specifiera året, e.x. ’/2004/’. WP-Cache kommer kontrollera om den strängen är en del URI:n och isåfall, inte cacha den sidan.Lägg till de filnamn som kan bli cachade, även om de matchar en av de avvisade strängarna angivna ovan.Lägg till reglerna själv. Redigera %s.htaccess och hitta blocket med kod som omsluts av raderna # BEGIN WPSuperCache och # END WPSuperCache. Det är två delar som ser väldigt lika ut. Precis nedanför raden %%{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ lägg till den här raden: (gör det två gånger, en för varje del)AvanceratÅlderAlternativt, du kan redigera din %s.htaccess fil manuellt och lägga till följande kod (före alla WordPress regler):ArkivTillgängliga tilläggTillägget Awaiting Moderation är %sBad Behaviour hittades inte. Var vänlig kontrollera din installation.Bad Behaviour-stöd är %s.Cache innehållCachetestareCacheträffar för den här webbplatsen för snabb åtkomst.Cachetillägg är PHP-script som finns i en tilläggsmapp i wp-super-cache-mappen. De laddas när Supercache laddas, mycket tidigare än vanliga WordPresstillägg.Cacheombyggning. Presentera en supercachefil till anonyma användare medan en ny fil genereras.Cachestatistik genereras inte automatiskt. Du måste klicka på länken nedan för att generera statistiken på den här sidan.Cachestatistik genererades senast för %s minuter sedan.Cachades för %s sekunder sedanCachade sidor sedan %1$s : %2$sCachningCachning avCachning påCachning måste vara aktiverad för att använda den här funktionenAvbryt cache-förladdningKan inte fortsätta... rätta till tidigare problem och försök igen.Kan inte uppdatera .htaccessKategoriÄndra utgångKontrollera framsidan var 5:e minut.Att leta efter och radera utgångna filer är kostsamt, men det är kostsamt att lämna dom där också. På en väldigt upptagen sida bör du ställa utgångstiden till 300 sekunder. Experimentera med olika värden och besök den här sidan för att se hur många utgångna filer som finns kvar vid olika tidpunkter under dagen. Om du använder förlådrad caching , sikta på att ha färre än 500 cachade sidor om möjligt. Du kan ha många gånger fler cachade filer när du använder mod_rewrite eller PHP-caching.Rensar upp gamla supercachefiler.Rensa alla cachefiler när ett inlägg eller sida publiceras.Rensa cache vid fel.Enkel fillåsning. Du behöver antagligen inte det här men det kan hjälpa om din server är överbelastad. Varning! Kan göra så att din server låser sig i unika fall!Kommentarsmoderering är aktiverad. Dina kommentarer kan ta ett tag innan de visas.Komprimera sidor så att de presenteras snabbare för besökare.Komprimering är inaktiverat som standard för vissa värdar har problem med komprimerade filer. Att sätta på eller stänga av det här rensar cachen.Konfigurationsfil ändrad, några värden kan vara fel. Ladda sidan igen från "Inställningar"-menyn för att återställa dom.Konfigurations fil saknas och %1$s katalogen (%2$s) är inte skrivbar av web servern. Kontrollera dess rättigheter.För närvarande cachas från inlägg %d till %d.Loggar just nu till:DebugFelsökningRaderaRadera CacheRadera utgångnaRadera Super Cache cachade filer (öppnas i nytt fönster)Radera cachade filerRadera tilläggets mod_rewrite regler i %s.htaccess omslutet av # BEGIN WPSuperCache och # END WPSuperCache och låt tillägget återskapa dom genom att ladda om den här sidan.Raderar supercache filen: %s
    Raderar wp-cache filen: %s
    Utvecklare: Gör ditt tillägg Lock Down kompatibelt genom att kontrollera "WPLOCKDOWN" konstanten. Följande kod gör att ditt tillägg respekterar WPLOCKDOWN inställningen.Direkt cachade filerDirekt cachade filer är filer skapade direkt från %s där din blogg bor. Den här funktionen är bara användbar om du förväntar en stor Digg eller Slashdot höjning av trafik till ett inlägg eller en sida.InaktiveraInaktiveradCacha inte följande sidtyper. Läs Conditional Tags dokumenten för en komplett diskussion av varje typ.Domain Mapping-tillägget detekterat! Var vänlig gå till Supercache-tilläggets sida och aktivera domain mapping hjälp-tillägget.Cacha inte sidor för kända användare.EnkelRedigera %s och lägg till följande rad:
    define('WP_CACHE', true);
    Annars kommer inte WP-Cache köras av WordPresskärnan.E-mailSkicka e-mail till blogg administratören när kontroller görs. (användbart för testning)AktiveraAktiveradFelFel: GZIP komprimering är aktiverad, inaktivera det om du vill aktivera wp-cache.Existerande direkta sidorUtgångstid:Utgångna filer är filer äldre än %s sekunder. Dom används fortfarande av tillägget och raderas periodvis.Utgångs tid & upprensningFlödenHämtar %s till den primära cachen:Hämtar första kopian av %s:Hämtar en andra kopia av %s:Laga konfigurationRätta till problem med tillägget genom att felsöka det här. Det kan skicka dig felsöknings e-mail eller logga dom till en fil i din cache katalog.För bästa prestanda ska du aktivera "Stöd för mobila enheter" eller radera de mobila omskrivningsreglerna i din .htaccess. Leta efter de 2 raderna med texten "2.0\ MMP|240x320" och radera dessa. Som exempel: för att cacha %1$sabout/, ska du skriva %1$sabout/ eller /about/. Den cachade filen kommer genereras nästa gång en anonym användare besöker den sidan.Färska Super Cachade filerFärska WP-Cachade filerFramsidaFramsides textFullständig uppdatering om %d timmar %d minuter och %d sekunder.GZIP-komprimering är aktiverat i WordPress, wp-cache kommer bli kringgått tills du har inaktiverat gzip-komprimering.UpprensningGzip-kodningsregler i %s.htaccess skapade.Han bloggar på %1$s och lägger ut bilder på %2$s.Dölj fil-listaHemJag är 99% säker på att det inte är några buggar i WP Super Cache och dom händer bara i undantagsfall men du kan köra en enkel kontroll var 5:e minut för att kontrollera att din sida är ok om du är orolig. Du kommer få ett e-mail om det är några problem.IP AdressOm det inte fungerar, kontrollera att filen %s/advanced-cache.php inte finns:Om utgångstiden är mer än 1800 sekunder (en halvtimme), kommer upprensning köras var 10:e minut, annars kommer den köras 10 sekunder efter utgångstiden ovan.Om du avinstallerar det här tillägget, kontrollera att katalogen %s är skrivbar av webservern så att filerna advanced-cache.php och cache-config.php kan raderas automatiskt. (Att kontrollera att dessa filer är skrivbara är antagligen också en bra idé) I ’Förladdningsläge’ kommer upprensningen bara ta bort gamla filer för kända användare, inte de förladdade supercachefilerna. Det är en rekommenderad inställning när cachen är förladdad.I väldigt ovanliga fall kan två problem dyka upp på vissa bloggar:
    1. Framsidan kan börja laddas ner som en zip fil.
    2. Fel sida blir ibland cachad som framsidan om din blogg använder en statisk framsida och permalänk strukturen är /%category%/%postname%/.
    Det verkar som att mod_rewrite inte är installerat. Ibland är inte den här kontrollen 100% tillförlitlig, speciellt om du inte använder Apache. Var vänlig kontrollera att mod_rewrite-modulen laddas. Det är nödvändigt för att skapa Super Cache statiska filer. Du kan fortfarande använda föråldrade och PHP-lägena.Det verkar som att din blogg har URL:er som slutar med en "/". Tyvärr eftersom du har installerat det här tillägget har en dubbelt-innehåll-bugg hittats där URL:er som inte slutar med "/" visar samma innehåll som dom med "/" och vidarebefordrar inte till rätt URL. För att laga, måste du redigera din .htaccess fil och lägga till de här två reglerna till de två grupperna med Super Cache regler:NyckelFöråldrad sidcachingMindre e-post, 1 i början och 1 i slutet av förladdning av alla inlägg.Lista alla cachade filerLista de senast cachade sidorna på den här sidan.Lock DownLock Down:Logg nivåLoggnings sättLogga till en fil är lättare men stöter på problemet att rensas cachen så rensas logg-filen.Gör WordPress snabbareTöm textboxen för att radera den från listan över direkta sidor och radera den cachade filen.Mycket e-post, 2 brev per 100 inlägg.Mellan, 1 brev per 100 inlägg.DiverseSaknade ApachemodulerStöd för mobila enheter.Mobila omskrivningsregler hittadeMobilt stöd kräver extra regler i din .htaccess fil, eller så kan du ställa in tillägget på föråldrat läge. Här är dina valmöjligheter (sorterat efter svårighetsgrad):Mod Rewrite reglerMod Rewrite reglerna kan inte uppdateras!Mod Rewrite regler måste uppdateras!Mod Rewrite regler uppdaterade!Mod rewrite kanske inte är installerat!Mod_rewrite är det snabbaste, PHP är nästan lika snabbt och enklare att få igång, medans föråldrat läge är långsammare, men mer flexibelt och också enkelt att få igång. Nya användare bör starta med PHP-caching.Behöver du hjälp? Kolla Super Cache readme-filen. Den innehåller installationsdokumentation, en FAQ och felsökningstips. Supportforumet finns också. Din fråga kanske redan har besvarats.Senast cachade sidor:Nästa GC om %s minuterNotera:Observera: aktiverar PHP-cachning, cacheombyggnad och stöd för mobila enheterObservera: Mod_rewrite eller föråldrar cachning aktiverad. Visar avancerade inställningar som standard.Observera: Supercache mod_rewrite-regler detekterades. Cachade filer kommer att presenteras med de reglerna. Redigera .htaccess-filen i roten för din installation och ta bort Supercachereglerna.Observera: WP Super Cache mod_rewrite regelkontroller är avstängda när du inte kör på huvudsidan i nätverket.Observera: WP Super Cache mod_rewrite regelkontroller är avstängda när du inte kör på huvudsidan i nätverket.OKObjektcache används. Ingen cachelistning möjlig.En eller flera sidförfrågningar misslyckades:Uppdatera endast aktuell sida när en kommentar läggs in.PHP komprimerar datat som sänds till besökare på din webbsida. Det rekommenderas att stänga av det eftersom tillägget sparar det komprimerade utdatat en gång i stället för att komprimera samma sida om och om igen. Se också #21 på felsökningssidan. Se denna sida för instruktioner hur du ändrar din php.ini.Sida %d: %d (%s):Sida 1: %sSida 2: %sSidorFel på permalänkstrukturenVar vänlig skapa %s /wp-cache-config.php från wp-super-cache/wp-cache-config-sample.phpVar vänlig säg hej till honom på %s också!Var vänlig läs inlägg 16 i Felsökningsdelen av readme.txtSe readme.txt för instruktioner om hur man avinstallerar detta script. Leta efter rubriken "How to uninstall WP Super Cache".Var vänlig gå till %1$s för att rensa cachen eftersom framsidan på din sida inte är rätt och saknar texten, "%2$s"!Var vänlig gå till %s för att rensa cachen eftersom framsidan av din sida nu laddas ner!TilläggFörladdaFörladda %s inlägg.Förladda cache nuFörladdning har startats om. %sFörladdningsläge (upprensning av endast gamla filer. Rekommenderat.)Förladdning skapar massor med filer. Cachning görs från det nyaste inlägget till det äldsta, så fundera på att bara cacha de nyaste om du har massor (10000+) inlägg. Det är särskilt viktigt med en delad webbserver.Förladdning av cache är avaktiverat. Var vänlig avaktivera föråldrat läge eller prata med din serveradministratör.Förbered din server för en förmodad topp i trafiken genom att aktivera Lock Down. När denna är aktiverad kommer nya kommentarer till ett inlägg inte uppdatera dom cachade statiska filerna.Berätta stolt för världen att din server är Diggsäker! (placerar ett meddelande i din bloggs sidfot)Skrivskyddat läge. Konfigurationen kan inte ändras.Skrivskyddad:RekommenderatUppdatering av cache om %d timmar %d minuter och %d sekunder.Uppdatera förladdade cachefiler var %s minut. (0 för att stänga av, minst %d minuter.)Uppdatera den här sidan när filrättigheterna har ändrats.Uppdatera den här sidan när du har uppdaterat din .htaccess fil.Uppdaterade följande inlägg:Regenerera cachestatistikAvvisade User AgentsKrävs för att visa komprimerade supercache filer korrekt.Krävs för att ställa in cacheinformation på supercache sidor. IE7 användare kommer se gamla sidor utan den här modulen.Återställ standardinställningarMod Rewrite regler måste uppdaterasRegler måste läggas till i %s också:Exempel WP-Cache konfigurations fil (%s) finns inte. Kontrollera din installation.SparaSpara filerSpara strängarSpara UA strängarSchemalagd förladdning av cachen avbruten.Schemalagd förladdning av cachen avbruten. Om ett jobb för tillfället körs kommer det inte att stängas av förrän de nuvarande 100 sidorna är färdiga.Schemalagd förladdning av cachen om %d minuter.Schemalagd förladdning av cachen om 10 sekunder.Schemalägger nästa uppdatering av förladdning om %d minuter.Skrolla ner till de avancerade inställningarna och klicka på knappen Uppdatera Mod_Rewrite Reglerna.SöksidorSkicka status-epost till mig när filerna uppdateras.Skicka osäker (icke https) förfrågan om hemsidaStäll in utgångsdatum på supercachade sidor. Besökare kanske inte ser nya sidor när dom laddar om eller lämnar en kommentar utan den här modulen.Sätt utgångstiden till 0 sekunder för att stänga av upprensning.Ställ in tillägget på föråldrat läge och aktivera mobilt stöd.InställningarEnstaka inläggTyvärr. Min blogg är låst. Uppdateringar kommer snart att synasGamla Super Cachade filerGamla WP-Cachade filerSträngar i ’User Agent’ huvudet som förhindrar WP-Cache från cachande robotar, spindlar och crawlers’ förfrågningar. Notera att super cachade filer skickas fortfarande till dessa agenter om dom redan existerar.EtiketterTesta CacheTesta din cachade websida genom att genom att klicka på testknappen nedan.Testare & innehållText att leta efter på din framsida. Om den här texten fattas kommer cachen att rensas. Lämna tomt för att inaktivera.Tack för att du uppgraderat.WP Super Cache-konfigurationsfilen är %s/wp-cache-config.php och kan inte ändras. Den filen måste vara skrivbar av web-servern för att kunna göra några ändringar.Cachen till din blogg har rensats för framsidan på din sida saknar texten "%2$s". Var vänlig gå till %1$s för att bekräfta att cachen har rensats.Cachen till din blogg har rensats för framsidan av din sida laddas nu ner. Var vänlig gå till %s för att bekräfta att cachen har rensats.Filen %s.htaccess kan inte ändras av webservern. Var vänlig rätta till detta genom att använda chmod kommandot eller din ftp klient.Följande Apache moduler saknas. Tillägget fungerar i föråldrat läge utan dessa. I fullt Supercache läge kan dina besökare dock se förvanskade sidor eller gammalt innehåll.Mod_rewrite reglerna har ändrats sedan du senast installerade det här tillägget. Tyvärr måste du ta bort de gamla supercache reglerna innan de nya är uppdaterade. Uppdatera den här sidan när du har redigerat din .htaccess fil. Om du vill uppgradera manuellt, ändra följande rad: %1$s så den ser ut såhär: %2$s De enda ändringarna är "HTTP_COOKIE" blir "HTTP:Cookie" och "wordpressuser" blir "wordpress". Det här är en WordPress 2.5 ändring men det är bakåt kompatibelt med äldre versioner om du är modig nog att använda dem.Sidorna matchar inte! Tidsstämplarna är olika eller hittades inte!Rewrite-reglerna som krävs för detta tillägg har ändrats eller saknas.Tidsstämplarna på sidorna matchar!Detta är en avancerad funktion och kunskap om både PHP och WordPress agerande behövs för att skapa dem.Det här kommer att cacha varje publicerat inlägg och sida på din webbplats. Det kommer att skapa statiska supercachefiler så att okända besökare (inklusive bottar) kommer att träffa en cachad sida. Det kommer antagligen att hjälpa din Google-rankning eftersom de numera använder hastighet som ett mätvärde när det bedömer webbplatser.Det här har ingen påverkan på vanliga användare men mobila användare kommer se ocachade sidor.För att visa statiska html filer måste din server ha korrekta mod_rewrite regler tillagda i en fil som heter %s.htaccessFör många cachade filer, listning ej möjlig.Efterföljande slash kontroll krävs.URITyvärr kan inte WordPress hitta filen wp-cron.php. Det här skriptet krävs för att upprensningen av det här tillägget ska fungera korrekt, WordPress schemalagda inlägg såväl som andra kritiska aktiviteter.Tyvärr kan inte omskrivningsreglerna uppdateras automatiskt när WordPress MU körs. Var vänlig öppna din .htaccess och lägg till följande mod_rewrite regel över alla andra regler i den filen.Uppdatera direkta sidorUppdatera Mod_Rewrite ReglernaUppdatera inställningarUppdatera StatusAnvänd PHP för att presentera cachade filer.Använd mod_rewrite för att serva cachefiler.Använd objektcache för att lagra cachade filer.Visa Mod_Rewrite reglerWP Super Cache-inställningarWP Super Cache har kontrollerat framsidan på din blogg. Var vänlig gå till %s om du vill inaktivera detta.WP Super Cache är inaktiverat. Var vänlig gå till tilläggets administrations sida för att aktivera cachning.WP Super Cache mod rewrite regler hittades i din %s.htaccess fil.
    Klicka på följande länk för att se raderna som lagts till i den filen. Om du har uppgraderat tillägget kontrollera att reglerna överensstämmer.WP Super Cache måste ställas in. Gå till administrations sidan för att aktivera och konfigurera tillägget.WP-CacheWP-Super-CacheVarningVarning!Varning! %s är skrivbar!Varning! PHP Safe Mode aktiverat!Varning! Ditt värdnamn "%s" löses upp till %sWordPress MU detekteratWordPress är låst. Super Cache statiska filer kommer inte raderas när nya kommentarer är gjorda.WordPress är inte låst. Nya kommentarer kommer uppdatera Super Cache statiska filer som vanligt.Skrivbar:Du kan redigera filen själv och lägga till följande regler.Du kan se var reglerna går och utforska de kompletta reglerna genom att klicka "Visa mod_rewrite regler" länken nedan.Du kan uppleva problem när du använder det här tillägget eftersom SAFE MODE är aktiverat.Du måste ha BEGIN och END markeringar i %s.htaccess för att automatisk uppdatering ska fungera. Dom ser ut såhär om omger de huvudsakliga WordPress mod_rewrite reglerna:Du måste göra %s skrivbar för att aktivera den här funktionen. Eftersom det här är en säkerhetsrisk, gör den skrivskyddad efter att din sida är genererad.Du eller en administratör kan få det att fungera genom att ändra grupp-ägaren av pluginskripten till att passa webserver användaren. Gruppägaren av mappen %s/cache/ måste också ändras. Läs safe mode manualsidan för mer information.Du eller en administratör måste inaktivera det här. Läs safe mode manualsidan för mer information. Det här kan tyvärr inte inaktiveras i en .htaccess fil. Det måste göras i konfigurationsfilen php.ini.Du bör ändra rättigheterna på %s och göra dom mer restriktiva. Använd din ftp-klient, eller följande kommando för att rätta till:Din %s.htaccess är inte skrivbar av webservern och måste uppdateras med dom nödvändiga mod_rewrite reglerna. Dom nya reglerna ska finnas över dom vanliga WordPress reglerna som i koden nedan:Din WP-Cache konfigurations fil (%s) är för gammal och inte skrivbar av web servern. Var vänlig radera den och uppdatera den här sidan.Din cache katalog ($cache_path) fanns inte och kunde inte skapas av web servern. Kontrollera %s rättigheter.Din cache katalog (%1$s) eller %2$s måste vara skrivbar för att det här tillägget ska fungera. Dubbel-kontrollera det.Din kommentar väntar på moderering.Din server är inställd för att kontrollera ägaren av PHP-skript innan den tillåter dom att läsa och skriva filer.Din server tror ditt värdnamn löses upp till %s. En del tjänster som upprensningen av det här tillägget, och Wordpress schemalagda inlägg kanske inte fungerar korrekt.Zlib utdatakomprimering aktiverad![%1$s] %2$d inlägg uppdaterade[%1$s] Cacheförladdning startad[%1$s] Uppdaterar inlägg från %2$d till %3$d[%s] cacheförladdning färdig.[%s] Framsida kontrollerad![%s] Framsidan är gzippad! Cachen rensad![%s] Fram sidan är gzippad! Var vänlig rensa cachen![%s] Framsidan är inte rätt! Cachen är rensad![%s] Framsidan är inte rätt! Var vänlig rensa cachen![%s] Förladdning kan ha hängt sig.allainaktiveradaktiveradfilsekunderlanguages/wp-super-cache-sr_RS.po000066600000276540152133035240012743 0ustar00# Copyright (C) 2013 # This file is distributed under the same license as the package. msgid "" msgstr "" "Project-Id-Version: WP super cache plugin\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2013-04-16 12:02:02+00:00\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "PO-Revision-Date: 2013-05-07 19:00+0100\n" "Last-Translator: Anja Skrba \n" "Language-Team: Anja Skrba \n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" "Language: Srpski / Serbian\n" "X-Generator: Poedit 1.5.5\n" "X-Poedit-SourceCharset: UTF-8\n" #: ossdl-cdn.php:151 msgid "" "Your website probably uses lots of static files. Image, Javascript and CSS " "files are usually static files that could just as easily be served from " "another site or CDN. Therefore this plugin replaces any links in the " "wp-content and wp-includes directories (except for " "PHP files) on your site with the URL you provide below. That way you can " "either copy all the static content to a dedicated host or mirror the files " "to a CDN by origin pull." msgstr "" "Vaš web sajt verovatno koristi dosta statičnih fajlova. Slikovni, Javascript " "i CSS fajlovi su obično statični fajlovi koji lako mogu da se "" "povlače" sa drugog sajta, ili CDN-a. Iz tog razloga ovaj WordPress " "dodatak zamenjuje sve linkove u wp-content i wp-includes direktorijumima (izuzev PHP fajlova) vašeg sajta, URL-om koji dajete " "dole. Na taj način možete, ili kopirati sav statičan sadržaj na poseban " "hosting server, ili "preslikati" (mirror) fajlove na CDN, pomoću origin pull-a." #: ossdl-cdn.php:152 wp-cache.php:1167 msgid "" "The CDN Sync Tool plugin will help upload files to " "Amazon S3/Cloudfront if you would rather not depend on origin pull. See the " "plugin support forum if you have any queries about this " "plugin." msgstr "" "Dodatak CDN Sync Tool će vam pomoći da prenesete " "fajlove na Amazon S3/Cloudfront, ako radije ne biste da zavisite od origin " "pull-a. Pogledajte forum za podršku dodatku, ako imate " "bilo kakvih pitanja u vezi sa ovim dodatkom." #: ossdl-cdn.php:153 msgid "" "WARNING: Test some static urls e.g., " "%s to ensure your CDN service is fully working before saving changes." msgstr "" "UPOZORENJE: Pre nego snimite izmene, " "isprobajte nekoliko statičnih url-ova, npr. %s , da budete sigurni da vaš " "CDN servis radi u potpunosti." #: ossdl-cdn.php:154 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "" "Možete definisati različite CDN URL-ove za svaki sajt iz mreže višestrukih " "sajtova." #: ossdl-cdn.php:162 msgid "Enable CDN Support" msgstr "Uključiti CDN podršku" #: ossdl-cdn.php:165 msgid "Off-site URL" msgstr "Spoljašnji URL" #: ossdl-cdn.php:168 msgid "" "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "" "Novi URL koji će se koristiti umesto %1$s, za ponovno upisivanje. Bez " "prateće /, molim vas. Primer: %2$s." #: ossdl-cdn.php:172 msgid "Include directories" msgstr "Uključiti direktorijume" #: ossdl-cdn.php:175 msgid "" "Directories to include in static file matching. Use a comma as the " "delimiter. Default is wp-content, wp-includes, which will be " "enforced if this field is left empty." msgstr "" "Direktorijumi koje treba uključiti pri statičkom upoređivanju fajlova. " "Koristite zapetu kao razdvajač. Podrazumevani su wp-content, wp-" "includes, koji će se uključiti ako se ovo polje ostavi prazno." #: ossdl-cdn.php:179 msgid "Exclude if substring" msgstr "Isključiti ako je pod-niz" #: ossdl-cdn.php:182 msgid "" "Excludes something from being rewritten if one of the above strings is found " "in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "" "Isključuje nešto da ne bude presnimljeno, ako se jedan od gornjih stringova " "pronađe među rezultatima koji se podudaraju. Upotrebite zapetu kao " "razdvajač, ovako: .php, .flv, .do, i uvek uključite .php (podrazumevano)." #: ossdl-cdn.php:186 msgid "Additional CNAMES" msgstr "Dodatni CNAME zapisi" #: ossdl-cdn.php:189 msgid "" "These CNAMES will " "be used in place of %1$s for rewriting (in addition to the off-site URL " "above). Use a comma as the delimiter. For pages with a large number of " "static files, this can improve browser performance. CNAMEs may also need to " "be configured on your CDN.
    Example: %2$s" msgstr "" "Ovi CNAME zapisi " "će se koristiti umesto %1$s, za ponovno upisivanje (uz gornji spoljašnji " "URL). Koristite zapetu kao razdvajač. Za strane sa velikim brojem statičkih " "fajlova, ovo može poboljšati performanse pregledača. Takođe, možda treba " "konfigurisati CNAME zapise na vašem CDN-u.
    Primer: %2$s" #: ossdl-cdn.php:193 msgid "Skip https URLs to avoid \"mixed content\" errors" msgstr "" "Preskočiti https URL-ove, da se izbegnu \"pomešani sadržaj (mixed content)\" " "greške" #: ossdl-cdn.php:197 msgid "Save Changes" msgstr "Snimiti izmene" #: ossdl-cdn.php:199 msgid "" "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "" "CDN funkcionalnost koju daje OSSDL CDN Off Linker od Mark Kubacki-a" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Vaš komentar čeka moderaciju." #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "Čekanje na moderaciju" #: plugins/awaitingmoderation.php:34 plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:75 plugins/jetpack.php:27 #: plugins/searchengine.php:69 plugins/wptouch.php:22 wp-cache.php:1405 msgid "Enabled" msgstr "Uključeno" #: plugins/awaitingmoderation.php:35 plugins/badbehaviour.php:66 #: plugins/domain-mapping.php:76 plugins/jetpack.php:28 #: plugins/searchengine.php:70 plugins/wptouch.php:23 wp-cache.php:1405 msgid "Disabled" msgstr "Isključeno" #: plugins/awaitingmoderation.php:36 msgid "" "Enables or disables plugin to Remove the text \"Your comment is awaiting " "moderation.\" when someone leaves a moderated comment." msgstr "" "Uključuje ili isključuje dodatak za uklanjanje teksta \"Vaš komentar čeka " "moderaciju (Your comment is awaiting moderation).\", kada neko ostavi " "moderisani komentar." #: plugins/awaitingmoderation.php:40 plugins/badbehaviour.php:71 #: plugins/domain-mapping.php:81 plugins/jetpack.php:33 #: plugins/searchengine.php:75 plugins/wptouch.php:28 wp-cache.php:1866 #: wp-cache.php:1868 msgid "enabled" msgstr "uključeno" #: plugins/awaitingmoderation.php:42 plugins/badbehaviour.php:73 #: plugins/domain-mapping.php:83 plugins/jetpack.php:35 #: plugins/searchengine.php:77 plugins/wptouch.php:30 msgid "disabled" msgstr "isključeno" #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "Čekanje na moderaciju je sada %s" #: plugins/awaitingmoderation.php:45 plugins/badbehaviour.php:76 #: plugins/domain-mapping.php:86 plugins/jetpack.php:38 #: plugins/searchengine.php:80 plugins/wptouch.php:33 msgid "Update" msgstr "Ažurirati" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "Bad Behaviour nije pronađen. Molim vas, proverite vašu instalaciju." #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "Bad Behaviour (nepristojno ponašanje)" #: plugins/badbehaviour.php:68 msgid "" "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-" "behavior/\") " msgstr "" "(Podržano je samo nasleđeno keširanje, kompresija je isključena, i traži se " "Bad Behaviour u " "direktorijumu \"%s/plugins/bad-behavior/\") " #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "Podrška za Bad Behaviour je sada %s" #: plugins/badbehaviour.php:83 wp-cache.php:1495 wp-cache.php:1500 msgid "Warning!" msgstr "Upozorenje!" #: plugins/domain-mapping.php:73 msgid "Domain Mapping" msgstr "Domain Mapping (mapiranje domena)" #: plugins/domain-mapping.php:78 msgid "" "Provides support for Domain Mapping plugin to map multiple domains to a " "blog." msgstr "" "Obezbeđuje podršku za Domain Mapping dodatak, za uparivanje " "(mapiranje) više domena sa blogom." #: plugins/domain-mapping.php:84 msgid "Domain Mapping support is now %s" msgstr "Podrška za Domain Mapping je sada %s" #: plugins/domain-mapping.php:98 msgid "" "Domain Mapping plugin detected! Please go to the Supercache plugins page and " "enable the domain mapping helper plugin." msgstr "" "Pronađen je dodatak Domain Mapping! Molim vas, idite na stranu Supercache " "dodataka i uključite pomoćni dodatak za mapiranje domena." #: plugins/jetpack.php:25 msgid "Jetpack Mobile Theme" msgstr "Jetpack tema za mobilne uređaje" #: plugins/jetpack.php:30 msgid "" "Provides support for the Jetpack mobile theme and plugin. PHP caching mode and mobile " "support will be enabled too." msgstr "" "Obezbeđuje podršku za Jetpack temu, i dodatak, za mobilne uređaje." #: plugins/jetpack.php:36 msgid "Jetpack Mobile Theme support is now %s" msgstr "Podrška za Jetpack temu za mobilne uređaje je sada %s" #: plugins/multisite.php:13 msgid "Cached" msgstr "Keširano" #: plugins/multisite.php:31 wp-cache.php:1418 msgid "Enable" msgstr "Uključiti" #: plugins/multisite.php:33 plugins/searchengine.php:61 wp-cache.php:1418 msgid "Disable" msgstr "Isključiti" #: plugins/multisite.php:39 msgid "Caching has been disabled on this blog on the Network Admin Sites page." msgstr "" "Keširanje na ovom blogu je isključeno na strani za mrežnu administraciju " "sajtova (Network Admin Sites)" #: plugins/searchengine.php:67 msgid "No Adverts for Friends" msgstr "No Adverts for Friends (bez reklama za prijatelje)" #: plugins/searchengine.php:72 msgid "" "Provides support for No Adverts for Friends." msgstr "" "Obezbeđuje podršku za No Adverts for Friends." #: plugins/searchengine.php:78 msgid "No Adverts for Friends support is now %s" msgstr "Podrška za No Adverts for Friends je sada %s" #: plugins/wptouch.php:20 msgid "WPTouch" msgstr "WPTouch" #: plugins/wptouch.php:25 msgid "" "Provides support for WPTouch mobile theme and plugin." msgstr "" "Obezbeđuje podršku za WPTouch temu, i dodatak, za mobilne uređaje" #: plugins/wptouch.php:31 msgid "WPTouch support is now %s" msgstr "Podrška za WPTouch je sada %s" #: plugins/wptouch.php:45 msgid "" "WPTouch plugin detected! Please go to the Supercache plugins page and enable " "the WPTouch helper plugin." msgstr "" "Pronađen je dodatak WPTouch! Molim vas, idite na stranu Supercache dodataka " "i uključite pomoćni dodatak za WPTouch." #: wp-cache-phase2.php:1257 msgid "Cache expiry cron job failed. Job will run again in 10 seconds." msgstr "" "Cron zadatak za istek keša nije uspeo. Zadatak će se ponovo pokrenuti za 10 " "sekundi." #: wp-cache-phase2.php:1261 msgid "" "Cache expiry cron job took more than 30 seconds. You should probably run the " "garbage collector more often." msgstr "" "Cron zadatku za istek keša je trebalo više od 30 sekundi. Verovatno bi " "trebalo da češće pokrećete sakupljač smeća." #: wp-cache-phase2.php:1270 msgid "[%1$s] WP Super Cache GC Report" msgstr "[%1$s] WP Super Cache izveštaj o sakupljanju smeća (GC Report)" #: wp-cache.php:99 msgid "" "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-" "sample.php" msgstr "" "Molim vas, napravite fajl %s /wp-cache-config.php iz fajla wp-super-cache/wp-" "cache-config-sample.php" #: wp-cache.php:165 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Upozorenje! Uključen je PHP siguran način rada (safe mode)!" #: wp-cache.php:166 msgid "" "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "" "Možete imati problema pri radu sa ovim dodatkom, jer je uključen SIGURAN MOD " "(safe mode)." #: wp-cache.php:170 msgid "" "Your server is set up to check the owner of PHP scripts before allowing them " "to read and write files." msgstr "" "Vaš server je podešen tako da proverava vlasnika PHP skripti, pre nego im " "dozvoli da čitaju i upisuju podatke u fajlove." #: wp-cache.php:171 msgid "" "You or an administrator may be able to make it work by changing the group " "owner of the plugin scripts to match that of the web server user. The group " "owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further " "details." msgstr "" "Vi, ili administrator, možda možete učiniti da proradi, menjanjući grupnog " "vlasnika skripti tako da se poklopi sa korisnikom web servera. Grupni " "vlasnik direktorijuma %s/cache/ takođe mora da se promeni. Za još detalja " "pogledajte stranu sa uputstvom " "za siguran mod." #: wp-cache.php:173 msgid "" "You or an administrator must disable this. See the safe mode manual page for further details. This " "cannot be disabled in a .htaccess file unfortunately. It must be done in the " "php.ini config file." msgstr "" "Vi, ili administrator, morate isključiti ovo. Za dalje informacije " "pogledajte stranu sa uputstvom " "za siguran mod. Na žalost, ovo se ne može isključiti u fajlu .htaccess. " "To se mora uraditi u konfiguracionom fajlu php.ini." #: wp-cache.php:179 msgid "Permlink Structure Error" msgstr "Greška permalink strukture" #: wp-cache.php:180 msgid "" "A custom url or permalink structure is required for this plugin to work " "correctly. Please go to the Permalinks " "Options Page to configure your permalinks." msgstr "" "Da bi ovaj dodatak pravilno radio, potreban je prilagođeni url, ili " "prilagođena permalink struktura. Molim vas, idite na Stranu sa opcijama vezanim za permalinkove (Permalinks " "Options Page), da konfigurišete vaše permalinkove." #: wp-cache.php:192 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Upozorenje! Vaše host ime \"%s\" ukazuje na %s" #: wp-cache.php:193 msgid "" "Your server thinks your hostname resolves to %s. Some services such as " "garbage collection by this plugin, and WordPress scheduled posts may not " "operate correctly." msgstr "" "Vaš server \"misli\" da vaše host ime ukazuje na %s. Neki servisi, poput " "sakupljanja smeća od strane ovog dodatka, i WordPress zakazanih objava, " "možda ne funkcionišu ispravno." #: wp-cache.php:194 wp-cache.php:208 msgid "" "Please see entry 16 in the Troubleshooting section of the " "readme.txt" msgstr "" "Molim vas, pogledajte stavku 16 u Troubleshooting section " "(Sekciji o otklanjanju problema) readme.txt fajla" #: wp-cache.php:207 msgid "" "Unfortunately WordPress cannot find the file wp-cron.php. This script is " "required for the the correct operation of garbage collection by this plugin, " "WordPress scheduled posts as well as other critical activities." msgstr "" "Na žalost, WordPress ne može da pronađe fajl wp-cron.php. Ova skripta je " "potrebna za pravilno funkcionisanje sakupljanja smeća od strane ovog " "dodatka, WordPress zakazanih objava, i drugih kritičnih aktivnosti." #: wp-cache.php:221 msgid "Cannot continue... fix previous problems and retry." msgstr "" "Nije moguće nastaviti... otklonite prethodne probleme i pokušajte ponovo." #: wp-cache.php:230 msgid "Zlib Output Compression Enabled!" msgstr "Zlib izlazna kompresija je uključena!" #: wp-cache.php:231 msgid "" "PHP is compressing the data sent to the visitors of your site. Disabling " "this is recommended as the plugin caches the compressed output once instead " "of compressing the same page over and over again. Also see #21 in the " "Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "" "PHP komprimuje podatke koji se šalju posetiocima vašeg sajta. Isključivanje " "ovoga se preporučuje, jer dodatak kešira komprimovani izlaz jednom, umesto " "komprimovanja iste strane iznova i iznova. Takođe pogledajte #21 u sekciji o " "otklanjanju problema (Troubleshooting section). Pogledajte ovu stranu za instrukcije o " "modifikovanju vašeg php.ini fajla." #: wp-cache.php:235 msgid "Mod rewrite may not be installed!" msgstr "Mod rewrite možda nije instaliran!" #: wp-cache.php:236 msgid "" "It appears that mod_rewrite is not installed. Sometimes this check isn’" "t 100% reliable, especially if you are not using Apache. Please verify that " "the mod_rewrite module is loaded. It is required for serving Super Cache " "static files. You will still be able to use legacy or PHP modes." msgstr "" "Izgleda da mod_rewrite nije instaliran. Ponekad ova provera nije 100% " "pouzdana, posebno ako ne koristite Apache. Molim vas, potvrdite da je učitan " "modul mod_rewrite. On je potreban za serviranje Super Cache statičnih " "fajlova. I dalje ćete moći da koristite zastarele ili PHP modove." #: wp-cache.php:242 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Mod u kome je moguć samo pregled. Konfiguracija ne može da se menja." #: wp-cache.php:243 msgid "" "The WP Super Cache configuration file is %s/wp-cache-config.php " "and cannot be modified. That file must be writeable by the webserver to make " "any changes." msgstr "" "WP Super Cache konfiguracioni fajl je %s/wp-cache-config.php, i " "ne može se menjati. U taj fajl mora da bude omogućen upis podataka od strane " "web servera, da bi se pravile bilo kakve izmene." #: wp-cache.php:244 msgid "" "A simple way of doing that is by changing the permissions temporarily using " "the CHMOD command or through your ftp client. Make sure it’s globally " "writeable and it should be fine." msgstr "" "Jednostavan način da se to uradi je privremeno menjanje dozvola, koristeći " "naredbu CHMOD, ili preko vašeg ftp klijenta. Postarajte se da u njega " "globalno bude omogućen upis podataka, i trebalo bi sve da bude u redu." #: wp-cache.php:245 wp-cache.php:294 msgid "" "This page explains how to change file permissions." msgstr "" "Ova strana objašnjava kako promeniti dozvole za fajlove." #: wp-cache.php:246 msgid "Writeable:" msgstr "Moguć upis podataka:" #: wp-cache.php:247 msgid "Readonly:" msgstr "Moguć samo pregled:" #: wp-cache.php:265 msgid "Warning! Garbage collection is not scheduled!" msgstr "Upozorenje! Sakupljanje smeća nije zakazano!" #: wp-cache.php:266 msgid "" "Garbage collection by this plugin clears out expired and old cached pages on " "a regular basis. Use this form to enable it." msgstr "" "Sakupljanje smeća od strane ovog dodatka redovno briše istekle i stare " "keširane strane. Upotrebite ovaj obrazac da ga " "uključite." #: wp-cache.php:271 wp-cache.php:299 wp-cache.php:369 msgid "Dismiss" msgstr "Odbaciti" #: wp-cache.php:292 msgid "Warning! %s is writeable!" msgstr "Pažnja! u %s je moguć upis podataka!" #: wp-cache.php:293 msgid "" "You should change the permissions on %s and make it more restrictive. Use " "your ftp client, or the following command to fix things:" msgstr "" "Trebalo bi da na %s promenite dozvole, i učinite ih restriktivnijim. Da " "popravite stvari, upotrebite vaš ftp klijent, ili sledeću naredbu:" #: wp-cache.php:311 msgid "Mobile rewrite rules detected" msgstr "Otkrivena su mobilna pravila za ponovni upis" #: wp-cache.php:312 msgid "" "For best performance you should enable \"Mobile device support\" or delete " "the mobile rewrite rules in your .htaccess. Look for the 2 lines with the " "text \"2.0\\ MMP|240x320\" and delete those." msgstr "" "Za najbolje performanse treba da uključite \"Podršku za mobilne uređaje " "(Mobile device support)\", ili da obrišete mobilna pravila za ponovni upis u " "vašem fajlu .htaccess. Potražite 2 linije sa tekstom \"2.0\\ MMP|240x320\", " "i obrišite ih." #: wp-cache.php:312 msgid "" "This will have no affect on ordinary users but mobile users will see " "uncached pages." msgstr "" "Ovo se neće odraziti na obične korisnike, ali mobilni korisnici će videti " "nekeširane strane." #: wp-cache.php:318 wp-cache.php:329 msgid "Rewrite rules must be updated" msgstr "Pravila za ponovni upis moraju da se ažuriraju" #: wp-cache.php:319 wp-cache.php:330 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "" "Pravila za ponovni upis, koja zahteva ovaj dodatak, su izmenjena, ili " "nedostaju." #: wp-cache.php:320 msgid "" "Mobile support requires extra rules in your .htaccess file, or you can set " "the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "" "Podrška za mobilne uređaje zahteva dodatna pravila u vašem fajlu .htaccess, " "ili možete podesiti dodatak na zastareli mod (legacy mode). Evo vaših opcija " "(poređanih po težini):" #: wp-cache.php:321 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "" "Podesite dodatak na zastareli mod i uključite podršku za mobilne uređaje." #: wp-cache.php:322 wp-cache.php:331 msgid "" "Scroll down the Advanced Settings page and click the Update " "Mod_Rewrite Rules button." msgstr "" "Skrolujte na dole, na strani sa naprednim podešenjima (Advanced Settings), i " "kliknite na dugme Ažurirati mod_rewrite pravila (Update Mod_Rewrite " "Rules)." #: wp-cache.php:323 msgid "" "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN " "WPSuperCache and # END WPSuperCache and let the plugin " "regenerate them by reloading this page." msgstr "" "U %s.htaccess fajlu obrišite mod_rewrite pravila dodatka, smeštena između " "# BEGIN WPSuperCache i # END WPSuperCache, i " "pustite da ih dodatak opet generiše, učitavajući ponovo ovu stranu." #: wp-cache.php:324 msgid "" "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed " "by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line " "%%{HTTP:Cookie} !^.*(comment_author_|%s|wp-postpass_).*$ add " "these lines: (do it twice, once for each section)" msgstr "" "Sami dodajte pravila. Otvorite fajl %s.htaccess u uređivaču, i pronađite " "blok koda koji se nalazi između linija # BEGIN WPSuperCache i " "# END WPSuperCache. Tu se nalaze dve sekcije koje izgledaju " "vrlo slično. Odmah ispod linije %%{HTTP:Cookie} !^.*(comment_author_|" "%s|wp-postpass_).*$ dodajte ove linije: (uradite to dva puta - za " "svaku sekciju)" #: wp-cache.php:337 msgid "Required to serve compressed supercache files properly." msgstr "Potrebno da se pravilno serviraju komprimovani supercache fajlovi." #: wp-cache.php:337 msgid "" "Required to set caching information on supercache pages. IE7 users will see " "old pages without this module." msgstr "" "Potrebno da bi se na supercache stranama postavile informacije o keširanju. " "Korisnici IE7 će videti stare strane, bez ovog modula." #: wp-cache.php:337 msgid "" "Set the expiry date on supercached pages. Visitors may not see new pages " "when they refresh or leave comments without this module." msgstr "" "odešavanje datuma isteka na superkeširanim stranama. Posetioci mogu da ne " "vide nove strane kada osvežavaju sadržaj u pregledaču ili ostavljaju " "komentare, bez ovog modula." #: wp-cache.php:344 msgid "Missing Apache Modules" msgstr "Nedostaju Apache moduli " #: wp-cache.php:345 msgid "" "The following Apache modules are missing. The plugin will work in legacy " "mode without them. In full Supercache mode, your visitors may see corrupted " "pages or out of date content however." msgstr "" "Nedostaju sledeći Apache moduli. Bez njih će ovaj dodatak raditi u " "zastarelom modu. Međutim, u punom Supercache modu, vaši posetioci mogu da " "vide nepotpune strane, ili sadržaj koji više nije važeći." #: wp-cache.php:363 msgid ".htaccess file may need to be moved" msgstr ".htaccess fajl možda treba da se premesti" #: wp-cache.php:364 msgid "" "It appears you have WordPress installed in a sub directory as described here. Unfortunately WordPress writes to the .htaccess in the install " "directory, not where your site is served from.
    When you update the " "rewrite rules in this plugin you will have to copy the file to where your " "site is hosted. This will be fixed in the future." msgstr "" "Izgleda da vam je WordPress instaliran u pod-folderu, kao što je opisano     ovde. Na žalost, WordPress upisuje podatke u .htaccess fajl u instalacionom " "direktorijumu, a ne tamo odakle se vaš sajt servira.
    Kada ažurirate " "pravila za ponovni upis u ovom dodatku, moraćete da kopirate ovaj fajl na " "lokaciju na kojoj se hostuje vaš sajt. Ovo će u budućnosti biti rešeno." #: wp-cache.php:597 msgid "" "Warning! You attempted to enable compression but zlib." "output_compression is enabled. See #21 in the Troubleshooting section " "of the readme file." msgstr "" "Upozorenje! Pokušali ste da uključite kompresiju, ali je " "zlib.output_compression uključeno. Pogledajte #21 u sekciji o " "otklanjanju problema (Troubleshooting section), readme fajla." #: wp-cache.php:693 msgid "WP Super Cache Settings" msgstr "WP Super Cache podešenja" #: wp-cache.php:707 msgid "" "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced " "Settings Page by default." msgstr "" "Obratite pažnju: Uključeni su Mod_rewrite, ili zastarelo keširanje " "(Legacy caching). Podrazumevano je prikazivanje strane sa naprednim " "podešenjima (Advanced Settings)." #: wp-cache.php:718 msgid "" "Configuration file changed, some values might be wrong. Load the page again " "from the \"Settings\" menu to reset them." msgstr "" "Konfiguracioni fajl je izmenjen, neke vrednosti bi mogle biti pogrešne. " "Učitajte stranu ponovo, iz menija \"Podešenja (Settings\", da ih resetujete." #: wp-cache.php:750 msgid "Caching must be enabled to use this feature" msgstr "Da bi se koristilo ovo svojstvo, keširanje mora da bude uključeno" #: wp-cache.php:768 wp-cache.php:908 msgid "Cancel Cache Preload" msgstr "Otkazati učitavanje keša unapred" #: wp-cache.php:776 msgid "" "Scheduled preloading of cache almost cancelled. It may take up to a minute " "for it to cancel completely." msgstr "" "Zakazano učitavanje keša unapred je skoro otkazano. Može potrajati još " "najviše minut dok se ono potpuno otkaže." #: wp-cache.php:787 msgid "Scheduled preloading of cache cancelled." msgstr "Zakazano učitavanje keša unapred je otkazano." #: wp-cache.php:819 wp-cache.php:906 msgid "Preload Cache Now" msgstr "Učitati keš unapred sada" #: wp-cache.php:823 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Zakazano učitavanje keša unapred za 10 sekundi." #: wp-cache.php:828 msgid "Scheduled preloading of cache in %d minutes" msgstr "Zakazano učitavanje keša unapred za %d minuta" #: wp-cache.php:832 msgid "" "This will cache every published post and page on your site. It will create " "supercache static files so unknown visitors (including bots) will hit a " "cached page. This will probably help your Google ranking as they are using " "speed as a metric when judging websites now." msgstr "" "Ovo će keširati svaku objavljenu objavu, ili stranu, na vašem sajtu. " "Napraviće superkeš statične fajlove, tako da će nepoznati posetioci " "(uključujući i botove) pogoditi keširanu stranu. Ovo će vam verovatno pomoći " "kod Google rangiranja, pošto oni sada koriste brzinu kao meru, kada sude o " "web sajtovima." #: wp-cache.php:833 msgid "" "Preloading creates lots of files however. Caching is done from the newest " "post to the oldest so please consider only caching the newest if you have " "lots (10,000+) of posts. This is especially important on shared hosting." msgstr "" "Međutim, učitavanje unapred kreira dosta fajlova. Keširanje se radi od " "najnovije do najstarije objave, tako da, molim vas, ako imate mnogo " "(10,000+) objava, razmislite o tome da keširate samo one najnovije. Ovo je " "naročito važno kod deljenog hostinga." #: wp-cache.php:834 msgid "" "In ’Preload Mode’ regular garbage collection will only clean out " "old legacy files for known users, not the preloaded supercache files. This " "is a recommended setting when the cache is preloaded." msgstr "" "U ’Modu za učitavanje unapred (Preload Mode&)#8217; redovno " "sakupljanje smeća će očistiti samo stare zaostale (legacy) fajlove, za " "poznate korisnike., a ne unapred učitane superkeš fajlove. Ovo je " "podrazumevano podešenje, onda kada se keš učitava unapred." #: wp-cache.php:838 msgid "" "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d " "minutes.)" msgstr "" "Osvežavati unapred učitane keš fajlove svakih %s minuta. (0 za " "isključivanje, najmanje %d minuta.)" #: wp-cache.php:851 msgid "all" msgstr "sve" #: wp-cache.php:864 msgid "Preload %s posts." msgstr "Unapred učitati %s objava." #: wp-cache.php:871 msgid "" "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "" "Mod za učitavanje unapred (Preload mode) (sakupljanje smeća samo nad " "zastarelim keš fajlovima. Preporučeno.)" #: wp-cache.php:874 msgid "Preload tags, categories and other taxonomies." msgstr "Unapred učitati oznake (tags), kategorije i druge taksonomije." #: wp-cache.php:877 msgid "Send me status emails when files are refreshed." msgstr "Slati mi e-mailove kada se fajlovi osvežavaju." #: wp-cache.php:882 msgid "Many emails, 2 emails per 100 posts." msgstr "Mnogo e-mailova, 2 e-maila na 100 objava." #: wp-cache.php:885 msgid "Medium, 1 email per 100 posts." msgstr "Srednje, 1 e-mail na 100 objava." #: wp-cache.php:888 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "" "Manje e-mailova, 1 na početku i 1 na kraju prethodnog učitavanja svih objava." #: wp-cache.php:892 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Osvežavanje keša za %d časova, %d minuta i %d sekundi." #: wp-cache.php:893 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Potpuno osvežavanje keša za %d časova, %d minuta i %d sekundi." #: wp-cache.php:899 msgid "Currently caching from post %d to %d." msgstr "Trenutno se keširaju objave od %d do %d." #: wp-cache.php:903 msgid "Page last cached: %s" msgstr "Poslednja keširana strana: %s" #: wp-cache.php:906 msgid "Update Settings" msgstr "Ažurirati podešenja" #: wp-cache.php:914 msgid "" "Preloading of cache disabled. Please disable legacy page caching or talk to " "your host administrator." msgstr "" "Isključeno je učitavanje keša unapred. Molim vas, isključite keširanje " "zastarelih strana, ili razgovarajte sa vašim hosting administratorom." #: wp-cache.php:931 wp-cache.php:1043 msgid "Caching" msgstr "Keširanje" #: wp-cache.php:935 msgid "Cache hits to this website for quick access." msgstr "Keš pogoci na ovom web sajtu, za brzi pristup." #: wp-cache.php:935 wp-cache.php:936 wp-cache.php:953 wp-cache.php:962 #: wp-cache.php:969 wp-cache.php:972 wp-cache.php:990 wp-cache.php:1046 msgid "Recommended" msgstr "Preporučeno" #: wp-cache.php:936 msgid "Use mod_rewrite to serve cache files." msgstr "Koristiti mod_rewrite za serviranje keš fajlova." #: wp-cache.php:937 msgid "Use PHP to serve cache files." msgstr "Koristiti PHP za serviranje keš fajlova." #: wp-cache.php:938 msgid "Legacy page caching." msgstr "Staro keširanje strana (legacy page caching)." #: wp-cache.php:939 msgid "" "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, " "while legacy caching is slower again, but more flexible and also easy to get " "working. New users should use PHP caching." msgstr "" "Mod_rewrite je najbrži, PHP je skoro isto tako brz, a jednostavniji za " "stavljanje u rad, dok je, opet, staro keširanje (legacy caching) sporije, " "ali je fleksibilnije i, takođe, jednostavnije za stavljanje u rad. Novi " "korisnici bi trebalo da koriste PHP keširanje." #: wp-cache.php:945 msgid "Miscellaneous" msgstr "Razno" #: wp-cache.php:951 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "" "Upozorenje! Kompresija je isključena, jer nije pronađena funkcija gzencode()." #: wp-cache.php:953 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Komprimovati strane, tako da se brže serviraju posetiocima." #: wp-cache.php:954 msgid "" "Compression is disabled by default because some hosts have problems with " "compressed files. Switching it on and off clears the cache." msgstr "" "Kompresija je u startu isključena, jer neki hostinzi imaju problema sa " "komprimovanim fajlovima. Njeno uključivanje i isključivanje brišu keš." #: wp-cache.php:962 msgid "" "304 Not Modified browser caching. Indicate when a page has not been modified " "since last requested." msgstr "" "304 Ne modifikovano (Not Modified) keširanje od strane pregledača. Ukazuje " "kada strana nije izmenjena od poslednjeg zahteva." #: wp-cache.php:965 msgid "" "Warning! 304 browser caching is only supported when not using mod_rewrite " "caching." msgstr "" "Upozorenje! 304 keširanje od strane pregledača je podržano samo kada se ne " "koristi mod_rewrite keširanje." #: wp-cache.php:967 msgid "" "304 support is disabled by default because some hosts have had problems with " "the headers used in the past." msgstr "" "Podrška za 304 je u startu isključena, jer neki hostinzi imaju problema sa " "zaglavljima korišćenim u prošlosti." #: wp-cache.php:969 msgid "" "Don’t cache pages for known users." msgstr "" "Ne keširati strane za poznate korisnike." #: wp-cache.php:970 msgid "Don’t cache pages with GET parameters. (?x=y at the end of a url)" msgstr "Ne keširati strane sa GETparametrima. (?x=y, na kraju url-a)" #: wp-cache.php:971 msgid "" "Make known users anonymous so they’re served supercached static files." msgstr "" "Učiniti poznate korisnike anonimnim, tako da im se serviraju superkeširani " "statički fajlovi." #: wp-cache.php:972 msgid "" "Cache rebuild. Serve a supercache file to anonymous users while a new file " "is being generated." msgstr "" "Ponovna izgradnja keša. Servirati anonimnim korisnicima superkeširani fajl, " "dok se generiše novi fajl." #: wp-cache.php:973 msgid "" "Proudly tell the world your server is     Stephen Fry proof! " "(places a message in your blog’s footer)" msgstr "" "Ponosno recite svetu da je vaš server Stephen Fry proof! " "(postavlja poruku u podnožju vašeg bloga)" #: wp-cache.php:979 wp-cache.php:1256 wp-cache.php:1875 msgid "Advanced" msgstr "Napredno" #: wp-cache.php:983 msgid "" "Enable dynamic caching (mfunc, mclude, dynamic-cached-content). See the FAQ for " "further details.)" msgstr "" "Uključiti dinamičko keširanje (mfunc, mclude, dynamic-cached-content). " "Pogledajte često postavljana pitanja (FAQ) za više detalja.)" #: wp-cache.php:984 msgid "" "Mobile device support. (External plugin or theme required. See the FAQ for " "further details.)" msgstr "" "Podrška za mobilne uređaje. (Potreban je spoljni dodatak, ili tema. " "Pogledajte često postavljana pitanja (FAQ) za više detalja.)" #: wp-cache.php:986 msgid "Mobile Browsers" msgstr "Mobilni pregledači" #: wp-cache.php:986 msgid "Mobile Prefixes" msgstr "Mobilni prefiksi" #: wp-cache.php:988 msgid "" "Remove UTF8/blog charset support from .htaccess file. Only necessary if you " "see odd characters or punctuation looks incorrect. Requires rewrite rules " "update." msgstr "" "Ukloniti UTF8/blog karakter-set podršku iz .htaccess fajla. Potrebno je samo " "ako vidite neobične karaktere, ili interpunkcija izgleda nepravilno. Zahteva " "ažuriranje pravila ponovnog upisa (rewrite rules)." #: wp-cache.php:989 msgid "Clear all cache files when a post or page is published or updated." msgstr "" "Obrisati sve keš fajlove, onda kada se objava ili strana objavi ili ažurira." #: wp-cache.php:990 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "" "Dodatne provere početne strane. (Veoma retko zaustavlja keširanje početne " "strane)" #: wp-cache.php:991 msgid "Only refresh current page when comments made." msgstr "Osvežiti aktuelnu stranu samo kada se ostave komentari." #: wp-cache.php:992 msgid "List the newest cached pages on this page." msgstr "Prikazati listu poslednjih keširanih strana na ovoj strani." #: wp-cache.php:994 msgid "" "Coarse file locking. You probably don’t need this but it may help if " "your server is underpowered. Warning! May cause your server to lock up " "in very rare cases!" msgstr "" "Grubo zaključavanje fajlova. Ovo vam verovatno ne treba, ali može pomoći ako " "je vaš server slabijih mogućnosti. Upozorenje! U vrlo retkim slučajevima " "može izazvati zaključavanje servera!" #: wp-cache.php:996 msgid "" "Late init. Display cached files after WordPress has loaded. Most useful in " "legacy mode." msgstr "" "Kasna inicijalizacija. Prikazuje keširane fajlove nakon što se učita " "WordPress. Najkorisnije u starom modu (legacy mode)." #: wp-cache.php:998 msgid "Use object cache to store cached files." msgstr "Koristiti objektni keš (object cache) za čuvaje keširanih fajlova." #: wp-cache.php:998 msgid "(Experimental)" msgstr "(Eksperimentalno)" #: wp-cache.php:1000 msgid "DO NOT CACHE PAGE secret key: %s" msgstr "NE KEŠIRATI STRANU tajni ključ: %s" #: wp-cache.php:1006 msgid "Note:" msgstr "Napomena:" #: wp-cache.php:1008 msgid "" "Uninstall this plugin on the plugins page. It will automatically clean up " "after itself. If manual intervention is required then simple instructions " "are provided." msgstr "" "De-instalirati ovaj dodatak na strani sa dodacima (plugins). On će " "automatski počistiti za sobom. Ako je potrebna manuelna intervencija, " "obezbedeđene su jednostavne instrukcije." #: wp-cache.php:1009 msgid "" "If uninstalling this plugin, make sure the directory %s is " "writeable by the webserver so the files advanced-cache.php and " "cache-config.php can be deleted automatically. (Making sure those " "files are writeable too is probably a good idea!)" msgstr "" "Ako de-instalirate ovaj dodatak, postarajte se da u direktorijum %s " "bude omogućen upis od strane web servera, tako da fajlovi advanced-cache." "php i cache-config.php mogu automatski da budu obrisani. " "(Osiguravanje da i u ove fajlove bude moguć upis je verovatno dobra ideja!)" #: wp-cache.php:1010 msgid "" "Please see the readme.txt for " "instructions on uninstalling this script. Look for the heading, \"How to " "uninstall WP Super Cache\"." msgstr "" "Molim vas, pogledajte readme.txt fajl, za instrukcije o de-instaliranju ove skripte. otražite naslov \"How " "to uninstall WP Super Cache (Kako de-instalirati WP Super Cache)\"." #: wp-cache.php:1011 msgid "" "Need help? Check the Super Cache readme file. It " "includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already " "have been answered." msgstr "" "Treba vam pomoć? Pogledajte Super Cache readme fajl. On " "uključuje instalacionu dokumentaciju, često postavljana pitanja (FAQ) i " "savete za otklanjanje problema. Takođe je dostupan i forum " "za podršku. Na vaše pitanje je možda već odgovoreno." #: wp-cache.php:1014 wp-cache.php:1061 msgid "Update Status" msgstr "Ažurirati status" #: wp-cache.php:1021 msgid "Accepted Filenames & Rejected URIs" msgstr "Prihvaćena imena fajlova i odbačeni URI-ji" #: wp-cache.php:1046 msgid "Caching On" msgstr "Keširanje uključeno" #: wp-cache.php:1047 msgid "Caching Off" msgstr "Keširanje isključeno" #: wp-cache.php:1048 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "" "Napomena: uključuje PHP keširanje, ponovnu izgradnju keša i podršku za " "mobilne uređaje" #: wp-cache.php:1058 msgid "" "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. " "Cached files will be served using those rules. If your site is working ok " "please ignore this message or you can edit the .htaccess file in the root of " "your install and remove the SuperCache rules." msgstr "" "Obratite pažnju: Uključeno je PHP keširanje, ali su pronađena Supercache " "mod_rewrite pravila za ponovni upis. Keširani fajlovi će biti servirani " "koristeći ta pravila. Ako vaš sajt dobro funkcioniše, molim vas, ignorišite " "ovu poruku, ili možete urediti .htaccess fajl u osnovnom direktorijumu vaše " "instalacije i ukloniti SuperCache pravila." #: wp-cache.php:1063 msgid "Cache Tester" msgstr "Proverivač keša" #: wp-cache.php:1064 msgid "Test your cached website by clicking the test button below." msgstr "Proverite svoj keširani web sajt, klikom na donje dugme za proveru." #: wp-cache.php:1070 msgid "Fetching %s to prime cache: " msgstr "Preuzimanje %s u primarni keš:" #: wp-cache.php:1072 wp-cache.php:1081 wp-cache.php:1093 msgid "OK" msgstr "U redu" #: wp-cache.php:1075 msgid "Fetching first copy of %s: " msgstr "Preuzimanje prve kopije %s:" #: wp-cache.php:1084 wp-cache.php:1095 msgid "FAILED" msgstr "NIJE USPELO" #: wp-cache.php:1087 msgid "Fetching second copy of %s: " msgstr "Preuzimanje druge kopije %s:" #: wp-cache.php:1099 msgid "One or more page requests failed:" msgstr "Jedan ili više zahteva za stranu nije uspelo:" #: wp-cache.php:1118 wp-cache.php:1119 msgid "Page %d: %d (%s)" msgstr "Strana %d: %d (%s)" #: wp-cache.php:1125 msgid "Page 1: %s" msgstr "Strana 1: %s" #: wp-cache.php:1126 msgid "Page 2: %s" msgstr "Strana 2: %s" #: wp-cache.php:1127 msgid "The timestamps on both pages match!" msgstr "Vremenske oznake (timestamps) na obe strane se podudaraju!" #: wp-cache.php:1129 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "" "Strane se ne podudaraju! Vremenske oznake (timestamps) se razlikuju, ili " "nisu pronađene!" #: wp-cache.php:1130 msgid "Things you can do:" msgstr "Stvari koje možete uraditi:" #: wp-cache.php:1131 msgid "" "Load your homepage in a logged out browser, check the timestamp at the end " "of the html source. Load the page again and compare the timestamp. Caching " "is working if the timestamps match." msgstr "" "Učitajte vašu početnu stranu u odjavljen pregledač i proverite vremensku " "oznaku na kraju html izvornog koda. Učitajte istu stranu ponovo, i uporedite " "vremensku oznaku. Keširanje funkcioniše ako se vremenske oznake podudaraju." #: wp-cache.php:1132 msgid "" "Enable logging on the Debug page here. That should help you track down the " "problem." msgstr "" "Omogućiti prijavu na strani za otklanjanje programskih grešaka (Debugging " "page), ovde. To bi trebalo da vam pomogne da pronađete problem." #: wp-cache.php:1133 msgid "" "You should check Page 1 and Page 2 above for errors. Your local server " "configuration may not allow your website to access itself." msgstr "" "Trebalo bi da proverite ima li grešaka na strani 1 i strani 2, gore. " "Konfiguracija vašeg lokalnog servera možda ne dozvoljava vašem web sajtu da " "pristupa sam sebi." #: wp-cache.php:1141 msgid "Send non-secure (non https) request for homepage" msgstr "Slati neobezbeđene (koji nisu https) zahteve za početnu stranu" #: wp-cache.php:1142 msgid "Test Cache" msgstr "Proveriti keš" #: wp-cache.php:1146 msgid "Delete Cached Pages" msgstr "Obrisati keširane strane" #: wp-cache.php:1147 msgid "" "Cached pages are stored on your server as html and PHP files. If you need to " "delete them use the button below." msgstr "" "Keširane strane se čuvaju na vašem serveru, kao html i PHP fajlovi. Ako " "morate da ih obrišete, upotrebite donje dugme." #: wp-cache.php:1150 wp-cache.php:2416 wp-cache.php:2435 wp-cache.php:2606 #: wp-cache.php:3141 msgid "Delete Cache" msgstr "Obrisati keš" #: wp-cache.php:1157 wp-cache.php:2422 msgid "Delete Cache On All Blogs" msgstr "Obrisati keš na svim blogovima" #: wp-cache.php:1162 msgid "Recommended Links and Plugins" msgstr "Preporučeni linkovi i dodaci" #: wp-cache.php:1163 msgid "" "Caching is only one part of making a website faster. Here are some other " "plugins that will help:" msgstr "" "Keširanje je samo jedan deo ubrzavanja web sajta. Evo i nekih drugih " "dodataka koji će pomoći:" #: wp-cache.php:1164 msgid "" "WPSCMin, a Supercache plugin that minifies cached pages " "by removing whitespaces and extra characters " msgstr "" "WPSCMin, Supercache dodatak koji minimizira keširane " "strane, uklanjajući prazan prostor i višak karaktera" #: wp-cache.php:1165 msgid "" "Yahoo! Yslow is an extension for the Firefox add-on " "Firebug. It analyzes web pages and suggests ways to improve their " "performance based on a set of rules for high performance web pages. Also try " "the performance tools online at GTMetrix." msgstr "" "Yahoo! Yslow je proširenje za Firefox nadgradnju, " "Firebug. Ono analizira web strane i predlaže načine za unapređivanje " "njihovih performansi, prema pravilima za web strane visokih performansi. " "Takođe probajte onlajn alate za performanse, na GTMetrix." #: wp-cache.php:1166 msgid "" "Use Google Libraries allows you to load some commonly " "used Javascript libraries from Google webservers. Ironically it may reduce " "your Yslow score." msgstr "" "Use Google Libraries vam omogućava da učitate neke često " "korišćene Javascript biblioteke sa Google web servera. Ironija je što to " "može umanjiti vaš Yslow rezultat." #: wp-cache.php:1168 msgid "" "Advanced users only: Speed up your site with " "Caching and cache-control explains how to make your site more cacheable " "with .htaccess rules." msgstr "" "Samo za napredne korisnike: Speed up your " "site with Caching and cache-control (Ubrzajte vaš sajt pomoću keširanja i " "kontrole keša) objašnjava kako da vaš sajt učinite pogodnijim za " "keširanje, pomoću .htaccess pravila." #: wp-cache.php:1169 msgid "" "Advanced users only: Install an object cache. Choose from " "Memcached, XCache, eAcccelerator and others." msgstr "" "Samo za napredne korisnike: Instalirajte neki objektni keš. " "Odaberite između Memcached, XCache, eAcccelerator i drugih." #: wp-cache.php:1170 msgid "" "Cron View is a useful plugin to use when trying to debug " "garbage collection and preload problems." msgstr "" "Cron View je koristan dodatak, za korišćenje onda kada " "pokušavate da otklonite programske greške koje prave probleme sa uklanjanjem " "smeća i učitavanjem unapred." #: wp-cache.php:1181 msgid "Make WordPress Faster" msgstr "Učinite WordPress bržim" #: wp-cache.php:1182 msgid "" "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s je održavan i razvijen od strane %2$s, uz doprinos mnogih drugih." #: wp-cache.php:1183 msgid "He blogs at %1$s and posts photos at %2$s." msgstr "On bloguje na %1$s i objavljuje fotografije na %2$s." #: wp-cache.php:1184 msgid "Please say hi to him on %s too!" msgstr "Molim vas, pozdravite i njega, na %s!" #: wp-cache.php:1185 msgid "Need Help?" msgstr "Treba vam pomoć?" #: wp-cache.php:1187 msgid "" "Use the debug system in the Debug tab above. It will tell you what the " "plugin is doing." msgstr "" "Koristite sistem za otklanjanje grešaka u gornjoj kartici Otklanjanje " "grešaka (Debug). On će vam reći šta dodatak radi." #: wp-cache.php:1188 msgid "Installation Help" msgstr "Pomoć oko instalacije" #: wp-cache.php:1189 msgid "Frequently Asked Questions" msgstr "Često postavljana pitanja (FAQ)" #: wp-cache.php:1190 msgid "Support Forum" msgstr "forum za podršku" #: wp-cache.php:1191 msgid "Development Version" msgstr "razvojna verzija" #: wp-cache.php:1193 msgid "Rate This Plugin!" msgstr "Ocenite ovaj dodatak!" #: wp-cache.php:1194 msgid "" "Please rate this plugin and tell me if it works for you " "or not. It really helps development." msgstr "" "Molim vas, ocenite ovaj dodatak i recite mi da li, u " "vašem slučaju, funkcioniše, ili ne. Ovo stvarno pomaže razvoju." #: wp-cache.php:1203 msgid "Cached pages since %1$s : %2$s" msgstr "Keširano strana, od %1$s : %2$s" #: wp-cache.php:1204 msgid "Newest Cached Pages:" msgstr "Najnovije keširane strane:" #: wp-cache.php:1208 msgid "Cached %s seconds ago" msgstr "Keširano pre %s sekundi" #: wp-cache.php:1211 msgid "(may not always be accurate on busy sites)" msgstr "(može biti neprecizno kod opterećenih sajtova)" #: wp-cache.php:1227 msgid "" "Cache plugins are PHP scripts that live in a plugins folder inside the wp-" "super-cache folder. They are loaded when Supercache loads, much sooner than " "regular WordPress plugins." msgstr "" "Keš dodaci su PHP skripte koje se nalaze u folderu sa dodacima (plugins), " "unutar wp-super-cache foldera. One se učitavaju kada se učitava Supercache, " "mnogo pre nego obični WordPress dodaci." #: wp-cache.php:1228 msgid "" "This is strictly an advanced feature only and knowledge of both PHP and " "WordPress actions is required to create them." msgstr "" "Ovo je, striktno, samo jedno napredno svojstvo, i potrebno je poznavanje i " "PHP i WordPress akcija, da bi se ona kreirala." #: wp-cache.php:1229 msgid "" "Warning! Due to the way WordPress upgrades plugins the " "plugins you upload to wp-super-cache/plugins/ will be deleted when you " "upgrade WP Super Cache. You can avoid this by loading the plugins from " "elsewhere. Set $wp_cache_plugins_dir to the new location in " "wp-config.php and WP Super Cache will look there instead.
    More info " "available in the developer documentation." msgstr "" "Upozorenje! Zbog načina na koji WordPress unapređuje " "dodatke, dodaci koje prenesete u wp-super-cache/plugins/ će biti obrisani " "kada unapredite WP Super Cache. Ovo možete izbeći učitavanjem dodataka sa " "neke druge lokacije. U fajlu wp-config.php podesite " "$wp_cache_plugins_dir na novu lokaciju, i WP Super Cache će tražiti " "tu, umesto na staroj lokaciji.
    Više informacija je dostupno u dokumentaciji za " "programere." #: wp-cache.php:1239 msgid "Available Plugins" msgstr "Raspoloživi dodaci" #: wp-cache.php:1256 msgid "Easy" msgstr "Jednostavno" #: wp-cache.php:1256 msgid "CDN" msgstr "CDN" #: wp-cache.php:1256 msgid "Contents" msgstr "Sadržaji" #: wp-cache.php:1256 msgid "Preload" msgstr "Učitavanje unapred" #: wp-cache.php:1256 msgid "Plugins" msgstr "Dodaci" #: wp-cache.php:1256 msgid "Debug" msgstr "Otklanjanje programskih grešaka" #: wp-cache.php:1291 msgid "" "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "" "Obratite pažnju: Provere WP Super Cache mod_rewrite pravila su iksljučene, " "osim ako vam glavni sajt radi na ovoj mreži." #: wp-cache.php:1300 msgid "Mod Rewrite Rules" msgstr "Mod Rewrite pravila" #: wp-cache.php:1306 msgid "WordPress MU Detected" msgstr "Pronađen je WordPress MU" #: wp-cache.php:1306 msgid "" "Unfortunately the rewrite rules cannot be updated automatically when running " "WordPress MU. Please open your .htaccess and add the following mod_rewrite " "rules above any other rules in that file." msgstr "" "Na žalost, pravila za ponovni upis ne mogu da se ažuriraju automatski, kada " "se koristi WordPress MU. Molim vas, otvorite .htaccess i dodajte sledeća " "mod_rewrite pravila, iznad svih drugih pravila u tom fajlu." #: wp-cache.php:1308 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite pravila ne mogu da se ažuriraju!" #: wp-cache.php:1309 msgid "" "You must have BEGIN and END markers in %s." "htaccess for the auto update to work. They look like this and surround the " "main WordPress mod_rewrite rules:" msgstr "" "Da bi automatsko ažuriranje funkcionisalo, morate imati BEGIN i END markere u %s.htaccess fajlu. Oni izgledaju " "ovako, i okružuju glavna WordPress mod_rewrite pravila:" #: wp-cache.php:1311 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Kada ažurirate vaš .htaccess fajl, osvežite ovu stranu." #: wp-cache.php:1315 msgid "Thank you for upgrading." msgstr "Hvala vam za unapređivanje." #: wp-cache.php:1315 msgid "" "The mod_rewrite rules changed since you last installed this plugin. " "Unfortunately you must remove the old supercache rules before the new ones " "are updated. Refresh this page when you have edited your .htaccess file. If " "you wish to manually upgrade, change the following line: %1$s so it looks " "like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" " "and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change " "but it’s backwards compatible with older versions if you’re " "brave enough to use them." msgstr "" "Mod_rewrite pravila su se promenila od kada ste poslednji put instalirali " "ovaj dodatak. Na žalost, morate ukloniti stara superkeš pravila pre nego se " "nova ažuriraju. Kada završite uređivanje vašeg .htaccess fajla, osvežite ovu " "stranu. Ako želite da uradite manuelno unapređivanje, izmenite sledeću " "liniju: %1$s, da izgleda ovako: %2$s Jedine izmene su to što \"HTTP_COOKIE\" " "postaje \"HTTP:Cookie\" i \"wordpressuser\" postaje \"wordpress\". Ovo je " "WordPress 2.5 izmena, ali ona je komaptibilna unazad sa starijim verzijama, " "ako ste dovoljno hrabri da ih koristite." #: wp-cache.php:1319 msgid "Trailing slash check required." msgstr "Potrebna je provera prateće kose crte." #: wp-cache.php:1319 msgid "" "It looks like your blog has URLs that end with a \"/\". Unfortunately since " "you installed this plugin a duplicate content bug has been found where URLs " "not ending in a \"/\" end serve the same content as those with the \"/\" and " "do not redirect to the proper URL. To fix, you must edit your .htaccess file " "and add these two rules to the two groups of Super Cache rules:" msgstr "" "Izgleda da vaš blog ima URL-ove koji završavaju sa \"/\". Na žalost, pošto " "ste instalirali ovaj dodatak, programska greška sa dupliranim sadržajem se " "pojavljuje tamo gde URL-ovi ne završavaju sa \"/\", i servira se isti " "sadržaj kao za one sa \"/\", a ne vrši se usmeravanje na odgovarajući URL. " "Da popravite ovo, morate urediti vaš .htaccess fajl, i dodati ova pravila " "dvema grupama Super Cache pravila:" #: wp-cache.php:1321 msgid "" "You can see where the rules go and examine the complete rules by clicking " "the \"View mod_rewrite rules\" link below." msgstr "" "Možete videti gde pravila idu, i ispitati kompletna pravila, klikom na donji " "link \"Pregledati mod_rewrite pravila (View mod_rewrite rules)\"." #: wp-cache.php:1335 msgid "Mod Rewrite rules updated!" msgstr "Mod Rewrite pravila su ažurirana!" #: wp-cache.php:1336 msgid "" "%s.htaccess has been updated with the necessary mod_rewrite rules. Please " "verify they are correct. They should look like this:" msgstr "" "%s.htaccess je dopunjen sa neophodnim mod_rewrite pravilima. Molim vas, " "potvrdite da su ona ispravna. Trebalo bi da ovako izgledaju:" #: wp-cache.php:1338 msgid "Mod Rewrite rules must be updated!" msgstr "Mod Rewrite pravila moraju da budu ažurirana!" #: wp-cache.php:1339 msgid "" "Your %s.htaccess is not writable by the webserver and must be updated with " "the necessary mod_rewrite rules. The new rules go above the regular " "WordPress rules as shown in the code below:" msgstr "" "U vaš %s.htaccess fajl nije omogućen upis podataka od strane web servera, a " "on se mora ažurirati sa neophodnim mod_rewrite pravilima. Nova pravila " "dolaze iznad uobičajenih WordPress pravila, kao što je prikazano u donjem " "kodu:" #: wp-cache.php:1344 msgid "" "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have " "upgraded the plugin make sure these rules match." msgstr "" "U vašem %s.htaccess fajlu su pronađena WP Super Cache mod rewrite pravila." "
    Kliknite na sledeći link da vidite linije koje su dodate u taj fajl. " "Ako ste unapredili dodatak, postarajte se da se ova pravila poklapaju." #: wp-cache.php:1347 msgid "" "A difference between the rules in your .htaccess file and the plugin rewrite " "rules has been found. This could be simple whitespace differences but you " "should compare the rules in the file with those below as soon as possible. " "Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "" "Pronađena je razlika između pravila u vašem .htaccess fajlu i pravila " "dodatka, za ponovni upis. Ovo može biti jednostavno razlika u praznom " "prostoru, ali bi što pre trebalo da uporedite pravila u fajlu sa ovim " "donjim. Da ažurirate pravila, kliknite na dugme ’Ažurirati Mod_Rewrite " "pravila (Update Mod_Rewrite Rules)’." #: wp-cache.php:1349 msgid "View Mod_Rewrite Rules" msgstr "Pregledati Mod_Rewrite pravila" #: wp-cache.php:1355 wp-cache.php:2722 msgid "Rules must be added to %s too:" msgstr "Pravila se takođe moraju dodati u %s:" #: wp-cache.php:1362 msgid "Gzip encoding rules in %s.htaccess created." msgstr "U %s.htaccess fajlu su kreirana pravila za Gzip kodiranje." #: wp-cache.php:1369 msgid "Fix Configuration" msgstr "Popraviti konfiguraciju" #: wp-cache.php:1372 msgid "Restore Default Configuration" msgstr "Vratiti podrazumevanu konfiguraciju" #: wp-cache.php:1380 msgid "" "Comment moderation is enabled. Your comment may take some time to appear." msgstr "" "Uključena je moderacija komentara. Vašem komentaru može biti potrebno " "određeno vreme da se pojavi." #: wp-cache.php:1405 msgid "Lock Down:" msgstr "Zaključati:" #: wp-cache.php:1406 msgid "" "Prepare your server for an expected spike in traffic by enabling the lock " "down. When this is enabled, new comments on a post will not refresh the " "cached static files." msgstr "" "Pripremite vaš server za neočekivani saobraćajni špic, omogućivši " "zaključavanje. Kada je ono uključeno, novi komentari na objave neće " "osvežavati keširane statičke fajlove." #: wp-cache.php:1407 msgid "" "Developers: Make your plugin lock down compatible by checking the " "\"WPLOCKDOWN\" constant. The following code will make sure your plugin " "respects the WPLOCKDOWN setting." msgstr "" "Programeri: Učinite vaš dodatak kompatibilnim sa zaključavanjem, čekiravši " "\"WPLOCKDOWN\" konstantu. Sledeći kod će se postarati da vaš dodatak poštuje " "WPLOCKDOWN podešenje." #: wp-cache.php:1409 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "" "Žao mi je. Moj blog je zaključan. Ispravke/dopune će se pojaviti uskoro" #: wp-cache.php:1413 msgid "" "WordPress is locked down. Super Cache static files will not be deleted when " "new comments are made." msgstr "" "WordPress je zaključan. Super Cache statički fajlovi se neće brisati kada se " "postave novi komentari." #: wp-cache.php:1415 msgid "" "WordPress is not locked down. New comments will refresh Super Cache static " "files as normal." msgstr "" "WordPress nije zaključan. Novi komentari će osvežavati Super Cache statičke " "fajlove, kao i obično." #: wp-cache.php:1421 msgid "Lock Down" msgstr "Zaključati" #: wp-cache.php:1429 msgid "Directly Cached Files" msgstr "Direktno keširani fajlovi" #: wp-cache.php:1487 msgid "%s removed!" msgstr "%s uklonjeno!" #: wp-cache.php:1495 msgid "" "You must make %s writable to enable this feature. As this is a security risk " "please make it readonly after your page is generated." msgstr "" "Morate omogućiti upis podataka u %s, da biste omogućili ovo svojstvo. Pošto " "je to sigurnosni rizik, molim vas da ponovo onemogućite upis podataka u " "fajl, nakon što se vaša strana generiše." #: wp-cache.php:1500 msgid "" "%s is writable. Please make it readonly after your page is generated as this " "is a security risk." msgstr "" "U %s je moguć upis podataka. Molim vas, onemogućite upis podataka u ovaj " "fajl, nakon što se generiše vaša strana, jer je to sigurnosni rizik." #: wp-cache.php:1515 msgid "Existing direct page" msgstr "Postojeća direktna strana" #: wp-cache.php:1515 msgid "Delete cached file" msgstr "Obrisati keširani fajl" #: wp-cache.php:1520 msgid "Add direct page:" msgstr "Dodati direktnu stranu:" #: wp-cache.php:1522 msgid "" "Directly cached files are files created directly off %s where your blog " "lives. This feature is only useful if you are expecting a major Digg or " "Slashdot level of traffic to one post or page." msgstr "" "Direktno keširani fajlovi se kreiraju direktno iz %s, gde se nalazi vaš " "blog. Ovo svojstvo je korisno samo ako očekujete značajan nivo Digg ili " "Slashdot saobraćaja ka jednoj objavi, ili strani." #: wp-cache.php:1524 msgid "" "For example: to cache %1$sabout/, you would enter %1$sabout/ or /" "about/. The cached file will be generated the next time an anonymous user " "visits that page." msgstr "" "Na primer: da keširate %1$sabout/, unećete %1$sabout/ ili /about/. " "Keširani fajl će se generisati sledeći put kada anonimni posetilac poseti tu " "stranu." #: wp-cache.php:1525 msgid "" "Make the textbox blank to remove it from the list of direct pages and delete " "the cached file." msgstr "" "Ispraznite tekstualno polje, da ga uklonite sa liste direktnih strana, i " "obrišete keširani fajl." #: wp-cache.php:1530 msgid "Update Direct Pages" msgstr "Ažurirati direktne strane" #: wp-cache.php:1558 msgctxt "timezone date format" msgid "Y-m-d G:i:s" msgstr "Y-m-d (G-m-d) G:i:s" #: wp-cache.php:1620 msgid "Expiry Time & Garbage Collection" msgstr "Vreme isteka i sakupljanje smeća" #: wp-cache.php:1622 msgid "" "UTC time is %s" msgstr "" "UTC (usklađeno univerzalno vreme)" " vreme je %s" #: wp-cache.php:1625 msgid "Local time is %1$s" msgstr "Lokalno vreme je %1$s" #: wp-cache.php:1629 msgid "Next scheduled garbage collection will be at %s UTC" msgstr "Sledeće zakazano sakupljanje smeća će biti u %s UTC" #: wp-cache.php:1633 msgid "" "Warning! PRELOAD MODE activated. Supercache files will not " "be deleted regardless of age." msgstr "" "Upozorenje! PRELOAD MODE (mod za učitavanje unapred) je " "aktiviran. Superkeš fajlovi se neće brisati, nevezano za starost." #: wp-cache.php:1650 msgid "Cache Timeout" msgstr "Vreme isteka keša" #: wp-cache.php:1651 wp-cache.php:1654 msgid "seconds" msgstr "sekundi" #: wp-cache.php:1652 msgid "" "How long should cached pages remain fresh? Set to 0 to disable garbage " "collection. A good starting point is 3600 seconds." msgstr "" "Koliko dugo keširane strane treba da ostanu sveže? Da isključite sakupljanje " "smeća, postavite vrednost 0. Dobra polazna tačka je 3600 sekundi." #: wp-cache.php:1653 msgid "Scheduler" msgstr "Planer" #: wp-cache.php:1653 msgid "Timer:" msgstr "Tajmer:" #: wp-cache.php:1654 msgid "Check for stale cached files every interval seconds." msgstr "" "Tražiti keširane fajlove koji se ne koriste, svakih interval " "sekundi." #: wp-cache.php:1655 msgid "Clock:" msgstr "Sat:" #: wp-cache.php:1656 msgid "HH:MM" msgstr "HH:MM" #: wp-cache.php:1656 msgid "" "Check for stale cached files at this time (UTC) or starting " "at this time every interval below." msgstr "" "Tražiti keširane fajlove koji se ne koriste u ovo vreme (UTC), ili, počevši od ovog vremena, svakih interval nadalje." #: wp-cache.php:1658 msgid "Interval:" msgstr "Interval:" #: wp-cache.php:1664 msgid "Notification Emails" msgstr "E-mailovi sa obaveštenjima" #: wp-cache.php:1665 msgid "Email me when the garbage collection runs." msgstr "Obavestiti me e-mailom kada se pokrene sakupljanje smeća." #: wp-cache.php:1667 msgid "Garbage Collection" msgstr "Sakupljanje smeća" #: wp-cache.php:1668 msgid "" "Garbage collection is the simple act of throwing out your garbage. " "For this plugin that would be old or stale cached files that may be " "out of date. New cached files are described as fresh." msgstr "" "Sakupljanje smeća je jednostavno čin izbacivanja vašeg smeća. Za " "ovaj dodatak, to bi bili stari, ili nekorišćeni keširani fajlovi " "koji bi mogli biti zastareli. Novi keširani fajlovi se nazivaju svežim." #: wp-cache.php:1669 msgid "" "Cached files are fresh for a limited length of time. You can set that time " "in the Cache Timeout text box on this page." msgstr "" "Keširani fajlovi ostaju sveži ograničeno vreme. To vreme možete podesiti u " "tekstualnom polju Vreme isteka keša (Cache Timeout), na ovoj strani." #: wp-cache.php:1670 msgid "" "Stale cached files are not removed as soon as they become stale. They have " "to be removed by the garbage collecter. That is why you have to tell the " "plugin when the garbage collector should run." msgstr "" "Keširani fajlovi koji se ne koriste, ne uklanjaju se čim postanu \"ustajali" "\". Njih mora da ukloni sakupljač smeća. Zato morate reći dodatku kada " "sakupljač smeća treba da se pokrene." #: wp-cache.php:1671 msgid "" "Use the Timer or Clock schedulers to define when the " "garbage collector should run." msgstr "" "Koristite planere Tajmer (Timer) ili Sat (Clock), da " "definišete kada sakupljač smeća treba da se pokrene." #: wp-cache.php:1672 msgid "" "The Timer scheduler tells the plugin to run the garbage collector " "at regular intervals. When one garbage collection is done, the next run is " "scheduled." msgstr "" "Tajmer (Timer) planer govori dodatku da pokreće sakupljač smeća u " "pravilnim intervalima. Kada jedan sakupljač smeća završi sa radom, zakazuje " "se sledeće pokretanje." #: wp-cache.php:1673 msgid "" "Or, the Clock scheduler allows the garbage collection to run at " "specific times. If set to run hourly or twicedaily the garbage collector " "will be first scheduled for the time you enter here. It will then run again " "at the indicated interval. If set to run daily it will run once a day at the " "time specified." msgstr "" "Ili, Sat (Clock) planer, koji omogućava da se sakupljač smeća " "pokreće u određeno vreme. Ako je podešen da radi na svaki sat, ili dva puta " "na dan, pokretanje sakupljača smeća će prvo biti zakazano u vreme koje " "unesete ovde. Nakon toga će biti pokretan u navedenim intervalima. Ako je " "podešen da se pokreće jednom dnevno, on će se pokretati jednom dnevno - u " "navedeno vreme." #: wp-cache.php:1675 msgid "" "There are no best garbage collection settings but here are a few scenarios. " "Garbage collection is separate to other actions that clear our cached files " "like leaving a comment or publishing a post." msgstr "" "Ne postoje najbolja podešenja za sakupljanje smeća, ali evo nekoliko " "scenarija. Sakupljanje smeća je odvojeno od drugih akcija koje brišu " "keširane fajlove, kao što je ostavljanje komentara, ili objavljivanje objave." #: wp-cache.php:1677 msgid "" "Sites that want to serve lots of newly generated data should set the " "Cache Timeout to 60 and use the Timer scheduler set to 90 " "seconds." msgstr "" "Sajtovi koji žele da pruže dosta novo generisanih podataka, treba da podese " "Vreme isteka keša (Cache Timeout) na 60, i da koriste Tajmer " "(Timer), podešen na 90 sekundi." #: wp-cache.php:1678 msgid "" "Sites with widgets and rss feeds in their sidebar should probably use a " "timeout of 3600 seconds and set the timer to 600 seconds. Stale files will " "be caught within 10 minutes of going stale." msgstr "" "Sajtovi sa vidžetima i sa rss tokovima u svojoj bočnoj traci, verovatno " "treba da koriste vreme isteka od 3600 sekundi, i da podese tajmer na 600 " "sekundi. Fajlovi koji se ne koriste će se uhvatiti u roku od 10 minuta, od " "kako postanu \"ustajali\"." #: wp-cache.php:1679 msgid "" "Sites with lots of static content, no widgets or rss feeds in their sidebar " "can use a timeout of 86400 seconds or even more and set the timer to " "something equally long." msgstr "" "Sajtovi sa dosta statičkog sadržaja, bez vidžeta i rss tokova u svojoj " "bočnoj traci, mogu da koriste vreme isteka od 86400 sekundi, pa čak i više, " "i da podese tajmer na neko podjednako dugo vreme." #: wp-cache.php:1680 msgid "" "Sites where an external data source updates at a particular time every day " "should set the timeout to 86400 seconds and use the Clock scheduler set " "appropriately." msgstr "" "Sajtovi čiji se neki spoljni izvor podataka ažurira svakog dana u isto " "vreme, treba da podese vreme isteka na 86400 sekundi, i da koriste Sat " "(Clock) planer u skladu sa tim." #: wp-cache.php:1682 msgid "" "Checking for and deleting expired files is expensive, but it’s " "expensive leaving them there too. On a very busy site you should set the " "expiry time to 600 seconds. Experiment with different values and " "visit this page to see how many expired files remain at different times " "during the day. If you are using legacy caching aim to have less than 500 " "cached files if possible. You can have many times more cached files when " "using mod_rewrite or PHP caching." msgstr "" "Traženje i brisanje isteklih fajlova je skupo, ali je takođe skupo " "ostavljati ih gde jesu. Na veoma posećenom sajtu, trebalo bi da podesite " "vreme isteka na 600 sekundi. Eksperimentišite sa različitim " "vrednostima i posećujte ovu stranu, da vidite koliko isteklih fajlova ostaje " "u različito vreme, tokom dana. Ako koristite staro keširanje (legacy " "caching), ciljajte na to da imate manje od 500 keširanih fajlova, ako je to " "moguće. Kada koristite mod_rewrite ili PHP keširanje, možete imati mnogo " "više keširanih fajlova." #: wp-cache.php:1683 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Da isključite sakupljanje smeća, podesite vreme isteka na 0 sekundi." #: wp-cache.php:1684 msgid "Change Expiration" msgstr "Izmeniti isticanje" #: wp-cache.php:1728 msgid "Rejected User Agents" msgstr "Odbačeni korisnički agenti" #: wp-cache.php:1729 msgid "" "Strings in the HTTP ’User Agent’ header that prevent WP-Cache " "from caching bot, spiders, and crawlers’ requests. Note that super " "cached files are still sent to these agents if they already exists." msgstr "" "Stringovi u HTTP ’User Agent’ zaglavlju, koji sprečavaju WP-" "Cache da kešira zahteve botova, tragača (spiders) i pretraživača (crawlers). " "Imajte na umu da se superkeširani fajlovi i dalje šalju ovim agentima, ako " "već postoje." #: wp-cache.php:1736 msgid "Save UA Strings" msgstr "Sačuvati UA stringove" #: wp-cache.php:1759 msgid "" "Do not cache the following page types. See the Conditional Tags documentation for a " "complete discussion on each type." msgstr "" "Ne keširati sledeće tipove strana. Pogledajte dokumentaciju o Uslovnim tagovima " "(Conditional Tags), za kompletnu diskusiju o svakom tipu." #: wp-cache.php:1762 msgid "Single Posts" msgstr "Pojedinačne objave" #: wp-cache.php:1763 msgid "Pages" msgstr "Strane" #: wp-cache.php:1764 msgid "Front Page" msgstr "Prva strana" #: wp-cache.php:1765 msgid "Home" msgstr "Početna strana" #: wp-cache.php:1766 msgid "Archives" msgstr "Arhive" #: wp-cache.php:1767 msgid "Tags" msgstr "Oznake (tags)" #: wp-cache.php:1768 msgid "Category" msgstr "Kategorija" #: wp-cache.php:1769 msgid "Feeds" msgstr "Izvori podataka (feeds)" #: wp-cache.php:1770 msgid "Search Pages" msgstr "Strane za pretragu" #: wp-cache.php:1771 msgid "Author Pages" msgstr "Strane o autorima" #: wp-cache.php:1773 wp-cache.php:1885 msgid "Save" msgstr "Sačuvati" #: wp-cache.php:1790 msgid "" "Add here strings (not a filename) that forces a page not to be cached. For " "example, if your URLs include year and you dont want to cache last year " "posts, it’s enough to specify the year, i.e. ’/2004/’. WP-" "Cache will search if that string is part of the URI and if so, it will not " "cache that page." msgstr "" "Ovde dodajte stringove (ne ime fajla), koji forsiraju da strana ne bude " "keširana. Na primer, ako vaši URL-ovi uključuju godinu, a ne želite da " "keširate prošlogodišnje objave, dovoljno je navesti godinu, npr. " "’/2004/’. WP-Cache će tražiti da li je taj string deo URI-ja, i " "ako jeste, neće keširati tu stranu." #: wp-cache.php:1796 msgid "Save Strings" msgstr "Sačuvati stringove" #: wp-cache.php:1812 msgid "" "Add here those filenames that can be cached, even if they match one of the " "rejected substring specified above." msgstr "" "Ovde dodajte imena fajlova koji mogu da se keširaju, čak i ako sadrže neki " "od gornjih stringova za odbacivanje." #: wp-cache.php:1818 msgid "Save Files" msgstr "Sačuvati fajlove" #: wp-cache.php:1859 msgid "Currently logging to: %s" msgstr "Trenutno se prijavljuje na: %s" #: wp-cache.php:1862 msgid "" "Fix problems with the plugin by debugging it here. It can log them to a file " "in your cache directory." msgstr "" "Rešava probleme sa dodatkom, otklanjajući ovde programske greške. Može " "napraviti dnevnički zapis o njima u vašem keš direktorijumu." #: wp-cache.php:1866 msgid "Debugging" msgstr "Otklanjanje programskih grešaka" #: wp-cache.php:1867 msgid "IP Address" msgstr "IP adrese" #: wp-cache.php:1867 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(zahtevi za logove samo sa ove IP adrese. Vaša IP adresa je %s)" #: wp-cache.php:1868 msgid "Cache Status Messages" msgstr "Poruke o statusu keša" #: wp-cache.php:1869 msgid "Display comments at the end of every page like this:" msgstr "Prikazivati komentare na kraju svake strane, ovako:" #: wp-cache.php:1875 msgid "" "In very rare cases two problems may arise on some blogs:
    1. The front " "page may start downloading as a zip file.
    2. The wrong page is " "occasionally cached as the front page if your blog uses a static front page " "and the permalink structure is /%category%/%postname%/.
    " msgstr "" "U veoma retkim slučajevima, na nekim blogovima se mogu pojaviti dva problema:" "
    1. Prva strana može da počne da se preuzima kao zip fajl.
    2. " "Povremeno se kao prva strana kešira pogrešna strana, ako vaš blog koristi " "statičnu prvu stranu, a permalink struktura teme je /%category%/%postname" "%/.
    " #: wp-cache.php:1876 msgid "" "I’m 99% certain that they aren’t bugs in WP Super Cache and they " "only happen in very rare cases but you can run a simple check once every 5 " "minutes to verify that your site is ok if you’re worried. You will be " "emailed if there is a problem." msgstr "" "99% sam siguran da to nisu programske greške u WP Super Cache-u, i do njih " "dolazi samo u veoma retkim slučajevima, ali možete pokrenuti jednostavnu " "proveru svakih 5 minuta, da potvrdite da je vaš sajt u redu, ako ste " "zabrinuti. Biće vam poslat e-mail ako bude problema." #: wp-cache.php:1878 msgid "Check front page every 5 minutes." msgstr "Proveravati prvu stranu svakih 5 minuta." #: wp-cache.php:1879 msgid "Front page text" msgstr "Tekst prve strane" #: wp-cache.php:1879 msgid "" "Text to search for on your front page. If this text is missing the cache " "will be cleared. Leave blank to disable." msgstr "" "Tekst za traženje na prvoj strani. Ako ovaj tekst nedostaje, keš će biti " "obrisa. Da isključite, ostavite prazno." #: wp-cache.php:1880 msgid "Clear cache on error." msgstr "Obrisati keš u slučaju greške." #: wp-cache.php:1881 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "" "Poslati e-amil administratoru bloga, kada se urade provere. (korisno za " "proveru)" #: wp-cache.php:1895 msgid "" "Error: GZIP compression is enabled, disable it if you want to enable wp-" "cache." msgstr "" "Greška: GZIP kompresija je uključena, isključite je ako hoćete da uključite " "wp-cache." #: wp-cache.php:1945 wp-cache.php:2086 wp-cache.php:2122 msgid "Warning" msgstr "Upozorenje" #: wp-cache.php:1945 msgid "" "GZIP compression is enabled in WordPress, wp-cache will be bypassed until " "you disable gzip compression." msgstr "" "GZIP kompresija je uključena u WordPress-u, wp-cache će biti zaobilažen dok " "ne isključite gzip kompresiju." #: wp-cache.php:2007 wp-cache.php:2012 wp-cache.php:2045 wp-cache.php:2050 #: wp-cache.php:2056 msgid "Error" msgstr "Greška" #: wp-cache.php:2007 msgid "" "Your cache directory (%1$s) did not exist and couldn’" "t be created by the web server. Check %1$s permissions." msgstr "" "Vaš keš direktorijum (%1$s) ne postoji, i nije mogao da " "bude kreiran od strane web servera. Proverite %1$-ove dozvole." #: wp-cache.php:2012 msgid "" "Your cache directory (%1$s) or %2$s need " "to be writable for this plugin to work. Double-check it." msgstr "" "Upis u vaš keš direktorijum (%1$s), ili %2$s, mora da bude omogućen da bi ovaj dodatak funkcionisao. Proverite ga " "dva puta." #: wp-cache.php:2045 msgid "" "Your WP-Cache config file (%s) is out of date and not " "writable by the Web server.Please delete it and refresh this page." msgstr "" "Vaš WP-Cache konfiguracioni fajl (%s) je star i web server " "ne može da vrši upis u njega. Molim vas, obrišite ga i osvežite ovu stranu." #: wp-cache.php:2050 msgid "" "Configuration file missing and %1$s directory (%2$s) is " "not writable by the Web server.Check its permissions." msgstr "" "Konfiguracioni fajl nedostaje, a u %1$-ov direktorijum (%2$s) nije moguć upis podataka od strane web servera. Proverite njegove " "dozvole." #: wp-cache.php:2056 msgid "" "Sample WP-Cache config file (%s) does not exist.Verify you " "installation." msgstr "" "WP-Cache konfiguracioni fajl - primer (%s) ne postoji. " "Proverite vašu instalaciju." #: wp-cache.php:2086 msgid "Could not update %s!     WPCACHEHOME must be set in config file." msgstr "" "%s nije mogao da se ažurira! WPCACHEHOME mora da se podesi u " "konfiguracionom fajlu." #: wp-cache.php:2122 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php ne postoji i ne može da se ažurira." #: wp-cache.php:2123 msgid "1. If it already exists please delete the file first." msgstr "1. Ako već postoji, molim vas da ga prvo obrišete." #: wp-cache.php:2124 msgid "" "2. Make %1$s writable using the chmod command through your ftp or server " "software. (chmod 777 %1$s) and refresh this page. This is only a " "temporary measure and you’ll have to make it read only afterwards " "again. (Change 777 to 755 in the previous command)" msgstr "" "2. Omogućite upis podataka u %s-e, koristeći naredbu chmod, preko vašeg ftp, " "ili serverskog softvera. (chmod 777 %1$s) i osvežite ovu stranu. " "Ovo je samo privremena mera, i moraćete posle da opet onemogućite upis u " "njega. (U prethodnoj naredbi promenite 777 u 755)" #: wp-cache.php:2125 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Osvežite ovu stranu da ažurirate %s/advanced-cache.php" #: wp-cache.php:2126 msgid "" "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "" "Ako to ne funkcioniše, proverite da li fajl %s/advanced-cache.php " "postoji:" #: wp-cache.php:2127 msgid "" "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change " "the text CACHEHOME to %2$s
  • 3. Save the file and " "copy it to %3$s and refresh this page.
    • " msgstr "" "
  • 1. Otvorite fajl %1$s$wp_cache_file u nekom uređivaču teksta.
  • 2. Izmenite tekst CACHEHOME u %2$s
  • 3. " "Sačuvajte fajl i kopirajte ga u %3$s, a zatim osvežite ovu stranu." #: wp-cache.php:2150 msgid "" "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by " "WordPress to load the code that serves cached pages. Unfortunately it is set " "to false. Please edit your wp-config.php and add or edit the following line " "above the final require_once command:

    define('WP_CACHE', " "true);

    " msgstr "" "

    WP_CACHE konstanta je podešena na vrednost false

    WP_CACHE " "konstantu WordPress koristi da učita kod koji servira keširane strane. Na " "žalost, ona je podešena na vrednost false. Molim vas, uredite vaš wp-config." "php fajl i dodajte ili uredite sledeće linije, iznad završne naredbe " "require_once:

    define('WP_CACHE', true);

    " #: wp-cache.php:2152 msgid "" "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "" "Greška: WP_CACHE nije uključen u vašem wp-config.php fajlu, i ne mogu da ga izmenim." #: wp-cache.php:2153 msgid "" "Edit %s and add the following line:
    define" "('WP_CACHE', true);
    Otherwise, WP-Cache will not be " "executed by WordPress core. " msgstr "" "Uredite %s i dodajte sledeću liniju:
    define" "('WP_CACHE', true);
    U suprotnom, WP-Cache se neće " "izvršiti od strane WordPress jezgra. " #: wp-cache.php:2157 msgid "" "

    WP_CACHE constant added to wp-config.php

    If you continue to see " "this warning message please see point 5 of the Troubleshooting Guide. The " "WP_CACHE line must be moved up." msgstr "" "

    WP_CACHE konstanta je dodata u wp-config.php

    Ako i dalje budete " "videli ovu poruku sa upozorenjem, molim vas, pogledajte tačku 5 Vodiča za " "otklanjanje problema (Troubleshooting Guide). WP_CACHE linija se mora " "pomeriti na gore." #: wp-cache.php:2185 msgid "Cache Contents" msgstr "Sadržaj keša" #: wp-cache.php:2188 msgid "Object cache in use. No cache listing available." msgstr "U upotrebi je objektni keš. Nije dostupan listing keša." #: wp-cache.php:2212 msgid "Deleting supercache file: %s
    " msgstr "Brisanje superkeš fajla: %s
    " #: wp-cache.php:2229 msgid "Deleting wp-cache file: %s
    " msgstr "Brisanje wp-cache fajla: %s
    " #: wp-cache.php:2294 msgid "" "Cache stats are not automatically generated. You must click the link below " "to regenerate the stats on this page." msgstr "" "Statistike keša se ne generišu automatski. Morate kliknuti na donji link da " "na ovoj strani generišete statistike." #: wp-cache.php:2295 msgid "Regenerate cache stats" msgstr "Ponovo generisati statistike keša" #: wp-cache.php:2297 msgid "Cache stats last generated: %s minutes ago." msgstr "Poslednje generisanje statistika keša: pre %s minuta." #: wp-cache.php:2303 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:2304 wp-cache.php:2319 msgid "%s Cached Pages" msgstr "%s keširanih strana" #: wp-cache.php:2305 wp-cache.php:2324 msgid "%s Expired Pages" msgstr "%s isteklih strana" #: wp-cache.php:2318 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:2328 msgid "Fresh WP-Cached Files" msgstr "Sveži WP-Cache fajlovi" #: wp-cache.php:2329 wp-cache.php:2345 wp-cache.php:2361 wp-cache.php:2377 msgid "URI" msgstr "URI" #: wp-cache.php:2329 wp-cache.php:2345 msgid "Key" msgstr "Ključ" #: wp-cache.php:2329 wp-cache.php:2345 wp-cache.php:2361 wp-cache.php:2377 msgid "Age" msgstr "Starost" #: wp-cache.php:2329 wp-cache.php:2345 wp-cache.php:2361 wp-cache.php:2377 msgid "Delete" msgstr "Obrisati" #: wp-cache.php:2344 msgid "Stale WP-Cached Files" msgstr "WP-keširani fajlovi koji se ne koriste" #: wp-cache.php:2360 msgid "Fresh Super Cached Files" msgstr "Sveži superkeširani fajlovi" #: wp-cache.php:2376 msgid "Stale Super Cached Files" msgstr "Superkeširani fajlovi koji se ne koriste" #: wp-cache.php:2392 msgid "Hide file list" msgstr "Sakriti listu fajlova" #: wp-cache.php:2394 msgid "Too many cached files, no listing possible." msgstr "Previše keširanih fajlova, nije moguć prikaz liste" #: wp-cache.php:2396 msgid "List all cached files" msgstr "Prikazati listu svih keširanih fajlova" #: wp-cache.php:2399 msgid "" "Expired files are files older than %s seconds. They are still used by the " "plugin and are deleted periodically." msgstr "" "Istekli fajlovi su stariji od %s sekundi. Oni se i dalje koriste od strane " "dodatka, i brišu se periodično." #: wp-cache.php:2410 msgid "Delete Expired" msgstr "Obrisati isteklo" #: wp-cache.php:2435 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Obrisati Super Cache keširane fajlove (otvara se u novom prozoru)" #: wp-cache.php:2582 msgid "%1$s is Stephen Fry proof thanks to caching by %2$s" msgstr "" "%1$s je Stephen Fry proveren (Stephen Fry proof), zahvaljujući keširanju od " "strane %2$s" #: wp-cache.php:2615 msgid "" "WP Super Cache must be configured. Go to the admin page " "to enable and configure the plugin." msgstr "" "WP Super Cache mora biti konfigurisan. Idite na stranu za " "administraciju, da uključite i konfigurišete ovaj dodatak." #: wp-cache.php:2621 msgid "Settings" msgstr "Podešavanja" #: wp-cache.php:2631 msgid "" "WP Super Cache is disabled. Please go to the plugin admin " "page to enable caching." msgstr "" "WP Super Cache je isključen. Molim vas, idite na stranu za " "administraciju dodataka, da omogućite keširanje." #: wp-cache.php:2634 msgid "" "Warning! WP Super Cache caching broken! The script advanced-cache.php could " "not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php " "and make sure the path to %2$swp-cache-phase1.php is correct." msgstr "" "Upozorenje! WP Super Cache keširanje je neispravno! Skriptin fajl advanced-" "cache.php nije mogao da učita wp-cache-phase1.php.

    Molim vas, " "uredite %1$s/advanced-cache.php fajl i postarajte se da putanja ka %2$swp-" "cache-phase1.php fajlu bude ispravna." #: wp-cache.php:2653 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Prva strana je gzip-ovana! Molim vas, obrišite keš!" #: wp-cache.php:2653 msgid "" "Please visit %s to clear the cache as the front page of your site is now " "downloading!" msgstr "" "Molim vas, posetite %s da obrišete keš, pošto se prva strana vašeg sajta " "sada preuzima." #: wp-cache.php:2656 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Prva strana je gzip-ovana! Keš je obrisan!" #: wp-cache.php:2656 msgid "" "The cache on your blog has been cleared because the front page of your site " "is now downloading. Please visit %s to verify the cache has been cleared." msgstr "" "Keš na vašem blogu je obrisan, pošto se prva strana vašeg sajta sada " "preuzima. Molim vas, posetite %s, da potvrdite da je keš obrisan." #: wp-cache.php:2663 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Prva strana nije ispravna! Molim vas, obrišite keš!" #: wp-cache.php:2663 msgid "" "Please visit %1$s to clear the cache as the front page of your site is not " "correct and missing the text, \"%2$s\"!" msgstr "" "Molim vas, posetite %1$s da obrišete keš, pošto prva strana vašeg sajta nije " "ispravna, i nedostaje joj tekst, \"%2$s\"!" #: wp-cache.php:2666 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Prva strana nije ispravna! Keš je obrisan!" #: wp-cache.php:2666 msgid "" "The cache on your blog has been cleared because the front page of your site " "is missing the text \"%2$s\". Please visit %1$s to verify the cache has been " "cleared." msgstr "" "Keš na vašem blogu je obrisan, pošto na prvoj strani vašeg sajta nedostaje " "tekst \"%2$s\". Molim vas, posetite %1$s, da potvrdite da je keš obrisan." #: wp-cache.php:2671 msgid "[%s] Front page check!" msgstr "[%s] Provera prve strane!" #: wp-cache.php:2671 msgid "" "WP Super Cache has checked the front page of your blog. Please visit %s if " "you would like to disable this." msgstr "" "WP Super Cache je proverio prvu stranu vašeg bloga. Molim vas, posetite %s, " "ako želite da ovo isključite." #: wp-cache.php:2714 msgid "Cannot update .htaccess" msgstr "Fajl .htaccess ne može da se ažurira" #: wp-cache.php:2714 msgid "" "The file %s.htaccess cannot be modified by the web server. " "Please correct this using the chmod command or your ftp client." msgstr "" "Fajl %s.htaccess nije mogao da bude izmenjen od strane web " "servera. Molim vas, ispravite ovo, koristeći naredbu chmod, ili vaš ftp " "klijent." #: wp-cache.php:2714 msgid "Refresh this page when the file permissions have been modified." msgstr "Osvežiti ovu stranu kada se dozvole fajla izmene." #: wp-cache.php:2714 msgid "" "Alternatively, you can edit your %s.htaccess file manually and " "add the following code (before any WordPress rules):" msgstr "" "Alternativno, možete manuelno urediti vaš fajl %s.htaccess, i " "dodati sledeći kod (pre bilo kakvih WordPress pravila):" #: wp-cache.php:2718 msgid "" "To serve static html files your server must have the correct mod_rewrite " "rules added to a file called %s.htaccess" msgstr "" "Da bi servirao statičke html fajlove, vaš server mora imati ispravna " "mod_rewrite pravila, dodata u fajl pod nazivom %s.htaccess" #: wp-cache.php:2719 msgid "You can edit the file yourself add the following rules." msgstr "Možete sami urediti fajl, dodajte sledeća pravila." #: wp-cache.php:2720 msgid " Make sure they appear before any existing WordPress rules. " msgstr "" "Postarajte se da se ona pojave pre bilo kakvih postojećih WordPress pravila." #: wp-cache.php:2728 msgid "Update Mod_Rewrite Rules" msgstr "Ažurirati Mod_Rewrite pravila" #: wp-cache.php:2891 msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Učitavanje keša unapred je počelo" #: wp-cache.php:2921 msgid "[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d" msgstr "[%1$s] Osvežavanje %2$s taksonomije od %3$d do %4$d" #: wp-cache.php:2967 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Osvežavanje objava od %2$d do %3$d" #: wp-cache.php:2988 msgid "[%1$s] Cache Preload Stopped" msgstr "[%1$s] Učitavanje keša unapred je zaustavljeno" #: wp-cache.php:2998 msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d objava je osveženo" #: wp-cache.php:2998 msgid "Refreshed the following posts:" msgstr "Osvežene su sledeće objave:" #: wp-cache.php:3008 msgid "Scheduling next preload refresh in %d minutes." msgstr "Sledeće osvežavanje učitavanja unapred se zakazuje za %d minuta" #: wp-cache.php:3019 msgid "[%s] Cache Preload Completed" msgstr "[%s] Učitavanje keša unapred je završeno" #: wp-cache.php:3019 msgid "Cleaning up old supercache files." msgstr "Brisanje starih superkeš fajlova." #: wp-cache.php:3062 msgid "[%s] Preload may have stalled." msgstr "[%s] Učitavanje unapred je možda zastalo." #: wp-cache.php:3062 msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Učitavanje unapred je ponovo započeto.\n" "%s" #: wp-cache.php:3105 msgid "Supercache Uninstall Problems" msgstr "Problemi sa de-instaliranjem Supercache-a" #: wp-cache.php:3105 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file " "first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" msgstr "" "Dragi korisniče,\n" "\n" "WP Super Cache je uklonjen sa vašeg bloga, ali mod_rewrite pravila\n" "u vašem .htaccess nisu.\n" "\n" "Molim vas, uredite sledeći fajl i uklonite kod\n" "između 'BEGIN WPSuperCache' i 'END WPSuperCache'. Molim vas, prvo napravite " "backup kopiju fajla!\n" "\n" "%s\n" "\n" "Sa poštovanjem,\n" "WP Super Cache dodatak\n" "http://wordpress.org/extend/plugins/wp-super-cache/" #: wp-cache.php:3142 msgid "Delete cache of the current page" msgstr "Obrisati keš aktuelne strane" languages/wp-super-cache-ro_RO.mo000066600000164052152133035240012722 0ustar009 8<9,vM` s~?3>rb"*7Z5C5y =bj^ \ r&!!?"#w$Z%`%&.&'&((:(n'*p*,,,,, ,3,-"- 1-,>-k-^.p{.+.//./^/ f/ r/+}//3// 00!%0G0!27>2v22I;3@33sK44%?5e5|5 55 5555553616777888u\9j9=:B::?:9;@;H;NN;; ;n;$.<S<Y<v<<<~<@==>> >><>g*??+?*?? @@ AbAA1B:C&D"/EkRFGGEGH*3H ^H hH sH }HbHH]I$aII IIIIIJ$J"JJ! K,KKL&LM<"Mb_MM|uNyNlO0oO!O-OkO\Q mQ xQQQTQQURmRpSUSSSSTTJ5TTd]UU`iV0V V W7WSIW?W<WX9XPX7eXjXY&YDYYcYY Y YY(YZ+Z,Z.Zf![ [/[0[[?x\8\\ \:]B][]q]H^ M^;X^^q^_1__x`aaQb<idGd#due eTf~f+ggggghNibi{i ii%i'ijjj4jbjklk9lBlQlYlbl|l*llbl[@m m7mrmMRnnYo/o qrr?ssRt$tetau v%vAv)^vvv*v/v.w3FwzwwwwwwwHby+yNy&z7ztIz zz@R{K{{{x|9}DL}\}7}L&~ s~LejGfu3JÂqhpمb,ɉ} %ōɍOX$oP  /Oo354j=Ñ ˑՑEޑ$N@ 'В>(7O`ǕX5,ȗ~\)ۘ #- 4AKQ87ny{&T,X " ޠ( UvGn Z+h:ϤB 2g<I{ ŨHϩ\u<BSY Hή  ! , 9~GƯj/M#}%ڰ̱16&M!t"/ܴ >aRy+ݷC M  ")\B"iº,* "._Q;]d7 >b ^pR "CZMz J1k/tBJYj-~2[45qkG>NMGOM^!( G h{zs;MJAA(:1l7! -4/<dzPWgv  ")o p}OM`CAG"61y" A%b-#31,>^G% "G>L(+3uTk$^&  9b!8j _#`%v6ip4Q*+0!;KgW@DI  )&r:$8H"=' {c*A2oZM~.5haC,1 E2U6[yS(lq4YP s9]0/'VBFN /X ,3t 5-w1}|xe\?O"#%Jmd)<zR7.7-n f Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php     does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.) (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) (support for multiple domains on multisite websites) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.No Adverts for Friends plugin is %s.Domain Mapping support plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting Moderation plugin is %sBad Behaviour not found. Please check your install.Bad Behaviour support is %s.Cache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Don’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLegacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching.Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.One or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Update Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: WP Super Cache Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-09-27 13:58+0000 PO-Revision-Date: 2011-06-13 18:44+0200 Last-Translator: Alexandr K. Language-Team: Michail Bogdanov MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Romanian X-Poedit-Country: MOLDOVA, REPUBLIC OF Asiguraţi-vă că ele apar înainte de orice reguli WordPress existent.%1$s să-i mulţumesc %2$s pentru munca lor%1$s este menţinut şi dezvoltat de %2$s, cu contribuţii de la multe altele.%s pagini cached%s pagini expirat%s este writable Vă rugăm să-l doar în citire după ce pagina este generat ca acesta este un risc de securitate.%s eliminat!%s.htaccess a fost actualizat cu normele necesare mod_rewrite. Va rugam a verifica dacă sunt corecte ar trebui să arate acest lucru:%s/advanced-cache.php nu există sau nu pot fi actualizate.(1 = mai puţin, 5 = mai mult, poate provoca de încărcare server severe.)(Experimental)(Numai cache moştenire a sprijinit, de compresie cu handicap şi necesită Bad Behavior în "%s/plugins/bad-behavior/")(Scoateţi textul "Comentariul dvs. este în aşteptarea moderaţie.", atunci când cineva lasă un comentariu moderat.)(Pot să nu fie întotdeauna exacte pe site-urile ocupat)(jurnal numai cereri de la această adresă IP. IP-ul tau este - %s)(Necesită friendsadverts.php prea) (suport pentru mai multe domenii pe site-uri multisite)1. În cazul în care există deja vă rugăm să ştergeţi primul fişier.2. Asiguraţi %1$s scriere utilizând comanda chmod prin ftp sau software de tip server şi. (Chmod 777 %1$s) reîmprospăta această pagină. Aceasta este doar o măsură temporară şi va trebui să-l citesc numai ulterior din nou. (Schimbaţi 777-755 în comenzii precedente) 3. Refresh această pagină pentru a actualiza %s/avansat-cache.php304 Not Modified browser caching. Indice când o pagină nu a fost modificat de la ultima solicitate.Sprijin pentru eroarea 304 este dezactivată în mod implicit (din cauza unei probleme de unele servicii).Nu Anunţuri pentru prietenii plug-in este %s.Domeniu Mapping suport plug-in este %s

    Parţial WP_CACHE adăugat la fişierul de configurare wp-config.php

    Dacă vedeţi în continuare acest mesaj, apoi verificaţi cu punctul 5 din FAQ (în limba engleză). Rând cu WP_CACHE ar trebui să fie plasat mai mare.

    WP_CACHE opţiune nu este activată

    Această opţiune trebuie să fie activat pentru a WordPress poate lucra corect cu fişierul cache. In acest moment este dezactivat. Pentru a activa aceasta, deschideţi fişierul wp-config.php şi adăugaţi următoarea linie:

    define('WP_CACHE', true);

  • 1. Deschideţi fişierul %1$s$wp_cache_file într-un editor de text.
  • 2. Schimbaţi linia CACHEHOME pe %2$s
  • 3. Salvaţi fişierul şi copiaţi %3$s, apoi reîmprospătaţi pagina.
    • Eroare: WP_CACHE Variabila nu fie activate în comun configuraţiile wp-config.php.Garbage Collection
    Ultima GC a fost %s minute în urmă
    Atenţie încercat! Puteţi să activaţi de compresie, dar zlib.output_compression este activată. Vedea în secţiunea Troubleshooting (#21) din fişierul readme.Un URL-ul personalizat sau structura Permalink este necesar pentru acest plug-in pentru a funcţiona corect. Vă rugăm să mergeţi la Permalinks pagina Opţiuni pentru a configura permalinks dumneavoastră.O diferenţă între normele în fişierul htaccess. Şi plugin-ul regulile de rescriere a fost găsit Acest lucru ar putea fi diferenţele de simplu, dar spaţiu. Ar trebui să comparaţi normele în dosarul cu cele de mai jos cât mai curând posibil. Faceţi clic pe ’Update normele Mod_Rewrite’, pentru a face acest lucru în mod automat.Un mod simplu de a face asta este de a schimba permisiunile utilizând comanda chmod temporar sau prin intermediul dvs. de client FTP. Asiguraţi-vă că la nivel global inscriptibile şi ar trebui să fie bine.Nume de fişiere acceptate & URI respinsAdauga pagina direct:Adăugaţi aici siruri de caractere (nu un nume de fisier) că forţele o pagină nu trebuie să fie în cache. De exemplu, dacă URL-urile includ an şi tu dont doriţi să cache posturi de anul trecut, este suficient să se precizeze an, adică ’/2011/’. WP-Cache va căuta în cazul în care şir este parte a URI şi, dacă acest lucru nu, se va cache acea pagină.Adăugaţi aici acele numele de fişiere care pot fi memorate în cache, chiar dacă acestea se potrivesc unul dintre respins subşir specificate mai sus.Adăugaţi regulile de tine liniile. Editare %s.htaccess şi pentru a găsi bloc de cod închisă de # BEGIN WPSuperCache şi # END WPSuperCache. Există două secţiuni, care arata foarte similar linie. Doar sub %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ adăugaţi aceste linii: (o fac de două ori, o dată pentru fiecare secţiune) AdvancedAgeAlternativ, puteţi edita %s.htaccess fişier manual şi adăugaţi următorul cod (înainte de orice reguli WordPress):ArhivelePlugin-uri disponibileAşteaptă moderarea plug-in este %sBad Comportamentul nu a fost găsită. Vă rugăm să verificaţi a vă instala.Sprijin Bad Behaviour este %s.Cache CuprinsCache TesterCache hit-uri la acest site pentru acces rapid.Cache plugin-uri sunt scripturi PHP care trăiesc într-un folder plugin-uri în interiorul folderul wp-super-cache. Ele sunt încărcate atunci când încarcă Supercache, mult mai devreme decât regulate WordPress plugin-uri.Cache reconstrui servesc un fişier supercache. Utilizatorilor anonimi în timp ce un fişier nou este generat.Cache statisticile nu sunt generate automat. Trebuie să faceţi clic pe link-ul de mai jos pentru a regenera statisticile de pe aceasta pagina.Cache statistici ultima generat: %s minute în urmă.Cache %s secunde în urmăPaginile stocate în cache de la %1$s : %2$sCachingCache OffCache OnStocarea trebuie să fie activată pentru a utiliza această funcţieCancel Cache preîncărcateNu se poate continua... rezolva problemele anterioare şi încercaţi din nou.Nu se poate actualiza. HtaccessCategorieSchimbarea de expirareCheck prima pagina la fiecare 5 minute.Verificarea şi ştergerea fişierelor expirat este scump, dar e scump lasandu-le acolo. Pe foarte ocupat un site care ar trebui să stabilească expirarea timp pentru 300 secunde. Experiment cu valori diferite şi să vizitaţi această pagină pentru a vedea modul în care a expirat mai multe fişiere rămân la diferite ori în timpul zilei. Dacă folosiţi caching scopul de moştenire să aibă mai puţin de 500 de fişiere cache, dacă este posibil. Puteţi avea fişiere de multe ori mai mult cache atunci când se utilizează mod_rewrite sau caching PHP.Curăţarea fişierele vechi supercache.Ştergeţi toate fişierele cache atunci când un post sau pagină se publică.Clear cache la eroare.Fişier de blocare grosier. Ai face, probabil, nu este necesar acest lucru, dar ar putea ajuta dacă serverul este underpowered Atenţie! Poate provoca server-ul dvs. pentru a bloca in cazuri foarte rare!Este activată moderarea comentariilor. Comentariul dvs. poate lua ceva timp să apară.Comprimare fişiere cache pentru a accelera de lucru.Compresia este dezactivată în mod implicit, deoarece unele gazdele au probleme cu fişiere comprimate. Pornirea-l pe şi în afara şterge memoria cache.Fişier de configurare schimbat, unele valori ar putea fi greşită Încărcaţi a doua pagină din nou. De la "Settings" meniu pentru a le reseta.Fişier de configurare lipsă şi %1$s dosar (%2$s) nu poate fi scris de server. Check Web permisiunile sale.În prezent, caching de la post %d la %d.În prezent, logare la:DebugDebuggingDeleteDelete CacheŞterge expiratŞterge Super Cache cache fişierele (se deschide într-o fereastră nouă)Şterge cache fileŞterge plugin mod_rewrite normele în %s.htaccess închise de către # BEGIN WPSuperCache şi # END WPSuperCache şi lăsaţi plugin-ul regenera le reîncărcaţi această pagină.Ştergerea supercache fişier: %s
    Ştergerea wp-cache fişier: %s
    Dezvoltatorii: Asiguraţi-vă plugin bloca compatibil prin verificarea "WPLOCKDOWN". Constanta urmatorul cod va asiguraţi-vă că plugin respectă setarea WPLOCKDOWN.Fişiere direct cacheFişiere direct din cache sunt fişiere create direct de pe %s în cazul în care locuieşte blog-ul dvs. Această caracteristică este. Util numai dacă se asteapta la o Digg majore sau Slashdot nivel de trafic pentru un post sau pagină.OffDisabledNu cache pagina de următoarele tipuri. Consultaţi Condiţionat Tag-uri documentaţia pentru o discuţie completă pentru fiecare tip.Domeniu Mapping plugin detectate Vă rugăm să mergeţi la pagina Supercache plugin-uri şi pentru a permite helper cartografiere domeniu plugin.Nu paginile în cache pentru utilizatorii cunoscuţi.EasyEditare codul %s şi adăugaţi următoarele:
    define('WP_CACHE', true);
    . În caz contrar, WP-Cachenu va porni.EmailEmail blog-ul admin, atunci când controalele sunt efectuate. (util pentru testarea)ActivatEnabledEroareEroare: compresie gzip este activat, dezactivati-l dacă doriţi să activaţi wp-cache.Directe existente paginaExpirare timp:Expirate fişiere sunt fişierele mai vechi %s secunde. Ele sunt încă utilizate de către plugin-ul şi se elimină periodic.Expirat pagina & Clar de molozFeedsSe preiau %s la cache prim:Exemplar preiau primul %s:Copie preiau doilea lui %s:Fix de configurareFix probleme cu plugin-ul de depanare-l aici poate trimite e-mailuri sau debug log-le într-un fişier în directorul cache-ul dumneavoastră.Pentru cele mai bune performanţe ar trebui să permită "Mobile sprijin dispozitiv de" sau şterge mobil rescrie regulile în dumneavoastră htaccess Uita-te pentru cele 2 linii cu textul " 2.0\MMP|240x320" şi ştergeţi-le.De exemplu: pentru cache %1$sabout/ ar trebui să introduceţ %1$sabout/ or /about/. Cache la dosar va fi generat în următorii un timp anonim vizite că pagina utilizatorului.Fresh Super fişierele din cacheFresh Files WP-CacheHomePrima pagină textRefresh completă a memoriei cache în ore %d %d minute şi %d secunde.GZIP compresie este activată în WordPress, WP-cache vor fi ocolite până când compresie gzip dezactivaţi.Clar de molozGzip reguli de codare în %s.htacces creat.El a blog-uri la %1$s şi fotografii de mesaje de la %2$s.Ascunde listă de fişiereHomeI’m 99% certain that they aren’t Bug-uri în WP Super Cache şi ele se întâmplă numai în cazuri foarte rare, dar puteţi rula o verificare simplă o dată la fiecare 5 minute pentru a verifica dacă site-ul dvs. este ok, dacă sunteţi îngrijorat. Tu va fi trimisă în cazul în care există o problemă.Adresa IPDacă acest lucru nu funcţionează, asiguraţi-vă că %s/avansat-cache.php doar nu există:În cazul în care ora de expirare este mai mare de 1800 secunde (o jumătate de oră), de colectare a gunoiului se va face la fiecare 10 minute, altfel se va întâmpla 10 secunde după ora de expirare de mai sus.În cazul în dezinstalarea acest plug-in, asiguraţi-vă că %s dosar este inscriptibile de către serverul web astfel încât fişierele avansate-cache.php şi config.php cache-pot fi şterse în mod automat idee. (Asigurându-vă că aceste fişiere sunt inscriptibile prea este, probabil, un bun.).În ’General caching’ colectare a gunoiului regulat va curata doar la fişierele vechi moştenire pentru utilizatorii cunoscuţi nu, fişierele preîncărcate supercache. Aceasta este o setare recomandată atunci când memoria cache este preîncărcate.În cazuri foarte rare pot apărea două probleme pe unele blog-uri:
    1. Pagina de faţă poate începe descărcarea ca un fişier zip.
    2. Pagina este greşit ocazional cache ca pagina de faţă dacă blog-ul dvs. foloseşte o pagină statică şi structura Permalink este /%category%/%postname%/.
    Se pare că mod_rewrite nu este instalat. Uneori, această verificare nu este 100% de încredere, mai ales dacă nu sunteţi folosind Apache. Vă rugăm să verificaţi că mod_rewrite modulul este încărcat. Este necesar pentru a servi fişiere statice Super Cache. Veţi fi în continuare posibilitatea de a utiliza moduri de moştenire sau PHP.Se pare ca blog-ul dvs. are adresele URL care se termină cu o "/". Din păcate, din moment ce ai instalat acest plug-un duplicat bug conţinut a fost găsit în cazul în care nu adresele URL se termină într-o "/" sfârşitul servesc acelaşi conţinut ca şi cele cu "/" şi nu redirecţionare a URL-ul propriu Pentru a repara, trebuie să editaţi fişierul htaccess şi adăugaţi aceste două reguli pentru cele două grupe de reguli Super Cache:CheieLegacy caching pagina.Mai e-mailuri, 1 la începutul şi 1 la sfârşitul preîncărcarea toate mesajele.Lista toate fişierele din cacheLista de cele mai noi paginile stocate în cache de pe această pagină.Lock DownLock Down:Jurnal nivelLogging TipulConectarea la un fişier este mai uşor, dar se confruntă cu problema că golirea memoriei cache va şterge fişierul jurnal.A face WordPress mai repedeAsiguraţi-casuta necompletat pentru a-l scoate din lista de pagini directe şi a şterge fişierul cache.Multe e-mailuri, 2 email-uri la 100 de posturi.Medium, 1 e-mail la 100 de posturi.DiverseMissing Module ApacheMobile sprijin dispozitiv.Mobile regulile de rescriere detectatSuport pentru dispozitive mobile necesită norme suplimentare în fişierul htaccess, sau puteţi seta modul de plug-in pentru moştenirea Aici sunt opţiunile dumneavoastră (în ordine de dificultate):Mod Reguli de rescriereMod Regulile de rescriere nu poate fi actualizat!Mod Regulile de rescriere trebuie să fie actualizate!Mod Regulile de rescriere actualizate!Mod rescrie nu poate fi instalat!Mod_rewrite este cel mai rapid, PHP este aproape la fel de rapid şi mai uşor de lucru pentru a obţine, în timp ce caching moştenirea este mai lent din nou, dar este mai flexibilă şi, de asemenea, uşor pentru a obţine de lucru. Utilizatorii noi ar trebui să meargă cu caching PHP.Aveti nevoie de ajutor? Verificaţi Super Cache fişier Readme. Acesta include documentaţia de instalare, o şi depanare sfaturi FAQ. forum de suport este de asemenea disponibil. întrebarea dvs. poate au fost deja răspuns.Cele mai noi Pagini cache:Next GC în câteva minute %sNotă:Notă: PHP permite caching, reconstrui cache, şi suport mobilNota: mod_rewrite activat sau caching Legacy. Rezultate Advanced Settings Page implicit.Nota: Supercache mod_rewrite normele detectate fişierele din cache va fi servite cu aceste norme. Editaţi fişierul htaccess în rădăcina dvs. de a instala şi de a elimina normele SuperCache.Nota: WP Super Cache mod_rewrite controale regulă cu handicap cu excepţia cazului în care rulează pe pe site-ul principal al acestei reţele.Nota: WP Super Cache mod_rewrite controale regulă cu handicap cu excepţia cazului în care rulează pe site-ul principal al acestei reţele.OKLista de caching disponibile.Una sau mai multe cereri de start a eşuat:Numai reincarca pagina curentă atunci când observaţiile făcute.PHP este comprimarea datelor trimise de vizitatorii site-ului. Dezactivarea acest lucru este recomandat ca plugin-ul cache de ieşire comprimat o dată în loc de comprimare aceeaşi pagină de peste si peste din nou. Vedea, de asemenea #21 în secţiunea Depanare. Consultaţi această pagină pentru instrucţiuni referitoare la modificarea fişierul php.ini.Pagina %d: %d (%s)Pagina 1: %sPagina 2: %sPaginiPermlink Structura ErrorVă rugăm să creaţi %s /wp-cache-config.php din wp-super-cache/wp-cache-config-sample.phpVă rugăm să-l salut pe %s prea!Vă rugăm să consultaţi de intrare 16 în secţiunea Rezolvare Probleme de readme.txtVă rugăm să citiţi readme.txt pentru instrucţiuni privind dezinstalarea acest script. Uita-te pentru rubrica, "Cum să dezinstalaţi WP Super Cache".A apărut o eroare pe pagina principală a blog-ul dvs. nu a fost detectat text cheie "%2$s". Pentru a corecta o greşeală, puteţi vizita această pagină %1$s şi clar manual memoria cache.Eroare!" Vizita %s pentru a elimina cache!Plugin-uriPreîncărcatePreîncărcate mesaje %s.Preîncărcate Cache NowPreîncărcate a fost repornit. %sPreîncărcate modul (de colectare a gunoiului numai pe fisiere cache moştenirea recomandate.)Preincarcarea creează o mulţime de fişiere cu toate acestea. Caching se face de la cel mai nou post la cea mai veche deci vă rugăm să ia în considerare numai caching mai nou, dacă aveţi o mulţime (10.000 +) de posturi. Acest lucru este important mai ales pe shared hosting.Preincarcarea de cache cu handicap. Vă rugăm să dezactivaţi memorarea paginilor în cache moştenire sau vorbiti cu administratorul gazdă.Pregătiţi-server-ul dvs. pentru un vârf aşteptată a traficului prin activarea blocare în jos. Cand este activat, noi comentarii pe un post care nu va actualiza fişierele cache static.Spune cu mândrie lumea server-ul dvs. este dovada Digg! (Locuri un mesaj în subsol blog-ului dvs.)Doar în citire Mode. Configurare nu poate fi schimbat.Readonly:RecomandatReîmprospătare de cache în %d ore %d minute şi %d secunde.Reîmprospătare cache preîncărcat fişiere minute la fiecare %s (0 dezactiva, minim %d minute.)Reîmprospătare această pagină atunci când permisiunile pentru fisiere au fost modificate.Reîmprospătare această pagină atunci când aţi actualizat fişierul htaccess.Actualizat următoarele posturi:Stats Regenerare cacheRespins de agenţi de utilizareNecesar pentru a servi fişiere comprimate supercache în mod corespunzător.Necesare pentru a seta informaţii cache de pe paginile supercache IE7 utilizatorii vor vedea paginile vechi, fără acest modul.Restore de configurare impliciteRegulile de rescriere trebuie să fie actualizateRegulile trebuie să fie adăugată la %s prea:Exemplu de WP-Cache fişier de configurare (%s) nu exista. Va rugam sa verificati vă de instalare.SalvareSalvaţi FilesSalvaţi StringsSalvaţi Strings UAPreîncărcându programate de cache anulate.Preîncărcându programate de cache anulat cazul în care un loc de muncă este în prezent rulează acesta nu va shutdown până când curentul 100 de pagini sunt complete.Preîncărcându programate de cache în %d minutePreîncărcându programate de cache în 10 secunde.Programarea minute refresh preload următoare în %d.Derulaţi în jos pagina Setări avansate şi faceţi clic pe butonul Update mod_rewrite Reguli.Paginile de căutareTrimite-mi email-uri de stare atunci când fişierele sunt actualizate.Trimite non-sigură (https non) cererea pentru pagina de startSetaţi data de expirare de pe paginile supercached Vizitatorii nu pot vedea noi pagini atunci când reîmprospătare sau lăsaţi comentarii, fără acest modul.Seta ora de expirare la 0 de secunde pentru a dezactiva colectare a gunoiului.Setaţi plug-in pentru modul de moştenire şi pentru a permite suport mobil.SetăriPosturi SingleImi pare rau. Blog-ul meu este blocat. Actualizări va apărea în scurt timpViciat Super fişierele din cacheViciat Files WP-CachePentru a preveni plug-in pentru interogări cache-ul de la roboţii motoarelor de căutare şi altor roboţi în reţea, introduceţi numele acestora în caseta de mai jos (câte unul pe linie). În cazul în care o copie a paginii există deja în cache, Super Cache, acesta va fi trimis la bot.Tag-uriTest CacheTestaţi-vă site-ul cache făcând clic pe butonul de test de mai jos.Tester & ContinutText pentru a căuta pe pagina dvs. Dacă acest text lipseşte cache va fi şters. Lăsaţi necompletat pentru a dezactiva.Vă mulţumim pentru upgrade.WP Super Cache fişier de configurare este de %s/wp-cache-config.php şi nu pot fi modificate. Acest dosar trebuie să fie inscriptibile de către webserver să facă orice modificări.A apărut o eroare pe pagina principală a blog-ul dvs. nu a fost detectat text cheie "%2$s". Vizitaţi această pagină %1$s pentru a verifica cache.Cache tot blog-ul dvs. a fost eliminat, ca plugin-ul observat o eroare pe pagina principală (aceasta descărcări arhivă). Pentru a verifica cache-ul, vă rugăm să vizitaţi această strnitsu %s.Fişier %s.htaccess nu poate fi modificat de către Web Server. Vă rugăm să corectaţi acest lucru, folosind chmod sau comanda dvs. client FTP.Următoarele module Apache lipsesc plugin va. Lucra în modul de moştenire fără ele. În modul complet Supercache, vizitatorii dvs. pot vedea paginile corupt sau din data de conţinut cu toate acestea.Mod_rewrite normele modificate de la ultima ta instalat acest plug-in. Din păcate, trebuie să eliminaţi vechile reguli supercache înainte de cele noi sunt actualizate reîmprospăta această pagină. După ce aţi editat fişierul .htaccess. Dacă doriţi să faceţi upgrade manual, modificaţi următoarea linie: %1$s astfel se pare ca aceasta: %2$s. Singurele modificări sunt "HTTP_COOKIE"devine"HTTP:Cookie" şi "wordpressuser"devine"WordPress". Acesta este un WordPress 2.5. schimbare, dar este compatibil cu versiunile mai vechi daca esti destul de curajos să le folosească.Paginile nu se potrivesc sau marcajele de timp diferă! Nu au fost găsit!Rescriere normele impuse de acest plugin-au schimbat sau lipsesc.Marcajele de timp pe ambele pagini meci!Acest lucru este strict o funcţie avansată doar şi cunoştinţe atât de PHP şi acţiuni WordPress este obligată să le creeze.Acest lucru va cache fiecare post publicat şi pe pagina site-ul dvs. Acesta va crea fişiere supercache statice astfel vizitatori necunoscut (inclusiv roboţi) va lovi o pagina din cache. Acest lucru va ajuta, probabil, rang dvs. Google ca le folosesc de viteză, ca metric atunci când judecă site-uri web acum.Acest lucru va avea nici o afecta pe utilizatorii obişnuiţi, dar utilizatorii de telefonie mobilă vor vedea paginile uncached.Pentru a servi statice HTML server de fişiere dvs. trebuie să aibă corect mod_rewrite normele adăugat într-un fişier numit %s.htaccessPrea multe fişiere cache, nici un anunţ este posibil.Trailing slash verifica necesare.URIDin pacate WordPress nu poate găsi fişierul wp-cron.php Acest script este necesar pentru funcţionarea corectă de colectare a gunoiului de acest plug-in, WordPress posturi programate, precum şi alte activităţi critice.Din păcate, rescrie regulile nu pot fi actualizate automat atunci când rulează WordPress UM. Vă rugăm să vă deschide htaccess şi. Se adaugă următoarele mod_rewrite regulile de mai sus a oricăror alte norme în acel fişier.Update Pagini DirectUpdate mod_rewrite reguliSetări de updateStatus UpdateUtilizarea PHP pentru a servi fişiere cache.Foloseste mod_rewrite pentru a servi fişiere cache.Utilizarea cache obiect pentru a stoca fişierele din cache.Vezi mod_rewrite ReguliSetări WP Super CacheWP Super Cache a verificat prima pagină a blog-ul dvs. Vă rugăm să vizitaţi %s dacă doriţi să dezactivaţi acest lucru.Plugin WP Super Cache nu este activat. Pentru a activa aceasta, mergeţi la pagina de management plug-in.WP Super Cache mod regulile de rescriere au fost detectate în fişierul% s.htaccess.
    Faceţi clic pe link-ul următor pentru a vedea liniile de adăugat la acel fişier. Dacă aţi actualizat plugin-ul asiguraţi-vă că aceste reguli se potrivesc.Plugin WP Super Cache ar trebui să fie configurat: Pentru a activa şi configura, du-te la pagina de management plug-in.WP-Cache StatusWP-Super-CacheAtenţieAtenţie!Atenţie: %s este inscriptibile!Avertisment PHP Safe Mode Enabled!Avertisment! Hostname "%s" rezolvă la %sWordPress MU DetectedWordPress este blocat. Super fişiere statice Cache nu vor fi şterse atunci când noi comentarii sunt făcute.WordPress nu este blocat în jos comentariile noi vor reîmprospăta Super Cache fişiere statice, ca de obicei.Inscriptibile:Aveţi posibilitatea să editaţi fişierul singur adăuga următoarele reguli.Puteţi vedea în cazul în care normele de du-te şi să examineze normele complet, făcând clic pe "View mod_rewrite normele" link-ul de mai jos.Este posibil să apară probleme de funcţionare, deoarece acest plug-in Safe Mode este activat.Trebuie să aveţi şi END markeri incepe in %s.htaccess pentru auto update la locul de muncă. Acestea arata ca acest lucru şi surround principal WordPress mod_rewrite normele:Trebuie să facă %s writable pentru a activa această facilitate. Deoarece acesta este un risc de securitate vă rugăm să-l doar în citire după ce pagina este generat.Ai sau un administrator ar putea să facem să funcţioneze prin schimbarea proprietar al grupului de plugin-ul script-uri pentru a se potrivi cel al utilizatorului server de web. Proprietar al grupului de %s/cache/ dosar trebuie să fie, de asemenea, schimbat. Se vedea modul de siguranţă pagina de manual pentru detalii suplimentare.Ai sau un administrator trebuie să dezactivaţi această. Consultaţi pagina de siguranţă modul manual pentru detalii suplimentare. Acest lucru nu poate fi dezactivat într-un fişier. htaccess, din păcate. Aceasta trebuie să fie în fişierul de configurare php.ini. Ar trebui să schimbaţi permisiunile pe% s şi să-l mai restrictive utilizarea clientului de FTP, sau următoarea comandă pentru a remedia lucrurile:%s.htaccess ta nu poate fi scris de serverul web şi trebuie să fie actualizate cu normele necesare mod_rewrite. Noile norme du-te mai presus de reguli WordPress regulate aşa cum se arată în codul de mai jos:Your WP-Cache fişier de configurare (%s) este de actualitate şi nu poate fi scris de către server. Please Web ştergeţi-l şi a reîmprospăta această pagină.Cache director ($ cache_path) nu există şi nu poate fi creat de către serverul de web. Verificarea %s permisiunilor.Cache dosar (%1$s) sau %2$s trebuie să fie writable pentru acest plugin pentru a lucra. Double-check.Comentariul dvs. este în aşteptarea moderaţie.Serverul este configurat pentru a verifica proprietarul de scripturi PHP înainte de a le permite să citească şi să scrie fişiere.Serverul crede hostname rezolvă la %s. Unele servicii, cum ar fi colectarea gunoiului de acest plugin, şi WordPress posturi programate să nu funcţioneze corect.Compresie de ieşire Zlib Enabled![%1$s] %2$d mesaje împrospătat[%1$s] Cache preîncărcate începute[%1$s] Refreshing mesajele de la %2$d la %3$d[%s] Cache preîncărcate Completed[%s] Prima pagina a verifica![%s] Home comprimate folosind gzip. Cache eliminat![%s] Home comprimate folosind gzip. Delete Cache![%s] Prima pagină este afişată cu o eroare! Cache eliminat![%s] Pagina Prima nu este corect. Vă rugăm să goliţi memoria cache![%s] preîncărcate poate fi stagnat.toateoffactivatfilesecundelanguages/wp-super-cache-lt_LT.mo000066600000160407152133035240012720 0ustar009 8<9,vM` s~?3>rb"*7Z5C5y =bj^ \ r&!!?"#w$Z%`%&.&'&((:(n'*p*,,,,, ,3,-"- 1-,>-k-^.p{.+.//./^/ f/ r/+}//3// 00!%0G0!27>2v22I;3@33sK44%?5e5|5 55 5555553616777888u\9j9=:B::?:9;@;H;NN;; ;n;$.<S<Y<v<<<~<@==>> >><>g*??+?*?? @@ AbAA1B:C&D"/EkRFGGEGH*3H ^H hH sH }HbHH]I$aII IIIIIJ$J"JJ! K,KKL&LM<"Mb_MM|uNyNlO0oO!O-OkO\Q mQ xQQQTQQURmRpSUSSSSTTJ5TTd]UU`iV0V V W7WSIW?W<WX9XPX7eXjXY&YDYYcYY Y YY(YZ+Z,Z.Zf![ [/[0[[?x\8\\ \:]B][]q]H^ M^;X^^q^_1__x`aaQb<idGd#due eTf~f+ggggghNibi{i ii%i'ijjj4jbjklk9lBlQlYlbl|l*llbl[@m m7mrmMRnnYo/o qrr?ssRt$tetau v%vAv)^vvv*v/v.w3FwzwwwwwwwTky2y3y'zAzPYzzzFI{O{{{k|3%}1Y}b}5};$~(`~PlG`̀|.SyބrX˅6v)@j `i'{=0#Tk/"@1c?͐ L,y . ʓE1PQ,b9{Ӗ Op @ח387&^5  y<HѝڝR=Yuj, "8Vt8ʡ>gR6΢MSl~ Xxyv_HNQIPHk :ի" 5@dPgӬ,;+h +׭0.#!#Ei2!;<xGɱO~$}!B$.gCڴbv V#M9:lǸ 4 ?M#b6Poe^1<ͼܼ2`G@ǽ! * K6Yv%.-(\O տ!/*Z*+IFE$HjRMR = JiX _YjW>CM*T>?|{?"X{U1G,[26 r1ulXap y+4\Zw Lq-PAB qrr&gf%!&/9$i#;9>(Hg)  G>L(+3uTk$^&  9b!8j _#`%v6ip4Q*+0!;KgW@DI  )&r:$8H"=' {c*A2oZM~.5haC,1 E2U6[yS(lq4YP s9]0/'VBFN /X ,3t 5-w1}|xe\?O"#%Jmd)<zR7.7-n f Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php     does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.) (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) (support for multiple domains on multisite websites) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.No Adverts for Friends plugin is %s.Domain Mapping support plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting Moderation plugin is %sBad Behaviour not found. Please check your install.Bad Behaviour support is %s.Cache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Don’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLegacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching.Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.One or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Update Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: WP Super Cache Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-09-27 13:58+0000 PO-Revision-Date: 2011-07-30 20:42+0200 Last-Translator: Natalija Strazdauskienė Language-Team: Nata Strazda MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Lithuanian X-Poedit-Country: LITHUANIA Įsitikinkite, kad jie eina prieš bet kurią WordPress egzistuojančią taisyklę. %1$s dėkingas įskiepiui %2$s už atliktą darbą%1$s sukurtas ir palaikomas %2$s ir daugelis kitų.%s talpykliniai puslapiai%s pasibaigę puslapiai%s įrašomas. Prašome pakeisti teises į "Ti skaitymui" jūsų blogo saugumui.%s pašalintas!failas %s.htaccess buvo sėkmingai atnaujintas, reikalingos mod_rewrite taisyklės pridėtos. Prašome patikrinti jas. Jos turi atrodyti taip:%s/advanced-cache.php neegzistuoja arba negali būti atnaujintas.(1 = mažiausias, 5 = didžiausias, gali sukelti per didelį krūvį serveriui)(Eksperimentinis)(Šis įskiepis funkcionuos tik vidutinio talpinimo režimu, atjunkite suspaudimą ir įdiekite įskiepį Bad Behavior "%s/plugins/blogas-elgesio/")(Pašalinti tekstą "Jūsų komentaras laukia patvirtinimo.", kai kas nors palieka komentarą peržiūrai.)(sąrašas nerekomenduojamas didelioms svetainėms)(tik logo užklausos iš šio IP. Jūsų IP - %s)(reikalingas friendsadverts.php taip pat) (palaiko daugybinius domenus ir daugybines svetaines)1. Jeigu jau egzistuoja, prašome pirmą pašalinti failą.2. Pakeiskite prieigos teises į %1$s, kad galima būtų šrašyti duomenis auto režimu (teisės turi būti: chmod 777 %1$s), patikrinkite teises ir atnaujinkite puslapį. Tai laikina taisyklė, po puslapio atnaujinimo teises reikės grąžinti į pradinius nustatymus (iš 777 į 755).3. Atnaujinkite puslapį, failas %s/advanced-cache.php atsinaujins pats304 Ne modifikuota naršyklės talpykla. Nurodoma, kai puslapis nebuvo pakeistas nuo paskutinio užklausimo.304 palaikymas yra išjungtas pagal nutylėjimą, nes pastaruoju metu GoDaddy turėjo problemų su kai kuriom naudojamom antraštėm.No Adverts for Friends įskiepis yra %s.Domain Mapping įskiepio palaikymas yra is %s

    WP_CACHE konstanta pridėta į wp-config.php

    Jei ir toliau matysite šį įspėjamąjį pranešimą, prašome žiūrėti 5 punkteDUK. WP_CACHE linija turi būti perkelta.

    WP_CACHE konstanta nustatyta į false

    WP_CACHE konstanta naudojama WordPress kodo įkelimui, kuris tarnauja puslapių talpyklai. Deja, tai klaidinga. Prašome redaguoti savo wp-config.php ir pridėti arba redaguoti šią eilutę virš galutinės require_once komandos:

    define('WP_CACHE', true);

  • 1. Atverti "%1$s$wp_cache_file teksto redaktoriumi.
  • 2. Keisti tekstą CACHEHOME%2$s
  • 3. Išsaugokite failą ir nukopijuokite jį į %3$s ir perkraukite šį puslapį.
    • Klaida: WP_CACHE nėra įjungtas jūsų wp-config.php faile ir aš negalėjau jį pakeisti.Šiukšlių valymas
    Paskutinis šiukšlių valymas buvo prieš %s min
    Įspėjimas! Jūs bandėte įjungti suspaudimą, bet zlib.output_compression zlib.output_compression yra įjungtas . Žr. #21 skyrių "Problemų diagnostika" readme failą.Teisingui įskiepio darbui reikalingas korektiškas url ar pastovios nuorodos struktūros nustatymas.. Prašome eiti į Pastovių nuorodų puslapį, kad sukonfiguruoti pastovias nuorodas.Tarp taisyklių jūsų faile .htaccess ir taisyklių pačio įskiepio rasti nesutapimai. Tai gali būti papildomas simbolis eilutėje, bet jūs patys turite sulyginti originalias taisykles su savo kuo greičiau. Paspauskite mygtuką ’Atnaujinti Mod_Rewrite taisykles’, kad padaryti tai ato režimu.Paparsčiausias būdas tai išspręsti - pakeisti prieigos teises, naudojant CHMOD, per FTP-klientą. Pakanka nustatyti globalias teises rašymui.Priimami failų pavadinimai & Atmesti URIPridėti tiesioginį puslapį:Laukelį žemiau galite užpildyti puslapių adresų fragmentais (arba puslapių grupėmis, pvz. archyvas už metus/mėnesį ir t.t.), kurie nebus saugojami. Įskiepis skanuos puslapių adresus ir ieškos fragmentus, nurodytus žemiau, prieš saugojimą.Laukelį, esantį žemiau, jūs galite užpildyti failų vardais, kurie bus saugojami net tuo atveju, jei pavadinimuose bus draudžiami fragmentai.Pridėkite taisykles patys. Redaguoti %s.htaccess ir rasti kodo bloką tarp # BEGIN WPSuperCache ir # END WPSuperCache . Yra du skyriai, kurie atrodo labai panašiai. Tiesiog žemiau linijos %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ pridėkite šias eilutes: (tai padaryti du kartus, vieną kartą kiekviename skyriuje)IšplėstinėAmžiusJūs taip pat galite redaguoti failą %s.htaccess rankiniu būdu ir asmeniškai įrašyti reikalingas taisykles (iki esančių ten WordPress taisyklių):ArchyvaiTurimi įskiepiaiLaukiamas patvirtinimo įskiepis yra %sBad Behaviour nerasta. Prašome patikrinti jūsų įdiegimą.Bad Behaviour parama yra %s.Talpyklos turiniaiTalpyklos patikraSaugoti svetainės peržiūras greitai prieigai.Talpyklos įskiepiai yra PHP skriptai, kurie gyvena įskiepio aplanko viduje wp-super-cache aplanke. Jie pakraunami, kai pasikrauna Supercache, daug greičiau nei reguliarūs WordPress įskiepiai.Talpykla atstatyta. Pateikti talpyklos failai anoniminiams vartotojams, kol naujas failas yra generuojamas.Cache statistika nėra automatiškai sugeneruojama. Jūs turite paspausti nuorodą žemiau, kad šiame puslapyje regeneruotusi statistika.Talpyklos statistika sugeneruota: %s min atgal.Įdėta į talpyklą prieš %s sekPuslapių talpykloje %1$s : %2$sSaugyklos statusasTalpykla išjungtaTalpykla įjungtaTalpykla turi būti įjungta jei norite naudoti šią funkcijąAtšaukti bendrąją talpykląNegalima tęsti...ištaisykite bųvusias problemas ir pabandykite iš naujo.Negali atnaujinti .htaccessKategorijaKeisti galiojimo pabaigąPatikrinkite pirmąjį puslapį kas 5 minutes.Pasibaigusių failų tikrinimas ir šalinimas užtrunka, bet ir palikti tokius failus sistemoje neverta. Dideliuose bloguose reikia nurodyti "gyvavimo laiką" kiekvienos kopijos 300 sek. Jūs galite eksperimentuoti su nustatymais ir pažiūrėti, kiek pasibaigusių puslapių kopijų lieka talpykloje dienos metu. Optimalus tokių puslapių skaičius ne daugiau nei 500. Naudokite saugojimą su mod_rewrite arba PHP, Jūs galėsite padidinti saugomų puslapių skaičių.Valymas senų supercache failų.Išvalyti visus talpyklos failus, kai skelbiama žinutė ar puslapis.Valyti talpyklą klaidos metu.Failų blokiravimas. Jms tikriausiai nereikia, tačiau ji gali padėti, jei jūsų serveris yra silpnas. Įspėjimas! Gali sukelti jūsų serverio užrakinimą labai retais atvejais!Komentarų tikrinimas įjungtas. Po kiek laiko jūsų komentarai bus apublikuoti.Suspausti puslapius, kad paspartinti darbą.Suspaudimas yra išjungtas pagal nutylėjimą, nes kai kurie hostingai turi problemų su suspaustais failais. Perjungimas tarp įjungimo ir išjungimo išvalo talpyklą.Konfigūracijos failas pakeistas, kai kurios reikšmės gali būti klaidingos. Pakraukite puslapį iš naujo iš "Nustatymai " meniu, kad tai ištaisyti.Konfiguracijos failas nerastas ir katalogas %1$s (%2$s) nėra įrašomas į serverį. Patikrinkite teises.Šiuo metu saugoma iš %d į %d.Šiuo metu prisijungta prie:DerinimasDerinimasPanaikintiIštrinti talpykląIštrinti pasibaigusįPašalinti Super Cache talpyklos failus (atsidarys naujam lange)Ištrinti talpyklos failąIštrinti įskiepio mod_rewrite taisykles %s.htaccess tarp # BEGIN WPSuperCache ir # END WPSuperCache ir tegul įskiepis regeneruoja juos kraunantis puslapiui.Ištrinamas supercache failas: %s
    Ištrynamas wp-cache failas: %s
    Programuotojams: Padarykite savo įskiepį uždarytu režimu ir suderintu su mūsų įskiepiu, įterpus "WPLOCKDOWN". Žemiau esantis kodas padės jums adaptuoti įskiepį prie mūsų.Tiesioginis failų saugojimasToks saugojimas sukuriamas tiesiogiai iš katalogo %s. Ši parinktis naudinga tuomet, kai laukiamas lankytojų antplūdis iš populeresnio blogo į jūsų blogo konkrečią žinutę ar puslapį.IšjungtiAtjungtaNe saugoti tokių tipų puslapius. Palyginkite su Sąlyginiai tegai dokumentacija, kad sužinoti daugiau.Domain Mapping įskiepis aptiktas! Prašome grįžti į įskiepių Supercache puslapį ir įjungti domeno žemėlapių padėjėjo įskiepį.Negalima saugoti puslapių žinomiems vartotojams.LengvasRedaguoti %s ir pridėti šią eilutę:
    apibrėžti('WP_CACHE', true);
    Priešingu atveju, WP-cache negali būti vykdomas WordPress Core .EmailPraneškite blogo administratoriui po patikrinimo (naudinga testuojant).ĮjungtiĮjungtaKlaidaKlaida: GZIP suspaudimas įjungtas, atjunkite jį, jeigu norite pajungti wp-cache.Esamas tiesioginis puslapisBaigiasi laikas:Pasibaigęs failai - tai failai, senesni nei %s sekundžių. Jie vis dar naudojami įskiepio ir trinami periodiškai.Pasibaigęs laikas & Šiukšlių valymasKanalaiPatikra %s svarbiausios talpyklos:Pirmosios kopijos %s patikra:Antrosios kopijos %s patikra:Nustatyti konfigūravimąČia galite išspręsti kai kurias problemas, iškylusias darbo su įskiepiu metu, derinimo pagalba. Jūs galite įrašyti logus į failus, esančius talpyklos kataloge.Geriausiu atvėju turėtumėte įjungti "Mobiliojo prietaiso parama" arba ištrinti .htaccess mobiliojo perrašymo taisykles. Ieškoti 2 eilutę su tekstu "2.0\MMP|240x320" ir ištrinti.Pavyzdžiui: kad patalpinti puslapį %1$sabout/ į talpyklą, reikia įrašyti %1$sabout/ arba /about/. Puslapis bus išsaugotas iš karto, kai pirmą kartą jis aplankytas.Šviežia Super failų talpyklaŠviežia WP-failų talpyklaPagrindinis puslapisPirmo puslapio tekstasPilnas saugyklos atnaujinimas:%d val %d min ir %d sekundžių.Suspaudimas GZIP įjungtas WordPress nustatymuose, įskiepis nedirbs tol, kol neatjungsite suspaudimą.Šiukšlių valymasGzip-suspaudimo taisyklės patalpintos į %s.htaccess.Apsilankykite įskiepio autoriaus bloge %1$s ir publikuokite nuotraukas %2$s.Slėpti failų sąrašąPradinis puslapisI’m 99% certain! Kalidos, kurios gali iškilti dirbant su WP Super Cache, nesusijusios su pačiu įskiepiu. Jos atsiranda retais atvėjais, bet jūs galite apsisaugoti, paleidžiant kas 5 min automatinį blogo tikrinimą. Atsiradus klaidai, jums apie tai bus pranešta per email.IP adresasJei tai neveikia, įsitikinkite, kad failas %s/advanced-cache.php neegzistuoja:Jeigu taupyklos aktualumas daugiau nei 1800 sek (pusė valandos), tuomet šiukšlių šalinimas bus vykdomas kas 10 min.Jeigu pašalinti šį įskiepį, įsitikinkite, kad katalogo %s yra įrašomi serveryje, todėl advanced-cache.php ir cache-config.php failai gali būti ištrinti automatiškai . (Įsitikinkite, kad tie failai yra įrašomi!)Režime ’Bendro talpinimo’ planuotas šiukšlių išvalymas ištrins tik talpykloje esančius paprasto tipo įrašus (talpykla iš Super Cache nebus pašalintas). Tai yra rekomenduojama naudojimui.Ypač retais atvėjais bloge gali iškilti dvi problemos:
    1. Vietoj pradinio puslapio vartotojai gali matyti siūlymą įkrauti su ja .zip archyvą
    2. Vietoj pradinio puslapio į talpyklą gali būti įdėtas visiškai kitas (tik tuo atvėju, jeigu blogas naudoja sekančią nuorodų struktūrą /%category%/%postname%/).
    Įvyko klaida, susijusi su tuo, kad modulis mod_rewrite neegzistuoja arba nėra įdiegtas. Prašome patikrinti modulio mod_rewrite serverio konfiguracijoje. Modulis reikalingas korektiškam įskiepio darbui su statistiniais failais. Be prijungto mod_rewrite jūs galite naudoti tik režimus su PHP palaikymu arba vidutinį talpinimą.Rodos, visos jūsų blogo nuorodos baigiasi simboliu "/". Dėja, kai tik jūs įdiegėte įskiepį, suveikė funkcija, radusi nuorodų kopijas be "/" gale, ir dabar negali perkelti teisingu adresu. Problemą pašalinti padėsfailo .htaccess redagavimas ir 2 naujų taisyklių įterpimas prie pagrindinių Supercache įskiepio taisyklių:RaktasSupaprastintas saugojimas.Žemas lygis: 1 e-mail pradžioje ir 1 gale po visų žinučių apkrova.Visų talpyklos failų sąrašasSąrašas naujausių talpyklos puslapių šiame puslapyje.Uždaras režimasUždaras režimas:Logo lygisĮėjimo būdasGauti priėimą prie failo logo paprasta, tačiau išvalant talpyklą logas taip pat bus ištrintas.Padaryti WordPress spartesniuKad pašalinti puslapį iš tokios talpyklos, išvalykite tekstinį laukelį ir pašalinkite talpyklą.Daug laiškų, 2 laiškai į 100 žinučių.Vidutinis lygis: 1 email į 100 žinučių.ĮvairūsTrūksta Apache moduliųMobiliojo prietaiso palaikymas.Mobiliai perrašytų taisyklių pažeidimaiMobilusis palaikymas reikalauja papildomų taisyklių jūsų .htaccess faile arba galite nustatyti įjungtu režimą. Čia yra jūsų parinktys (sudėtingumo tvarka):Mod Rewrite taisyklėsMod Rewrite taisyklės negali būti atnaujintos!Taisyklės mod_rewrite turi būti atnaujintos!Mod_rewrite taisyklės atnaujintos!Mod rewrite negali būti įdiegtas!Naudojimas mod_rewrite padės paspartinti blogo darbą, negu PHP (nors šis variantas irgi ne toks lėtas). Šis režimas paprastesnis ir patogesnis, bet pradedančiajam geriau naudoti saugojamą PHP.Reikia pagalbos? Patikrinkite Super Cache failą readme . Jis apima įdiegimo dokumentaciją, DUK ir trikčių diagnostikos patarimų. Palaikymo forumas. Į jūsų klausimą galbūt jau buvo atsakyta.Nauji talpyklos puslapiai:Sekantis Šiukšlių valymas bus po %s minPastaba:Pastaba: leidžia įjungti PHP talpinimą ir judriojo ryšio palaikymąPranešimas: mod_rewrite arba vidutinės talpyklos įjungimas. Rodyti išplėstinius nustatymų puslapį pagal nutylėjimą.Pastaba: Supercache mod_rewrite taisyklių aptikimas. Talpykliniai failai bus aptarnaujami naudojant šias taisykles. Redaguoti .htaccess failą jūsų pirminėje direktorijoje ir pašalinti SuperCache taisykles.Pastaba: Taisyklių WP Super Cache mod_rewrite tikrinimas atjungtas, kol nebus paleistas pagrindiniame bloge.Pastaba: taisylių WP Super Cache mod_rewrite tikrinimas atjungtas, kol nebus paleistas pagrindiniame bloge.OKTalpyklos objektas naudojamas. Talpyklos sąrašas nėpasiekiamas.Viena ar daugiau puslapio užklausų nepavyko:Tik atnaujinti dabartinį puslapį, kai atsiranda nauji komentarai.PHP naudoja duomenų suspaudimą dėl jūsų svetainės lankytojų puslapių atvaizdavimui. Šios parinkties atjungimas yra rekomenduojamas, kad išvengti daugkartinio puslapių suspaudimo su įskiepiu. Taipogi žiūrėkite #21 Problemų sekcijoje. Žiūrėkite šį puslapį, kad sekti instrukcijas modifikuotame jūsų php.ini.Puslapis %d:%d (%s)Puslapis 1: %sPuslapis 2: %sPuslapiaiNuolatinės nuorodos struktūraPrašome sukurti %s /wp-cache-config.php iš wp-super-cache/wp-cache-config-sample.phpPrašome aplankyti ir autoriaus %s!Prašau žiūrėti 16 eilutę problemų sekcijoje readme.txtPrašome žiūrėti readme.txt instrukcijas, kaip pašalinti šį scenarijų . Ieškoti pozicijoje, "Kaip pašalinti WP Super Cache".Prašome apsilankyti %1$s, kad išvalyti talpyklą, nes jūsų svetainės pradinis puslapis nėra korektiškas ir trūksta teksto - "%2$s"!Prašome apsilankyti %s, kad išvalyti talpyklą, nes jūsų svetainės pradinis puslapis dabar siunčiamas!ĮskiepiaiPrieškrūvisSaugoti %s įrašus.Sukūrti bendrąją talpyklą dabarIšankstinė apkrova turi būti iš naujo paleista. %sPreliminarus režimas (šiukšlių išvalymas veikia ne pilnai, Rekomenduojama.)Tačiau, naudojant šio tipo talpyklą sukūriama daug daugiau failų. Rekomenduojama naudoti tokį būdą, jei pas jus labai daug įrašų (10,000+) bloge. Ypač tai svarbu, jeigu jūs naudojatės virtualaus hostingo paslaugomis.Saugyklos prieškrova atjungta. Prašome įjungti pilną įskiepio darbą arba susisiekite su administratorium.Paruoškite savo blogą planuojamiems dideliems apsilankymų skaičiams, aktyvuojant šį režimą. Aktyvioje būsenoje naujų komentarų ir žinučių talpinimas neatnaujins talpykloje statinių failų.Papasakoti visiems, kad naudojatės įskiepiu (pranešimas bus patalpintas blogo poraštėje).Tik skaitymo režimas. Konfigūracija negali būti pakeista.Tik skaitymui:RekomenduojamaTalpyklos atnaujinimas po %d val %d min ir %d sek.Atnaujinti bendrą talpyklą kas %s min (įveskite 0, kad atjungti, minimalus min skaičius %d).Atnaujinkite šį puslapį, kai failo prieigos teisės bus modifikuoti.Atnaujinkite puslapį po to, kai atredaguosite .htaccess failą.Atnaujintos sekančios žinutęs:Atnaujinti talpyklos statistikąAtmesti botaiReikalaujama tinkamai suspaustiems supercache failams.Privalo nustatyti talpyklos informaciją supercache puslapiuose. IE7 vartotojai be šio modulio matys senus puslapius.Atkurti numatytąją konfigūraciją.Perrašomos taisyklės turi būti atnaujinamosTaisyklės taip pat bus įterptos į %s:Failas WP-Cache (%s) nerastas. Patikrinkite jūsų įdiegimą.IšsaugotiIšsaugoti failusIšsaugoti uždraustus fragmentusIšsaugoti nustatymusBendroji talpykla pagal tvarkaraštį atjungta.Bendroji talpykla pagal tvarkaraštį atjungta. Jeigu darbas yra paleistas, jis nebus uždarytas tol, kol einamosios 100 puslapių nebus talpykloje.Bendroji talpykla pradės veikti po %d minBendroji talpykla pradės darbą po 10 sek.Sekantis planinis bendros talpyklos atnaujinimas įvyks po:% d minučių.Slinkite žemyn puslapį Išplėstiniai nustatymai ir spustelėkite mygtuką Atnaujinti mod_rewrite taisykles.Paieškos puslapiaiSiųsti man statusą elektroniniu paštu, kai failai yra atnaujinami.Išsiųsti neapsaugotą (ne per https) užklausą pagrindiniam puslapiuiNustatyti galiojimo supercached puslapių pabaigos datą. Lankytojai nematys naujų puslapių, kai jie atsinaujins ar palikti komentarus be šio modulio.Nustatyti galiojimo laiką į 0 sekundžių, kad išjungti šiukšlių surinkimą.Nustatykite vidutinio talpynimo režimu ir kad būtų mobiliojo ryšio palaikymas.NustatymaiTik žinutėsAtsiprašome. Mano blogas laikinai nedirba. Užeikite vėliauPasenusi Super failų talpyklaPasenusi WP-failų talpyklaKad uždrausti įskiepiui saugoti paieškos ir kitų botų užklausas, įveskite jų pavadinimus į laukelį žemiau. Jeigu puslapio kopija jau egzistuoja Super Cache talpykloje, ji visvien bus nusiųsta botui.ŽymosPatikrintiPasitikrinkite savo išsaugotą svetainę, paspaudę žemiau esantį mygtuką testavimui.Testeris & TurinysĮveskite tekstą, kurį ieškos įskiepis pagrindiniame puslapyje. Jeigu tekstas nebus rastas, tuomet talpykla automatiškai išsivalys. Palikite laukelį tuščią, kad atjungti šią parinktį.Dėkojame už modernizaciją.Konfiguracijos įskiepio failas WP Super Cache %s/wp-cache-config.php negali būti pakeistas. Kad tęsti, jūs turite nustatyti rašymo teises.Jūsų blogo talpykla buvo išvalyta, kadangi jūsų blogo pradinis puslapis neturi teksto "%2$s"! Prašome aplanakyti %1$s, kad patikrinti, ar talpykla yra išvalyta.Jūsų blogo talpykla buvo išvalyta, kadangi jūsų svetainės pradinis puslapis šiuo metu siunčiamas. Prašome apsilankyti %s, kad patikrinti, ar talpykla buvo išvalyta.Failas %s.htaccess negali būti atnaujintas automatiniu būdu. Prašome pataisyti jį, naudojant chmod komandą arba ftp klientą.Trūksta šių Apache modulių. Įskiepis dirbs vidutiniu režimu be jų. Pilnu Supercache režimu jūsų lankytojai gali pamatyti sugadintus puslapius ar pasibaigusios datos turinį.Po paskutinio įskiepio atnaujinimo mod_rewrite taisyklės buvo pakeistos. Dėja, jums teks rankiniu būdu pašalinti senas taisykles. Atnaujinkite puslapį, kai baigsite redagavimą .htaccess failo. Jeigu norite atnaujinti viską patys, tuomet pakeiskite sekančią eilutę: %1$s į šią: %2$s . Vienintelis skirtumas - tai pakeitimas "HTTP_COOKIE" į "HTTP:Cookie" ir "wordpressuser" į "wordpress". Šie pakeitimai susiję su nauja WordPress 2.5 versija. Puslapiai nesutampa! Laikinas štampas skiriasi arba nebuvo rastas!Šis įskiepis reikalauja perrašomų taisyklių pasikeitimą arba jų nėra.Laikini abiejų puslpių štampai sutampa!Šiai parinkčiai naudoti reikalingi PHP ir WordPress žinios.Tai bus talpykloje po kiekvieno žinutės ir puslapio patalpinimo jūsų svetainėje. Ji sukurs supercache statinius failus, kad nežinomų lankytojų (įskaitant botų) lankys išsaugotą puslapį. Tai tikriausiai padės Google reitingavimui, nes jie kaip rodiklį naudoja greičio metriką, sprendžiant iš puslapio.Tai nedaro jokios įtakos paprastiems vartotojams, tačiau mobiliojo ryšio vartotojai galės matyti netalpinamus puslapius.Kad įskiepis galėtų teisingai dirbti su statiniais html failais, jūs turite įrašyti į failą %s.htaccess įskiepio mod_rewrite taisyklesPer daug failų talpykloje, juos dėti į sąrašą nebegalima.Reikalinga trailing slash patikra.URIDėja, WordPress negali rasti wp-cron.php failą. Šis skriptas reikalingas korektiškam šiukšlynės išvalymo operacijos rodymui šiam įskiepiui, WordPress reguliariose žinutėse bei kitose svarbiose vietose.Dėja, mod_rewrite negalima atnaujinti auto režimu WordPress MU. Jums teks rankiniu būdu tai atlikti: atidarykite failą .htaccess ir įterpkite sekančią taisyklę.Atnaujinti puslapiusAtnaujinti mod_rewrite teisesAtnaujinti nustatymusAtnaujinti statusąNaudokite PHP talpyklos failų aptarnavimui.Naudoti mod_rewrite talpyklos failų aptarnavimui.Naudokite objekto talpyklą talpyklos failams saugoti.Žiūrėti mod_rewrite taisyklesWP Super talpyklos nustatymaiWP Super Cache patikrino jūsų pradinį dienoraščio puslapį. Prašome aplankyti %s, jeigu norite atjungti tai.WP Super Cache išjungtas. Prašome apsilankyti įskiepio admino puslapyje, kad įjungti talpinimą.Taisyklės mod_rewrite įskiepiui WP Super Cache buvo aptiktos faile %s.htaccess.
    Paspauskite mygtuką, kad peržiūrėti eilutes. Jeigu jūs ką tik atnaujinote įskiepį, patikrinkite visas taisykles.WP Super Cache turi būti sukonfiguruotas! Prašome apsilankyti įskiepio admino puslapyje.WP-CacheWP-Super-CacheDėmesioDėmesio!Įspėjimas! %s yra įrašomas!Įspėjimas! PHP Saugus režymas įjungtas!Įspėjimas! Jūsų prieglobos vardas "%s" atsako %sWordPress MU aptiktasWordPress nenaudoja saugaus režimo. Nauji komentarai neatnaujina visus talpyklos elementus.WordPress nenaudoja saugaus režimo. Nauji komentarai atnaujina visus talpyklos elementus.Įrašomieji:Jūs galite redaguoti failą, savarankiškai pridedant sekančias taisykles.Kad pamatyti pilną veikiančių taisyklių sąrašą, paspauskite mygtuką "Pažiūrėti mod_rewrite taisykles".Jums gali kilti problemų naudojant šį įskiepį, nes Safe Mode yra įjungtas.Korektiškam darbui jūsų %s.htaccess faile turi būti įrašyti BEGIN ir END. Tarp jų randasi pagrindinės WordPress mod_rewrite taisyklės, pvz.:Jūs turite nustatyti teises į %s įrašomais, kad įjungti šią funkciją. Tačiau tai potenciali rizika. Po puslapio atnaujinimo grąžinkite teises.Jūs arba administratorius galite padaryti jį dirbantį, keisdami įskiepio skriptų grupės savininką, kad atitiktų žiniatinklio serverio vartotoją. %s/cache/ katalogas taip pat turi būti pakeistas. Žiūrėti saugaus rėžimo puslapį dėl papildomos informacijos.Jūs arba administratorius turite atjungti tai. Žiūrėkite saugaus rėžimo puslapį dėl papildomos informacijos. Dėja, tai negali būti atjungta .htaccess faile. Tam reikia papildyti php.ini konfiguracijos failą.Jums reikia pakeisti teises %s, ir padaryti jį labiau ribojamu. Naudokite savo FTP klientą arba šią komandą:Jūsų failas %s.htaccess nepasiekiamas įrašymui (serverio nustatymuose) ir negali būti atnaujintas auto režimu. Jūs turite rankiniu būdu pridėti naujas taisykles prie pagrindinių WordPress taip, kaip nurodyta žemiau:Konfiguracijos WP-Cache failas (%s) negaliojantis ir negali būti įrašomas. Prašome pašalinti jį ir perkrauti puslapį.Katalogas ($cache_path) neegzistuoja ir negali būti sukūrtas serveryje. Patikrinkite %s teises.Aplankas (%1$s) arba %2$s turi būti įrašomi, kad šis įskiepis veiktų. Pertikrinkite juos.Jūsų komentaras laukia patvirtinimo.Jūsų serveris patikrins PHP skriptų savininką, prieš leidžiant jiems skaityti ir rašyti failus.Jūsų serveris galvoja, jog jūsų prieglobos vardas pasikeitė į %s. Kai kurie servisai, kaip pavyzdžiui, šiukšlių surinkimas šiame įskiepyje ir WordPress planuojamuose žinutėse gali neveikti tinkamai.Zlib Išėjimo suspaudimas įjungtas![%1$s] %2$d žinučių atnaujinta[%1$s] Bendrasis talpinimas prasidėjo[%1$s] Atnaujinamos žinutės nuo %2$d iki %3$d[%s] Talpyklos prieškrūvis baigtas[%s] Pradinis puslapis patikrintas![%s] Pradinis puslapis buvo suspaustas! Talpykla išvalyta![%s] Pradinis puslapis suspaustas! Išvalykite talpyklą![%s] Pradinis puslapis nėra korektiškas! Talpykla išvalyta![%s] Pradinis puslapis nėra korektiškas! Prašome išvalyti talpyklą![%s] Prieškrūvis gali būti vilkinamas.visiišjungtasįjungtasfailassekundžiųlanguages/wp-super-cache-zh_CN.po000066600000242653152133035240012712 0ustar00# Copyright (C) 2012 # This file is distributed under the same license as the package. msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2012-06-21 09:44:46+00:00\n" "PO-Revision-Date: 2012-07-16 18:14+0800\n" "Last-Translator: \n" "Language-Team: Christopher Meng \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Chinese\n" "X-Poedit-Country: CHINA\n" #: ossdl-cdn.php:151 msgid "Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull." msgstr "您的网站可能使用了大量的静态文件。图像，Javascript 和 CSS 文件通常都是可供其他站点或者 CDN 方便调用的静态文件。因此，本插件使用下方您提供的地址替换了站点的所有 wp-content 和 wp-includes 目录地址(PHP 文件除外) 。这样即可以使您复制所有静态内容到独立主机，又可以通过 文件自动传输到 CDN 功能 为文件做镜像到 CDN。" #: ossdl-cdn.php:152 #: wp-cache.php:1071 msgid "The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin." msgstr "如果您不需要文件自动传输到 CDN 功能(origin pull)，CDN Sync Tool 插件将会帮助有关文件上传至 Amazon S3/Cloudfront 。如果您有意见或者需求，请访问插件支持论坛。" #: ossdl-cdn.php:153 msgid "WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes." msgstr "警告： 请测试一些静态地址比如 %s 以便确保您的 CDN 服务在保存设置前正在工作。" #: ossdl-cdn.php:154 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "您可以对多站点中的每个站点定义不同的 CDN 服务地址。" #: ossdl-cdn.php:162 msgid "Enable CDN Support" msgstr "开启 CDN 支持" #: ossdl-cdn.php:165 msgid "Off-site URL" msgstr "Off-site URL" #: ossdl-cdn.php:168 msgid "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "" #: ossdl-cdn.php:172 msgid "Include directories" msgstr "包含目录" #: ossdl-cdn.php:175 msgid "Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty." msgstr "Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty." #: ossdl-cdn.php:179 msgid "Exclude if substring" msgstr "如果是之前有则排除" #: ossdl-cdn.php:182 msgid "Excludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "如果以上的字符串中有任何一个符合，那么将不会被写入至重写规则中。请使用半角逗号隔开，例如 .php, .flv, .do,，并且无论如何不要删去 .php (默认)。" #: ossdl-cdn.php:186 msgid "Additional CNAMES" msgstr "附加 CNAME 记录" #: ossdl-cdn.php:189 msgid "These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$s" msgstr "" #: ossdl-cdn.php:193 msgid "Skip https URLs to avoid \"mixed content\" errors" msgstr "忽略 https 地址以避免 \"mixed content\" 错误" #: ossdl-cdn.php:197 msgid "Save Changes" msgstr "保存修改" #: ossdl-cdn.php:199 msgid "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "CDN 功能由 Mark Kubacki 编写的 OSSDL CDN Off Linker 插件提供。" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "您的评论正在等待审核。" #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "Awaiting Moderation" #: plugins/awaitingmoderation.php:34 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:75 #: plugins/searchengine.php:69 #: plugins/wptouch.php:22 #: wp-cache.php:1311 msgid "Enabled" msgstr "已启用" #: plugins/awaitingmoderation.php:35 #: plugins/badbehaviour.php:66 #: plugins/domain-mapping.php:76 #: plugins/searchengine.php:70 #: plugins/wptouch.php:23 #: wp-cache.php:1311 msgid "Disabled" msgstr "已禁用" #: plugins/awaitingmoderation.php:36 msgid "Enables or disables plugin to Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment." msgstr "启用或禁用该插件以便移除当新的待审核评论产生时的 \"您的评论正在等待审核。\" 提示。" #: plugins/awaitingmoderation.php:40 #: plugins/badbehaviour.php:71 #: plugins/domain-mapping.php:81 #: plugins/searchengine.php:75 #: plugins/wptouch.php:28 #: wp-cache.php:1769 #: wp-cache.php:1771 msgid "enabled" msgstr "已启用" #: plugins/awaitingmoderation.php:42 #: plugins/badbehaviour.php:73 #: plugins/domain-mapping.php:83 #: plugins/searchengine.php:77 #: plugins/wptouch.php:30 msgid "disabled" msgstr "已禁用" #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "Awaiting Moderation %s" #: plugins/awaitingmoderation.php:45 #: plugins/badbehaviour.php:76 #: plugins/domain-mapping.php:86 #: plugins/searchengine.php:80 #: plugins/wptouch.php:33 msgid "Update" msgstr "更新" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "没有找到 Bad Behavior 插件。请检查您的安装。" #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "Bad Behavior" #: plugins/badbehaviour.php:68 msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(仅支持传统模式，并且需要禁用压缩以及确保 Bad Behavior 插件在 \"%s/plugins/bad-behavior/\" 目录中) " #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "Bad Behavior 兼容%s" #: plugins/badbehaviour.php:83 #: wp-cache.php:1401 #: wp-cache.php:1406 msgid "Warning!" msgstr "警告!" #: plugins/domain-mapping.php:73 msgid "Domain Mapping" msgstr "Domain Mapping" #: plugins/domain-mapping.php:78 msgid "Provides support for Domain Mapping plugin to map multiple domains to a blog." msgstr "点击查看 Domain Mapping 插件对同主机多站点的支持。" #: plugins/domain-mapping.php:84 msgid "Domain Mapping support is now %s" msgstr "Domain Mapping 兼容%s" #: plugins/domain-mapping.php:98 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "已检测到 Domain Mapping 插件！请前往本插件的设置首页启用 Domain Mapping 插件支持。" #: plugins/multisite.php:13 msgid "Cached" msgstr "已缓存" #: plugins/multisite.php:31 #: wp-cache.php:1324 msgid "Enable" msgstr "启用" #: plugins/multisite.php:33 #: plugins/searchengine.php:61 #: wp-cache.php:1324 msgid "Disable" msgstr "禁用" #: plugins/multisite.php:39 msgid "Caching has been disabled on this blog on the Network Admin Sites page." msgstr "在该博客的站点网络管理页面上缓存功能已被禁用。" #: plugins/searchengine.php:67 msgid "No Adverts for Friends" msgstr "No Adverts for Friends" #: plugins/searchengine.php:72 msgid "Provides support for No Adverts for Friends." msgstr "点击查看 No Adverts for Friends 插件的支持。" #: plugins/searchengine.php:78 msgid "No Adverts for Friends support is now %s" msgstr "No Adverts for Friends 兼容%s" #: plugins/wptouch.php:20 msgid "WPTouch" msgstr "WPTouch" #: plugins/wptouch.php:25 msgid "Provides support for WPTouch mobile theme and plugin." msgstr "点击查看 WPTouch 的手机主题和插件本身的支持。" #: plugins/wptouch.php:31 msgid "WPTouch support is now %s" msgstr "WPTouch 兼容%s" #: plugins/wptouch.php:45 msgid "WPTouch plugin detected! Please go to the Supercache plugins page and enable the WPTouch helper plugin." msgstr "已检测到 WPTouch 插件！请前往插件设置首页启用 WPTouch 插件支持。" #: wp-cache-phase2.php:1209 msgid "Cache expiry cron job failed. Job will run again in 10 seconds." msgstr "清理到期缓存计划任务执行失败，将会在10秒后重试。" #: wp-cache-phase2.php:1213 msgid "Cache expiry cron job took more than 30 seconds. You should probably run the garbage collector more often." msgstr "缓存到期检查任务已经执行了不少于30秒。您可能需要更经常地运行垃圾回收期。" #: wp-cache-phase2.php:1222 msgid "[%1$s] WP Super Cache GC Report" msgstr "[%1$s] [%1$s] WP Super Cache 垃圾回收器报告" #: wp-cache.php:99 msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "请把 wp-super-cache/wp-cache-config-sample.php 改为 %s /wp-cache-config.php" #: wp-cache.php:162 msgid "Warning! PHP Safe Mode Enabled!" msgstr "警告！PHP 安全模式已启用！" #: wp-cache.php:163 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "由于启用了安全模式,在插件运行时您可能会遇到问题。" #: wp-cache.php:167 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "在 PHP 代码读取或者写入文件之前，您的服务器程序将会检查其属主。" #: wp-cache.php:168 msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "您或者管理员也许能通过修改插件的用户组属主为服务器软件用户来使得插件正常工作。%s/cache/ 目录的用户组属主同样需要修改。更多信息请访问 PHP 安全模式手册 页面。" #: wp-cache.php:170 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "您或者管理员必须禁用该功能。更多信息请访问 PHP 安全模式手册 。很遗憾这个操作不能在 .htaccess 文件中修改，您必须修改 php.ini 文件。" #: wp-cache.php:176 msgid "Permlink Structure Error" msgstr "固定链接结构出错" #: wp-cache.php:177 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "本插件需要正确的自定义链接或者固定链接结构才能正常工作。请前往 固定链接设置 页面进行配置。" #: wp-cache.php:189 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "警告！您的主机 \"%s\" 被解析至 %s" #: wp-cache.php:190 msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "您的服务器认为您的主机解析至 %s。有些服务比如垃圾回收器和定时发布功能将无法正常工作。" #: wp-cache.php:191 #: wp-cache.php:205 msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "请查看 readme.txt 中 疑难问题解决部分 的第16号问题" #: wp-cache.php:204 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "很遗憾，找不到 wp-cron.php。该文件是垃圾回收器正常工作，WordPress 定时发布任务以及其他活动的关键。" #: wp-cache.php:218 msgid "Cannot continue... fix previous problems and retry." msgstr "无法继续... 清修复之前遇到的问题然后重试。" #: wp-cache.php:227 msgid "Zlib Output Compression Enabled!" msgstr "Zlib 输出压缩已启用！" #: wp-cache.php:228 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP 正在压缩发送到来访者的数据。建议禁用该功能，因为本插件已经缓存了压缩后的输出数据而不是重复压缩多次它们。同时请查看 readme 文件的疑难问题解决部分的第21号问题。查看 这个页面 以了解配置 php.ini 的介绍。" #: wp-cache.php:232 msgid "Mod rewrite may not be installed!" msgstr "Mod rewrite 模块可能未安装！" #: wp-cache.php:233 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "貌似 mod_rewrite 模块尚未安装。也许情况并不是这样，尤其是当您不使用 Apache 作为服务器程序的时候。请检查 mod_rewrite 模块是否被加载。这对于 Super Cache 的静态文件的调用是必需的。不过您可以使用 PHP 缓存模式或者传统模式运行本插件。" #: wp-cache.php:239 msgid "Read Only Mode. Configuration cannot be changed." msgstr "只读模式。设置无法更改。" #: wp-cache.php:240 msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "WP Super Cache 的设置文件 %s/wp-cache-config.php 无法被变更。这个文件必须被设置为可被写入权限才能正常工作。" #: wp-cache.php:241 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "最简单的方法就是通过 ftp 客户端使用 CHMOD 命令临时修改文件权限。请确保文件全局可被写入，然后就可以了。" #: wp-cache.php:242 #: wp-cache.php:258 msgid "This page explains how to change file permissions." msgstr "这个页面 讲述了如何修改文件权限。" #: wp-cache.php:243 msgid "Writeable:" msgstr "可写的：" #: wp-cache.php:244 msgid "Readonly:" msgstr "只读：" #: wp-cache.php:256 msgid "Warning! %s is writeable!" msgstr "警告！ %s 可被写入！" #: wp-cache.php:257 msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "您应该通过 ftp 客户端或者以下命令更改 %s 的权限并确保它被严格限制：" #: wp-cache.php:267 msgid "Mobile rewrite rules detected" msgstr "检测到针对手机的重写规则" #: wp-cache.php:268 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "为了更好的访问体验，您应该启用 \"手机设备支持\" 或者删除 .htaccess. 文件中的手机重写规则。请查找 \"2.0\\ MMP|240x320\" 文本并删除它们。" #: wp-cache.php:268 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "这将不会影响电脑用户，但是手机用户将会访问未缓存的页面。" #: wp-cache.php:274 #: wp-cache.php:285 msgid "Rewrite rules must be updated" msgstr "重写规则必须被更新" #: wp-cache.php:275 #: wp-cache.php:286 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "插件需要的重写规则已被更改或者缺失。" #: wp-cache.php:276 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "若要对手机用户进行配置，需要额外添加规则到 .htaccess 文件中，或者您启用传统模式。这是您的选择(有些困难)：" #: wp-cache.php:277 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "设置插件为传统模式并且启用手机支持。" #: wp-cache.php:278 #: wp-cache.php:287 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "滚动查看高级选项卡，找到并点击 更新 Mod_Rewrite 规则 按钮。" #: wp-cache.php:279 msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "删除插件的 mod_rewrite 规则，它们是 %s.htaccess 文件中从 # BEGIN WPSuperCache 开始到 # END WPSuperCache 结束的代码块，随后请刷新本页来重建规则。" #: wp-cache.php:280 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "请自行添加规则。编辑 %s.htaccess 并找到从 # BEGIN WPSuperCache 开始到 # END WPSuperCache 结束的这部分代码。请注意有两部分很相似，请在 %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ 下方添加这些规则： (请执行该操作两次，每一部分一次)" #: wp-cache.php:293 msgid "Required to serve compressed supercache files properly." msgstr "这是必需的以便能够正确调用缓存文件。" #: wp-cache.php:293 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "该模块的作用是设定 supercache 页面的缓存信息。没有该模块，IE7用户将只会看见旧页面。" #: wp-cache.php:293 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "设定缓存文件的到期时间。没有该模块时，当来访者刷新或者留下评论时可能不会看到新页面。" #: wp-cache.php:300 msgid "Missing Apache Modules" msgstr "找不到 Apache 模块" #: wp-cache.php:301 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "由于下列 Apache 模块的缺失，本插件只能运行于传统模式。如果强制在完整的运行模式下运行，来访者可能会浏览异常的页面。" #: wp-cache.php:502 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "警告！您尝试启用压缩但是 zlib.output_compression 参数已被启用。请查看 readme 文件的疑难问题解决部分的第21号解答。" #: wp-cache.php:598 msgid "WP Super Cache Settings" msgstr "WP Super Cache 设置" #: wp-cache.php:612 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "注意：由于 Mod_rewrite 模式或者传统模式已启用，默认将显示高级设置选项卡。" #: wp-cache.php:623 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "设置文件已变更，有些数值可能是错误的。请通过 \"设置\" 菜单重新加载。" #: wp-cache.php:655 msgid "Caching must be enabled to use this feature" msgstr "这项功能必须在启用缓存功能后方可使用。" #: wp-cache.php:673 #: wp-cache.php:813 msgid "Cancel Cache Preload" msgstr "取消预加载缓存" #: wp-cache.php:681 msgid "Scheduled preloading of cache almost cancelled. It may take up to a minute for it to cancel completely." msgstr "预缓存计划任务马上就会被取消，这可能需要花费一点时间。" #: wp-cache.php:692 msgid "Scheduled preloading of cache cancelled." msgstr "预缓存计划任务已取消" #: wp-cache.php:724 #: wp-cache.php:811 msgid "Preload Cache Now" msgstr "立即预加载缓存" #: wp-cache.php:728 msgid "Scheduled preloading of cache in 10 seconds." msgstr "预缓存任务在10秒后启动。" #: wp-cache.php:733 msgid "Scheduled preloading of cache in %d minutes" msgstr "预缓存任务在%d秒后启动。" #: wp-cache.php:737 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "预缓存的功能是缓存所有已发布的页面和文章。它会创建 supercache 静态文件，这样的话，未知用户(包括搜索引擎蜘蛛)将会获得缓存后的页面。这将帮助您的站点的 Google PR 提升，因为 Google 会把网站的响应速度作为评判网站的标准。" #: wp-cache.php:738 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "预缓存将会创建大量新文件，并且会将所有文章进行缓存。如果您有10000篇以上文章，不建议您使用该功能，尤其是在共享主机上。" #: wp-cache.php:739 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "在预缓存模式下，垃圾回收器将只会对已知用户清理传统模式产生的旧文件，而不是预缓存的 supercache 文件。当缓存被预缓存时，本功能建议启用。" #: wp-cache.php:743 msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "每%s分钟刷新预缓存文件(设置为0则禁用，至少%d分钟。)" #: wp-cache.php:756 msgid "all" msgstr "全部" #: wp-cache.php:769 msgid "Preload %s posts." msgstr "预缓存 %s 篇文章。" #: wp-cache.php:776 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "预缓存模式(垃圾回收器只会在传统模式上生效。推荐。)" #: wp-cache.php:779 msgid "Preload tags, categories and other taxonomies." msgstr "预缓存标签，分类以及其他。" #: wp-cache.php:782 msgid "Send me status emails when files are refreshed." msgstr "当缓存文件刷新完毕后发送邮件通知。" #: wp-cache.php:787 msgid "Many emails, 2 emails per 100 posts." msgstr "大量邮件，每100篇文章发送2封邮件。" #: wp-cache.php:790 msgid "Medium, 1 email per 100 posts." msgstr "适量邮件，每100篇文章发送1封邮件。" #: wp-cache.php:793 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "少量邮件，缓存第一篇发送1封邮件，缓存结束时发送再1封邮件。" #: wp-cache.php:797 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "缓存将会在 %d小时%d分%d秒后刷新。" #: wp-cache.php:798 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "缓存全部刷新将会在%d小时%d分%d秒后开始。" #: wp-cache.php:804 msgid "Currently caching from post %d to %d." msgstr "正在缓存文章 %d 到文章 %d。" #: wp-cache.php:808 msgid "Page last cached: %s" msgstr "页面最后缓存： %s" #: wp-cache.php:811 msgid "Update Settings" msgstr "更新设置" #: wp-cache.php:819 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "预缓存功能已禁用。请禁用传统模式或者与您的主机管理员联系。" #: wp-cache.php:836 #: wp-cache.php:947 msgid "Caching" msgstr "缓存功能" #: wp-cache.php:840 msgid "Cache hits to this website for quick access." msgstr "启用缓存以便加快访问。" #: wp-cache.php:840 #: wp-cache.php:841 #: wp-cache.php:858 #: wp-cache.php:867 #: wp-cache.php:874 #: wp-cache.php:877 #: wp-cache.php:894 #: wp-cache.php:950 msgid "Recommended" msgstr "推荐" #: wp-cache.php:841 msgid "Use mod_rewrite to serve cache files." msgstr "mod_rewrite 缓存模式。" #: wp-cache.php:842 msgid "Use PHP to serve cache files." msgstr "PHP 缓存模式。" #: wp-cache.php:843 msgid "Legacy page caching." msgstr "传统缓存模式。" #: wp-cache.php:844 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching." msgstr "Mod_rewrite 方式最快；PHP 方式几乎与前者一样快并且容易部署；传统模式比它们稍慢，但是更灵活且部署简单。建议新用户使用 PHP 缓存模式。" #: wp-cache.php:850 msgid "Miscellaneous" msgstr "杂项" #: wp-cache.php:856 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "警告！由于未找到 gzencode() 函数，压缩已被禁用。" #: wp-cache.php:858 msgid "Compress pages so they’re served more quickly to visitors." msgstr "压缩页面以便让来访者更快浏览。" #: wp-cache.php:859 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "压缩默认已禁用，因为有些主机对压缩过的文件处理有问题。勾选或取消勾选该功能会清除缓存。" #: wp-cache.php:867 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Not Modified 浏览器缓存。声明一个页面自从上一次被请求后还未被变更。" #: wp-cache.php:870 msgid "Warning! 304 browser caching is only supported when not using mod_rewrite caching." msgstr "警告！304浏览器缓存功能只有不使用 mod_rewrite 缓存模式时生效。" #: wp-cache.php:872 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "304支持默认已禁用，因为 GoDaddy 对有些网页头部处理有问题。" #: wp-cache.php:874 msgid "Don’t cache pages for known users." msgstr "不要为已知用户缓存。" #: wp-cache.php:875 msgid "Don’t cache pages with GET parameters. (?x=y at the end of a url)" msgstr "不要为 GET 请求缓存。(地址结尾为?x=y)" #: wp-cache.php:876 msgid "Make known users anonymous so they’re served supercached static files." msgstr "让已知用户匿名使他们浏览的内容是缓存文件。" #: wp-cache.php:877 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "缓存重建。当新缓存生成时调用缓存文件给匿名用户。" #: wp-cache.php:878 msgid "Proudly tell the world your server is Stephen Fry proof! (places a message in your blog’s footer)" msgstr "自豪地告诉世界Stephen Fry proof！(在您的博客底部显示一行感谢作者信息)" #: wp-cache.php:884 #: wp-cache.php:1162 #: wp-cache.php:1778 msgid "Advanced" msgstr "高级" #: wp-cache.php:888 msgid "Mobile device support. (External plugin or theme required. See the FAQ for further details.)" msgstr "移动设备支持。(需要第三方插件或主题，请访问 FAQ 页面以了解更多信息。)" #: wp-cache.php:890 msgid "Mobile Browsers" msgstr "手机浏览器" #: wp-cache.php:890 msgid "Mobile Prefixes" msgstr "手机号段" #: wp-cache.php:892 msgid "Remove UTF8/blog charset support from .htaccess file. Only necessary if you see odd characters or punctuation looks incorrect. Requires rewrite rules update." msgstr "移除 .htaccess 文件中的 UTF8/blog 字符集。这个功能只适用于当您发现文件中字符不正确时。本功能需要更新重写规则。" #: wp-cache.php:893 msgid "Clear all cache files when a post or page is published or updated." msgstr "当有新文章或页面的发布或更新时清除之前的缓存文件。" #: wp-cache.php:894 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "首页额外检查。 (极少数情况下会停止对首页的缓存)" #: wp-cache.php:895 msgid "Only refresh current page when comments made." msgstr "当某页面有新评论时，只刷新该页面的缓存。" #: wp-cache.php:896 msgid "List the newest cached pages on this page." msgstr "在该页列出所有最新的缓存页面。" #: wp-cache.php:898 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "粗略文件锁定。您可能不需要该功能，但是它对小型站点很有帮助。警告！某些情况下您的服务器会被锁住！" #: wp-cache.php:900 msgid "Late init. Display cached files after WordPress has loaded. Most useful in legacy mode." msgstr "延迟初始化。该功能是指在 WordPress 加载后显示已缓存的文件。在传统模式下很有用。" #: wp-cache.php:902 msgid "Use object cache to store cached files." msgstr "使用对象缓存系统来存储缓存文件。" #: wp-cache.php:902 msgid "(Experimental)" msgstr "(实验室功能)" #: wp-cache.php:904 msgid "DO NOT CACHE PAGE secret key: %s" msgstr "访问这个链接将不会显示缓存内容： %s" #: wp-cache.php:910 msgid "Note:" msgstr "提示：" #: wp-cache.php:912 msgid "Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided." msgstr "请前往插件管理页面卸载本插件，插件会自动清除。如果需要您的手动操作，稍后会有提示。" #: wp-cache.php:913 msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "如果要卸载该插件，请确保 %s 目录可被服务器程序写入，这样的话 advanced-cache.php 和 cache-config.php 可被自动删除。(当然也请确保这两个文件可被写入！)" #: wp-cache.php:914 msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "请查看 readme.txt 以了解卸载流程。请在文件中搜索 \"How to uninstall WP Super Cache\"以便快速浏览。" #: wp-cache.php:915 msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "需要帮助？请查看 Super Cache 的 readme 文件。它包含了安装文档，常见问题解答以及某些故障排除提示。还有建议您查看论坛支持，您的问题也许已经被解答过了。" #: wp-cache.php:918 #: wp-cache.php:965 msgid "Update Status" msgstr "更新" #: wp-cache.php:925 msgid "Accepted Filenames & Rejected URIs" msgstr "已被接受的文件名和拒绝的 URI" #: wp-cache.php:950 msgid "Caching On" msgstr "启用缓存功能" #: wp-cache.php:951 msgid "Caching Off" msgstr "禁用缓存功能" #: wp-cache.php:952 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "提示：将会启用 PHP 缓存模式，缓存重建和手机支持" #: wp-cache.php:962 msgid "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "注意：PHP 缓存模式已启用，但是检测到遗留的 mod_rewrite 规则。已缓存的文件将会被这些规则调用。如果您的站点运行正常，请忽略本提示，否则请自行编辑 .htaccess 文件。" #: wp-cache.php:967 msgid "Cache Tester" msgstr "缓存测试" #: wp-cache.php:968 msgid "Test your cached website by clicking the test button below." msgstr "点击下面的测试按钮测试缓存效果。" #: wp-cache.php:974 msgid "Fetching %s to prime cache: " msgstr "正在抓取 %s 的初始缓存：" #: wp-cache.php:976 #: wp-cache.php:985 #: wp-cache.php:997 msgid "OK" msgstr "OK" #: wp-cache.php:979 msgid "Fetching first copy of %s: " msgstr "抓取 %s 的第一份缓存拷贝：" #: wp-cache.php:988 #: wp-cache.php:999 msgid "FAILED" msgstr "失败" #: wp-cache.php:991 msgid "Fetching second copy of %s: " msgstr "抓取 %s 的第二份缓存拷贝：" #: wp-cache.php:1003 msgid "One or more page requests failed:" msgstr "1个或多个页面的请求失败：" #: wp-cache.php:1022 #: wp-cache.php:1023 msgid "Page %d: %d (%s)" msgstr "页面 %d: %d (%s)" #: wp-cache.php:1029 msgid "Page 1: %s" msgstr "第一页： %s" #: wp-cache.php:1030 msgid "Page 2: %s" msgstr "第二页： %s" #: wp-cache.php:1031 msgid "The timestamps on both pages match!" msgstr "两个页面的时间戳相符！" #: wp-cache.php:1033 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "页面不相符！时间戳有差异或者不存在！" #: wp-cache.php:1034 msgid "Things you can do:" msgstr "您可以做的：" #: wp-cache.php:1035 msgid "Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match." msgstr "它会在一个已经登出的浏览器环境中加载首页并检查 html 文件结尾的时间戳，然后再次加载页面并对比时间戳。如果时间戳相符则缓存正在工作。" #: wp-cache.php:1036 msgid "Enable logging on the Debug page here. That should help you track down the problem." msgstr "在这里启用调试页面的日志记录。这会帮助您跟踪问题。" #: wp-cache.php:1037 msgid "You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself." msgstr "您应该在出错前检查页面1和页面2。您的本地服务器设置可能不允许您的网站读取。" #: wp-cache.php:1045 msgid "Send non-secure (non https) request for homepage" msgstr "发送不安全的(非 https) 首页请求" #: wp-cache.php:1046 msgid "Test Cache" msgstr "测试缓存" #: wp-cache.php:1050 msgid "Delete Cached Pages" msgstr "删除已缓存页面" #: wp-cache.php:1051 msgid "Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below." msgstr "已缓存的页面以 html 页面或者 PHP 文件的形式存储在您的服务器上。如果您需要删除它们，请使用下方按钮来完成。" #: wp-cache.php:1054 #: wp-cache.php:2316 #: wp-cache.php:2335 #: wp-cache.php:2506 #: wp-cache.php:3030 msgid "Delete Cache" msgstr "删除缓存" #: wp-cache.php:1061 #: wp-cache.php:2322 msgid "Delete Cache On All Blogs" msgstr "删除所有博客上的缓存" #: wp-cache.php:1066 msgid "Recommended Links and Plugins" msgstr "有用的链接和插件" #: wp-cache.php:1067 msgid "Caching is only one part of making a website faster. Here are some other plugins that will help:" msgstr "缓存只是让站点运行更快的一种方法，这里有一些其它插件提供类似功能：" #: wp-cache.php:1068 msgid "WPSCMin, a Supercache plugin that minifies cached pages by removing whitespaces and extra characters " msgstr "WPSCMin，一个可以通过移除空白部分和不必要的字符来缩小缓存页面大小的 Supercache 插件" #: wp-cache.php:1069 msgid "Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix." msgstr "Yahoo! Yslow 是一款火狐浏览器扩展 Firebug 的插件。它会通过一组高性能网页来分析网页的表现并给您改善网页的建议。您也可以在线使用表现检查工具 GTMetrix。" #: wp-cache.php:1070 msgid "Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score." msgstr "使用 Google Libraries 允许您从 Google 的服务器加载某些流行 Javascript 库。不过这很荒谬，会降低您的 Yslow 评估分数。" #: wp-cache.php:1072 msgid "Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules." msgstr "只允许高级用户： Speed up your site with Caching and cache-control 讲述了如何使您的网站通过 .htaccess 规则更容易被缓存。" #: wp-cache.php:1073 msgid "Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others." msgstr "只允许高级用户： 安装对象缓存系统。您可以选择 Memcached， XCache， eAcccelerator 或更多。" #: wp-cache.php:1074 msgid "Cron View is a useful plugin to use when trying to debug garbage collection and preload problems." msgstr "Cron View 是一款调试垃圾回收器和预缓存问题的利器。" #: wp-cache.php:1085 msgid "Make WordPress Faster" msgstr "让 WordPress 更快" #: wp-cache.php:1086 msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s 由 %2$s 与众多贡献人员一同开发并维护。" #: wp-cache.php:1087 msgid "He blogs at %1$s and posts photos at %2$s." msgstr "他有一个博客 %1$s 并会把自己的照片放在 %2$s。" #: wp-cache.php:1088 msgid "Please say hi to him on %s too!" msgstr "欢迎您在 %s 上与他交流！" #: wp-cache.php:1089 msgid "Need Help?" msgstr "需要帮助？" #: wp-cache.php:1091 msgid "Use the debug system in the Debug tab above. It will tell you what the plugin is doing." msgstr "在调试选项卡中使用调试工具。这将会告诉您插件正在如何工作。" #: wp-cache.php:1092 msgid "Installation Help" msgstr "安装帮助" #: wp-cache.php:1093 msgid "Frequently Asked Questions" msgstr "常见问题解答" #: wp-cache.php:1094 msgid "Support Forum" msgstr "论坛支持" #: wp-cache.php:1096 msgid "Rate This Plugin!" msgstr "给插件评个分吧！" #: wp-cache.php:1097 msgid "Please rate this plugin and tell me if it works for you or not. It really helps development." msgstr "请 对这个插件评分 并告诉我您的需求。这对我们的开发真的十分有用。" #: wp-cache.php:1106 msgid "Cached pages since %1$s : %2$s" msgstr "从 %1$s 已缓存的页面：%2$s" #: wp-cache.php:1107 msgid "Newest Cached Pages:" msgstr "最新的已缓存页面：" #: wp-cache.php:1111 msgid "Cached %s seconds ago" msgstr "%s秒前已缓存" #: wp-cache.php:1114 msgid "(may not always be accurate on busy sites)" msgstr "(在某些繁忙的大型站点上可能会不准确)" #: wp-cache.php:1133 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "这些对第三方插件的兼容本质都是位于 wp-super-cache 目录内 plugins 子目录内的 PHP 文件，它们在 Supercache 运行时即被加载，比这些第三方插件本身被加载稍微提前。" #: wp-cache.php:1134 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "严格意义上讲这是一个高级功能，您必须十分了解 PHP 和 WordPress 才能正确使用。" #: wp-cache.php:1135 msgid "Warning! Due to the way WordPress upgrades plugins the plugins you upload to wp-super-cache/plugins/ will be deleted when you upgrade WP Super Cache. You can avoid this by loading the plugins from elsewhere. Set $wp_cache_plugins_dir to the new location in wp-config.php and WP Super Cache will look there instead.
    More info available in the developer documentation." msgstr "警告！由于 WordPress 升级插件的方法，您之前上传至 wp-super-cache/plugins/ 的插件将会在更新时被删除。您可以通过在其他地方加载的方式避免，即设置 wp-config.php 中的 $wp_cache_plugins_dir 路径，这样 WP Super Cache 就会从这里加载。
    更多信息请查阅 开发者文档。" #: wp-cache.php:1145 msgid "Available Plugins" msgstr "可用插件" #: wp-cache.php:1162 msgid "Easy" msgstr "通用" #: wp-cache.php:1162 msgid "CDN" msgstr "CDN" #: wp-cache.php:1162 msgid "Contents" msgstr "内容" #: wp-cache.php:1162 msgid "Preload" msgstr "预缓存" #: wp-cache.php:1162 msgid "Plugins" msgstr "插件兼容" #: wp-cache.php:1162 msgid "Debug" msgstr "调试" #: wp-cache.php:1197 msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "注意：除非运行在 主站点，WP Super Cache 的 mod_rewrite 规则检查功能将被禁用 。" #: wp-cache.php:1206 msgid "Mod Rewrite Rules" msgstr "Mod Rewrite 规则" #: wp-cache.php:1212 msgid "WordPress MU Detected" msgstr "已检测到 WordPress 多站点模式" #: wp-cache.php:1212 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "很遗憾，在 WordPress 多站点模式下无法自动更新重写规则。请打开您的 .htaccess 文件并在其最上方手动添加下列 mod_rewrite 规则。" #: wp-cache.php:1214 msgid "Mod Rewrite rules cannot be updated!" msgstr "无法更新 Mod Rewrite 规则！" #: wp-cache.php:1215 msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "您必须确定在 %s.htaccess 文件中，有BEGIN 和 END 标记以便程序能够自动更新规则。比如：" #: wp-cache.php:1217 msgid "Refresh this page when you have updated your .htaccess file." msgstr "当您更新完您的 .htaccess 文件时，请刷新本页。" #: wp-cache.php:1221 msgid "Thank you for upgrading." msgstr "感谢您的升级。" #: wp-cache.php:1221 msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "自从您上次安装本插件后，mod_rewrite 规则已变更。非常抱歉，您必须在新规则更新前移除旧版本 supercache 的规则。在您编辑完成 .htaccess 文件后请刷新本页。如果您想要手动升级，修改一下几行: %1$s 比方说是这样： %2$s 其实所有修改都是将 \"HTTP_COOKIE\" 变为 \"HTTP:Cookie\" 以及将 \"wordpressuser\" 变为 \"wordpress\"。这是 WordPress 2.5 的变化，但是它理论上和旧版本兼容。(如果您愿意尝试的话)" #: wp-cache.php:1225 msgid "Trailing slash check required." msgstr "需要结尾的斜杠检查。" #: wp-cache.php:1225 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "貌似您博客的地址结尾有 \"/\"。很遗憾，自从您安装本插件时，一个内容重复故障就已经被发现。地址结尾包含 \"/\" 和不包含 \"/\" 的页面都显示相同的内容，但没有跳转到正确的地址。要想修复该问题，您需要自行编辑您的 .htaccess 文件并把下面两条规则添加至两组 Super Cache 规则中：" #: wp-cache.php:1227 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "您可以查看规则时如何生效的并且点击 \"View mod_rewrite rules\" 链接来测试下方的所有规则。" #: wp-cache.php:1241 msgid "Mod Rewrite rules updated!" msgstr "Mod Rewrite 规则已更新！" #: wp-cache.php:1242 msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "%s.htaccess 已经被必需的 mod_rewrite 规则更新。请检查它们是否正确。它们应该看上去这样：" #: wp-cache.php:1244 msgid "Mod Rewrite rules must be updated!" msgstr "Mod Rewrite 规则必须被更新！" #: wp-cache.php:1245 msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "您的服务器的 %s.htaccess 文件不可被服务器程序写入，但是它需要正确的 mod_rewrite 规则：" #: wp-cache.php:1250 msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "WP Super Cache 的 mod rewrite 规则已存在于您的 %s.htaccess 文件中。
    点击下面链接查看新添加进去的内容。如果您已经升级了本插件，确保这些规则符合。" #: wp-cache.php:1253 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "您服务器上的 .htaccess 文件和插件存在不同的重写规则。也许这不重要，但是您应该尽快对比一下。点击’更新 Mod_Rewrite 规则’ 按钮更新这些规则。" #: wp-cache.php:1255 msgid "View Mod_Rewrite Rules" msgstr "查看 Mod_Rewrite 规则" #: wp-cache.php:1261 #: wp-cache.php:2622 msgid "Rules must be added to %s too:" msgstr "规则必须也被添加至 %s ：" #: wp-cache.php:1268 msgid "Gzip encoding rules in %s.htaccess created." msgstr "Gzip 编码规则已经添加至 %s.htaccess 文件。" #: wp-cache.php:1275 msgid "Fix Configuration" msgstr "修复设置" #: wp-cache.php:1278 msgid "Restore Default Configuration" msgstr "恢复默认设置" #: wp-cache.php:1286 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "评论审核已启用。您的评论可能需要一段时间后才能被显示。" #: wp-cache.php:1311 msgid "Lock Down:" msgstr "锁定：" #: wp-cache.php:1312 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "如果您启用锁定，那么它将会为站点运行高峰时期做好准备。当这项功能启用时，新评论或文章将不会立即刷新至已缓存的静态文件。" #: wp-cache.php:1313 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "对开发者：为了使您自己的插件与锁定功能兼容，请检查 \"WPLOCKDOWN\" 常量。以下代码将会确保您的插件遵守 WPLOCKDOWN 设置。" #: wp-cache.php:1315 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "抱歉，本博客目前处于锁定中，稍后会进行更新。" #: wp-cache.php:1319 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress 已被锁定。当产生新评论时，Super Cache 的静态文件将不会被检测到。" #: wp-cache.php:1321 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress 没有被锁定。新的评论将会像往常一样刷新 Super Cache 的静态文件。" #: wp-cache.php:1327 msgid "Lock Down" msgstr "锁定" #: wp-cache.php:1335 msgid "Directly Cached Files" msgstr "直接缓存的文件" #: wp-cache.php:1393 msgid "%s removed!" msgstr "%s 已移除！" #: wp-cache.php:1401 msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "您必须将 %s 设置为可被写入才能使用此功能。由于该功能存在安全风险，请在页面生成后设置为只读权限。" #: wp-cache.php:1406 msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s 可被写入。由于存在安全风险，请在页面生成后设置为只读权限。" #: wp-cache.php:1421 msgid "Existing direct page" msgstr "已存在的跳转页面" #: wp-cache.php:1421 msgid "Delete cached file" msgstr "删除已缓存文件" #: wp-cache.php:1426 msgid "Add direct page:" msgstr "添加跳转页面：" #: wp-cache.php:1428 msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "" #: wp-cache.php:1430 msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "例如：为了缓存 %1$sabout/，您需要访问 %1$sabout/ 或 /about/。缓存文件将会在下次匿名用户来访时再次生成。" #: wp-cache.php:1431 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "如果文本框留空，将会移除直接页面列表中内容的并删除缓存文件。" #: wp-cache.php:1436 msgid "Update Direct Pages" msgstr "更新直接链接页面" #: wp-cache.php:1464 msgctxt "timezone date format" msgid "Y-m-d G:i:s" msgstr "Y-m-d G:i:s" #: wp-cache.php:1523 msgid "Expiry Time & Garbage Collection" msgstr "到期时间和垃圾回收器" #: wp-cache.php:1525 msgid "UTC time is %s" msgstr "UTC时间是%s" #: wp-cache.php:1528 msgid "Local time is %1$s" msgstr "本地时间是 %1$s" #: wp-cache.php:1532 msgid "Next scheduled garbage collection will be at %s UTC" msgstr "下次垃圾收集计划任务将会在 %s UTC 开始" #: wp-cache.php:1536 msgid "Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age." msgstr "警告！预缓存模式 已激活！Supercache 的缓存文件由于缓存的有效时间而不会被删除。" #: wp-cache.php:1553 msgid "Cache Timeout" msgstr "缓存超时时间" #: wp-cache.php:1554 #: wp-cache.php:1557 msgid "seconds" msgstr "秒" #: wp-cache.php:1555 msgid "How long should cached pages remain fresh? Set to 0 to disable garbage collection. A good starting point is 3600 seconds." msgstr "哪些缓存页面是没有过期的？设置为0可以禁用垃圾回收器。建议数值为3600。" #: wp-cache.php:1556 msgid "Scheduler" msgstr "计划" #: wp-cache.php:1556 msgid "Timer:" msgstr "定时器:" #: wp-cache.php:1557 msgid "Check for stale cached files every interval seconds." msgstr "每隔 interval 秒定期检查过期的缓存文件。" #: wp-cache.php:1558 msgid "Clock:" msgstr "时间：" #: wp-cache.php:1559 msgid "HH:MM" msgstr "小时:分钟" #: wp-cache.php:1559 msgid "Check for stale cached files at this time (UTC) or starting at this time every interval below." msgstr "每当到了您设定的 (UTC) 时间或者任务间隔检查过期的缓存文件。" #: wp-cache.php:1561 msgid "Interval:" msgstr "任务间隔：" #: wp-cache.php:1567 msgid "Notification Emails" msgstr "邮件通知" #: wp-cache.php:1568 msgid "Email me when the garbage collection runs." msgstr "当垃圾回收器运行时发送邮件通知我。" #: wp-cache.php:1570 msgid "Garbage Collection" msgstr "垃圾回收器" #: wp-cache.php:1571 msgid "Garbage collection is the simple act of throwing out your garbage. For this plugin that would be old or stale cached files that may be out of date. New cached files are described as fresh." msgstr "垃圾回收器 是一个减少垃圾的工具。因为插件产生的缓存会随着时间推移而过期，因此新生成的缓存文件因此是新鲜的。" #: wp-cache.php:1572 msgid "Cached files are fresh for a limited length of time. You can set that time in the Cache Timeout text box on this page." msgstr "缓存都是有一定的新鲜时间的，您可以在本页的 缓存过期时间 文本框进行设置。" #: wp-cache.php:1573 msgid "Stale cached files are not removed as soon as they become stale. They have to be removed by the garbage collecter. That is why you have to tell the plugin when the garbage collector should run." msgstr "过期的缓存文件并会被立刻删除。它们会被垃圾回收器清除。这就是您需要对垃圾回收器进行配置的原因。" #: wp-cache.php:1574 msgid "Use the Timer or Clock schedulers to define when the garbage collector should run." msgstr "使用 定时器 或 时钟 选项来设定垃圾回收器何时应该运行。" #: wp-cache.php:1575 msgid "The Timer scheduler tells the plugin to run the garbage collector at regular intervals. When one garbage collection is done, the next run is scheduled." msgstr "定时器 告诉插件间隔多久运行垃圾回收器。当一次回收完毕时，下次任务将会被设计划。" #: wp-cache.php:1576 msgid "Or, the Clock scheduler allows the garbage collection to run at specific times. If set to run hourly or twicedaily the garbage collector will be first scheduled for the time you enter here. It will then run again at the indicated interval. If set to run daily it will run once a day at the time specified." msgstr "或者，时钟允许垃圾回收器在特定时间时运行。如果您设置时间间隔为每小时或者一天两次，垃圾回收器将会按照您输入的设定运行。然后它将会按照已指定的时间间隔再次运行。如果设置为每天，它将会在每天特定时间运行，且一天内只有这一次。" #: wp-cache.php:1578 msgid "There are no best garbage collection settings but here are a few scenarios. Garbage collection is separate to other actions that clear our cached files like leaving a comment or publishing a post." msgstr "没有十分完美的垃圾回收器设置，不过它已被单独分离出来，这样清理缓存文件就像留下一条评论或者发布文章一样简单。" #: wp-cache.php:1580 msgid "Sites that want to serve lots of newly generated data should set the Cache Timeout to 60 and use the Timer scheduler set to 90 seconds." msgstr "有大量新数据产生的站点应该设置缓存超时时间为60并设置定时器时间为90秒。" #: wp-cache.php:1581 msgid "Sites with widgets and rss feeds in their sidebar should probably use a timeout of 3600 seconds and set the timer to 600 seconds. Stale files will be caught within 10 minutes of going stale." msgstr "在侧边栏有挂件和 rss 输出的站点应该设置超时时间为3600秒，并设置定时器为600秒。过期缓存将会在10分钟内随时被收集。" #: wp-cache.php:1582 msgid "Sites with lots of static content, no widgets or rss feeds in their sidebar can use a timeout of 86400 seconds or even more and set the timer to something equally long." msgstr "有大量静态内容且在侧边栏没有挂件和 rss 输出的站点，应该设置超时时间为86400秒或更长并设置定时器为一个很长的时间。" #: wp-cache.php:1583 msgid "Sites where an external data source updates at a particular time every day should set the timeout to 86400 seconds and use the Clock scheduler set appropriately." msgstr "每天有固定更新产生的站点应该设缓存超时时间为86400秒并正确设置时钟时间。" #: wp-cache.php:1585 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 600 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "检查并删除过期文件的确是一件很难做的事情，但是留着这些文件同样也是不必要的。在一个十分繁忙的站点上您应该设置到期时间为600秒。一天内可以在不同的时候设置不同的数值，访问本页来看看剩下多少到期的文件。如果您使用传统模式进行缓存，如果有可能的话，尽量保持500个以下文件。如果想缓存更多文件，请选择 PHP 模式或者 mod_rewrite 模式进行缓存。" #: wp-cache.php:1586 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "设置到期时间为0秒以便禁用垃圾回收器。" #: wp-cache.php:1587 msgid "Change Expiration" msgstr "修改过期设置" #: wp-cache.php:1631 msgid "Rejected User Agents" msgstr "已拒绝的用户代理(User Agent)" #: wp-cache.php:1632 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "" #: wp-cache.php:1639 msgid "Save UA Strings" msgstr "保存用户代理(UA)字段" #: wp-cache.php:1662 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "不要缓存例如下列格式的页面。请见 Conditional Tags 文档查看所有格式的具体说明。" #: wp-cache.php:1665 msgid "Single Posts" msgstr "单一文章" #: wp-cache.php:1666 msgid "Pages" msgstr "页面" #: wp-cache.php:1667 msgid "Front Page" msgstr "首页" #: wp-cache.php:1668 msgid "Home" msgstr "主页" #: wp-cache.php:1669 msgid "Archives" msgstr "存档" #: wp-cache.php:1670 msgid "Tags" msgstr "标签" #: wp-cache.php:1671 msgid "Category" msgstr "分类" #: wp-cache.php:1672 msgid "Feeds" msgstr "Feeds" #: wp-cache.php:1673 msgid "Search Pages" msgstr "搜索页面" #: wp-cache.php:1674 msgid "Author Pages" msgstr "作者页面" #: wp-cache.php:1676 #: wp-cache.php:1788 msgid "Save" msgstr "保存" #: wp-cache.php:1693 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "在这里添加强制禁止缓存的页面的地址关键字。例如，如果您的地址包含年份并且您不想缓存上一年的文章，您可以直接填写 ’/2004/’。WP-Cache 将会搜索所有符合条件的页面并且不缓存它们。" #: wp-cache.php:1699 msgid "Save Strings" msgstr "保存" #: wp-cache.php:1715 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "添加想要被缓存的文件名，即使它们出现在上面的被拒绝列表里面。" #: wp-cache.php:1721 msgid "Save Files" msgstr "保存文件" #: wp-cache.php:1762 msgid "Currently logging to: %s" msgstr "当前登录至：%s" #: wp-cache.php:1765 msgid "Fix problems with the plugin by debugging it here. It can log them to a file in your cache directory." msgstr "通过在这里调试来修复故障，调试功能会在缓存文件目录下生成日志。" #: wp-cache.php:1769 msgid "Debugging" msgstr "调试中" #: wp-cache.php:1770 msgid "IP Address" msgstr "IP 地址" #: wp-cache.php:1770 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(仅记录来自该 IP 的请求，您的 IP 是 %s)" #: wp-cache.php:1771 msgid "Cache Status Messages" msgstr "缓存状态消息" #: wp-cache.php:1772 msgid "Display comments at the end of every page like this:" msgstr "像这样的方式显示每页末尾的评论：" #: wp-cache.php:1778 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "在某些情况下，有以下2个问题可能会发生：
    1. 加载首页时会变成 zip 档案下载。
    2. 如果您的博客使用静态首页，并且固定链接结构类似于 /%category%/%postname%/ ，某些错误的页面会被当做首页进行缓存。
    " #: wp-cache.php:1779 msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "我有 99% 的把握：这不是 WP Super Cache 的 Bug，这种情况只会在极其罕见的情况下发生。如果您仍然不放心，我建议您每5分钟做一次对站点的简单检查，以便验证站点是否运行正常。如果产生任何问题，您会收到系统发送的邮件通知。" #: wp-cache.php:1781 msgid "Check front page every 5 minutes." msgstr "每5分钟检查一次首页。" #: wp-cache.php:1782 msgid "Front page text" msgstr "首页文字" #: wp-cache.php:1782 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "这是您将要在首页寻找的文字。如果您找不到，缓存将会被清除。留空则禁用该功能。" #: wp-cache.php:1783 msgid "Clear cache on error." msgstr "即使出错也清除缓存。" #: wp-cache.php:1784 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "当有检查时发送邮件提醒站点管理员。(对测试十分有用)" #: wp-cache.php:1798 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "错误：GZIP 压缩已启用，如果您想启用 wp-cache 请禁用 gzip 压缩。" #: wp-cache.php:1845 #: wp-cache.php:1986 #: wp-cache.php:2022 msgid "Warning" msgstr "警告" #: wp-cache.php:1845 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "WordPress 已启用 GZIP 压缩，wp-cache 将会自动忽略直到您禁用 gzip 压缩。" #: wp-cache.php:1907 #: wp-cache.php:1912 #: wp-cache.php:1945 #: wp-cache.php:1950 #: wp-cache.php:1956 msgid "Error" msgstr "错误" #: wp-cache.php:1907 msgid "Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions." msgstr "您的缓存目录 (%1$s) 不存在且 Web 服务器无法创建。请检查 %1$s 的权限设置。" #: wp-cache.php:1912 msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "您的缓存目录 (%1$s) 或者 %2$s需要被设置为可写入权限。请检查有关设置。" #: wp-cache.php:1945 msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "您的 WP-Cache 设置文件(%s) 已过期且不可被 Web 服务器读取。请删除该文件并刷新本页。" #: wp-cache.php:1950 msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." #: wp-cache.php:1956 msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Sample WP-Cache 设置文件(%s) 不存在。请检查您的安装。" #: wp-cache.php:1986 msgid "Could not update %s! WPCACHEHOME must be set in config file." msgstr "无法更新 %s！必须设置 WPCACHEHOME。" #: wp-cache.php:2022 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php 不存在或者不可被更新。" #: wp-cache.php:2023 msgid "1. If it already exists please delete the file first." msgstr "1. 如果文件已经存在请先删除它们。" #: wp-cache.php:2024 msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. 将 %1$s 通过 chmod 或者 ftp 客户端设置为可被写入(chmod 777 %1$s) 并刷新本页。这只是一个临时的操作，您需要随后恢复该文件之前的只读权限。(将之前括号内的777改为755，并执行修改后的命令)" #: wp-cache.php:2025 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. 刷新本页以便更新 %s/advanced-cache.php" #: wp-cache.php:2026 msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "如果不能工作，请确保文件 %s/advanced-cache.php 不存在：" #: wp-cache.php:2027 msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. 用文本编辑器打开 %1$s$wp_cache_file 。
  • 2. 修改从 CACHEHOME 到 %2$s 的文字
  • 3. 保存并把文件复制到 %3$s 然后刷新本页。
    • " #: wp-cache.php:2050 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "" #: wp-cache.php:2052 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "错误：您的 wp-config.php 文件中 WP_CACHE 未被启用 并且插件无法变更。" #: wp-cache.php:2053 msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "编辑 %s 并添加如下内容：
    define('WP_CACHE', true);
    WP-Cache 将不会被执行    。" #: wp-cache.php:2057 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the Troubleshooting Guide. The WP_CACHE line must be moved up." msgstr "" #: wp-cache.php:2085 msgid "Cache Contents" msgstr "缓存内容" #: wp-cache.php:2088 msgid "Object cache in use. No cache listing available." msgstr "对象缓存正处于使用中。没有缓存列表可用。" #: wp-cache.php:2112 msgid "Deleting supercache file: %s
    " msgstr "正在删除 supercache 的相关文件： %s
    " #: wp-cache.php:2129 msgid "Deleting wp-cache file: %s
    " msgstr "正在删除 wp-cache 的相关文件： %s
    " #: wp-cache.php:2194 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "缓存统计信息不是自动生成的，您需要点击下面的链接来重新生成。" #: wp-cache.php:2195 msgid "Regenerate cache stats" msgstr "重新生成缓存统计信息" #: wp-cache.php:2197 msgid "Cache stats last generated: %s minutes ago." msgstr "缓存统计已于 %s分钟前生成。" #: wp-cache.php:2203 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:2204 #: wp-cache.php:2219 msgid "%s Cached Pages" msgstr "%s 已缓存页面" #: wp-cache.php:2205 #: wp-cache.php:2224 msgid "%s Expired Pages" msgstr "%s 已过期页面" #: wp-cache.php:2218 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:2228 msgid "Fresh WP-Cached Files" msgstr "最新的 WP-Cached 文件" #: wp-cache.php:2229 #: wp-cache.php:2245 #: wp-cache.php:2261 #: wp-cache.php:2277 msgid "URI" msgstr "URI" #: wp-cache.php:2229 #: wp-cache.php:2245 msgid "Key" msgstr "密钥" #: wp-cache.php:2229 #: wp-cache.php:2245 #: wp-cache.php:2261 #: wp-cache.php:2277 msgid "Age" msgstr "有效时间" #: wp-cache.php:2229 #: wp-cache.php:2245 #: wp-cache.php:2261 #: wp-cache.php:2277 msgid "Delete" msgstr "删除" #: wp-cache.php:2244 msgid "Stale WP-Cached Files" msgstr "过期的 WP-Cached 文件" #: wp-cache.php:2260 msgid "Fresh Super Cached Files" msgstr "最新的 Super Cached 文件" #: wp-cache.php:2276 msgid "Stale Super Cached Files" msgstr "过期的 Super Cached 文件" #: wp-cache.php:2292 msgid "Hide file list" msgstr "隐藏文件列表" #: wp-cache.php:2294 msgid "Too many cached files, no listing possible." msgstr "缓存文件太多，没有列表可用。" #: wp-cache.php:2296 msgid "List all cached files" msgstr "列出所有已缓存的文件" #: wp-cache.php:2299 msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "到期文件是那些存在时间大于%s秒的文件。它们仍在被调用并会定期被删除。" #: wp-cache.php:2310 msgid "Delete Expired" msgstr "删除已过期文件" #: wp-cache.php:2335 msgid "Delete Super Cache cached files (opens in new window)" msgstr "删除 Super Cache 插件的缓存文件 (新窗口中打开)" #: wp-cache.php:2482 msgid "%1$s is Stephen Fry proof thanks to caching by %2$s" msgstr "%1$s is Stephen Fry proof thanks to caching by %2$s" #: wp-cache.php:2515 msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache 需要设置。请前往 插件管理页面 设置。" #: wp-cache.php:2521 msgid "Settings" msgstr "设置" #: wp-cache.php:2531 msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache 已禁用。请去 插件管理首页 开启缓存功能。" #: wp-cache.php:2534 msgid "Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct." msgstr "警告！WP Super Cache 缓存功能损坏！advanced-cache.php 无法加载 wp-cache-phase1.php。

    请编辑 %1$s/advanced-cache.php 并确保 %2$swp-cache-phase1.php的路径是正确的。" #: wp-cache.php:2553 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] 首页已经被 gzip 压缩！请清除缓存！" #: wp-cache.php:2553 msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "由于您的首页正在被加载，请自行访问 %s 以清除首页的缓存！" #: wp-cache.php:2556 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] 首页已被 gzip 压缩！缓存已清除！" #: wp-cache.php:2556 msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "由于首页正在被加载，您的博客的所有缓存已被清除。请访问 %s 以检查缓存是否已被清除。" #: wp-cache.php:2563 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] 首页不正确！请清除缓存！" #: wp-cache.php:2563 msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "请访问 %1$s 以清除您的站点的首页缓存，该缓存是错误的或者缺失文字 \"%2$s\"！" #: wp-cache.php:2566 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] 首页不正确！缓存已清除！" #: wp-cache.php:2566 msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "由于首页缺失 \"%2$s\" ，所有缓存已被清除。请访问 %1$s 以检查缓存是否已被清除。" #: wp-cache.php:2571 msgid "[%s] Front page check!" msgstr "[%s] 首页检查！" #: wp-cache.php:2571 msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache 已经检查您的博客的首页。如果您想禁用，请访问 %s 。" #: wp-cache.php:2614 msgid "Cannot update .htaccess" msgstr "无法更新 .htaccess 文件" #: wp-cache.php:2614 msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "%s.htaccess 文件无法被服务器变更。请使用 chmod 命令或 ftp 客户端来修正权限。" #: wp-cache.php:2614 msgid "Refresh this page when the file permissions have been modified." msgstr "当文件权限更改后请刷新本页。" #: wp-cache.php:2614 msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "另外，您还可以自行编辑您的 %s.htaccess 文件并添加以下代码 (在任何 WordPress 规则之前):" #: wp-cache.php:2618 msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "如果要使缓存页面生效，您的服务器必须要有包含正确的 mod_rewrite 规则的 %s.htaccess 文件" #: wp-cache.php:2619 msgid "You can edit the file yourself add the following rules." msgstr "您可以自行编辑该文件并添加下列规则。" #: wp-cache.php:2620 msgid " Make sure they appear before any existing WordPress rules. " msgstr " 确保它们在已有的 WordPress 规则前。" #: wp-cache.php:2628 msgid "Update Mod_Rewrite Rules" msgstr "更新 Mod_Rewrite 规则" #: wp-cache.php:2780 msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] 预缓存已开始" #: wp-cache.php:2810 msgid "[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d" msgstr "[%1$s] 正在刷新 从 %3$d 到 %4$d 的 %2$s 分类法" #: wp-cache.php:2856 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] 正在刷新从 %2$d 到 %3$d 的文章" #: wp-cache.php:2877 msgid "[%1$s] Cache Preload Stopped" msgstr "[%1$s] 预缓存已停止" #: wp-cache.php:2887 msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d 篇文章已刷新" #: wp-cache.php:2887 msgid "Refreshed the following posts:" msgstr "以下文章已被刷新：" #: wp-cache.php:2897 msgid "Scheduling next preload refresh in %d minutes." msgstr "下次预缓存任务将在%d分后开始。" #: wp-cache.php:2908 msgid "[%s] Cache Preload Completed" msgstr "[%s] 预缓存完成" #: wp-cache.php:2908 msgid "Cleaning up old supercache files." msgstr "正在清理过期的 supercache 文件。" #: wp-cache.php:2951 msgid "[%s] Preload may have stalled." msgstr "[%s] 预缓存可能已失去响应。" #: wp-cache.php:2951 msgid "" "Preload has been restarted.\n" "%s" msgstr "" "预缓存已经重新启动。\n" "%s" #: wp-cache.php:2994 msgid "Supercache Uninstall Problems" msgstr "Supercache 卸载问题" #: wp-cache.php:2994 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" msgstr "" "亲爱的用户，\n" "\n" "WP Super Cache 已在您的博客上被移除，但是被 mod_rewrite 调用的\n" " .htaccess 文件中的重定向规则尚未被移除。\n" "\n" "请编辑下列文件并且移除\n" "位于 'BEGIN WPSuperCache' 和 'END WPSuperCache' 之间的代码。请首先备份该文件以防不测！\n" "\n" "%s\n" "\n" "此致，\n" "WP Super Cache 插件\n" "http://wordpress.org/extend/plugins/wp-super-cache/" #: wp-cache.php:3031 msgid "Delete cache of the current page" msgstr "删除当前页面的缓存" languages/wp-super-cache-de_DE.mo000066600000212256152133035240012642 0ustar00a$ ,<,Maq` ~?n3* 7 Z 5P! !="b"j5#-#$# #$$%u&\P''?()*1++w,Z-%\--0...0&00:1nI2p2)4;4D4H44444 5#53B5v5z5)6 86,E6r6^#7p7+78n58/88 8 8`8+T9939999!9:!;7<M<c<I=@\==s">>?%?E?J^?@ @@ @@@5@&A9A3A1-B_BCCCDDDPEu_E EjEaFfF?GWG^GqG}yGGNGLHaH2I GInTI$IAI*J0JMJiJJeJJKaLzL LL<LgLPM+cM*MMMM NbN?OOP&QR"Sk$TUWUUEVGV*]V V V VV]V$W@W _WmWWWWOX$aX"XX!XX YYZ&ZZ<Zb [ [y\ ]0 ] =]!J]-l]k]_ _ "_-_3_mL_T_`U/``p3aUaab bb.bJMbbducc`dde0e e ee7eS.f?f<ffg5g7Jgjgg h)hYHhh h h hh(h+i,1i.^ifi i/j01jbj?j8$k]k fk/sk:kkk llm m;mqNmmmneopp#qqzs<qtGt#tRuumv vTw~Cx+xx yyyzK{R{f{{ {{%{'{ | |j8|b|}l}=~F~U~]~f~B~~~*b[^ Fŀ7 rDM/Aqf.$;e`ƈ>i ɋ)If*}/.،3;Z^gowF@<Nď&@ ҐߐOd<98d#;ēKڔn&-)G q6k:ݙ^tӚ jtB gA+աi-}} =EY+n#&E+/ 8:sx1 =V.  #q.>߯P"H ku$%#ѲPF`U"Ix´S.!޶ijpy @423f( yɽ!CweݾR  T* ,:$O@'FnV> +K?x%.*2YU c m/0 `wkQU saHv9  '1gK+#  "$/Gw74I.~15 S@]d C c/p@ Xz%XR{f $"9L\p5$bP <`EEB#/SoD~.J,y4j FPfx-./;6r ;5;qL*Zw >[2 ' W~F5LTlcRW3rEc^2IP| Tb~ (05"Xszy )1:YX'2*({)X8FqRJdd"  6   C /  aD"6!Pr4=0=.l  O z/[9 Z.#NL <=)EqL7If@_\Y&Dxr}FK,-1* !Y[Qm>;" | WB_8s4VuTINR"B`k$22E%@^JPDAU3g X=$cn`K'PA?ldVO/M:4+79+]S'6i%F&ZbTw5C0^M#)0({GX H.,<py]1o8~eRU ? S*G(a-t!:\QWa35Jh ;>Cvj 6H Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumUse Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together.Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.This page explains how to change file permissions.No Adverts for Friends plugin is %s.

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages are stored on your server as html and PHP files. If you need to delete them use the button below.Cached pages since %1$s : %2$sCachingCaching OffCaching OnCaching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.ContentsCurrently caching from post %d to %d.Currently logging to: %sDear User, WP Super Cache was removed from your blog but the mod_rewrite rules in your .htaccess were not. Please edit the following file and remove the code between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first! %s Regards, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggingDeleteDelete CacheDelete Cached PagesDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. Email the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExcludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default).Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionExtra homepage checks. (Very occasionally stops homepage caching)FeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesIt appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelMake WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Provides support for Domain Mapping plugin to map multiple domains to a blog.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSkip https URLs to avoid "mixed content" errorsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Supercache Uninstall ProblemsTagsTest CacheTest your cached website by clicking the test button below.Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$sThis is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledsecondsProject-Id-Version: wp-super-cache 1.2 Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2011-02-23 17:57:46+00:00 PO-Revision-Date: 2011-02-24 16:42+0100 Last-Translator: Language-Team: Blog-Lounge.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: en, er, X-Poedit-Language: German X-Poedit-Country: GERMANY X-Poedit-SourceCharset: utf-8 Stelle sicher dass sie oberhalb sämtlicher WordPress-Regeln stehen. %1$s ist "schlag- und rüttelfest" dank dem Caching von %2$s%1$s wurde entwickelt/wird gewartet von %2$s unter Beteiligung vieler Anderer.%s Seiten im Cache%s Expired-Pages im Cache%s ist beschreibbar! Da es sich dabei um ein Sicherheitsrisiko handelt, ändere das bitte wieder auf "Nur Lesen" nachdem die Seite generiert ist.%s entfernt!%s.htaccess wurde mit den nötigen mod_rewriteRegeln aktualisiert. Bitte überprüfe, ob sie korrekt sind. So sollten sie aussehen: %s/advanced-cache.php existiert nicht oder kann nicht aktualisiert werden.(1 = weniger, 5 = mehr, kann heftige Serverlast verursachen)(Experimentell)(Nur Legacy-Caching wird unterstützt, Komprimierung deaktiviert, und benötigt Bad Behavior in "%s/plugins/bad-behavior/") (auf besucherstarken Seiten vielleicht nicht immer exakt)(nur Abfragen dieser IP protokollieren. Deine IP ist %s)(friendsadverts.php ebenfalls erforderlich) 1. Wenn es sie schon gibt, bitte die Datei zuerst löschen.2. Vergebe %1$s Schreibrechte per CHMOD in der Konsole oder mit deinem FTP-Programm. (chmod 777 %1$s) und lade diese Seite neu. Das ist nur eine zeitweilige Massnahme und Du musst sie danach wieder auf "Nur Lesen" setzen (ändere 777 zu 755 im vorhergehenden Befehl).3. Lade diese Seite neu um %s/advanced-cache.php zu aktualisieren.304 Not Modified Browser Caching. Stelle fest wenn eine Seite seit dem letzten Aufruf nicht modifiziert wurde.304-Support ist standardmässig deaktiviert, da "GoDaddy" in der Vergangenheit Probleme mit ein paar der eingesetzten Header hatte.Frequently Asked QuestionsHilfe zur InstallationSupport-ForumNutze Google-Libraries ermöglicht es, einige der allgemein gebräuchlichen Javascript-Bibliotheken von Google Webservern zu laden. Ironischerweise kann das deine Werte im Yslow-Score verschlechtern.WP Minify reduziert die Anzahl der von deinem Webserver ausgelieferten Dateien durch Kombination der Javascript- und CSS-Dateien. Alternativ dazu kannst Du WPSCMin, ein Supercache-Plugin zur Minimierung gecacheder Seiten nutzen. Dieses bündelt JS/CSS-Dateien in keiner Weise.Yahoo! Yslow ist eine Erweiterung des Firefox add-on Firebug. Sie analysiert Webseiten und bietet Möglichkeiten zur Verbesserung der Performanz an, die auf einer Reihe von Regeln für hoch-performante Webseiten bestehen. Probiere auch die Performance-Online-Tools unter GTMetrix.Diese Seite erklärt, wie Datei-Zugriffsrechte geändert werden können (Englisch).No Adverts for Friends-Plugin ist %s.

    WP_CACHE-Konstante zu wp-config.php hinzugefügt

    Wenn diese Warnung wiederholt angezeigt wird, lese bitte zu Punkt 5 in den FAQ nach. Die WP_CACHE-Zeile muss nach oben verschoben werden."

    WP_CACHE-Konstante auf "False" gesetzt

    Die WP_CACHE-Konstante wird von WordPress genutzt, um den Code der Cache-Seiten erstellt zu laden. Unglücklicherweise ist das auf "Nein" gestellt. Bitte bearbeite deine wp-config.php und ändere bzw. füge die folgende Zeile oberhalb der abschliessenden "require_once"-Anweisung dazu:

    define('WP_CACHE', true);

  • 1. Öffne %1$s$wp_cache_file in einem Texteditor (Notepad++ oder das blaue Teil von Windows..)
  • 2. Ändere den Text CACHEHOME in %2$s
  • 3. Speichere die Datei, kopiere sie nach %3$s und lade diese Seite neu.
    • WARNUNG: Teste erst ein paar statische URLs, z.B.: %s - um vor dem Speichern deiner Änderungen sicherzustellen, daß dein CDN-Service voll funkionsfähig ist.Nur für Fortgeschrittene: Speed up your site with Caching and cache-control erklärt, wie deine Seite über Regeln in der .htaccess-Datei cache-fähiger gemacht wird.Nur für Fortgeschrittene: Installiere einen "Objekt-Cache". Wähle Memcached, XCache, eAcccelerator und andere.Fehler: WP_CACHE ist nicht aktiviert in deiner wp-config.php und ich kann sie nicht modifizieren.Garbage Collection
    Letzte "Entmüllung" war vor %s Minuten
    Seite zuletzt gecached: %sAchtung! Du hast versucht die Datei-Komprimierung zu aktivieren, aber zlib.output_compression ist aktiv. Lese dazu #21 im Bereich Troubleshooting der Datei readme.txt.Benutzerdefinierte Struktur oder Permalink-Struktur ist für korrektes Funkionieren des Plugins erforderlich. Bitte gehe zu Einstellungen > Permalinks um deine Permalinks zu konfigurieren.Eine Abweichung zwischen den Regeln in deiner .htaccess file und den Rewrite Rules im Plugin wurde festgestellt. Dabei kann es sich nur um unterschiedliche Abstände oder Leerzeichen handeln, Du solltest aber die Regeln in der Datei mit den hier unten angezeigten möglichst bald abgleichen. Klicke den "Mod_Rewrite Rules"-Button um die Regeln zu aktualisieren.Eine einfache Art das zu tun ist, die Berechtigungen temporär per CHMOD über die Konsole oder mit deinem FTP-Programmm zu ändern. Sorge dafür dass sie global beschreibbar ist, dann soll es wohl klappen.Akzeptierte Dateinamen & Abgewiesene URIsDirekt-Seite hinzufügen: Hier Strings (Zeichenketten, keine Dateinamen) einfügen, um so dafür zu sorgen dass eine Seite nicht gecached wird. Als Beispiel: Wenn deine URLs das Jahresdatum enthalten und Du die Beiträge vom vergangenen Jahr nicht cachen willst, reicht es das Jahr, z.B. "/2004/" anzugeben. WP-Cache wird überprüfen, ob diese Zeichenkette im URI enthalten ist und in dem Fall diese Seite dann nicht cachen.Hier die Dateinamen angeben, die gecached werden sollen, auch wenn sie einer oben auszusortierenden Zeichenkette entsprechen.Trage die Regeln selbst ein. Bearbeite %s.htaccess und finde den Block zwischen den Zeilen # BEGIN WPSuperCache und # END WPSuperCache. Da gibt es zwei Bereiche, die sich sehr ähneln. Direkt unterhalb der Zeile %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ diese Zeilen einfügen: (zweimal, jeweils eine in beiden Bereichen)Weitere CNAMESErweitertAlterAlternativ dazu kannst Du deine %s.htaccess manuell bearbeiten und folgenden Code einfügen (oberhalb aller WordPress-Einträge): ArchiveVerfügbare PluginsWartet auf Freigabe "Awaiting Moderation"-Plugin ist jetzt %s. Schlechtes Verhalten (Bad Behavior)"Bad Behaviour"-Support ist jetzt %s. "Bad Behaviour" nicht gefunden. Bitte überprüfe deine Installation.CDNCDN-Funktionen bereitgestellt durch OSSDL CDN Off Linker von Mark Kubacki.Cache-InhalteCache-TesterCache Treffer auf diese Webseite für schnellen Zugriff.Cache-Plugins sind PHP-Skripte, die sich im Plugin-Verzeichnis innerhalb des Ordners "wp-super-cache" befinden. Sie werden zusammen mit Supercache geladen, viel früher als reguläre WordPress-Plugins.Cache neu erstellen. Liefert eine Supercache-Datei an anonyme Besucher aus, während eine neue Datei erstellt wird.Cache-Statistiken werden nicht automatisch erzeugt. Du musst auf den Link hier unten klicken, um die Statistik für diesen Blog neu zu generieren.Cache-Statistik zuletzt generiert vor %s Minuten.Vor %s Sekunden gecachedGecachede Seiten werden auf deinem Server als HTML- und PHP-Dateien gespeichert. Wenn Du sie löschen mußt, nutze den Button hier unten.Cached-Pages seit %1$s : %2$sCachingCaching AusCaching AnCaching ist nur eine Möglichkeit, eine Webseite "schneller" zu machen. Hier ein paar weitere hilfreiche Plugins:Caching muss aktiviert sein, um diese Option nutzen zu könnenCache-Preload abstellenGeht nicht weiter... vorausgegangene Probleme beheben und noch einmal versuchen.Kann .htaccess nicht aktualisierenKategorieLaufzeit ändernCheck die Startseite alle 5 Minuten.Suchen und Entfernen von abgelaufenen Dateien kostet ressourcen, sie einfach da zu belassen aber auch. Auf einer sehr gut besuchten Seite solltest Du die Laufzeit auf 300 Sekunden setzen. Experimentiere mit verschiedenen Werten und besuche diese Seite mehrmals um zu überprpüfen, wieviele "expired"-Dateien sich zu welcher Zeit im Laufe des Tages ansammeln. Wenn Du Legacy-Caching benutzt, versuche möglich unter 500 Cache-Dateien zu bleiben. Du kannst um ein Vielfaches mehr Dateien haben, wenn Du mod_rewrite oder PHP-Caching einsetzt.Alte Supercache-Dateien bereinigen.Alle Cache-Dateien bereinigen, wenn ein Beitrag oder eine Seite publiziert wird.Bei "Error" Cache leeren.Datei "stumpf" sperren. Brauchst Du wahrscheinlich nicht, aber es könnte helfen wenn dein Server schwächelt. Achtung! Kann in seltenen Fällen dazu führen das dein Server abstürzt!Kommentare werden moderiert. Es kann etwas dauern, bis dein Kommentar angezeigt wird.Komprimiere Seiten, so das sie schneller an Besucher ausgeliefert werden.Die Komprimierung ist standardmässig deaktiviert, da manche Hosts Probleme mit komprimierten Dateien haben. An- und abschalten leert den Cache.Die Konfigurationsdatei wurde geändert, einige Werte sind vielleicht falsch. Bitte die Seite neu laden im Menü "Einstellungen", um sie zurückzusetzen.Deine WP-Cache Konfigurationsdatei fehlt und %1$s Verzeichnis (%2$s) ist nicht beschreibbar für den Webserver. Bitte überprüfe die Berechtigungen für den Webserver.InhalteMomentan wird von Beitrag %d bis %d gecached.Aktuelle Protokolle (Logs) in: %sLieber Benutzer, WP Super Cache wurde von deinem Blog entfernt, aber die mod_rewrite rules in deiner .htaccess nicht. Bitte bearbeite fogende Datei und lösche den Code zwischen 'BEGIN WPSuperCache' und 'END WPSuperCache'. Und bitte erst die Datei sichern! %s Mit freundlichem Gruß, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggenLöscheCache leerenLösche gecachede SeitenAbgelaufene löschenLösche Super-Cache gecachede Dateien (öffnet in neuem Fenster)Lösche gecachede DateiLösche die mod_rewrite rules des Plugins in %s.htaccess zwischen # BEGIN WPSuperCache und # END WPSuperCache und lass sie dann vom Plugin neu generieren. Dazu musst Du nur diese Seite im Browser neu laden.Supercache-Datei löschen: %s
    Datei wp-cache löschen: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting: Direkt gecachede DateienDirekt gecachede Seiten sind Dateien, die direkt in %s erzeugt werden, da wo dein Blog liegt. Diese Option ist nur sinnvoll, wenn Du auf dem Niveau von Facebook oder Digg Traffic auf einer Seite oder auf einem Beitrag erwartest.Verzeichnisse, die in Static File Matching mit einbezogen werden sollen. Benutze das Komma als Trennzeichen. Die Vorgabe ist wp-content, wp-includes, zwangsläufig eingesetzt, wenn das Feld leer gelassen wird.DeaktiviereDeaktiviertFolgende Page-Typen nicht cachen. Studiere zu jedem Typ die ausführliche Diskussion in der Dokumentation Conditional Tags.Domain-Mapping"Domain Mapping"-Plugin gefunden! Bitte gehe zur Supercache Plugins-Page und aktiviere das "Domain Mapping" Hilfs-Plugin."Domain Mapping"-Support ist %s. Seiten für bekannte Benutzer nicht cachen.EasyBearbeite %s und füge folgende Zeile hinzu:
    define('WP_CACHE', true);
    Ansonsten wird WP-Cache nicht ausgeführt durch Wordpress.E-Mail an den Administrator wenn die Überprüfung beendet. (hilfreich für Tests)AktiviereAktiviere CDN SupportAktiviertAktiviert oder deaktiviert: Entferne den Text "Dein Kommentar wird vor der Freigabe moderiert." wenn jemand einen zu moderierenden Kommentar hinterlässt. FehlerError: GZIP-Komprimierung ist aktiv, deaktiviere sie wenn Du wp-cache nutzen willst.Verbergen falls SubstringSchließt etwas vor Revisionen aus, wenn eine der obengenannten Zeichenketten im Ergebnis gefunden wird. Benutze ein Komma als Trennzeichen, wie hier: .php, .flv, .do, und binde immer .php mit ein (Standard).Direkt-Seite existiertLaufzeitende:Abgelaufene Dateien sind Dateien die älter als %s Sekunden sind. Sie werden noch vom Plugin genutzt und in regelmässigen Abständen gelöscht.Expiry-Time & Garbage-CollectionExtra Startseiten-Checks. (Stoppt in sehr seltenen Fällen Startseiten-Caching)FeedsLädt %s um den Cache zu priorisieren: Lädt die erste Kopie von %s: Lädt die zweite Kopie von %s: Repariere KonfigurationVersuche Probleme mit dem Plugin durch den Debugger hier zu lösen. Das System kann sie in eine Log-Datei in deinem Cache-Verzeichnis schreiben.Für optimale Performance solltest Du "Mobile Endgeräte unterstützen" aktivieren oder die "Rewrite Rules für mobile Endgeräte" in der .htaccess löschen. Suche die beiden Zeilen mit dem Text "2.0\ MMP|240x320" und entferne sie.Als Beispiel: Um %1$sabout/ zu cachen, würdest Du %1$sabout/ oder /about/ eingeben. Die Cache-Datei wird dann erstellt, sobald ein anonymer Besucher die Seite aufruft.Neue Super-Cached DateienNeue WP-Cache-DateienStartseiteText der StartseiteVollständiges Erneuern des Cache in %d Stunden %d Minuten und %d Sekunden.GZIP-Komprimierung ist in WordPress aktiviert - wp-cache wird überbrückt, bis Du "gzip compression" deaktiviert hast.Müll-Entsorgung (Garbage-Collection)"Gzip encoding rules" in %s.htaccess erstellt.Er bloggt unter %1$s und publiziert Photos in %2$sDatei-Liste verbergenHomeIch bin zu 99% sicher, dass das keine von WP-Super-Cache verursachten Bugs sind, und sie kommen nur in extrem seltenen Fällen vor. Du kannst aber alle 5 Minuten einen simplen Check laufen lassen, um sicherzugehen dass deine Seite ok ist, wenn Du dir Sorgen machst. Du bekommst dann eine E-Mail Benachrichtigung, falls ein Problem auftaucht.IP-AddresseWenn das nicht hilft, stelle sicher dass die Datei %s/advanced-cache.php nicht existiert: Wenn die Laufzeit länger als 1800 Sekunden (halbe Stunde) ist, wird "Garbage Collection" alle 10 Minuten ausgeführt, andernfalls passiert das 10 Sekunden nach Ablauf der oben angegebenen Zeit.Wenn Du das Plugin deinstallierst, stelle sicher dass Verzeichnis %s für den Webserver beschreibbar ist, so das die Dateien advanced-cache.php und cache-config.php automatisch entfernt werden können. (..die Dateien ebenfalls beschreibbar zu machen ist dabei eine gute Idee!)Im "Preload-Modus" wird die normale "Garbage Collection" (Leeren des abgelaufenen Cache) nur alte Legacy-Dateien für schon bekannte Benutzer bereinigen, nicht die vorab geladenen Supercache-Dateien. Das ist die empfohlene Einstellung wenn der Cache vorgeladen wird.In sehr seltenen Fällen können zwei Probleme auf manchen Blogs auftreten:
    1. Die Startseite kann anfangen sich als zip.Archiv herunterzuladen.
    2. Eine falsche Seite wird nach dem Zufallsprinzip als Startseite gecached, wenn dein Blog eine statische Seite als Startseite benutzt und deine Permalinks mit /%category%/%postname%/ strukturiert sind.
    Schließe Verzeichnisse mit einScheint als wäre mod_rewrite nicht installiert. Manchmal ist dieser Check nicht zuverlässig, besonders wenn dein Webserver nicht mit Apache arbeitet. Bitte stelle sicher, dass das Modul mod_rewrite aktiviert ist. Es wird benötigt, um statische Supercache-Dateien zu erstellen. Du kannst dann immer noch Legacy oder PHP-Modi benutzen.Sieht aus als hätte dein Blog URLs, die mit "/" aufhören. Dummerweise wurde ein Bug entdeckt, nachdem Du das Plugin installiert hast: URLs, die ohne "/" enden liefern den gleichen Inhalt wie URLs mit "/", und werden nicht auf den eigentlichen URL weitergeleitet (Dublicate Content). Um das zu beheben, bearbeite deine .htaccess und füge diese beiden Regeln den zwei Super-Cache-Gruppen hinzu: SchlüsselVerzögerte Initiierung. Zeige gecachede Dateien nachdem WordPress geladen ist. Meistens nützlich im Legacy-Modus.Legacy Page-Caching.Weniger E-Mails, 1 am Anfang und 1 am Ende des Preloads aller Beiträge.Alle Cache-Dateien auflistenAuflistung der zuletzt gecacheden Pages auf dieser Seite.SperreSperren: Log-LevelMach WordPress schneller!Leere die Textbox, um sie von der Liste der Direkt-Seiten zu entfernen und die Cache-Datei zu löschen.Viele E-Mails, 2 E-Mails pro 100 Beiträge.Mittel, 1 E-Mail pro 100 Beiträge.SonstigesFehlende Apache-ModuleUnterstützung mobiler Endgeräte."Rewrite Rules" für mobile Endgeräte gefundenDie Unterstützung mobiler Endgeräte benötigt Extra-Regeln in der Datei .htaccess, oder Du setzt das Plugin in den Legacy-Modus. Hier sind deine Oprionen (sortiert nach Schwierigkeitsgrad):Mod Rewrite RulesMod Rewrite Rules können nicht aktualisiert werden!Mod Rewrite Rules müssen aktualisiert werden!Mod Rewrite Rules aktualisiert!Mod Rewrite ist wahrscheinlich nicht installiert!Mod_rewrite ist am schnellsten, PHP ist fast genau so schnell und einfacher ans Laufen zu kriegen, währen Legacy-Caching langsamer läuft, aber flexibler und ebenso leicht zu aktivieren. Neulinge sollten PHP-Caching wählen.Hilfe benötigt?Hilfe benötigt? Check die Datei Super Cache readme. Sie enthält die Dokumenration zur Installation, FAQ und Troubleshooting-Tipps. Das Supportforum steht ebenso zur Verfügung. Vielleicht ist deine Frage dort schon beantwortet worden.Neueste Cached-Pages: Nächste "Entmüllung" in %s MinutenHinweis: Hinweis: aktiviert PHP-Caching, Cache-Rebuild und Mobile-SupportHinweis: Mod_rewrite oder Legacy-Caching aktiviert. Die Seite "Erweiterte-Einstellungen" wird standardmässig angezeigt.Hinweis: PHP-Caching ist aktiviert, es wurden aber Supercache mod_rewrite rules gefunden. Cache-Dateien werden nach diesen Regeln erstellt. Wenn deine Seite funkioniert, kannst Du diesen Hinweis gerne ignorieren. Oder bearbeite die Datei .htaccess - auf der "root" (oberste Ebene im Webverzeichnis) deiner Installation - und entferne die Supercache-Regeln.Hinweis: WP-Super-Cache mod_rewrite rule Checks sind deaktiviert, insofern sie nicht auf der Hauptseite dieses Blog-Netzwerks laufen.OKObjekt-Cache im Gebrauch. Cache-Listing steht nicht zur Verfügung.Off-site URLEin oder mehrere Seitenaufrufe fehlgeschlagen: Aktuelle Seite nur erneuern, wenn Kommentare geschrieben werden.PHP komprimiert die Daten, die an die Besucher deiner Seite gesendet werden. Deaktivierung wird hier empfohlen, da das Plugin ansonsten einmalig die komprimierte Ausgabe cached statt die gleiche Seite immer und immer wieder zu cachen. Beachte dazu auch #21 im Bereich "Troubleshooting". Lese diese Seite mit Anweisungen zur Bearbeitung deiner php.ini.Seite %d: %d (%s)Seite 1: %sSeite 2: %sSeitenFehler in Permalink-StrukturBitte bewerte dieses Plugin und berichte mir, ob es für dich funktioniert oder nicht. Damit unterstützt Du die Weiterentwicklung wirklich und wahrhaftig.Bitte erstelle %s /wp-cache-config.php aus der wp-super-cache/wp-cache-config-sample.phpBitte sag auch "Hallo" zu ihm bei %s!Bitte lese den Eintrag Nº16 im Bereich: Troubleshooting der readme.txtBitte werfe einen Blick in readme.txt für Anleitungen zur Deinstallation dieses Skripts. Suche nach der Überschrift "How to uninstall WP Super Cache".Bitte gehe zu %1$s um den Cache zu leeren, da deine Startseite nicht in Ordnung zu sein scheint und der Text fehlt, "%2$s"!Bitte gehe zu %s um den Cache zu leeren, da die Startseite deiner Website gerade heruntergeladen wird!PluginsPreloadLade %s Beiträge vorab.Cache jetzt vorladen"Preload" wurde neu gestartet %sPreload-Modus (Garbage-Collection nur für Legacy Cache-Dateien. Empfohlen.)"Vorladen" produziert aber auch eine Menge Dateien. Es wird vom ältesten bis zum neuesten Beitrag gecached, also bedenke bitte nur die Neuesten zu cachen, wenn Du viele (10.000+) Einträge hast. Das spielt vor allem auf virtuellen Servern (shared hosting) eine entscheidende Rolle.Cache-Preloading deaktiviert. Bitte deaktiviere Legacy-Caching oder kläre das mit deinem Hosting-Administrator.Bereite deinen Server auf eine zu erwartende Höchstlast an Traffic vor, indem Du "Sperren" aktivierst. In dieser Einstellung werden die statischen Dateien im Cache nicht erneuert, wenn zu den Beiträgen Kommentare veröffentlicht werden.Proudly tell the world your server is Digg proof! (zeigt einen kleinen Hinweis im Footer deines Blogs, dass dein Server "hieb- und stichfest" ist)Unterstützt das Domain Mapping-Plugin, um verschiedene Domains auf einen Blog einzutragen.Bitte bewerte dieses Plugin!Nur Leserechte (Read-Only Modus). Die Konfiguration kann nicht geändert werden.Nur Leserechte: EmpfohlenEmpfohlene Links und PluginsErneuern des Cache in %d Stunden %d Minuten und %d Sekunden.Erneuere vorab geladene Cache-Dateien alle %s Minuten. (0 zum deaktivieren, Minimum %d Minuten.)Lade diese Seite neu, wenn die Datei-Berechtigungen geändert wurden.Lade die Seite neu, wenn Du die Datei .htaccess aktualisiert hast.Folgenende Beiträge aktualisiert: Regeneriere Cache-StatistikAbgewehrte User-AgentsErforderlich um komprimierte Supercache-Dateien sauber zu erstellen.Erforderlich um Caching-Infos in Supercache-Seiten zu schreiben. IE7-User bekommen ohne dieses Modul nur alte Seiten zu sehen.Ursprüngliche Konfiguration wieder herstellen"Rewrite Rules" müssen aktualisiert werden!Regeln müssen auch noch zu %s hinzugefügt werden: WP-Cache Konfigurations-Beispieldatei (%s) existiert nicht. Überprüfe die Installation.SpeichernÄnderungen speichernDateien speichernStrings speichernUser-Agenten-Strings speichernPlanmässiges Vorladen des Cache abgebrochen.Planmässiges Vorladen des Cache in %d MinutenPlanmässiges Vorladen des Cache in 10 SekundenNächste "Preload"-Aktualisierung in %d Minuten eingeplant.Scroll zum Ende der "Erweitere Einstellungen"-Seite und klicke auf den Schalter Mod_Rewrite Rules aktualisieren.SuchseitenSende mir E-Mails zum Status, wenn Dateien erneuert wurden.Sende "Non-Secure"-Anfrage (kein https) für HomepageSetzt das Ablaufdatum für Supercache-Seiten. Besucher bekommen unter Umständen ohne diese Modul neue Seiten nicht angezeigt oder verlieren Kommentare, wenn sie den Browser neu laden.Setze die Laufzeit auf 0 Sekunden um die Garbage-Collection zu deaktivieren.Setze das Plugin auf den half-on-Modus und aktiviere " Unterstützung mobiler Endgeräte".EinstellungenEinzelne BeiträgeÜberspringt https URLs um "mixed content" Fehler zu vermeiden
    Entschuldigung. Mein Blog ist im "Gesperrt"-Modus. Updates werden in Kürze angezeigtAbgelaufene Super-Cached DateienAbgelaufene WP-Cache DateienStrings im HTTP "User Agent"-Header die WP-Cache davon abhalten, Anfragen von Bots, Spidern und Crawlern zu cachen. Vermerke, das Super-Cache-Dateien weiter an diese Agents ausgeliefert werden wenn sie schon existieren.Supercache Probleme beim DeinstallierenSuchworte (tags)Cache testenTeste deine gecachede Webseite durch anklicken des Schalters "Cache testen" hier unten.Text, um danach auf der Front-Page zu suchen: Wenn nicht gefunden, wird der Cache geleert. Leer lassen um das zu deaktivieren.Danke für das Upgrade.Das CDN Sync-Tool Plugin wird den Dateiupload zu Amazon S3/Cloudfront unterstützen, wenn Du lieber vom Orginalzugriff unabhängig bist. Lies das plugin support forum, wenn Du zu diesem Plugin irgendwelche Fragen hast.Die WP-Super-Cache Konfigurationsdatei %s/wp-cache-config.php kann nicht bearbeitet werden. Für jegliche Änderung muss der Webserver Schreibrechte für die Datei besitzen.Der Cache deines Blogs wurde geleert, da der Text "%2$s" nicht auf der Startseite ist. Bitte gehe zu %1$s um sicherzustellen, dass der Cache bereinigt ist.Der Cache deines Blogs wurde geleert, da die Startseite gerade runterlädt. Bitte gehe zu %s um sicherzustellen, dass der Cache bereinigt ist.Die Datei %s.htaccess kann vom Webserver nicht aktualisiert werden. Bitte ändere das per CHMOD-Command oder FTP-Programm.Folgende Apache-Module fehlen. Das Plugin arbeitet ohne sie im Legacy-Modus. Im vollen Supercache-Modus kann es ansonsten passieren, dass deine Besucher beschädigte Seiten oder veraltete Inhalte sehen.Die mod_rewrite-Regeln haben sich verändert, seit Du das Plugin installiert hast. Leider musst Du die alten Supercache-Regeln entfernen, bevor die Neuen aktualisiert werden können. Lade die Seite neu, wenn Du deine .htaccess aktualisiert hast. Wenn Du händisch aktualisieren willst, ändere die folgende Zeile: %1$s so dass sie hinterher so aussieht: %2$s Die einzigen Änderungen: "HTTP_COOKIE" wird zu "HTTP:Cookie" und "wordpressuser" wird zu "wordpress". Dies wurde in WordPress 2.5 geändert, ist aber abwärtskompatibel mit älteren Versionen - wenn Du mutig genug bist, sie zu benutzen.Der neue URL anstelle von %1$s für das Rewriting. Kein führendes Zeichen / bitte.
    Als Beispiel: %2$s.Die Seiten stimmen nicht überein! Die Zeitstempel sind unterschiedlich oder wurden nicht gefunden!Die "Rewrite Rules" für dieses Plugin wurden geändert oder sind nicht vorhanden.Die Zeitstempel auf beiden Seiten stimmen überein!Diese CNAMES werden anstatt der %1$s für Rewriting genutzt (als Ergänzung zu dem Off-Site URL weiter oben). Benutze ein Komma als Trennzeichen. Für Seiten mit einer großen Anzahl statischer Dateien kann sich dadurch die Leistung des Browsers verbessern. Es kann sein, das CNAMEs auch in deinem CDN konfiguriert werden müssen.
    Als Beispiel: %2$sDas ist definitiv nur eine Option für sehr weit "Fortgeschrittene". Kenntnisse sowohl in PHP als auch zu WordPress-Actions sind Vorraussetzung, um sie zu erstellen.Dadurch werden alle publizierten Seiten und Beiträge gecached. Es werden statische Supercache-Dateien erstellt, so dass anonyme Besucher (inklusive Bots) eine gecachede Seite aufrufen. Das kann möglicherweise dein Google-Ranking verbessern, da kurze Ladezeiten als Maßstab für die Beurteilung von Webseiten relevant sind.Hat keinen Einfluss auf normale Besucher, nur Handy-Benutzer bekommen ungecachede Seiten angezeigt.Um statische HTML-Dateien zu erstellen, benötigt dein Server die korrekten "mod_rewrite rules" in der Datei %s.htaccess.Zu viele Cache-Dateien, Auflistung nicht möglich.Überprüfung des "trailing slash" (Schrägstrich am Ende des URL) erforderlich.URILeider kann WordPress die Datei wp-cron.php nicht finden. Dieses Skript wird für einwandfreies Funktionieren der Garbage-Collection dieses Plugins, der zeitlichen Einbindung von Beiträgen in WordPress und andere kritische Aktionen benötigt.Leider können die "Rewrite-Rules" nicht automatisch aktualisiert werden, wenn Du WordPress MU benutzt. Bitte öffne deine .htaccess und füge die folgenden mod_rewrite Regeln oberhalb aller anderen Einträge in die Datei ein.Deinstalliere das Plugin in der Plugins-Verwaltung. Es wird dabei automatisch hinter sich aufräumen. Wenn ein manueller Eingriff nötig ist, gibt es einfache Anweisungen.AktualisierenDirekt-Seiten aktualisierenMod Rewrite Rules aktualisierenEinstellungen aktualisierenUpdate-StatusNutze PHP um Cache-Dateien auszuliefern.Nutze mod_rewrite um Cache-Dateien auszuliefern.Nutze Objekt-Cache um gecachede Dateien zu speichern.Mod_Rewrite Rules anzeigenWP-Super-Cache EinstellungenWP-Super-Cache hat die Startseite deines Blogs überprüft. Bitte gehe zu %s, wenn Du die Funktion deaktivieren möchtest.WP-Super-Cache ist deaktiviert. Bitte gehe zur Seite der Plugin-Administration um Caching zu aktivieren.WP-Super-Cache mod_rewrite rules in der Datei %s.htaccess gefunden.
    Klicke auf den folgenden Link, um die Einträge die dieser Datei hinzugefügt wurden, anzuzeigen. Wenn Du ein Upgrade des Plugins gemacht hast, stelle sicher dass diese Regeln zutreffen.WP-Super-Cache muss konfiguriert werden. Gehe zu den Einstellungen, um das Plugin zu aktivieren und zu konfigurieren.WP-CacheWP-Super-CacheWarnungWarnung!Warnung! %s ist beschreibbar!Warnung! Komprimierung ist deaktiviert, weil die Funktion gzencode() nicht vorhanden ist.Achtung! PHP Safe-Modus ist aktiviert!!Achtung! WP Super-Cache Caching abgebrochenn! Das Skript advanced-cache.php konnte wp-cache-phase1.php nicht aufrufen.

    Bitte bearbeite %1$s/advanced-cache.php und stelle sicher, daß der Pfad %2$swp-cache-phase1.php korrekt ist.Achtung! Dein Host-Name "%s" wird in %s aufgelöstWordPress MU (WP Multi-Sites) festgestelltWordPress ist im "locked down" Modus. Statische Super-Cache-Dateien werden nicht gelöscht, wenn neue Kommentare geschrieben werden.WordPress ist nicht im "locked down" Modus. Neue Kommentare werden ganz normal die statischen Super-Cache-Dateien erneuern.Beschreibbar: Du kannst verschiedene CDN-URLs für jede Seite eines Multsite-Blognetzwerks definieren.Du kannst die Datei selbst bearbeiten und folgende Regeln hinzufügen.Du kannst sehen wo die Regeln eingetragen werden, wenn Du den "View mod_rewrite rules"-Link hier unten anklickst.Kann sein dass es zu Probleme mit diesem Plugin kommt, da SAFE MODE aktiviert ist.Es müssen die Markierungen BEGIN und END in %s.htaccess stehen, damit das Auto-Update funktioniert. Sie sehen so aus und umgeben die WordPress mod_rewrite Regeln: Du musst %s beschreibbar machen, um diese Option zu nutzen. Da es sich dabei um ein Sicherheitsrisiko handelt, ändere das bitte wieder auf "Nur Leserechte" nachdem die Seite generiert ist.Du oder ein Administrador könnten es ans Laufen kriegen, wenn die Besitzrechte des Plugin-Skripts entsprechend den Einstellungen auf dem Webserver (Gruppe/Besitzer) angepasst werden. Die Besitzergruppe des %s/cache/-Verzeichnisses muss ebenfalls geändert werden. Weitere Details unter Safe-Modus Anleitung.Du oder ein Administrator müssen das deaktivieren. Bitte besuche die Seite Safe-Modus Anleitung für weitere Details. Leider kann das nicht per .htaccess ausgeschaltet werden, sondern muss in der php.ini konfiguriert werden.Du solltest die Zugriffsrechte in %s ändern, stelle sie etwas restriktiver ein. Benutze dein FTP-Programm, oder die folgende Anweisung um das zu erledigen:Deine %s.htaccess ist für den Webserver nicht beschreibbar und muss mit den nötigen mod_rewrite rules aktualisiert werden. Die neuen Regeln werden, wie hier im Code angezeigt, oberhalb der regulären WordPress-Regeln eingetragen: Deine WP-Cache Konfigurationsdatei (%s) ist nicht aktuell und nicht beschreibbar für den Webserver. Bitte lösche sie und lade diese Seite neu.Dein Cache-Verzeichnis ($cache_path) existiert nicht und konnte nicht erstellt werden. Prüfe %s Benutzerrechte.Dein Cache-Verzeichnis (%1$s) oder %2$s muss beschreibbar sein, damit das Plugin funktioniert. Doppelt überprüfen.Dein Kommentar wird vor der Freigabe moderiert.Dein Server ist so eingestellt, dass erst die Besitzrechte des PHP-Skripts überprüft werden, bevor Schreib- und Lese-Zugriff gestattet wird.Dein Server glaubt, dein Host-Name wird zu %s aufgelöst. Einige Dienste, z.B. die Garbage-Collection dieses Plugins und in WordPress eingebundene Beiträge, werden evtl. nicht korrekt funktionieren.Deine Webseite nutzt evtl. viele statische Dateien. Bilder, Javascript- und CSS-Dateien sind normalerweise statische Dateien, die genausogut von einer anderen (Sub-)Domain oder einem CDN (Content Distribution Network) ausgeliefert werden können. Deshalb ersetzt dieses Plugin alle Pfade in den Verzeichnissen wp-content und wp-includes (ausnahmsweise der PHP-Dateien) deiner Seite mit dem URL, den Du unten eingibst. Auf diese Art können die statischen Inhalte auf einen dedizierten Server kopiert werden, oder die Dateien über ein "CDN" via origin pull gespiegelt werden."Zlib Output Compression" (Dateiausgabe komprimiert) ist aktiviert!![%1$s] %2$d Beiträge aktualisiertCache-Preload gestartetCache-Preload abgestellt[%1$s] Beiträge von %2$d bis %3$d werden aktualisiert[%s] Cache-Preload abgeschlossen![%s] Startseiten-Check![%s] Startseite mit Gzip komprimiert! Cache geleert![%s] Startseite mit Gzip komprimiert! Bitte den Cache leeren.[%s] Startseite nicht in Ordnung! Cache geleert![%s] Startseite ist nicht in Ordnung! Bitte den Cache leeren!"Preload" evtl. unterbrochen.AlledeaktiviertaktiviertSekundenlanguages/wp-super-cache-zh_TW.po000066600000252371152133035240012742 0ustar00msgid "" msgstr "" "Project-Id-Version: WP Super Cache (Traditional Chinese)\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2012-06-21 09:44:46+00:00\n" "PO-Revision-Date: \n" "Last-Translator: Liang, Jih-Kai \n" "Language-Team: privism \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Chinese\n" "X-Poedit-Country: TAIWAN\n" "X-Poedit-SourceCharset: utf-8\n" #: ossdl-cdn.php:151 msgid "Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull." msgstr "你的網站可能使用了許多的靜態檔案。圖片、Javascript、CSS 檔案通常都是靜態檔案，可以很簡單地使用另一個站台或 CDN (內容傳遞網路)來服務。所以這個外掛會根據你下面所提供的 URL，取代你的網站中 wp-content 和 wp-includes 目錄下除了 PHP 檔案以外的任何連結。用這個方式，你可以把所有的靜態內容拷貝到一個專用的主機或或使用 origin pull 鏡射到 CDN 上。" #: ossdl-cdn.php:152 #: wp-cache.php:1071 msgid "The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin." msgstr "如果你不希望依賴 origin pull，CDN Sync Tool 是一個幫助你上傳檔案到 Amazon S3/Cloudfront 的外掛。 如果你對此外掛有任何問題，請參見 外掛支援論壇。" #: ossdl-cdn.php:153 msgid "WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes." msgstr "警告： 請先測試一些固定的網址，例如%s。在儲存變更前，確定你的 CDN 服務完全正常。" #: ossdl-cdn.php:154 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "你可以為多站台網路中的每個站台定義不同的 CDN URL。" #: ossdl-cdn.php:162 msgid "Enable CDN Support" msgstr "啟用 CDN 支援" #: ossdl-cdn.php:165 msgid "Off-site URL" msgstr "站外 URL" #: ossdl-cdn.php:168 msgid "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "這個新的 URL 在會重寫時用來取代 %1$s。請不要加上結尾的 /。
    例： %2$s" #: ossdl-cdn.php:172 msgid "Include directories" msgstr "包含以下目錄" #: ossdl-cdn.php:175 msgid "Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty." msgstr "靜態檔案比對包含的目錄。使用逗號作為分隔符號。預設為 wp-content, wp-includes ，當這個欄位空白時會強制套用。" #: ossdl-cdn.php:179 msgid "Exclude if substring" msgstr "若含有以下字串則排除" #: ossdl-cdn.php:182 msgid "Excludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "若網址中包含以上的字串，則不會被重寫。使用逗號作為分隔符號，像這樣：.php, .flv, .do，並請永遠包含.php (預設值)。" #: ossdl-cdn.php:186 msgid "Additional CNAMES" msgstr "額外的正規名稱(CNAMES)" #: ossdl-cdn.php:189 msgid "These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$s" msgstr "這些 正規名稱記錄(CNAMES) 會在重寫時用來取代 %1$s (和上面的站外URL一起)。 使用逗號作為分隔符號。 在有大量靜態檔案的網頁中，這可以增進瀏覽器效能。 這些正規名稱可能也需要在你的 CDN 被設定。
    例： %2$s" #: ossdl-cdn.php:193 msgid "Skip https URLs to avoid \"mixed content\" errors" msgstr "跳過 https 網址以避免「混合的內容」錯誤" #: ossdl-cdn.php:197 msgid "Save Changes" msgstr "儲存變更" #: ossdl-cdn.php:199 msgid "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "CDN 功能由OSSDL CDN Off Linker提供，作者為Mark Kubacki" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "您的迴響正等待審核中。" #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "Awaiting Moderation" #: plugins/awaitingmoderation.php:34 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:75 #: plugins/searchengine.php:69 #: plugins/wptouch.php:22 #: wp-cache.php:1311 msgid "Enabled" msgstr "啟用" #: plugins/awaitingmoderation.php:35 #: plugins/badbehaviour.php:66 #: plugins/domain-mapping.php:76 #: plugins/searchengine.php:70 #: plugins/wptouch.php:23 #: wp-cache.php:1311 msgid "Disabled" msgstr "停用" #: plugins/awaitingmoderation.php:36 msgid "Enables or disables plugin to Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment." msgstr "啟動或關閉此外掛，決定當有人發佈需審核的迴響時，是否去除「您的迴響正等待審核中」字樣。" #: plugins/awaitingmoderation.php:40 #: plugins/badbehaviour.php:71 #: plugins/domain-mapping.php:81 #: plugins/searchengine.php:75 #: plugins/wptouch.php:28 #: wp-cache.php:1769 #: wp-cache.php:1771 msgid "enabled" msgstr "已啟用" #: plugins/awaitingmoderation.php:42 #: plugins/badbehaviour.php:73 #: plugins/domain-mapping.php:83 #: plugins/searchengine.php:77 #: plugins/wptouch.php:30 msgid "disabled" msgstr "已停用" #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "Awaiting Moderation 外掛模組 %s" #: plugins/awaitingmoderation.php:45 #: plugins/badbehaviour.php:76 #: plugins/domain-mapping.php:86 #: plugins/searchengine.php:80 #: plugins/wptouch.php:33 msgid "Update" msgstr "更新" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "找不到 Bad Behaviour。請檢查是否正確安裝。" #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "Bad Behavior" #: plugins/badbehaviour.php:68 msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "（只支援傳統模式，停用壓縮，Bad Behavior 路徑必須為 \"%s/plugins/bad-behavior/\"）" #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "Bad Behaviour 外掛模組 %s" #: plugins/badbehaviour.php:83 #: wp-cache.php:1401 #: wp-cache.php:1406 msgid "Warning!" msgstr "警告！" #: plugins/domain-mapping.php:73 msgid "Domain Mapping" msgstr "Domain Mapping" #: plugins/domain-mapping.php:78 msgid "Provides support for Domain Mapping plugin to map multiple domains to a blog." msgstr "Domain Mapping外掛支援，映射多個網域至一個 blog。" #: plugins/domain-mapping.php:84 msgid "Domain Mapping support is now %s" msgstr "Domain Mapping 外掛模組 %s" #: plugins/domain-mapping.php:98 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Domain Mapping 外掛模組已被偵測到！請到 Supercache 外掛頁面啟用 domain mapping 支援外掛。" #: plugins/multisite.php:13 msgid "Cached" msgstr "已快取" #: plugins/multisite.php:31 #: wp-cache.php:1324 msgid "Enable" msgstr "啟用" #: plugins/multisite.php:33 #: plugins/searchengine.php:61 #: wp-cache.php:1324 msgid "Disable" msgstr "停用" #: plugins/multisite.php:39 msgid "Caching has been disabled on this blog on the Network Admin Sites page." msgstr "這個部落格的快取，已經在站台網路管理頁面中被關閉。" #: plugins/searchengine.php:67 msgid "No Adverts for Friends" msgstr "No Adverts for Friends" #: plugins/searchengine.php:72 msgid "Provides support for No Adverts for Friends." msgstr "No Adverts for Friends 外掛支援。" #: plugins/searchengine.php:78 msgid "No Adverts for Friends support is now %s" msgstr "No Adverts for Friends 支援 %s" #: plugins/wptouch.php:20 msgid "WPTouch" msgstr "WPTouch" #: plugins/wptouch.php:25 msgid "Provides support for WPTouch mobile theme and plugin." msgstr "WPTouch 行動裝置主題外掛支援。" #: plugins/wptouch.php:31 msgid "WPTouch support is now %s" msgstr "WPTouch 支援 %s" #: plugins/wptouch.php:45 msgid "WPTouch plugin detected! Please go to the Supercache plugins page and enable the WPTouch helper plugin." msgstr "WPTouch 外掛模組已被偵測到！請到 Supercache 外掛頁面啟用 WPTouch 支援外掛。" #: wp-cache-phase2.php:1209 msgid "Cache expiry cron job failed. Job will run again in 10 seconds." msgstr "執行清除過期快取的排程時失敗。將在十秒內再次執行。" #: wp-cache-phase2.php:1213 msgid "Cache expiry cron job took more than 30 seconds. You should probably run the garbage collector more often." msgstr "定時清除快取花費了超過三十秒以上的時間。你可能需要更常執行垃圾回收功能。" #: wp-cache-phase2.php:1222 msgid "[%1$s] WP Super Cache GC Report" msgstr "[%1$s] WP Super Cache 垃圾回收報告" #: wp-cache.php:99 msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "請以 wp-super-cache/wp-cache-config-sample.php 建立 %s /wp-cache-config.php" #: wp-cache.php:162 msgid "Warning! PHP Safe Mode Enabled!" msgstr "警告！PHP 安全模式已啟用！" #: wp-cache.php:163 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "在安全模式下，你的外掛可能會遭遇錯誤。" #: wp-cache.php:167 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "你的伺服器設定為先檢查 PHP 程式擁有者才可以存取檔案。" #: wp-cache.php:168 msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "你或管理員可以透過變更外掛程式群組的所有者使其與伺服器使用者一致，進而讓其運作。%s/cache/ 目錄的所有者也必須變更。查看安全模式使用手冊以取得更多說明。" #: wp-cache.php:170 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "你或管理員必須先停用此項目。查看安全模式使用手冊以取得更多說明。很抱歉，這無法在 .htaccess 檔案裡停用。它必須在 php.ini 設定檔中完成。" #: wp-cache.php:176 msgid "Permlink Structure Error" msgstr "固定網址結構錯誤" #: wp-cache.php:177 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "外掛要正常運作，必須有自定 url 或固定網址。請到固定網址選項設定你的固定網址。" #: wp-cache.php:189 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "警告！你的主機名稱 \"%s\" 解析到 %s" #: wp-cache.php:190 msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "你的伺服器認為你的主機名稱解析到 %s 。 WP Super Cache 外掛的某些服務，例如垃圾回收、WordPress 排程文章可能無法正常執行。" #: wp-cache.php:191 #: wp-cache.php:205 msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "請參閱 readme.txt 第 16 項錯誤排除段落" #: wp-cache.php:204 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "很抱歉，WordPress 找不到 wp-cron.php 檔案。必須要有這個程式才能正確執行垃圾回收、排程文章及其他重要活動。" #: wp-cache.php:218 msgid "Cannot continue... fix previous problems and retry." msgstr "無法繼續... 解決前述問題然後重試。" #: wp-cache.php:227 msgid "Zlib Output Compression Enabled!" msgstr "Zlib 輸出壓縮已被啟用！" #: wp-cache.php:228 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP頁面壓縮啟用中。建議將它關閉，因為外掛針對一個頁面只需要壓縮一次，而不需要反覆的壓縮。另請參見錯換排除段落第21條。 這邊有如何修改php.ini的說明。" #: wp-cache.php:232 msgid "Mod rewrite may not be installed!" msgstr "Mod rewrite 可能沒有安裝！" #: wp-cache.php:233 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "看來 mod_rewrite 沒有安裝。有時候這種檢查並非 100% 可信，特別是當你不是使用 Apache 時。請重新檢查 mod_rewrite 模組已經載入。執行 Super Cache 靜態檔案時必須要有它。但你仍然可以使用傳統或PHP快取模式。" #: wp-cache.php:239 msgid "Read Only Mode. Configuration cannot be changed." msgstr "唯讀模式。設定無法變更。" #: wp-cache.php:240 msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "WP Super Cache 設定檔 %s/wp-cache-config.php 無法修改。該檔案必須允許從伺服器端進行寫入以進行設定變更。" #: wp-cache.php:241 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "最簡單的方式是使用 CHMOD 指令或透過 FTP 程式來變更權限。請確保它們正確並可以寫入。" #: wp-cache.php:242 #: wp-cache.php:258 msgid "This page explains how to change file permissions." msgstr "這邊解釋如何變更檔案權限。" #: wp-cache.php:243 msgid "Writeable:" msgstr "可寫入：" #: wp-cache.php:244 msgid "Readonly:" msgstr "唯讀：" #: wp-cache.php:256 msgid "Warning! %s is writeable!" msgstr "警告！%s 可寫入！" #: wp-cache.php:257 msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "你應該變更 %s 權限使其更加嚴密。使用你的FTP程式，或是按照以下指令來解決：" #: wp-cache.php:267 msgid "Mobile rewrite rules detected" msgstr "偵測到行動裝置重寫規則" #: wp-cache.php:268 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "為了獲得最好的效能，你應該啟用\"行動裝置支援\"，或從你的 .htaccess 刪除行動裝置重寫規則。尋找包含 \"2.0\\ MMP|240x320\" 字串的兩行並刪除它們。" #: wp-cache.php:268 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "這不會對一般使用者造成任何影響，但行動裝置使用者將會看到未快取的頁面。" #: wp-cache.php:274 #: wp-cache.php:285 msgid "Rewrite rules must be updated" msgstr "Mod Rewrite 規則必須更新！" #: wp-cache.php:275 #: wp-cache.php:286 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "這個外掛所需的重寫規則已被變更或不存在。" #: wp-cache.php:276 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "行動裝置支援必須在你的 .htaccess 檔案裡新增額外規則，或是你可以將外掛設定為傳統模式。這是你的選擇（依難易度排列）：" #: wp-cache.php:277 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "將外掛設為傳統模式並開啟行動裝置支援。" #: wp-cache.php:278 #: wp-cache.php:287 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "捲動到進階選項頁面的下方並點擊更新 Mod_Rewrite 規則按鈕。" #: wp-cache.php:279 msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "從 %s.htaccess 內刪除 # BEGIN WPSuperCache 和 # END WPSuperCache 之間原始碼區段的 mod_rewrite 規則，之後重新載入本頁讓外掛再次產生規則。" #: wp-cache.php:280 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "自行加入規則。編輯 %s.htaccess 並找到 # BEGIN WPSuperCache 和 # END WPSuperCache 之間的原始碼區段。有兩個區段非常相似。緊接著 %%{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ 的下方新增這幾行(要做兩次，一個區段一次)：" #: wp-cache.php:293 msgid "Required to serve compressed supercache files properly." msgstr "需要此模組以正確提供 supercache 壓縮檔。" #: wp-cache.php:293 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "需要此模組以設定在 supercache 頁面的快取資訊。若無此模組，IE7使用者將會看到舊頁面。" #: wp-cache.php:293 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "設定 supercache 快取頁面過期時間。沒有這個模組，訪客在重新整理或留下迴響時可能看不到新頁面。" #: wp-cache.php:300 msgid "Missing Apache Modules" msgstr "Apache 模組遺失" #: wp-cache.php:301 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "以下的 Apache 模組遺失。沒有它們外掛將在傳統模式下工作。若在完整的 Supercache 模式，你的訪客可能會看到損壞的網頁或是過時的內容。" #: wp-cache.php:502 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "警告！ 你試著要開啟壓縮，但是 zlib.output_compression 已被啟用。 參見讀我檔案裡錯誤排除段落第21條。" #: wp-cache.php:598 msgid "WP Super Cache Settings" msgstr "WP Super Cache 狀態" #: wp-cache.php:612 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "注意：Mod_rewrite 或傳統快取已被開啟。 預設顯示進階選項頁面。" #: wp-cache.php:623 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "設定檔已變更，某些數值可能錯誤。再次從\"設定\"選單讀取頁面以重設選項。" #: wp-cache.php:655 msgid "Caching must be enabled to use this feature" msgstr "必須啟用快取才能使用這個功能" #: wp-cache.php:673 #: wp-cache.php:813 msgid "Cancel Cache Preload" msgstr "取消快取預先載入" #: wp-cache.php:681 msgid "Scheduled preloading of cache almost cancelled. It may take up to a minute for it to cancel completely." msgstr "預載快取排程即將取消。完全取消可能要花費至一分鐘。" #: wp-cache.php:692 msgid "Scheduled preloading of cache cancelled." msgstr "預載快取排程已被取消。" #: wp-cache.php:724 #: wp-cache.php:811 msgid "Preload Cache Now" msgstr "馬上開始預先載入" #: wp-cache.php:728 msgid "Scheduled preloading of cache in 10 seconds." msgstr "預載快取將在十秒之後開始。" #: wp-cache.php:733 msgid "Scheduled preloading of cache in %d minutes" msgstr "下次預載快取排程時間：%d分鐘後" #: wp-cache.php:737 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "這會快取你網站上所有已發布的文章和頁面。它會產生 supercache 靜態檔案，匿名訪客(包括機器人)會命中快取頁面。這有可能會對你的 Google 排名有幫助，因為他們也將網站速度納入衡量項目之一。" #: wp-cache.php:738 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "不過預先載入會產生很多檔案。快取會從最新的文章開始做到最早的文章，所以當你有非常多 (10,000+) 文章的時候，可能只會有新文章被快取到。這在共享主機上特別重要。" #: wp-cache.php:739 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "在「預先載入」模式，通常的垃圾回收只會清除給已知使用者的傳統快取檔案，而不會清除預先載入的 supercache 檔案。這是預先載入的建議設定。" #: wp-cache.php:743 msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "每 %s 分鐘更新預載快取檔案。(0 關閉，最低 %d 分鐘。)" #: wp-cache.php:756 msgid "all" msgstr "所有" #: wp-cache.php:769 msgid "Preload %s posts." msgstr "預先載入 %s 篇文章。" #: wp-cache.php:776 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "預先載入模式(只對傳統模式快取做垃圾回收。建議選項。)" #: wp-cache.php:779 msgid "Preload tags, categories and other taxonomies." msgstr "預載標籤，類別，以及其它的分類。" #: wp-cache.php:782 msgid "Send me status emails when files are refreshed." msgstr "當檔案被更新的時候寄信給我。" #: wp-cache.php:787 msgid "Many emails, 2 emails per 100 posts." msgstr "很多信件，每一百篇文章二封信。" #: wp-cache.php:790 msgid "Medium, 1 email per 100 posts." msgstr "中等，每一百篇文章一封信。" #: wp-cache.php:793 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "較少信件，開始的時候一封還有結束的時候一封。" #: wp-cache.php:797 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "在%d小時%d分鐘%d秒之後更新快取。" #: wp-cache.php:798 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "完整更新快取，耗費了 %d 小時 %d 分鐘 %d 秒。" #: wp-cache.php:804 msgid "Currently caching from post %d to %d." msgstr "目前正在快取第 %d 到 %d 篇文章。" #: wp-cache.php:808 msgid "Page last cached: %s" msgstr "最新快取頁面： %s" #: wp-cache.php:811 msgid "Update Settings" msgstr "更新狀態" #: wp-cache.php:819 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "預先載入已被關閉。請關閉傳統模式或和主機管理員連絡。" #: wp-cache.php:836 #: wp-cache.php:947 msgid "Caching" msgstr "快取" #: wp-cache.php:840 msgid "Cache hits to this website for quick access." msgstr "啟用快取以加速對本網站的存取" #: wp-cache.php:840 #: wp-cache.php:841 #: wp-cache.php:858 #: wp-cache.php:867 #: wp-cache.php:874 #: wp-cache.php:877 #: wp-cache.php:894 #: wp-cache.php:950 msgid "Recommended" msgstr "建議選項" #: wp-cache.php:841 msgid "Use mod_rewrite to serve cache files." msgstr "使用 mod_rewrite 快取" #: wp-cache.php:842 msgid "Use PHP to serve cache files." msgstr "使用 PHP 快取" #: wp-cache.php:843 msgid "Legacy page caching." msgstr "傳統快取模式" #: wp-cache.php:844 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching." msgstr "Mod_rewrite 快取是最快的，PHP 快取幾乎一樣快且較容易上手；傳統模式較慢，但是有更多的彈性且同樣容易上手。新使用者應該使用 PHP 快取。" #: wp-cache.php:850 msgid "Miscellaneous" msgstr "雜項" #: wp-cache.php:856 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "警告！因為找不到 gzencode() 函式，壓縮已被停用。" #: wp-cache.php:858 msgid "Compress pages so they’re served more quickly to visitors." msgstr "壓縮網頁，讓訪客能更快速觀看" #: wp-cache.php:859 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "壓縮預設為停用，因為某些主機在壓縮檔案時可能發生問題。啟用或停用這項功能會清除快取。" #: wp-cache.php:867 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 未修改支援。當一個頁面在上次被要求後沒有被更改的時候送出。" #: wp-cache.php:870 msgid "Warning! 304 browser caching is only supported when not using mod_rewrite caching." msgstr "警告! 304 瀏覽器快在不使用 mod_rewrite 快取時才能支援。" #: wp-cache.php:872 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "304 支援預設為停用，因為過去GoDaddy在它使用的某些檔頭會產生問題。" #: wp-cache.php:874 msgid "Don’t cache pages for known users." msgstr "不要為已知使用者快取。" #: wp-cache.php:875 msgid "Don’t cache pages with GET parameters. (?x=y at the end of a url)" msgstr "不快取使用 GET 參數的頁面。(結尾有 ?x=y 的網址)" #: wp-cache.php:876 msgid "Make known users anonymous so they’re served supercached static files." msgstr "讓已知使用者匿名化，以靜態快取檔案服務他們。" #: wp-cache.php:877 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "重建快取。當新檔案重建的時候，提供 supercache 檔案給匿名使用者。" #: wp-cache.php:878 msgid "Proudly tell the world your server is Stephen Fry proof! (places a message in your blog’s footer)" msgstr "告訴全世界你的伺服器不怕 Stephen Fry (一個名人)攻擊！（在你的部落格底部放置一段訊息）" #: wp-cache.php:884 #: wp-cache.php:1162 #: wp-cache.php:1778 msgid "Advanced" msgstr "進階選項" #: wp-cache.php:888 msgid "Mobile device support. (External plugin or theme required. See the FAQ for further details.)" msgstr "行動裝置支援 (需要外掛或額外的主題來支援。 參見常見問答以獲得更多資訊。)" #: wp-cache.php:890 msgid "Mobile Browsers" msgstr "行動瀏覽器" #: wp-cache.php:890 msgid "Mobile Prefixes" msgstr "行動前置字串" #: wp-cache.php:892 msgid "Remove UTF8/blog charset support from .htaccess file. Only necessary if you see odd characters or punctuation looks incorrect. Requires rewrite rules update." msgstr "從 .htaccess 中移除 UTF8 字元集支援。只在你看到奇怪的字元或錯誤的標點時才需要。必須更新重寫規則。" #: wp-cache.php:893 msgid "Clear all cache files when a post or page is published or updated." msgstr "當發布或更新文章、網誌分頁時清除所有快取。" #: wp-cache.php:894 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "額外的首頁檢查(有很小的機會導致首頁快取停止)。" #: wp-cache.php:895 msgid "Only refresh current page when comments made." msgstr "當迴響發佈時，只更新目前頁面。" #: wp-cache.php:896 msgid "List the newest cached pages on this page." msgstr "在本頁列出最新的快取頁面。" #: wp-cache.php:898 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "粗略檔案鎖定。你大概不會用到這個功能，但如果你的伺服器效能較差，開啟後可能會有所幫助。警告！可能在少數情況下鎖死你的伺服器！" #: wp-cache.php:900 msgid "Late init. Display cached files after WordPress has loaded. Most useful in legacy mode." msgstr "延遲初始化，在 WordPress 載入之後再顯示快取。通常使用在傳統模式。" #: wp-cache.php:902 msgid "Use object cache to store cached files." msgstr "使用 object 快取來儲存快取檔案。" #: wp-cache.php:902 msgid "(Experimental)" msgstr "(實驗選項)" #: wp-cache.php:904 msgid "DO NOT CACHE PAGE secret key: %s" msgstr "存取非快取頁面 密鑰： %s" #: wp-cache.php:910 msgid "Note:" msgstr "備註：" #: wp-cache.php:912 msgid "Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided." msgstr "請在外掛頁面反安裝此外掛。它將會在反安裝後將設定清除。如需手動介入，亦會提供簡單的指示。" #: wp-cache.php:913 msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "如果移除這個外掛，請確認目錄 %s 為伺服器可以寫入，advanced-cache.php 和 cache-config.php 檔案會自動刪除。（確認這些檔案是可寫入的，也是個好主意！）" #: wp-cache.php:914 msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "反安裝資訊請參見 readme.txt，尋找 \"How to uninstall WP Super Cache\" 標題。" #: wp-cache.php:915 msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "需要幫助？ 看看Super Cache 讀我檔案。 它包含了安裝資訊，常見問題及錯誤排除小技巧。另外在支援論壇上，你的問題可能也已經有人回答過了。" #: wp-cache.php:918 #: wp-cache.php:965 msgid "Update Status" msgstr "更新狀態" #: wp-cache.php:925 msgid "Accepted Filenames & Rejected URIs" msgstr "接受的檔案名稱和拒絕的 URI" #: wp-cache.php:950 msgid "Caching On" msgstr "開啟快取" #: wp-cache.php:951 msgid "Caching Off" msgstr "關閉快取" #: wp-cache.php:952 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "說明：啟用 PHP 快取，重建快取，以及行動裝置支援" #: wp-cache.php:962 msgid "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "注意：PHP 快取已被啟用，但偵測到 Supercache mod_rewrite 規則。快取檔案會用這些規則來服務。如果你的網站動作正常，你可以忽略這個訊息，否則請編輯站台安裝根目錄下的 .htaccess 檔以移除 SuperCache 規則。" #: wp-cache.php:967 msgid "Cache Tester" msgstr "快取測試" #: wp-cache.php:968 msgid "Test your cached website by clicking the test button below." msgstr "請按下面的測試按鈕以測試你的網站快取。" #: wp-cache.php:974 msgid "Fetching %s to prime cache: " msgstr "抓取 %s 至主要快取：" #: wp-cache.php:976 #: wp-cache.php:985 #: wp-cache.php:997 msgid "OK" msgstr "完成" #: wp-cache.php:979 msgid "Fetching first copy of %s: " msgstr "抓取第一份%s：" #: wp-cache.php:988 #: wp-cache.php:999 msgid "FAILED" msgstr "失敗" #: wp-cache.php:991 msgid "Fetching second copy of %s: " msgstr "抓取第二份%s：" #: wp-cache.php:1003 msgid "One or more page requests failed:" msgstr "一個或以上的頁面要求失敗：" #: wp-cache.php:1022 #: wp-cache.php:1023 msgid "Page %d: %d (%s)" msgstr "頁面 %d: %d (%s)" #: wp-cache.php:1029 msgid "Page 1: %s" msgstr "頁面1： %s" #: wp-cache.php:1030 msgid "Page 2: %s" msgstr "頁面2： %s" #: wp-cache.php:1031 msgid "The timestamps on both pages match!" msgstr "頁面時間標籤相符！" #: wp-cache.php:1033 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "無頁面時間標籤或標籤不相符！" #: wp-cache.php:1034 msgid "Things you can do:" msgstr "你可以做的事：" #: wp-cache.php:1035 msgid "Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match." msgstr "在已登出的瀏覽器載入你的首頁，檢查html結尾的時間標籤，並再次載入頁面並比較時間標籤。快取如果有效時間標籤會是一致的。" #: wp-cache.php:1036 msgid "Enable logging on the Debug page here. That should help you track down the problem." msgstr "在本除錯頁面開啟記錄功能，應該可以幫助你找出問題所在。" #: wp-cache.php:1037 msgid "You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself." msgstr "檢查上面第一頁及第二頁的錯誤。你的本機伺服器設定可能不允許你的網站存取自己本身。" #: wp-cache.php:1045 msgid "Send non-secure (non https) request for homepage" msgstr "以非加密 (非 https) 傳輸請求首頁" #: wp-cache.php:1046 msgid "Test Cache" msgstr "測試快取" #: wp-cache.php:1050 msgid "Delete Cached Pages" msgstr "刪除快取頁面" #: wp-cache.php:1051 msgid "Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below." msgstr "快取頁面以 html 和 PHP 檔案的形式儲存在你的伺服器上。如果你需要刪除它們，請按下面的按鈕。" #: wp-cache.php:1054 #: wp-cache.php:2316 #: wp-cache.php:2335 #: wp-cache.php:2506 #: wp-cache.php:3030 msgid "Delete Cache" msgstr "刪除快取" #: wp-cache.php:1061 #: wp-cache.php:2322 msgid "Delete Cache On All Blogs" msgstr "刪除所有部落格的快取頁面" #: wp-cache.php:1066 msgid "Recommended Links and Plugins" msgstr "建議連結及外掛" #: wp-cache.php:1067 msgid "Caching is only one part of making a website faster. Here are some other plugins that will help:" msgstr "快取只是讓網站變快的方法之一。這邊是一些其它有幫助的外掛：" #: wp-cache.php:1068 msgid "WPSCMin, a Supercache plugin that minifies cached pages by removing whitespaces and extra characters " msgstr "WPSCMin，一個 Supercache 的外掛，藉由移除多餘的空白和無用的字元將頁面最小化。" #: wp-cache.php:1069 msgid "Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix." msgstr "Yahoo! Yslow 是 Firefox 附加元件 Firebug 的一個延伸套件。它可以分析你的網頁，並根據一些高效率網頁規則，建議你增加效能的方式。 你也可以試試一個線上效能分析工具 GTMetrix。" #: wp-cache.php:1070 msgid "Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score." msgstr "Use Google Libraries可以讓你從 Google 的伺服器上載入一些常用的 Javascript 函式庫。很諷刺的是它會降低你的 Yslow 分數。" #: wp-cache.php:1072 msgid "Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules." msgstr "進階使用者專用： 使用快取及快取控制加速你的網站，解釋怎麼讓你的網站更適用 .htaccess 規則來進行快取。" #: wp-cache.php:1073 msgid "Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others." msgstr "進階使用者專用： 安裝物件快取。 你可以從 Memcached、XCache、eAcccelerator 或其它的加速器中選擇一個。" #: wp-cache.php:1074 msgid "Cron View is a useful plugin to use when trying to debug garbage collection and preload problems." msgstr "Cron View 外掛，在你想要針對垃圾回收及預先載入問題除錯時相當有用。" #: wp-cache.php:1085 msgid "Make WordPress Faster" msgstr "讓 WordPress 更快速" #: wp-cache.php:1086 msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s由%2$s開發及維護，並得到許多人的幫助貢獻。" #: wp-cache.php:1087 msgid "He blogs at %1$s and posts photos at %2$s." msgstr "我的部落格在 %1$s，相簿在 %2$s。繁體中文翻譯問題請洽priv" #: wp-cache.php:1088 msgid "Please say hi to him on %s too!" msgstr "在%s上向我問好！" #: wp-cache.php:1089 msgid "Need Help?" msgstr "需要幫助?" #: wp-cache.php:1091 msgid "Use the debug system in the Debug tab above. It will tell you what the plugin is doing." msgstr "請使用上方除錯分頁的除錯系統，它會告訴你這個外掛的功能。" #: wp-cache.php:1092 msgid "Installation Help" msgstr "安裝指南" #: wp-cache.php:1093 msgid "Frequently Asked Questions" msgstr "常見問題" #: wp-cache.php:1094 msgid "Support Forum" msgstr "支援論壇" #: wp-cache.php:1096 msgid "Rate This Plugin!" msgstr "為這個外掛評分！" #: wp-cache.php:1097 msgid "Please rate this plugin and tell me if it works for you or not. It really helps development." msgstr "請為這個外掛評分，並告訴我它是否運作正常。這對開發非常有幫助。" #: wp-cache.php:1106 msgid "Cached pages since %1$s : %2$s" msgstr "快取頁面自 %1$s ：%2$s" #: wp-cache.php:1107 msgid "Newest Cached Pages:" msgstr "最新的快取頁面：" #: wp-cache.php:1111 msgid "Cached %s seconds ago" msgstr "於 %s 秒前快取" #: wp-cache.php:1114 msgid "(may not always be accurate on busy sites)" msgstr "（在忙碌的網站上未必準確）" #: wp-cache.php:1133 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "快取外掛是 wp-super-cache 裡 plugin 資料夾中的一些 PHP 程式。它們在 Supercache 載入的時候就會被載入，比一般的 WordPress plugin 要早得多。" #: wp-cache.php:1134 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "這是一個非常進階的功能，只有對 PHP 和 Wordpress 動作都非常了解的人才能撰寫。" #: wp-cache.php:1135 msgid "Warning! Due to the way WordPress upgrades plugins the plugins you upload to wp-super-cache/plugins/ will be deleted when you upgrade WP Super Cache. You can avoid this by loading the plugins from elsewhere. Set $wp_cache_plugins_dir to the new location in wp-config.php and WP Super Cache will look there instead.
    More info available in the developer documentation." msgstr "警告！ 肇因於 WordPress 升級外掛的方式，上傳至 wp-super-cache/plugins 的外掛在升級 WP Super Cache 將會被刪除。你可以把外掛放到別的地方以避免此一問題。在 wp-config.php 中設定 $wp_cache_plugins_dir 至新的位置，WP Super Cache 將會改用此一新位置。
    開發者文件中有更多的資訊。" #: wp-cache.php:1145 msgid "Available Plugins" msgstr "可使用的外掛" #: wp-cache.php:1162 msgid "Easy" msgstr "簡易模式" #: wp-cache.php:1162 msgid "CDN" msgstr "CDN" #: wp-cache.php:1162 msgid "Contents" msgstr "內容" #: wp-cache.php:1162 msgid "Preload" msgstr "預先載入" #: wp-cache.php:1162 msgid "Plugins" msgstr "外掛" #: wp-cache.php:1162 msgid "Debug" msgstr "除錯設定" #: wp-cache.php:1197 msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "注意：除非在這個網路的主站上執行，WP Super Cache mod_rewrite 規則檢查會被關閉。s" #: wp-cache.php:1206 msgid "Mod Rewrite Rules" msgstr "Mod Rewrite 規則" #: wp-cache.php:1212 msgid "WordPress MU Detected" msgstr "偵測到 WordPress MU" #: wp-cache.php:1212 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "抱歉，當執行 WordPress MU 時重寫規則無法自動更新。請開啟你的 .htaccess，並在上述檔案中任何位置加入下方的 mod_rewrite 規則。" #: wp-cache.php:1214 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite 規則無法更新！" #: wp-cache.php:1215 msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "要讓它自動工作，你必須在 %s.htaccess 上有 BEGIN 和 END 標記，它們看起來像這樣，圍繞 WordPress 的主要 mod_rewrite 規則：" #: wp-cache.php:1217 msgid "Refresh this page when you have updated your .htaccess file." msgstr "當你已更新你的 .htaccess 檔案後重新整理此頁。" #: wp-cache.php:1221 msgid "Thank you for upgrading." msgstr "感謝升級。" #: wp-cache.php:1221 msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "從你上次安裝此外掛，mod_rewrite 規則已經變更。在新的 supercache 規則更新前，你必須先刪除舊的 supercache 規則。在你修改你的 .htaccess 檔案後重新整理此頁。如果你希望手動更新，更改以下幾行：%1$s 使它看起來像這樣：%2$s ，唯一改變的地方是 \"HTTP_COOKIE\" 變成 \"HTTP:Cookie\" 以及 \"wordpressuser\" 變成 \"wordpress\"。這是 WordPress 2.5 的改變，但如果你敢使用，它與舊版本相容。" #: wp-cache.php:1225 msgid "Trailing slash check required." msgstr "尾端斜線的檢查是必須的。" #: wp-cache.php:1225 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "看起來你的部落格有以\"/\"結束的 URL。不幸地在你安裝這個外掛後，在URL不是以\"/\"結束的頁面，發現了一個重複內容的 bug，也就是相同的內容卻不是被指向正確的 URL。你必須修改你的 .htaccess 檔案以修復這個問題，在兩個 Super Cache 規則區段內新增下面兩個規則：" #: wp-cache.php:1227 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "你可以看到規則去向，透過點選下方的「查看 mod_rewrite 規則」連結來看到完整的規則" #: wp-cache.php:1241 msgid "Mod Rewrite rules updated!" msgstr "Mod Rewrite 規則已更新！" #: wp-cache.php:1242 msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "%s.htaccess 已更新必要的 mod_rewrite 規則。請確保它們是正確的。它們應該像這樣：" #: wp-cache.php:1244 msgid "Mod Rewrite rules must be updated!" msgstr "Mod Rewrite 規則必須更新！" #: wp-cache.php:1245 msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "你的 %s.htaccess 無法由伺服器寫入，必須更新 mod_rewrite 規則。新的規則必須在一般的 WordPress 規則之上，如下面的原始碼所示：" #: wp-cache.php:1250 msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "在你的 %s.htaccess 檔案中已經檢測到 WP Super Cache 重寫規則。
    點選以下連結，查看新增到該檔案的內容。如果你已經升級外掛，請確保與這些規則相同。" #: wp-cache.php:1253 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "發現 .htaccess 的 rewrite 規則和外掛 rewrite 規則的不一致。有可能只是單純空白字元的差別，但是你應該立即比較以下的規則。 點擊「更新 Mod_Rewrite 規則」按鈕以更新規則。" #: wp-cache.php:1255 msgid "View Mod_Rewrite Rules" msgstr "查看 Mod_Rewrite 規則" #: wp-cache.php:1261 #: wp-cache.php:2622 msgid "Rules must be added to %s too:" msgstr "也必須新增到 %s 的規則：" #: wp-cache.php:1268 msgid "Gzip encoding rules in %s.htaccess created." msgstr "%s.htaccess 內 gzip 規則建立。" #: wp-cache.php:1275 msgid "Fix Configuration" msgstr "修復設定" #: wp-cache.php:1278 msgid "Restore Default Configuration" msgstr "還原到預設選項" #: wp-cache.php:1286 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "迴響審核已啟用。您的迴響可能需要一些時間才會顯示。" #: wp-cache.php:1311 msgid "Lock Down:" msgstr "鎖定：" #: wp-cache.php:1312 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "如果你預測會有流量高峰到來時，可以啟用鎖定功能。當這個功能啟用時，在文章裡發佈新迴響將不會更新靜態快取檔案。" #: wp-cache.php:1313 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "開發者：透過檢查 \"WPLOCKDOWN\"，讓你的外掛與鎖定功能相容。下面的原始碼將確保你的外掛遵守 WPLOCKDOWN 設定。" #: wp-cache.php:1315 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "抱歉。我的部落格已經鎖定。將會在短時間後更新。" #: wp-cache.php:1319 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress 已鎖定。新的迴響產生時將不會刪除 Super Cache 靜態快取檔案。" #: wp-cache.php:1321 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress 未鎖定。新的迴響產生時將會正常更新 Super Cache 靜態快取檔案。" #: wp-cache.php:1327 msgid "Lock Down" msgstr "鎖定" #: wp-cache.php:1335 msgid "Directly Cached Files" msgstr "直接快取檔案" #: wp-cache.php:1393 msgid "%s removed!" msgstr "%s 已移除！" #: wp-cache.php:1401 msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "啟用這項功能前必須確認 %s 是可寫入狀態。由於這牽涉到一個安全風險，請在你的網頁產生後把它設為唯讀。" #: wp-cache.php:1406 msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s 可寫入。由於這牽涉到一個安全風險，請在你的網頁產生後把它設為唯讀。" #: wp-cache.php:1421 msgid "Existing direct page" msgstr "已存在的直接頁面" #: wp-cache.php:1421 msgid "Delete cached file" msgstr "刪除快取檔案" #: wp-cache.php:1426 msgid "Add direct page:" msgstr "新增直接頁面：" #: wp-cache.php:1428 msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "直接快取檔案是從你的部落格 %s 產生直接建立的檔案。這項功能只在你預測將會有從 Digg 或 Slashdot 大量流量進入某篇文章或頁面時才有用。" #: wp-cache.php:1430 msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "舉例來說：快取 %1$sabout/, 你應該輸入 %1$sabout/ 或 /about/ 。快取檔案將在下一個匿名使用者訪問該頁面時產生。" #: wp-cache.php:1431 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "將輸入框清空，就能將它從直接頁面清單中移除並刪除快取檔案。" #: wp-cache.php:1436 msgid "Update Direct Pages" msgstr "更新直接頁面" #: wp-cache.php:1464 msgctxt "timezone date format" msgid "Y-m-d G:i:s" msgstr "Y-m-d G:i:s" #: wp-cache.php:1523 msgid "Expiry Time & Garbage Collection" msgstr "過期時間與垃圾回收" #: wp-cache.php:1525 msgid "UTC time is %s" msgstr "UTC 時間是 %s" #: wp-cache.php:1528 msgid "Local time is %1$s" msgstr "本地時間是 %1$s" #: wp-cache.php:1532 msgid "Next scheduled garbage collection will be at %s UTC" msgstr "下次垃圾回收排程時間 %s UTC" #: wp-cache.php:1536 msgid "Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age." msgstr "警告 預載模式 已被啟用。Supercache檔案將不會由於過期而被刪除。" #: wp-cache.php:1553 msgid "Cache Timeout" msgstr "快取逾時" #: wp-cache.php:1554 #: wp-cache.php:1557 msgid "seconds" msgstr "秒" #: wp-cache.php:1555 msgid "How long should cached pages remain fresh? Set to 0 to disable garbage collection. A good starting point is 3600 seconds." msgstr "設定快取的有效期限。設定 0 以關閉垃圾回收功能。可以從 3600 秒先開始嘗試。" #: wp-cache.php:1556 msgid "Scheduler" msgstr "排程器" #: wp-cache.php:1556 msgid "Timer:" msgstr "計時：" #: wp-cache.php:1557 msgid "Check for stale cached files every interval seconds." msgstr "每隔幾秒檢查失效的快取檔案。" #: wp-cache.php:1558 msgid "Clock:" msgstr "時刻：" #: wp-cache.php:1559 msgid "HH:MM" msgstr "HH:MM (時:分)" #: wp-cache.php:1559 msgid "Check for stale cached files at this time (UTC) or starting at this time every interval below." msgstr "在下列時間 (UTC) 檢查失效快取，或從此時間開始每段間隔檢查。" #: wp-cache.php:1561 msgid "Interval:" msgstr "間隔：" #: wp-cache.php:1567 msgid "Notification Emails" msgstr "通知郵件" #: wp-cache.php:1568 msgid "Email me when the garbage collection runs." msgstr "在垃圾回收執行時寄 email 給我。" #: wp-cache.php:1570 msgid "Garbage Collection" msgstr "垃圾回收" #: wp-cache.php:1571 msgid "Garbage collection is the simple act of throwing out your garbage. For this plugin that would be old or stale cached files that may be out of date. New cached files are described as fresh." msgstr "垃圾回收就是將你的垃圾丟掉的簡單動作。以此外掛來說，垃圾就是指舊的或失效 (stale) 的檔案。新的快取檔案則稱為有效 (fresh) 快取。" #: wp-cache.php:1572 msgid "Cached files are fresh for a limited length of time. You can set that time in the Cache Timeout text box on this page." msgstr "快取檔案有一定限度的有效期限。你可以在本頁的快取逾時文字方塊設定這個期限。" #: wp-cache.php:1573 msgid "Stale cached files are not removed as soon as they become stale. They have to be removed by the garbage collecter. That is why you have to tell the plugin when the garbage collector should run." msgstr "失效的快取檔案並不會在失效的時候馬上就被移除。他們必須被垃圾回收機制移除。這就是為什麼你必須告訴外掛何時執行垃圾回收。" #: wp-cache.php:1574 msgid "Use the Timer or Clock schedulers to define when the garbage collector should run." msgstr "使用計時或時刻來決定何時執行垃圾回收。" #: wp-cache.php:1575 msgid "The Timer scheduler tells the plugin to run the garbage collector at regular intervals. When one garbage collection is done, the next run is scheduled." msgstr "計時排程器以一定的時間間隔執行垃圾回收。當一次垃圾回收完成後，就會再度進行下一次的排程。" #: wp-cache.php:1576 msgid "Or, the Clock scheduler allows the garbage collection to run at specific times. If set to run hourly or twicedaily the garbage collector will be first scheduled for the time you enter here. It will then run again at the indicated interval. If set to run daily it will run once a day at the time specified." msgstr "而時刻排程器，可以讓外掛在指定的時刻執行垃圾回收。如果設定為每小時 (hourly) 或兩天一次 (twicedaily) 執行，垃圾回收會在你輸入的時刻第一次被執行，接下來會在設定的間隔時間後再執次行。如果設定為每日 (daily) 執行，那他會在每天你設定的時刻執行一次。" #: wp-cache.php:1578 msgid "There are no best garbage collection settings but here are a few scenarios. Garbage collection is separate to other actions that clear our cached files like leaving a comment or publishing a post." msgstr "並沒有最佳的垃圾回收設定，不過這裡列出幾個情境。垃圾回收和其它會造成清除快取的情形，例如留言和發佈文章，是有區別的。" #: wp-cache.php:1580 msgid "Sites that want to serve lots of newly generated data should set the Cache Timeout to 60 and use the Timer scheduler set to 90 seconds." msgstr "希望提供大量動態資料的站台，應該將快取逾時設定為 60 秒，並使用 90 秒的計時排程。" #: wp-cache.php:1581 msgid "Sites with widgets and rss feeds in their sidebar should probably use a timeout of 3600 seconds and set the timer to 600 seconds. Stale files will be caught within 10 minutes of going stale." msgstr "在邊欄有小工具及 rss 饋料的站台，也許應該設定 3600 的逾時，以及 600 秒的計時排程。失效的檔案會在失效十分鐘後被清除。" #: wp-cache.php:1582 msgid "Sites with lots of static content, no widgets or rss feeds in their sidebar can use a timeout of 86400 seconds or even more and set the timer to something equally long." msgstr "有大量靜態內容，邊欄沒有小工具及 rss 饋料的站台，可以使用 86400 或更長的逾時，並將計時排程設定為等長的時間。" #: wp-cache.php:1583 msgid "Sites where an external data source updates at a particular time every day should set the timeout to 86400 seconds and use the Clock scheduler set appropriately." msgstr "在每天固定時刻使用外部資料來源更新的站台，則應該將逾時設為86400秒，並將時刻排程設定在適當的時間。" #: wp-cache.php:1585 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 600 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "檢查和刪除過期檔案代價高昂，但把這些檔案留在那裡也一樣。在非常忙碌的網站，你應該將過期時間設定為 600 秒。嘗試使用不同的數值，並注意這些頁面一天裡在不同時段產生多少過期檔案，如果使用傳統快取，可能的話盡量不要讓快取檔案數多於 500 個。若使用 mod_rewrite 或 PHP 快取，快取數量可以增加數倍。" #: wp-cache.php:1586 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "把過期時間設定為 0 以關閉垃圾回收功能" #: wp-cache.php:1587 msgid "Change Expiration" msgstr "變更過期時間" #: wp-cache.php:1631 msgid "Rejected User Agents" msgstr "被拒絕的使用者代理（User Agents）" #: wp-cache.php:1632 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "HTTP User Agent；防止快取機器人、蜘蛛或抓取器對於 WP-Cache 的請求。請注意，如果快取檔案已經存在，仍然會發送給這些代理。" #: wp-cache.php:1639 msgid "Save UA Strings" msgstr "儲存 UA 字串" #: wp-cache.php:1662 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "不快取以下頁面類型。查看條件標籤文件中對每個類型的完整探討。" #: wp-cache.php:1665 msgid "Single Posts" msgstr "單篇文章" #: wp-cache.php:1666 msgid "Pages" msgstr "網誌分頁" #: wp-cache.php:1667 msgid "Front Page" msgstr "首頁" #: wp-cache.php:1668 msgid "Home" msgstr "主頁" #: wp-cache.php:1669 msgid "Archives" msgstr "存檔" #: wp-cache.php:1670 msgid "Tags" msgstr "標籤" #: wp-cache.php:1671 msgid "Category" msgstr "分類" #: wp-cache.php:1672 msgid "Feeds" msgstr "訂閱" #: wp-cache.php:1673 msgid "Search Pages" msgstr "搜尋頁面" #: wp-cache.php:1674 msgid "Author Pages" msgstr "作者頁面" #: wp-cache.php:1676 #: wp-cache.php:1788 msgid "Save" msgstr "儲存" #: wp-cache.php:1693 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "在下方輸入框內新增字串（不是檔案名稱），控制不要被快取的頁面。舉例來說，如果你的 URL 中包含年份，但你不想快取去年的文章，那麼就指定年份，例如 ’/2004/’ 。WP-Cache 將會搜尋這個字串是否包含在URI之中，如果是的話則不會快取這個頁面。" #: wp-cache.php:1699 msgid "Save Strings" msgstr "儲存字串" #: wp-cache.php:1715 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "這是可以被快取的檔案名，即使它們與上方設定的拒絕字串相符時也仍將被快取。" #: wp-cache.php:1721 msgid "Save Files" msgstr "儲存檔案" #: wp-cache.php:1762 msgid "Currently logging to: %s" msgstr "正在記錄到：%s" #: wp-cache.php:1765 msgid "Fix problems with the plugin by debugging it here. It can log them to a file in your cache directory." msgstr "在這裡使用外掛除錯模式解決問題。它可以在你的快取目錄內產生紀錄檔。" #: wp-cache.php:1769 msgid "Debugging" msgstr "除錯" #: wp-cache.php:1770 msgid "IP Address" msgstr "IP位址" #: wp-cache.php:1770 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "（僅記錄來自此IP位址的請求。你的 IP 是 %s）" #: wp-cache.php:1771 msgid "Cache Status Messages" msgstr "快取狀態訊息" #: wp-cache.php:1772 msgid "Display comments at the end of every page like this:" msgstr "顯在每頁的頁尾顯示像這樣的評論：" #: wp-cache.php:1778 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "在極少數的部落格可能會出現兩個問題：
    1. 在首頁可能會以一個 zip 檔案開始下載。
    2. 如果你的部落格使用一個靜態的首頁，或以 /%category%/%postname%/ 作為固定網址結架構的話，那麼錯誤的頁面有時候會被當成首頁被快取起來。
    " #: wp-cache.php:1779 msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "我有十足的把握肯定，它們不是 WP Super Cache 的錯誤。它只會發生在極少數的情況下，但如果你擔心的話，你可以每5分鐘進行一次簡單的檢查，以確保你的網站是正常的。如果有問題，你將會收到電子郵件。" #: wp-cache.php:1781 msgid "Check front page every 5 minutes." msgstr "每五分鐘檢查首頁" #: wp-cache.php:1782 msgid "Front page text" msgstr "首頁文字" #: wp-cache.php:1782 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "在你的首頁裡要搜尋的文字。如果缺少這些文字時快取將被清除。保留空白停用這個功能。" #: wp-cache.php:1783 msgid "Clear cache on error." msgstr "清除快取時發生錯誤。" #: wp-cache.php:1784 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "當檢查時寄送電子郵件給網站管理員。（供測試用）" #: wp-cache.php:1798 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "錯誤：GZIP 壓縮已啟用，如果你想啟用 wp-cache，請停用它。" #: wp-cache.php:1845 #: wp-cache.php:1986 #: wp-cache.php:2022 msgid "Warning" msgstr "警告" #: wp-cache.php:1845 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "在 WordPress 上 GZIP 壓縮已啟用，wp-cache 將被繞過，直到你停用 gzip 壓縮。" #: wp-cache.php:1907 #: wp-cache.php:1912 #: wp-cache.php:1945 #: wp-cache.php:1950 #: wp-cache.php:1956 msgid "Error" msgstr "錯誤" #: wp-cache.php:1907 msgid "Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions." msgstr "你的快取目錄（%1$s）不存在，且無法從伺服器端建立。請檢查 %1$s 權限。" #: wp-cache.php:1912 msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "你的快取目錄（%1$s）或 %2$s 必須讓外掛可寫入才能正常運作。請重新檢查一次。" #: wp-cache.php:1945 msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "你的 WP-Cache 設定檔（%s）已經過期，且無法由伺服器端寫入，請刪除它並重新整理此頁面。" #: wp-cache.php:1950 msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "設定檔遺失，%1$s 目錄（%2$s）也無法被伺服器寫入。請檢查權限。" #: wp-cache.php:1956 msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "WP-Cache 設定檔範本（%s）不存在。請確認你的安裝。" #: wp-cache.php:1986 msgid "Could not update %s! WPCACHEHOME must be set in config file." msgstr "無法更新 %s！ WPCACHEHOME 必須在設定檔中被設定。" #: wp-cache.php:2022 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php 不存在或是無法更新。" #: wp-cache.php:2023 msgid "1. If it already exists please delete the file first." msgstr "1. 如果它已經存在，請先刪除。" #: wp-cache.php:2024 msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. 請使用你的FTP程式或伺服器軟體，以 chmod 指令使%1$s可寫入。（chmod 777 %1$s），並重新整理此頁面。這只是一個暫時的作法，你事後必須再把它變更為唯讀。（使用前面的指令，將權限從 777 變更為 755）" #: wp-cache.php:2025 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. 重新整理此頁面以更新 %s/advanced-cache.php" #: wp-cache.php:2026 msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "如果無法運作，請確認 %s/advanced-cache.php 檔案不存在：" #: wp-cache.php:2027 msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. 以文字編輯器開啟 %1$s$wp_cache_file。
  • 2. 將 CACHEHOME 變更為 %2$s
  • 3. 儲存檔案並複製為 %3$s，然後重新整理此頁面。
    • " #: wp-cache.php:2050 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    WP_CACHE 變數被設為 false

    WP_CACHE 變數被WordPress用來載入快取程式，可是它被設為 false(關閉)。請編輯你的 wp-config.php 檔並把以下的內容放在最後的 require_once 命令之前。

    define('WP_CACHE', true);

    " #: wp-cache.php:2052 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "錯誤：在你的 wp-config.php 檔案裡 WP_CACHE 是停用狀態，且無法修改。" #: wp-cache.php:2053 msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "編輯 %s 並加入以下原始碼：
    define('WP_CACHE', true);
    否則，WP-Cache 將無法被 WordPress 核心執行。" #: wp-cache.php:2057 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the Troubleshooting Guide. The WP_CACHE line must be moved up." msgstr "

    WP_CACHE 不斷被新增到 wp-config.php

    如果你持續看到此警告訊息，請參閱 常見問答 第五點。WP_CACHE 原始碼必須往前移動。" #: wp-cache.php:2085 msgid "Cache Contents" msgstr "快取內容" #: wp-cache.php:2088 msgid "Object cache in use. No cache listing available." msgstr "正在使用 Object 快取。無法顯示快取清單。" #: wp-cache.php:2112 msgid "Deleting supercache file: %s
    " msgstr "刪除 supercache 檔案：%s
    " #: wp-cache.php:2129 msgid "Deleting wp-cache file: %s
    " msgstr "刪除 wp-cache 檔案：%s
    " #: wp-cache.php:2194 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "快取統計不會自動產生，你必須點擊以下的連結，本頁的統計資料才會重新產生。" #: wp-cache.php:2195 msgid "Regenerate cache stats" msgstr "重新產生快取統計" #: wp-cache.php:2197 msgid "Cache stats last generated: %s minutes ago." msgstr "快取統計最後產生時間：%s分鐘以前。" #: wp-cache.php:2203 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:2204 #: wp-cache.php:2219 msgid "%s Cached Pages" msgstr "%s 個頁面已快取" #: wp-cache.php:2205 #: wp-cache.php:2224 msgid "%s Expired Pages" msgstr "%s 個頁面已過期" #: wp-cache.php:2218 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:2228 msgid "Fresh WP-Cached Files" msgstr "有效的 WP-Cached 檔案" #: wp-cache.php:2229 #: wp-cache.php:2245 #: wp-cache.php:2261 #: wp-cache.php:2277 msgid "URI" msgstr "URI 網址" #: wp-cache.php:2229 #: wp-cache.php:2245 msgid "Key" msgstr "關鍵字" #: wp-cache.php:2229 #: wp-cache.php:2245 #: wp-cache.php:2261 #: wp-cache.php:2277 msgid "Age" msgstr "時間(秒)" #: wp-cache.php:2229 #: wp-cache.php:2245 #: wp-cache.php:2261 #: wp-cache.php:2277 msgid "Delete" msgstr "刪除" #: wp-cache.php:2244 msgid "Stale WP-Cached Files" msgstr "失效的 WP-Cached 檔案" #: wp-cache.php:2260 msgid "Fresh Super Cached Files" msgstr "有效的 Super Cached 檔案" #: wp-cache.php:2276 msgid "Stale Super Cached Files" msgstr "失效的 Super Cached 檔案" #: wp-cache.php:2292 msgid "Hide file list" msgstr "隱藏檔案清單" #: wp-cache.php:2294 msgid "Too many cached files, no listing possible." msgstr "快取檔案過多，無法列出。" #: wp-cache.php:2296 msgid "List all cached files" msgstr "列出所有快取檔案" #: wp-cache.php:2299 msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "過期檔案是超過 %s 秒鐘的檔案。它們仍然會被外掛使用並會定期刪除。" #: wp-cache.php:2310 msgid "Delete Expired" msgstr "刪除過期檔案" #: wp-cache.php:2335 msgid "Delete Super Cache cached files (opens in new window)" msgstr "刪除 Super Cache 快取檔案（在新視窗打開）" #: wp-cache.php:2482 msgid "%1$s is Stephen Fry proof thanks to caching by %2$s" msgstr "%1$s 使用的快取程式為 %2$s" #: wp-cache.php:2515 msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache 必須設定。請前往管理後台啟用和設定外掛。" #: wp-cache.php:2521 msgid "Settings" msgstr "設定" #: wp-cache.php:2531 msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache 停用。請前往 外掛管理員啟用快取。" #: wp-cache.php:2534 msgid "Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct." msgstr "警告！ WP Super Cache 快取毀損！ advanced-cache.php 腳本無法載入 wp-cache-phase1.php。

    請編輯 %1$s/advanced-cache.php 並且確認指向 %2$swp-cache-phase1.php 的路徑是正確的。" #: wp-cache.php:2553 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] 首頁已使用 gzip 壓縮！請清除快取！" #: wp-cache.php:2553 msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "請前往 %s 清除快取，網站的首頁正在下載！" #: wp-cache.php:2556 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] 首頁已使用 gzip 壓縮！快取已清除！" #: wp-cache.php:2556 msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "你的部落格快取已被清除。因為你的部落格首頁正在下載，請前往 %s 確認快取已被清除。" #: wp-cache.php:2563 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] 首頁不正確！請清除快取！" #: wp-cache.php:2563 msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "請前往 %1$s 清除快取，部落格的首頁不正確，缺少文字 \"%2$s\"！" #: wp-cache.php:2566 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] 首頁不正確！快取已清除！" #: wp-cache.php:2566 msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "你的部落格已被清除快取，因為你的部落格首頁缺少文字 \"%2$s\"。請前往 %1$s 確認快取已被清除。" #: wp-cache.php:2571 msgid "[%s] Front page check!" msgstr "[%s] 首頁檢查！" #: wp-cache.php:2571 msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache 已檢查過你部落格的首頁。如果你想停用這項功能，請前往 %s 。" #: wp-cache.php:2614 msgid "Cannot update .htaccess" msgstr "無法更新 .htaccess" #: wp-cache.php:2614 msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "%s.htaccess 檔案無法被網頁伺服器更新。請使用 chmod 指令或透過 FTP 程式修正。" #: wp-cache.php:2614 msgid "Refresh this page when the file permissions have been modified." msgstr "在權限修改後請重新整理這個頁面。" #: wp-cache.php:2614 msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "或者，你可以手動編輯 %s.htaccess 檔案並加入以下原始碼（在任何 WordPress 規則前）：" #: wp-cache.php:2618 msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "為了使用靜態的 HTML 檔案，你的伺服器上必須有正確的 mod_rewrite 規則，新增到一個名為 %s.htaccess 的檔案。" #: wp-cache.php:2619 msgid "You can edit the file yourself add the following rules." msgstr "你可以自行編輯並新增以下規則。" #: wp-cache.php:2620 msgid " Make sure they appear before any existing WordPress rules. " msgstr "確認它們出現在任何已存在的 WordPress 規則之前。" #: wp-cache.php:2628 msgid "Update Mod_Rewrite Rules" msgstr "更新 Mod_Rewrite 規則" #: wp-cache.php:2780 msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] 快取預載已經開始" #: wp-cache.php:2810 msgid "[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d" msgstr "[%1$s] 更新 %2$s 分類第%3$d 到 %4$d 篇文章" #: wp-cache.php:2856 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] 更新第 %2$d 到第 %3$d 篇文章" #: wp-cache.php:2877 msgid "[%1$s] Cache Preload Stopped" msgstr "[%1$s] 快取預載已停止" #: wp-cache.php:2887 msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s]%2$d 篇文章已被更新" #: wp-cache.php:2887 msgid "Refreshed the following posts:" msgstr "已更新下列文章：" #: wp-cache.php:2897 msgid "Scheduling next preload refresh in %d minutes." msgstr "下次更新預載快取時間：%d分鐘後" #: wp-cache.php:2908 msgid "[%s] Cache Preload Completed" msgstr "[%s] 預載快取完成" #: wp-cache.php:2908 msgid "Cleaning up old supercache files." msgstr "清除舊的 supercache 檔案。" #: wp-cache.php:2951 msgid "[%s] Preload may have stalled." msgstr "[%s] 預先載入可能已經停止" #: wp-cache.php:2951 msgid "" "Preload has been restarted.\n" "%s" msgstr "" "預先載入已經被重新啟動.\n" "%s" #: wp-cache.php:2994 msgid "Supercache Uninstall Problems" msgstr "Supercache 反安裝問題" #: wp-cache.php:2994 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" msgstr "" "親愛的使用者，\n" "\n" "WP Super Cache 已從你的部落格被移除，但是 .htaccess 中的\n" "mod_rewrite規則仍然存在。\n" "\n" "請編輯下列檔案並移除 'BEGIN WPSuperCache' 及 'END WPSupercache' 之間的原始碼。\n" "請先備份這個檔案！\n" "\n" "%s\n" "\n" "WP Super Cache Plugin 敬上\n" "http://wordpress.org/extend/plugins/wp-super-cache/" #: wp-cache.php:3031 msgid "Delete cache of the current page" msgstr "刪除目前頁面的快取" #~ msgid "" #~ "WP Minify reduces the number of files served by your " #~ "web server by joining Javascript and CSS files together. Alternatively " #~ "you can use WPSCMin, a Supercache plugin that minifies " #~ "cached pages. It does not however join JS/CSS files together." #~ msgstr "" #~ "WP Minify 合併Javascript及CSS檔案，以減少網頁伺服器需要" #~ "服務的檔案數量。 或者你也可以使用 WPSCMin，一個減少快取" #~ "面數量的 Supercache 外掛。(但它並不會合併JS/CSS檔案)" #~ msgid "Log level" #~ msgstr "記錄等級" #~ msgid "(1 = less, 5 = more, may cause severe server load.)" #~ msgstr "（1 = 低，5 = 更多，可能會導致嚴重的伺服器負載）" #~ msgid "" #~ "Garbage Collection
    Last GC was %s " #~ "minutes ago
    " #~ msgstr "" #~ "垃圾回收
    上次垃圾回收於 %s 分鐘前" #~ "
    " #~ msgid "Next GC in %s minutes" #~ msgstr "下次垃圾回收於 %s 分鐘後" #~ msgid "Current server time is: %s" #~ msgstr "目前的伺服器時間為：%s" #~ msgid "" #~ "(requires friendsadverts.php too) " #~ msgstr "" #~ "（必須有 friendsadverts.php）" #~ msgid "Mobile device support." #~ msgstr "行動裝置支援。" #~ msgid "Expire time:" #~ msgstr "過期時間：" #~ msgid "" #~ "If the expiry time is more than 1800 seconds (half an hour), garbage " #~ "collection will be done every 10 minutes, otherwise it will happen 10 " #~ "seconds after the expiry time above." #~ msgstr "" #~ "如果過期時間大於1800秒（半個小時），垃圾回收會每10分鐘進行一次，否則就會在" #~ "設定到期時間的10秒後進行清理。" #~ msgid "Tester & Contents" #~ msgstr "測試及內容" #~ msgid "" #~ "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on " #~ "on the main site of this network." #~ msgstr "" #~ "注意：除非在這個網路的主站上執行，WP Super Cache " #~ "mod_rewrite規則檢查會被關閉。" #~ msgid "" #~ "Logging to a file is easier but faces the problem that clearing the cache " #~ "will clear the log file." #~ msgstr "記錄到一個檔案更容易，但面臨的問題是清除快取將會清除記錄檔。" #~ msgid "Logging Type" #~ msgstr "記錄種類" #~ msgid "Email" #~ msgstr "電子郵件" #~ msgid "file" #~ msgstr "檔案" #~ msgid "(support for multiple domains on multisite websites) " #~ msgstr "(在多站台網站上，支援複數網域名稱)" languages/wp-super-cache-it_IT.mo000066600000202306152133035240012705 0ustar00S Lp<q,M)9`J ~?63v*Z7Z5 N =\!b!j!-h"$" ""#$\%%?&((()0*w*ZS+%++,.@-o.&(/O/:`/n0p 1{222 33$383 V3c33333i4 x4,44^c5p5+36_6/u66 6 6`6+%7Q73f7777!77!979:4:I:@-;n;s;g<%< =$= *=4= ;=H=5W===3`>1>>n??C@K@T@AuA AjABBB?BCC} CCNCC DnD$DDDDDE~EESFFG (G3G<CGgGG+G*'HRHaHfH iIbtIIJK&^L"MkNPWPpPEPP*P Q Q !Q +Qb8QQ]Q$R4R SRaRxRRRCS$US"zSS!SS TTU&UU<UbV wV|WyXzX0}X!X-XkXjZ {Z ZZZmZT[s[U[[p\U]^]f]n]]]J]]d^>_`_F``0` &a 0ae ł)Eb*y/.ԃ37VZckp%xF9g 3?PوN*yL9Taۊ-=(kOnuSɍ%$+,_5rll( 4J7#!Eb#T]b #& J!W:ym},i"/¤/AG Xme.ӥ\-x &ŦH"5NX"ʩNXg 8 Yf lvA =;'c>Q J T`3 n۲JQh}Z&%EkpŶu?Zr@ֹrF0̺ 3a@<Ⱦ#ue|^*X: w* !Kms ,4/,4> s?=s8T6-JFxQ d q~I"l[} * 2=U$pU]yIglG 7_OR>&A h @(/,k v| >578,p{5(A^GeH Vk @u,y|,Ib._8D3G%KqXa|)18" [|mr  %OC'70$r "L.A{cO~JF ,Cp l$i*0!' 24g@5?49/n -fR'<-52Co)&p9a%8ML!+D i] FO XKELG10FHBm 6 >gb.d?uW@.J5e'^{179N#?B=:ICSA #=RcTM%/z ($ONy}( 3&7nk6U,2hjI_P@; q$t~83!KvE"w/QD+P<sxS\:*4A GZJQ"0Yr*,| ;4H>l)`V [ Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumUse Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together.Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.No Adverts for Friends plugin is %s.

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.One or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Provides support for Domain Mapping plugin to map multiple domains to a blog.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: WP Super Cache in italiano Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-11-22 17:30+0000 PO-Revision-Date: 2010-11-23 20:55+0100 Last-Translator: Gianni Diurno (aka gidibao) Language-Team: Gianni Diurno | gidibao.net MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Italian X-Poedit-Country: ITALY X-Poedit-KeywordsList: __;_e X-Poedit-Basepath: .. X-Poedit-SearchPath-0: . Accertati che appaiano prima di ogni regola WordPress già presente. %1$s é a prova di Digg grazie alla cache fornita da %2$sIl plugin %1$s viene aggiornato e sviluppato da %2$s grazie anche al contributo di molte altre persone.%s pagine nella cache%s pagine scadute%s é scrivibile. Assicurati che essa sia di sola lettura una volta che la pagina verrà generata (limita i problemi di sicurezza).%s rimosso!Il file %s.htaccess é stato aggiornato con l'inserimento delle regole mod_rewrite necessarie. Verifica la loro correttezza. Ecco come dovrebbero essere:Il file %s/advanced-cache.php non esiste oppure non può essere aggiornato.(1 = minore, 5 = maggiore, può essere causa di un maggior carico sul server.)(Sperimentale)(utilizzare la sola cache parziale, non attivare la compressione ed installare Bad Behavior sotto "%s/plugins/bad-behavior/") (il dato potrebbe essere non sempre accurato per quei siti ad alto traffico)(richieste per il registro provenienti da questo solo indirizzo IP. Il tuo IP é %s)(é necessario anche friendsadverts.php) 1. Nel caso fosse già esistente, cancellalo.2. Rendi il file %1$s scrivibile utilizzando il comando chmod via ftp oppure grazie al software del server. (chmod 777 %1$s) e ricarica questa pagina. Questa é una misura temporanea: ad operazione compiuta, rendi il file di sola lettura. (modificando da 777 a 755 il comando precedente)3. Ricarica questa pagina per aggiornare il file %s/advanced-cache.php304 Not Modified browser caching. Indica quando una pagina non é stata modificata dalla sua ultima richiesta.Il supporto 304 non é attivo (predefinita) poiché GoDaddy ha riscontrato dei problemi con alcuni header utilizzati.FAQInfo installazioneForum di supportoL'utilizzo delle Google Libraries ti permette di caricare le librerie Javascript di comune uso direttamente dai server di Google. Potrebbe ironicamente ridurre il tuo punteggio Yslow.WP Minify riduce il numero dei file serviti dal tuo web server unendo insieme i file Javascript e CSS. Come alternativa, potresti utilizzare WPSCMin, un plugin Supercache che rimpicciolisce le pagine cache (non unisce insieme i file JS/CSS).Yahoo! Yslow é una estensione per Firebug (add-on per Firefox). Analizza le pagine web e suggerisce come migliorare le loro prestazioni basandosi su di una serie di regole per il miglioramento delle pagine web. Potresti anche provare il tool online a nome GTMetrix.Il plugin No Adverts for Friends é %s.

    La costante WP_CACHE é stata aggiunta al file wp-config.php

    Nel caso in cui continuassi a visualizzare questo messaggio consulta il punto 5 delle FAQ. La riga WP_CACHE deve essere spostata.

    Costante WP_CACHE impostata a false

    La costante WP_CACHE viene utilizzata da WordPress per caricare il codice necessario per servire le pagine in cache. Sfortunatamente, l'impostazione é a false. Modifica il tuo wp-config.php ed aggiungi o modifica la seguente linea al di sopra del comando require_once:

    define('WP_CACHE', true);

  • 1. Apri %1$s$wp_cache_file con un editor di testo.
  • 2. Modifica il testo da CACHEHOME a %2$s
  • 3. Salva il file e copialo in %3$s quindi, ricarica questa pagina.
    • ATTENZIONE: Prova alcuni url statici ad esempio, %s prima di salvare le modifiche giusto per assicurarti che il tuo servizio CDN funzioni correttamente.Solo per utenti esperti: Speed up your site with Caching and cache-control spiega come rendere il tuo sito più cacheable grazie alle regole .htaccess.Solo per utenti esperti: Installa un object cache. Scegli tra Memcached, XCache, eAcccelerator ed altri.Errore: WP_CACHE non é attivo nel tuo file wp-config.php ed il plugin non é in grado di modificarlo.Garbage Collection
    L'ultima GC é stata effettuata %s minuti fa
    Ultima cache pagina: %sAttenzione! hai provato ad attivare la compressione mentre la zlib.output_compression é attiva. Vai alla n.ro 21 della sezione Troubleshooting presente nel file readme.Affinché il plugin possa funzionare correttamente sarà necessario un url personalizzato oppure la struttura del permalink. Vai alla pagina per le opzioni dei Permalink per configurare i tuoi permalink.E' stata rilevata una differenza tra le regole del tuo file .htaccess e quelle rewrite del plugin. Questo potrebbe dipendere anche da una sola spaziatura nel testo: effettua quanto prima una comparazione tra le regole presenti nel file con quelle qui sotto. Premi il pulsante ’Update Mod_Rewrite Rules’ per aggiornare.Un modo semplice per compiere l'operazione é quello di modificare temporaneamente i permessi facendo uso del comando CHMOD oppure via il tuo client ftp. Assicurati che sia scrivibile affinché il tutto possa funzionare propriamente.Nomi file consentiti e URL respintiAggiungi una pagina diretta:Aggiungi qui le stringhe (non il nome del file) per forzare il blocco della cache per quella data pagina. Ad esempio, se il tuo URL contenesse l'anno e tu non gradissi la cache per gli articoli pubblicati in quel dato periodo, sarà sufficiente specificare l'anno, ad es. ’/2004/’. WP-Cache effettuerà una ricerca in modo tale da verificare la presenza di quella stringa nell'URI quindi, la cache per quella pagina non verrà generata.Aggiungi qui i nomi dei file per i quali potrà essere effettuata la cache (anche in caso di corrispondenza con una delle stringhe specificate più sopra).Aggiungi tu stesso le regole. Modifica il file %s.htaccess e trova il blocco del codice contenuto tra le linee # BEGIN WPSuperCache e # END WPSuperCache. Troverai due sezioni particolarmente simili tra loro. Proprio sotto la linea %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ aggiungi queste linee: (per due volte, una per ogni sezione)AvanzatoEtàCome alternativa, puoi modificare manualmente il file %s.htaccess aggiungendo il seguente codice (prima di ogni regola WordPress):ArchiviPlugin disponibiliIn attesa di moderazioneIl plugin Awaiting Moderation é %sBad BehaviorIl supporto Bad Behaviour é %s.Non é stato trovato Bad Behaviour. Effettua una verifica.CDNLa funzionalità CDN é fornita da OSSDL CDN Off Linker di Mark KubackiContenuti cacheVerifica cacheCache hit di questo sito per accesso rapido.I plugin di cache sono degli scripts PHP che risiedono in una cartella a nome plugins allocata nella cartella wp-super-cache. Questi plugin saranno caricati al momento del caricamento di Supercache in un modo più rapido dei regolari plugin di WordPress.Rigenerazione cache. Serve un file supercache agli utenti anonimi quando un nuovo file é stato generato.Le statistiche della cache non sono generate in automatico. E' necessario che tu prema il link qui sotto per potere rigenerare in questa pagina le statistiche.Ultima statistica cache generata: %s minuti fa.Cache effettuata %s secondi faPagine in cache da %1$s : %2$sCacheCache non attivaCache attivaLa cache é solamente uno tra i modi per potere rendere un sito più veloce. Ecco alcuni plugin plugin utili:Attiva la cache per utilizzare questa funzioneAnnulla pre-carica cacheNon é possibile proseguire l'operazione. Correggi i problemi precedenti prima di riprovare.Non é possibile aggiornare il file .htaccessCategoriaModifica la scadenzaControlla la front page ogni 5 minuti.La ricerca e la cancellazione dei file scaduti é particolarmente dispendiosa così come lo é il lasciarli lì scaduti. Qualora avessi un sito con un traffico rilevante, imposta il tempo di scadenza a 300 secondi. Effettua eventualmente più prove con valori differenti e controlla in questa pagina (più volte durante l'arco della giornata) il totale dei file scaduti presenti. Il numero ottimale dovrebbe essere inferiore a circa 500 file di cache (lmodalità parziale). Il numero dei file nella cachepotrà essere comunque superiore utilizzando mod_rewrite o PHP caching.Cancella i vecchi file supercache.Svuota tutti i file di cache quando viene pubblicato un articolo o una pagina.Svuota la cache in caso di errore.Blocco grezzo del file. Sebbene questa funzione non sia particolarmente necessaria potrebbe tornarti utile qualora il tuo server non avesse una potenza sufficiente. Attenzione! In alcuni casi molto rari potrebbe bloccare il tuo server!Moderazione dei commenti attiva. Il tuo commento non apparirà immediatamente.Compressione delle pagine in modo che esse siano servite più rapidamente ai visitatori.La compressione é disattivata come predefinita poiché alcuni host riscontrano dei problemi con i file compressi. La commutazione attivo/non attivo svuoterà la cache.La configurazione del file é stata modificata: alcuni valori potrebbero essere errati. Ricarica nuovamente la pagina dal menu delle "Impostazioni" per ripristinare.Non é presente il file di configurazione e la cartella %1$s (%2$s) non é scrivibile. Verifica i suoi permessi.Cache in corso dal post %d a %d.Log attuale:DebugDebuggingCancellaCancella la cacheCancella la cache scadutaCancella i file cache di Super Cache (apre in una nuova finestra)Cancella i file nella cacheCancella le regole mod_rewrite del plugin in %s.htaccess presenti tra # BEGIN WPSuperCache e # END WPSuperCache quindi, permetti al plugin di rigenerarle al momento della ricarica di questa pagina.Sto cancellando il file supercache: %s
    Sto cancellando il file wp-cache: %s
    Sviluppatori: é possibile rendere compatibile il plugin con il blocco di protezione grazie alla costante "WPLOCKDOWN". Il seguente codice farà sì che il plugin sia in grado di sopperire alle impostazioni WPLOCKDOWN.File cache direttaI file di cache diretta sono dei file creati direttamente sotto %s ossia laddove il tuo blog risiede. Questa opzione é particolarmente utile qualora ti aspettassi un alto livello di traffico proveniente da Digg o Slashdot verso un articolo/pagina.DisattivaDisattivatoNon effettuare la cache per i tipi di pagine a seguire. Per maggiori informazioni, leggi la documentazione circa i tag condizionali.Informazioni autoreIl plugin Domain Mapping é stato rilevato! Vai alla pagina dei plugin di Supercache ed attiva il plugin di supporto a domain mapping.Il supporto Domain Mapping é %sNon servire pagine cache per gli utenti conosciuti.FacileModifica %s aggiungendo la seguente linea:
    define('WP_CACHE', true);
    Diversamente, WP-Cache non verrà eseguito dal core di Wordpress.EmailInvia una email di notifica all'aministratore del blog per l'avvenuto controllo. (utile per il testing) AttivaAttivatoAttiva/disattiva il plugin per rimuove il testo "Il tuo commento é in attesa di essere moderato." quando viene lasciato un commento da moderare.ErroreErrore: la compressione GZIP é attiva: disattivala qualora desiderassi attivare wp-cache.Pagina diretta esistentePeriodo scadenza:I file scaduti sono file più vecchi di %s secondi. Sebbene questi file vengano comunque utilizzati dal plugin sappi che sono cancellati periodicamente.Periodo scadenza e Garbage CollectionFeedAnalisi %s cache di base: Analisi prima copia di %s: Analisi seconda copia di %s: Correggi la configurazioneCorreggi qui i problemi con il debugging del plugin. Potrai sceglie tra l'invio delle tue email di debug oppure consultare il registro contenuto in un file allocato nella cartella della cache.Per una migliore prestazione attivare il "Supporto mobile device" oppure cancellare le regole mobile rewrite presenti nel tuo file .htaccess. Cerca le 2 linee contenenti il testo "2.0\ MMP|240x320" e cancellale.Esempio: per la cache di %1$sabout/, sarà necessario che tu inserisca %1$sabout/ oppure /about/. Il file di cache verrà generato la prima volta che un utente anonimo visiterà quella pagina.Aggiorna file Super CachedAggiorna file WP-CachedPagina principaleTesto front pageRicarica completa della cache tra %d ore %d minuti e %d secondi.La tua installazione di WordPress ha la compressione GZIP attiva: wp-cache non sarà disponibile sino a quando la compressione gzip non verrà disattivata.Garbage CollectionSono state create nel file %s.htaccess le regole per la codifica Gzip.Il suo blog é %1$s e le sue foto le trovi %2$s.Nascondi la lista dei fileHomeSono certo al 99% che non si tratta di bug in WP Super Cache e questo problema può accadere in casi veramente molto rari. Puoi attivare comunque un controllo ogni 5 minuti in modo tale che sia possibile monitorare il tuo sito. In caso di problemi, ti verrà inviata una email.Indirizzo IPNel caso in cui non funzionasse, accertati che il file %s/advanced-cache.php non esista:Qualora il periodo di scadenza fosse maggiore di 1800 secondi (mezz'ora), la garbage collection verrà effettuata ogni 10 minuti diversamente, l'operazione verrà effettuata 10 secondi dopo il periodo di scadenza indicato qui sopra.Qualora desiderassi disinstallare questo plugin, assicurati che la cartella %s sia scrivibile in modo tale che i file advanced-cache.php e cache-config.php possano venire cancellati automaticamente. (l'accertarsi che anche questi due file siano scrivibile é probabilmente una buona idea!)Nella ’Modalità precarica’ la garbage collection verrà svuotata per i soli utenti conosciuti, non per i file supercache precaricati. Preferisci questa configurazione se la cache fosse pre-caricata.In alcuni casi molto rari, é possibile che si verifichino in alcuni blog due problematiche:
    1. La front page potrebbe giungere come download di un file zip.
    2. La pagina errata può essere in certi casi custodita nella cache quale front page qualora il tuo blog facesse uso di una front page statica e la struttura del permalink fosse /%category%/%postname%/.
    Pare che il mod_rewrite non sia installato. Considera che questa affermazione potrebbe non essere attendibile al 100%, specialmente qualora non venisse utilizzato Apache. Verifica che sia stato caricato il modulo mod_rewrite. Il modulo sarà necessario per potere servire i file statici di Super Cache. Avrai comunque ancora la possibilità di poter utilizzare la modalità parziale o PHP.Pare che il tuo URL termini con uno "/". Dal momento in cui hai installato questo plugin, é stato rilevato un bug che duplica il contenuto laddove l'URL non termina con uno "/"; di fatto, vengono proposti gli stessi contenuti di quelli con lo "/" e non viene altresì effettuato un reindirizzamento all'URL appropriato. Per la correzione, sarà necessario modificare il tuo file .htaccess aggiungendo queste due regole ai due gruppi di regole di Super Cache:ChiaveLate init. Mostra i file in cache dopo che WordPress é stato caricato. Utile nella modalità legacy.Pagina cache parziale.Poche email, 1 all'avvio ed 1 al termine della operazione di precarica per tutti gli articoli.Lista di tutti i file presenti nella cacheElenca su questa pagina la lista delle nuove pagine cache.Blocco di protezioneBlocco di protezione:Livello logTipo di loggingConsultare il file di registro é semplice ma ricordati che, una volta svuotata la cache, verrà cancellato anche il file di registro.Rendi più veloce WordPressSvuota la casella di testo per rimuovere l'indirizzo dalla lista delle pagine dirette e cancellare dalla cache il file.Numerose email, 2 email ogni 100 articoli.Medio, 1 email ogni 100 articoli.VarieModuli Apache mancantiSupporto Sono state rilevate le regole Mobile rewriteIl supporto mobile necessita della aggiunta di alcune regole extra nel tuo file .htaccess oppure che tu imposti il plugin nella modalità parziale. Qui puoi trovare le opzioni disponibili (in ordine di difficoltà):Regole Mod RewriteLe regole Mod Rewrite non possono essere aggiornate!E' necessario aggiornare le regole Mod Rewrite!Le regole Mod Rewrite sono state aggiornate!Il Mod rewrite potrebbe non essere stato installato!Il Mod_rewrite é il più veloce, il PHP é piuttosto veloce e semplice da fare funzionare mentre, nonstante la cache parziale sia la più lenta, essa é da ritenersi la più flessibile e semplice da fare funzionare. I nuovi utenti dovrebbero utilizzare la cache PHP.Serve un aiuto?Serve aiuto? Leggi il file Super Cache readme. In esso sono contenute le info sulla installazione, le FAQ e numerosi suggerimenti. Puoi anche utilizzare il forum di supporto: qui potresti trovare una risposta alle tue domande.Pagine recenti nella cache:La prossima GC verrà effettuata tra %s minutiNota:Nota: attiva cache PHP, rigenerazione cache e supporto mobileAvviso: Mod_rewrite o cache parziale attivi. Le impostazioni avanzate sono la pagina di avvio predefinita.Avviso: la cache PHP é attiva ma sono state rilevate delle regole Supercache mod_rewrite. I file della cache saranno serviti utilizzando queste regole. Ignora questo messaggio qualora il tuo sito funzionasse correttamente oppure modifica il file .htaccess file allocato nella root della tua installazione e rimuovi le regole di SuperCache.Avviso: la regola mod_rewrite per WP Super Cache non sarà attiva eccetto che sul sito principale di questo network.Avviso: la regola mod_rewrite per WP Super Cache non sarà attiva eccetto che per il sito principale di questo network.OKOggetto cache in uso. Nessun elenco cache disponibile.La richiesta di una o più pagine é fallita:Ricarica la sola pagina in uso quando vengono effettuati dei commenti.Il PHP sta comprimendo i dati inviati ai visitatori del tuo sito. E' preferibile disattivare questa opzione qualora il plugin comprimesse la cache per l'output al posto di comprimere più volte la stessa pagina.. Consultare la n.ro 21 della sezione Troubleshooting. Leggi questa pagina per le istruzioni sul come modificare il tuo php.ini.Pagina %d: %d (%s)Pagina 1: %sPagina 2: %sPagineErrore struttura permalinkVota questo plugin e dimmi se funziona oppure no. Il tuo feedback mi aiuterà nello sviluppo di questo progetto.Crea %s /wp-cache-config.php da wp-super-cache/wp-cache-config-sample.phpMandagli un saluto su %s!Leggi il punto numero 16 nella sezione Troubleshooting del file readme.txtLeggi il readme.txt per le istruzioni su come disinstallare questo script. Vedi anche, "Come disinstallare WP Super Cache".Visita %1$s per svuotare la cache nel caso in cui la front page del tuo sito non fosse corretta e mancasse del testo, "%2$s"!Visita %s per svuotare la cache!PluginsPre-caricaPre-carica %s articoli.Pre-carica la cache adessoLa pre-carica é stata riavviata. %sModalità pre-carica (garbage collection solo per file cache parziale. Raccomandato.)Il pre-caricamento crea comunque un gran numero di file. La cache verrà effettuata a partire dell'articolo più recente sino a giungere a quello più datato quindi, prendi in considerazione il fatto di effettuare la cache del più recente qualora avessi molti articoli (+ 10.000). Tutto ciò é particolarmente importante per gli hosting condivisi.La pre-carica della cache non é attiva. Disattiva la cache parziale oppure conferisci con l'amministratore del tuo host.Proteggi il tuo server da un inatteso picco di traffico attivando il blocco. Quando il blocco é attivo, i nuovi commenti non ricaricheranno i file statici nella cache.Fai sapere a tutti che il tuo sito é a prova di Digg! (inserisce un messaggio nel footer del tuo blog)Provvede il supporto per il plugin Domain Mapping per la mappatura dei domini multipli di un blog.Vota questo plugin!Modalita di sola lettura. La configurazione non può essere modificata.Sola lettura:RaccomandatoLink e plugin consigliatiRicarica della cache tra %d ore %d minuti e %d secondi.Ricarica i file della cache pre-caricata ogni %s minuti. (0 per disattivare, minimo %d minuti.)Ricarica questa pagina una volta che i permessi per il file sono stati modificati.Ricarica questa pagina una volta aggiornato il file .htaccess.I seguenti post sono stati aggiornati:Rigenera statistiche della cacheUser Agents E' necessario fornire correttamente i file compressi supercache.E' necessario impostare le informazioni cache per le pagine supercache. In assenza di questo modulo, gli utenti che utilizzano IE7 visualizzeranno le pagine non aggiornate.Ripristina la configurazione predefinitaE' necessario aggiornare le regole Mod Rewrite!Le regole devono essere aggiunte anche a %s:Il file campione per la configurazione di WP-Cache (%s) non esiste. Effettua una verifica.SalvaSalva le modificheSalva i fileSalva le stringheSalva le stringhe UAIl pre-caricamento programmato della cache é stato annullato.Pre-caricamento programmato della cache tra %d minutiPre-caricamento programmato della cache tra 10 secondi.Prossima ricarica programmata tra %d minuti.Vai al fondo della pagina delle impostazioni avanzate e clicca il pulsante Aggiorna le regole Mod_Rewrite.Pagine ricercaInviami una email di notifica alla ricarica dei file.Invia una richiesta non crittografata (non https) per la homepageImposta la data di scadenza per le pagine supercached. Senza questo modulo, i visitatori potrebbero non visualizzare le nuove pagine sebbene venga ricaricata la pagina oppure inviare dei commenti.Imposta a 0 il tempo di scadenza per disattivare la garbage collection.Imposta il plugin nella modalità parziale ed attiva il supporto mobile.ImpostazioniArticoli singoliIl mio blog ha attivato un blocco di protezione. Gli aggiornamenti appariranno a breveScadenza file Super CachedOrdina i file WP-CachedLe stringhe presenti nella header HTTP degli ’User Agent’ che impediscono a WP-Cache di fornire i dati nella cache alle richieste da parte dei bot, degli spider e dei crawler. Nota che anche i file super cached saranno inviati a questi agent qualora esistessero.TagTest cacheVerifica la cache del tuo sito cliccando sul pulsante qui sotto.Verifiche e contenutiil testo da cercare nella tua front page. La cache verrà svuotata in assenza del testo. Lascia vuoto per disattivareGrazie per avere effettuato l'aggiornamento.Il file di configurazione di WP Super Cache é %s/wp-cache-config.php e non può essere modificato. Affinché possa essere modicato, il file in questione deve essere scrivibile.La cache del blog é stata svuotata perché manca il testo "%2$s" nella front page del tuo sito. Visita %1$s per controllare se la cache sia stata svuotata.La cache del blog é stata svuotata perché la front page del tuo sito é sotto downloading. Visita %1$s per controllare se la cache sia stata svuotata.Il file %s.htaccess non può essere modificato. Correggi utilizzando il comando chmod oppure il tuo client ftp.Non sono presenti i seguenti moduli Apache. Senza di essi, il plugin funzionerà in modalità parziale. Qualora facessi uso della modalita Supercache attiva, i tuoi visitatori potrebbero visualizzare delle pagine non aggiornate e/o corrotte.Le regole mod_rewrite sono cambiate dalla tua ultima installazione di questo plugin. E' necessario che tu rimuova le regole supercache precedenti prima che le nuove siano aggiornate. Ricarica questa pagina una volta che avrai modificato il tuo file .htaccess. Qualora desiderassi effettuare un aggiornamento manuale, modifica la seguente linea: %1$s rendendola simile a questa: %2$s Le sole modifiche sono "HTTP_COOKIE" che diventa "HTTP:Cookie" e "wordpressuser" che va sostituito con "wordpress". Questa é una modifica relativa a WordPress 2.5 comunque, la sua validità é estesa anche alle versioni precedenti (qualora avessi il coraggio di utilizzarle).Le pagine non coincidono! La timestamp differisce oppure non é presente!Le regole di scrittura richieste da questo plugin sono state modificate oppure non sono presenti. La timestamp (data) delle due pagine coincide!Questa é una funzione strettamente avanzata e necessita di una valida conoscenza sul come operare in ambito di PHP e WordPress.Questa operazione effettuerà la cache di ogni articolo e pagina pubblicati nel tuo sito. Verranno quindi creati dei file statici supercache in modo tale che i visitatori sconosciuti (bot compresi) visualizzeranno la pagina nella cache. Tutto questo potrebbe esserti utile per quanto concerne il ranking di Google nel caso in cui essi utilizzasero la velocità come metro di valutazione per il giudizio dei siti web.Questa operazione non avrà alcun effetto per gli utenti comuni mentre gli utenti via mobile non visualizzeranno le pagine nella cache.Affinché il tuo server possa fornire dei file html statici é necessario che le regole mod_rewrite vengano aggiunte al file %s.htaccessSono presenti troppi file cache: non é possibile mostrare l'elenco.E' necessaria una verifica sullo slash di chiusura.URIWordPress non é in grado di trovare il file wp-cron.php. Questo script é necessario script per un corretto funzionamento della garbage collection fornita da questo plugin, per la pubblicazione programmata dei post di WordPress così come per tutte le altre attività di rilevante importanza.Sfortunatamente, le rewrite rule non possono essere aggiornate in automatico quando WordPress MU é in funzione. Apri il tuo file .htaccess ed aggiungi le seguenti regole mod_rewrite in cima ad ogni altra regola presente nel file.AggiornaAggiorna le pagine diretteAggiorna le regole Mod_RewriteAggiorna le impostazioniAggiorna lo statoUtilizza PHP per servire i file in cache.Utilizza mod_rewrite per servire i file in cache.Utilizza l'oggetto cache per conservare i file in cache.Visualizza le regole Mod_RewriteImpostazioni WP Super CacheWP Super Cache ha controllato la front page del tuo blog. Visita %s qualora gradissi disattivare la funzione.WP Super Cache non é attivo. Vai alla pagina di amministrazione del plugin per attivare la funzione di caching.Sono state rilevate le regole mod rewrite di WP Super Cache nel tuo file %s.htaccess.
    Clicca il seguente link per vedere le linee aggiunte a quel file. Nel caso in cui avessi aggiornato il plugin assicurati che esse coincidano.E' necessario configurare WP Super Cache. Vai alla pagina di amministrazione per attivare e configurare il plugin.WP-CacheWP-Super-CacheAttenzioneAttenzione!Attenzione! %s é scrivibile!Attenzione! La compressione non é attiva - non trovata la funzione gzencode().Attenzione! Il PHP Safe Mode é attivo!Attenzione! Il tuo hostname "%s" viene convertito in %sE' stata rilevata una installazione WordPress MUWordPress ha un blocco di protezione. Quando verranno effettuati dei nuovi commenti, i file statici di Super Cache non saranno cancellati.WordPress ha un blocco di protezione. I nuovi commenti rigenereranno come al solito i file statici di Super Cache.Scrivibile:Puoi definire dei differenti URL CDN per ogni sito di un network multi-sito.Puoi modificare tu stesso il file aggiungendo le seguenti regole.Puoi vedere dove posizionare ed esaminare nella loro completezza le regole cliccando il link qui sotto a nome "Visualizza le regole Mod_Rewrite".Attivando questo plugin potresti andare incontro ad alcuni problemi poiché il SAFE MODE é attivo.Affinché l'aggiornamento automatico possa funzionare, sono necessari i marcatori BEGIN ed END nel file %s.htaccess. Sono simili a questa ed avvolgono le principali regole mod_rewrite di WordPress:E' necessario rendere scrivibile %s affinché questa opzione possa essere attivata. Per ragioni di sicurezza, rendi di sola lettura una volta che la pagina é stata generata.L'amministratore del sito ha la possibilità di cambiare il proprietario del gruppo che fa capo agli script di questo plugin facendo sì che esso coincida con l'utente web del server. Anche il proprietario del gruppo per la cartella %s/cache/ può essere cambiato. Per ulteriori informazioni, consulta la pagina del manuale safe mode.L'amministratore del sito ha la possibilità di disattivare questa funzione. Per ulteriori informazioni, consulta la pagina del manuale safe mode. La disattivazione non potrà avvenire via file .htaccess. L'operazione dovrà essere effettuata nel file di configurazione php.ini.E' necessario modificare i permessi per %s per renderli maggiormente restrittivi. Utilizza per la correzione il tuo client ftp oppure il seguente comando:Il tuo file %s.htaccess non é scrivibile e deve essere aggiornato con le regole mod_rewrite necessarie. Le nuove regole andranno inserite al di sopra di quelle regolari di WordPress così come nel codice qui sotto:Il tuo file di configurazione WP-Cache (%s) non é aggiornato e non é scrivibile. Cancellalo e ricarica questa pagina.La tua cartella per la cache ($cache_path) non esiste e non può essere creata nel server. Verifica i permessi %s.La tua cartella per la cache (%1$s) oppure %2$s é necessario renderla scrivibile affinché il plugin possa funzionare. Verifica con attenzione.Il tuo commento é in attesa di moderazione.Prima che sia possibile la lettura e la scrittura dei file, il tuo server richiede che venga effettuata una verifica circa il proprietario degli script PHP.Il tuo server ritiene che il tuo hostname venga convertito in %s. Alcuni servizi quali ad esempio la garbage collection fornita da questo plugin e la pubblicazione programmata dei post di WordPress potrebbero non funzionare correttamente.Probabilmente il tuo sito fa uso di molti file statici. I file immagine, Javascript e CSS sono generalmente dei file statici che potrebbero essere facilmente serviti da un altro sito o CDN. Quindi questo plugin sostituirà ogni link presente nelle cartelle wp-content e wp-includes (ad eccezione dei file PHP) del tuo sito con l'URL fornito qui sotto. In quel modo potrai copiare tutti i contenuti statici presso un host dedicato o fare un mirror dei file verso un CDN via origin pull.Compressione Zlib (output) attivata![%1$s] %2$d articoli sono stati ricaricati[%1$s] La pre-carica della cache ha avuto inizio[%1$s] Pre-carica cache arrestata[%1$s] Ricarica articoli da %2$d a %3$d[%s] La pre-carica della cache é stata completata[%s] Controllo Front page![%s] La front page é stata gzipped! La cache é stata svuotata![%s] La front page é stata gzipped! Svuota la cache![%s] La front page non é corretta! La cache é stata svuotata![%s] La front page non é corretta! Svuota la cache![%s] La pre-carica potrebbe avere dei problemi.tuttodisattivatoattivatofilesecondilanguages/wp-super-cache-fr_FR.mo000066600000170540152133035240012677 0ustar004 \<,&MS` #~/?3"1b*57`Z55) _=m\r { ?d!"wo#Z#B$$.%&&'':'n )px)***w++ +3++, ,, ,M,^,p]-+--/.@. H. T.+_..3....!/)/!07 1X1n1I2@g22s-33%!4G4^4 d4n4 u4454443515666}777u>8j899?9::%:N+:z: :n:$ ;0;6;S;o;;~;<<== ==g=2>+E>*q>>>> ?b?!@@A&B"CkD^FbFEwFF*F F G G Gb*GG]G$H&H EHSHjHHH5I$GI"lII!IIJK&KK<KbKbL|MyM N0N!@N-bNkNO P P#P)PTBPPUP QpQU,RRRRRRJR SdSbT` U0jU U USU?V<EVVVV7VjWpWWWYW%X *X 5XBX(RX{X+Y,-Y.ZYfY Y/Y0-Z^Z?Z8 [Y[ b[:o[[[[\ \;\\q]]]@^^v__`<bGc#Vcuzc cTd~Pe+eefffggg gh%h'Ehmhhjhbijil4jjjjjjj*k/kbEk[k l7lrGlMlmm/Dntoippq1rr$>secss lttt)tt u*$u/Ou.u3uuvvvvv#vKxA#y`eyyyyzzIU{M{{{{|>A}F}c}D+~=p~/~Od. f3STވ/%ƍ^g&~K#'>8wzcސF ͑7 &4OHf"QҒ1$ Vb/]*L;!rwO:0'X t ~ !Xǚ# D=);g!p rFgKá]ʡ(?S 5 ,?,l`R0-@ n|p30Du1 ͨeب>WpsjbޭA R='B /Eʲx5Y&ֳ0&E>H,2,%4=ZYfǻHʻ4LHE W co"u^7t/p+ )iSzLA w,hJ )X-A&77s5 $+ 82=HLK/H{IG,4SE+, Pk~((Z_v].4cg xu5!/'Wt7@F%Our *3 B L"W0z7xO`w{m6- X0D" :([6%(8 CC:E-6 ;GOWE<J#).rRh{\! 7_6g~|]^#s}fm/O%&.9IdU>BG  $$o8"F ; % w`(?0lXKz)0eA*/  C-S4YQ&in23Np4[+*"T@DL-V'1qW3(t,yx1ub Z=M! Hja':vP5,2+k c Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.) (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) (support for multiple domains on multisite websites) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.phpNo Adverts for Friends plugin is %s.Domain Mapping support plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting Moderation plugin is %sBad Behaviour not found. Please check your install.Bad Behaviour support is %s.Cache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Don’t cache pages for known users.Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textGZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLegacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching.Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.One or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRefresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Update Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: WP Super Cache fr Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-06-16 10:25+0000 PO-Revision-Date: Last-Translator: Maître Mô Language-Team: Maître Mô MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=n != 1; X-Poedit-Language: French X-Poedit-Country: France X-Poedit-SourceCharset: utf-8 X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;_n_noop:1,2;_c,_nc:4c,1,2;_x:1,2c;_ex:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2 X-Poedit-Basepath: . X-Textdomain-Support: yes X-Poedit-SearchPath-0: . Assurez-vous qu'elles apparaissent avant les règles existantes WordPress. %1$s est compatible avec Digg grâce à la mise en cache par %2$s%1$s est maintenu et développé par %2$s avec les contributions de beaucoup d'autres personnes.%s Pages Mises en Cache%s Pages Expirées%s peut être écrit. Merci de le remettre en mode lecture seule après que votre page ait été générée, dans la mesure où il s'agit d'un risque de sécurité.%s supprimé !Le fichier %s.htaccess a été mis à jour avec les règles de Mode Réécriture nécessaires. Merci de vérifier qu'elles sont correctes. Elles devraient ressembler à ceci :%s/advanced-cache.php n'existe pas ou ne peut pas être mis à jour.(1 = le plus bas, 5 = le plus haut, peut sévèrement surcharger le serveur.)(Expérimental)(Seule la mise en cache par héritage est prise en charge, la compression est désactivée ; nécessite Bad Behavior dans "%s/plugins/bad-behavior/")(Supprime le texte "Votre commentaire est en attente de modération." lorsque quelqu'un laisse un commentaire à modérer.)(peut ne pas être toujours exact sur des sites fort occupés)(N'enregistrer que les requêtes de cette adresse IP. Votre IP est %s)(nécessite également friendsadverts.php) (Prise en charge de plusieurs domaines sur les sites Web multisites)1. S'il existe déjà, veuillez supprimer le fichier d'abord.2. Permettez à %1$s d'être écrit en utilisant la commande chmod via votre logiciel ftp ou serveur. (chmod 777 %1$s) et rafraîchissez cette page. Il ne s'agit que d'une mesure temporaire, et vous devrez le repasser en lecture seule ensuite. (Passez de 777 à 755 dans la commande précitée)3. Rafraîchissez cette page pour mettre à jour %s/advanced-cache.phpL'extension Pas de pub pour les amis est %s.Le support de l'extension Domain Mapping est %s

    Constante WP_CACHE ajoutée à wp-config.php

    Si vous continuez à voir s'afficher ce message d'avertissement, merci de lire le point 5 de laFAQ. La ligne WP_CACHE doit être déplacée.

    Constante WP_CACHE réglée sur \"false\"

    La constante WP_CACHE est utilisée par WordPress pour charger le code qui fournit des pages mises en cache. Malheureusement, elle est réglée sur \"false\". Merci de modifier votre fichier wp-config.php, et d'y ajouter ou modifier la ligne suivante, au-dessus de la commande finale require_once :

    define('WP_CACHE', true);

  • 1. Ouvrez le fichier %1$s$wp_cache_file dans un éditeur de texte.
  • 2. Remplacez le texte CACHEHOME par %2$s
  • 3. Sauvegardez le fichier et copiez-le dans %3$s, puis rafraîchissez cette page.
    • Erreur : WP_CACHE n'est pas activé dans votre fichier wp-config.php et je ne peux pas le modifier.Éboueur
    Le dernier éboueur est passé il y a %s minutes
    Attention ! Vous avez tenté d'activer la compression mais zlib.output_compression est activée. Voir le #21 dans la section Dépannage du fichier readme.Une URL personnalisée ou une structure de permaliens est nécessaire pour que ce plugin fonctionne correctement. S’il vous plaît, aller sur la page Options permaliens pour configurer vos permaliens.Une différence entre les règles dans votre fichier .htaccess et celles de réécriture dans l'extension a été découverte. Il peut ne s'agir que d'une différence d'espace blanc, mais vous devriez comparer les règles du fichier avec celles ci-dessous aussi vite que possible. Cliquez sur le bouton ’Actualiser les Règles du Mode Réécriture’ pour mettre à jour les règles.Un moyen simple de faire ceci est de modifier temporairement les permissions en utilisant la commande CHMOD, ou via votre client FTP. Assurez-vous que l'ensemble peut être écrit, et cela devrait fonctionner.Noms de fichiers acceptés & URIs rejetéesAjouter une page directe :Ajoutez ici les chaînes (pas un nom de fichier) qui forcent une page à ne pas être mise en cache. Par exemple, si vos URLs incluent l'année et que vous ne voulez pas mettre en cache les articles de l'année dernière, il suffit de préciser l'année, c-à-d ’/2004/’. WP-Cache recherchera si cette chaîne fait partie de l'URI et dans l'affirmative, ne mettra pas cette page en cache.Ajouter ici les noms des fichiers qui peuvent être mis en cache, même s'ils correspondent à l'une des sous-chaînes rejetées spécifiées ci-dessus.Ajoutez les règles vous-même. Éditez %s.htaccess et trouvez le bloc de code situé entre les lignes # BEGIN WPSuperCache et # END WPSuperCache. Il existe deux sections, qui se ressemblent beaucoup. Juste en dessous de la ligne %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$, ajoutez ces lignes (faites-le deux fois, une par section) :AvancéÂgeAlternativement, vous pouvez éditer votre fichier %s.htaccess manuellement et y ajouter le code suivant (devant toute règle WordPress) :ArchivesExtensions DisponiblesL'extension Awaiting Moderation est %sBad Behaviour n'a pas été trouvé. Merci de vérifier votre installation.Le support de Bad Behaviour est %s.Contenus du CacheTesteur du CacheMise en cache des connexions à ce site pour un accès rapide.Les extensions de Cache sont des scripts PHP qui vivent dans un dossier d'extensions à l'intérieur du dossier wp-super-cache. Ils sont chargés lorsque SuperCache se charge, beaucoup plus tôt que les extensions WordPress classiques.Reconstruction du cache. Sert un fichier SuperCache aux utilisateurs anonymes pendant qu'un nouveau fichier est généré.Les statistiques de mise en cache ne sont pas générées automatiquement. Vous devez cliquer sur le lien ci-dessous pour régénérer les statistiques sur cette page.Dernière statistiques de mise en cache générées il y a %s minutes.Mise en cache il y a %s secondesPages mise en cache depuis %1$s : %2$sMise en cacheMise en cache désactivéeMise en cache ActivéeLa mise en cache doit être activée pour utiliser cette fonctionnalitéAnnuler le Préchargement du CacheImpossible de continuer... Résolvez les problèmes susmentionnés et réessayez.Impossible de mettre à jour le fichier .htaccessCatégoriesModifier le Délai d'ExpirationVérifier la page de garde toute les 5 minutes.La vérification et la suppression des fichiers périmés coûte cher, mais il coûte également cher de les laisser là. Sur un site très occupé, vous devriez définir le délai d'expiration à 300 secondes. Essayez avec différentes valeurs, et visitez cette page pour voir combien de fichiers expirés demeurent à différents moments de la journée. Si vous utilisez la mise en cache Héritée, ayez pour objectif d'avoir moins de 500 fichiers mis en cache, si possible. Vous pouvez avoir infiniment plus de fichiers mis en cache en utilisant les modes de mise en cache Réécriture ou PHP.Nettoyage des anciens fichiers supercache.Effacer tous les fichiers de cache quand un article ou une page est publié.Effacer le cache en cas d'erreur.Verrouillage Majeur de fichier. Vous n'avez probablement pas besoin de ça, mais ça peut aider si votre serveur est peu puissant. Attention ! Peut bloquer votre serveur dans de très rares cas !La modération des commentaires est activée. Votre commentaire peut prendre un certain temps avant d'apparaître.Compresse les pages afin qu'elles soient servies plus rapidement aux visiteurs.La compression est désactivée par défaut parce que certains hébergements ont des problèmes avec des fichiers compressés. Le mettre en marche/arrêt efface le cache.Le fichier de configuration a été modifié, certaines valeurs peuvent-être erronées. Rechargez la page depuis le menu "Réglages" pour les remettre à zéro.Le fichier de configuration est manquant et le répertoire %1$s (%2$s) ne peut pas être écrit par le serveur Web. Vérifiez ses permissions.Mise en cache actuelle des articles de %d à %d.Actuellement connecté à :DébogageDébogageSupprimerSupprimer le CacheSupprimer les Fichiers Périmés Supprimer les fichiers mis en cache par Super Cache (s'ouvre dans une nouvelle fenêtre)Suppression de fichier mis en cacheSupprimez les règles de Réécriture de l'extension dans %s.htaccess situées entre # BEGIN WPSuperCache et # END WPSuperCache et laissez laissez l'extension les régénérer en rechargeant cette page.Suppression du fichier supercache : %s
    Suppression du fichier wp-cache : %s
    Développeurs : Rendez vos extensions compatibles avec le mode Verrouillage en vérifiant la constante "WPLOCKDOWN". Le code suivant vous assurera que votre extension respecte les réglages de WPLOCKDOWN.Fichiers Directement Mis en CacheLes fichiers directement mis en cache sont des fichiers créés directement à partir de %s, où se trouve votre blog. Cette fonction n'est utile que si vous vous attendez à un niveau de trafic majeur de Digg ou Slashdot sur un article ou une page.DésactiverDésactivéNe pas mettre en cache les types de page suivants. Voir la documentation     Marqueurs Conditionnelspour un exposé complet sur chaque type.Extension Domain Mapping détectée ! Merci d'aller sur la page Extensions SuperCache et d'y activer l'extension assistant de Domain Mapping.Ne pas mettre en cache les pages pour les utilisateurs connus.Éditez %s et ajoutez-y la ligne suivante:
    define('WP_CACHE', true);
    , sinon WP-Cache ne sera pas exécuté par le noyau WordPress.MailEnvoi d'un mai à l'administrateur du blog lorsque les contrôles sont effectués. (Utile pour le test)ActiverActivéErreurErreur : la compression GZIP est activée, la désactiver si vous souhaitez activer wp-cache.Page directe existanteDate d'expiration :Les fichiers périmés sont ceux remontant à plus de %s secondes. Ils sont encore utilisés par l'extension et sont détruits périodiquement.Date d'Expiration & ÉboueurFluxRécupération de %s pour la première mise en cache.Récupération de la première copie de %s :Récupération de la deuxième copie de %s :Correction de la ConfigurationRésout les problèmes de l'extension en la déboguant ici. Peut vous adresser des mails de débogage ou les enregistrer dans un fichier de votre répertoire de cache.Pour des performances optimales, vous devriez activer le "Support des systèmes de mobiles" ou supprimer les règles de réécriture pour mobiles dans votre .htaccess. Localisez les 2 lignes avec le texte "2.0\ MMP|240x320" et supprimez-les.Par exemple: pour mettre en cache %1$sabout/, vous entrez %1$sabout/ ou /about/. Le fichier de cache sera généré à la prochaine visite d'un utilisateur anonyme sur cette page.Fichiers Récemment Mis en Cache par Super CacheFichiers Récemment Mis en Cache par WP-CachePage de GardeTexte de la page de gardeLa compression GZIP est activée dans WordPress, wp-cache sera outrepassé jusqu'à ce que vous la désactiviez.ÉboueurRègles d'encodage Gzip dans %s.htaccess créées. Il blogue sur %1$s et poste des photos sur %2$s.Masquer la liste des fichiersAccueilJe suis certain à 99% qu'il ne s''agit pas de bugs de WP Super Cache et qu'ils ne surviennent que très rarement, mais vous pouvez exécuter une vérification simple, une fois toutes les 5 minutes, pour vérifier que votre site est OK, si vous avez peur. Vous recevrez un mail s'il survient un problème.Adresse IPSi ça ne fonctionnait pas, assurez vous que le fichier %s/advanced-cache.php n'existe pas :Si le délai d'expiration est supérieur à 1800 secondes (une demi-heure), la collecte des ordures sera effectuée toutes les 10 minutes ; sinon, elle s'effectuera 10 secondes après le délai d'expiration ci-dessus.Si vous désinstallez cette extension, assurez-vous que le répertoire %s peut être écrit par le serveur Web, de façon que les fichiers advanced-cache.php et cache-config.php puissent être automatiquement détruits. (S'assurer que ces fichiers peuvent également être écrits est probablement une bonne idée !)En \"Mode Préchargement\", la collecte régulière des poubelles ne nettoiera que les anciens fichiers héritage pour les utilisateurs connus, pas les fichiers préchargés SuperCache. Ce paramètre est recommandé lorsque le cache est préchargé.Dans de très rares cas, deux problèmes peuvent survenir sur certains blogs:
    1. La page de garde peut commencer à se télécharger comme un fichier zip.
    2. Une mauvaise page est parfois mise en cache en tant que page de garde si votre blog utilise une page de garde statique et que la structure des permaliens est /%category%/%postname%/.
    Il semble que le Mode Réécriture ne soit pas installé. Parfois, cette vérification n'est pas fiable à 100%, surtout si vous n'utilisez pas Apache. Merci de vérifier que le module mode réécriture est chargé. Il est nécessaire pour se servir des fichiers statiques Super Cache. Vous serez toujours en mesure d'utiliser des modes Héritage ou PHP.Il semble que votre blog possède des URLs qui se terminent par un "/". Malheureusement, depuis que vous avez installé cette extension, un bug de duplicate content a été découvert, dans lequel les URLs ne se terminant pas par un "/" servent le même contenu que celles finissant par le "/", et ne redirigent pas vers la bonne URL. Pour le résoudre, vous devez éditer votre fichier .htaccess et ajouter ces deux règles aux deux groupes de règles de Super Cache :CléMise en cache de page Héritée.Moins de mails, 1 au début et 1 à la fin du préchargement de tous les articles.Liste de tous les fichiers mis en cacheListe les pages les plus récemment mises en cache sur cette page.VerrouillageVerrouillage :Niveau d'enregistrementType d'EnregistrementSe connecter à un fichier est plus facile, mais se heurte au problème qu'effacer le cache effacera le fichier des enregistrements.Accélérez WordPressLaissez en blanc la zone de texte pour la supprimer de la liste des pages directes et supprimer le fichier mis en cache.De nombreux e-mails, 2 e-mails pour 100 commentaires.Moyen, 1 e-mail pour 100 commentaires.DiversModules Apache manquantsSupport des systèmes mobiles.Règles de réécriture pour mobiles détectéesLe support de mobiles requiert des règles supplémentaires dans votre fichier .htaccess, ou vous pouvez régler l'extension en Mode Héritage. Voici vos options (par ordre de difficulté) :Règles du Mode RéécritureLes règles du Mode Réécriture ne peuvent pas être mises à jour !Les règles du Mode Réécriture doivent être mises à jour !Règles du Mode Réécriture mises à jour !Le mode Réécriture ne doit pas être installé !Le Mode Réécriture est le plus rapide, le Mode PHP est presque aussi rapide et plus facile à faire fonctionner, tandis que le mode Mise en Cache Héritée est plus lent encore, mais plus souple et plus facile à faire fonctionner. Les nouveaux utilisateurs devraient utiliser la mise en cache PHP.Besoin d'aide ? Lisez le fichier readme de Super Cache. Il inclut une documentation pour l'installation, une FAQ, et des conseils de dépannage. Le forum de support est également disponible. Il a peut-être déjà été répondu à votre question.Plus Récentes Pages Mises en Cache :Le prochain éboueur passera dans %s minutesNote :Note : active la mise en cache PHP, la reconstruction du cache, et le support des mobilesAvis : Le mode de mise en cache réécriture ou héritage est activé. Affichage de la page des Paramètres Avancés par défaut.Avis : règles du mode réécriture SuperCache détectées. Les fichiers mis en cache seront servis à l'aide de ces règles. Editer le fichier .htaccess à la racine de votre installation et supprimer les règles SuperCache.Avis : les contrôles des règles du mode réécriture de WP Super Cache sont désactivés, à moins qu'ils ne s'exécutent sur le site principal de ce réseau.Avis : Les contrôles des règles du mode réécriture de WP Super Cache est désactivé, à moins qu'il ne s'exécute sur le site principal de ce réseau.OKObjet du cache en cours d'utilisation. Pas de liste de cache disponible.Un ou plusieurs requête(s) de page a/ont échoué :Rafraîchir uniquement la page courante lorsqu'un commentaire est effectué.PHP compresse les données envoyées aux visiteurs de votre site. Il est recommandé de désactiver ceci car l'extension met en cache la sortie compressée une seule fois, au lieu de compresser la même page encore et encore. Voir également le #21 dans la section Dépannage. Voir cette page pour obtenir des instructions pour la modification de votre fichier php.ini.Page% d:% d (% s)Page 1 : %sPage 2 : %sPagesErreur de Structure des PermaLiensMerci de créer %s /wp-cache-config.php à partir de wp-super-cache/wp-cache-config-sample.phpMerci de lui adresser aussi un petit "salut !" sur %s !Veuillez lire l'entrée 16 de la section Troubleshooting (dysfonctionnements) du fichier readme.txtMerci de lire le fichier readme.txt pour les instructions relatives à la désinstallation de ce script. Cherchez le titre "How to uninstall WP Super Cache"(\"Comment désinstaller WP Super Cache\" -en anglais).Merci de visiter %1$s pour effacer le cache, car la page de garde de votre site n'est pas correcte et il y manque le texte , "%2$s" !Merci de visiter %s pour effacer le cache, car la page de garde de votre site est en cours de téléchargement !ExtensionsPréchargementPrécharger %s articles.Précharger le Cache MaintenantLe préchargement a été redémarré. %smode de Préchargement (collecte des poubelles uniquement sur les fichiers cache héritage. Recommandé.)Le préchargement crée cependant un nombre important de fichiers. La mise en cache est effectuée des articles les plus récents au plus anciens, donc merci d'envisager de ne mettre en cache que les plus récents, si vous avez un nombre important (10.000 +) d'articles. Ceci est spécialement important pour les hébergements mutualisés.Le Préchargement du cache est désactivé. Merci de désactiver la mise en cache des pages par Héritage, ou parlez-en à l'administrateur de votre hébergement.Prépare votre serveur pour un pic de trafic attendu en activant le mode de verrouillage. Lorsqu'il est activé, les nouveaux commentaires sur un article ne rafraîchissent pas les fichiers statiques du cache.Annoncez fièrement au Monde que votre serveur est compatible avec Digg ! (affiche un message dans le pied-de-page de votre blog)Mode Lecture Seule. La configuration ne peut pas être modifiée.Lecture Seule :RecommandéRafraîchir les fichiers de préchargement du cache toutes les %s minutes. (0 pour désactiver, au minimum %d minutes.)Rafraîchissez cette page lorsque les autorisations de fichiers auront été modifiées.Rafraichissez cette page après avoir mis à jour votre fichier .htaccess.Rafraîchissement des articles suivants :Regénérer les statistiques du cacheUser Agents rejetésRequis pour servir les fichier compressés Supercache proprement.Requis pour attacher les informations de mise en cache aux pages SuperCache. Les utilisateurs d'IE7 ne verront que les anciennes pages sans ce module.Restaurer la Configuration par DéfautLes règles de Réécriture doivent être mises à jourLes règles. doivent également être ajoutées à %s :Le fichier d'exemple de configuration de WP-Cache (%s) n'existe pas. Vérifiez votre installation.SauvegarderSauvegarder les FichiersSauvegarder les ChaînesSauvegarder les Listes d'User AgentsPréchargement programmé du cache annulé.Préchargement programmé du cache annulé. Si un travail est actuellement en cours, il ne s'arrêtera pas jusqu'à ce que les 100 pages en cours soit terminées.Préchargement programmé du cache dans %d minutesPréchargement programmé du cache dans 10 secondes.Prochain rafraîchissement de préchargement programmé dans %d minutes.Défilez jusqu'à la page Paramètres Avancés et cliquez sur le bouton Mise à Jour des Règles du Mode Réécriture.Page de RechercheM'envoyer un mail d'état de statuts lorsque les fichiers sont rafraîchis.Envoi d'une requête non-sécurisée ( non-https) pour la page d'accueilRègle la date d'expiration sur les pages mises en cache par Supercache. Les visiteurs ne pourront pas voir les nouvelles pages lorsqu'ils rafraîchiront, ou lorsqu'ils laisseront des commentaires, sans ce module.Réglez le délai d'expiration à 0 secondes pour désactiver l'éboueur.Règle l'extension en Mode Héritage et active le support pour mobiles.OptionsArticles SimplesDésolé. Mon blog est verrouillé. Les mises à jours vont apparaître rapidement.Vieux Fichiers Mis en Cache par Super CacheFichiers Périmés mis en cache par WP-CacheChaines de caractères dans l'en-tête HTTP ’User Agents’ qui empêchent WP-Cache de mette en cache les requêtes des robots, spiders et crawlers’. Notez que les fichiers mis en cache par SuperCache sont encore envoyés à ces agents s'ils existent toujours.TagsTest du CacheTestez votre site web mis en cache en cliquant sur le bouton de test ci-dessous.Testeur & ContenusTexte à rechercher sur votre page de garde. Si ce texte est manquant, le cache sera effacé. Laissez en blanc pour désactiver.Merci d'avoir effectué la mise à jour.Le fichier de configuration de WP Super Cache est %s/wp-cache-config.php et ne peut pas être modifié. Ce fichier doit pouvoir être écrit par votre serveur web pour effectuer des modifications.Le cache de votre blog a été effacé parce qu'il manque le texte "%2$s" à la page de garde de votre site. Merci de visiter %1$s pour vérifier le bon effacement du cache.Le cache de votre blog a été effacé car la page de garde de votre site est en cours de téléchargement. Merci de visiter %s pour vérifier que le cache a bien été effacé.Le fichier %s.htaccess ne peut pas être modifié par le serveur web. Merci de corriger ça en utilisant la commande chmod ou votre client ftp.Les modules Apache suivants sont manquants. L'extension fonctionne sans eux en mode héritage. En mode complet SuperCache, vos visiteurs pourront cependant voir les pages endommagées ou du contenu non mis à jour.Les règles du Mode Réécriture ont changé depuis votre dernère installation de cette extension. Malheureusement, vous devez supprimer les anciennes règles de SuperCache avant que les nouvelles soient mises à jour. Rafraîchissez cette page après avoir édité votre fichier .htaccess. Si vous souhaitez mettre à jour manuellement, modifiez la ligne suivante : %1$s de façon qu'elle ressemble à ceci : %2$s. Les seuls changements sont "HTTP_COOKIE", devenant "HTTP:Cookie", et "wordpressuser ", devenant "wordpress". C'est une modification de WordPress 2.5, mais il est rétrocompatible avec les anciennes versions, si vous êtes assez courageux pour utiliser celles-ci.Les pages ne correspondent pas ! Les horodateurs sont différents ou n'ont pas été trouvés !Les règles de réécriture nécessitées par cette extension ont changé ou sont manquantes.Les horodateurs des deux pages correspondent !Il s'agit d'une fonctionnalité avancée seulement, au sens strict : la connaissance à la fois des actions PHP et de celles de WordPress est nécessaire pour la créer.Ceci mettra en cache tous les articles et pages publiés sur votre site. Ça créera des fichiers statiques SuperCache de façon que les visiteurs inconnus (y compris les robots) reçoivent une page mise en cache. Ce qui améliorera probablement votre classement Google, du fait qu'il utilise désormais la vitesse dans ses mesures pour classer les sites Web.Cela n'affectera pas les utilisateurs ordinaires, mais les utilisateurs de mobiles verront des pages non mises en cache.Pour servir les fichiers HTML statiques, votre serveur doit avoir les règles de mode de réécriture correctes ajoutées à un fichier nommé %s.htaccessTrop de fichiers mis en cache, pas de liste possible.Le slash final est requis.URIMalheureusement, WordPress n'arrive pas à trouver le fichier wp-cron.php. Ce script est requis pour un fonctionnement correct de l'éboueur de cette extension, ainsi d'ailleurs que de la publication différée de WordPress et d'autres fonctions critiques.Malheureusement, les règles de réécriture ne peuvent pas être mises à jour automatiquement lorsque WordPress MU s'exécute. Merci d'ouvrir votre fichier .htaccess et d'y ajouter les règles de Mode Réécriture suivantes, au-dessus de toutes les autres règles de ce fichier.Mettre à jour les Pages DirectesMettre à jour les Règles du Mode RéécritureMettre à jour les RéglagesMettre à jour les StatutsUtiliser le mode PHP pour servir les fichiers de cache.Utiliser le Mode Réécriture pour servir les fichiers de cache.Utilisez un objet mis en cache pour stocker les fichiers mis en cache.Voir les règles du Mode RéécritureRéglages WP Super CacheWP Super Cache a vérifié la page de garde de votre blog. Merci de visiter %s si vous souhaitez désactiver ceci.WP Super Cache est désactivé. Merci de vous rendre sur la page d'administration de l'extension pour activer la mise en cache.Les règles du Mode Réécriture de WP Super Cache ont été détectées dans votre fichier %s.htaccess.
    Cliquez sur le lien ci-dessous pour voir les lignes ajoutées à ce fichier. Si vous avez mis à jour l'extension, assurez-vous que ces règles correspondent.WP Super Cache doit être configuré. Allez sur La page d’administration pour activer et configurer le plugin.WP-CacheWP-Super-CacheAttentionAttention!Attention ! %s peut être écrit !Attention ! Le Mode Sécurité PHP est activé !Attention ! Votre nom de domaine "%s" se traduit par %sWordPress MU DétectéWordPress est verrouillé. Les fichiers statiques Super Cache ne seront pas supprimés lorsque de nouveaux commentaires sont effectués.WordPress n'est pas verrouillé. Les nouveaux commentaires rafraîchiront normalement les fichier statiques Super Cache.Peut être écrit :Vous pouvez éditer vous-même le fichier pour y ajouter les règles suivantes.Vous pouvez aller regarder là où sont les règles et examiner les règles complètes en cliquant sur le lien "Voir les règles du Mode Réécriture" ci-dessous.Vous pourriez rencontrer certains problèmes en exécutant cette extension, car le Mode de Sécurité PHP est activés.Vous devez avoir les marqueurs BEGIN et END dans %s.htaccess pour que la mise à jour automatique fonctionne. Ils ressemblent à ceci, et entourent les règles principales du mode réécriture de WordPress :Vous devez rendre %s apte à être écrit pour activer cette fonction. Comme il s'agit d'un risque de sécurité, veuillez le remettre en mode lecture seule après que votre page ait été générée.Vous ou un administrateur pouvez être en mesure de le faire fonctionner en modifiant le groupe du propriétaire des scripts de l'extension pour le faire correspondre à celui de l'utilisateur du serveur web. Le groupe du propriétaire du répertoire de %s/cache/ doit également être modifié. Voir la page du manuel du Mode Sécurité pour plus de détails.Vous ou un administrateur devez désactiver ceci. Voir la page du manuel du Mode Sécurité pour plus de détails. Ça ne peut malheureusement pas être désactivé dans un fichier .htaccess. Ça doit l'être dans le fichier de configuration php.ini.Vous devriez modifier les permissions sur %s et les rendre plus restrictives. Utilisez votre client FTP, ou la commande ci-dessous, pour résoudre ces choses :Votre fichier %s.htaccess ne peut pas être écrit par le serveur Web et doivent être mises à jour avec les règles du Mode Réécriture nécessaires. Les nouvelles règles se placent au-dessus des règles standard de WordPress comme montré dans le code suivant :Votre fichier de configuration WP-Cache (%s) est obsolète et ne peut pas être écrit par le serveur Web. Veuillez le détruire et rafraîchir cette page.Votre répertoire de cache ($cache_path) n'existe pas et n'a pas pu être créé par le serveur web. Vérifiez les permissions %s.Votre répertoire de cache (%1$s) ou %2$s) doit pouvoir être écrit pour que cette extension fonctionne. Vérifiez doublement.Votre commentaire est en attente de modération.Votre serveur est configuré pour vérifier le propriétaire des scripts PHP avant de les autoriser à lire et écrire les fichiers.Votre serveur pense que votre nom de domaine se traduit en tant que %s. Certains services comme l'éboueur de cette extension, et la publication différée de WordPress, peuvent ne pas fonctionner correctement.Compression Zlib Output activée ![%1$s] %2$d articles rafraîchis[%1$s] Préchargement du Cache Démarré[%1$s] Rafraîchissement des articles de %2$d à %3$d.[%s] Préchargement du Cache Terminé[%s] Vérification de la Page de garde ![%s] La page de garde est \"gzippée\" ! Cache effacé ![%s] La page de garde est \"gzipée\" ! Merci d'effacer le cache ![%s] La page de garde n'est pas correcte ! Cache effacé ![%s] La page de garde n'est pas correcte ! Merci d'effacer le cache ![%s] Le préchargement peut avoir décroché.tousdésactivéactivéfichiersecondeslanguages/wp-super-cache-ja.po000066600000266365152133035240012311 0ustar00msgid "" msgstr "" "Project-Id-Version: ja\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2011-02-23 17:57:46+00:00\n" "PO-Revision-Date: \n" "Last-Translator: JOTAKI, Taisuke \n" "Language-Team: ja \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: \n" "X-Poedit-Language: Japanese\n" "X-Poedit-Country: JAPAN\n" "X-Poedit-SourceCharset: utf-8\n" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "Bad Behaviour が見つかりませんでした。インストールを確認してください。" #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "Bad Behavior" #: plugins/badbehaviour.php:65 #: plugins/awaitingmoderation.php:34 #: plugins/domain-mapping.php:60 #: wp-cache.php:1205 msgid "Enabled" msgstr "有効" #: plugins/badbehaviour.php:66 #: plugins/awaitingmoderation.php:35 #: plugins/domain-mapping.php:61 #: wp-cache.php:1205 msgid "Disabled" msgstr "無効" #: plugins/badbehaviour.php:68 msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(レガシーキャッシングのみサポートしています。圧縮が無効になっていて、\"%s/plugins/bad-behavior/\" に Bad Behavior が必要です)" #: plugins/badbehaviour.php:71 #: plugins/awaitingmoderation.php:40 #: plugins/searchengine.php:69 #: plugins/domain-mapping.php:66 #: wp-cache.php:1552 msgid "enabled" msgstr "使用中" #: plugins/badbehaviour.php:73 #: plugins/awaitingmoderation.php:42 #: plugins/searchengine.php:67 #: plugins/domain-mapping.php:68 msgid "disabled" msgstr "停止中" #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "Bad Behavior のサポートは現在%sです。" #: plugins/badbehaviour.php:76 #: plugins/awaitingmoderation.php:45 #: plugins/domain-mapping.php:71 msgid "Update" msgstr "更新" #: plugins/badbehaviour.php:83 #: wp-cache.php:1295 #: wp-cache.php:1297 msgid "Warning!" msgstr "警告 !" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "あなたのコメントは管理者の承認待ちです。" #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "承認待ち" #: plugins/awaitingmoderation.php:36 msgid "Enables or disables plugin to Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment." msgstr "モデレートされたコメントが残されたときに表示されるテキスト \"あなたのコメントはモデレーション待ちです。\" を取り除くプラグインの有効化もしくは無効化。" #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "承認待ちは%s件です。" #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1218 msgid "Disable" msgstr "停止する" #: plugins/searchengine.php:71 msgid "No Adverts for Friends plugin is %s." msgstr "No Adverts for Friends プラグインは%sです。" #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(friendsadverts.php も必要です) " #: plugins/searchengine.php:74 #: wp-cache.php:1218 msgid "Enable" msgstr "使用する" #: plugins/domain-mapping.php:58 msgid "Domain Mapping" msgstr "ドメインマッピング" #: plugins/domain-mapping.php:63 msgid "Provides support for Domain Mapping plugin to map multiple domains to a blog." msgstr "ドメインマッピングをサポートしてブログに複数のドメインをマップします。" #: plugins/domain-mapping.php:69 msgid "Domain Mapping support is now %s" msgstr "ドメインマッピングのサポートは現在%sです。" #: plugins/domain-mapping.php:83 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "ドメインマッピングプラグインを検知しました ! Supercache プラグインの設定ページを開いてドメインマッピングのヘルパープラグインを有効化してください。" #: ossdl-cdn.php:146 msgid "Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull." msgstr "おそらく、あなたのサイトでもたくさんの静的ファイルを使用していると思います。画像、JavaScript、CSS のファイルは通常は静的なファイルで、別サイトもしくはCDN から提供させるようにするのはとても簡単です。そのため、このプラグインでは wp-content と wp-includes ディレクトリ内の PHP ファイルを除くすべてのリンクを以下で指定している URL に入れ替える機能があります。すべての静的コンテンツを専用サーバーにコピーするか、origin pull で CDN にファイルをミラーすることができます。" #: ossdl-cdn.php:147 #: wp-cache.php:968 msgid "The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin." msgstr "origin pull に頼りたくない場合は、Amazon S3/Cloudfront へのファイルのアップロードをサポートする CDN Sync Tool プラグインが役に立つでしょう。このプラグインに関して質問がある場合はプラグインサポートフォーラムを参照してください。" #: ossdl-cdn.php:148 msgid "WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes." msgstr "注意: 変更を保存する前に静的な URL、%s などで CDN サービスが完全に動作していることを確認してください。" #: ossdl-cdn.php:149 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "マルチサイトネットワーク上の場合は各サイトに別々の CDN URL を設定することができます。" #: ossdl-cdn.php:157 msgid "Enable CDN Support" msgstr "CDN サポートを有効化" #: ossdl-cdn.php:160 msgid "Off-site URL" msgstr "オフサイト URL" #: ossdl-cdn.php:163 msgid "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "%1$s の代わりに新しい URL がrewriteに使われます。最後の / は付けないようにしてください。
    例: %2$s。" #: ossdl-cdn.php:167 msgid "Include directories" msgstr "含めるディレクトリ" #: ossdl-cdn.php:170 msgid "Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty." msgstr "静的ファイルマッチングに含むディレクトリです。コンマで区切ってください。デフォルトは wp-content, wp-includes で、この欄が空欄の場合は強制的にこのデフォルトが使用されます。" #: ossdl-cdn.php:174 msgid "Exclude if substring" msgstr "除外するサブストリング" #: ossdl-cdn.php:177 msgid "Excludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "上記文字列にマッチするファイルはrewriteから除外されます。複数の場合は .php, .flv, .do のようにコンマで区切ってください。.php は常に含めてください。(デフォルト)" #: ossdl-cdn.php:181 msgid "Additional CNAMES" msgstr "追加 CNAME" #: ossdl-cdn.php:184 msgid "These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$s" msgstr "上記 CNAME は %1$s の代わりに (さらに上のオフサイト URL に加えて) rewriteで使用されます。複数の場合はコンマで区切ってください。静的ファイルが多数あるページの場合にブラウザーのパフォーマンスを改善できます。CNAME は CDN で設定する必要があるかもしれません。
    例: %2$s" #: ossdl-cdn.php:188 msgid "Skip https URLs to avoid \"mixed content\" errors" msgstr "\"mixed content\" エラーを避けるために https の URL をスキップする" #: ossdl-cdn.php:192 msgid "Save Changes" msgstr "変更を保存" #: ossdl-cdn.php:194 msgid "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "CDN 機能は Mark Kubacki の OSSDL CDN Off Linker によって提供されています。" #: wp-cache.php:99 msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "wp-super-cache/wp-cache-config-sample.php から %s /wp-cache-config.php を作成してください。" #: wp-cache.php:162 msgid "Warning! PHP Safe Mode Enabled!" msgstr "警告 ! PHP セーフモードが有効になっています !" #: wp-cache.php:163 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "セーフモードが有効なため、このプラグインの動作に問題が発生するかもしれません。" #: wp-cache.php:167 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "お使いのサーバーではファイルの読み書きの許可の前に PHP スクリプトのオーナーを確認するように設定されています。" #: wp-cache.php:168 msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "あなたもしくは管理者が、このプラグインスクリプトのグループオーナーをウェブサーバーのユーザーと一致するように変更すれば動作するようになるかもしれません。%s/cache/ ディレクトリのグループオーナーは変更する必要があります。詳細は safe mode manual page を参照してください。" #: wp-cache.php:170 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "あなたもしくは管理者がこの機能を無効にする必要があります。詳細は safe mode manual page をご覧ください。残念ながら .htaccess ファイル内では無効にできません。php.ini 設定ファイルで無効にする必要があります。" #: wp-cache.php:176 msgid "Permlink Structure Error" msgstr "パーマリンク構造エラー" #: wp-cache.php:177 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "このプラグインが正しく動作するためにはカスタムな URL (もしくはパーマリンク) 構造が必要です。パーマリンク設定画面を開いてパーマリンクを設定してください。" #: wp-cache.php:189 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "警告 ! ホスト名 \"%s\" が %s に設定されています" #: wp-cache.php:190 msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "お使いのサーバーはホスト名が %s に設定されています。このプラグインのガーベージコレクションや WordPress の予約投稿などのサービスが正しく動作しないかもしれません。" #: wp-cache.php:191 #: wp-cache.php:205 msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "readme.txt Troubleshooting section の 16 を参照してください" #: wp-cache.php:204 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "残念ながら WordPress が wp-cron.php ファイルを見つけられません。WordPress による予約投稿やその他の重要な活動だけでなく、このプラグインによるガベージコレクションの正常なオペレーションにもこのスクリプトが不可欠です。" #: wp-cache.php:219 msgid "Cannot continue... fix previous problems and retry." msgstr "継続できません…前の問題を修正して再度お試しください。" #: wp-cache.php:228 msgid "Zlib Output Compression Enabled!" msgstr "Zlib アウトプット圧縮を有効にしました !" #: wp-cache.php:229 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP がサイト訪問者に送るデータを圧縮しています。このプラグインは同じページを何度も圧縮するのではなく、圧縮した出力をキャッシュするだけなので、この機能は無効にすることをおすすめします。また、トラブルシューティングの #21 も参考にしてください。 php.ini の修正については「実行時設定」の説明をご覧ください。" #: wp-cache.php:233 msgid "Mod rewrite may not be installed!" msgstr "Mod rewrite がインストールされていないようです !" #: wp-cache.php:234 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "mod_rewrite がインストールされていないようです。このチェックは、特に Apache を使用していない場合、100% 信用できないことがあります。mod_rewrite モジュールが読み込まれているかよく確認してください。このモジュールは Super Cache 静的ファイルの提供に不可欠です。ただし、レガシーもしくは PHP モードは使用できます。" #: wp-cache.php:239 msgid "Read Only Mode. Configuration cannot be changed." msgstr "読み込み専用モード。設定は変更できません。" #: wp-cache.php:240 msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "WP Super Cache 設定ファイルは %s/wp-cache-config.php で、変更できません。変更するにはこのファイルにウェブサーバーが書き込みできるようにする必要があります。" #: wp-cache.php:241 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "これを行なう簡単な方法としては、CHMOD コマンドや ftp クライントを使用して一時的に権限を変更する方法があります。グローバルに書き込み可能で問題ないことを確認してください。" #: wp-cache.php:242 #: wp-cache.php:258 msgid "This page explains how to change file permissions." msgstr "ファイルパーミッションの変更はこのページを参考にしてください。" #: wp-cache.php:243 msgid "Writeable:" msgstr "書き込み可能:" #: wp-cache.php:244 msgid "Readonly:" msgstr "読込みのみ:" #: wp-cache.php:256 msgid "Warning! %s is writeable!" msgstr "警告 ! %s が書き込み可能になっています！" #: wp-cache.php:257 msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "%s の権限を変更して、より限定されたものにしてください。ftp クライアントもしくは次のコマンドを使用して修正してください:" #: wp-cache.php:267 msgid "Mobile rewrite rules detected" msgstr "モバイル用 rewrite ルールを検知しました" #: wp-cache.php:268 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "パフォーマンスを最大にするには \"モバイル機器サポート\"を使用するか、.htaccess の mobile rewrite ルールを削除してください。\"2.0\\ MMP|240x320\" の 2 行を探して削除してください。" #: wp-cache.php:268 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "この機能は通常のユーザーには何も影響ありませんが、モバイルユーザーにはキャッシュされたページを表示します。" #: wp-cache.php:274 #: wp-cache.php:285 msgid "Rewrite rules must be updated" msgstr "Rewrite ルールを更新する必要があります" #: wp-cache.php:275 #: wp-cache.php:286 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "このプラグインに必要な rewrite ルールが変更されたか無くなっています。" #: wp-cache.php:276 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "モバイルサポートには .htaccess ファイルにルールを追加する必要があります。もしくはプラグインをレガシーモードに設定します。次のオプションがあります (難しい順):" #: wp-cache.php:277 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "レガシーモードに設定し、モバイルサポートを使用します。" #: wp-cache.php:278 #: wp-cache.php:287 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "詳細設定ページでスクロールダウンして Mod_Rewrite ルールを更新 ボタンをクリックしてください。" #: wp-cache.php:279 msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "%s.htaccess 内の # BEGIN WPSuperCache と # END WPSuperCache で囲まれたこのプラグインの mod_rewrite ルールを削除して、ページを再読込みしてプラグインに再生成させてください。" #: wp-cache.php:280 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "自分でルールを追加する。%s.htaccess を開いて # BEGIN WPSuperCache と # END WPSuperCache で囲まれているコードブロックを探します。とてもよく似ているセクションが 2 箇所あります。code>%%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$     の下に次の行を追加します: (これを 2 回、各セクションで実施します)" #: wp-cache.php:293 msgid "Required to serve compressed supercache files properly." msgstr "正しく圧縮された supercache ファイルを提供する必要があります。" #: wp-cache.php:293 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "supercache のページでキャッシングの設定が必要です。IE7 ユーザーはこのモジュールがないと古いページを参照します。" #: wp-cache.php:293 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "supercached ページで有効期限を設定してください。このモジュールがないと、読者は再読込みしたりコメントを残しても新しいページを参照できないかもしれません。" #: wp-cache.php:300 msgid "Missing Apache Modules" msgstr "欠けている Apache モジュール" #: wp-cache.php:301 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "次の Apache モジュールが見つかりません。これらのモジュールがなしの場合、レガシーモードで動作します。フル Supercache モードでは、閲覧者は壊れたページや古いデータを閲覧するかもしれません。" #: wp-cache.php:459 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "警告 ! 圧縮を有効にしようとしましたが、zlib.output_compression が有効になっています。readme ファイルのトラブルシューティング #21 を参照してください。" #: wp-cache.php:550 msgid "WP Super Cache Settings" msgstr "WP Super Cache 設定" #: wp-cache.php:561 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "お知らせ: Mod_rewrite もしくはレガシーキャッシングが有効になっています。詳細設定ページをデフォルトで表示します。" #: wp-cache.php:572 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "設定ファイルが変更され、いくつかの値が誤っています。\"設定\"メニューからページを再読込みしてリセットしてください。" #: wp-cache.php:597 msgid "Caching must be enabled to use this feature" msgstr "この機能を利用するにはキャッシングを有効にしてください。" #: wp-cache.php:615 #: wp-cache.php:746 msgid "Cancel Cache Preload" msgstr "キャッシュプリロードをキャンセル" #: wp-cache.php:623 #: wp-cache.php:634 msgid "Scheduled preloading of cache cancelled." msgstr "予定されていたキャッシュのプリロードがキャンセルされました。" #: wp-cache.php:660 #: wp-cache.php:744 msgid "Preload Cache Now" msgstr "キャッシュプリロードをすぐに実行" #: wp-cache.php:664 msgid "Scheduled preloading of cache in 10 seconds." msgstr "10 秒後にキャッシュのプリロードを開始します。" #: wp-cache.php:669 msgid "Scheduled preloading of cache in %d minutes" msgstr "%d 分後にキャッシュのプリロードを開始します。" #: wp-cache.php:673 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "この機能はこのサイトで公開されているすべての投稿と固定ページをキャッシュします。Super Cache の静的ファイルが生成されるので、訪問者 (botも含む) はキャッシュされたページを閲覧することになります。これにより、ウェブサイトの測定基準のひとつとして「速さ」を採用している Google ランキングの改善に役立つかもしれません。" #: wp-cache.php:674 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "プリロード機能は大量のファイルを生成します。キャッシュは新しい投稿から先に生成するので、投稿記事がたくさん (1万ページ以上) ある場合は新しい投稿記事だけをキャッシュするようにしてください。これは共有サーバーを使用しているときは特に重要です。" #: wp-cache.php:675 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "’プリロードモード’ では、定期ガーベージコレクションは既存ユーザー用の古いレガシーファイルのみ削除し、プリロードされた supercache ファイルは削除しません。これはキャッシュがプリロードされたときの推奨設定です。" #: wp-cache.php:679 msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "プリロードされたキャッシュファイルは %s 分毎にリフレッシュされます。(0 にすると無効、最小 %d 分)" #: wp-cache.php:692 msgid "all" msgstr "すべて" #: wp-cache.php:705 msgid "Preload %s posts." msgstr "%s 件の投稿をプリロード。" #: wp-cache.php:712 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "プリロードモード (レガシーなキャッシュファイルに対してのみガーベージコレクションを実行。推奨)" #: wp-cache.php:715 msgid "Send me status emails when files are refreshed." msgstr "ファイルリフレッシュ時にステータスメールを送信する。" #: wp-cache.php:720 msgid "Many emails, 2 emails per 100 posts." msgstr "メール多数。投稿数 100 につき 2 件のメール。" #: wp-cache.php:723 msgid "Medium, 1 email per 100 posts." msgstr "中くらいのメール数。投稿数 100 につき 1 件のメール。" #: wp-cache.php:726 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "メール少数。すべての投稿のプリロードの最初と最後に 1 件づつのメール。" #: wp-cache.php:730 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "キャッシュのリフレッシュは %d 時間 %d 分 %d 秒後です。" #: wp-cache.php:731 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "キャッシュの完全リフレッシュは %d 時間 %d 分 %d 秒後です。" #: wp-cache.php:737 msgid "Currently caching from post %d to %d." msgstr "投稿 %d から %d のキャッシュを作成中" #: wp-cache.php:741 msgid "Page last cached: %s" msgstr "最後にキャッシュされたページ: %s" #: wp-cache.php:744 msgid "Update Settings" msgstr "設定を更新" #: wp-cache.php:752 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "キャッシュのプリロードは停止しています。レガシーなページキャッシングを無効にするかホスト管理者に伝えてください。" #: wp-cache.php:769 #: wp-cache.php:865 msgid "Caching" msgstr "キャッシング" #: wp-cache.php:773 msgid "Cache hits to this website for quick access." msgstr "ヒットしたページをキャッシュし、素早くアクセスさせる。" #: wp-cache.php:773 #: wp-cache.php:774 #: wp-cache.php:791 #: wp-cache.php:796 #: wp-cache.php:799 #: wp-cache.php:800 #: wp-cache.php:813 #: wp-cache.php:868 msgid "Recommended" msgstr "推奨" #: wp-cache.php:774 msgid "Use mod_rewrite to serve cache files." msgstr "キャッシュファイルの提供に mod_rewrite を利用する。" #: wp-cache.php:775 msgid "Use PHP to serve cache files." msgstr "キャッシュファイルの提供に PHP を利用する。" #: wp-cache.php:776 msgid "Legacy page caching." msgstr "レガシーなページキャッシング。" #: wp-cache.php:777 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching." msgstr "Mod_rewrite が最速で、PHP はほぼ同じ速さで動作させるのがより簡単です。レガシーキャッシングは遅いですが、より柔軟で動作させるのが簡単です。新しいユーザーは PHP キャッシングを利用するようにしてください。" #: wp-cache.php:783 msgid "Miscellaneous" msgstr "その他" #: wp-cache.php:789 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "注意 ! gzencode() 関数が見つからないため圧縮は無効です。" #: wp-cache.php:791 msgid "Compress pages so they’re served more quickly to visitors." msgstr "ページを圧縮し、訪問者により速くページを供給する。" #: wp-cache.php:792 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "ホストによっては圧縮されたファイルで問題が発生する場合があるので、デフォルトでは無効にしています。この機能を有効にして無効にすると、キャッシュがクリアされます。" #: wp-cache.php:796 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Not Modified ブラウザーキャッシング。最後にリクエストされてから変更がないことを示す。" #: wp-cache.php:797 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "304 サポートはデフォルトでは無効にしています。過去に GoDaddy で問題が発生したことがあるためです。" #: wp-cache.php:799 msgid "Don’t cache pages for known users." msgstr "既知のユーザー向けにはページをキャッシュしない。" #: wp-cache.php:800 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "キャッシュリビルド。新しいファイルの生成中にこのサイトの登録ユーザー以外のユーザーに supercache のファイルを供給する。" #: wp-cache.php:801 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "使用しているサーバーが Digg に耐えられることを誇らしげに表示する (フッターにメッセージを表示する)" #: wp-cache.php:807 #: wp-cache.php:1056 #: wp-cache.php:1563 msgid "Advanced" msgstr "詳細" #: wp-cache.php:811 msgid "Mobile device support." msgstr "モバイル機器サポート" #: wp-cache.php:812 msgid "Clear all cache files when a post or page is published." msgstr "投稿や固定ページの公開時にすべてのキャッシュファイルを削除する。" #: wp-cache.php:813 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "追加のホームページチェック。(非常にまれにホームページのキャッシングを止めることがあります)" #: wp-cache.php:814 msgid "Only refresh current page when comments made." msgstr "コメントが投稿されたときに該当のページだけリフレッシュする。" #: wp-cache.php:815 msgid "List the newest cached pages on this page." msgstr "キャッシュされた最新のページを一覧表示する。" #: wp-cache.php:817 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "荒削りなファイルロック。おそらく必要ないですが、使用しているサーバーが非力な場合には役に立つかもしれません。警告 ! まれにですがサーバーを止めてしまうことがあります !" #: wp-cache.php:819 msgid "Late init. Display cached files after WordPress has loaded. Most useful in legacy mode." msgstr "遅延 init。WordPress が読み込んだ後にキャッシュされたファイルを表示します。レガシーモードで有益です。" #: wp-cache.php:821 msgid "Use object cache to store cached files." msgstr "キャッシュファイルの保存にオブジェクトキャッシュを使用する。" #: wp-cache.php:821 msgid "(Experimental)" msgstr "(実験的)" #: wp-cache.php:828 msgid "Note:" msgstr "メモ:" #: wp-cache.php:830 msgid "Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided." msgstr "アンインストールはプラグインページから行ないます。不要なものは自動的に除去されますが、もし手動での操作が必要な場合は簡単な説明が表示されます。" #: wp-cache.php:831 msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "このプラグインをアンインストールする場合、%s ディレクトリがウェブサーバーによる書き込みを許可していることを確認してください。許可してあれば advanced-cache.php と cache-config.php は自動的に削除されます。(これらのファイルも書き込み可能になっているかも確認したほうがいいかもしれません !)" #: wp-cache.php:832 msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "アンインストールの説明は readme.txt の \"How to uninstall WP Super Cache\" を参照してください。" #: wp-cache.php:833 msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "お困りですか ? Super Cache readme ファイルを読んでみてください。このファイルにはインストールのドキュメント、よくある質問とその答え、トラブルシューティングのヒントが含まれています。また、サポートフォーラム も利用可能です。あなたの問題の答がすでにあるかもしれません。" #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "ステータスを更新" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "受け付けるファイル名と除外する URI" #: wp-cache.php:868 msgid "Caching On" msgstr "キャッシング利用" #: wp-cache.php:869 msgid "Caching Off" msgstr "キャッシング停止" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "メモ: PHP キャッシング、キャッシュリビルド、モバイルサポートを有効化します。" #: wp-cache.php:880 msgid "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "お知らせ: PHP キャッシングが有効化されていますが Supercache mod_rewrite ルールが検知されました。キャッシュされているファイルはこのルールを利用して提供されます。サイトの表示に問題がなければこのメッセージは無視してください。もし問題があれば、WordPress のルートにある .htaccess ファイルを開いて SuperCache のルールを取り除いてください。" #: wp-cache.php:885 msgid "Cache Tester" msgstr "キャッシュテスター" #: wp-cache.php:886 msgid "Test your cached website by clicking the test button below." msgstr "下のテストボタンをクリックするとキャッシュされたページをテストできます。" #: wp-cache.php:892 msgid "Fetching %s to prime cache: " msgstr "キャッシュを準備するために %s を取得: " #: wp-cache.php:894 #: wp-cache.php:902 #: wp-cache.php:910 msgid "OK" msgstr "OK" #: wp-cache.php:897 msgid "Fetching first copy of %s: " msgstr "%s の最初のコピーを取得中: " #: wp-cache.php:905 msgid "Fetching second copy of %s: " msgstr "%s の二つめのコピーを取得中: " #: wp-cache.php:913 msgid "One or more page requests failed:" msgstr "ページのリクエストに失敗しました:" #: wp-cache.php:932 #: wp-cache.php:933 msgid "Page %d: %d (%s)" msgstr "ページ %d: %d (%s)" #: wp-cache.php:939 msgid "Page 1: %s" msgstr "ページ 1: %s" #: wp-cache.php:940 msgid "Page 2: %s" msgstr "ページ 2: %s" #: wp-cache.php:941 msgid "The timestamps on both pages match!" msgstr "両方のページのタイムスタンプがマッチしました !" #: wp-cache.php:943 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "ページがマッチしません ! タイムスタンプが違うか見つかりません !" #: wp-cache.php:950 msgid "Send non-secure (non https) request for homepage" msgstr "非セキュア (https ではない) なホームページへのリクエストを送信" #: wp-cache.php:951 msgid "Test Cache" msgstr "キャッシュをテスト" #: wp-cache.php:955 msgid "Delete Cached Pages" msgstr "キャッシュされているページの削除" #: wp-cache.php:956 msgid "Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below." msgstr "キャシュされたページはお使いのサーバー上に html と PHP ファイルとして保存されます。キャッシュされたページを削除するには下のボタンをクリックしてください。" #: wp-cache.php:959 #: wp-cache.php:2093 #: wp-cache.php:2105 #: wp-cache.php:2268 msgid "Delete Cache" msgstr "キャッシュを削除" #: wp-cache.php:963 msgid "Recommended Links and Plugins" msgstr "おすすめのリンクとプラグイン" #: wp-cache.php:964 msgid "Caching is only one part of making a website faster. Here are some other plugins that will help:" msgstr "キャッシングはウェブサイトを高速化する手段のひとつに過ぎません。役に立つ他のプラグインをご紹介します:" #: wp-cache.php:965 msgid "WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together." msgstr "WP Minify は JavaScript と CSS ファイルを結合させることによりウェブサーバーから送信されるファイルの数を減らします。別の手段としては WPSCMin があります。これは Supercache のプラグインで、JS/CSS ファイルの結合は行ないませんが、キャッシュされたページを小さくします。" #: wp-cache.php:966 msgid "Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix." msgstr "Yahoo! Yslow は Firefox のアドオンの Firebug の拡張機能です。これはウェブページを分析し、ハイパフォーマンスウェブページ用のルールセットをベースにパフォーマンス改善方法を提案します。また、オンラインのパフォーマンスツールの GTMetrix 試してみるといいでしょう。" #: wp-cache.php:967 msgid "Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score." msgstr "Use Google Libraries プラグインにより、一般的に利用されている JavaScript のライブラリのいくつかを Google のウェブサーバーから読み込むようにします。皮肉にも、これにより Yslow のスコアが下がることもあります。" #: wp-cache.php:969 msgid "Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules." msgstr "上級者のみ: Speed up your site with Caching and cache-control (キャッシングと cache-control によるサイトのスピードアップ) では .htaccess ルールでサイトをよりキャッシュする方法を説明しています。" #: wp-cache.php:970 msgid "Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others." msgstr "上級者のみ: オブジェクトキャッシュのインストール。Memcached、XCache、eAcccelerator、もしくは他から選択してください。" #: wp-cache.php:981 msgid "Make WordPress Faster" msgstr "WordPress を速くする" #: wp-cache.php:982 msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s は %2$s と他の多く方の貢献によってメンテナンスされ、開発されています。" #: wp-cache.php:983 msgid "He blogs at %1$s and posts photos at %2$s." msgstr "彼は %1$s でブログを書き、%2$s に写真を投稿しています。" #: wp-cache.php:984 msgid "Please say hi to him on %s too!" msgstr "%s でも彼に一言どうぞ !" #: wp-cache.php:985 msgid "Need Help?" msgstr "助けが必要ですか ?" #: wp-cache.php:987 msgid "Installation Help" msgstr "インストールのヘルプ" #: wp-cache.php:988 msgid "Frequently Asked Questions" msgstr "よくある質問と答え" #: wp-cache.php:989 msgid "Support Forum" msgstr "サポートフォーラム" #: wp-cache.php:991 msgid "Rate This Plugin!" msgstr "このプラグインをレーティングしてください !" #: wp-cache.php:992 msgid "Please rate this plugin and tell me if it works for you or not. It really helps development." msgstr "このプラグインをレーティングして、動作しているかどうかをお知らせください。開発に非常に役立ちます。" #: wp-cache.php:1001 msgid "Cached pages since %1$s : %2$s" msgstr "%1$s 以降のキャッシュページ : %2$s" #: wp-cache.php:1002 msgid "Newest Cached Pages:" msgstr "キャッシュされた最新のページ:" #: wp-cache.php:1006 msgid "Cached %s seconds ago" msgstr "%s 秒前にキャッシュされました" #: wp-cache.php:1009 msgid "(may not always be accurate on busy sites)" msgstr "(アクセスの多いサイトでは必ずしも正確ではないかもしれません)" #: wp-cache.php:1028 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "キャッシュプラグインは PHP のスクリプトで wp-super-cache フォルダ内の plugins フォルダ内にあります。これは Supercache の読み込み時に読み込まれ、通常の WordPress プラグインよりもかなり早い段階で読み込まれます。" #: wp-cache.php:1029 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "これは厳密に言えば拡張機能だけで、作成には PHP と WordPress アクションの両方の知識が必要です。" #: wp-cache.php:1039 msgid "Available Plugins" msgstr "利用可能なプラグイン" #: wp-cache.php:1056 msgid "Easy" msgstr "簡易" #: wp-cache.php:1056 msgid "CDN" msgstr "CDN" #: wp-cache.php:1056 msgid "Contents" msgstr "コンテンツ" #: wp-cache.php:1056 msgid "Preload" msgstr "プリロード" #: wp-cache.php:1056 msgid "Plugins" msgstr "プラグイン" #: wp-cache.php:1056 msgid "Debug" msgstr "デバッグ" #: wp-cache.php:1091 msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "お知らせ: WP Super Cache mod_rewrite ルールチェックは、このネットワークのメインサイトで動作していなければ無効です。" #: wp-cache.php:1100 msgid "Mod Rewrite Rules" msgstr "Mod Rewrite ルール" #: wp-cache.php:1106 msgid "WordPress MU Detected" msgstr "WordPress MU を検知しました" #: wp-cache.php:1106 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "残念ながら、WordPress MU が稼働中は rewrite ルールを自動的に更新できません。.htaccess を開いて次の mod_rewrite ルールをこのファイルの中の他のすべてのルールの上に追加してください。" #: wp-cache.php:1108 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite ルールを更新できません !" #: wp-cache.php:1109 msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "自動更新を作動させるには BEGIN と END マーカーが %s.htaccess 内に必ず必要です。これは次のようになっていて、WordPress のメインの mod_rewrite ルールを囲んでいます:" #: wp-cache.php:1111 msgid "Refresh this page when you have updated your .htaccess file." msgstr " .htaccess ファイルを更新したら、このページを再読込みしてください。" #: wp-cache.php:1115 msgid "Thank you for upgrading." msgstr "アップグレードありがとうございます。" #: wp-cache.php:1115 msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "mod_rewrite ルールは最後にこのプラグインがインストールされてから変更されています。残念ながら、新しいルールを更新する前に古い supercache のルールを取り除く必要があります。.htaccess ファイルを編集したら、このページを再読込みしてください。もし手動でアップグレードしたいならば、次の行を変更してください: %1$s は次に似ています: %2$s 違いは \"HTTP_COOKIE\" が \"HTTP:Cookie\" になり、\"wordpressuser\" が \"wordpress\" になったことだけです。これは WordPress 2.5 での変更ですが、これ以前のバージョンとの後方互換性があります。もしそれほど古いバージョンを使用する勇気があればの話ですが。" #: wp-cache.php:1119 msgid "Trailing slash check required." msgstr "最後のスラッシュの確認が必要です。" #: wp-cache.php:1119 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "あなたのブログの URL は最後が \"/\" になっているようです。残念ながら、このプラグインをインストールした後に重複コンテンツのバグが見つかりました。\"/\" で終わっていない URL は \"/\" で終わっている URL を同じコンテンツとして提供し、正しい URL にリダイレクトしません。これを修正するには .htaccess ファイルを編集してこれら 2 つのルールを Super Cache ルールの 2 つのグループに追加する必要があります。" #: wp-cache.php:1121 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "下の \"mod_rewrite ルールを表示する\" リンクをクリックするとルールを参照して問題ないか確認することができます。" #: wp-cache.php:1135 msgid "Mod Rewrite rules updated!" msgstr "Mod Rewrite ルールを更新しました !" #: wp-cache.php:1136 msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "%s.htaccess が必要な mod_rewrite ルールで更新されました。正しく更新されたか確認してください。次のようになっているはずです:" #: wp-cache.php:1138 msgid "Mod Rewrite rules must be updated!" msgstr "Mod Rewrite ルールを更新する必要があります !" #: wp-cache.php:1139 msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "%s.htaccess はウェブサーバーによる書き込みができません。必要な mod_rewrite ルールで更新する必要があります。新しいルールは以下のコードのように通常の WordPress ルールの上に追加します:" #: wp-cache.php:1144 msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "WP Super Cache mod rewrite ルールが %s.htaccess ファイル内に検知されました。
    次のリンクをクリックしてこのファイルに追加された行を確認してください。プラグインをアップグレードをしたのなら、これらのルールがマッチしていることを確認してください。" #: wp-cache.php:1147 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "現在の .htaccess ファイルと、このプラグインの rewrite ルールに差異が見つかりました。この差異は単純にスペースの数の違いかもしれませんが、できるだけ早くこのファイル内のルールと以下を比較確認してください。’Mod_Rewrite ルールを更新’ をクリックするとこのルールを更新します。" #: wp-cache.php:1150 msgid "View Mod_Rewrite Rules" msgstr "Mod_Rewrite ルールを参照する" #: wp-cache.php:1154 #: wp-cache.php:2384 msgid "Rules must be added to %s too:" msgstr "ルールは %s にも追加する必要があります:" #: wp-cache.php:1162 msgid "Gzip encoding rules in %s.htaccess created." msgstr "Gzip エンコードルール %s.htaccess に作成されました。" #: wp-cache.php:1169 msgid "Fix Configuration" msgstr "設定の修正" #: wp-cache.php:1172 msgid "Restore Default Configuration" msgstr "デフォルト設定を復元" #: wp-cache.php:1180 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "コメントは承認待ちです。表示されるまでしばらく時間がかかるかもしれません。" #: wp-cache.php:1205 msgid "Lock Down:" msgstr "ロックダウン:" #: wp-cache.php:1206 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "ロックダウンを有効にすることにより、予想されるトラフィックの激増に対してサーバーが対処できるようにします。この機能が有効になると、新しいコメントが投稿されてもキャッシュされた静的ファイルは更新されません。" #: wp-cache.php:1207 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "開発者のみなさんへ: \"WPLOCKDOWN\" 定数をチェックすることにより、あなたのプラグインにロックダウンとの互換性を持たせることができます。次のコードにより、あなたのプラグインが WPLOCKDOWN 設置を考慮するようになります。" #: wp-cache.php:1209 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "すみませんが、このブログは一時的に停止中です。間もなく更新されます。" #: wp-cache.php:1213 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress はロックダウンされています。Super Cache の静的ファイルは新しいコメントが投稿されても削除されません。" #: wp-cache.php:1215 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress はロックダウンされていません。新しいコメントが投稿されると Super Cache の静的ファイルは通常通りにリフレッシュされます。" #: wp-cache.php:1221 msgid "Lock Down" msgstr "ロックダウン" #: wp-cache.php:1229 msgid "Directly Cached Files" msgstr "ダイレクトキャッシュファイル" #: wp-cache.php:1287 msgid "%s removed!" msgstr "%s 個を削除しました !" #: wp-cache.php:1295 msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "この機能を利用するには %s を書き込み可能にする必要があります。これにはセキュリティリスクを伴いますので、ページ生成後には読み込みのみにしてください。" #: wp-cache.php:1297 msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s を書き込み可能です。これにはセキュリティリスクを伴いますので、ページ生成後には読み込みのみにしてください。" #: wp-cache.php:1311 msgid "Existing direct page" msgstr "既存のダイレクトページ" #: wp-cache.php:1311 msgid "Delete cached file" msgstr "キャッシュファイルを削除" #: wp-cache.php:1316 msgid "Add direct page:" msgstr "ダイレクトページを追加:" #: wp-cache.php:1318 msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "ダイレクトキャッシュファイルはブログのある %s からダイレクトに生成されたファイルです。この機能は Digg やスラッシュドットなど巨大レベルのトラフィックがひとつの投稿やページに集中することが予想されるときだけ役に立ちます。" #: wp-cache.php:1320 msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "例: %1$sabout/ をキャッシュするには %1$sabout/ もしくは /about/ を入力します。このキャッシュファイルは次に該当のページに誰かが来た時に生成されます。" #: wp-cache.php:1321 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "ダイレクトページのこのリストから取り除くには、テキストボックスをブランクにしてキャッシュファイルを削除してください。" #: wp-cache.php:1326 msgid "Update Direct Pages" msgstr "ダイレクトページを更新" #: wp-cache.php:1364 msgid "Expiry Time & Garbage Collection" msgstr "有効時間とガーベージコレクション" #: wp-cache.php:1366 msgid "Expire time:" msgstr "有効時間:" #: wp-cache.php:1367 msgid "seconds" msgstr "秒" #: wp-cache.php:1368 msgid "Garbage Collection" msgstr "ガーベージコレクション" #: wp-cache.php:1368 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "有効期限が 1800 秒 (30 分) 以上の場合、ガーベージコレクションは 10 分ごとに実行されます。それ以外の場合は期限切れ時間の 10 秒後に実行されます。" #: wp-cache.php:1369 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "期限切れファイルのチェックや削除はそれなりの負荷がかかりますが、そのまま残しておくのも負荷になります。アクセスがかなり多いサイトの場合、有効期限を 300 秒に設定するといいでしょう。いろいろな値でこのページを表示させ、時間帯によってどのくらいの期限切れファイルが残るのかを試してみるといいでしょう。レガシーキャッシュ機能を使用している場合は、できればキャッシュファイルの数は 500 以下になるようにしましょう。mod_rewrite や PHP キャッシングを利用している場合はその何倍ものキャッシュファイルを保持できます。" #: wp-cache.php:1370 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "ガーベージコレクションを無効にするには有効時間を 0 秒に設定してください。" #: wp-cache.php:1371 msgid "Change Expiration" msgstr "有効時間を変更" #: wp-cache.php:1415 msgid "Rejected User Agents" msgstr "除外するユーザーエージェント" #: wp-cache.php:1416 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "WP-Cache が bot、spider、クローラーのリクエストをキャッシュしないようにする HTTP ’User Agent’ ヘッダー内の文字列です。すでにキャッシュが存在する場合はこれらのエージェントに Super Cache のファイルが送信されます。" #: wp-cache.php:1423 msgid "Save UA Strings" msgstr "UA 文字列を保存" #: wp-cache.php:1446 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "次のページタイプはキャッシュしません。各タイプについての詳細は Conditional Tags を参照してください。" #: wp-cache.php:1449 msgid "Single Posts" msgstr "シングルページ" #: wp-cache.php:1450 msgid "Pages" msgstr "ページ" #: wp-cache.php:1451 msgid "Front Page" msgstr "フロントページ" #: wp-cache.php:1452 msgid "Home" msgstr "ホーム" #: wp-cache.php:1453 msgid "Archives" msgstr "アーカイブ" #: wp-cache.php:1454 msgid "Tags" msgstr "タグ" #: wp-cache.php:1455 msgid "Category" msgstr "カテゴリー" #: wp-cache.php:1456 msgid "Feeds" msgstr "フィード" #: wp-cache.php:1457 msgid "Search Pages" msgstr "検索ページ" #: wp-cache.php:1459 #: wp-cache.php:1573 msgid "Save" msgstr "保存" #: wp-cache.php:1476 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "ここにキャッシュしないようにするページの文字列 (ファイル名ではなく) を追加します。例えば、URL に「西暦」を含んでいて昨年の投稿をキャッシュしたくない場合は西暦 ’/2004/’ だけを入力すれば十分です。WP-Chache は URI にその文字列が含まれているか検索し、含まれていた場合はそのページをキャッシュしません。" #: wp-cache.php:1482 msgid "Save Strings" msgstr "文字列を保存" #: wp-cache.php:1498 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "上で指定した除外文字列にマッチしてもキャッシュするファイル名をここに追加してください。" #: wp-cache.php:1504 msgid "Save Files" msgstr "ファイルを保存" #: wp-cache.php:1545 msgid "Currently logging to: %s" msgstr "現在ログ取得中: %s" #: wp-cache.php:1548 msgid "Fix problems with the plugin by debugging it here. It can log them to a file in your cache directory." msgstr "このデバッグ設定でプラグインの問題を修正します。キャッシュディレクトリのファイルにログを記録します。" #: wp-cache.php:1552 msgid "Debugging" msgstr "デバッグ" #: wp-cache.php:1553 msgid "IP Address" msgstr "IP アドレス" #: wp-cache.php:1553 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(この IP アドレスからのリクエストだけを記録します。あなたの IP アドレスは %s です)" #: wp-cache.php:1554 msgid "Log level" msgstr "ログレベル" #: wp-cache.php:1560 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = 小、5 = 大、大きなサーバーのロードを引き起こすかもしれません)" #: wp-cache.php:1563 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "とてもまれなケースですが、2 つの問題が発生することがあります:
    1. フロントページが zip ファイルとしてダウンロードされることがある
    2. 静的なフロントページを使用していてパーマリンク構造が /%category%/%postname%/ の場合にフロントページとして誤ったページがキャッシュされてしまう
    " #: wp-cache.php:1564 msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "WP Super Cache のバグではないと 99% 思いますし、発生するのはごくごく稀ですが、もし心配なら 5 分ごとにサイトが問題ないか確認するよう簡単なチェックができます。もし問題が発生すればメールが届きます。" #: wp-cache.php:1566 msgid "Check front page every 5 minutes." msgstr "5 分ごとにフロントページをチェックする。" #: wp-cache.php:1567 msgid "Front page text" msgstr "フロントページテキスト" #: wp-cache.php:1567 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "フロントページで検索するテキスト。もしこのテキストがなければキャッシュがクリアされます。無効するにはブランクにしてください。" #: wp-cache.php:1568 msgid "Clear cache on error." msgstr "エラー発生時にキャッシュをクリアする。" #: wp-cache.php:1569 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "確認時にブログ管理者にメールを送る。(テスト時に有益)" #: wp-cache.php:1583 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "エラー: GZIP 圧縮が有効です。wp-cache を使用する場合は無効にしてください。" #: wp-cache.php:1630 #: wp-cache.php:1796 msgid "Warning" msgstr "警告" #: wp-cache.php:1630 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "WordPress の GZIP 圧縮が有効です。GZIP 圧縮が無効にされるまで wp-cache はバイパスされます。" #: wp-cache.php:1692 #: wp-cache.php:1697 #: wp-cache.php:1729 #: wp-cache.php:1734 #: wp-cache.php:1740 msgid "Error" msgstr "エラー " #: wp-cache.php:1692 msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "キャッシュディレクトリ ($cache_path) がなく、ウェブサーバーによって作成することもできませんでした。%s のパーミッションを確認してください。" #: wp-cache.php:1697 msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "このプラグインを動作させるにはキャッシュディレクトリ (%1$s) もしくは %2$s に書き込める必要があります。よく確認してください。" #: wp-cache.php:1729 msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "WP-Cache 設定ファイル (%s) は古いもので、ウェブサーバーによる書き込みを許可していません。このファイルを削除してこのページを再読込みしてください。" #: wp-cache.php:1734 msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "設定ファイルが見つかりません。%1$s ディレクトリ (%2$s) がウェブサーバーによる書き込みを許可していません。パーミッションを確認してください。" #: wp-cache.php:1740 msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "WP-Cache の設定サンプルファイル (%s) がありません。インストールを確認してください。" #: wp-cache.php:1796 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php がないか、更新できません。" #: wp-cache.php:1797 msgid "1. If it already exists please delete the file first." msgstr "1. もしこのファイルがすでにあれば、まず最初にこのファイルを削除してください" #: wp-cache.php:1798 msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. ftp やサーバーソフトウェアで chmod コマンドを使用して %1$s を書き込み可能にし、(chmod 777 %1$s) このページを再読込みします。これは一時的な処置で、この後、読み込みのみに再度する必要があります。(前述のコマンドで 777 を 755 に変更します)" #: wp-cache.php:1799 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. %s/advanced-cache.php を更新するためにこのページを再読込みします" #: wp-cache.php:1800 msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "もし動作しなければ %s/advanced-cache.php ファイルが存在するか確認してください:" #: wp-cache.php:1801 msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. テキストエディターで %1$s$wp_cache_file を開きます
  • 2. テキスト CACHEHOME を %2$s に変更します
  • 3. ファイルを保存し、%3$s へコピーしてこのページを再読込みします
    • " #: wp-cache.php:1824 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    WP_CACHE 定数が false に設定されています

    WP_CACHE 定数はキャッシュされたページを提供するためのコードを読み込むために WordPress によって利用される定数です。残念ながらこの定数が false に設定されています。wp-config.php を開いて、最後の require_once コマンドの上に次の行を追加もしくは編集してください。

    define('WP_CACHE', true);

    " #: wp-cache.php:1826 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "エラー: wp-config.php ファイルの WP_CACHE が有効になっていません。このプラグインから修正はできません。" #: wp-cache.php:1827 msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "%s を編集して次の行を追加してください:
    define('WP_CACHE', true);
    追加しないと WordPress コアによる WP-Cache の実行ができません。" #: wp-cache.php:1831 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    WP_CACHE 定数の wp-config.php への追加

    もしこの警告メッセージが表示され続けるのなら、FAQ のポイント 5 を参照してください。WP_CACHE の行を上に上げる必要があります。" #: wp-cache.php:1855 msgid "Cache Contents" msgstr "キャッシュコンテンツ" #: wp-cache.php:1858 msgid "Object cache in use. No cache listing available." msgstr "オブジェクトキャッシュを使用中です。キャッシュリストはありません。" #: wp-cache.php:1882 msgid "Deleting supercache file: %s
    " msgstr "supercache ファイルを削除しています: %s
    " #: wp-cache.php:1899 msgid "Deleting wp-cache file: %s
    " msgstr "wp-cache ファイルを削除しています: %s
    " #: wp-cache.php:1964 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "キャッシュ統計値は自動的には生成されません。再生成するには下のリンクをクリックしてください。" #: wp-cache.php:1965 msgid "Regenerate cache stats" msgstr "キャッシュ状況データを再生成" #: wp-cache.php:1967 msgid "Cache stats last generated: %s minutes ago." msgstr "キャッシュ統計値が最後に生成されたのは %s 分前です。" #: wp-cache.php:1973 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:1974 #: wp-cache.php:1989 msgid "%s Cached Pages" msgstr "キャッシュページ数: %s" #: wp-cache.php:1975 #: wp-cache.php:1994 msgid "%s Expired Pages" msgstr "期限切れページ数: %s" #: wp-cache.php:1988 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1998 msgid "Fresh WP-Cached Files" msgstr "新しい WP-Cache ファイル" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "URI" msgstr "URI" #: wp-cache.php:1999 #: wp-cache.php:2015 msgid "Key" msgstr "キー" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "Age" msgstr "経過時間" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "Delete" msgstr "削除 " #: wp-cache.php:2014 msgid "Stale WP-Cached Files" msgstr "古い WP-Cache ファイル" #: wp-cache.php:2030 msgid "Fresh Super Cached Files" msgstr "新しい Super Cache ファイル" #: wp-cache.php:2046 msgid "Stale Super Cached Files" msgstr "古い Super Cache ファイル" #: wp-cache.php:2062 msgid "Hide file list" msgstr "ファイルリストを隠す" #: wp-cache.php:2064 msgid "Too many cached files, no listing possible." msgstr "キャッシュファイルが多すぎるため一覧表示できません。" #: wp-cache.php:2066 msgid "List all cached files" msgstr "すべてのキャッシュファイルを表示" #: wp-cache.php:2072 msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "ガーベージコレクション
    最後の GC は %s 分前です
    " #: wp-cache.php:2073 msgid "Next GC in %s minutes" msgstr "次の GC は %s 分後です" #: wp-cache.php:2076 msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "期限切れファイルとは %s 秒より古くなったファイルです。こうしたファイルはこのプラグインによってまだ使用されますが、定期的に削除されます。" #: wp-cache.php:2087 msgid "Delete Expired" msgstr "期限切れキャッシュを削除" #: wp-cache.php:2105 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Super Cache のキャッシュファイルを削除する (新しいウインドウで開きます)" #: wp-cache.php:2244 msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s は %2$s でキャッシングされているおかげで Digg に耐えられます" #: wp-cache.php:2277 msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache の設定が必要です。管理ページを開いてこのプラグインの有効化と設定を行なってください。" #: wp-cache.php:2283 msgid "Settings" msgstr "設定" #: wp-cache.php:2293 msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache は停止中です。プラグイン管理ページを開いてキャッシングを有効にしてください。" #: wp-cache.php:2296 msgid "Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct." msgstr "Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct." #: wp-cache.php:2315 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] フロントページが gzip で圧縮されました ! キャッシュをクリアしてください !" #: wp-cache.php:2315 msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "フロントページがダウンロードされる状態なので、%s を開いてキャッシュをクリアしてください !" #: wp-cache.php:2318 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] フロントページが gzip 圧縮されました ! キャッシュがクリアされました !" #: wp-cache.php:2318 msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "フロントページがダウンロードされる状態だったのでブログのキャッシュをクリアしました。%s を開いてキャッシュがクリアされたことを確認してください。" #: wp-cache.php:2325 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] フロントページが不正です ! キャッシュをクリアしてください !" #: wp-cache.php:2325 msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "フロントページが不正でテキスト \"%2$s\" が見つからないので、%1$s を開いてキャッシュをクリアしてください !" #: wp-cache.php:2328 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] フロントページが不正です ! キャッシュがクリアされました !" #: wp-cache.php:2328 msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "フロントページにテキスト \"%2$s\" が見つからなかったのでブログのキャッシュをクリアしました。%1$s を開いてキャッシュがクリアされたことを確認してください。" #: wp-cache.php:2333 msgid "[%s] Front page check!" msgstr "[%s] フロントページチェック !" #: wp-cache.php:2333 msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache はあなたのブログのフロントページをチェックしました。この機能の使用を停止するには %s を開いてください。" #: wp-cache.php:2376 msgid "Cannot update .htaccess" msgstr ".htaccess を更新できません" #: wp-cache.php:2376 msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "%s.htaccessファイルがウェブサーバーによって変更できません。chmod コマンドや ftp クライアントで修正してください。" #: wp-cache.php:2376 msgid "Refresh this page when the file permissions have been modified." msgstr "ファイルのパーミッションを変更したらこのページを再読込みしてください。" #: wp-cache.php:2376 msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "もしくは、%s.htaccess ファイルを手動で編集して次のコードを追加してください (WordPress のルールの前に):" #: wp-cache.php:2380 msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "静的 html ファイルを利用できるようにするには、お使いのサーバーで %s.htaccess と呼ばれるファイルに正しい mod_rewrite ルールが追加されている必要があります。" #: wp-cache.php:2381 msgid "You can edit the file yourself add the following rules." msgstr "このファイルをご自分で編集して次のルールを追加できます。" #: wp-cache.php:2382 msgid " Make sure they appear before any existing WordPress rules. " msgstr "かならず WordPress の既存のルールの前に入れてください。" #: wp-cache.php:2390 msgid "Update Mod_Rewrite Rules" msgstr "Mod_Rewrite ルールを更新" #: wp-cache.php:2515 msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] キャッシュのプリロードが開始されました" #: wp-cache.php:2517 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] %2$d から %3$d の投稿をリフレッシュ中" #: wp-cache.php:2535 msgid "[%1$s] Cache Preload Stopped" msgstr "[%1$s] キャッシュプリロード停止" #: wp-cache.php:2544 msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d の投稿をリフレッシュ" #: wp-cache.php:2544 msgid "Refreshed the following posts:" msgstr "以下の投稿がリフレッシュされました:" #: wp-cache.php:2553 msgid "Scheduling next preload refresh in %d minutes." msgstr "次のプレロードリフレッシュは %d 分後の予定です。" #: wp-cache.php:2563 msgid "[%s] Cache Preload Completed" msgstr "[%s] キャッシュのプリロードを完了" #: wp-cache.php:2563 msgid "Cleaning up old supercache files." msgstr "古い supercache のファイルを片付けています。" #: wp-cache.php:2605 msgid "[%s] Preload may have stalled." msgstr "[%s] プリロードは停滞しています。" #: wp-cache.php:2605 msgid "" "Preload has been restarted.\n" "%s" msgstr "" "プリロードを再スタートしました。\n" "%s" #: wp-cache.php:2648 msgid "Supercache Uninstall Problems" msgstr "Supercache アンインストール時の問題" #: wp-cache.php:2648 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" msgstr "" "ユーザー様へ\n" "\n" "あなたのブログから WP Super Cache が削除されましたが、mod_rewrite ルールは\n" ".htaccess から削除されていません。\n" "\n" "次のファイルを開いて 'BEGIN WPSuperCache' と 'END WPSuperCache' の\n" "あいだのコードを取り除いてください。最初にこのファイルのバックアップを忘れずに !\n" "\n" "%s\n" "\n" "よろしくお願いします。\n" "WP Super Cache プラグイン\n" "http://wordpress.org/extend/plugins/wp-super-cache/" #~ msgid "" #~ "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on " #~ "on the main site of this network." #~ msgstr "" #~ "お知らせ: WP Super Cache mod_rewrite ルールチェックは、このネットワークの" #~ "メインサイトで動作していなければ無効です。" #~ msgid "Tester & Contents" #~ msgstr "テスターとコンテンツ" #~ msgid "" #~ "Logging to a file is easier but faces the problem that clearing the cache " #~ "will clear the log file." #~ msgstr "" #~ "ファイルにログを記録する方が簡単ですが、キャッシュをクリアするとログファイ" #~ "ルもクリアされてしまいます。" #~ msgid "Logging Type" #~ msgstr "ログ形式" #~ msgid "Email" #~ msgstr "メールアドレス" #~ msgid "file" #~ msgstr "ファイル" #~ msgid "WP Super Cache Manager" #~ msgstr "WP Super Cache 管理画面" #~ msgid "Why your configuration may not be changed" #~ msgstr "なぜ設定を変更できないのか" #~ msgid "Why" #~ msgstr "なぜ" #~ msgid "ON" #~ msgstr "オン" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "WP Cache と Super Cache を使用する" #~ msgid "HALF ON" #~ msgstr "ハーフオン" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Super Cache は不使用、古い WP-Cache のキャッシュ機能のみ使用する" #~ msgid "OFF" #~ msgstr "オフ" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "WP Cache と Super Cache を使用しない" #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "キャッシュリビルド。新しいファイルの生成中に supercache ファイルを匿名ユー" #~ "ザーに提供します。とてもたくさんアクセスとたくさんのコメントがつ" #~ "くサイトにおすすめします。\"ダイレクトキャッシュページ\"と \"ロックダウン" #~ "モード\" はサポートされなくなります。" #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "新しくキャッシュされたページをリストアップする (アクセスの多いサイトの場合" #~ "はさらに負荷が上がるかもしれません。注意して使用してください)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s はブログを速くします。Amazon gift card を私に" #~ "買ってくれたらもっと速く*なります。好きなだけ \"%3$s\" に送って" #~ "ください ! どんな金額でも助かります !" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "もし Amazon がお気に召さないのなら、PayPal でお願いします。下の \"Donate" #~ "\" ボタンをクリックするか、私のウィッシュリストをご覧く" #~ "ださい。" #~ msgid "Thanks in advance!" #~ msgstr "よろしくお願いします !" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "オーケー、特に速くはなりませんが、このプラグインの作者がとても幸せになりま" #~ "す !" #~ msgid "Don’t show me this again." #~ msgstr "このお知らせを表示させない。" #~ msgid "Hide" #~ msgstr "隠す" #~ msgid "Super Cache Compression" #~ msgstr "Super Cache 圧縮" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "ハーフオン モードの場合、デフォルトで圧縮を使用します。" #~ msgid "Super Cache compression is now disabled." #~ msgstr "Super Cache 圧縮の使用が停止されました。" #~ msgid "Super Cache compression is now enabled." #~ msgstr "Super Cache 圧縮の使用が開始されました。" #~ msgid "Update Compression" #~ msgstr "圧縮設定の更新" #~ msgid "Debug Settings" #~ msgstr "デバッグ設定" #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "このファイルをご自分で編集して次のルールを追加する必要があります。" #~ msgid "" #~ "Mobile device support using WordPress Mobile Edition." #~ msgstr "" #~ "WordPress Mobile Edition を使用したモバイル機器のサポー" #~ "ト" #~ msgid "" #~ "Uninstall using the uninstall script to remove files and directories created by the " #~ "plugin. (Please see readme." #~ "txt for instructions on uninstalling this script.)" #~ msgstr "" #~ "アンインストールスクリプトを使用してアンインストールすると、このプラグインによって作成されたファイ" #~ "ルとディレクトリを削除します。(詳しくは readme.txt をご覧ください)" #~ msgid "" #~ "He blogs at %1$s, posts photos at %2$s and wishes he " #~ "had more time to read and relax." #~ msgstr "" #~ "彼は %1$s でブログして、%2$s で写真を投稿して、もっと本を読む時間とリラッ" #~ "クスする時間を欲しがっています。" languages/wp-super-cache-be_BY.mo000066600000223721152133035240012661 0ustar009 8<9,vM` s~?3>rb"*7Z5C5y =bj^ \ r&!!?"#w$Z%`%&.&'&((:(n'*p*,,,,, ,3,-"- 1-,>-k-^.p{.+.//./^/ f/ r/+}//3// 00!%0G0!27>2v22I;3@33sK44%?5e5|5 55 5555553616777888u\9j9=:B::?:9;@;H;NN;; ;n;$.<S<Y<v<<<~<@==>> >><>g*??+?*?? @@ AbAA1B:C&D"/EkRFGGEGH*3H ^H hH sH }HbHH]I$aII IIIIIJ$J"JJ! K,KKL&LM<"Mb_MM|uNyNlO0oO!O-OkO\Q mQ xQQQTQQURmRpSUSSSSTTJ5TTd]UU`iV0V V W7WSIW?W<WX9XPX7eXjXY&YDYYcYY Y YY(YZ+Z,Z.Zf![ [/[0[[?x\8\\ \:]B][]q]H^ M^;X^^q^_1__x`aaQb<idGd#due eTf~f+ggggghNibi{i ii%i'ijjj4jbjklk9lBlQlYlbl|l*llbl[@m m7mrmMRnnYo/o qrr?ssRt$tetau v%vAv)^vvv*v/v.w3FwzwwwwwwwFyPy%zz0z {{{|{'}1}6} MQrL<jgih҃rՇ4&8_%vI(&  ) !6>u1/#APeN˛j=;8t%#ޝ4o17i+xQ:A1js.ޣ J=.Mn!ީ"$4G@|'HEM]0"MίŴ~ԴS"o*M 1,F,s4<շi%|!Ļ![!}5UQb $B #1Y^bHd (^>(n5Oj*8cRTU $2EjU6F.WEk8"V: QB<1 @;g|Y>\s2t8C|(+CVo!1NL6_9aWtDzh3~.)K W5sGQC&EWOwQRvckvklbh o |d# 3tVBg'4Hub@}SW) f 7o   l  + D b Ls T p/L  A6ZA %`w%]k r|c9 `!<"B""#("$4K$;$E$;%:>%oy%u%s_&k&L?' '''' 'G>L(+3uTk$^&  9b!8j _#`%v6ip4Q*+0!;KgW@DI  )&r:$8H"=' {c*A2oZM~.5haC,1 E2U6[yS(lq4YP s9]0/'VBFN /X ,3t 5-w1}|xe\?O"#%Jmd)<zR7.7-n f Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.) (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) (support for multiple domains on multisite websites) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.No Adverts for Friends plugin is %s.Domain Mapping support plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting Moderation plugin is %sBad Behaviour not found. Please check your install.Bad Behaviour support is %s.Cache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Don’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLegacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching.Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.One or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Update Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: WP Super Cache Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-09-27 13:58+0000 PO-Revision-Date: 2011-08-10 18:25+0200 Last-Translator: Language-Team: Alexandr Alexandrov MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Belarusian X-Poedit-Country: BELARUS Праверце што яны ідуць перад усімі ўжо існуючымі ў дакуменце правіламі WordPress.%1$s ўдзячны плагіна %2$s за проделаннную працуДадатковы модуль %1$s створаны і абнаўляецца аўтарам %2$s пры падтрымцы многіх іншых.%s старонак у кэшы%s старонак пратэрмінаваныДиректрия% s даступная для запісу. Вам варта змяніць яе права на " Толькі чытанне ".%s выдалены!Файл% s.htaccess быў паспяхова абноўлены, неабходныя правілы mod_rewrite былі дададзеныя. Калі ласка, праверце іх. Яны павінны выглядаць так:%s/advanced-cache.php не існуе або не можа быць абноўлены ў аўтаматычным рэжыме.(1 = найменшы, 5 = найбольшы, можа выклікаць болшую нагрузку на сервер)(Эксперыментальныя налады)(Гэты дадатковы модуль будзе функцыянаваць толькі ў рэжыме сярэдняга кэшавання, адключыце сціск і ўсталюйце ўбудова "Bad Behavior" у "%s/plugins/bad-behavior/")(Прыбірае тэкст " Ваш каментар чакае праверкі" калі хто-то размяшчае каментар да запісу)(Спіс не рэкамендаваны для вялікіх сайтаў)(Запісвае звароту толькі з гэтага IP. Ваш IP -% s)(Патрабуе ўсталёўкі friendsadverts.php ) (Падтрымка для MU - сэрвісу блогаў)1. Калі ён ужо існуе ў тэчках Вашага блога, выдаліце ​​яго.2. Зменіце правы доступу да %1$s, каб можна было запісаць дадзеныя ў аўтаматычным рэжыме (правы павінны быць: chmod 777 %1$s), праверце правільнасць зададзеных правоў і абновіце старонку. Гэта часовае ўмова, пасля абнаўлення старонкі правы доступу трэба вярнуць на ранейшыя (з 777 на 755). 3. Абнавіце старонку, файл% s / advanced-cache.php абновіцца самПамылка 304. Дадзеная памылка ўзнікае тады, калі старонка не была зменена з часу мінулага запыту.Падтрымка памылкі 304 адключаная па змаўчанні (з-за праблем некаторых сэрвісаў).Статут ўбудовы " No Adverts for Friends":% s.Статут ўбудовы " Domain Mapping": %s

    Пераменная WP_CACHE дададзеная ў файл канфігурацый wp-config.php

    Калі Вы да гэтага часу бачыце дадзенае паведамленне, то паспрабуйцце звярнуцца з пунктам 5 чаво (на англ.). Радок з WP_CACHE павінна быць размешчаная вышэй.

    Параметр WP_CACHE не актываваны

    Дадзены параметр павінен быць актываваны для таго, каб WordPress мог карэктна працаваць з файламі кэша. У дадзены момант ён адключаны. Каб уключыць яго, адкрыйце файл wp-config.php і дадайце ў яго наступны радок:

    define('WP_CACHE', true);

  • 1. Адкрыйце файл %1$s$wp_cache_file ў тэкставым рэдактары.
  • 2. Зменіце радок CACHEHOME на %2$s
  • 3. Захавайце файл і скапіруйце ў %3$s, затым абновіце старонку.
    • "Памылка: Зменная WP_CACHE ня актываваная ў файле агульных канфігурацый wp-config.php . "Ачыстка смецця
    Папярэдняя ачыстка была% s хвілін назад
    "Увага! Вы спрабуеце ўключыць сціск, але модуль zlib.output_compression адключаны. Глядзіце пункт нумар 21 падзелу "Апісанне праблем " у файле readme.txt (на англ.) Для карэктнай працы ўбудовы неабходная карэктная налада структуры спасылак. Каб наладзіць іх, наведайце старонку Сталыя спасылкі . Паміж правіламі ў Вашым файле. Htaccess і правіламі самога плагіна выяўленыя неадпаведнасці. Гэта можа быць проста лішні сімвал ў радку, але Вы павінны асабіста параўнаць арыгінальныя правілы са сваімі як мага хутчэй. Націсніце на кнопку 'Абнавіць правілы Mod_Rewrite', каб зрабіць гэта ў аўтаматычным рэжыме. Самы просты спосаб выправіць гэта - змяніць правы доступу, выкарыстоўваючы CHMOD, праз FTP-кліент. Дастаткова ўсталяваць глабальныя правы на запіс.Дапушчальныя імёны & Забароненыя адрасыДадаць старонку ў кэш:Поле ніжэй Вы таксама можаце запоўніць фрагментамі адрасоў старонак (або груп старонак, напрыклад, архіў за год / месяц і г.д.), якія не будуць кэшавацца. Плагін будзе сканаваць адрасы старонак на прадмет наяўнасці ў іх фрагментаў, указаных ніжэй, перад кэшаваннем. Поле ніжэй Вы можаце запоўніць назвамі файлаў якія будуць кэшаваць, нават калі ў іх назве ёсць забароненых да кэшавання фрагменты.Дадайце правілы самастойна. Для гэтага адкрыйце у рэдактары файл% s.htaccess і знайдзіце код паміж # BEGIN WPSuperCache і # END WPSuperCache . Вы ўбачыце два падобных блока кода. Адразу пасля радка %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ дадайце наступнае (такіх радкоў дзве, дадайце код і пасля другой): НаладыУзростВы таксама можаце рэдагаваць файл %s.htaccess ўручную і асабіста дадаць неабходныя правілы (да наяўных там правілаў WordPress): АрхівыДаступныя ўбудовыСтатут ўбудовы " Awaiting Moderation": %sПлагін " Bad Behaviour" не быў знойдзены. Праверце, завяршылі Ці Вы яго ўстаноўку.Статут ўбудовы " Bad Behaviour": %s.Стан кэшаПраверка кэшаванняКэшаваць хіты сайта для паскарэння доступу.Кэшаванне адбываецца за кошт PHP файлаў, якія захоўваюцца ў тэчцы ўбудовы. Яны загружаюцца пры ўключэнні рэжыму Supercache. Загрузка адбываецца нашмат часцей, чым для астатніх убудоў WordPress.Аўта перабудова кэшу. Госці блога ўбачаць састарэлыя версіі старонак кэша пакуль новыя будуць генеравацца.Статыстыка аб'ектыў ў кэшы НЕ ствараецца аўтаматычна. Каб абнавіць яе ўручную націсніце на спасылку ніжэй.Статыстыка аб'ектаў у кэшы апошні раз створана:% s мін таму.Паведамленні ў кэш% s секунд назадСтаронак ў кэшы з %1$s: %2$sСтатут кэшаванняКэшаванне выключанаКэшаванне ўключанаКэшаванне павінна быць уключана, калі Вы хочаце выкарыстоўваць дадзеную опцыюАдмяніць агульнае кэшаваннеНемагчыма працягнуць ... перш чым паўтарыць спробу, выпраўце папярэднія памылкі.Не магу абнавіць файл. HtaccessРубрыкіЗмяніць час жыцця копііПравяраць галоўную старонку кожныя 5 хвілін.Паверка і выдаленне пратэрмінаваных старонак кэша займае час, але і пакідаць такія файлы ў сістэме не варта. На вялікіх блогах трэба выстаўляць " час жыцця " кожнай копіі 300 секунд. Вы можаце паэксперыментаваць з наладай і паглядзець, колькі пратэрмінаваных копій старонак застаецца ў кэшы на працягу дня. Аптымальнае лік такіх старонак не больш за 500. Выкарыстоўваючы кэшаванне з mod_rewrite або PHP, Вы зможаце павялічыць колькасць кэшируемых старонак. Выдаляць старыя файлы з кэша Super Cache.Ачышчаць кэш калі новая запіс або старонка апублікаваная.Ачышчаць кэш пры памылцы.Блакаванне файлаў. Вам хутчэй за ўсё не спатрэбіцца дадзеная опцыя, але яна можа вырашыць праблему маламагутных хостынгаў. Увага! Уключэнне опцыі, у рэдкіх выпадках, можа выклікаць праблемы ў працы блога!"Праверка каментарыяў ўключана. Перш чым Вашы каментары будуць апублікаваныя пройдзе нейкі час.Сціскаць файлы кэша каб паскорыць працу.Сціск кэша адключана па змаўчанні, так як можа некарэктна працаваць на некаторых хостынгах. Уключэнне або Адключэнне дадзенай опцыі аўтаматычна чысціць часовы кэш.Файл канфігурацый быў зменены, некаторыя налады не адпавядаюць патрабаванням ўбудовы. Наведайце старонку " Налады "каб выправіць гэта.Канфігурацыйны файл адсутнічае, а тэчка %1$s (%2$s) недаступная для запісу. Праверце правы доступу.У дадзены моманты кэшуюцца запісы з% d па% d.Рэжым запісаны на:АбслугоўваннеРэжым адладкіВыдаліцьВыдаліць увесь кэшВыдаліць пратэрмінаваны кэшВыдаліць файлы Super Cache (у новым акне)Выдаліць файлы з кэшаВыдаліце ​​ўсе правілы mod_rewrite з файла% s.htaccess, паміж # BEGIN WPSuperCache і # END WPSuperCache і абновіце старонку (аднаўленне правілаў запусціцца аўтаматычна). Выдаленне файлаў Super Cache:% s
    Выдаленне файлаў WP-Cache:% s
    Распрацоўнікам: Зрабіце свой уласны убудова закрытага рэжыму сумяшчальным з нашым, дадаўшы зменную " WPLOCKDOWN". Прыведзены ніжэй код дапаможа Вам адаптаваць свой ўбудова да налад нашага Рэжыму.Прамое кэшаванне старонакДадзены кэш ствараецца прама з папкі, дзе знаходзіцца Ваш блог (тэчка% s). Гэтая опцыя карысная толькі тады, калі чакаецца вялікі прыток наведвальнікаў з больш папулярнага сайта на пэўную старонку або запіс Вашага.АдключыцьАдключаныНе кэшаваць старонкі наступных тыпаў. Паспрабуйцце звярнуцца да Артыкулам Кодэкса WP (па-ангельску), каб даведацца больш падрабязна пра тыпы старонак. Выяўленая падтрымка сэрвісу мультиблогов! Каб палегчыць і паскорыць працу плагіна, Вам трэба ўключыць падтрымку мультиблогов ў наладах.Не кэшаваць старонкі для вядомых карыстальнікаў."КэшВыпраўце файл наладак код %s і дадайце наступную пункту:
    define('WP_CACHE', true);
    Інакш, WP-Cache не зможа запусціцца. EmailПаведаміць адміністратару блога па завяршэння праверкі (карысна пры тэставанні на памылкі).ДазволіцьУключаныПамылкаПамылка: сціск GZIP ўключана, адключыце яго калі хочаце запусціць wp-cache.Старонка існуеАктуальнасць кэшу:Пратэрмінаваны кэш - гэта старонкі, створаныя больш чым% s секунд таму. Не гледзячы на ​​свой статус, яны выкарыстоўваюцца ў агульным кэшы і перыядычна выдаляюцца.Пратэрмінаваныя старонкі & Ачыстка смеццяФидыПраверка старонкі% s у кэшы:Праверка першай копіі% s:Праверка второй копіі% s:Аднавіць стандартныя наладыТут Вы можаце вырашыць некаторыя праблемы, якія ўзнікаюць пры працы з убудовай, з дапамогай адладкі. Вы можаце запісваць службовую інфармацыю (логі) у файлы дырэкторыі кэша.Для больш прадуктыўнай працы сайта, Вам варта ўключыць опцыю " Падтрымка мабільных прылад "або выдаліць гэтую запіс з правілаў ст. Htaccess. Знайдзіце наступны тэкст (два радкі) "2.0\ MMP|240x320" і выдаліце яго.Напрыклад: каб дадаць у кэш старонцы на %1$s about /, трэба прапісаць %1$s about / ці / about /. Кэш для старонкі будзе створаны адразу ж пасля першага да яе звароту госцем.Новыя файлы Super CacheНовыя файлы WP-CacheАсноўная старонкаКлючавой тэкстПоўнае кэшаванне проихойдет праз% d г% d мін і% d сек.Сціск GZIP ўключана ў наладах WordPress, убудова не будзе працаваць да таго часу, пакуль Вы не адключыце gzip.Ачыстка смеццяПравілы для Gzip-сціску дададзеныя ў файл% s.htaccess.Наведайце блог аўтара плагіна %1$s і яго фотаблог на %2$s.Прыбраць спісХатняя старонкаI'm 99% certain! Памылкі, якія могуць паўстаць пры працы з WP Super Cache, не звязаныя з самім убудовай. Яны ўзнікаюць у рэдкіх выпадках, але Вы можаце падстрахавацца, запусціўшы аўтаматычную праверку блога кожныя 5 хвілін. У выпадку памылкі, Вам будзе адпраўлена паведамленне. Адрас IPКалі гэта не спрацавала, пераканайцеся што% s / advanced-cache.php сапраўды не існуе:Калі час актуальнасці кэша больш за 1800 секунд (паўгадзіны), то ачыстка смецця будзе запускацца кожныя 10 хвілін.Деактивируя убудова, пераканайцеся што тэчка% s даступная для запісу ў наладах Вашага сервера, каб файлы плагіна advanced-cache.php і cache-config.php былі выдаленыя ў аўтаматычным рэжыме (таксама праверце наяўнасць правоў на запіс для гэтых двух файлаў).У рэжыме 'Агульнага кэшавання' запланаваная ачыстка смецця будзе выдаляць толькі кэш запісаў простага тыпу (кэш з Super Cache не будзе выдалены). Дадзеная налада рэкамендавана для выкарыстання.У асабліва рэдкіх выпадках на блогу могуць здарыцца дзве праблемы:
    1. Замест галоўнай старонкі карыстальнікі будуць бачыць прапанову загрузіць. Zip архіў з ёй
    2. Замест галоўнай старонкі можа быць дададзеная ў кэш зусім іншая (толькі ў выпадку, калі Ваш бог выкарыстоўвае наступную структуру спасылак /% category% /% postname% /).
    Узнікла памылка, звязаная з тым, што модуль mod_rewrite адсутнічае ці не ўсталяваны. Калі ласка, праверце наяўнасць модуля mod_rewrite ў канфігурацыях сервера. Модуль неабходны для карэктнай працы ўбудовы з статычнымі файламі. Без падлучанага mod_rewrite Вы можаце выкарыстоўваць толькі рэжымы з падтрымкай PHP або сярэднюю кэшаванне . Здаецца, усе спасылкі Вашага блога заканчваюцца сімвалам "/". На жаль, як толькі Вы ўсталявалі гэты дадатковы модуль, спрацавала опцыя, выявілая копіі спасылак без знака "/" на канцы, і цяпер яна не можа ажыццявіць перанакіраванне на верны адрас. Каб гэта выправіць гэта, Вы павінны адрэдагаваць файл. htaccess і дадаць два новыя правілы да групы асноўных правілаў плагіна Supercache: КлючСпрошчанае кэшаванне.Нізкі ўзровень: 1 e-mail ў пачатку і 1 у канцы кэшавання.Спіс кэшаваных файлаўСтварыць спіс старонак у кэшы (выводзіцца на гэтай старонцы)Закрыты рэжымЗакрыты рэжым:Узровень логуТып ўваходуАтрымаць доступ да файла лога проста, але пры ачыстцы кэша лог таксама будзе выдалены.Зрабі свой блог хутчэй!Каб выдаліць старонку з такога кэша, ачысціце тэкставае поле і выдаліце ​​файлы кэша.Высокі ўзровень: 2 паведамленні на 100 запісаў.Сярэдні ўзровень: 1 паведамленне на 100 запісаў.РознаеАдсутныя модулі ApacheПадтрымка мабільных прыладВыяўленая падтрымка мабільных прыладПадтрымка блогам мабільных прылад патрабуе прысутнасці асаблівых правілаў у файле. Htaccess, інакш Вы не зможаце выкарыстоўваць гэтую опцыю. Ніжэй прадстаўлены магчымы спосабы (у парадку складанасці):Модуль Mod RewriteMod Rewrite не можа быць абноўлены!Правілы mod_rewrite павінны быць абноўлены!Правілы mod_rewrite абноўлены!Здаецца, модуль mod_rewrite не ўстаноўлены!Выкарыстанне mod_rewrite дапаможа зрабіць працу блога хутчэй, чым PHP (хоць і гэты варыянт таксама не такі павольны). Гэты рэжым прасцей і зручней, але пачаткоўцу карыстачу лепш выкарыстоўваць кэшаванне PHP.Усё яшчэ патрэбна дапамога? Глядзіце афіцыйны чаво па плагіна Super Cache (па-ангельску). Таксама, Вы можаце задаць сваё пытанне на форумах тых. падтрымкі (па-ангельску), або азнаёміцца ​​з праблемамі іншых карыстальнікаў і прапанаванымі ім рашэннямі. Новае ў кэшы:Наступная ачыстка будзе праз% s хвілінВажна:Важна: рэкамендуецца ўключыць PHP кэшаванне, аўто перабудову кэша і падтрымку для мабільных прыладВажна: Mod_rewrite або Legacy caching адключаныя. Па змаўчанні будзе загружацца старонка " Налады ".Увага: Сярод правілаў mod_rewrite выяўленыя правілы ад Supercache. Для працы з кэшам будуць выкарыстаны менавіта гэтыя правілы. Каб выдаліць іх, Вам трэба ўручную адрэдагаваць файл. Htaccess.Увага: Праверка правілаў WP Super Cache mod_rewrite адключаная для блогаў сеткі пакуль не будзе запушчана на галоўным блогу . Увага: Праверка правілаў WP Super Cache mod_rewrite адключаная для блогаў сеткі пакуль не будзе запушчана на галоўным блогу . ЁСЦЬСпіс кэшавання недаступны.Пры працы з кэшам адбыліся памылкі:Перагружаць старонку пры даданні новага каментара да яеPHP выкарыстоўвае сціск для сціснутых старонкі Вашага сайта. Адключэнне дадзенай опцыі рэкамендуецца, каб пазбегнуць шматразовага сціску старонак убудовай. Даведацца больш, наведаўшы профіль 16 ст " Апісанне праблем "у файле readme.txt (на англ.). Таксама азнаёмцеся з гэтай старонкай (на англ.) па php.ini. Старонка% d:% d (% s)Старонка 1:% sСтаронка 2:% sСтаронкіПамылка структуры спасылакКалі ласка, стварыце файл% s / wp-cache-config.php з wp-super-cache/wp-cache-config-sample.phpКалі ласка, наведайце% s аўтара!Каб даведацца больш, наведайце раздзел 16 ст Апісанні праблем у файле readme.txt (на англ.) Для даведкі глядзіце readme.txt (дакумент на англ.). Там Вы знойдзеце карысную інфармацыю па выкарыстанню і выдаленню плагіна WP Super Cache. Адбылася памылка, на галоўнай старонцы Вашага блога не быў выяўлены ключавой тэкст "%2$s"! Каб выправіць памылку, наведайце гэтую старонку %1$s і ўручную ачысьціць кэш.Адбылася памылка! Наведайце% s каб выдаліць кэш!Даданыя модуліАгульны кэшКэшаваць% s запісу.Стварыць агульны кэш цяперАгульнае кэшаванне было перазапушчаныя. %sПапярэдні рэжым (ачыстка смецця працуе не цалкам, опцыя рэкамендавана да ўключэння.)Аднак, пры выкарыстанні дадзенага віду кэша ствараецца нашмат больш файлаў. Рэкамендуецца выкарыстоўваць такі тып, калі ў Вас вельмі шмат запісаў (10 тысяч і больш) на блогу. Асабліва гэта важна, калі Вы карыстаецеся паслугамі віртуальнага хостынгу.Агульнае кэшаванне адключана. Калі ласка, уключыце поўны рэжым працы ўбудовы або звернецеся да адміністратара сервера.Падрыхтуйце свой блог да запланаваных усплёскаў наведвальнасці, актываваўшы дадзены рэжым. У актыўным стане размяшчэнне новых каментароў і запісаў НЕ будзе абнаўляць статычныя файлы ў кэшы.Расказаць ўсім, што Вы карыстаецеся убудовай WP Super Cache (паведамленне будзе размешчана ў " склепе "сайта)!Рэжым " только_чтение ". Налады не могуць быць зменены.Толькі чытанне:РэкамендаванаАбнаўленне кэша праз% d г% d мін і% d сек.Перагружаць агульны кэш кожныя% s хвілін (ўвядзіце 0, каб адключыць, мінімальнае дапушчальнае кол-у хвілін% d).Абнавіце старонку калі неабходныя правы доступу будуць зададзены.Абнавіце старонку калі скончыце рэдагаванне файла. Htaccess.Наступныя запісы абноўлены:Абнавіць статыстыку кэшаПошукавыя і іншыя ботыНеабходна для правільнага сціску файлаў.Неабходна наладзіць кэшаванне на старонцы ўбудовы. Карыстальнікі браўзэра IE7 будуць бачыць необновленные старонкі з кэша без падтрымкі дадзенага модуля.Аднавіць налады па змаўчанніПравы на запіс павінны быць абноўленыяПравілы павінны быць таксама дададзены да% s:Файл WP-Cache (% s) не быў знойдзены. Праверце, завяршылі Вы ўстаноўку ўбудовы.ЗахавацьЗахаваць спіс файлаўЗахаваць спіс забароненых фрагментаўЗахаваць наладкіАгульнае кэшаванне па раскладзе адключана.Агульнае кэшаванне па раскладзе адключана. Калі служба цяпер запушчана, яна не будзе завершана пакуль бягучыя 100 старонак не кэшаваць.Агульнае кэшаванне адбудзецца праз% d хвілінАгульная кэшаванне адбудзецца праз 10 секунд.Наступнае запланаванае абнаўленне агульнага кэша праз% d хвілін.Пракруціць старонку ўніз і націсніце кнопку Абнавіць правілы Mod_Rewrite."Старонкі пошукуАдпраўляць мне паведамленні з апавяшчэннямі аб абнаўленні кэша.Даслаць неабаронены (не па https) запыт для галоўнай старонкіУсталюйце дату заканчэння актуальнасці старонак. Карыстальнікі могуць не ўбачыць новую версію кэшаваныя старонкі без дадзенага модуля.Усталюйце значэнне на 0, каб адключыць Ачыстку смецця.Перакладзіце убудова ў рэжым сярэдняга кэшавання і ўключыце падтрымку мобмльных прылад.НаладыЗапісыВыбачайце, мой блог часова недаступны. Зайдзіце пазнейСтарыя файлы Super CacheСтарыя файлы WP-CacheКаб забараніць плагіна кэшаваць запыты ад пошукавых ботаў і іншых сеткавых робатаў, увядзіце іх назвы ў полі ніжэй (па адным у радку). Калі копія старонкі ўжо існуе ў кэшы Super Cache, то яна ўсё роўна будзе адпраўлена боту.ПазнакіПраверыцьПраверце наладкі кэшавання свайго блога націскам адной кнопкі.ПраверкаКалі ласка, увядзіце тэкст які ўбудова будзе шукаць на галоўнай старонцы. Калі тэкст не будзе знойдзены, то кэш аўтаматычна ачысціцца. Пакіньце поле пустым каб адключыць опцыю.Дзякуй за абнаўленне.Канфігурацыйны файл плагіна WP Super Cache %s/wp-cache-config.php не можа быць зменены. Каб працягнуць, Вы павінны ўсталяваць правы на запіс для файла. Адбылася памылка, на галоўнай старонцы Вашага блога не быў выяўлены ключавой тэкст "%2$s"! Наведайце гэтую старонку %1$s каб праверыць кэш.Увесь кэш для Вашага блога быў ачышчаны, так як убудова заўважыў памылку на галоўнай старонцы (яна запампоўваліся архівам). Каб праверыць кэш, наведайце гэтую стрницу% s.Файл %s.htaccess не можа быць абноўлены ў аўтаматычным рэжыме. Каб выправіць гэта задайце неабходныя для запісу правы доступу да яго. Наступныя модулі Apache адсутнічаюць на Вашым серверы. Без іх убудова зможа працаваць толькі ў рэжыме сярэдняга кэшавання. У рэжыме з падтрымкай Super Cache Вашы карыстальнікі могуць бачыць пашкоджаныя старонкі або пратэрмінаваныя іх копіі.З моманту апошняй усталяванай версіі плагіна правілы mod_rewrite былі змененыя. На жаль, Вам давядзецца ўручную выдаліць старыя правілы перш чым новыя запрацуюць. Абнавіце гэтую старонку калі скончыце рэдагаваць файл. Htaccess. Калі Вы жадаеце цалкам абнавіць усе самі, то заменіце наступны радок:%1$s на гэтую:%2$s. Адзінае адрозненне - гэта замена "HTTP_COOKIE " на "HTTP: Cookie " і "wordpressuser " на "wordpress ". Гэтыя перамены звязаны з новай версіяй WordPress 02/05 . Вядома Вы можаце працягваць працаваць са старымі версіямі, калі хопіць адвагі;) Старонкі не супадаюць! Часавы штамп адрозніваецца ці не быў знойдзены!Неабходныя для працы ўбудовы правы былі змененыя або отсуствіі.Часовыя штампы абодвух варыянтаў старонкі супадаюць!Для выкарыстання дадзенай опцыі трэба ведаць не толькі PHP, але і WordPress (не на пачатковым узроўні).Пры актывацыі агульнага кэшавання, будзе створана копія для кожнай запісу і старонкі Вашага блога. У гэтым рэжыме ствараюцца статычныя старонкі, якія затым будуць бачыць " неапазнаныя "наведвальнікі (напрыклад, пошукавыя боты і іншыя). Гэта можа дапамагчы ў паляпшэнні ўзроўню PR Google, так як у аснове іх алгарытму ляжыць і хуткасць водгуку вэб-сайта. На Вашых звычайных наведвальніках гэта ніяк не адаб'ецца, а вось якія выкарыстоўваюць мабільныя прылады для вэб-серфінгу не будуць атрымліваць кэшаваныя старонкі (калі опцыя адключаная).Каб убудова мог правільна працаваць з статычнымі html файламі, Вы павінны дадаць у файл %s.htaccess правілы модуля mod_rewrite Занадта шмат аб'ектаў у кэшы, стварэнне спісу немагчыма.Патрабуецца праверка trailing slash.АДРАСНа жаль, файл wp-cron.php не быў знойдзены. Гэты скрыпт неабходны для карэктнай працы опциии " Ачыстка смецця "і самога WordPress.На жаль, mod_rewrite немагчыма абнавіць у аўтаматычным рэжыме ў WordPress MU. Вам прыйдзецца ўручную зрабіць гэта: адкрыйце файл. Htaccess (размешчаны ў каранёвай дырэкторыі блога) і дадайце наступныя правілы ў яго.Абнавіць стрницыАбнавіць правілы mod_rewriteАбнавіць наладыАбнавіцьВыкарыстоўваць PHP для абслугоўвання кэша.Выкарыстоўваць mod_rewrite для абслугоўвання кэша.Выкарыстоўваць аб'екты кэша для захоўвання кэшаваных файлаў.Паглядзець правілы mod_rewriteНалады WP Super CacheПлагін WP Super Cache толькі што праверыў галоўную старонку Вашага блога на прадмет памылак. Каб адключыць апавяшчэння і праверку наведаеце гэтую старонку% s.Плагін WP Super Cache не актываваны. Каб актываваць яго, перайдзіце на старонку кіравання убудовай. Правілы mod_rewrite для плагіна WP Super Cache былі выяўленыя ў файле% s.htaccess.
    Націсніце на адпаведную кнопку, каб паглядзець радкі. Калі Вы толькі што абнавілі убудова, праверце ўсе правілы. Плагін WP Super Cache павінен быць наладжаны! Каб актываваць яго і наладзіць, перайдзіце на старонку кіравання убудовай. Стан WP-CacheСтан WP-Super-CacheУвагаУвага!Увага! Тэчка% s даступная для запісу!Увага! Уключаны рэжым PHP Safe Mode!Увага! Ваша hostname "% s"пераўтворана ў% sЗнойдзены WordPress MU!Ваш блог выкарыстоўвае Закрыты рэжым. Новыя каментары не абнаўляюць ўсе статычныя элементы кэша.Ваш блог не выкарыстоўвае Закрыты рэжым. Апошнія каментарыі абнаўляюць ўсе статычныя элементы кэша.Даступна для запісу:Вы можаце ўручную адрэдагаваць файл і дадаць неабходныя правілы.Каб паглядзець поўны спіс якія працуюць правілаў, націсніце кнопку ніжэй " Паглядзець правілы mod_rewrite ".Пры працы з убудовай могуць узнікнуць праблемы, так як PHP Safe Mode уключаны на Вашым серверы.Для карэктнай працы, у Вашым файле% s.htaccess павінны быць прапісаны маркеры BEGIN, і END. Паміж імі знаходзяцца асноўныя правілы WordPress mod_rewrite, прыклад:Вы павінны дазволіць запіс для% s. Але так як гэта патэнцыйная ўразлівасць, пасля абнаўлення старонкі вярніце правы на чытанне.Вы або Адміністратар можаце выправіць памылкі, змяніўшы групу ўладальніка скрыптоў плагіна праз налады вэб-сервера. Таксама трэба змяніць уладальніка для тэчкі% s / cache /. Для больш падрабязнай інфармацыі глядзіце старонку дапамогі па рэжыму safe mode (на англ.). Вы або Адміністратар павінны адключыць гэта. Для больш падрабязнай інфармацыі глядзіце старонку дапамогі па рэжыму safe mode (на англ.). Дадзеныя налады НЕ могуць быць адключаныя праз файл. htaccess, для вырашэння праблемы трэба рэдагаваць php.ini ў наладах вэб-сервера. Вы павінны змяніць правы на тэчку% s. Каб зрабіць гэта - скарыстайцеся FTP-кліента або наступнай камандай:Ваш файл% s.htaccess недаступны для запісу (у наладах сервера) і не можа быць абноўлены ў аўтаматычным рэжыме. Вы павінны ўручную дадаць новыя правілы да асноўных правілах WordPress так, як паказана ніжэй:Канфігурацыйны файл WP-Cache (% s) можа быць ня дзейнічае і недаступны для запісу. Калі ласка, выдаліце яго ўручную і абновіце старонку.Тэчка ($ cache_path) не існуе і не можа быць створана ў аўтаматычным рэжыме. Праверце правы доступу да% s.Тэчка (%1$s) або %2$s павінна быць даступная для запісу. Перепроверьте правы доступу.Ваш каментар чакае пацверджання.Ваш сервер настроены так, што правярае ўладальніка для ўсіх PHP скрыптоў перад тым як дазволіць ім чытанне або запіс у файл.Ваш вэб-сервер вырашыў, што hostname зменена на% s. Некаторыя опцыі ўбудовы (напрыклад, " Ачыстка смецця ") і сам WordPress могуць працаваць некарэктна.Сціск Zlib Output ўключана![%1$s] %2$d кэш запісаў абноўлены[%1$s] Агульная кэшаванне пачалося[%1$s] Абнаўленне кэша запісаў з %2$d па %3$d[%s] Агульная кэшаванне завершана[%s] Галоўная старонка праверана![%s] Галоўная старонка сціснута з дапамогай gzipped! Кэш выдалены![%s] Галоўная старонка сціснута з дапамогай gzipped! Выдаліце ​​кэш![%s] Галоўная старонка адлюстроўваецца з памылкай! Кэш выдалены![%s] Кэш галоўнай старонкі змяшчае памылку! Выдаліце ​​кэш![%s] Агульная кэшаванне магло быць спынена.ЎвесьАдключаныУключаныФайлСекундlanguages/wp-super-cache-ru_RU.mo000066600000255327152133035240012744 0ustar00` <,MQa`r ~?^3* 7 Z 5@! v!="b"j%#-#$# #$$%u&\@''?()*!++wy,Z,%L-r- ... 0&00:0n92p24+444844444 55325f5j56 (6,56b6^7pr7+78n%8/88 8 8`8+D9p939999!9:!;7<=<S<I=@L==s>>?%?5?JN?@ @@ @@@5@A)A3A1BOBB CCDDD@EuOE EjEQFVF?GGGNGaG}iGGNGmmmpnoo.ppzs<|sGs#tR%tuxu uTv~Nw+wwxxxyVz]zqzz zz%z'z{+{jC{b{|l|H}Q}`}h}q}B}}}*~~b[i F7rOM€Ɂ/L|q9$Aeḟ>o ϊ)%Ol*/.ދ3 A`dmu} X&؏m~h7~#OړW*slcqc՗'CG< șԚWq`E/)F]}'ۨ 0BIE,&Hȳ$3 !"28k1>U8'T^|K۷'q7V:0#k)'2Gz1F1UMտAj*nuL8TWO8=Vet-.>'/WDwAp2oT,#2o' ~!5bW%"K`2-(-VB3h"d!!ahS8`!") LZihN%!QGKT,I`v2j u.LL *.78fMXF6_D.C qNV A9Bm2;',8ev<7#V ! 0 %B -h G   N g+He[vyF Rv r3.*+YMCE3IyT,g,K% O3ORv&)pGq*b"+ >Ki#} 7f    7Y!)" "# $%&(8,}-{-b.Lk.0i[1?35k5ES6 66v7 8 ::+>:#j::F:N:o5;/;!;;=Z=??!?@-@E?@a@:@u"AIB BCC%eDD&EEVF"FHIJMPMOOPHQQRyS*9W2dW9W?WEX9WX8X_Xa*YeYaYLTZZZZ ZO z/Z8 Y-#ML ;=(Dq7If@^K[X&Cxr}FJ+,0) !Y[Pm=;"| VA_7s3VuTHNQ!B_k$21E%?^IODAU3g X<#cn`K&P@>ldUN.L:4*69+\R'6i$E%ZbSw4C/]M")0({FW H.,<py]1o8~eRT ? S*G'`-t 9\QWa25Jh :>Bvj 5G Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumUse Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together.Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.This page explains how to change file permissions.No Adverts for Friends plugin is %s.

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages are stored on your server as html and PHP files. If you need to delete them use the button below.Cached pages since %1$s : %2$sCachingCaching OffCaching OnCaching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.ContentsCurrently caching from post %d to %d.Currently logging to: %sDear User, WP Super Cache was removed from your blog but the mod_rewrite rules in your .htaccess were not. Please edit the following file and remove the code between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first! %s Regards, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggingDeleteDelete CacheDelete Cached PagesDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. Email the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExcludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default).Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionExtra homepage checks. (Very occasionally stops homepage caching)FeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesIt appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelMake WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Provides support for Domain Mapping plugin to map multiple domains to a blog.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSkip https URLs to avoid "mixed content" errorsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Supercache Uninstall ProblemsTagsTest CacheTest your cached website by clicking the test button below.Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$sThis is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledsecondsProject-Id-Version: WP Super Cache Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2011-02-28 22:08:12+00:00 PO-Revision-Date: 2011-03-15 23:04+0300 Last-Translator: Elvis Language-Team: Elvis MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Russian X-Poedit-Country: RUSSIAN FEDERATION Убедитесь что они идут перед всеми уже существующими в документе правилами WordPress. %1$s благодарен плагину %2$s за проделаннную работуПлагин %1$s создан и обновляется автором %2$s при поддержке многих других.%s страниц в кэше%s страниц просроченоДиректрия %s доступна для записи. Вам следует изменить ее права на "Только чтение".%s удален!Файл %s.htaccess был успешно обновлен, необходимые правила mod_rewrite были добавлены. Пожалуйста, проверьте их. Они должны выглядеть так:%s/advanced-cache.php не существует или не может быть обновлен в автоматическом режиме.(1 = наименьший, 5 = наибольший, может вызвать большую нагрузку на сервер)(экспериментальные настройки) (данный плагин может работать только в режиме среднего кэширования, отключите сжатие и установите плагин "Bad Behavior" в "%s/plugins/bad-behavior/") (список не рекомендован для больших сайтов)(записывает обращения только с этого IP. Ваш IP - %s)(требуется установка friendsadverts.php) 1. Если он уже существует в папках Вашего блога, удалите его.2. Измените права доступа к %1$s, чтобы можно было записать данные в автоматическом режиме (права должны быть: chmod 777 %1$s), проверьте правильность заданных прав и обновите страницу. Это временное условие, после обновления страницы права доступа нужно вернуть на прежние (с 777 на 755).3. Перезагрузите страницу, файл %s/advanced-cache.php обновится самОшибка 304. Данная ошибка возникает тогда, когда страница не была изменена со времени прошлого запроса.Поддержка ошибки 304 отключена по умолчанию (из-за проблем некоторых сервисов).ЧАВО (англ.)Помощь по установке (англ.)Форум поддержки (англ.)Библиотека JS от Google позволит использовать оптимизированные файлы Javascript с сервера Google (некоторые плагины уже используют эти библиотеки).Плагин WP Minify уменьшает нагрузку на сервер за счет объединения CSS и JS файлов. Также можно использовать и WPSCMin для уменьшени объема кэшированных страниц. Однако он не может объединять JS и CSS файлы.Дополнение Yahoo! Yslow прекрасно подойдет для владельцев браузера Firefox. Yslow успешно анализирует страницы Вашего блога и предлагает оптимальные решения для оптимизации и ускорения. Также стоит попробовать онлайн-утилиту GTMetrix.Здесь (англ. статья) подробно описано как изменить права доступа к файлам на сервере.Статус плагина "No Adverts for Friends": %s.

    Переменная WP_CACHE добавлена в файл конфигураций wp-config.php

    Если Вы до сих пор видите данное сообщение, то сверьтесь с пунктом 5 ЧАВО (на англ.). Строка с WP_CACHE должна быть размещена выше.

    Параметр WP_CACHE не активирован

    Данный параметр должен быть активирован для того, чтобы WordPress мог корректно работать с файлами кэша. В данный момент он отключен. Чтобы включить его, откройте файл wp-config.php и добавьте в него следующую строчку:

    define('WP_CACHE', true);

  • 1. Откройте файл %1$s$wp_cache_file в текстовом редакторе.
  • 2. Измените строчку CACHEHOME на %2$s
  • 3. Сохраните файл и скопируйте в %3$s, затем перезагрузите страницу.
    • ВНИМАНИЕ: Прежде всего, протестируйте адреса CDN, например: %s - чтобы убедиться в корректной работе серверов.Только для понимающих пользователей: Ускорьте свой блог, используя дополнительные возможности контроля кэша за счет правил .htaccess.Только для понимающих пользователей: Установите дополнительное кэшировани объектов, используя Memcached, XCache или eAcccelerator.Ошибка: Переменная WP_CACHE не была найдена в файле общих конфигураций wp-config.php.Очистка мусора
    Предыдущая очистка была %s минут назад
    Последний раз страница была кэширована: %sВнимание! Вы пытаетесь включить сжатие, но модуль zlib.output_compression отключен. Смотрите пункт номер 21 раздела "Описание проблем" в файле readme.txt (на англ.)Для работы плагина необходима корректная настройка структуры ссылок. Чтобы настроить их, посетите страницу Постоянные ссылки.Между правилами в Вашем файле .htaccess и правилами самого плагина обнаружены несоответствия. Это может быть просто лишний символ в строке, но Вы должны лично сравнить оригинальные правила со своими как можно скорее. Нажмите на кнопку ’Обновить правила Mod_Rewrite’, чтобы сделать это в автоматическом режиме.Самый простой способ исправить это - изменить права доступа, используя CHMOD, через FTP-клиент. Достаточно установить глобальные права на запись.Допустимые имена & Запрещенные адресаДобавить страницу в кэш:Поле ниже Вы также можете заполнить фрагментами адресов страниц (или групп страниц, например, архив за год/месяц и т.д.), которые не будут кэшироваться. Плагин будет сканировать адреса страниц на предмет наличая в них фрагментов, указанных ниже, перед кэшированием.Поле ниже Вы можете заполнить названиями файлов которые будут кэшированы, даже если в их названии есть запрещенных к кэшированию фрагменты.Добавьте правила самостоятельно. Для этого откройте в редакторе файл %s.htaccess и найдите код между # BEGIN WPSuperCache и # END WPSuperCache. Вы увидите два похожих блока кода. Сразу после строки %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ добавьте следующее (таких строк две, добавьте код и после второй):Дополнительные CNAME (канонические имена)НастройкиВозрастВы также можете отредактировать файл %s.htaccess вручную и лично добавить необходимые правила:АрхивыДоступные плагиныПлагин "Awaiting Moderation"Плагин "Awaiting Moderation" сейчас %sПлагин "Bad Behaviour" Статус плагина "Bad Behaviour": %s. Плагин "Bad Behaviour" не был найден. Проверьте, завершили ли Вы его установку.Настройка CDNДанные настройки CDN предоставлены плагином OSSDL CDN Off Linker от Mark KubackiСостояние кэшаПроверка кэшированияКэшировать сессии просмотров для быстрого доступа.Кэширование происходит за счет PHP файлов, хранящихся в папке плагина. Они загружаются при включении режима Supercache. Загрузка происходит намного чаще, чем для остальных плагинов WordPress.Авто перестройка кэша. Гости блога увидят устаревшие версии страниц кэша пока новые будут генерироваться.Статистика объектов в кэше НЕ создается автоматически. Чтобы обновить ее вручную нажмите на ссылку ниже.Статистика объектов в кэше последний раз создана: %s мин назад.Добавлено в кэш %s секунд назадКэшированные страницы Вашего блога хранятся на сервере в виде .php и .html файлов. Чтобы удалить их, нажмите на кнопку ниже.Страниц в кэше с %1$s : %2$sСтатус кэшированияКэширование выключеноКэширование включеноКэширование страниц - лишь первый шаг на пути ускорения блога! Ниже приведены пару советов по оптимизации Вашего блога:Кэширование должно быть включено, если Вы хотите использовать данную опциюОтменить общее кэшированиеНевозможно продолжить... прежде чем повторить попытку, исправьте предыдущие ошибки.Не могу обновить файл .htaccessРубрикиИзменить время жизни копииПроверять главную страницу каждые 5 минут.Поверка и удаление просроченных страниц кэша занимает время, но и оставлять такие файлы в системе не стоит. На больших блогах нужно выставлять "время жизни" каждой копии 300 секунд. Вы можете поэкспериментировать с настройкой и посмотреть, сколько просроченных копий остается в кэше в течение дня. Оптимальное число - не более 500. Используя mod_rewrite или PHP, Вы сможете увеличить количество кэшируемых страниц.Удалять старые файлы из кэша Super Cache.Очищать кэш когда новая запись или страница опубликована.Очищать кэш при ошибке.Блокировка файлов. Вам скорее всего не понадобится данная опция, но она может решить проблему маломощных хостингов. Внимание! Включение опции, в редких случаях, может вызвать проблемы в работе блога!Проверка комментариев включена. Прежде чем Ваши комментарии будут опубликованы пройдет какое-то время.Сжимать файлы кэша чтобы ускорить работу.Сжатие кэша отключено по умолчанию, так как может некорректно работать на некоторых хостингах. Включение или Отключение данной опции автоматически чистит временный кэш.Файл конфигураций был изменен, некоторые настройки не соответствуют требованиям плагина. Посетите страницу "Настройки" чтобы исправить это.Конфигурационный файл отсутствует, а папка %1$s (%2$s) недоступна для записи. Проверьте права доступа.Состояние кэшаВ данный моменты кэшируются записи с %d по %d.Currently logging to: %sУважаемый пользователь, плагин WP Super Cache был успешно удален с Вашего блога, но правила mod_rewrite в файле .htaccess не были приведены в исходное состояние. Пожалуйста, отредактируйте даный файл вручную, используя текстовый редактор, удалив строчки между 'BEGIN WPSuperCache' и 'END WPSuperCache'. Но сначала создайте резервную копию файла! %s Успехов, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/ОбслуживаниеОтладкаУдалитьУдалить весь кэшУдалить страницы из кэшаУдалить просроченный кэшУдалить файлы Super Cache (в новом окне)Удалить файлы из кэшаУдалите все правила mod_rewrite из файла %s.htaccess, между # BEGIN WPSuperCache и # END WPSuperCache и обновите страницу (восстановление правил запустится автоматически).Удаление файлов Super Cache: %s
    Удаление файлов WP-Cache: %s
    Разработчикам: сделайте свой собственный плагин закрытого режима совместимым с нашим, добавив переменную "WPLOCKDOWN". Приведенный ниже код поможет Вам адоптировать свой плагин к настройкам нашего Режима.Прямое кэширование страницДанный кэш создается прямо из папки, где находится Ваш блог (папка %s). Эта опция полезна только тогда, когда ожидается большой приток посетителей с более популярного ресурса на конкретную страницу или запись Вашего.Включить следующие директории со статичными файлами для перезаписи при совпадении. Используйте запятую (,) для разделения. По умолчанию будут добавлены директории wp-content и wp-includes.ОтключитьОтключенНе кэшировать страницы следующих типов. Сверьтесь с Статьей Кодекса WP (англ.), чтобы узнать подробнее о типах страниц.Плагин "МультиБлог"Обнаружен плагин "Domain Mapping"! Чтобы облегчить и ускорить его работу, Вам нужно включить поддержку мультиблогов в настройках.Статус плагина "Domain Mapping": %s. Не кэшировать страницы для известных пользователей.КэшОтредактируйте код %s и добавьте следующую сточку:
    define('WP_CACHE', true);
    Иначе WP-Cache не сможет запуститься. Сообщить администратору блога по завершению проверки (полезно при тестировании на ошибки).ВключитьВключить поддержку CDNВключенВключите или выключите плагин, чтобы убрать надпись "Ваш комментарий ожидает проверки" когда кто-то размещает комментарий к записи.ОшибкаОшибка: сжатие GZIP включено, отключите его если хотите запустить wp-cache.Исключить форматыИсключить следующие форматы для перезаписи, если найдено совпадение. Используйте запятую (,) для разделения исключений, например: .php, .flv, .do - не забывайте включать .php (по умолчанию).Страница существуетАктуальность кэша:Просроченный кэш - это страницы, созданные более чем %s секунд назад. Не смотря на свой статус, они используются в общем кэше и периодически удаляются.Просроченные страницы & Очистка мусораДополнительная сверка кэша (очень редко может нарушить работу кэширования).ФидыПроверка страницы %s в кэше: Проверка первой копии %s: Проверка второй копии %s: Восстановить стандартные настройкиЗдесь Вы можете решить некоторые проблемы, возникающие при работе с плагином, с помощью отладки. Вся служебная информацию (логи) будет записана в файлы директории кэша.Для более продуктивной работы сайта, Вам стоит включить опцию "Поддержка мобильных устройств" или удалить эту запись из правил в .htaccess. Найдите следующий текст (две строчки) "2.0\ MMP|240x320" и удалите его.Например: чтобы добавить в кэш страницу %1$sabout/, нужно прописать %1$sabout/ или /about/. Кэш для страницы будет создан сразу же после первого к ней обращения гостем.Новые файлы Super CacheНовые файлы WP-CacheОсновная страницаКлючевой текстПолное кэширование проихойдет через %d ч %d мин и %d сек.Сжатие GZIP включено в настройках WordPress, плагин не будет работать до тех пор, пока Вы не отключите gzip.Очистка мусораПравила для Gzip-сжатия добавлены в файл %s.htaccess.Посетите блог автора плагина %1$s и его фотоблог на %2$s.Убрать списокДомашняя страницаОшибки, которые могут возникнуть при работе с WP Super Cache, не связаны с плагином. Они появляются лишь в редких случаях (и то из-за проблем с хостингом или другими плагинами), но Вы можете подстраховаться, запустив автоматическую сверку кэша каждые 5 минут. В случае ошибки, Вам будет отправлено сообщение.Адрес IPЕсли это не сработало, убедитесь что файл %s/advanced-cache.php не существует:Если время актуальности кэша более 1800 секунд (полчаса), то очистка мусора будет запускаться каждые 10 минут.Деактивируя плагин, убедитесь что папка %s доступна для записи в настройках Вашего сервера, чтобы файлы плагина advanced-cache.php и cache-config.php были удалены в автоматическом режиме (также проверьте наличие прав на запись для этих двух файлов).В режиме ’Общего кэширования’ запланированная очистка мусора будет удалять только кэш записей простого типа (кэш из Super Cache не будет удален). Данная настройка рекомендована для использования.В особо редких случаях на блоге могут случиться две проблемы:
    1. Вместо главной страницы пользователи будут видеть предложение загрузить .zip архив с ней
    2. Вместо главной страницы может быть добавлена в кэш совершенно другая (только в случае, если Ваш бог использует следующую структуру ссылок /%category%/%postname%/).
    Включить директорииВозникла ошибка, связанная с тем, что модуль mod_rewrite отсутствует или не установлен. Пожалуйста, проверьте наличие модуля mod_rewrite в конфигурациях сервера. Модуль необходим для корректной работы плагина с статичными файлами. Без подключенного mod_rewrite Вы можете использовать только режимы с поддержкой PHP или среднее кэширование.Кажется, все ссылки Вашего блога заканчиваются символом "/". К сожалению, как только Вы установили данный плагин, сработала опция, обнаружившая копии ссылок без символа "/" на конце, и теперь она не может осуществить перенаправление на верный адрес. Чтобы это исправить это, Вы должны отредактировать файл .htaccess и добавить два новых правила к группе основных правил плагина Supercache:Ключ"Поздняя" инициализация. Плагин будет отображать кэшированные страницы после загрузки WordPress. Опция полезна при режиме совместимости.Упрощенное кэширование.Низкий уровень: 1 e-mail в начале и 1 в конце кэширования.Список кэшированных файловСоздать список страниц в кэше (выводится на этой странице)Закрытый режимЗакрытый режим:Уровень логаСделай свой блог быстрее!Чтобы удалить страницу из такого кэша, очистите текстовое поле и удалите файлы кэша.Высокий уровень: 2 сообщения на 100 записей.Средний уровень: 1 сообщение на 100 записей.РазноеОтсутствующие модули ApacheПоддержка мобильных устройствОбнаружена поддержка мобильных устройствПоддержка блогом мобильных устройств требует присутствия особых правил в файле .htaccess, иначе Вы не сможете использовать эту опцию. Ниже представлены возможые способы (в порядке сложности):Модуль Mod RewriteMod Rewrite не может быть обновлен!Правила mod_rewrite должны быть обновлены!Правила mod_rewrite обновлены!Кажется, модуль mod_rewrite не установлен!Использование mod_rewrite поможет сделать работу блога быстрее, чем PHP (хотя и этот вариант тоже не такой медленный). Этот режим проще и удобнее, но начинающему пользователю лучше использовать кэширование PHP.Нужна помощь?Все еще нужна помощь? Смотрите официальный ЧАВО по плагину Super Cache (англ.). Также, Вы можете задать свой вопрос на форумах тех. поддержки (англ.), или ознакомиться с проблемами других пользователей и предложенными им решениями.Новое в кэше:Следующая очистка будет через %s минутВажно:Важно: рекомендуется включить PHP кэширование, авто перестройку кэша и поддержку для мобильных устройствВажно: Mod_rewrite или Legacy caching отключены. По умолчанию будет загружаться страница "Настройки".Внимание: Среди правил mod_rewrite обнаружены правила от Supercache. Для работы с кэшем будут использоваться они. Чтобы удалить эти правила, Вам нужно вручную отредактировать файл .htaccess.Внимание: проверка правил WP Super Cache mod_rewrite отключена для блогов сети пока не будет запущена на главном блоге.ЕСТЬСписок кэширования недоступен.Основной URLПри работе с кэшем произошли ошибки:Обновлять страницу при добавлении нового комментария к нейPHP использует сжатие для сжатых страницы Вашего сайта. Отключение данной опции рекомендуется, чтобы избежать многократного сжатия страниц плагином. Узнать больше, посетив раздел 16 в "Описание проблем" в файле readme.txt (на англ.). Также ознакомьтесь с этой страницей (на англ.) по php.ini.Страница %d: %d (%s)Страница 1: %sСтраница 2: %sСтраницыОшибка структуры ссылокПожалуйста, оцените этот плагин или расскажите о своей проблеме. Этим вы поможете развивать WP Super Cache дальше.Пожалуйста, создайте файл %s /wp-cache-config.php из wp-super-cache/wp-cache-config-sample.phpПожалуйста, посетите %s автора!Чтобы узнать больше, посетите раздел 16 в Описании проблем в файле readme.txt (на англ.)Для справки смотрите readme.txt (документ на англ.). Там Вы найдете полезную информацию по использованию и удалению плагина WP Super Cache.Произошла ошибка, на главной странице Вашего блога не был обнаружен ключевой текст "%2$s"! Чтобы исправить ошибку, посетите эту страницу %1$s и вручную очистие кэш.Произошла ошибка! Посетите %s чтобы удалить кэш!ПлагиныОбщий кэшКэшировать %s записи.Создать общий кэш сейчасОбщее кэширование было перезапущено. %sПредварительный режим (очистка мусора работает не полностью, опция рекомендована к включению.)Однако, при использовании данного вида кэша создается намного больше файлов. Рекомендуется использовать такой тип, если у Вас очень много записей (10 тысяч и более) на блоге. Особенно это важно, если Вы пользуетесь услугами виртуального хостинга.Общее кэширование отключено. Пожалуйста, включите полный режим работы плагина или обратитесь к администратору сервера.Подготовьте свой блог к запланированным всплескам посещаемости, активировав данный режим. В активном состоянии размещение новых комментариев и записей НЕ будет обновлять статичные файлы в кэше.Рассказать всем, что Вы пользуетесь плагином WP Super Cache (сообщение будет размещено в "подвале" сайта)!Помогите улучшить плагин "Domain Mapping"!Оцените плагин!Режим "только_чтение". Настройки не могут быть изменены.Только чтение:РекомендованоРекомендованные для ускорения блога плагины и полезные материалыОбновление кэша через %d ч %d мин и %d сек.Обновлять общий кэш каждые %s минут (введите 0, чтобы отключить, минимальное допустимое кол-во минут %d).Обновите страницу когда необходимые права доступа будут заданы.Обновите страницу когда закончите редактирование файла .htaccess.Следующие записи обновлены:Обновить статистику кэшаПоисковые и другие ботыНеобходимо для правильного сжатия файлов.Необходимо настроить кэширование на странице плагина. Пользователи браузера IE7 будут видеть необновленные страницы из кэша без поддержки данного модуля.Восстановить настройки по умолчаниюПрава на запись должны быть обновленыПравила должны быть также добавлены к %s:Файл WP-Cache (%s) не был найден. Проверьте, завершена ли установка плагина.СохранитьСохранить все измененияСохранить список файловСохранить список запрещенных фрагментовСохранить настройкиОбщее кэширование по расписанию отключено.Общее кэширование произойдет через %d минутОбщее кэширование произойдет через 10 секунд.Следующее запланированное обновление общего кэша через %d минут.Прокрутите страницу вниз и нажмите кнопку Обновить правила Mod_Rewrite.Страницы поискаОтправлять мне сообщения с уведомлениями об обновлении кэша.Отправить незащищенный (не по https) запрос для главной страницыУстановите дату истечения актуальности страниц. Пользователи могут не увидеть новую версию кэшированной страницы без данного модуля.Установите значение 0 чтобы отключить Очистку мусора.Переведите плагин в режим среднего кэширования и включите поддержку мобмльных устройств.НастройкиЗаписиПропустить адреса типа https чтобы избежать ошибок, связанных с использование защищенных и незащищенных узловИзвините, мой блог временно недоступен. Зайдите попозже...Старые файлы Super CacheСтарые файлы WP-CacheЧтобы запретить плагину кэшировать запросы от поисковых ботов и других сетевых роботов, введите их названия в поле ниже (по одному в строке). Если копия страницы уже существует в кэше Super Cache, то она все равно будет отправлена боту.Проблемы при удалении плагинаМеткиПроверитьЗдесь можно проверить правильность кэширования страниц Вашего блога одним нажатием.Введите текст который плагин будет искать на главной странице. Если текст не будет обнаружен, то кэш автоматически очистится. Оставьте поле пустым чтобы отключить опцию.Спасибо за обновление.Конфигурационный файл плагина WP Super Cache %s/wp-cache-config.php не может быть изменен. Чтобы продолжить, Вы должны установить права на запись для файла.Произошла ошибка, на главной странице Вашего блога не был обнаружен ключевой текст "%2$s"! Посетите эту страницу %1$s чтобы проверить кэш.Весь кэш для Вашего блога был очищен, так как плагин заметил ошибку на главной странице (она скачивалась архивом). Чтобы проверить кэш, посетите эту стрницу %s.Файл %s.htaccess не может быть обновлен в автоматическом режиме. Чтобы исправить это задайте необходимые для записи права доступа к нему.Следующие модули Apache отсутствуют на Вашем сервере. Без них плагин сможет работать только в режиме среднего кэширования. В режиме с поддержкой Super Cache Ваши пользователи могут видеть поврежденные страницы или просроченные их копии.С момента последней установленной версии плагина правила mod_rewrite были изменены. К сожалению, Вам придется вручную удалить старые правила прежде чем новые заработают. Обновите эту страницу когда закончите редактировать файл .htaccess. Если Вы хотите полностью обновить все сами, то замените следующую строку: %1$s на эту: %2$s . Единственное отличие - это замена "HTTP_COOKIE" на "HTTP:Cookie" и "wordpressuser" на "wordpress". Эти перемены связаны с новой версией WordPress 2.5. Конечно Вы можете продолжать работать со старыми версиями, если хватит смелости ;)Новый адрес будет использован вместо старого %1$s. Не используйте символ / на конце адреса.
    Пример: %2$s.Страницы не совпадают! Временной штамп отличается или не был найден!Необходимые для работы плагина права были изменены или отсуствуют.Временные штампы обоих вариантов страницы совпадают!Эти записи CNAME будут использованы вместо %1$s (в дополнении к основному URL). Используйте запятую (,) для разделения записей. Для страниц с большим количеством статичных файлов данная опция может уменьшить время загрузки. Записи CNAME также могут быть использованы для конфигурации CDN.
    Пример: %2$sДля использования данной опции нужно знать PHP, и свободно разбираться в устройстве WordPress.При активации общего кэширования, будет создана копия для каждой записи и страницы Вашего блога. В этом режиме создаются статичные страницы, которые затем будут видеть "неопознанные" посетители (например, поисковые боты и другие). Это может помочь в улучшении уровня PR Google, так как в основе их алгоритма лежит и скорость отклика веб-сайта.На Ваших обычных посетителях это никак не отразится, а вот использующие мобильные устройства для веб-серфинга не будут получать кэшированные страницы (если опция отключена).Чтобы плагин мог правильно работать со статичными html файлами, Вы должны добавить в файл %s.htaccess правила модуля mod_rewriteСлишком много объектов в кэше, создание списка невозможно.Требуется проверка ссылок на слеш ("/").АДРЕСК сожалению, файл wp-cron.php не был обнаружен. Этот скрипт необходим для корректной работы опциии "Очистка мусора" и самого WordPress.К сожалению, mod_rewrite невозможно обновить в автоматическом режиме в WordPress MU. Вам придется вручную сделать это: откройте файл .htaccess (расположен в корневой директории блога) и добавьте следующие правила в него.Удаляйте плагин только со специальной страницы. Все лишние файлы будут удалены автоматически (некоторые файлы нужно будет редактировать вручную).ОбновитьОбновить стрницыОбновить правила mod_rewriteОбновить настройкиОбновитьИспользовать PHP для обслуживания кэша.Использовать mod_rewrite для обслуживания кэша.Использовать объекты кэша для хранения кэшированных файлов.Посмотреть правила mod_rewriteНастройки WP Super CacheПлагин WP Super Cache только что проверил главную страницу Вашего блога на предмет ошибок. Чтобы отключить уведомления и проверку посетите эту страницу %s.Плагин WP Super Cache не активирован! Чтобы включить его, перейдите на страницу управления.Правила mod_rewrite для плагина WP Super Cache были обнаружены в файле %s.htaccess.
    Нажмите на соответствующую кнопку, чтобы посмотреть строчки. Если Вы только что обновили плагин, проверьте все правила.Плагин WP Super Cache должен быть настроен! Чтобы включить его и настроить, перейдите на страницу управления.Состояние WP-CacheСостояние WP-Super-CacheВниманиеВнимание!Внимание! Папка %s доступна для записи!Внимание! Функция gzencode() не найдена, сжатие отключено.Внимание! Включен режим PHP Safe Mode!ВНИМАНИЕ! Кэширование отключено, плагин поврежден! WP Super Cache не может загрузить скрипт wp-cache-phase1.php.

    Чтобы исправить ошибку, откройте файл %1$s/advanced-cache.php и проверьте строчку, указывающую на %2$swp-cache-phase1.php.Внимание! Ваше hostname "%s" преобразовано в %sОбнаружен WordPress MU!Ваш блог использует Закрытый режим. Новые комментарии не обновляют все статичные элементы кэша.Ваш блог не использует Закрытый режим. Новые комментарии обновляют все статичные элементы кэша.Доступно для записи:Вы можете использовать различные адреса CDN для каждого блога (если у Вас мультиблог).Вы можете вручную отредактировать файл и добавить необходимые правила.Чтобы посмотреть полный список работающих правил, нажмите кнопку "Посмотреть правила mod_rewrite".При работе с плагином могут возникнуть проблемы, так как PHP Safe Mode включен на Вашем сервере.Для корректной работы в Вашем файле %s.htaccess должны быть прописаны маркеры BEGIN, и END. Между ними находятся основные правила WordPress mod_rewrite, пример:Вы должны разрешить запись для %s. Но так как это потенциальная уязвимость, после обновления страницы верните права на чтение.Вы или Администратор можете исправить ошибки, изменив группу владельца скриптов плагина через настройки веб-сервера. Также нужно изменить владельца для папки %s/cache/. Для более подробной информации смотрите страницу помощи по режиму safe mode (на англ.).Вы или Администратор должны отключить это. Для более подробной информации смотрите страницу помощи по режиму safe mode (на англ.). Данные настройки НЕ могут быть отключены через файл .htaccess, для решения проблемы нужно редактировать php.ini в настройках веб-сервера.Вы должны изменить права на папку %s. Чтобы сделать это - воспользуйтесь FTP-клиентом или следующей командой:Ваш файл %s.htaccess недоступен для записи (в настройках сервера) и не может быть обновлен в автоматическом режиме. Вы должны вручную добавить новые правила к основным так, как указано ниже:Конфигурационный файл WP-Cache (%s) может быть недоступен для записи. Пожалуйста, удалите его вручную и обновите страницу.Папка для хранения кэша ($cache_path) не существует и не может быть создана в автоматическом режиме. Проверьте права доступа к %s.Папка (%1$s) или %2$s должна быть доступна для записи. Перепроверьте права доступа.Ваш комментарий ожидает подтверждения.Ваш сервер настроен так, что проверяет владельца для всех PHP скриптов перед тем как разрешить им чтение или запись в файл.Ваш веб-сервер решил, что hostname изменено на %s. Некоторые опции плагина (например, "Очистка мусора") и сам WordPress могут работать некорректно.Скорее всего, на Вашем блоге очень много статичных файлов: изображений, файлов JS и CSS. Для улучшения работы блога, стоит загружать данные файлы с другого сайта или CDN. Данный плагина позволит изменить ссылки на все статичные файлы в wp-content и wp-includes (кроме файлов .php) на указанные ниже. Вы также можете скопировать все статичные файлы на любой другой хост или создать их копии на CDN. Подробнее об этом узнайте тут (англ.).Сжатие Zlib Output включено![%1$s] %2$d кэш записей обновлен[%1$s] Общее кэширование началось[%1$s] Общее кэширование остановлено[%1$s] Обновление кэша записей с %2$d по %3$d[%s] Общее кэширование завершено[%s] Главная страница проверена![%s] Главная страница сжата с помощью gzipped! Кэш удален![%s] Главная страница сжата с помощью gzipped! Удалите кэш![%s] Главная страница отображается с ошибкой! Кэш удален![%s] Кэш главной страницы содержит ошибку! Удалите кэш![%s] Общее кэширование могло быть прервано.весьотключенвключенсекундlanguages/wp-super-cache-sv_SE.po000066600000210547152133035240012725 0ustar00msgid "" msgstr "" "Project-Id-Version: wp-super-cache 0.9.9.6\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2010-09-27 13:58+0000\n" "PO-Revision-Date: \n" "Last-Translator: Fredrik Forséll \n" "Language-Team: Faffe \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Swedish\n" "X-Poedit-Country: SWEDEN\n" "X-Poedit-SourceCharset: utf-8\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Din kommentar väntar på moderering." #: plugins/awaitingmoderation.php:23 #: plugins/awaitingmoderation.php:38 #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:47 #: plugins/domain-mapping.php:62 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1114 msgid "Disable" msgstr "Inaktivera" #: plugins/awaitingmoderation.php:29 #: plugins/badbehaviour.php:55 #: plugins/domain-mapping.php:53 #: plugins/searchengine.php:67 msgid "disabled" msgstr "inaktiverad" #: plugins/awaitingmoderation.php:31 #: plugins/badbehaviour.php:57 #: plugins/domain-mapping.php:55 #: plugins/searchengine.php:69 #: wp-cache.php:1460 msgid "enabled" msgstr "aktiverad" #: plugins/awaitingmoderation.php:33 #, php-format msgid "Awaiting Moderation plugin is %s" msgstr "Tillägget Awaiting Moderation är %s" #: plugins/awaitingmoderation.php:34 msgid "(Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment.) " msgstr "(Ta bort texten \"Din kommentar väntar på moderering.\" när någon lämnar en modererad kommentar.)" #: plugins/awaitingmoderation.php:36 #: plugins/badbehaviour.php:63 #: plugins/domain-mapping.php:60 #: plugins/searchengine.php:74 #: wp-cache.php:1114 msgid "Enable" msgstr "Aktivera" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "Bad Behaviour hittades inte. Var vänlig kontrollera din installation." #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s." msgstr "Bad Behaviour-stöd är %s." #: plugins/badbehaviour.php:61 #, php-format msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(endast föråldrad cache stöds, inaktiverad kompression och kräver Bad Behavior i \"%s/plugins/bad-behavior/\")" #: plugins/badbehaviour.php:69 #: wp-cache.php:1191 #: wp-cache.php:1193 msgid "Warning!" msgstr "Varning!" #: plugins/domain-mapping.php:57 #, php-format msgid "Domain Mapping support plugin is %s" msgstr "Domain Mapping-tilläget är %s" #: plugins/domain-mapping.php:58 msgid "(support for multiple domains on multisite websites) " msgstr "(stöd för flera domäner på flera webbplatser)" #: plugins/domain-mapping.php:72 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Domain Mapping-tillägget detekterat! Var vänlig gå till Supercache-tilläggets sida och aktivera domain mapping hjälp-tillägget." #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s." msgstr "No Adverts for Friends-tillägget är %s" #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(kräver friendsadverts.php också) " #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Var vänlig skapa %s /wp-cache-config.php från wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:138 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Varning! PHP Safe Mode aktiverat!" #: wp-cache.php:139 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Du kan uppleva problem när du använder det här tillägget eftersom SAFE MODE är aktiverat." #: wp-cache.php:143 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Din server är inställd för att kontrollera ägaren av PHP-skript innan den tillåter dom att läsa och skriva filer." #: wp-cache.php:144 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Du eller en administratör kan få det att fungera genom att ändra grupp-ägaren av pluginskripten till att passa webserver användaren. Gruppägaren av mappen %s/cache/ måste också ändras. Läs safe mode manualsidan för mer information." #: wp-cache.php:146 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Du eller en administratör måste inaktivera det här. Läs safe mode manualsidan för mer information. Det här kan tyvärr inte inaktiveras i en .htaccess fil. Det måste göras i konfigurationsfilen php.ini." #: wp-cache.php:152 msgid "Permlink Structure Error" msgstr "Fel på permalänkstrukturen" #: wp-cache.php:153 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "En anpassad url- eller permalänkstruktur behövs för att detta tillägg ska fungera korrekt. Var vänlig gå till Inställningssidan för Permalänkar och ställ in dina permalänkar." #: wp-cache.php:165 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Varning! Ditt värdnamn \"%s\" löses upp till %s" #: wp-cache.php:166 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Din server tror ditt värdnamn löses upp till %s. En del tjänster som upprensningen av det här tillägget, och Wordpress schemalagda inlägg kanske inte fungerar korrekt." #: wp-cache.php:167 #: wp-cache.php:181 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Var vänlig läs inlägg 16 i Felsökningsdelen av readme.txt" #: wp-cache.php:180 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Tyvärr kan inte WordPress hitta filen wp-cron.php. Det här skriptet krävs för att upprensningen av det här tillägget ska fungera korrekt, WordPress schemalagda inlägg såväl som andra kritiska aktiviteter." #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "Kan inte fortsätta... rätta till tidigare problem och försök igen." #: wp-cache.php:204 msgid "Zlib Output Compression Enabled!" msgstr "Zlib utdatakomprimering aktiverad!" #: wp-cache.php:205 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP komprimerar datat som sänds till besökare på din webbsida. Det rekommenderas att stänga av det eftersom tillägget sparar det komprimerade utdatat en gång i stället för att komprimera samma sida om och om igen. Se också #21 på felsökningssidan. Se denna sida för instruktioner hur du ändrar din php.ini." #: wp-cache.php:209 msgid "Mod rewrite may not be installed!" msgstr "Mod rewrite kanske inte är installerat!" #: wp-cache.php:210 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Det verkar som att mod_rewrite inte är installerat. Ibland är inte den här kontrollen 100% tillförlitlig, speciellt om du inte använder Apache. Var vänlig kontrollera att mod_rewrite-modulen laddas. Det är nödvändigt för att skapa Super Cache statiska filer. Du kan fortfarande använda föråldrade och PHP-lägena." #: wp-cache.php:215 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Skrivskyddat läge. Konfigurationen kan inte ändras." #: wp-cache.php:216 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "WP Super Cache-konfigurationsfilen är %s/wp-cache-config.php och kan inte ändras. Den filen måste vara skrivbar av web-servern för att kunna göra några ändringar." #: wp-cache.php:217 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Ett enkelt sätt att göra detta är att ändra rättigheterna tillfälligt genom att använda CHMOD kommandot eller genom din ftp-klient. Kontrolllera att den är globalt skrivbar och det ska gå bra." #: wp-cache.php:218 msgid "Writeable:" msgstr "Skrivbar:" #: wp-cache.php:219 msgid "Readonly:" msgstr "Skrivskyddad:" #: wp-cache.php:231 #, php-format msgid "Warning! %s is writeable!" msgstr "Varning! %s är skrivbar!" #: wp-cache.php:232 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Du bör ändra rättigheterna på %s och göra dom mer restriktiva. Använd din ftp-klient, eller följande kommando för att rätta till:" #: wp-cache.php:240 msgid "Mobile rewrite rules detected" msgstr "Mobila omskrivningsregler hittade" #: wp-cache.php:241 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "För bästa prestanda ska du aktivera \"Stöd för mobila enheter\" eller radera de mobila omskrivningsreglerna i din .htaccess. Leta efter de 2 raderna med texten \"2.0\\ MMP|240x320\" och radera dessa. " #: wp-cache.php:241 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Det här har ingen påverkan på vanliga användare men mobila användare kommer se ocachade sidor." #: wp-cache.php:247 #: wp-cache.php:258 msgid "Rewrite rules must be updated" msgstr "Mod Rewrite regler måste uppdateras" #: wp-cache.php:248 #: wp-cache.php:259 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Rewrite-reglerna som krävs för detta tillägg har ändrats eller saknas." #: wp-cache.php:249 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Mobilt stöd kräver extra regler i din .htaccess fil, eller så kan du ställa in tillägget på föråldrat läge. Här är dina valmöjligheter (sorterat efter svårighetsgrad):" #: wp-cache.php:250 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Ställ in tillägget på föråldrat läge och aktivera mobilt stöd." #: wp-cache.php:251 #: wp-cache.php:260 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Skrolla ner till de avancerade inställningarna och klicka på knappen Uppdatera Mod_Rewrite Reglerna." #: wp-cache.php:252 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Radera tilläggets mod_rewrite regler i %s.htaccess omslutet av # BEGIN WPSuperCache och # END WPSuperCache och låt tillägget återskapa dom genom att ladda om den här sidan." #: wp-cache.php:253 #, php-format msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Lägg till reglerna själv. Redigera %s.htaccess och hitta blocket med kod som omsluts av raderna # BEGIN WPSuperCache och # END WPSuperCache. Det är två delar som ser väldigt lika ut. Precis nedanför raden %%{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ lägg till den här raden: (gör det två gånger, en för varje del)" #: wp-cache.php:266 msgid "Required to serve compressed supercache files properly." msgstr "Krävs för att visa komprimerade supercache filer korrekt." #: wp-cache.php:266 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Krävs för att ställa in cacheinformation på supercache sidor. IE7 användare kommer se gamla sidor utan den här modulen." #: wp-cache.php:266 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Ställ in utgångsdatum på supercachade sidor. Besökare kanske inte ser nya sidor när dom laddar om eller lämnar en kommentar utan den här modulen." #: wp-cache.php:273 msgid "Missing Apache Modules" msgstr "Saknade Apachemoduler" #: wp-cache.php:274 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Följande Apache moduler saknas. Tillägget fungerar i föråldrat läge utan dessa. I fullt Supercache läge kan dina besökare dock se förvanskade sidor eller gammalt innehåll." #: wp-cache.php:413 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Varning! Du försökte aktivera komprimering men zlib.output_compression är aktiverad. Se #21 i felsökningssektionen i readme-filen." #: wp-cache.php:501 msgid "WP Super Cache Settings" msgstr "WP Super Cache-inställningar" #: wp-cache.php:512 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Observera: Mod_rewrite eller föråldrar cachning aktiverad. Visar avancerade inställningar som standard." #: wp-cache.php:523 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Konfigurationsfil ändrad, några värden kan vara fel. Ladda sidan igen från \"Inställningar\"-menyn för att återställa dom." #: wp-cache.php:540 #: wp-cache.php:614 msgid "Caching must be enabled to use this feature" msgstr "Cachning måste vara aktiverad för att använda den här funktionen" #: wp-cache.php:542 msgid "Cache Tester" msgstr "Cachetestare" #: wp-cache.php:543 msgid "Test your cached website by clicking the test button below." msgstr "Testa din cachade websida genom att genom att klicka på testknappen nedan." #: wp-cache.php:550 #, php-format msgid "Fetching %s to prime cache: " msgstr "Hämtar %s till den primära cachen:" #: wp-cache.php:552 #: wp-cache.php:559 #: wp-cache.php:566 msgid "OK" msgstr "OK" #: wp-cache.php:557 #, php-format msgid "Fetching first copy of %s: " msgstr "Hämtar första kopian av %s:" #: wp-cache.php:564 #, php-format msgid "Fetching second copy of %s: " msgstr "Hämtar en andra kopia av %s:" #: wp-cache.php:570 msgid "One or more page requests failed:" msgstr "En eller flera sidförfrågningar misslyckades:" #: wp-cache.php:589 #: wp-cache.php:590 #, php-format msgid "Page %d: %d (%s)" msgstr "Sida %d: %d (%s):" #: wp-cache.php:596 #, php-format msgid "Page 1: %s" msgstr "Sida 1: %s" #: wp-cache.php:597 #, php-format msgid "Page 2: %s" msgstr "Sida 2: %s" #: wp-cache.php:598 msgid "The timestamps on both pages match!" msgstr "Tidsstämplarna på sidorna matchar!" #: wp-cache.php:600 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Sidorna matchar inte! Tidsstämplarna är olika eller hittades inte!" #: wp-cache.php:606 msgid "Send non-secure (non https) request for homepage" msgstr "Skicka osäker (icke https) förfrågan om hemsida" #: wp-cache.php:607 msgid "Test Cache" msgstr "Testa Cache" #: wp-cache.php:632 #: wp-cache.php:755 msgid "Cancel Cache Preload" msgstr "Avbryt cache-förladdning" #: wp-cache.php:638 msgid "Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete." msgstr "Schemalagd förladdning av cachen avbruten. Om ett jobb för tillfället körs kommer det inte att stängas av förrän de nuvarande 100 sidorna är färdiga." #: wp-cache.php:649 msgid "Scheduled preloading of cache cancelled." msgstr "Schemalagd förladdning av cachen avbruten." #: wp-cache.php:675 #: wp-cache.php:753 msgid "Preload Cache Now" msgstr "Förladda cache nu" #: wp-cache.php:678 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Schemalagd förladdning av cachen om 10 sekunder." #: wp-cache.php:682 #, php-format msgid "Scheduled preloading of cache in %d minutes" msgstr "Schemalagd förladdning av cachen om %d minuter." #: wp-cache.php:686 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Det här kommer att cacha varje publicerat inlägg och sida på din webbplats. Det kommer att skapa statiska supercachefiler så att okända besökare (inklusive bottar) kommer att träffa en cachad sida. Det kommer antagligen att hjälpa din Google-rankning eftersom de numera använder hastighet som ett mätvärde när det bedömer webbplatser." #: wp-cache.php:687 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Förladdning skapar massor med filer. Cachning görs från det nyaste inlägget till det äldsta, så fundera på att bara cacha de nyaste om du har massor (10000+) inlägg. Det är särskilt viktigt med en delad webbserver." #: wp-cache.php:688 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "I ’Förladdningsläge’ kommer upprensningen bara ta bort gamla filer för kända användare, inte de förladdade supercachefilerna. Det är en rekommenderad inställning när cachen är förladdad." #: wp-cache.php:692 #, php-format msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Uppdatera förladdade cachefiler var %s minut. (0 för att stänga av, minst %d minuter.)" #: wp-cache.php:705 msgid "all" msgstr "alla" #: wp-cache.php:718 #, php-format msgid "Preload %s posts." msgstr "Förladda %s inlägg." #: wp-cache.php:725 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Förladdningsläge (upprensning av endast gamla filer. Rekommenderat.)" #: wp-cache.php:728 msgid "Send me status emails when files are refreshed." msgstr "Skicka status-epost till mig när filerna uppdateras." #: wp-cache.php:733 msgid "Many emails, 2 emails per 100 posts." msgstr "Mycket e-post, 2 brev per 100 inlägg." #: wp-cache.php:736 msgid "Medium, 1 email per 100 posts." msgstr "Mellan, 1 brev per 100 inlägg." #: wp-cache.php:739 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Mindre e-post, 1 i början och 1 i slutet av förladdning av alla inlägg." #: wp-cache.php:743 #, php-format msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Uppdatering av cache om %d timmar %d minuter och %d sekunder." #: wp-cache.php:744 #, php-format msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Fullständig uppdatering om %d timmar %d minuter och %d sekunder." #: wp-cache.php:750 #, php-format msgid "Currently caching from post %d to %d." msgstr "För närvarande cachas från inlägg %d till %d." #: wp-cache.php:753 msgid "Update Settings" msgstr "Uppdatera inställningar" #: wp-cache.php:761 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Förladdning av cache är avaktiverat. Var vänlig avaktivera föråldrat läge eller prata med din serveradministratör." #: wp-cache.php:776 #: wp-cache.php:865 msgid "Caching" msgstr "Cachning" #: wp-cache.php:780 msgid "Cache hits to this website for quick access." msgstr "Cacheträffar för den här webbplatsen för snabb åtkomst." #: wp-cache.php:780 #: wp-cache.php:781 #: wp-cache.php:795 #: wp-cache.php:799 #: wp-cache.php:802 #: wp-cache.php:803 #: wp-cache.php:868 msgid "Recommended" msgstr "Rekommenderat" #: wp-cache.php:781 msgid "Use mod_rewrite to serve cache files." msgstr "Använd mod_rewrite för att serva cachefiler." #: wp-cache.php:782 msgid "Use PHP to serve cache files." msgstr "Använd PHP för att presentera cachade filer." #: wp-cache.php:783 msgid "Legacy page caching." msgstr "Föråldrad sidcaching" #: wp-cache.php:784 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching." msgstr "Mod_rewrite är det snabbaste, PHP är nästan lika snabbt och enklare att få igång, medans föråldrat läge är långsammare, men mer flexibelt och också enkelt att få igång. Nya användare bör starta med PHP-caching." #: wp-cache.php:790 msgid "Miscellaneous" msgstr "Diverse" #: wp-cache.php:795 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Komprimera sidor så att de presenteras snabbare för besökare." #: wp-cache.php:796 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Komprimering är inaktiverat som standard för vissa värdar har problem med komprimerade filer. Att sätta på eller stänga av det här rensar cachen." #: wp-cache.php:799 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Not Modified webbläsarcaching. Indikerar när en sida inte har modifierats sedan den senast hämtades." #: wp-cache.php:800 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "304-stöd är avstängt som standard eftersom GoDaddy förut har haft problem med några av sidhuvudena som använts." #: wp-cache.php:802 msgid "Don’t cache pages for known users." msgstr "Cacha inte sidor för kända användare." #: wp-cache.php:803 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Cacheombyggning. Presentera en supercachefil till anonyma användare medan en ny fil genereras." #: wp-cache.php:804 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Berätta stolt för världen att din server är Diggsäker! (placerar ett meddelande i din bloggs sidfot)" #: wp-cache.php:810 #: wp-cache.php:957 #: wp-cache.php:1473 msgid "Advanced" msgstr "Avancerat" #: wp-cache.php:814 msgid "Mobile device support." msgstr "Stöd för mobila enheter." #: wp-cache.php:815 msgid "Clear all cache files when a post or page is published." msgstr "Rensa alla cachefiler när ett inlägg eller sida publiceras." #: wp-cache.php:816 msgid "Only refresh current page when comments made." msgstr "Uppdatera endast aktuell sida när en kommentar läggs in." #: wp-cache.php:817 msgid "List the newest cached pages on this page." msgstr "Lista de senast cachade sidorna på den här sidan." #: wp-cache.php:819 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Enkel fillåsning. Du behöver antagligen inte det här men det kan hjälpa om din server är överbelastad. Varning! Kan göra så att din server låser sig i unika fall!" #: wp-cache.php:822 msgid "Use object cache to store cached files." msgstr "Använd objektcache för att lagra cachade filer." #: wp-cache.php:822 msgid "(Experimental)" msgstr "(Experimentellt)" #: wp-cache.php:829 msgid "Note:" msgstr "Notera:" #: wp-cache.php:831 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Om du avinstallerar det här tillägget, kontrollera att katalogen %s är skrivbar av webservern så att filerna advanced-cache.php och cache-config.php kan raderas automatiskt. (Att kontrollera att dessa filer är skrivbara är antagligen också en bra idé) " #: wp-cache.php:832 #, php-format msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Se readme.txt för instruktioner om hur man avinstallerar detta script. Leta efter rubriken \"How to uninstall WP Super Cache\"." #: wp-cache.php:833 #, php-format msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Behöver du hjälp? Kolla Super Cache readme-filen. Den innehåller installationsdokumentation, en FAQ och felsökningstips. Supportforumet finns också. Din fråga kanske redan har besvarats." #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "Uppdatera Status" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "Accepterade filnamn & Avvisade URI:er" #: wp-cache.php:868 msgid "Caching On" msgstr "Cachning på" #: wp-cache.php:869 msgid "Caching Off" msgstr "Cachning av" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Observera: aktiverar PHP-cachning, cacheombyggnad och stöd för mobila enheter" #: wp-cache.php:880 msgid "Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Observera: Supercache mod_rewrite-regler detekterades. Cachade filer kommer att presenteras med de reglerna. Redigera .htaccess-filen i roten för din installation och ta bort Supercachereglerna." #: wp-cache.php:892 msgid "Make WordPress Faster" msgstr "Gör WordPress snabbare" #: wp-cache.php:893 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s underhålls och är utvecklat av %2$s med stöd från många andra." #: wp-cache.php:894 #, php-format msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Han bloggar på %1$s och lägger ut bilder på %2$s." #: wp-cache.php:895 #, php-format msgid "Please say hi to him on %s too!" msgstr "Var vänlig säg hej till honom på %s också!" #: wp-cache.php:903 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Cachade sidor sedan %1$s : %2$s" #: wp-cache.php:904 msgid "Newest Cached Pages:" msgstr "Senast cachade sidor:" #: wp-cache.php:908 #, php-format msgid "Cached %s seconds ago" msgstr "Cachades för %s sekunder sedan" #: wp-cache.php:911 msgid "(may not always be accurate on busy sites)" msgstr "(kanske inte alltid är helt korrekt på upptagna sidor)" #: wp-cache.php:930 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Cachetillägg är PHP-script som finns i en tilläggsmapp i wp-super-cache-mappen. De laddas när Supercache laddas, mycket tidigare än vanliga WordPresstillägg." #: wp-cache.php:931 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Detta är en avancerad funktion och kunskap om både PHP och WordPress agerande behövs för att skapa dem." #: wp-cache.php:941 msgid "Available Plugins" msgstr "Tillgängliga tillägg" #: wp-cache.php:957 msgid "Easy" msgstr "Enkel" #: wp-cache.php:957 msgid "Tester & Contents" msgstr "Testare & innehåll" #: wp-cache.php:957 msgid "Preload" msgstr "Förladda" #: wp-cache.php:957 msgid "Plugins" msgstr "Tillägg" #: wp-cache.php:957 msgid "Debug" msgstr "Debug" #: wp-cache.php:984 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Observera: WP Super Cache mod_rewrite regelkontroller är avstängda när du inte kör på huvudsidan i nätverket." #: wp-cache.php:986 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Observera: WP Super Cache mod_rewrite regelkontroller är avstängda när du inte kör på huvudsidan i nätverket." #: wp-cache.php:996 msgid "Mod Rewrite Rules" msgstr "Mod Rewrite regler" #: wp-cache.php:1002 msgid "WordPress MU Detected" msgstr "WordPress MU detekterat" #: wp-cache.php:1002 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Tyvärr kan inte omskrivningsreglerna uppdateras automatiskt när WordPress MU körs. Var vänlig öppna din .htaccess och lägg till följande mod_rewrite regel över alla andra regler i den filen." #: wp-cache.php:1004 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite reglerna kan inte uppdateras!" #: wp-cache.php:1005 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Du måste ha BEGIN och END markeringar i %s.htaccess för att automatisk uppdatering ska fungera. Dom ser ut såhär om omger de huvudsakliga WordPress mod_rewrite reglerna:" #: wp-cache.php:1007 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Uppdatera den här sidan när du har uppdaterat din .htaccess fil." #: wp-cache.php:1011 msgid "Thank you for upgrading." msgstr "Tack för att du uppgraderat." #: wp-cache.php:1011 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Mod_rewrite reglerna har ändrats sedan du senast installerade det här tillägget. Tyvärr måste du ta bort de gamla supercache reglerna innan de nya är uppdaterade. Uppdatera den här sidan när du har redigerat din .htaccess fil. Om du vill uppgradera manuellt, ändra följande rad: %1$s så den ser ut såhär: %2$s De enda ändringarna är \"HTTP_COOKIE\" blir \"HTTP:Cookie\" och \"wordpressuser\" blir \"wordpress\". Det här är en WordPress 2.5 ändring men det är bakåt kompatibelt med äldre versioner om du är modig nog att använda dem." #: wp-cache.php:1015 msgid "Trailing slash check required." msgstr "Efterföljande slash kontroll krävs." #: wp-cache.php:1015 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Det verkar som att din blogg har URL:er som slutar med en \"/\". Tyvärr eftersom du har installerat det här tillägget har en dubbelt-innehåll-bugg hittats där URL:er som inte slutar med \"/\" visar samma innehåll som dom med \"/\" och vidarebefordrar inte till rätt URL. För att laga, måste du redigera din .htaccess fil och lägga till de här två reglerna till de två grupperna med Super Cache regler:" #: wp-cache.php:1017 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Du kan se var reglerna går och utforska de kompletta reglerna genom att klicka \"Visa mod_rewrite regler\" länken nedan." #: wp-cache.php:1031 msgid "Mod Rewrite rules updated!" msgstr "Mod Rewrite regler uppdaterade!" #: wp-cache.php:1032 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "%s.htaccess har uppdaterats med dom nödvändiga mod_rewrite reglerna. Var vänlig kontrollera att dom är rätt. Dom ska se ut såhär:" #: wp-cache.php:1034 msgid "Mod Rewrite rules must be updated!" msgstr "Mod Rewrite regler måste uppdateras!" #: wp-cache.php:1035 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Din %s.htaccess är inte skrivbar av webservern och måste uppdateras med dom nödvändiga mod_rewrite reglerna. Dom nya reglerna ska finnas över dom vanliga WordPress reglerna som i koden nedan:" #: wp-cache.php:1040 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "WP Super Cache mod rewrite regler hittades i din %s.htaccess fil.
    Klicka på följande länk för att se raderna som lagts till i den filen. Om du har uppgraderat tillägget kontrollera att reglerna överensstämmer." #: wp-cache.php:1043 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "En skillnad mellan reglerna i din .htaccess-fil och tilläggets omskrivningsregler har hittats. Det kan bero på enkla blankstegsfel men du bör kontrollera reglerna i filen mot de nedan snarast. Clicka på ’Uppdatera Mod_Rewrite-reglerna’-knappen för att uppdaterna reglerna." #: wp-cache.php:1046 msgid "View Mod_Rewrite Rules" msgstr "Visa Mod_Rewrite regler" #: wp-cache.php:1050 #: wp-cache.php:2287 #, php-format msgid "Rules must be added to %s too:" msgstr "Regler måste läggas till i %s också:" #: wp-cache.php:1058 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Gzip-kodningsregler i %s.htaccess skapade." #: wp-cache.php:1065 msgid "Fix Configuration" msgstr "Laga konfiguration" #: wp-cache.php:1068 msgid "Restore Default Configuration" msgstr "Återställ standardinställningar" #: wp-cache.php:1076 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Kommentarsmoderering är aktiverad. Dina kommentarer kan ta ett tag innan de visas." #: wp-cache.php:1101 msgid "Lock Down:" msgstr "Lock Down:" #: wp-cache.php:1101 msgid "Disabled" msgstr "Inaktiverad" #: wp-cache.php:1101 msgid "Enabled" msgstr "Aktiverad" #: wp-cache.php:1102 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Förbered din server för en förmodad topp i trafiken genom att aktivera Lock Down. När denna är aktiverad kommer nya kommentarer till ett inlägg inte uppdatera dom cachade statiska filerna." #: wp-cache.php:1103 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Utvecklare: Gör ditt tillägg Lock Down kompatibelt genom att kontrollera \"WPLOCKDOWN\" konstanten. Följande kod gör att ditt tillägg respekterar WPLOCKDOWN inställningen." #: wp-cache.php:1105 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Tyvärr. Min blogg är låst. Uppdateringar kommer snart att synas" #: wp-cache.php:1109 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress är låst. Super Cache statiska filer kommer inte raderas när nya kommentarer är gjorda." #: wp-cache.php:1111 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress är inte låst. Nya kommentarer kommer uppdatera Super Cache statiska filer som vanligt." #: wp-cache.php:1117 msgid "Lock Down" msgstr "Lock Down" #: wp-cache.php:1125 msgid "Directly Cached Files" msgstr "Direkt cachade filer" #: wp-cache.php:1183 #, php-format msgid "%s removed!" msgstr "%s borttaget!" #: wp-cache.php:1191 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Du måste göra %s skrivbar för att aktivera den här funktionen. Eftersom det här är en säkerhetsrisk, gör den skrivskyddad efter att din sida är genererad." #: wp-cache.php:1193 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s är skrivbar. Var vänlig gör den skrivskyddad efter att din sida är genererad eftersom det här är en säkerhetsrisk." #: wp-cache.php:1207 msgid "Existing direct page" msgstr "Existerande direkta sidor" #: wp-cache.php:1207 msgid "Delete cached file" msgstr "Radera cachade filer" #: wp-cache.php:1212 msgid "Add direct page:" msgstr "Lägg till direkt sida:" #: wp-cache.php:1214 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Direkt cachade filer är filer skapade direkt från %s där din blogg bor. Den här funktionen är bara användbar om du förväntar en stor Digg eller Slashdot höjning av trafik till ett inlägg eller en sida." #: wp-cache.php:1216 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Som exempel: för att cacha %1$sabout/, ska du skriva %1$sabout/ eller /about/. Den cachade filen kommer genereras nästa gång en anonym användare besöker den sidan." #: wp-cache.php:1217 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Töm textboxen för att radera den från listan över direkta sidor och radera den cachade filen." #: wp-cache.php:1222 msgid "Update Direct Pages" msgstr "Uppdatera direkta sidor" #: wp-cache.php:1260 msgid "Expiry Time & Garbage Collection" msgstr "Utgångs tid & upprensning" #: wp-cache.php:1262 msgid "Expire time:" msgstr "Utgångstid:" #: wp-cache.php:1263 msgid "seconds" msgstr "sekunder" #: wp-cache.php:1264 msgid "Garbage Collection" msgstr "Upprensning" #: wp-cache.php:1264 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Om utgångstiden är mer än 1800 sekunder (en halvtimme), kommer upprensning köras var 10:e minut, annars kommer den köras 10 sekunder efter utgångstiden ovan." #: wp-cache.php:1265 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Att leta efter och radera utgångna filer är kostsamt, men det är kostsamt att lämna dom där också. På en väldigt upptagen sida bör du ställa utgångstiden till 300 sekunder. Experimentera med olika värden och besök den här sidan för att se hur många utgångna filer som finns kvar vid olika tidpunkter under dagen. Om du använder förlådrad caching , sikta på att ha färre än 500 cachade sidor om möjligt. Du kan ha många gånger fler cachade filer när du använder mod_rewrite eller PHP-caching." #: wp-cache.php:1266 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Sätt utgångstiden till 0 sekunder för att stänga av upprensning." #: wp-cache.php:1267 msgid "Change Expiration" msgstr "Ändra utgång" #: wp-cache.php:1311 msgid "Rejected User Agents" msgstr "Avvisade User Agents" #: wp-cache.php:1312 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Strängar i ’User Agent’ huvudet som förhindrar WP-Cache från cachande robotar, spindlar och crawlers’ förfrågningar. Notera att super cachade filer skickas fortfarande till dessa agenter om dom redan existerar." #: wp-cache.php:1319 msgid "Save UA Strings" msgstr "Spara UA strängar" #: wp-cache.php:1342 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Cacha inte följande sidtyper. Läs Conditional Tags dokumenten för en komplett diskussion av varje typ." #: wp-cache.php:1345 msgid "Single Posts" msgstr "Enstaka inlägg" #: wp-cache.php:1346 msgid "Pages" msgstr "Sidor" #: wp-cache.php:1347 msgid "Front Page" msgstr "Framsida" #: wp-cache.php:1348 msgid "Home" msgstr "Hem" #: wp-cache.php:1349 msgid "Archives" msgstr "Arkiv" #: wp-cache.php:1350 msgid "Tags" msgstr "Etiketter" #: wp-cache.php:1351 msgid "Category" msgstr "Kategori" #: wp-cache.php:1352 msgid "Feeds" msgstr "Flöden" #: wp-cache.php:1353 msgid "Search Pages" msgstr "Söksidor" #: wp-cache.php:1355 #: wp-cache.php:1483 msgid "Save" msgstr "Spara" #: wp-cache.php:1372 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Lägg till strängar (inte ett filnamn) som tvingar en sida att inte vara cachad. Som exempel, om dina URL:er innehåller år och du vill inte cacha föregående års inlägg, räcker det med att specifiera året, e.x. ’/2004/’. WP-Cache kommer kontrollera om den strängen är en del URI:n och isåfall, inte cacha den sidan." #: wp-cache.php:1378 msgid "Save Strings" msgstr "Spara strängar" #: wp-cache.php:1394 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Lägg till de filnamn som kan bli cachade, även om de matchar en av de avvisade strängarna angivna ovan." #: wp-cache.php:1400 msgid "Save Files" msgstr "Spara filer" #: wp-cache.php:1445 msgid "Currently logging to: " msgstr "Loggar just nu till:" #: wp-cache.php:1455 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Rätta till problem med tillägget genom att felsöka det här. Det kan skicka dig felsöknings e-mail eller logga dom till en fil i din cache katalog." #: wp-cache.php:1456 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Logga till en fil är lättare men stöter på problemet att rensas cachen så rensas logg-filen." #: wp-cache.php:1460 msgid "Debugging" msgstr "Felsökning" #: wp-cache.php:1461 msgid "Logging Type" msgstr "Loggnings sätt" #: wp-cache.php:1461 msgid "Email" msgstr "E-mail" #: wp-cache.php:1462 msgid "file" msgstr "fil" #: wp-cache.php:1463 msgid "IP Address" msgstr "IP Adress" #: wp-cache.php:1463 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(logga bara förfrågningar från den här IP adressen. Din IP är %s)" #: wp-cache.php:1464 msgid "Log level" msgstr "Logg nivå" #: wp-cache.php:1470 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = mindre, 5 = mer, kan orsaka tyngre server belastning.) " #: wp-cache.php:1473 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "I väldigt ovanliga fall kan två problem dyka upp på vissa bloggar:
    1. Framsidan kan börja laddas ner som en zip fil.
    2. Fel sida blir ibland cachad som framsidan om din blogg använder en statisk framsida och permalänk strukturen är /%category%/%postname%/.
    " #: wp-cache.php:1474 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "Jag är 99% säker på att det inte är några buggar i WP Super Cache och dom händer bara i undantagsfall men du kan köra en enkel kontroll var 5:e minut för att kontrollera att din sida är ok om du är orolig. Du kommer få ett e-mail om det är några problem." #: wp-cache.php:1476 msgid "Check front page every 5 minutes." msgstr "Kontrollera framsidan var 5:e minut." #: wp-cache.php:1477 msgid "Front page text" msgstr "Framsides text" #: wp-cache.php:1477 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Text att leta efter på din framsida. Om den här texten fattas kommer cachen att rensas. Lämna tomt för att inaktivera." #: wp-cache.php:1478 msgid "Clear cache on error." msgstr "Rensa cache vid fel." #: wp-cache.php:1479 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Skicka e-mail till blogg administratören när kontroller görs. (användbart för testning)" #: wp-cache.php:1493 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Fel: GZIP komprimering är aktiverad, inaktivera det om du vill aktivera wp-cache." #: wp-cache.php:1540 #: wp-cache.php:1702 msgid "Warning" msgstr "Varning" #: wp-cache.php:1540 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "GZIP-komprimering är aktiverat i WordPress, wp-cache kommer bli kringgått tills du har inaktiverat gzip-komprimering." #: wp-cache.php:1598 #: wp-cache.php:1603 #: wp-cache.php:1635 #: wp-cache.php:1640 #: wp-cache.php:1646 msgid "Error" msgstr "Fel" #: wp-cache.php:1598 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Din cache katalog ($cache_path) fanns inte och kunde inte skapas av web servern. Kontrollera %s rättigheter." #: wp-cache.php:1603 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Din cache katalog (%1$s) eller %2$s måste vara skrivbar för att det här tillägget ska fungera. Dubbel-kontrollera det." #: wp-cache.php:1635 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Din WP-Cache konfigurations fil (%s) är för gammal och inte skrivbar av web servern. Var vänlig radera den och uppdatera den här sidan." #: wp-cache.php:1640 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Konfigurations fil saknas och %1$s katalogen (%2$s) är inte skrivbar av web servern. Kontrollera dess rättigheter." #: wp-cache.php:1646 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Exempel WP-Cache konfigurations fil (%s) finns inte. Kontrollera din installation." #: wp-cache.php:1702 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php finns inte eller kan inte uppdateras." #: wp-cache.php:1703 msgid "1. If it already exists please delete the file first." msgstr "1. Om den redan finns var vänlig radera filen först." #: wp-cache.php:1704 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Gör %1$s skrivbar genom att använda chmod kommandot genom din ftp eller server programvara. (chmod 777 %1$s) och uppdatera den här sidan. Det här är endast en tillfällig åtgärd och du måste göra den read only igen efteråt. (Ändra 777 till 755 i det föregående kommandot)" #: wp-cache.php:1705 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Ladda om den här sidan för att uppdatera %s/advanced-cache.php" #: wp-cache.php:1706 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Om det inte fungerar, kontrollera att filen %s/advanced-cache.php inte finns:" #: wp-cache.php:1707 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Öppna %1$s$wp_cache_file i en text redigerare.
  • 2. Ändra texten CACHEHOME till %2$s
  • 3. Spara filen och kopiera den till %3$s och ladda om den här sidan.
    • " #: wp-cache.php:1730 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    WP_CACHE-konstanten är sat till falskt

    WP_CACHE-konstanten används av WordPress för att ladda koden som presenteras cachade sidor. Tyvärr är den satt till falskt. Var vänlig redigera din wp-config.php och lägg till eller redigera följande rad ovanför det sista require_once-kommandot:

    define('WP_CACHE', true);

    " #: wp-cache.php:1732 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Fel: WP_CACHE är inte aktiverad i din wp-config.php fil och jag kunde inte ändra den." #: wp-cache.php:1733 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Redigera %s och lägg till följande rad:
    define('WP_CACHE', true);
    Annars kommer inte WP-Cache köras av WordPresskärnan." #: wp-cache.php:1737 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    WP_CACHE konstant tillagd i wp-config.php

    Om du fortsätter att se det här varningsmeddelandetvar vänlig läs punkt 5 i FAQ. WP_CACHE raden måste flyttas upp." #: wp-cache.php:1759 msgid "Cache Contents" msgstr "Cache innehåll" #: wp-cache.php:1762 msgid "Object cache in use. No cache listing available." msgstr "Objektcache används. Ingen cachelistning möjlig." #: wp-cache.php:1786 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Raderar supercache filen: %s
    " #: wp-cache.php:1803 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Raderar wp-cache filen: %s
    " #: wp-cache.php:1868 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Cachestatistik genereras inte automatiskt. Du måste klicka på länken nedan för att generera statistiken på den här sidan." #: wp-cache.php:1869 msgid "Regenerate cache stats" msgstr "Regenerera cachestatistik" #: wp-cache.php:1871 #, php-format msgid "Cache stats last generated: %s minutes ago." msgstr "Cachestatistik genererades senast för %s minuter sedan." #: wp-cache.php:1877 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:1878 #: wp-cache.php:1894 #, php-format msgid "%s Cached Pages" msgstr "%s Cachade sidor" #: wp-cache.php:1879 #: wp-cache.php:1899 #, php-format msgid "%s Expired Pages" msgstr "%s Utgågna sidor" #: wp-cache.php:1893 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1904 msgid "Fresh WP-Cached Files" msgstr "Färska WP-Cachade filer" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "URI" msgstr "URI" #: wp-cache.php:1905 #: wp-cache.php:1921 msgid "Key" msgstr "Nyckel" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Age" msgstr "Ålder" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Delete" msgstr "Radera" #: wp-cache.php:1920 msgid "Stale WP-Cached Files" msgstr "Gamla WP-Cachade filer" #: wp-cache.php:1936 msgid "Fresh Super Cached Files" msgstr "Färska Super Cachade filer" #: wp-cache.php:1952 msgid "Stale Super Cached Files" msgstr "Gamla Super Cachade filer" #: wp-cache.php:1968 msgid "Hide file list" msgstr "Dölj fil-lista" #: wp-cache.php:1970 msgid "Too many cached files, no listing possible." msgstr "För många cachade filer, listning ej möjlig." #: wp-cache.php:1972 msgid "List all cached files" msgstr "Lista alla cachade filer" #: wp-cache.php:1978 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Garbage Collection
    Senaste GC gjordes %s minuter sedan
    " #: wp-cache.php:1979 #, php-format msgid "Next GC in %s minutes" msgstr "Nästa GC om %s minuter" #: wp-cache.php:1982 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Utgångna filer är filer äldre än %s sekunder. Dom används fortfarande av tillägget och raderas periodvis." #: wp-cache.php:1993 msgid "Delete Expired" msgstr "Radera utgångna" #: wp-cache.php:1999 #: wp-cache.php:2011 #: wp-cache.php:2174 msgid "Delete Cache" msgstr "Radera Cache" #: wp-cache.php:2011 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Radera Super Cache cachade filer (öppnas i nytt fönster)" #: wp-cache.php:2150 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s är Digg säker tack vare cachning av %2$s" #: wp-cache.php:2183 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache måste ställas in. Gå till administrations sidan för att aktivera och konfigurera tillägget." #: wp-cache.php:2189 msgid "Settings" msgstr "Inställningar" #: wp-cache.php:2199 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache är inaktiverat. Var vänlig gå till tilläggets administrations sida för att aktivera cachning." #: wp-cache.php:2218 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Fram sidan är gzippad! Var vänlig rensa cachen!" #: wp-cache.php:2218 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Var vänlig gå till %s för att rensa cachen eftersom framsidan av din sida nu laddas ner!" #: wp-cache.php:2221 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Framsidan är gzippad! Cachen rensad!" #: wp-cache.php:2221 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Cachen till din blogg har rensats för framsidan av din sida laddas nu ner. Var vänlig gå till %s för att bekräfta att cachen har rensats." #: wp-cache.php:2228 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Framsidan är inte rätt! Var vänlig rensa cachen!" #: wp-cache.php:2228 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Var vänlig gå till %1$s för att rensa cachen eftersom framsidan på din sida inte är rätt och saknar texten, \"%2$s\"!" #: wp-cache.php:2231 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Framsidan är inte rätt! Cachen är rensad!" #: wp-cache.php:2231 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Cachen till din blogg har rensats för framsidan på din sida saknar texten \"%2$s\". Var vänlig gå till %1$s för att bekräfta att cachen har rensats." #: wp-cache.php:2236 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Framsida kontrollerad!" #: wp-cache.php:2236 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache har kontrollerat framsidan på din blogg. Var vänlig gå till %s om du vill inaktivera detta." #: wp-cache.php:2279 msgid "Cannot update .htaccess" msgstr "Kan inte uppdatera .htaccess" #: wp-cache.php:2279 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Filen %s.htaccess kan inte ändras av webservern. Var vänlig rätta till detta genom att använda chmod kommandot eller din ftp klient." #: wp-cache.php:2279 msgid "Refresh this page when the file permissions have been modified." msgstr "Uppdatera den här sidan när filrättigheterna har ändrats." #: wp-cache.php:2279 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Alternativt, du kan redigera din %s.htaccess fil manuellt och lägga till följande kod (före alla WordPress regler):" #: wp-cache.php:2283 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "För att visa statiska html filer måste din server ha korrekta mod_rewrite regler tillagda i en fil som heter %s.htaccess" #: wp-cache.php:2284 msgid "You can edit the file yourself add the following rules." msgstr "Du kan redigera filen själv och lägga till följande regler." #: wp-cache.php:2285 msgid " Make sure they appear before any existing WordPress rules. " msgstr "Kontrollera att de syns före alla existerande WordPress regler." #: wp-cache.php:2293 msgid "Update Mod_Rewrite Rules" msgstr "Uppdatera Mod_Rewrite Reglerna" #: wp-cache.php:2389 #, php-format msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Cacheförladdning startad" #: wp-cache.php:2391 #, php-format msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Uppdaterar inlägg från %2$d till %3$d" #: wp-cache.php:2402 #, php-format msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d inlägg uppdaterade" #: wp-cache.php:2402 msgid "Refreshed the following posts:" msgstr "Uppdaterade följande inlägg:" #: wp-cache.php:2411 #, php-format msgid "Scheduling next preload refresh in %d minutes." msgstr "Schemalägger nästa uppdatering av förladdning om %d minuter." #: wp-cache.php:2421 #, php-format msgid "[%s] Cache Preload Completed" msgstr "[%s] cacheförladdning färdig." #: wp-cache.php:2421 msgid "Cleaning up old supercache files." msgstr "Rensar upp gamla supercachefiler." #: wp-cache.php:2462 #, php-format msgid "[%s] Preload may have stalled." msgstr "[%s] Förladdning kan ha hängt sig." #: wp-cache.php:2462 #, php-format msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Förladdning har startats om.\n" "%s" #~ msgid "WP Super Cache Manager" #~ msgstr "WP Super Cache Manager" #~ msgid "Why your configuration may not be changed" #~ msgstr "Varför din konfiguration inte kan ändras" #~ msgid "Why" #~ msgstr "Varför" #~ msgid "ON" #~ msgstr "PÅ" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "WP Cache och Super Cache aktiverat" #~ msgid "HALF ON" #~ msgstr "HALV PÅ" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Super Cache inaktiverad, endast ärvd WP-Cache cachning." #~ msgid "OFF" #~ msgstr "AV" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "WP Cache och Super Cache inaktiverat" #~ msgid "Don’t cache pages for logged in users." #~ msgstr "Cacha inte sidor för inloggade användare." #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "Återbygg cache. Visa en supercachad fil till anonyma användare medan en " #~ "ny fil genereras. Rekommenderas för väldigt upptagna hemsidor " #~ "med många kommentarer. Gör \"direkt cachade sidor\" och \"Lockdown mode\" " #~ "förlegade." #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "Visa de nyast cachade sidorna (kan vara tungt att köra på belastade " #~ "sidor, använd med försiktighet.)" #~ msgid "" #~ "Uninstall using the uninstall script to remove files and directories created by the " #~ "plugin. (Please see readme." #~ "txt for instructions on uninstalling this script.)" #~ msgstr "" #~ "Avinstallera genom att använda avinstallations skriptet för att ta bort filer och kataloger " #~ "skapade av tillägget. (Var vänlig läs readme.txt för instruktioner om hur du avinstallerar det " #~ "här skriptet.)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s gör verkligen din blogg snabbare. Gör den ännu snabbare * " #~ "genom att köpa mig ett Amazon presentkort! Ställ ut " #~ "det till \"%3$s\" på vilken summa du vill. Varje penny hjälper!" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "Om Amazon inte är din grej, finns det även PayPal. Klicka på \"Donate\" " #~ "knappen nedan eller ta en snabb titt på min önskelista." #~ msgid "Thanks in advance!" #~ msgstr "Tack på förhand!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Ok, det kommer inte gå ännu snabbare, men du kommer göra det här " #~ "tilläggets skapare väldigt glad!" #~ msgid "Don’t show me this again." #~ msgstr "Visa mig inte det här igen." #~ msgid "Hide" #~ msgstr "Dölj" #~ msgid "" #~ "He blogs at %1$s, posts photos at %2$s and wishes he " #~ "had more time to read and relax." #~ msgstr "" #~ "Han bloggar på %1$s, postar bilder på %2$s och önskar han hade mer tid att läsa och koppla av." #~ msgid "Super Cache Compression" #~ msgstr "Super Cache komprimering" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "Komprimering är aktiverat som standard i HALV PÅ läge." #~ msgid "Super Cache compression is now disabled." #~ msgstr "Super Cache komprimering är nu inaktiverat." #~ msgid "Super Cache compression is now enabled." #~ msgstr "Super Cache komprimering är nu aktiverat." #~ msgid "Update Compression" #~ msgstr "Updatera komprimering" #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "Du måste redigera filen själv och lägga till följande regler." #~ msgid "Debug Settings" #~ msgstr "Felsöknings inställningar" languages/wp-super-cache-es_ES.mo000066600000132132152133035240012672 0ustar00=<,.M[jz` ~?w3*7Z5K =[)wZU&i:ncK  =!3F!z!! !!"/"3" ###,#!>#c`#k$0%F%I%?&@&s'{''( !(+( 2(?(5N(((3W)1))e*{*:+B+K+,+(,H,,?,?-F-N-NT-- -n-$4.Y._.~q../00 00g011+D1p1hx11111 233bG44&56k7b9f9W|9 9 9 9 9b:c:]y:::;#;;$;";<!/<Q<&f<<<<U<<T<K=Uk=p=U2>>`/?0? ???< @H@7]@j@AAY=AA A AA AA9SBB B:BBB CC3C(0D'YDDqDDE$EEkFGGEHT]J~J1KPKTK*LLMMN +N9N!PN rNNNjNb+OOlXPPPPPPQ*(QSQ)WQQbQ[Q VR7aRrRM S8ZSSLT/TUVwW2XXEYeY/ZZ*Z/[.D[3s[[[[[[P]S ^O^^^___ F`T`@`A3aua8)b@bb_b2c%6cG\dade fqflngg/hhhZjjlll5mA>m$mmmm n5nC5o*yo oo.ootq#r*reslsTtttu'uuuu uu>vMvgv6,o,'ɍ: G MYYbWŎ'jEn1a;A,Kn;ؒ&)ÓlZaqPdŕYݕ#7[yW/p.+ϗ јJbN~0NƟ '@#d{ȣ#ߣ"=mSG|7̦ Ҧߦ". N0Z+ DRIө yȫAB }1!EK[;P 4@IQ 5)Tup^Jq'`&!ez01Zl- 2QyAC98mb+ nFDr=YxNH@$~gsk]|d:ijo{h,3? _GEK}.B SLV\%6X7c( f/["<ORWvI4w>;aMPU#t* Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%1$s really makes your blog go faster. Make it go faster* by buying me an Amazon gift card! Make it out to "%3$s" for whatever amount you want. Every penny helps!%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Only half-on caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.phpNo Adverts for Friends plugin is %s

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ add this line: (do it twice, once for each section)AdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesBad Behaviour not found. Please check your install.Bad Behaviour support is %sCache ContentsCache PluginsCache rebuild. Serve a supercache file to anonymous users while a new file is being generated. Recommended for very busy websites with lots of comments. Makes "directly cached pages" and "Lockdown mode" obsolete.Cached %s seconds agoCached pages since %1$s : %2$sCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. Aim to have less than 500 cached files if possible.Clear all cache files when a post or page is published. (This may significantly slow down saving of posts.)Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compression is disabled by default because some hosts have problems with compressed files. Switching this on and off clears the cache.Compression is enabled by default when in HALF ON mode.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently logging to: Debug SettingsDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Don’t cache pages for logged in users.Don’t show me this again.Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by Wordpress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnabledErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "Android|2.0\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textGZIP compression is enabled in Wordpress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.HALF ONHe blogs at %1$s, posts photos at %2$s and wishes he had more time to read and relax.HideHide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf Amazon isn’t your thing, there’s also PayPal. Click the "Donate" button below or take a quick peek at my wishlist.If expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use half-on mode.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyList all cached filesList the newest cached pages (may be expensive to run on busy sites, use with caution.)Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Missing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to half-on mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Newest Cached Pages:Next GC in %s minutesNote:OFFONOk, it won’t go any faster but you’ll make this plugin author very happy!PagesPlease create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Read Only Mode. Configuration cannot be changed.Readonly:Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Rejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave FilesSave StringsSave UA StringsSearch PagesSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the plugin to half on mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Super Cache CompressionSuper Cache Disabled, only legacy WP-Cache caching.Super Cache compression is now disabled.Super Cache compression is now enabled.TagsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.Thanks in advance!The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in half-on mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessTrailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall using the uninstall script to remove files and directories created by the plugin. (Please see readme.txt for instructions on uninstalling this script.)Update CompressionUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate StatusView Mod_Rewrite RulesWP Cache and Super Cache disabledWP Cache and Super Cache enabledWP Super Cache ManagerWP Super Cache StatusWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! PHP Safe Mode Enabled!Warning! Your hostname "%s" resolves to %sWhyWhy your configuration may not be changedWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must edit the file yourself add the following rules.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache!disabledenabledfilesecondsProject-Id-Version: WP Super Cache 0.9.7 Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2009-11-13 10:27+0000 PO-Revision-Date: Last-Translator: Omi Language-Team: Omi MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=n != 1; X-Poedit-Language: Spanish X-Poedit-Country: Spain X-Poedit-SourceCharset: utf-8 Asegúrese de que se muestran antes de cualquier regla de WordPress existente. %1$s está orgullosamente a prueba de Digg gracias a la caché que proporciona %2$s%1$s es mantenido y desarrollado por %2$s con la colaboración de muchos otros.%1$s realmente consigue que su blog sea más veloz. Puede acelerarlo todavía más* comprándome una tarjeta regalo de Amazon! Hágalo para "%3$s" por la cantidad que quiera. Cada céntimo ayuda!%s Páginas en caché%s Páginas caducadas%s es editable. Como es un riesgo para la seguridad, asegúrese de dejarlo como solo lectura después de que se haya generado la página.%s eliminado!El fichero %s.htaccess ha sido actualizado con las reglas mod_rewrite necesarias. Por favor, verifique que son correctas. Deberían parecerse a lo siguiente:%s/advanced-cache.php no existe o no puede ser actualizado.(1 = menor, 5 = mayor, puede provocar una gran carga al servidor)(Sólo se soporta caché "a medias", se desactiva la compresión y requiere instalar Bad Behavior en "%s/plugins/bad-behavior/") (puede no ser siempre preciso en sitios muy concurridos)(depurar sólo peticiones desde esta dirección IP. Su IP es %s)(Necesita también friendsadverts.php) 1. Si existe, por favor, borre primero el fichero.2. Proporcione permisos de escritura a %1$s utilizando el comando CHMOD de su cliente de FTP. (chmod 777 %1$s) y recargue esta página. Esto sólo es una medida temporal: terminado el proceso deberá volver a dejarlo como de sólo lectura (cambiar de 777 a 755 en el comando anterior)3. Recargue esta página para actualizar %s/advanced-cache.phpEl plugin No Adverts for Friends está %s

    Constante WP_CACHE añadida al fichero wp-config.php

    Si sigue viendo este mensaje de aviso, revise por favor el punto 5 del FAQ. La línea WP_CACHE debe subirse sobre otras líneas.

  • 1. Abra el fichero %1$s$wp_cache_file en un editor de texto.
  • 2. Cambie el texto CACHEHOME por %2$s
  • 3. Guarde los cambios y salve el fichero en %3$s; luego recargue esta página.
    • Error: WP_CACHE no está activo en su fichero wp-config.php y no puedo modificarlo.Recolección de Basura
    La última "RdB" se hizo hace %s minutos
    La forma más sencilla es cambiar temporalmente los permisos utilizando el comando CHMOD de su cliente FTP. Asegúrese de que puede ser globalmente editado y todo debería ir bien.Nombres de archivos aceptados y URIs rechazadasAñadir página directa:Añada aquí las cadenas (no el nombre del fichero) que forzará que una página no entre en caché. Por ejemplo, si su URL incluye un año y no quiere que los artículos del último año entren en caché, bastará con especificar el año, por ejemplo:’/2004/’. WP-Cache buscará si esa cadena forma parte de la URI para, de ser así, no alojar dicha página en la caché.Añada aquí aquellos nombres de archivos que pueden ser almacenados en caché, incluso si coinciden con alguna de las subcadenas especificadas arriba.Añadir las reglas manualmente. Edite el fichero %s.htaccess y localice el bloque de código encerrado entre las líneas # BEGIN WPSuperCache y # END WPSuperCache. Hay dos secciones que parecen muy similares. Justo debajo de la línea %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ añada esta otra línea: (deberá hacerlo dos veces, una para cada sección)AvanzadoEdadAlternativamente, puede editar manualmente su fichero %s.htaccess y añadir el siguiente código (antes de cualquier regla de WordPress):ArchivosNo se encuentra Bad Behaviour. Por favor, revise su instalación.El soporte de Bad Behaviour está %sContenidos en cachéCaché de Plugins Reconstruir caché. Sirve un fichero supercaché a los usuarios anónimos mientras que el nuevo está siendo generado. Recomendado para sitios muy activos con muchos comentarios. Hace que "páginas directamente en caché" y "modo Confinamiento" queden obsoletos.En caché desde hace %s segundosPáginas en caché desde %1$s : %2$sNo puedo continuar...solucione los problemas descritos y reintente.No se pudo actualizar el fichero .htaccessCategoríasCambiar caducidadComprobar la página principal cada 5 minutos.Comprobar y eliminar archivos caducados es costoso, pero dejarlos ahí lo es más. En un sitio con mucho tráfico debería establecer el tiempo de caducidad a 300 segundos. Experimente con diferentes valores y visite regularmente esta página para comprobar cuantos ficheros caducados aparecen a diferentes horas del día. El objetivo está en tener menos de 500 archivos en caché siempre que sea posible.Limpiar la caché cuando se publique un artículo o página (esto puede ralentizar bastante el proceso de guardado).Limpiar la caché en caso de error.Bloquear ficheros toscamente. Normalmente no necesitará esto, pero podría serle de ayuda si su servidor tiene poca potencia. ¡Aviso, es muy poco probable, pero podría ocasionar que su servidor se bloquease!La moderación de comentarios está activada. Su comentario podría tardar cierto tiempo en aparecer.La compresión está desactivada por defecto debido a que algunos servidores tienen problemas con los archivos comprimidos. Activar o desactivar esta opción limpiará la caché.La compresión está activa por defecto cuando se ejecuta el modo A MEDIAS.El archivo de configuración ha cambiado, algunos valores pueden ser incorrectos. Recargue de nuevo la página desde el menú "Opciones" para reestablecerlos.Falta el archivo de configuración y %1$s el directorio (%2$s) no puede editarse por el servidor. Compruebe sus permisos.Actualmente registrando datos (log) en:Depurar opcionesModo depuraciónBorrarBorrar cachéBorrar caducadosBorrar archivos de Super Caché (se abrirá una nueva ventana)Archivo de caché borradoEliminar las reglas mod_rewrite del plugin en %s.htaccess que estén entre # BEGIN WPSuperCache y # END WPSuperCache y permitir que el plugin vuelva a generarlas recargando esta página.Borrando archivo supercache: %s
    Borrando archivo wp-cache: %s
    Atención desarrolladores: hagan su plugin compatible con el modo "confinamiento" comprobando la constante "WPLOCKDOWN". El siguiente código hará que su plugin respete la configuración WPLOCKDOWN.Archivos directos en cachéLos archivos directos a caché son archivos creados directamente fuera de %s donde reside su blog. Esta opción sólo es útil si esta experimentando problemas de mucho tráfico en un artículo o página concreta desde sitios del estilo a Digg o Menéame.DesactivarDesactivadoNo almacenar en caché los siguientes tipos de páginas. Revise el apartado Conditional Tags de la documentación para acceder a un completo argumento sobre cada uno de los tipos.No hacer caché de páginas para usuarios autentificados.No mostrar esto nuevamente.Edite el fichero %s y añada la siguiente línea:
    define('WP_CACHE', true);
    En caso contrario, WP-Cache no será ejecutado por el núcleo de Wordpress.EmailEnviar un email al administrador del blog cuando se hagan comprobaciones (útil para pruebas)ActivarActivadoErrorError: la compresión GZIP está activada; debe desactivarla si quiere activar wp-cache.Página directa existenteTiempo de caducidad:Los ficheros caducados son aquellos superiores a %s segundos. Todavía están en uso por el plugin y son borrados periódicamente.Tiempo de caducidad y Recogida de basuraFeedsArreglar configuraciónSolucione problemas con el plugin depurándolos aquí. Podrá recibir emails de depuración o guardar los registros en un fichero de su directorio caché.Para un mejor rendimiento debería activar "Soporte para dispositivos móviles" o borrar las reglas mobile rewrite rules de su archivo .htaccess. Localice las 2 líneas con el texto "Android|2.0\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone" y elimínelas.Por ejemplo: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Archivos recientes en Super CachéArchivos recientes en cachéPágina principalTexto página principalLa compresión GZIP está activa en WordPress, wp-cache se omitirá hasta que desactive dicha compresión.Recolección de basuraReglas de codificación Gzip creadas en %s.htaccessA MEDIASEl escribe en %1$s, publica fotos en %2$s y desearía tener más tiempo para leer y relajarse.OcultarOcultar lista de archivosHomeEstoy seguro al 99% de que no son fallos de WP Super Cache y de que tan sólo ocurren en casos muy excepcionales, pero si esto le preocupa puede ejecutar un sencillo test cada 5 minutos para verificar que su sitio esta bien. Recibirá un correo en caso de problemas.Dirección IPSi Amazon no es su sitio preferido, también puede ayudarme a través de PayPal. Pinche sobre el botón "Donate" que está un poco más abajo o eche un rápido vistazo a mi lista de deseos.Si el tiempo de caducidad es mayor a 1800 segundos (media hora), la recolección de basura se hará cada 10 minutos; en otro caso, se hará 10 segundos después del tiempo de caducidad indicado arriba.Si eso no funciona, asegúrese de que el archivo %s/advanced-cache.php no existe:Si desinstala este plugin asegúrese de que el directorio %s es editable por el servidor web para que los archivos advanced-cache.php y cache-config.php puedan eliminarse automáticamente (asegurarse de que esos archivos son editables es también una buena idea!)En algún caso bastante excepcional pueden ocurrir dos problemas en algunos blogs:
    1. La página principal puede empezar a descargarse como un archivo zip.
    2. Ocasionalmente, una página incorrecta se almacena en caché como si fuese la página principal si su blog utiliza una página principal estática y la estructura de enlaces permanentes es /%categoría%/%artículo%/.
    Parece que mod_rewrite no está instalado. Algunas veces esto no es 100% preciso, especialmente si no está utilizando Apache. Por favor, compruebe que el módulo mod_rewrite se encuentra cargado. Es necesario para servir los ficheros estáticos del Super Cache. No obstante, debería ser capaz de poder usar el modo de caché "a medias".Parece que su blog tiene URLs que terminan con "/". Desafortunadamente, desde que instaló este plugin, se ha encontrado un fallo de contenido duplicado para las URLs que no terminan en "/" y de aquellas que sí lo hacen y que provoca que no se llame a la URL correcta. Para resolverlo, deberá editar su fichero .htaccess y añadir las dos siguientes reglas a los dos grupos de Super Caché:ClaveMostrar archivos en cachéListar las nuevas páginas en caché (puede ser costoso de ejecutar en sitios muy activos, utilizar con precaución).ConfinamientoModo Confinamiento:Nivel de registroTipo de registroGuardar los registros en un fichero es más sencillo, pero limpiar la caché provocará que se borren dichos archivos de registro.Hace WordPress VelozDeje el cuadro en blanco para eliminarla de la lista de páginas directas en caché y borrar así el fichero de caché.Módulos de Apache AusentesSoporte para dispositivos móviles.Reglas Mobile rewrite detectadasEl soporte para móviles requiere de reglas extra en su archivo .htaccess. También puede seleccionar el modo "A medias". Aquí se muestran sus opciones (en orden de dificultad):Reglas Mod Rewrite¡Las reglas Mod Rewrite no pueden actualizarse!¡Las reglas Mod Rewrite deben actualizarse!¡Las reglas Mod Rewrite se han actualizado!¡Mod rewrite puede no estar instalado!Nuevas páginas en caché:La siguiente "RdB" se hará en %s minutosNota:DESACTIVADOACTIVADOOk, no conseguirá que vaya más rápido, ¡pero hará muy feliz al autor de este plugin!PáginasPor favor, cree %s /wp-cache-config.php desde wp-super-cache/wp-cache-config-sample.phpPor favor, dígale hola también en %s!Por favor, revise la entrada nº 16 de la sección Troubleshooting del fichero readme.txtPor favor, visite %1$s para limpiar la caché, ya que la página principal de su sitio no es correcta y falta el texto , "%2$s"!Por favor, visite %s para limpiar la caché ya que la página principal de su sitio esta ahora descargándose!Prepare su servidor para un pico de tráfico no esperado activando el modo "confinamiento". Cuando está activo, los nuevos comentarios de un artículo no provocarán que se refresquen los archivos estáticos de la caché.¡Dígale al mundo que su servidor está a prueba de Digg! (pone un mensaje en el pie de su blog)Modo de Solo Lectura. La configuración no puede cambiarse.Sólo lectura:Recargue esta página cuando los permisos hayan sido modificados.Recargue esta página después de que haya actualizado su fichero .htaccessAgentes de usuario rechazadosRequerido para servir archivos de supercache correctamente.Requerido para establecer la información en las páginas de supercache. Los usuarios de IE7 verán páginas antiguas sin este módulo.Volver a la configuración por defectoLas reglas deben añadirse también a %s:El archivo de ejemplo de configuración WP-Cache (%s) no existe. Verifique su instalación.GrabarGrabar archivosGrabar cadenasGrabar cadenas User AgentPáginas de búsquedaEstablece la fecha de caducidad en las páginas de supercache. Los visitantes puede que no vean las nuevas páginas al refrescar o que no puedan dejar comentarios sin este modulo.Establecer este plugin en el modo "A medias" y activar el soporte para móviles.ConfiguracionesArtículos individualesLo siento, mi blog está en modo confinamiento. Las actualizaciones aparecerán en breve.Archivos anticuados en Super CachéArchivos anticuados en cachéCadenas en la cabecera HTTP ’User Agent’ que previenen que WP-Cache almacene peticiones de robots de búsqueda. Tenga en cuenta que los archivos de Super Caché se siguen enviando a esos agentes si ya existen.Compresión Super CachéSuper Cache desactivado, sólo caché WP-Cache.La Compresión Super Caché se ha desactivado.La Compresión Super Caché se ha activado.Etiquetas (tags)Texto a buscar en su página principal. Si se detecta que falta este texto, la caché se limpiará. Déjelo en blanco para desactivar esta opciónGracias por actualizar.¡Gracias por adelantado!El archivo de configuración de WP Super Cache es %s/wp-cache-config.php y no puede modificarse. Dicho archivo debe tener permisos de escritura para que pueda ser modificado.Se ha limpiado la caché de su blog debido a que la página principal de su sitio carece del texto "%2$s". Por favor, visite %1$s para comprobar que la caché se ha limpiado correctamente.La caché de su blog se ha limpiado ya que la página principal de su sitio se está descargando. Por favor, visite %s para comprobar que la caché se ha limpiado correctamente.El fichero %s.htaccess no puede ser modificado por el servidor. Por favor, resuélvalo mediante el comando CHMOD de su cliente de FTP.Faltan los siguientes módulos de Apache. El plugin trabajará en modo "A Medias" sin ellos. En el modo Supercache sus visitantes podrían ver páginas corruptas o contenido desactualizado.Las reglas mod_rewrite han cambiado desde que instaló este plugin. Desafortunadamente, deberá eliminar las antiguas reglas de supercache antes de que puedan instalarse las nuevas. Recargue esta página después de que haya editado su fichero .htaccess file. Si desea realizar una actualización manual, cambie la siguiente línea: %1$s para que quede como la siguiente: %2$s Los únicos cambios son que"HTTP_COOKIE" pasa a ser "HTTP:Cookie" y "wordpressuser" se convierte en "wordpress". Este es un cambio de WordPress 2.5 aunque sigue siendo compatible con versiones anteriores (si tiene valor para usarlas)Esto no tendrá repercusión sobre los usuarios normales pero los usuarios de móviles verán las páginas sin usar la caché.Para servir archivos html estáticos, su servidor debe tener las reglas mod_rewrite correctas añadidas a un fichero llamado %s.htaccessComprobación de "trailing slash" (barra al final de una dirección) requeridaURIDesafortunadamente WordPress no puede localizar el fichero wp-cron.php. Este script es necesario para el funcionamiento de la función de recolección de basura que realiza este, plugin así como para la publicación diferida de WordPress y otras actividades críticas.Desafortunadamente las reglas "rewrite" no pueden actualizarse de forma automática cuando se ejecuta WordPress MU. Por favir, abra su archivo .htaccess y añada las siguientes reglas mod_rewrite por debajo de otras reglas existentes en dicho fichero.Desinstale utilizando el script de desinstalación para eliminar los archivos y directorios creados por el plugin. (Por favor, eche un vistazo al archivo readme.txt para obtener instrucciones sobre como desinstalar este script)Actualizar compresiónActualizar páginas directasActualizar reglas Mod_RewriteActualizar EstadoVer reglas Mod_RewriteWP Cache y Super Cache desactivadosWP Cache y Super Cache activosGestión de WP Super CacheEstado WP Super CacheWP Super Cache ha comprobado la página principal de su blog. Por favor, visite %s si quiere desactivar esto.WP Super Cache está desactivado. Por favor, vaya a la página de administración del plugin para activar la caché.Se han detectado reglas mod rewrite de WP Super Cache en su fichero %s.htaccess.
    Pinche sobre el siguiente enlace para ver las líneas añadidas a dicho fichero. Si ha actualizado el plugin, asegúrese de que dichas reglas coinciden.WP Super Cache debe configurarse. Vaya a la página de administración para activar y configurar el plugin.WP-CacheWP-Super-CacheAviso¡Atención!¡Atención, %s es editable!¡Atención, modo PHP Safe activo!¡Atención! Su hostname "%s" resuelve como %s¿Por qué?¿Por qué no puede cambiarse su configuración?Se ha detectado WordPress MUWordPress está en modo confinamiento. Los ficheros estáticos de Super Caché no se borrarán cuando se hagan nuevos comentarios.WordPress no está en modo confinamiento. Los nuevos comentarios refrescarán los ficheros estáticos de Super Caché con normalidad.Editable:Puede editar manualmente el archivo y añadir las siguientes reglas.Puede ver dónde van las reglas y examinar todas ellas pinchando sobre el enlace "Ver reglas mod_rewrite" que se muestra abajo.Podría experimentar problemas ejecutando este plugin con el modo PHP SAFE activo.Deberá editar manualmente el fichero para añadir las siguientes reglas.Debe tener marcadores BEGIN y END dentro de su fichero %s.htaccess para que funcione la actualización automática. Se parecen a lo siguiente y rodean a las reglas mod_rewrite principales de WordPress:Debe hacer que %s pueda editarse para activar esta opción. Como es un riesgo para la seguridad, asegúrese de volverlo a dejar como solo lectura después de que se haya generado la página.Usted, o un administrador, debería ser capaz de hacerlo funcionar cambiando el propietario del grupo de los scripts para que coincidan con el del usuario web del servidor. El propietario del grupo del directorio %s/cache/ también deberá cambiarse. Revise la página sobre safe mode en el manual para obtener más información.Usted, o un administrador, deberán desactivar esto. Revise la página sobre safe mode en el manual para obtener más información. Desafortunadamente, esto no puede ser desactivado desde un fichero .htaccess sino que debe hacerse desde el fichero de configuración php.iniDebería cambiar los permisos de %s y hacerlos más restrictivos. Utilice su cliente de FTP o el siguiente comando para resolver cosas:Su fichero %s.htaccess no puede ser editado por el servidor y debe actualizarse con las reglas mod_rewrite necesarias. Las nuevas reglas van encima de las reglas normales de WordPress, como se muestra en el siguiente código:El archivo de configuración de WP-Cache (%s) está desactualizado y no puede editarse por el servidor. Por favor, bórrelo y recargue esta página.Si directorio caché ($cache_path) no existe y no puede ser creado por el servidor. Compruebe los permisos de %s.Su directorio caché (%1$s) o %2$s necesita tener permisos de escritura para que este plugin funcione. Verifíquelo bien.Su servidor está configurado para comprobar el propietario de los scripts PHP antes de permitirles escribir y leer archivos.Su servidor cree que su hostname resuelve como %s. Algunos servicios, como la recolección de basura de este plugin o la publicación diferida de WordPress, podrían no funcionar correctamente.[%s] Comprobar página principal![%s] La página principal esta comprimida con Gzip! Caché eliminada![%s] La página principal esta comprimida con Gzip! Debe limpiar la caché.[%s] La página principal no es correcta, caché eliminada![%s] La página principal esta comprimida con Gzip! Por favor, limpie la caché.desactivadoactivadoarchivosegundoslanguages/wp-super-cache-uk.po000066600000176715152133035240012335 0ustar00msgid "" msgstr "" "Project-Id-Version: wp-super-cache\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2009-11-13 10:27+0000\n" "PO-Revision-Date: \n" "Last-Translator: Vitaly \n" "Language-Team: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Ukrainian\n" "X-Poedit-Country: UKRAINE\n" "X-Poedit-SourceCharset: utf-8\n" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "ПОГАНУ ПОВЕДІНКУ не знайдено. Будь ласка, перевірте Вашу інсталяцію." #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:66 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:709 msgid "Disable" msgstr "Вимкнути" #: plugins/badbehaviour.php:55 #: plugins/searchengine.php:67 msgid "disabled" msgstr "вимкнено" #: plugins/badbehaviour.php:57 #: plugins/searchengine.php:69 #: wp-cache.php:1052 msgid "enabled" msgstr "ввімкнено" #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s" msgstr "Підтримку ПОГАНОЇ ПОВЕДІНКИ %s" #: plugins/badbehaviour.php:62 #, php-format msgid "(Only half-on caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr " (Підтримується тільки напів-кешування, стиснення ввимкнено та потребує ПОГАНУ ПОВЕДІНКУ у \"%s/plugins/bad-behavior/\") " #: plugins/badbehaviour.php:64 #: plugins/searchengine.php:74 #: wp-cache.php:709 msgid "Enable" msgstr "Ввімкнути" #: plugins/badbehaviour.php:70 #: wp-cache.php:786 #: wp-cache.php:788 msgid "Warning!" msgstr "Увага!" #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s" msgstr "Плаґін Нема посилань для друзів %s" #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(необхідно також friendsadverts.php) " #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Будь ласка, створіть %s /wp-cache-config.php з wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:170 msgid "WP Super Cache Manager" msgstr "Управління Вордпрес Супер Кешем" #: wp-cache.php:172 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Увага! Ввімкнено PHP Безпечний Режим (Safe Mode)!" #: wp-cache.php:173 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Ви можете відчувати проблеми у роботі плаґіну, тому що ввімкнено Безпечний Режим (Safe Mode)." #: wp-cache.php:175 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Ваш сервер налаштований на перевірку власника PHP скриптів перед тим, як дозволити їм читати та писати файли." #: wp-cache.php:176 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Ви або Адміністратор можете виправити роботу, змінивши власника групи скриптів плаґіну. Необхідно також змінити власника групи папки %s/cache/. Додаткові деталі Ви можете переглянути на сторінці документації безпечного режиму." #: wp-cache.php:178 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Ви або Адміністратор повинні вимкнути це. Додаткові деталі Ви можете переглянути на сторінці документації безпечного режиму. На жаль, це не можна вимкнути у фалі .htaccess. Це можна поправити у файлі налаштувань php.ini." #: wp-cache.php:189 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Змінено файл налаштувань, деякі змінні можуть бути неправильними. Щоб обнулити їх, завантажте сторінку знову з розділу меню \"Налаштування\"." #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "Продовження неможливе... виправте попередні проблеми та спробуйте знову." #: wp-cache.php:211 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Увага! Ваше ім’я хосту \"%s\" прікріплено до %s" #: wp-cache.php:213 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Ваш сервер думає, що ім’я хосту прікріплено до %s. Деякі служби, такі як збір сміття цим плаґіном та WordPress scheduled posts можуть працювати неправильно." #: wp-cache.php:214 #: wp-cache.php:228 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Будь ласка, перегляньте пункт 16 у Розділі проблем у файлі readme.txt" #: wp-cache.php:227 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Нажаль, Вордпрес не може знайти файл wp-cron.php. Скрипт потребує правильних дій збору сміття цим плаґіном, WordPress scheduled posts такий самий як і інші критичні дії." #: wp-cache.php:239 msgid "Mod rewrite may not be installed!" msgstr "Можливо Mod_rewrite не встановлено!" #: wp-cache.php:240 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use half-on mode." msgstr "Здається, що mod_rewrite не встановлено. Іноді ця перевірка не є на 100% достовірною, особливо якщо Ви використовуєте не Apache. Будь ласка, переконайтесь у тому, що модуль mod_rewrite завантажено. Це необхідно для видачі статичних файлів Супер Кешу. Ви всерівно будете мати змогу використовувати режим напів-кешування." #: wp-cache.php:245 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Режим лише читання. Налаштування не можливо змінити." #: wp-cache.php:245 msgid "Why your configuration may not be changed" msgstr "Чому Ваші налаштування не можливо змінити" #: wp-cache.php:245 msgid "Why" msgstr "Чому" #: wp-cache.php:247 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Вордпрес Супер Кеш файл з налаштуваннями: %s/wp-cache-config.php і не може бути відредагованим. Щоб внести зміни, цей файл повинен бути доступним для запису веб-сервером." #: wp-cache.php:248 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Щоб це зробити, необхідно тимчасово змінити права доступу, використовуючи команду CHMOD або за допомогою вашого ftp-клієнту. Запевніться у тому, що є доступ для запису." #: wp-cache.php:249 msgid "Writeable:" msgstr "Доступне для запису:" #: wp-cache.php:250 msgid "Readonly:" msgstr "Доступне для читання:" #: wp-cache.php:262 #, php-format msgid "Warning! %s is writeable!" msgstr "Увага! Папка %s доступна для запису!" #: wp-cache.php:263 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Вам необхідно змінити права доступу для папки %s та зробити їх більш обмеженими. Використовуйте Ваш ftp-клієнт або наступні команди, щоб це виправити:" #: wp-cache.php:354 msgid "WP Super Cache Status" msgstr "Статус Вордпрес Супер Кеш" #: wp-cache.php:357 msgid "ON" msgstr "Ввімкнено" #: wp-cache.php:357 msgid "WP Cache and Super Cache enabled" msgstr "Вордпрес Кеш та Вордпрес Супер Кеш ввімкнено" #: wp-cache.php:358 msgid "HALF ON" msgstr "Ввімкнено наполовину" #: wp-cache.php:358 msgid "Super Cache Disabled, only legacy WP-Cache caching." msgstr "Супер Кеш вимкнено, кешує лише Вордпрес Кеш." #: wp-cache.php:359 msgid "OFF" msgstr "Вимкнено" #: wp-cache.php:359 msgid "WP Cache and Super Cache disabled" msgstr "Вордпрес Кеш та Вордпрес Супер Кеш вимкнено" #: wp-cache.php:360 msgid "Don’t cache pages for logged in users." msgstr "Не кешувати сторінки для залогованих користувачів." #: wp-cache.php:361 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Скажіть гордо світу, що Ваш сервер підтверджено Діггом! (розмістити повідомлення у підвал Вашого сайту)" #: wp-cache.php:362 msgid "Clear all cache files when a post or page is published. (This may significantly slow down saving of posts.)" msgstr "Видалити всі закешовані файли, якщо стаття або сторінка оновилась. (Це може значно сповільнити збереження сторінок.)" #: wp-cache.php:363 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated. Recommended for very busy websites with lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" obsolete." msgstr "Оновлення кешу. Видавати супер-кешований файл для анонімних користувачів, поки не згенерується новий файл. Рекомендовано для дуже завантажених сайтів з великою кількістю коментарів. Робить \"безпосередньо закешовані сторінки\" та \"Режим блокування\" непотрібними." #: wp-cache.php:365 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Блокування великих файлів. Вам це напевне не потрібно, але це може допомогти, якщо у Вас не дуже потужний сервер. Увага! Може спричинити блокування Вашого сервера у рідких випадках! " #: wp-cache.php:367 msgid "List the newest cached pages (may be expensive to run on busy sites, use with caution.)" msgstr "Список найновіших закешованих сторінок (може довго виконуватися на завантажених сайтах, використовуйте з обережністю.)" #: wp-cache.php:368 msgid "Mobile device support." msgstr "Підтримка стільникових пристроїв." #: wp-cache.php:373 msgid "Mobile rewrite rules detected" msgstr "Знайдено правила rewrite для стільникових пристроїв" #: wp-cache.php:374 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"Android|2.0\\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone\" and delete those." msgstr "Для кращої роботи Вам необхідно ввімкнути \"Підтримку стільникових пристроїв\" або видалити правило mod_rewrite для стільникових пристроїв у файлі .htaccess. Знайдіть дві стрічки з текстом \"Android|2.0\\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone\" та видаліть їх." #: wp-cache.php:374 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Це не спричинить ніякого ефекту на звичайних користувачів, але стільникові користувачі побачать незакешовані сторінки." #: wp-cache.php:377 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to half-on mode. Here are your options (in order of difficulty):" msgstr "Підтримка мобільних пристроїв потребує додаткових правил у Вашому .htaccess файлі або Ви можете налаштувати плаґін у режим напів-кешування. Ось Ваші налаштування (у порядку ускладнення):" #: wp-cache.php:378 msgid "Set the plugin to half on mode and enable mobile support." msgstr "Налаштувати плаґін у режим напів-кешування та ввімкнути підтримку стільникових пристроїв." #: wp-cache.php:379 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Видалити mod_rewrite правила плаґіну у %s.htaccess, що починається зі стрічки # BEGIN WPSuperCache та закінчується # END WPSuperCache та дозволити плаґіну перегенерувати їх за допомогою перезавантаження сторінки." #: wp-cache.php:380 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ add this line: (do it twice, once for each section)" msgstr "Додати правила самостійно. Відредагуйте %s.htaccess та знайдіть фрагмент коду, що починається зі стрічки # BEGIN WPSuperCache та закінчується стрічкою # END WPSuperCache. Є два подібні між собою фрагменти коду. Одразу під стрічкою %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ додайте цей код: (зробіть це двічі, тобто для кожного з фрагментів)" #: wp-cache.php:383 msgid "Note:" msgstr "Примітка:" #: wp-cache.php:383 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Якщо Ви деінсталюєте цей плаґін, переконайтесь, що папка %s є доступною для запису веб-сервером і файли advanced-cache.php та cache-config.php можуть бути видалені автоматично. (Переконайтесь, що ці файли доступні для запису також!)" #: wp-cache.php:384 #, php-format msgid "Uninstall using the uninstall script to remove files and directories created by the plugin. (Please see readme.txt for instructions on uninstalling this script.)" msgstr "Деінсталювати, використовуючи скрипт деінсталяції, щоб видалити файли та папки, створені плаґіном. (Будь ласка, перегляньте readme.txt для порад по деінсталяції.)" #: wp-cache.php:386 msgid "Update Status" msgstr "Зберегти налаштування" #: wp-cache.php:393 msgid "Required to serve compressed supercache files properly." msgstr "Необхідне для того, щоб правильно видавати стиснуті супер-кешовані файли." #: wp-cache.php:393 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Необхідне для того, щоб налаштувати інформацію щодо кешування на супер-кешованих сторінках. Без цього модуля користувачі ІЕ7 побачать старі сторінки." #: wp-cache.php:393 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Встановити термін дії для супер-кешованих сторінок. Без цього модуля відвідувачі можливо не побачать нових сторінок коли вони оновлять сторінку або залишать коментар." #: wp-cache.php:400 msgid "Missing Apache Modules" msgstr "Невистачає модулів Apache" #: wp-cache.php:401 msgid "The following Apache modules are missing. The plugin will work in half-on mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Наступні Apache модулі відсутні. Без них плаґін буде працювати у режимі напів-кешування. У режимі повного супер-кешування Ваші відвідувачі можливо побачать зіпсовані сторінки або протермінований вміст сторінок." #: wp-cache.php:413 msgid "Make WordPress Faster" msgstr "Зробити Вордпрес швидшим" #: wp-cache.php:415 #, php-format msgid "%1$s really makes your blog go faster. Make it go faster* by buying me an Amazon gift card! Make it out to \"%3$s\" for whatever amount you want. Every penny helps!" msgstr "%1$s справді робить Ваш сайт швидшим. Зробіть його ще швидшим*, купивши мені вітальну листівку на Амазоні! Зробити її у \"%3$s\" з будь-якою сумою. Кожна копійка допоможе!" #: wp-cache.php:416 #, php-format msgid "If Amazon isn’t your thing, there’s also PayPal. Click the \"Donate\" button below or take a quick peek at my wishlist." msgstr "Якщо Амазон не для Вас, є також PayPal. Клікніть внизу на кнопку \"Пожертвувати\" або перегляньте список моїх побажань." #: wp-cache.php:417 msgid "Thanks in advance!" msgstr "Дякую!" #: wp-cache.php:418 msgid "Ok, it won’t go any faster but you’ll make this plugin author very happy!" msgstr "Ну добре, воно не запрацює швидше, але Ви зробите автора цього плаґіну дуже щасливим!" #: wp-cache.php:426 msgid "Don’t show me this again." msgstr "Не показувати мені цього знову." #: wp-cache.php:426 msgid "Hide" msgstr "Приховати" #: wp-cache.php:429 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s підтримується та розроблено %2$s за сприянням багатьох інших розробників." #: wp-cache.php:430 #, php-format msgid "He blogs at %1$s, posts photos at %2$s and wishes he had more time to read and relax." msgstr "Він має блог на %1$s, публікує фото на %2$s та якби він мав більше часу почитати та розслабитись." #: wp-cache.php:431 #, php-format msgid "Please say hi to him on %s too!" msgstr "Сказати йому \"привіт\" у %s також!" #: wp-cache.php:440 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Сторінки закешовано з %1$s : %2$s" #: wp-cache.php:441 msgid "Newest Cached Pages:" msgstr "Новіші закешовані сторінки:" #: wp-cache.php:445 #, php-format msgid "Cached %s seconds ago" msgstr "Закешовано %s секунд тому назад" #: wp-cache.php:448 msgid "(may not always be accurate on busy sites)" msgstr "(може бути не завжди точним на завантажених сайтах)" #: wp-cache.php:469 msgid "Accepted Filenames & Rejected URIs" msgstr "Прийняті імена файлів та відхилені URI-шляхи" #: wp-cache.php:494 msgid "Cache Plugins" msgstr "Плаґіни для Кешу" #: wp-cache.php:505 #: wp-cache.php:516 msgid "Super Cache Compression" msgstr "Стиск Супер Кешу" #: wp-cache.php:506 msgid "Compression is enabled by default when in HALF ON mode." msgstr "У режимі Напів-Кешування стиск ввіммкнено за замовчуванням." #: wp-cache.php:518 #: wp-cache.php:696 msgid "Enabled" msgstr "Ввімкнено" #: wp-cache.php:519 #: wp-cache.php:696 msgid "Disabled" msgstr "Вимкнено" #: wp-cache.php:520 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching this on and off clears the cache." msgstr "Стиск вимкнено за замовчуванням, тому що деякі хости мають проблеми зі стиснутими файлами. Вмикання та вимикання цього пункту призводить до очищення кешу." #: wp-cache.php:523 msgid "Super Cache compression is now disabled." msgstr "Стиск Супер Кешу вимкнено." #: wp-cache.php:525 msgid "Super Cache compression is now enabled." msgstr "Стиск Супер Кешу ввімкнено." #: wp-cache.php:527 msgid "Update Compression" msgstr "Оновити стиск" #: wp-cache.php:534 msgid "Mod Rewrite Rules" msgstr "Правила Mod Rewrite" #: wp-cache.php:581 msgid "WordPress MU Detected" msgstr "Виявлено Вордпрес МЮ" #: wp-cache.php:581 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Нажаль, коли працює Вордпрес МЮ, правила rewrite не можуть бути оновлені автоматично. Будь ласка, відкрийте Ваш .htaccess файл та додайте наступні правила mod_rewrite з самого початку файлу." #: wp-cache.php:583 msgid "Mod Rewrite rules cannot be updated!" msgstr "Правила Mod Rewrite не можна оновити!" #: wp-cache.php:584 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Ви повинні мати маркери BEGIN та END у %s.htaccess файлі для того, щоб працювало автооновлення. Вони схожі на це та оточують головні mod_rewrite правила Вордпресу:" #: wp-cache.php:586 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Оновіть цю сторінку коли Ви оновите Ваш .htaccess файл." #: wp-cache.php:590 msgid "Thank you for upgrading." msgstr "Дякую за оновлення" #: wp-cache.php:590 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Правила mod_rewrite змінилися з того часу, коли Ви інсталювали цей плаґін. На жаль, Ви повинні видалити старі правила для Супер Кешу перед тим, як додати нові. Оновіть цю сторінку, коли відредагуєте Ваш .htaccess файл. Якщо Ви бажаєте додати оновлення вручну, змініть наступну стрічку: %1$s щоб вона виглядала приблизно ось так: %2$s Необхідно внести наступні зміни: \"HTTP_COOKIE\" замінити на \"HTTP:Cookie\" та \"wordpressuser\" замінити на \"wordpress\". Це зміна для Вордпресу 2.5, але це зворотня сумісність зі старішими версіями, якщо Ви достатньо хоробрий, щоб їх використовувати." #: wp-cache.php:594 msgid "Trailing slash check required." msgstr "Необхідна перевірка першого слешу." #: wp-cache.php:594 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Схоже на те, що Ваш сайт має URL-адреси, що закінчуються символом \"/\". На жаль, з того часу, як Ви інсталювали цей плаґін, виникла помилка дублювання вмісту, при якій URL-адреси, що не закінчуються символом \"/\" видають той самий вміст, що і сторінки з символом \"/\" у кінці та не перенаправляються на правильну URL-адресу. Щоб це виправити, Вам необхідно відредагувати Ваш .htaccess файл та додати ці два правила до двох груп правил Супер Кешу:" #: wp-cache.php:596 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Ви можете побачити, де правила виконуються та дослідити повні правила, відвідавши посилання \"Переглянути правила mod_rewrite\", що розміщено нижче." #: wp-cache.php:608 msgid "Cannot update .htaccess" msgstr "Неможливо оновити .htaccess" #: wp-cache.php:608 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Файл %s.htaccess не може бути змінений веб-сервером. Будь ласка, виправте це, використовуючи команду CHMOD або Ваш FTP-клієнт." #: wp-cache.php:608 msgid "Refresh this page when the file permissions have been modified." msgstr "Оновіть цю сторінку, якщо права доступу файлу було змінено." #: wp-cache.php:608 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Крім того, Ви можете редагувати свій %s.htaccess файл вручну та додати наступний код (перед будь-якими правилами Вордпресу):" #: wp-cache.php:611 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Щоб видавати статичні HTML-файли сервер повинен мати правильні правила mod_rewrite, що додані у файл %s.htaccess" #: wp-cache.php:613 msgid "You must edit the file yourself add the following rules." msgstr "Ви повинні редагувати файл самостійно, додаючи наступні правила." #: wp-cache.php:615 msgid "You can edit the file yourself add the following rules." msgstr "Ви можете редагувати файл самостійно, додаючи наступні правила." #: wp-cache.php:617 msgid " Make sure they appear before any existing WordPress rules. " msgstr "Переконайтеся, що вони розміщені перед будь-яким з існуючих правил Вордпресу." #: wp-cache.php:619 #: wp-cache.php:646 #, php-format msgid "Rules must be added to %s too:" msgstr "Правила необхідно додати до %s також:" #: wp-cache.php:624 msgid "Update Mod_Rewrite Rules" msgstr "Оновити правили Mod_Rewrite" #: wp-cache.php:633 msgid "Mod Rewrite rules updated!" msgstr "Правила Mod Rewrite оновлено!" #: wp-cache.php:634 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "У %s.htaccess було додано необхідні правила mod_rewrite. Будь ласка, перевірте їх правильність. Вони повинні бути подібними на ці:" #: wp-cache.php:636 msgid "Mod Rewrite rules must be updated!" msgstr "Правила Mod Rewrite необхідно оновити!" #: wp-cache.php:637 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Ваш %s.htaccess недоступний для запису веб-сервером, і повинен бути оновлений необхідними правилами mod_rewrite. Нові правила розміщуються вище звичайних правил Вордпресу, як показано в коді нижче:" #: wp-cache.php:642 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Знайдено mod_rewrite правила Вордпрес Супер Кешу у Вашому %s.htaccess файлі.
    Відвідайте наступне посилання, щоб побачити додані у цей файл стрічки. Якщо Ви оновили плаґін, переконайтесь, що ці правила підходять." #: wp-cache.php:643 msgid "View Mod_Rewrite Rules" msgstr "Переглянути правила Mod_Rewrite" #: wp-cache.php:654 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Створено правила Gzip декодування у %s.htaccess." #: wp-cache.php:661 msgid "Fix Configuration" msgstr "Виправити налаштування" #: wp-cache.php:664 msgid "Restore Default Configuration" msgstr "Відновити налаштування за замовчуванням" #: wp-cache.php:672 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Модерацію коментарів ввімкнено. Можливо знадобиться трохи часу, щоб Ваш коментар з’явився." #: wp-cache.php:696 msgid "Lock Down:" msgstr "Заблоковано:" #: wp-cache.php:697 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Підготуйте свій сервер для очікуваного збільшення трафіка, дозволяючи блокування. Коли ця опція ввімкнена, нові коментарі не будуть оновлювати закешованих статичних файлів." #: wp-cache.php:698 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Розробники: Зробіть Ваш плаґін сумісним для блокування, перевіривши константу \"WPLOCKDOWN\". Наступний код буде переконаний у тому, що Ваш плаґін перевіряє налаштування WPLOCKDOWN." #: wp-cache.php:700 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Вибачте. Мій сайт заблоковано. Оновлення скоро з’являться" #: wp-cache.php:704 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "Вордпрес заблоковано. Статичні файли Супер Кешу не будуть видалені коли з’являться нові коментарі." #: wp-cache.php:706 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "Вордпрес не заблоковано. Нові коментарі будуть оновлювати статичні файли Супер Кешу у звичайному режимі." #: wp-cache.php:712 msgid "Lock Down" msgstr "режим блокування" #: wp-cache.php:720 msgid "Directly Cached Files" msgstr "Безпосередньо закешовані файли" #: wp-cache.php:778 #, php-format msgid "%s removed!" msgstr "%s видалено!" #: wp-cache.php:786 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Ви повинні зробити %s доступною для запису для ввімкнення цієї функції. Оскільки це ризиковано, будь ласка, зробіть її знову доступною лише для читання після того, як Ваша сторінка згенерується." #: wp-cache.php:788 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "Папка %s доступна для запису. Будь ласка, зробіть її доступною для читання після того, як сторінка згенерується, бо це небезпечно." #: wp-cache.php:802 msgid "Existing direct page" msgstr "Дана сторінка існує" #: wp-cache.php:802 msgid "Delete cached file" msgstr "Видалити закешований файл" #: wp-cache.php:807 msgid "Add direct page:" msgstr "Додати дану сторінку:" #: wp-cache.php:809 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Безпосередньо закешовані файли - це файли, створені безпосередньо у %s, де розміщено Ваш сайт. Ця опція корисна лише тоді, якщо Ви очікуєте значного збільшення трафіку з Діггу або Слешдоту на одну зі своїх статей або сторінок." #: wp-cache.php:811 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Наприклад: щоб закешувати %1$sabout/, Вам необхідно ввести %1$sabout/ або /about/. Закешований файл буде створено наступного разу коли анонімний користувач відвідає цю сторінку." #: wp-cache.php:812 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Очистіть текстове поле, щоб знищити сторінку зі списку безпосередньо закешованих сторінок та видалити закешований файл." #: wp-cache.php:817 msgid "Update Direct Pages" msgstr "Оновити дані сторінки" #: wp-cache.php:857 msgid "Expiry Time & Garbage Collection" msgstr "Термін дії та збір сміття" #: wp-cache.php:859 msgid "Expire time:" msgstr "Час протермінування:" #: wp-cache.php:860 msgid "seconds" msgstr "секунд" #: wp-cache.php:861 msgid "Garbage Collection" msgstr "Збір Сміття" #: wp-cache.php:861 msgid "If expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Якщо час протермінування більш ніж 1800 секунд (півгодини), тоді збір сміття буде здійснюватися кожні 10 хвилин, в іншому випадку це відбудеться через 10 секунд після закінчення часу, що зазначено вище." #: wp-cache.php:862 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. Aim to have less than 500 cached files if possible." msgstr "Перевірка та видалення протермінованих файлів є ресурсоємкою процедурою, але залишати їх там було би неправильно. На дуже завантаженому сайті Ви повинні встановити термін дії на 300 секунд. Поекспериментуйте з різними значеннями та відвідайте цю сторінку, щоб дізнатися, скільки протермінованих файлів залишилося у різний час протягом дня. Прагніть до того, щоб залишилось менше ніж 500 закешованих файлів." #: wp-cache.php:863 msgid "Change Expiration" msgstr "Змінити термін дії" #: wp-cache.php:902 msgid "Rejected User Agents" msgstr "Відхилені броузери (боти)" #: wp-cache.php:903 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Стрічки у HTTP-запитах для браузерів (ботів), що забороняють Вордпрес Кешу кешувати запити ботів та пошукових павуків. Зауважте, що супер-кешовані файли все ще видаються цим браузерам (ботам), якщо вони вже існують." #: wp-cache.php:910 msgid "Save UA Strings" msgstr "Зберегти назви ботів (пошукових павуків)" #: wp-cache.php:933 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Не кешувати наступні типи сторінок. Відвідайте сторінку документації умовні теги для повного роз’яснення по кожному типу." #: wp-cache.php:936 msgid "Single Posts" msgstr "Одинарні статті" #: wp-cache.php:937 msgid "Pages" msgstr "Сторінки" #: wp-cache.php:938 msgid "Front Page" msgstr "Головна сторінка" #: wp-cache.php:939 msgid "Home" msgstr "Домашня сторінка" #: wp-cache.php:940 msgid "Archives" msgstr "Архіви" #: wp-cache.php:941 msgid "Tags" msgstr "Теги" #: wp-cache.php:942 msgid "Category" msgstr "Категорії" #: wp-cache.php:943 msgid "Feeds" msgstr "Фіди" #: wp-cache.php:944 msgid "Search Pages" msgstr "Сторінки пошуку" #: wp-cache.php:946 #: wp-cache.php:1073 msgid "Save" msgstr "Зберегти" #: wp-cache.php:963 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Додати стрічки (не і’мя файлу), що примушують сторінки не кешувати. Наприклад, якщо Ваші URL-адреси містять рік і Ви не хочете кешувати останній рік статей, тоді достатньо вказати рік, наприклад ’/2004/’. Вордпрес Кеш перевірить чи ця стрічка є частиною URI-шляху. Якщо так, тоді ця сторінка не буде закешованою." #: wp-cache.php:969 msgid "Save Strings" msgstr "Зберегти стрічки" #: wp-cache.php:985 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Додайте сюди імена файлів, які можуть бути закешованими, навіть якщо вони відповідають одній з відхилених стрічок, зазначених вище." #: wp-cache.php:991 msgid "Save Files" msgstr "Зберегти файли" #: wp-cache.php:1035 msgid "Debug Settings" msgstr "Налаштування відлагодження" #: wp-cache.php:1037 msgid "Currently logging to: " msgstr "Зараз лог записується у: " #: wp-cache.php:1047 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Виправіть проблеми з плаґіном, відлагоджуючи його тут. Він може надсилати Вам відгоджувальні листи на електротронну скриньку або зберігати інформацію у лог-файл у каталозі кешу." #: wp-cache.php:1048 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Ведення лог-файлу простіше, але виникає проблема - очищення кешу буде очищати лог-файл." #: wp-cache.php:1052 msgid "Debugging" msgstr "Відлагодження" #: wp-cache.php:1053 msgid "Logging Type" msgstr "Тип логу" #: wp-cache.php:1053 msgid "Email" msgstr "Електронна скринька" #: wp-cache.php:1054 msgid "file" msgstr "файл" #: wp-cache.php:1055 msgid "IP Address" msgstr "IP-адреса" #: wp-cache.php:1055 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(з цієї IP-адреси лише лог запити. Ваша IP-адреса: %s)" #: wp-cache.php:1056 msgid "Log level" msgstr "Рівень логу" #: wp-cache.php:1062 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = менше, 5 = більше, може викликати навантаження сервера.)" #: wp-cache.php:1064 msgid "Advanced" msgstr "Розширене" #: wp-cache.php:1064 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "У дуже рідкісних випадках на деяких сайтах, можуть виникнути дві проблеми:
    1. Головна сторінка може почати завантажуватись як Zip-файл.
    2. Випадково кешується не та сторінка як головна, якщо Ваш сайт використовує наступну структуру постійних посилань /%category%/%postname%/.
    " #: wp-cache.php:1065 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "На 99%c я впевнений, що ці помилки не стосуються плаґіну Вордпрес Супер Кеш і вони трапляються у дуже рідких випадках, але Ви можете провести просту перевірку кожних 5 хвилин, щоб запевнитися, що Ваш сайт функціонує добре. Якщо виникнуть якісь проблеми, Ви отримаєте електронне повідомлення." #: wp-cache.php:1067 msgid "Check front page every 5 minutes." msgstr "Перевіряти головну сторінку кожні 5 хвилин." #: wp-cache.php:1068 msgid "Front page text" msgstr "Текст головної сторінки" #: wp-cache.php:1068 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Текст для пошуку на головній сторінці. Якщо цей текст відсутній, тоді кеш буде очищено. Залиште порожнім, щоб відключити." #: wp-cache.php:1069 msgid "Clear cache on error." msgstr "Очистити кеш при помилці." #: wp-cache.php:1070 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Надіслати електронного листа адміністратору сайту, коли перевірку буде завершено. (корисно для тестування)" #: wp-cache.php:1083 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Помилка: стиск GZIP ввімкнено. Якщо Ви хочете, щоб Вордпрес-Кеш працював, тоді вимкніть це." #: wp-cache.php:1131 #: wp-cache.php:1293 msgid "Warning" msgstr "Увага" #: wp-cache.php:1131 msgid "GZIP compression is enabled in Wordpress, wp-cache will be bypassed until you disable gzip compression." msgstr "Стиск GZIP ввімкнено у Вордпресі, Вордпрес-Кеш буде пропущено, поки Ви не відключите стиск GZIP." #: wp-cache.php:1189 #: wp-cache.php:1194 #: wp-cache.php:1226 #: wp-cache.php:1231 #: wp-cache.php:1237 msgid "Error" msgstr "Помилка" #: wp-cache.php:1189 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Ваш каталог кешу ($cache_path) не існує і не може бути створений веб-сервер. Перевірте %s права доступу." #: wp-cache.php:1194 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Ваш каталог кешу (%1$s) або %2$s повинен мати дозвіл на запис щоб плаґін запрацював. Двічі це перевірте." #: wp-cache.php:1226 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Ваш конфігураційний файл Вордпрес-Кешу (%s) застарів та не доступний для запису веб-сервером. Будь ласка, видаліть його та оновіть цю сторінку." #: wp-cache.php:1231 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Конфігураційний файл відсутній та папка %1$s (%2$s) не доступна для запису веб-сервером. Перевірте права доступу." #: wp-cache.php:1237 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Не знайдено зразку конфігураційного файлу Вордпрес Кешу (%s). Перевірте Вашу інсталяцію." #: wp-cache.php:1293 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php не існує або не може бути оновленим." #: wp-cache.php:1294 msgid "1. If it already exists please delete the file first." msgstr "1. Якщо це вже існує, будь ласка, видаліть спочатку файл." #: wp-cache.php:1295 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Зробіть %1$s доступною для запису, використовуючи команди CHMOD або Ваш ftp-клієнт. (chmod 777 %1$s) та оновіть цю сторінку. Це лише тимчасова поправка, і Вам необхідно зробити цю папку доступною для читання вкінці знову. (Змініть 777 на 755 у попередній команді)" #: wp-cache.php:1296 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Обновіть цю сторінку, щоб оновити %s/advanced-cache.php" #: wp-cache.php:1297 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Якщо це не працює, переконайтесь, що файл %s/advanced-cache.php не існує:" #: wp-cache.php:1298 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Вдкрийте %1$s$wp_cache_file у текстовому редакторі.
  • 2. Змініть текст CACHEHOME на %2$s
  • 3. Збережіть файл і скопіюйте його в %3$s та оновіть цю сторінку.
    • " #: wp-cache.php:1318 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Помилка: WP_CACHE не ввімкнено у Вашому wp-config.php файлі і я не зміг відредагувати його." #: wp-cache.php:1319 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by Wordpress core. " msgstr "Відредагуйте код %s та додайте наступну стрічку:
    define('WP_CACHE', true);
    В іншому випадку Вордпрес-Кеш не виконається за допомогою ядра Вордпресу." #: wp-cache.php:1322 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    Константа WP_CACHE додана у файл wp-config.php

    Якщо Ви продовжуєте бачити це попередження, тоді дивіться пункт 5 у FAQ. Стрічка WP_CACHE повинна бути переміщена вгору." #: wp-cache.php:1343 msgid "Cache Contents" msgstr "Вміст Кешу" #: wp-cache.php:1362 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Видаляється супер-кешований файл: %s
    " #: wp-cache.php:1379 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Видаляється файл wp-cache: %s
    " #: wp-cache.php:1443 msgid "WP-Cache" msgstr "Вордпрес-Кеш" #: wp-cache.php:1444 #: wp-cache.php:1457 #, php-format msgid "%s Cached Pages" msgstr "%s закешованих сторінок" #: wp-cache.php:1445 #: wp-cache.php:1459 #, php-format msgid "%s Expired Pages" msgstr "%s протермінованих сторінок" #: wp-cache.php:1456 msgid "WP-Super-Cache" msgstr "Вордпрес-Супер-Кеш" #: wp-cache.php:1464 msgid "Fresh WP-Cached Files" msgstr "Свіжі Вордпрес-Закешовані файли" #: wp-cache.php:1465 #: wp-cache.php:1481 #: wp-cache.php:1497 #: wp-cache.php:1513 msgid "URI" msgstr "URI-шлях" #: wp-cache.php:1465 #: wp-cache.php:1481 msgid "Key" msgstr "Ключ" #: wp-cache.php:1465 #: wp-cache.php:1481 #: wp-cache.php:1497 #: wp-cache.php:1513 msgid "Age" msgstr "Вік" #: wp-cache.php:1465 #: wp-cache.php:1481 #: wp-cache.php:1497 #: wp-cache.php:1513 msgid "Delete" msgstr "Видалити" #: wp-cache.php:1480 msgid "Stale WP-Cached Files" msgstr "Протерміновані Вордпрес-Кешовані файли" #: wp-cache.php:1496 msgid "Fresh Super Cached Files" msgstr "Свіжі Супер Кешовані файли" #: wp-cache.php:1512 msgid "Stale Super Cached Files" msgstr "Протерміновані Супер Кешовані файли" #: wp-cache.php:1528 msgid "Hide file list" msgstr "Приховати список файлів" #: wp-cache.php:1530 msgid "List all cached files" msgstr "Список всіх закешованих файлів" #: wp-cache.php:1536 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Збір Сміття
    Останній Збір Сміття був %s хвилин тому
    " #: wp-cache.php:1537 #, php-format msgid "Next GC in %s minutes" msgstr "Наступний збір сміття відбудеться через %s хвилин" #: wp-cache.php:1540 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Протерміновані файли - це файли, що старші за %s секунд. Вони все рівно використовуються плаґіном та видаляються періодично." #: wp-cache.php:1543 msgid "Delete Expired" msgstr "Видалити протерміноване" #: wp-cache.php:1549 #: wp-cache.php:1563 #: wp-cache.php:1719 msgid "Delete Cache" msgstr "Очистити кеш" #: wp-cache.php:1563 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Видалити закешовані файли Супер Кешу (завантажиться у новому вікні)" #: wp-cache.php:1695 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s підтверджено Діггом і закешовано за допомогою %2$s" #: wp-cache.php:1728 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "Вордпрес Супер Кеш необхідно налаштувати. Перейдіть на сторінку адміністрування, щоб ввімкнути та налаштувати плаґін." #: wp-cache.php:1734 msgid "Settings" msgstr "Налаштування" #: wp-cache.php:1744 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "Вордпрес Супер Кеш ввімкнено. Будь ласка, перейдіть на сторінку адміністрування плаґіну, щоб ввімкнути кешування." #: wp-cache.php:1763 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Головну сторінку стиснено gzipp-ом! Будь ласка, очистіть кеш!" #: wp-cache.php:1763 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Будь ласка, відвідайте %s, щоб очистити кеш, тому що головна сторінка Вашого сайту зараз завантажується!" #: wp-cache.php:1766 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Головну сторінку стиснено gzipp-ом! Кеш очищено!" #: wp-cache.php:1766 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Кеш на Вашому сайті була очищено, тому що головна сторінка зараз завантажується. Будь ласка, відвідайте %s для перевірки того, що кеш було очищено." #: wp-cache.php:1773 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Головна сторінка не правильна! Будь ласка, очистіть кеш!" #: wp-cache.php:1773 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Відвідайте %1$s, щоб очистити кеш, тому що головна сторінка Вашого сайту неправильна та відсутній текст, \"%2$s\"!" #: wp-cache.php:1776 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Головна сторінка не правильна! Кеш очищено!" #: wp-cache.php:1776 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Кеш на Вашому сайті було очищено, тому що на головній сторінці відсутній текст \"%2$s\". Відвідайте %1$s для перевірки того, що кеш було очищено." #: wp-cache.php:1781 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Перевірка головної сторінки!" #: wp-cache.php:1781 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "Вордпрес Супер Кеш перевірив головну сторінку Вашого сайту. Будь ласка, відвідайте %s, якщо Ви хочете це відключити." languages/wp-super-cache-ua_UA.po000066600000260222152133035240012673 0ustar00# Translation of the WordPress plugin by . # Copyright (C) 2010 # This file is distributed under the same license as the package. # FIRST AUTHOR , 2010. # msgid "" msgstr "" "Project-Id-Version: WP Super Cache\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2010-09-27 13:58+0000\n" "PO-Revision-Date: 2011-07-24 13:13+0200\n" "Last-Translator: Alexandr \n" "Language-Team: Alyona Lompar \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Ukrainian\n" "X-Poedit-Country: UKRAINE\n" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Ваш коментар очікує підтвердження." #: plugins/awaitingmoderation.php:23 #: plugins/awaitingmoderation.php:38 #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:47 #: plugins/domain-mapping.php:62 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1114 msgid "Disable" msgstr "Відключити" #: plugins/awaitingmoderation.php:29 #: plugins/badbehaviour.php:55 #: plugins/domain-mapping.php:53 #: plugins/searchengine.php:67 msgid "disabled" msgstr "Відключений" #: plugins/awaitingmoderation.php:31 #: plugins/badbehaviour.php:57 #: plugins/domain-mapping.php:55 #: plugins/searchengine.php:69 #: wp-cache.php:1460 msgid "enabled" msgstr "Включений" #: plugins/awaitingmoderation.php:33 #, php-format msgid "Awaiting Moderation plugin is %s" msgstr "Статус плагіна \"Awaiting Moderation\": %s" #: plugins/awaitingmoderation.php:34 msgid "(Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment.) " msgstr "(Прибирає текст \" Ваш коментар очікує перевірки\" коли хтось розміщує коментар до запису)" #: plugins/awaitingmoderation.php:36 #: plugins/badbehaviour.php:63 #: plugins/domain-mapping.php:60 #: plugins/searchengine.php:74 #: wp-cache.php:1114 msgid "Enable" msgstr "Включити" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "Плагін \" Bad Behaviour\" не був знайдений. Перевірте, чи завершили Ви його встановлення." #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s." msgstr "Статус плагіна \" Bad Behaviour\": %s." #: plugins/badbehaviour.php:61 #, php-format msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Даний плагін буде функціонувати лише в режимі середнього кешування, вимкніть стиск і встановіть плагін \"Bad Behavior\" в \"%s/ plugins/bad-behavior/ \") " #: plugins/badbehaviour.php:69 #: wp-cache.php:1191 #: wp-cache.php:1193 msgid "Warning!" msgstr "Увага!" #: plugins/domain-mapping.php:57 #, php-format msgid "Domain Mapping support plugin is %s" msgstr "Статус плагіна \"Domain Mapping\": %s" #: plugins/domain-mapping.php:58 msgid "(support for multiple domains on multisite websites) " msgstr "(Підтримка для MU - сервісу блогів)" #: plugins/domain-mapping.php:72 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Виявлена ​​підтримка сервісу мультіблогов! Щоб полегшити і прискорити роботу плагіна, Вам потрібно включити підтримку мультіблогов в налаштуваннях." #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s." msgstr "Статус плагіна \"No Adverts for Friends\": %s." #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(Вимагає установки friendsadverts.php)" #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Будь ласка, створіть файл %s /wp-cache-config.php з wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:138 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Увага! Включений режим PHP Safe Mode!" #: wp-cache.php:139 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "При роботі з плагіном можуть виникнути проблеми, тому що PHP Safe Mode включений на Вашому сервері." #: wp-cache.php:143 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Ваш сервер налаштований так, що перевіряє власника для всіх PHP скриптів перед тим як дозволити їм читання або запис в файл." #: wp-cache.php:144 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Ви або Адміністратор можете виправити помилки, змінивши групу власника скриптів плагіна через налаштування веб-сервера. Також потрібно змінити власника для папки %s/cache/. Для більш детальної інформації дивіться сторінку допомоги по режиму safe mode (на англ.)." #: wp-cache.php:146 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Ви або Адміністратор повинні відключити це. Для більш детальної інформації дивіться сторінку допомоги по режиму safe mode (на англ.). Ці налаштування НЕ можуть бути відключені через файл. htaccess, для вирішення проблеми потрібно редагувати php.ini в настройках веб-сервера." #: wp-cache.php:152 msgid "Permlink Structure Error" msgstr "Помилка структури посилань" #: wp-cache.php:153 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Для коректної роботи плагіна необхідна коректна настройка структури посилань. Щоб налаштувати їх, відвідайте сторінку Постійні посилання." #: wp-cache.php:165 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Увага! Ваше hostname \"%s\" перетворено у %s" #: wp-cache.php:166 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Ваш веб-сервер вирішив, що hostname змінено на %s. Деякі опції плагіна (наприклад, \"Очищення сміття\") і сам WordPress можуть працювати некоректно." #: wp-cache.php:167 #: wp-cache.php:181 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Щоб дізнатися більше, відвідайте розділ 16 в Описі проблем у файлі readme.txt (на англ.)" #: wp-cache.php:180 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "На жаль, файл wp-cron.php не було виявлено. Цей скрипт необхідний для коректної роботи опцііі \"Очищення сміття\" і самого WordPress." #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "Неможливо продовжити ... перш ніж повторити спробу, виправте попередні помилки." #: wp-cache.php:204 msgid "Zlib Output Compression Enabled!" msgstr "Стиснення Zlib Output включено!" #: wp-cache.php:205 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP використовує стиснення для стислих сторінки Вашого сайту. Відключення даної опції рекомендується, щоб уникнути багаторазового стиснення сторінок плагіном. Дізнатися більше, відвідавши розділ 16 в \"Опис проблем\" у файлі readme.txt (на англ.). Також ознайомтеся з цієї сторінкою (на англ.) по php.ini." #: wp-cache.php:209 msgid "Mod rewrite may not be installed!" msgstr "Здається, модуль mod_rewrite не встановлено!" #: wp-cache.php:210 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Виникла помилка, пов'язана з тим, що модуль mod_rewrite відсутній або не встановлений. Будь ласка, перевірте наявність модуля mod_rewrite в конфігураціях сервера. Модуль необхідний для коректної роботи плагіна з статичними файлами. Без підключеного mod_rewrite Ви можете використовувати тільки режими з підтримкою PHP або середню кешування." #: wp-cache.php:215 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Режим \"только_чтеніе\". Настройки не можуть бути змінені." #: wp-cache.php:216 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Конфігураційний файл плагіна WP Super Cache %s/wp-cache-config.php не може бути змінений. Щоб продовжити, Ви повинні встановити права на запис для файлу." #: wp-cache.php:217 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Найпростіший спосіб виправити це - змінити права доступу, використовуючи CHMOD, через FTP-клієнт. Досить встановити глобальні права на запис." #: wp-cache.php:218 msgid "Writeable:" msgstr "Доступно для запису:" #: wp-cache.php:219 msgid "Readonly:" msgstr "Тільки читання:" #: wp-cache.php:231 #, php-format msgid "Warning! %s is writeable!" msgstr "Увага! Папка %s доступна для запису!" #: wp-cache.php:232 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Ви повинні змінити права на папку %s. Щоб зробити це - скористайтеся FTP-клієнтом або наступною командою:" #: wp-cache.php:240 msgid "Mobile rewrite rules detected" msgstr "Виявлена підтримка мобільних пристроїв" #: wp-cache.php:241 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Для більш продуктивної роботи сайту, Вам варто включити опцію \"Підтримка мобільних пристроїв\" або видалити цей запис із правил ст. Htaccess. Знайдіть такий текст (дві строчки) \"2.0\\MMP|240x320\" і видаліть його." #: wp-cache.php:241 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "На Ваших звичайних відвідувачів це ніяк не відіб'ється, а ось використовують мобільні пристрої для веб-серфінгу не будуть отримувати кешовані сторінки (якщо опція відключена)." #: wp-cache.php:247 #: wp-cache.php:258 msgid "Rewrite rules must be updated" msgstr "Права на запис повинні бути оновлені" #: wp-cache.php:248 #: wp-cache.php:259 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Необхідні для роботи плагіна права були змінені або відсутні." #: wp-cache.php:249 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Підтримка блогом мобільних пристроїв вимагає присутності особливих правил у файлі. Htaccess, інакше Ви не зможете використовувати цю опцію. Нижче представлені можливий способи (в порядку складності):" #: wp-cache.php:250 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Переведіть плагін в режим середнього кешування і активуйте мобільних пристроїв." #: wp-cache.php:251 #: wp-cache.php:260 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Прокрутіть сторінку вниз і натисніть кнопку Оновити правила Mod_Rewrite.." #: wp-cache.php:252 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Видаліть всі правила mod_rewrite з файлу %s.htaccess, між # BEGIN WPSuperCache і # END WPSuperCache і обновіть сторінку (відновлення правил запуститься автоматично)." #: wp-cache.php:253 #, php-format msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Додайте правила самостійно. Для цього відкрийте в редакторі файл %s.htaccess і знайдіть код між # BEGIN WPSuperCache і # END WPSuperCache . Ви побачите два схожих блоки коду. Відразу після рядка %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ додайте наступне (таких рядків дві, додайте код і після другої):" #: wp-cache.php:266 msgid "Required to serve compressed supercache files properly." msgstr "Необхідно для правильного стиснення файлів." #: wp-cache.php:266 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Необхідно налаштувати кешування на сторінці плагіна. Користувачі браузера IE7 будуть бачити неоновленою сторінки з кеша без підтримки даного модуля." #: wp-cache.php:266 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Встановіть дату закінчення актуальності сторінок. Користувачі можуть не побачити нову версію кешовані сторінки без даного модуля." #: wp-cache.php:273 msgid "Missing Apache Modules" msgstr "Відсутні модулі Apache" #: wp-cache.php:274 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Наступні модулі Apache відсутні на Вашому сервері. Без них плагін зможе працювати тільки в режимі середнього кешування. У режимі з підтримкою Super Cache Ваші користувачі можуть бачити пошкоджені сторінки або прострочені їх копії." #: wp-cache.php:413 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "\"Увага! Ви намагаєтеся включити стиск, але модуль zlib.output_compression відключений. Дивіться пункт номер 21 розділу \"Опис проблем\" у файлі readme.txt (на англ.)" #: wp-cache.php:501 msgid "WP Super Cache Settings" msgstr "Установки WP Super Cache" #: wp-cache.php:512 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Важливо: Mod_rewrite або Legacy caching відключені. Типово буде завантажуватися сторінка \"Настройки\"." #: wp-cache.php:523 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Файл конфігурацій був змінений, деякі настройки не відповідають вимогам плагіна. Відвідайте сторінку \"Настройки\" щоб виправити це." #: wp-cache.php:540 #: wp-cache.php:614 msgid "Caching must be enabled to use this feature" msgstr "Кешування повинно бути включено, якщо Ви хочете використовувати дану опцію" #: wp-cache.php:542 msgid "Cache Tester" msgstr "Перевірка кешування" #: wp-cache.php:543 msgid "Test your cached website by clicking the test button below." msgstr "Перевірте налаштування кешування свого блога натисканням однієї кнопки." #: wp-cache.php:550 #, php-format msgid "Fetching %s to prime cache: " msgstr "Перевірка сторінки %s в кеші:" #: wp-cache.php:552 #: wp-cache.php:559 #: wp-cache.php:566 msgid "OK" msgstr "Є" #: wp-cache.php:557 #, php-format msgid "Fetching first copy of %s: " msgstr "Перевірка першої копії %s:" #: wp-cache.php:564 #, php-format msgid "Fetching second copy of %s: " msgstr "Перевірка другої копії %s:" #: wp-cache.php:570 msgid "One or more page requests failed:" msgstr "При роботі з кешем сталися помилки:" #: wp-cache.php:589 #: wp-cache.php:590 #, php-format msgid "Page %d: %d (%s)" msgstr "Сторінка %d: %d (%s)" #: wp-cache.php:596 #, php-format msgid "Page 1: %s" msgstr "Сторінка 1: %s" #: wp-cache.php:597 #, php-format msgid "Page 2: %s" msgstr "Сторінка 2 :%s" #: wp-cache.php:598 msgid "The timestamps on both pages match!" msgstr "Тимчасові штампи обох варіантів сторінки збігаються!" #: wp-cache.php:600 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Сторінки не збігаються! Тимчасової штамп відрізняється або не було знайдено!" #: wp-cache.php:606 msgid "Send non-secure (non https) request for homepage" msgstr "Відправити незахищений (не по https) запит для головної сторінки" #: wp-cache.php:607 msgid "Test Cache" msgstr "Перевірити" #: wp-cache.php:632 #: wp-cache.php:755 msgid "Cancel Cache Preload" msgstr "Скасувати загальне кешування" #: wp-cache.php:638 msgid "Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete." msgstr "Загальне кешування за розкладом відключено. Якщо служба зараз запущена, вона не буде завершена поки поточні 100 сторінок Не кешувати." #: wp-cache.php:649 msgid "Scheduled preloading of cache cancelled." msgstr "Загальне кешування за розкладом відключено." #: wp-cache.php:675 #: wp-cache.php:753 msgid "Preload Cache Now" msgstr "Створити загальний кеш зараз" #: wp-cache.php:678 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Загальне кешування відбудеться через 10 секунд." #: wp-cache.php:682 #, php-format msgid "Scheduled preloading of cache in %d minutes" msgstr "Загальне кешування відбудеться через %d хвилин" #: wp-cache.php:686 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "При активації загального кешування, буде створено копію для кожного запису і сторінки Вашого блогу. В цьому режимі створюються статичні сторінки, які потім будуть бачити \"непізнані\" відвідувачі (наприклад, пошукові боти та інші). Це може допомогти в поліпшенні рівня PR Google, так як в основі їх алгоритму лежить і швидкість відгуку веб-сайту." #: wp-cache.php:687 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Проте, при використанні даного виду кешу створюється набагато більше файлів. Рекомендується використовувати такий тип, якщо у Вас дуже багато записів (10 тисяч і більше) на блозі. Особливо це важливо, якщо Ви користуєтеся послугами віртуального хостингу." #: wp-cache.php:688 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "В режимі ’Загальних кешування’ запланована очистка сміття буде видаляти тільки кеш записів простого типу (кеш з Super Cache не буде вилучено). Дана настройка рекомендована для використання." #: wp-cache.php:692 #, php-format msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Оновлювати загальний кеш кожні %s хвилин (введіть 0, щоб відключити, мінімальний допустимий кількість хвилин %d)." #: wp-cache.php:705 msgid "all" msgstr "Весь" #: wp-cache.php:718 #, php-format msgid "Preload %s posts." msgstr "Кешувати %s записи." #: wp-cache.php:725 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Попередній режим (очищення сміття працює не повністю, опція рекомендована до включення.)" #: wp-cache.php:728 msgid "Send me status emails when files are refreshed." msgstr "Відправляти мені повідомлення з повідомленнями про оновлення кешу." #: wp-cache.php:733 msgid "Many emails, 2 emails per 100 posts." msgstr "Високий рівень: 2 повідомлення на 100 записів." #: wp-cache.php:736 msgid "Medium, 1 email per 100 posts." msgstr "Середній рівень: 1 повідомлення на 100 записів." #: wp-cache.php:739 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Низький рівень: 1 e-mail на початку і 1 в кінці кешування." #: wp-cache.php:743 #, php-format msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Оновлення кешу через %d ч %d хв і %d сек." #: wp-cache.php:744 #, php-format msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Повне кешування проіхойдет через %d ч %d хв і %d сек." #: wp-cache.php:750 #, php-format msgid "Currently caching from post %d to %d." msgstr "В даний моменти кешуються записи з %d з %d." #: wp-cache.php:753 msgid "Update Settings" msgstr "Оновити настройки" #: wp-cache.php:761 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Загальне кешування відключено. Будь повний режим роботи плагіна або зверніться до адміністратора сервера." #: wp-cache.php:776 #: wp-cache.php:865 msgid "Caching" msgstr "Статус кешування" #: wp-cache.php:780 msgid "Cache hits to this website for quick access." msgstr "Кешувати хіти сайту для прискорення доступу." #: wp-cache.php:780 #: wp-cache.php:781 #: wp-cache.php:795 #: wp-cache.php:799 #: wp-cache.php:802 #: wp-cache.php:803 #: wp-cache.php:868 msgid "Recommended" msgstr "Рекомендовано" #: wp-cache.php:781 msgid "Use mod_rewrite to serve cache files." msgstr "Використовувати mod_rewrite для обслуговування кешу." #: wp-cache.php:782 msgid "Use PHP to serve cache files." msgstr "Використовувати PHP для обслуговування кешу." #: wp-cache.php:783 msgid "Legacy page caching." msgstr "Спрощене кешування." #: wp-cache.php:784 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching." msgstr "Використання mod_rewrite допоможе зробити роботу блога швидше, ніж PHP (хоча і цей варіант теж не такий повільний). Цей режим простіше і зручніше, але починаючому користувачеві краще використовувати кешування PHP." #: wp-cache.php:790 msgid "Miscellaneous" msgstr "Різне" #: wp-cache.php:795 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Стискати файли кешу щоб прискорити роботу." #: wp-cache.php:796 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Стиснення кешу вимкнено за замовчуванням, так як може некоректно працювати на деяких хостингах. Включення або Відключення даної опції автоматично чистить тимчасовий кеш." #: wp-cache.php:799 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "Помилка 304. Дана помилка виникає тоді, коли сторінка не була змінена з часу минулого запиту." #: wp-cache.php:800 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "Підтримка помилки 304 відключена за замовчуванням (через проблеми деяких сервісів)." #: wp-cache.php:802 msgid "Don’t cache pages for known users." msgstr "Не кешувати сторінки для відомих користувачів." #: wp-cache.php:803 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Авто перебудова кеша. Гості блогу побачать застарілі версії сторінок кеша поки нові будуть генеруватися." #: wp-cache.php:804 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Розповісти усім, що Ви користуєтеся плагіном WP Super Cache (повідомлення буде розміщено в \"підвалі\" сайту)!" #: wp-cache.php:810 #: wp-cache.php:957 #: wp-cache.php:1473 msgid "Advanced" msgstr "Настройки" #: wp-cache.php:814 msgid "Mobile device support." msgstr "Підтримка мобільних пристроїв" #: wp-cache.php:815 msgid "Clear all cache files when a post or page is published." msgstr "Очищати кеш коли новий запис або сторінка опублікована." #: wp-cache.php:816 msgid "Only refresh current page when comments made." msgstr "Оновлювати сторінку при додаванні нового коментаря до неї" #: wp-cache.php:817 msgid "List the newest cached pages on this page." msgstr "Створити список сторінок в кеші (виводиться на цій сторінці)" #: wp-cache.php:819 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Блокування файлів. Вам швидше за все не знадобиться ця опція, але вона може вирішити проблему малопотужних хостингів. Увага! Включення опції, в окремих випадках, може викликати проблеми в роботі блогу!" #: wp-cache.php:822 msgid "Use object cache to store cached files." msgstr "Використовувати об'єкти кеша для зберігання кешованих файлів." #: wp-cache.php:822 msgid "(Experimental)" msgstr "(Експериментальні установки)" #: wp-cache.php:829 msgid "Note:" msgstr "Важливо:" #: wp-cache.php:831 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Деактивувавши плагін, переконайтеся що папка %s доступна для запису в настройках Вашого сервера, щоб файли плагіна advanced-cache.php і cache-config.php були вилучені в автоматичному режимі (також перевірте наявність прав на запис для цих двох файлів)." #: wp-cache.php:832 #, php-format msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Для довідки дивіться readme.txt (документ на англ.). Там Ви знайдете корисну інформацію щодо використання та видалення плагіна WP Super Cache. " #: wp-cache.php:833 #, php-format msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Все ще потрібна допомога? Дивіться офіційний ЧАВО по плагіну Super Cache (англ.). Також, Ви можете задати своє питання на форумах тех. підтримки (англ.), або ознайомитися з проблемами інших користувачів і запропонованими їм рішеннями. " #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "Оновити" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "Допустимі імена & Заборонені адреси" #: wp-cache.php:868 msgid "Caching On" msgstr "Кешування включено" #: wp-cache.php:869 msgid "Caching Off" msgstr "Кешування вимкнено" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Важливо: рекомендується включити PHP кешування, авто перебудову кешу і підтримку для мобільних пристроїв" #: wp-cache.php:880 msgid "Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Увага: Серед правил mod_rewrite виявлені правила від Supercache. Для роботи з кешем будуть використані саме ці правила. Щоб видалити їх, Вам потрібно вручну відредагувати файл. Htaccess." #: wp-cache.php:892 msgid "Make WordPress Faster" msgstr "Зроби свій блог швидше!" #: wp-cache.php:893 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "Додаток %1$s створений і оновлюється автором %2$s за підтримки багатьох інших." #: wp-cache.php:894 #, php-format msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Відвідайте блог автора плагіна %1$s та його фотоблог на %2$s." #: wp-cache.php:895 #, php-format msgid "Please say hi to him on %s too!" msgstr "Будь ласка, відвідайте %s автора!" #: wp-cache.php:903 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Сторінок в кеші з %1$s: %2$s" #: wp-cache.php:904 msgid "Newest Cached Pages:" msgstr "Нове в кеші:" #: wp-cache.php:908 #, php-format msgid "Cached %s seconds ago" msgstr "Написано в кеш %s секунд назад" #: wp-cache.php:911 msgid "(may not always be accurate on busy sites)" msgstr "(Список не рекомендований для великих сайтів)" #: wp-cache.php:930 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Кешування відбувається за рахунок PHP файлів, що зберігаються в папці плагіна. Вони завантажуються при включенні режиму Supercache. Завантаження відбувається набагато частіше, ніж для решти плагінів WordPress." #: wp-cache.php:931 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Для використання даної опції потрібно знати не тільки PHP, але і WordPress (не на початковому рівні)." #: wp-cache.php:941 msgid "Available Plugins" msgstr "Доступні плагіни" #: wp-cache.php:957 msgid "Easy" msgstr "Кеш" #: wp-cache.php:957 msgid "Tester & Contents" msgstr "Перевірка" #: wp-cache.php:957 msgid "Preload" msgstr "Загальний кеш" #: wp-cache.php:957 msgid "Plugins" msgstr "Додатки" #: wp-cache.php:957 msgid "Debug" msgstr "Обслуговування" #: wp-cache.php:984 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Увага: Перевірка правил WP Super Cache mod_rewrite відключена для блогів мережі поки не буде запущена на головному блозі." #: wp-cache.php:986 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Увага: Перевірка правил WP Super Cache mod_rewrite відключена для блогів мережі поки не буде запущена на головному блозі." #: wp-cache.php:996 msgid "Mod Rewrite Rules" msgstr "Модуль Mod Rewrite" #: wp-cache.php:1002 msgid "WordPress MU Detected" msgstr "Виявлено WordPress MU!" #: wp-cache.php:1002 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "На жаль, mod_rewrite неможливо оновити в автоматичному режимі в WordPress MU. Вам доведеться вручну зробити це: відкрийте файл. Htaccess (розташований в кореневій директорії блога) і додайте наступні правила в нього." #: wp-cache.php:1004 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite не може бути оновлений!" #: wp-cache.php:1005 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Для коректної роботи, у Вашому файлі %s.htaccess повинні бути прописані маркери BEGIN і END. Між ними знаходяться основні правила WordPress mod_rewrite, приклад:" #: wp-cache.php:1007 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Оновлення сторінку коли закінчите редагування файлу.Htaccess." #: wp-cache.php:1011 msgid "Thank you for upgrading." msgstr "Спасибі за оновлення." #: wp-cache.php:1011 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "З моменту останньої встановленої версії плагіна правила mod_rewrite були змінені. На жаль, Вам доведеться вручну видалити старі правила перш ніж нові зароблять. Оновлення цю сторінку коли закінчите редагувати файл.Htaccess. Якщо Ви хочете повністю оновити все самі, то замініть наступний рядок: %1$s на цю: %2$s. Єдина відмінність - це заміна \"HTTP_COOKIE\" на \"HTTP: Cookie\" і \"wordpressuser\" на \"wordpress\". Ці зміни пов'язані з новою версією WordPress 2.5 . Звичайно Ви можете продовжувати працювати зі старими версіями, якщо вистачить сміливості;) " #: wp-cache.php:1015 msgid "Trailing slash check required." msgstr "Необхідна перевірка trailing slash." #: wp-cache.php:1015 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Здається, всі посилання Вашого блогу закінчуються символом \"/\". На жаль, як тільки Ви встановили даний плагін, спрацювала опція, що виявила копії посилань без символу \"/\" на кінці, і тепер вона не може здійснити перенаправлення на вірний адресу. Щоб це виправити це, Ви повинні відредагувати файл.htaccess і додати два нових правила до групи основних правил плагіна Supercache:" #: wp-cache.php:1017 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Щоб подивитися повний список працюючих правил, натисніть кнопку нижче \"Переглянути правила mod_rewrite\"." #: wp-cache.php:1031 msgid "Mod Rewrite rules updated!" msgstr "Правила mod_rewrite оновлені!" #: wp-cache.php:1032 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "Файл %s.htaccess був успішно оновлений, необхідні правила mod_rewrite були додані. Будь ласка, перевірте їх. Вони повинні виглядати так:" #: wp-cache.php:1034 msgid "Mod Rewrite rules must be updated!" msgstr "Правила mod_rewrite повинні бути оновлені!" #: wp-cache.php:1035 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Ваш файл %s.htaccess недоступний для запису (в настройках сервера) і не може бути оновлений в автоматичному режимі. Ви повинні вручну додати нові правила до основних правил WordPress так, як зазначено нижче:" #: wp-cache.php:1040 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Правила mod_rewrite для плагіна WP Super Cache були виявлені у файлі %s.htaccess.
    Натисніть на відповідну кнопку, щоб подивитися строчки. Якщо Ви тільки що оновили плагін, перевірте всі правила. " #: wp-cache.php:1043 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "Між правилами у Вашому файлі. Htaccess і правилами самого плагіна виявлені невідповідності. Це може бути просто зайвий символ у рядку, але Ви повинні особисто порівняти оригінальні правила зі своїми якомога швидше. Натисніть на кнопку ’Оновити правила Mod_Rewrite’, щоб зробити це в автоматичному режимі." #: wp-cache.php:1046 msgid "View Mod_Rewrite Rules" msgstr "Подивитися правила mod_rewrite" #: wp-cache.php:1050 #: wp-cache.php:2287 #, php-format msgid "Rules must be added to %s too:" msgstr "Правила повинні бути також додані до %s:" #: wp-cache.php:1058 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Правила для Gzip-стиснення додані в файл %s.htaccess." #: wp-cache.php:1065 msgid "Fix Configuration" msgstr "Відновити стандартні настройки" #: wp-cache.php:1068 msgid "Restore Default Configuration" msgstr "Відновити налаштування за замовчуванням" #: wp-cache.php:1076 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Перевірка коментарів включена. Перш ніж Ваші коментарі будуть опубліковані пройде якийсь час." #: wp-cache.php:1101 msgid "Lock Down:" msgstr "Закритий режим:" #: wp-cache.php:1101 msgid "Disabled" msgstr "Вимкнуто" #: wp-cache.php:1101 msgid "Enabled" msgstr "Включений" #: wp-cache.php:1102 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Підготуйте свій блог до запланованих сплесків відвідуваності, активувавши даний режим. В активному стані розміщення нових коментарів і записів НЕ буде оновлювати статичні файли в кеші." #: wp-cache.php:1103 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Розробникам: Зробіть свій власний плагін закритого режиму сумісним з нашим, додавши змінну \"WPLOCKDOWN\". Наведений нижче код допоможе Вам адоптувати свій плагін до налаштувань нашого Режиму." #: wp-cache.php:1105 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Вибачте, мій блог тимчасово недоступний. Зайдіть пізніше" #: wp-cache.php:1109 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "Ваш блог використовує Закритий режим. Нові коментарі не оновлюють всі статичні елементи кешу." #: wp-cache.php:1111 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "Ваш блог не використовує Закритий режим. Останні коментарі оновлюють всі статичні елементи кешу." #: wp-cache.php:1117 msgid "Lock Down" msgstr "Закритий режим" #: wp-cache.php:1125 msgid "Directly Cached Files" msgstr "Пряме кешування сторінок" #: wp-cache.php:1183 #, php-format msgid "%s removed!" msgstr "%s знищений!" #: wp-cache.php:1191 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Ви повинні дозволити запис для %s. Але так як це потенційна уразливість, після оновлення сторінки поверніть права на читання." #: wp-cache.php:1193 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "Діректрія %s доступна для запису. Вам слід змінити її права на \"Тільки читання\"." #: wp-cache.php:1207 msgid "Existing direct page" msgstr "Сторінка існує" #: wp-cache.php:1207 msgid "Delete cached file" msgstr "Видалити файли з кешу" #: wp-cache.php:1212 msgid "Add direct page:" msgstr "Додати сторінку в кеш:" #: wp-cache.php:1214 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Даний кеш створюється прямо з папки, де знаходиться Ваш блог (папка %s). Ця опція корисна тільки тоді, коли очікується великий приплив відвідувачів з більш популярного сайту на конкретну сторінку або запис Вашого." #: wp-cache.php:1216 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Наприклад: щоб додати в кеш сторінку%1$sabout/, потрібно прописати %1$sabout/ або /about/. Кеш для сторінки буде створено відразу ж після першого до неї звернення гостем." #: wp-cache.php:1217 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Щоб видалити сторінку з такого кеша, очистіть текстове поле і видаліть файли кешу." #: wp-cache.php:1222 msgid "Update Direct Pages" msgstr "Оновити сторінки" #: wp-cache.php:1260 msgid "Expiry Time & Garbage Collection" msgstr "Прострочені сторінки & Очищення сміття" #: wp-cache.php:1262 msgid "Expire time:" msgstr "Актуальність кешу:" #: wp-cache.php:1263 msgid "seconds" msgstr "Секунд" #: wp-cache.php:1264 msgid "Garbage Collection" msgstr "Очищення сміття" #: wp-cache.php:1264 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Якщо час актуальності кешу більше 1800 секунд (півгодини), то очищення сміття буде запускатися кожні 10 хвилин." #: wp-cache.php:1265 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Повірка та видалення прострочених сторінок кеша займає час, але й залишати такі файли в системі не варто. На великих блогах потрібно виставляти \"час життя\" кожної копії 300 секунд. Ви можете поекспериментувати з налаштуванням і подивитися, скільки прострочених копій сторінок залишається в кеші протягом дня. Оптимальне число таких сторінок не більше 500. Використовуючи кешування з mod_rewrite або PHP, Ви зможете збільшити кількість кешируємой сторінок." #: wp-cache.php:1266 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Встановіть значення на 0, щоб відключити Очищення сміття." #: wp-cache.php:1267 msgid "Change Expiration" msgstr "Змінити час життя копії" #: wp-cache.php:1311 msgid "Rejected User Agents" msgstr "Пошукові та інші боти" #: wp-cache.php:1312 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Щоб заборонити плагіну кешувати запити від пошукових ботів і інших мережевих роботів, введіть їх назви в поле нижче (по одному в рядку). Якщо копія сторінки вже існує в кеші Super Cache, то вона все одно буде відправлена боту." #: wp-cache.php:1319 msgid "Save UA Strings" msgstr "Зберегти налаштування" #: wp-cache.php:1342 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Не кешувати сторінки наступних типів. Перевірте Статтею Кодексу WP (англ.), щоб дізнатися докладніше про типи сторінок." #: wp-cache.php:1345 msgid "Single Posts" msgstr "Записи" #: wp-cache.php:1346 msgid "Pages" msgstr "Сторінки" #: wp-cache.php:1347 msgid "Front Page" msgstr "Основна сторінка" #: wp-cache.php:1348 msgid "Home" msgstr "Домашня сторінка" #: wp-cache.php:1349 msgid "Archives" msgstr "Архіви" #: wp-cache.php:1350 msgid "Tags" msgstr "Мітки" #: wp-cache.php:1351 msgid "Category" msgstr "Рубрики" #: wp-cache.php:1352 msgid "Feeds" msgstr "Фіди" #: wp-cache.php:1353 msgid "Search Pages" msgstr "Сторінки пошуку" #: wp-cache.php:1355 #: wp-cache.php:1483 msgid "Save" msgstr "Зберегти" #: wp-cache.php:1372 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Поле нижче Ви також можете заповнити фрагментами адрес сторінок (або груп сторінок, наприклад, архів за рік/місяць і т.д.), які не будуть кешуватися. Плагін буде сканувати адреси сторінок на предмет наявності в них фрагментів, зазначених нижче, перед кешуванням. " #: wp-cache.php:1378 msgid "Save Strings" msgstr "Зберегти список заборонених фрагментів" #: wp-cache.php:1394 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Поле нижче Ви можете заповнити назвами файлів які будуть кешованими, навіть якщо у їх назві є заборонених до кешуванню фрагменти." #: wp-cache.php:1400 msgid "Save Files" msgstr "Зберегти список файлів" #: wp-cache.php:1445 msgid "Currently logging to: " msgstr "Режим записаний на:" #: wp-cache.php:1455 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Тут можна вирішити деякі проблеми, що виникають при роботі з плагіном, за допомогою налагодження. Ви можете записувати службову інформацію (логи) у файли директорії кешу." #: wp-cache.php:1456 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Отримати доступ до файлу лога просто, але при очищенні кешу лог також буде видалено." #: wp-cache.php:1460 msgid "Debugging" msgstr "Режим відлагодження" #: wp-cache.php:1461 msgid "Logging Type" msgstr "Тип входу" #: wp-cache.php:1461 msgid "Email" msgstr "Email" #: wp-cache.php:1462 msgid "file" msgstr "Файл" #: wp-cache.php:1463 msgid "IP Address" msgstr "Адреса IP" #: wp-cache.php:1463 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(Записує звернення тільки з цього IP. Ваш IP - %s)" #: wp-cache.php:1464 msgid "Log level" msgstr "Рівень логу" #: wp-cache.php:1470 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = найменший, 5 = найбільший, може викликати болше навантаження на сервер)" #: wp-cache.php:1473 msgid "In very rare cases two problems may arise on some blogs:

    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "В особливо рідкісних випадках на блозі можуть статися дві проблеми:
    1. Замість головної сторінки користувачі будуть бачити пропозицію завантажити. Zip архів з нею
    2. Замість головної сторінки може бути додана в кеш зовсім інша (тільки у випадку, якщо Ваш бог використовує наступну структуру посилань /%category%/%postname%/).
    " #: wp-cache.php:1474 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "II’m 99% certain! Помилки, які можуть виникнути при роботі з WP Super Cache, не пов'язані з самим плагіном. Вони виникають в окремих випадках, але Ви можете підстрахуватися, запустивши автоматичну перевірку блогу кожні 5 хвилин. У разі помилки, Вам буде надіслано повідомлення. " #: wp-cache.php:1476 msgid "Check front page every 5 minutes." msgstr "Перевіряти головну сторінку кожні 5 хвилин." #: wp-cache.php:1477 msgid "Front page text" msgstr "Ключовий текст" #: wp-cache.php:1477 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Введіть текст який плагін буде шукати на головній сторінці. Якщо текст не буде виявлений, то кеш автоматично очиститься. Залиште поле порожнім щоб відключити опцію." #: wp-cache.php:1478 msgid "Clear cache on error." msgstr "Очищати кеш при помильці." #: wp-cache.php:1479 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Повідомити адміністратора блогу по завершенню перевірки (корисно при тестуванні на помилки)." #: wp-cache.php:1493 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Помилка: стиснення GZIP увімкнено, вимкніть його якщо хочете запустити wp-cache." #: wp-cache.php:1540 #: wp-cache.php:1702 msgid "Warning" msgstr "Увага" #: wp-cache.php:1540 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "Стиснення GZIP включено в настройках WordPress, плагін не буде працювати до тих пір, поки Ви не відключите gzip." #: wp-cache.php:1598 #: wp-cache.php:1603 #: wp-cache.php:1635 #: wp-cache.php:1640 #: wp-cache.php:1646 msgid "Error" msgstr "Помилка" #: wp-cache.php:1598 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Папка ($ cache_path) не існує і не може бути створена в автоматичному режимі. Перевірте права доступу до %s." #: wp-cache.php:1603 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Папка (%1$s) або %2$s повинна бути доступна для запису. Перевірте права доступу." #: wp-cache.php:1635 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Конфігураційний файл WP-Cache (%s) може бути недійсний і недоступний для запису. Будь ласка, видаліть його вручну і обновіть сторінку." #: wp-cache.php:1640 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Конфігураційний файл відсутній, а папка %1$s (%2$s) недоступна для запису. Перевірте права доступу." #: wp-cache.php:1646 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Файл WP-Cache (%s) не був знайдений. Перевірте, завершили Ви установку плагіна." #: wp-cache.php:1702 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php не існує або не може бути оновлений в автоматичному режимі." #: wp-cache.php:1703 msgid "1. If it already exists please delete the file first." msgstr "1. Якщо він вже існує в папках Вашого блога, видаліть його." #: wp-cache.php:1704 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Змініть права доступу до %1$s, щоб можна було записати дані в автоматичному режимі (права повинні бути: chmod 777 %1$s) перевірте правильність заданих прав і обновіть сторінку. Це тимчасове умова, після оновлення сторінки права доступу потрібно повернути на колишні (з 777 на 755). " #: wp-cache.php:1705 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Оновлення сторінку, файл %s/advanced-cache.php оновиться сам" #: wp-cache.php:1706 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Якщо це не спрацювало, переконайтеся що %s/advanced-cache.php точно не існує:" #: wp-cache.php:1707 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Відкрийте файл %1$s$wp_cache_file в текстовому редакторі.
  • 2. Змініть рядок CACHEHOME на %2$s
  • 3. Збережіть файл і скопіюйте в %3$s, потім оновіть сторінку.
    • " #: wp-cache.php:1730 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    Параметр WP_CACHE не активований

    Даний параметр повинен бути активований для того, щоб WordPress міг коректно працювати з файлами кеша. В даний момент він відключений. Щоб включити його, відкрийте файл wp-config.php і додайте в нього наступний рядок:

    define('WP_CACHE', true);

    " #: wp-cache.php:1732 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Помилка: Мінлива WP_CACHE не активована у файлі загальних конфігурацій wp-config.php." #: wp-cache.php:1733 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Відредагуйте код %s і додайте наступну строчку:
    define('WP_CACHE', true);
    Інакше, WP-Cache не зможе запуститися.." #: wp-cache.php:1737 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    Мінлива WP_CACHE добавлена в файл конфігурацій wp-config.php

    Якщо Ви досі бачите це повідомлення, то звіртеся з пунктом 5 ЧАВО (на англ.). Рядок із WP_CACHE повинна бути розміщена вище." #: wp-cache.php:1759 msgid "Cache Contents" msgstr "Стан кешу" #: wp-cache.php:1762 msgid "Object cache in use. No cache listing available." msgstr "Список кешування недоступний." #: wp-cache.php:1786 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Видалення файлів Super Cache:%s
    " #: wp-cache.php:1803 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Видалення файлів WP-Cache: %s
    " #: wp-cache.php:1868 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Статистика об'єктів в кеші НЕ створюється автоматично. Щоб оновити її вручну натисніть на посилання нижче." #: wp-cache.php:1869 msgid "Regenerate cache stats" msgstr "Оновити статистику кеша" #: wp-cache.php:1871 #, php-format msgid "Cache stats last generated: %s minutes ago." msgstr "Статистика об'єктів в кеші останній раз створено: %s мин назад." #: wp-cache.php:1877 msgid "WP-Cache" msgstr "Стан WP-Cache" #: wp-cache.php:1878 #: wp-cache.php:1894 #, php-format msgid "%s Cached Pages" msgstr "%s сторінок в кеші" #: wp-cache.php:1879 #: wp-cache.php:1899 #, php-format msgid "%s Expired Pages" msgstr "%s сторінок прострочено" #: wp-cache.php:1893 msgid "WP-Super-Cache" msgstr "Стан WP-Super-Cache" #: wp-cache.php:1904 msgid "Fresh WP-Cached Files" msgstr "Нові файли WP-Cache" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "URI" msgstr "АДРЕСА" #: wp-cache.php:1905 #: wp-cache.php:1921 msgid "Key" msgstr "Ключ" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Age" msgstr "Вік" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Delete" msgstr "Видалити" #: wp-cache.php:1920 msgid "Stale WP-Cached Files" msgstr "Старі файли WP-Cache" #: wp-cache.php:1936 msgid "Fresh Super Cached Files" msgstr "Нові файли Super Cache" #: wp-cache.php:1952 msgid "Stale Super Cached Files" msgstr "Старі файли Super Cache" #: wp-cache.php:1968 msgid "Hide file list" msgstr "Прибрати список" #: wp-cache.php:1970 msgid "Too many cached files, no listing possible." msgstr "Надто багато об'єктів в кеші, створення списку неможливо." #: wp-cache.php:1972 msgid "List all cached files" msgstr "Список кешованих файлів" #: wp-cache.php:1978 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Очищення сміття
    Попереднє очищення було%s хвилин тому
    " #: wp-cache.php:1979 #, php-format msgid "Next GC in %s minutes" msgstr "Наступне очищення буде через%s хвилин" #: wp-cache.php:1982 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Прострочений кеш - це сторінки, створені більш ніж %s секунд тому. Не дивлячись на свій статус, вони використовуються в загальному кеші і періодично видаляються." #: wp-cache.php:1993 msgid "Delete Expired" msgstr "Видалити прострочений кеш" #: wp-cache.php:1999 #: wp-cache.php:2011 #: wp-cache.php:2174 msgid "Delete Cache" msgstr "Видалити весь кеш" #: wp-cache.php:2011 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Видалити файли Super Cache (у новому вікні)" #: wp-cache.php:2150 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s вдячний плагіну %2$s за проделаннную роботу" #: wp-cache.php:2183 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "Додаток WP Super Cache повинен бути налаштований! Щоб активувати його і налаштувати, перейдіть на сторінку управління плагіном." #: wp-cache.php:2189 msgid "Settings" msgstr "Настройки" #: wp-cache.php:2199 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "Додаток WP Super Cache не активовано. Щоб активувати його, перейдіть на сторінку управління плагіном." #: wp-cache.php:2218 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Головна сторінка стиснута за допомогою gzipped! Видаліть кеш!" #: wp-cache.php:2218 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Сталася помилка! Відвідайте %s щоб видалити кеш!" #: wp-cache.php:2221 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Головна сторінка стиснута за допомогою gzipped! Кеш знищений!" #: wp-cache.php:2221 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Весь кеш для Вашого блогу був очищений, так як плагін помітив помилку на головній сторінці (вона Викачуємо архів). Для перевірки кеш, відвідайте цю стрніцу %s." #: wp-cache.php:2228 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Кеш головної сторінки містить помилку! Видаліть кеш!" #: wp-cache.php:2228 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Сталася помилка, на головній сторінці Вашого блогу не був виявлений ключовою текст \"%2$s\"! Щоб виправити помилку, відвідайте цю сторінку %1$s і уручну очистити кеш." #: wp-cache.php:2231 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Головна сторінка відображається з помилкою! Кеш знищений!" #: wp-cache.php:2231 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Сталася помилка, на головній сторінці Вашого блогу не був виявлений ключовою текст \"%2$s\"! Відвідайте цю сторінку %1$s щоб перевірити кеш." #: wp-cache.php:2236 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Головна сторінка перевірена!" #: wp-cache.php:2236 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "Додаток WP Super Cache щойно перевірив головну сторінку Вашого блогу на предмет помилок. Щоб відключити повідомлення та перевірку відвідайте цю сторінку %s." #: wp-cache.php:2279 msgid "Cannot update .htaccess" msgstr "Не можу оновити файл.Htaccess" #: wp-cache.php:2279 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Файл %s.htaccess не може бути оновлений в автоматичному режимі. Щоб виправити це задайте необхідні для запису права доступу до нього. " #: wp-cache.php:2279 msgid "Refresh this page when the file permissions have been modified." msgstr "Оновлення сторінку коли необхідні права доступу будуть задані." #: wp-cache.php:2279 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Ви також можете редагувати файл %s.htaccess вручну і особисто додати необхідні правила (до наявних там правил WordPress): " #: wp-cache.php:2283 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Щоб плагін міг правильно працювати з статичними html файлами, Ви повинні додати в файл %s.htaccess правила модуля mod_rewrite " #: wp-cache.php:2284 msgid "You can edit the file yourself add the following rules." msgstr "Ви можете вручну відредагувати файл і додати необхідні правила." #: wp-cache.php:2285 msgid " Make sure they appear before any existing WordPress rules. " msgstr "Перевірте, що вони йдуть перед всіма вже існуючими в документі правилами WordPress." #: wp-cache.php:2293 msgid "Update Mod_Rewrite Rules" msgstr "Оновити правила mod_rewrite" #: wp-cache.php:2389 #, php-format msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Загальне кешування почалося" #: wp-cache.php:2391 #, php-format msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Оновлення кеша записів з %2$d до %3$d" #: wp-cache.php:2402 #, php-format msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d кеш записів оновлений" #: wp-cache.php:2402 msgid "Refreshed the following posts:" msgstr "Наступні записи оновлені:" #: wp-cache.php:2411 #, php-format msgid "Scheduling next preload refresh in %d minutes." msgstr "Наступне заплановане оновлення загального кешу через %d хвилин." #: wp-cache.php:2421 #, php-format msgid "[%s] Cache Preload Completed" msgstr "[%s] Загальне кешування завершено" #: wp-cache.php:2421 msgid "Cleaning up old supercache files." msgstr "Видаляти старі файли з кешу Super Cache." #: wp-cache.php:2462 #, php-format msgid "[%s] Preload may have stalled." msgstr "[%s] Загальнe кешування могло бути перервано." #: wp-cache.php:2462 #, php-format msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Загальне кешування було перезапущенe. \n" "%s" #~ msgid "" #~ "Scroll down this page and click the Update Mod_Rewrite Rules button." #~ msgstr "" #~ "Пролистайте страницу вних и нажмите кнопку Обновить правила " #~ "Mod_Rewrite." #~ msgid "WP Super Cache Manager" #~ msgstr "Управление плагином WP Super Cache" #~ msgid "Why your configuration may not be changed" #~ msgstr "Почему конфигурации не могут быть изменены" #~ msgid "Why" #~ msgstr "Почему" #~ msgid "ON" #~ msgstr "ВКЛ" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "Плагины WP Cache и Super Cache включены" #~ msgid "HALF ON" #~ msgstr "РАБОТАЕТ НАПОЛОВИНУ" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Плагин Super Cache отключен, работает только кэшировани WP-Cache" #~ msgid "OFF" #~ msgstr "ВЫКЛ" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "Плагины WP Cache и Super Cache отключены" #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "Восстановление кэша. При включенной опции, гости сайта будут получать " #~ "старые страницы из плагина Super Cache, пока формируются новые. " #~ "Рекомендуется использовать данную опцию только для очень " #~ "посещаемых блогов, где много комментариев. После включения опции в " #~ "настройках \"прямое кэширование страниц\" и \"закрытый режим\" нет нужды " #~ "(они устаревают)" #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "Создавать список новых кэшированных страниц (использовать на свой страх и " #~ "риск, может затормозить сайты с большим количеством посетителей)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s действительно ускоряет Ваш блог. Вы можете сделать его еще " #~ "быстрее*, купив мне подарочную карту сервиса " #~ "Amazon! Можете выбрать \"%3$s\" любое значение, какое хотите. Каждая " #~ "копейка поможет мне!" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "Если Вы не хотите иметь дело с Amazon , то можно сделать пожертвование " #~ "через PayPal. Нажмите кнопку \"Пожертвовать\" или выберите подарок для " #~ "меня из моего списка желаний." #~ msgid "Thanks in advance!" #~ msgstr "Заранее благодарю!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Ладно, он не будет быстрее, но Вы все равно сделаете автора плагина очень " #~ "счастливым!" #~ msgid "Don’t show me this again." #~ msgstr "Не показывать больше это сообщение." #~ msgid "Hide" #~ msgstr "Спрятать" #~ msgid "" #~ "He blogs at %1$s and posts photos at %2$s. He would really appreciate a " #~ "donation to encourage development of this plugin." #~ "
    Even a penny will help." #~ msgstr "" #~ "Блог автора - %1$s, фотоблог - %2$s. Автор плагина будет благодарен любой " #~ "поддержке от Вас.
    Даже копейка может помочь в " #~ "его работе." #~ msgid "Super Cache Compression" #~ msgstr "Сжатие кэша Super Cache" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "" #~ "Сжатие кэша отключено по умолчанию в режиме РАБОТАЕТ НАПОЛОВИНУ." #~ msgid "Super Cache compression is now disabled." #~ msgstr "Сжатие кэша Super Cache теперь отключено." #~ msgid "Super Cache compression is now enabled." #~ msgstr "Сжатие кэша Super Cache теперь включено." #~ msgid "Update Compression" #~ msgstr "Обновить настройки сжатия" #~ msgid "Debug Settings" #~ msgstr "Параметры отладки" #~ msgid "" #~ "

    WP_CACHE constant in wp-config.php set to false

    The WP_CACHE " #~ "constant is defined in your wp-config.php but must be set to true, not " #~ "false for this plugin to work correctly.

    " #~ msgstr "" #~ "

    Значение для WP_CACHE в конфигурационном файле WordPrees wp-config." #~ "php установлено на \"false\"

    Чтобы плагин заработал, значение " #~ "WP_CACHE в wp-config.php нужно поставить на \"true\".

    " #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "" #~ "Вы должны вручную отредактировать файл и добавить необходимые правила." languages/wp-super-cache-tr_TR.po000066600000240574152133035240012743 0ustar00msgid "" msgstr "" "Project-Id-Version: WP Super Cache\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2011-01-05 14:52:03+00:00\n" "PO-Revision-Date: \n" "Last-Translator: Baris Unver \n" "Language-Team: Baris Unver \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Turkish\n" "X-Poedit-Country: TURKEY\n" "X-Poedit-SourceCharset: utf-8\n" #: ossdl-cdn.php:133 msgid "Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull." msgstr "Siteniz muhtemelen çok fazla statik dosya kullanıyordur. Görsel, JavaScript ve CSS dosyaları genellikle başka bir siteden veya bir CDN sisteminden kolayca sunabileceğiniz statik dosyalardır. Bu yüzden bu eklenti wp-content ve wp-includes dizinleri içerisindeki (PHP dosyaları haricindeki) tüm bağlantıları, aşağıda belirleyeceğiniz URL üzerinden sunacaktır. Bu şekilde tüm statik dosyalarınız sanal sunucunuza veya satın aldığınız CDN sistemine \"origin pull\" tekniğiyle aktarılacaktır." #: ossdl-cdn.php:134 #: wp-cache.php:965 msgid "The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin." msgstr "CDN Eşleme Aracı eklentisi, eğer \"origin pull\" yöntemini istemezseniz Amazon S3/Cloudfront sistemlerine dosyaları otomatik olarak yükleyecektir. Yardıma ihtiyacınız olursa, eklenti destek forumunu kullanabilirsiniz (İngilizcedir)." #: ossdl-cdn.php:135 msgid "WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes." msgstr "UYARI: CDN hizmetinizin düzgün şekilde çalışıp çalışmadığını, %s gibi statik dosyaları önce bir test ederek anlayabilirsiniz." #: ossdl-cdn.php:136 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "Çok siteli bir yapıya sahipseniz, her site için farklı CDN adresleri verebilirsiniz." #: ossdl-cdn.php:144 msgid "Enable CDN Support" msgstr "CDN Desteğini Etkinleştir" #: ossdl-cdn.php:147 msgid "Off-site URL" msgstr "Site dışı URL" #: ossdl-cdn.php:150 msgid "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "Yeniden yazım için %1$s yerine kullanılacak yeni adres. Adresin sonuna taksim (/ karakteri) koymayın lütfen..
    Örnek: %2$s." #: ossdl-cdn.php:154 msgid "Include directories" msgstr "Dizinleri dahil et" #: ossdl-cdn.php:157 msgid "Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty." msgstr "Statik dosya eşlemesinde kullanılacak dizinler. Dizinleri virgüllerle ayırabilirsiniz. Varsayılan wp-content, wp-includes şeklindedir, kutu boş bırakılırsa bunlar kullanılacaktır." #: ossdl-cdn.php:161 msgid "Exclude if substring" msgstr "Hariç tutulacaklar" #: ossdl-cdn.php:164 msgid "Excludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "Hariç tutulacak dosyaların uzantılarını buraya girin ve uzantıları virgülle ayırın. (örn. .php, .flv, .do) .php her zaman olmalıdır (ve varsayılandır)." #: ossdl-cdn.php:168 msgid "Additional CNAMES" msgstr "Ek CNAME'ler" #: ossdl-cdn.php:171 msgid "These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$s" msgstr "Bu CNAME'ler, yeniden yazım için %1$s yerine kullanılacaktır (yukarıda belirlediğiniz site dışı adrese ek olarak). Virgülle ayırın. Fazlaca statik dosyaya sahip sayfalar için bu seçenek tarayıcı performansını artırabilir. CNAME'lerin bazen CDN hizmetiniz için de ayarlanması gerekebilir.
    Example: %2$s" #: ossdl-cdn.php:176 msgid "Save Changes" msgstr "Değişiklikleri Kaydet" #: ossdl-cdn.php:178 msgid "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "CDN kullanımı, Mark Kubacki tarafından yazılan OSSDL CDN Off Linker ile sağlanmaktadır" #: wp-cache.php:99 msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Lütfen wp-super-cache/wp-cache-config-sample.php dosyasından %s /wp-cache-config.php dosyasını oluşturun." #: wp-cache.php:162 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Uyarı! PHP Güvenli Mod (Safe Mode) Etkin!" #: wp-cache.php:163 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "SAFE MODE açık olduğu için bu eklentiyi kullanırken sorunlarla karşılaşabilirsiniz." #: wp-cache.php:167 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Sunucunuz, dosya okuma/yazma işlemlerine izin verilmeden önce PHP betiğinin sahibini kontrol edecek şekilde ayarlanmış." #: wp-cache.php:168 msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Siz veya bir yönetici, eklenti betiklerini çalıştıran kullanıcıyı sunucu kullanıcısıyla aynı yaparak sorunu çözebilirsiniz. %s/cache/ dizininin grup sahibi de aynı şekilde değişmelidir. Güvenli Mod yardım sayfasına bakarak ayrıntılı bilgi edinebilirsiniz." #: wp-cache.php:170 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Siz veya başka bir yönetici bunu etkisizleştirmeli. \"güvenli mod\" bilgilendirme sayfasına gidip ayrıntılı bilgi alabilirsiniz. Ne yazık ki, bu ayar .htaccess ile etkisizleştirilemez; php.ini ayar dosyasının düzenlenmesi gerekiyor." #: wp-cache.php:176 msgid "Permlink Structure Error" msgstr "Kalıcı Bağlantı Yapısı Hatası" #: wp-cache.php:177 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Bu eklentinin çalışabilmesi için özel bir adres sisteminin ayarlı olması gerekiyor. Kalıcı Bağlantı Ayarları sayfasına gidip adres sisteminizi ayarlamalısınız." #: wp-cache.php:189 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Warning! Your hostname \"%s\" resolves to %s" #: wp-cache.php:190 msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Sunucunuz, hostname'inizin %s şeklinde çözümlendiğini sanıyor. Bu eklentinin çöp toplama gibi bazı işlevleri (ve WordPress'in yazı zamanlama işlevi) bu şekilde düzgün çalışmayabilir." #: wp-cache.php:191 #: wp-cache.php:205 msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Lütfen readme.txt dosyasında, hata çözme bölümündeki 16. girdiyi okuyun." #: wp-cache.php:204 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Ne yazık ki WordPress, wp-cron.php dosyasını bulamadı. Bu dosya, çöp toplama, yazı zamanlama gibi işlevleri yerine getirmesi için şarttır." #: wp-cache.php:219 msgid "Cannot continue... fix previous problems and retry." msgstr "Devam edilemiyor... önceki sorunları çözün ve tekrar deneyin." #: wp-cache.php:228 msgid "Zlib Output Compression Enabled!" msgstr "Zlib Çıktı Sıkıştırma Etkin!" #: wp-cache.php:229 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP, ziyaretçilerinizin gördüğü verileri sıkıştırıyor. Bunu devre dışı bırakmak, eklentinin önbelleğe aldığı sayfaların tekrar tekrar sıkıştırılmaması için tavsiye edilir. (Hata Giderme bölümünde 21. maddeyi okuyun.) PHP.ini dosyanızı düzenleme yönergeleri için bu sayfayı okuyun." #: wp-cache.php:233 msgid "Mod rewrite may not be installed!" msgstr "Mod rewrite yüklenmemiş olabilir!" #: wp-cache.php:234 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Mod_rewrite yüklü değil gibi gözüküyor. Bazen bu kontrol kesin değildir, özellikle Apache kullanmıyorsanız. Lütfen mümkünse mod_rewrite'ın yüklü olup olmadığını doğrulayın. Eklentinin önbellek dosyalarını sunabilmesi için bu özelliğin bulunması şarttır ama yoksa, eski tarz önbelleklemeyi veya PHP ile önbelleklemeyi de kullanabilirsiniz." #: wp-cache.php:239 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Salt Okunur Mod. Ayarlar değiştirilemez." #: wp-cache.php:240 msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "WP Super Cache ayar dosyası %s/wp-cache-config.php düzenlenemiyor. Düzenleme yapılabilmesi için dosyanın sunucu tarafından yazılabilir olması gerekiyor." #: wp-cache.php:241 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Bunu yapmanın basit bir yolu, dosyanın CHMOD izinlerini kısa bir süreliğine değiştirmektir. CHMOD 777 yapmanız yeterlidir ama sonrasında işlemi geri almayı, izinleri eski haline getirmeyi unutmayın." #: wp-cache.php:242 msgid "Writeable:" msgstr "Yazılabilir:" #: wp-cache.php:243 msgid "Readonly:" msgstr "Salt Okunur:" #: wp-cache.php:255 msgid "Warning! %s is writeable!" msgstr "Uyarı! %s yazılabilir!" #: wp-cache.php:256 msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "%s izinlerini düzenlemeli ve daha kısıtlayıcı hale getirmelisiniz. FTP istemcinizi kullanın veya aşağıdaki komutu uygulayın:" #: wp-cache.php:264 msgid "Mobile rewrite rules detected" msgstr "Tespit edilen mobil yeniden yazım kuralları (rewrite rules)" #: wp-cache.php:265 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "En iyi performans için \"Mobil cihaz desteği\"ni etkinleştirin veya .htaccess dosyasındaki mobil cihazlarla ilgili satırları kaldırın. Bunu yapmak için \"2.0\\ MMP|240x320\" ile başlayan iki satırı silmeniz yeterlidir." #: wp-cache.php:265 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Normal ziyaretçilere bir etkisi olmayacaktır ama mobil kullanıcılar önbelleklenmemiş sayfaları göreceklerdir." #: wp-cache.php:271 #: wp-cache.php:282 msgid "Rewrite rules must be updated" msgstr "Mod_Rewrite kuralları güncellenmeli" #: wp-cache.php:272 #: wp-cache.php:283 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Bu eklentinin ihtiyaç duyduğum yeniden yazım kuralları değişmiş veya yok olmuş." #: wp-cache.php:273 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Mobil cihaz desteği, .htaccess dosyanıza fazladan kural eklenmesini gerektirir. Veya eski tarz önbelleklemeyi kullanabilirsiniz. Seçenekleriniz (zorluk sırasına göre) şunlar:" #: wp-cache.php:274 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Eklentiyi Eski Tarz moduna getirin ve mobil cihaz desteğini aktifleştirin." #: wp-cache.php:275 #: wp-cache.php:284 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Gelişmiş Ayarlar sayfasında aşağılara doğru gidin ve Mod_Rewrite Kurallarını Güncelle düğmesine tıkayın." #: wp-cache.php:276 msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "%s.htaccess dosyanızda, # BEGIN WPSuperCache ile # END WPSuperCache arasındaki satırları (bu iki satır da dahil olmak üzere) silerek eklentinin ürettiği mod_rewrite kurallarını silebilirsiniz. Sayfayı yenilediğinizde eklenti yenisini üretecektir." #: wp-cache.php:277 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Kuralları kendiniz ekleyin. %s.htaccess dosyasını düzenlemek için açın ve # BEGIN WPSuperCache ile # END WPSuperCache arasındaki satırları bulun. Birbirine çok benzeyen iki bölüm olacaktır. %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ satırının hemen altına şu satırları ekleyin: (iki bölüm için de birer defa yapmayı unutmayın)" #: wp-cache.php:290 msgid "Required to serve compressed supercache files properly." msgstr "Sıkıştırılmış supercache dosyalarını sunabilmek için gereklidir." #: wp-cache.php:290 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Super Cache ile önbelleklenmiş sayfalarda, önbellekleme bilgilerinin girilmesi için gereklidir. IE7 kullanıcıları bu olmadan, önbelleğe alınmamış sayfaları görüntülemeye devam ederler." #: wp-cache.php:290 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Super Cache ile önbelleklenmiş sayfalarda son kullanma tarihini belirleyin. Bu modül olmadan ziyaretçiler, sayfayı yenilediklerinde veya yorum bıraktıklarında yeni sayfayı göremeyebilirler." #: wp-cache.php:297 msgid "Missing Apache Modules" msgstr "Kayıp Apache Modülleri" #: wp-cache.php:298 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Aşağıdaki Apache modülleri eksik. Onlar olmadan eklenti eski tarz önbelleklemeyle çalışacaktır. Super Cache modunda ziyaretçileriniz, eski içerikle veya bozuk veriyle karşılaşabilir." #: wp-cache.php:456 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Dikkat! Sıkıştırmayı etkinleştirmek istediniz fakat zlib.output_compression etkin durumda. Beni Oku dosyasının 'Hata Giderme' sayfasında 21 numaralı maddeye göz atın." #: wp-cache.php:547 msgid "WP Super Cache Settings" msgstr "WP Super Cache Ayarları" #: wp-cache.php:558 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Not: Mod_rewrite veya eski tarz önbellekleme etkin. Varsayılan olarak Gelişmiş Ayarlar görüntüleniyor." #: wp-cache.php:569 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Ayarların bulunduğu dosya değiştirildi, bazı değerler yanlış olabilir. \"Ayarlar\" menüsünden sayfayı tekrar yükleyip ayarları sıfırlayın." #: wp-cache.php:594 msgid "Caching must be enabled to use this feature" msgstr "Bu özelliği kullanabilmeniz için önbellekleme etkin olmalıdır." #: wp-cache.php:612 #: wp-cache.php:743 msgid "Cancel Cache Preload" msgstr "Önbellek Önyüklemesi'ni Devre Dışı Bırak" #: wp-cache.php:620 #: wp-cache.php:631 msgid "Scheduled preloading of cache cancelled." msgstr "Önbellek önyüklemesinin zamanlanması iptal edildi." #: wp-cache.php:657 #: wp-cache.php:741 msgid "Preload Cache Now" msgstr "Önbellek Önyüklemesi'ni Şimdi Çalıştır" #: wp-cache.php:661 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Önbellek önyüklemesinin zamanlanması 10 saniye içinde başlıyor." #: wp-cache.php:666 msgid "Scheduled preloading of cache in %d minutes" msgstr "Önbellek önyüklemesinin zamanlanması %d dakika içinde başlıyor" #: wp-cache.php:670 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Bu, site içerisindeki tüm yazı ve sayfaları tek tek önbelleğe alacaktır ve (botlar da dahil olmak üzere) ziyaretçiler bu oluşturulmuş Super Cache'li sayfaları görecektir. Google'daki sıralamanızı yükseltme açısından hız da önemli olduğu için bu seçenek faydalı olabilir." #: wp-cache.php:671 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Yalnız önyükleme çok sayıda dosya oluşturur. Önbellekleme de en yeni yazıdan en eskisine kadar yapılır, dolayısıyla lütfen çok fazla (10 binden fazla) yazınız varsa yalnızca en yeni yazıları önyüklemeye alın. Paylaşımlı hosting'lerde bu özellikle önemlidir." #: wp-cache.php:672 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "Önyükleme Modu'nda düzenli çöp toplama yalnızca bilinen kullanıcılar için eski önbellek dosyalarını temizlemede kullanılır, Super Cache'li dosyalar etkilenmez. Önbellek önyüklemesi yapıldığında bu seçeneğin etkinleştirilmesi önerilir." #: wp-cache.php:676 msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Önyüklenmiş önbelleği her %s dakikada bir yenile. (0 devre dışı bırakır, en az %d dakika yazılmalıdır.)" #: wp-cache.php:689 msgid "all" msgstr "tümü" #: wp-cache.php:702 msgid "Preload %s posts." msgstr "%s yazıyı önyüklemeye al." #: wp-cache.php:709 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Önyükleme modu (çöp toplama yalnızca eski tarz önbelleklemede. Önerilir.)" #: wp-cache.php:712 msgid "Send me status emails when files are refreshed." msgstr "Dosyalar yenilendiğinde bana durum e-postaları gönder." #: wp-cache.php:717 msgid "Many emails, 2 emails per 100 posts." msgstr "Çok: 100 yazı önyüklemesi başına 2 e-posta." #: wp-cache.php:720 msgid "Medium, 1 email per 100 posts." msgstr "Orta: 100 yazı önyüklemesi başına bir e-posta." #: wp-cache.php:723 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Az: Önyüklemenin başında ve sonunda 1'er e-posta." #: wp-cache.php:727 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Önbellek %d saat, %d dakika ve %d saniye sonra yenilenecek." #: wp-cache.php:728 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Önbelleğin tamamı %d saat, %d dakika ve %d saniye sonra yenilenecek." #: wp-cache.php:734 msgid "Currently caching from post %d to %d." msgstr "Şu anda %d ile %d arasındaki yazılar önbelleğe alınıyor." #: wp-cache.php:738 msgid "Page last cached: %s" msgstr "Son önbelleğe alınan sayfa: %s" #: wp-cache.php:741 msgid "Update Settings" msgstr "Ayarları Güncelle" #: wp-cache.php:749 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Önbellek önyüklemesi devre dışı. Lütfen eski tarz önbellekleme seçeneğini etkisizleştirin veya barındırıcı firmanızla görüşün." #: wp-cache.php:766 #: wp-cache.php:862 msgid "Caching" msgstr "Önbellekleme" #: wp-cache.php:770 msgid "Cache hits to this website for quick access." msgstr "Bu siteye gelen ziyaretleri, daha hızlı erişim için önbelleğe alın." #: wp-cache.php:770 #: wp-cache.php:771 #: wp-cache.php:788 #: wp-cache.php:793 #: wp-cache.php:796 #: wp-cache.php:797 #: wp-cache.php:810 #: wp-cache.php:865 msgid "Recommended" msgstr "Önerilen" #: wp-cache.php:771 msgid "Use mod_rewrite to serve cache files." msgstr "Önbellek dosyalarını sunmak için mod_rewrite kullan." #: wp-cache.php:772 msgid "Use PHP to serve cache files." msgstr "Önbellek dosyalarını sunmak için PHP kullan." #: wp-cache.php:773 msgid "Legacy page caching." msgstr "Eski tarz sayfa önbellekleme" #: wp-cache.php:774 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching." msgstr "Mod_rewrite en hızlısıdır. PHP önbellekleme de çok hızlıdır ve kullanımı kolaydır. Eski tarz önbellekleme daha yavaştır ama daha esnektir ve bunun da kullanımı kolaydır. Yeni kullanıcılar PHP önbelleklemeyi denemelidir." #: wp-cache.php:780 msgid "Miscellaneous" msgstr "Diğer" #: wp-cache.php:786 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "Uyarı! Sıkıştırma devre dışı ve gzencode() fonksiyonu bulunamadı." #: wp-cache.php:788 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Sayfalar daha hızlı yüklensin diye sayfaları sıkıştır." #: wp-cache.php:789 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Sıkıştırma varsayılan olarak devre dışıdır çünkü bazı barındırıcılar (hosting firmaları) sıkıştırılmış dosyalarla sorun yaşarlar. Bu özelliği açmak veya kapamak önbelleği temizler." #: wp-cache.php:793 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Not Modified tarayıcı önbelleklemesi. Son gösterimden beri sayfada bir değişiklik olmadıysa belirtir." #: wp-cache.php:794 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "304 desteği varsayılan olarak devre dışıdır çünkü geçmişte GoDaddy, kullanılan header'larla ilgili sorun çıkarıyordu." #: wp-cache.php:796 msgid "Don’t cache pages for known users." msgstr "Giriş yapmış kullanıcılar veya düzenli yorumcular için sayfaların önbellekleme." #: wp-cache.php:797 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Önbellek yenileme. Yeni bir önbellek dosyası oluşturulurken ziyaretçilere eskisi gösterilir." # Digg is not commonly used in our language, thus it's irrevelant to translate the "Digg-proof" expression. I translated this entry as "Tell your visitors that how durable this blog is!" (Baris Unver, translator.) #: wp-cache.php:798 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Ziyaretçilerinize bu blog'un ne kadar dayanıklı olduğunu duyurun! (blog'un footer kısmına bir mesaj eklenir.)" #: wp-cache.php:804 #: wp-cache.php:1053 #: wp-cache.php:1559 msgid "Advanced" msgstr "Gelişmiş" #: wp-cache.php:808 msgid "Mobile device support." msgstr "Mobil aygıt desteği." #: wp-cache.php:809 msgid "Clear all cache files when a post or page is published." msgstr "Bir yazı veya sayfa yayınlandığında önbelleği temizle." #: wp-cache.php:810 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "Fazladan anasayfa kontrolü. (Sık sık anasayfa önbelleklenmesi durur.)" #: wp-cache.php:811 msgid "Only refresh current page when comments made." msgstr "Sadece yorum yapıldığında sayfayı güncelle." #: wp-cache.php:812 msgid "List the newest cached pages on this page." msgstr "Bu sayfada son önbelleklenen sayfaları listele." #: wp-cache.php:814 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Kabaca dosya kilitleme. Muhtemelen buna ihtiyacınız olmayacaktır ama eğer sunucunuz güçsüzse yardımcı olabilir. UYARI: Çok nadir de olsa sunucunuzu kilitleyebilir!" #: wp-cache.php:816 msgid "Late init. Display cached files after WordPress has loaded. Most useful in legacy mode." msgstr "Geç başlatma: WordPress yüklendikten sonra önbellek dosyalarını gösterme. Eski tarz önbelleklemede çok işe yarar." #: wp-cache.php:818 msgid "Use object cache to store cached files." msgstr "Önbellek dosyalarını depolamak için \"object cache\"yi kullan." #: wp-cache.php:818 msgid "(Experimental)" msgstr "(Deneysel)" #: wp-cache.php:825 msgid "Note:" msgstr "Not:" #: wp-cache.php:827 msgid "Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided." msgstr "Bu eklentiyi kaldır: Otomatik olarak kendi artıklarını temizler. Eğer elle müdahale gerektirirse, basit bir yönerge ile yol gösterir." #: wp-cache.php:828 msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Bu eklentiyi kaldırıyorsanız, %sadvanced-cache.php ve cache-config.php dosyaları otomatik olarak kaldırılabilsin. (O dosyaların da yazılabilirliğini kontrol etmek de iyi olur!)" #: wp-cache.php:829 msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Lütfen eklentiyi kaldırmak için readme.txt dosyasındaki yönergelere başvurun. \"How to uninstall WP Super Cache\" bölümünü arayın." #: wp-cache.php:830 msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Yardıma ihtiyacınız mı var? Super Cache BeniOku dosyasını inceleyin. Bu belge; eklentiyi yüklemek için gerekli dokümantasyonu, Sık Sorulan Sorular'ı ve Hata Anlama ipuçlarını içerir. Yardım forumu (İngilizce) de mevcuttur, burada sorununuzun çözümünü bulabilirsiniz." #: wp-cache.php:833 #: wp-cache.php:880 msgid "Update Status" msgstr "Durumu Güncelle" #: wp-cache.php:840 msgid "Accepted Filenames & Rejected URIs" msgstr "Kabul Edilecek Dosyalar & Reddedilecek Adresler" #: wp-cache.php:865 msgid "Caching On" msgstr "Önbellekleme Açık" #: wp-cache.php:866 msgid "Caching Off" msgstr "Önbellekleme Kapalı" #: wp-cache.php:867 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Not: PHP önbelleklemeyi, önbelleğin yenilemeyi ve mobil tarayıcı desteğini etkinleştirir" #: wp-cache.php:877 msgid "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Not: PHP önbellekleme aktif durumda ama Super Cache için var olan mod_rewrite kuralları mevcut ve önbelleklenen sayfalar bu kurallara göre sunulacak. Eğer siteniz düzgün çalışıyorsa bu mesajı dikkate almanıza gerek yok ama .htaccess dosyasından Super Cache önbelleklemeyi sağlayan kuralları kaldırmanızda fayda var." #: wp-cache.php:882 msgid "Cache Tester" msgstr "Önbellek Testi" #: wp-cache.php:883 msgid "Test your cached website by clicking the test button below." msgstr "Önbelleklenmiş sitenizi aşağıdaki test düğmesine basarak sınayın." #: wp-cache.php:889 msgid "Fetching %s to prime cache: " msgstr "Fetching %s to prime cache: " #: wp-cache.php:891 #: wp-cache.php:899 #: wp-cache.php:907 msgid "OK" msgstr "Tamam" #: wp-cache.php:894 msgid "Fetching first copy of %s: " msgstr "%s dosyasının ilk kopyası alınıyor:" #: wp-cache.php:902 msgid "Fetching second copy of %s: " msgstr "%s dosyasının ikinci kopyası alınıyor:" #: wp-cache.php:910 msgid "One or more page requests failed:" msgstr "Bir veya birden fazla sayfa sorgusu başarısız:" #: wp-cache.php:929 #: wp-cache.php:930 msgid "Page %d: %d (%s)" msgstr "Sayfa %d: %d (%s)" #: wp-cache.php:936 msgid "Page 1: %s" msgstr "Sayfa 1: %s" #: wp-cache.php:937 msgid "Page 2: %s" msgstr "Sayfa 2: %s" #: wp-cache.php:938 msgid "The timestamps on both pages match!" msgstr "İki sayfanın zaman damgaları uyuşuyor!" #: wp-cache.php:940 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Sayfalar birbirini tutmuyor! Zaman damgaları birbirinden farklı veya bulunamadı!" #: wp-cache.php:947 msgid "Send non-secure (non https) request for homepage" msgstr "Güvenliksiz (https'siz) anasayfa sorgusu gönder" #: wp-cache.php:948 msgid "Test Cache" msgstr "Önbelleği Test Et" #: wp-cache.php:952 msgid "Delete Cached Pages" msgstr "Önbelleğe Alınan Sayfaları Sil" #: wp-cache.php:953 msgid "Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below." msgstr "Önbelleklenen sayfalar, sunucunuzda HTML ve PHP sayfaları halinde depolanır. Bunları silmek isterseniz aşağıdaki düğmeye tıklayın." #: wp-cache.php:956 #: wp-cache.php:2089 #: wp-cache.php:2101 #: wp-cache.php:2264 msgid "Delete Cache" msgstr "Önbelleği Temizle" #: wp-cache.php:960 msgid "Recommended Links and Plugins" msgstr "Tavsiye Edilen Bağlantılar ve Eklentiler" #: wp-cache.php:961 msgid "Caching is only one part of making a website faster. Here are some other plugins that will help:" msgstr "Önbellekleme, bir siteyi hızlandırmak için atılan adımlardan yalnızca bir tanesidir. Sitenizi hızlandırmaya yardımcı olacak başka eklentiler de mevcuttur:" #: wp-cache.php:962 msgid "WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together." msgstr "WP Minify, CSS ve JavaScript dosyalarını birleştirerek sitenize yapılan HTTP sorgularını azaltır. Alternatif olarak, önbelleklenen sayfaları sıkıştıran bir Super Cache eklentisi olan WPSCMin'i kullanabilirsiniz. Ama bu eklenti JS ve CSS dosyalarını birleştirmez." #: wp-cache.php:963 msgid "Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix." msgstr "Yahoo! Yslow, Firefox'un Firebug eklentisinin bir alt eklentisidir. Sayfaları analiz etmeye yarar ve yüksek performanslı sayfalarda kullanılan bazı kurallara dayanarak sitenizi hızlandırmak için öneriler sunar. Alternatif olarak, YSlow testi de içeren GTMetrix performans araçlarını deneyebilirsiniz." #: wp-cache.php:964 msgid "Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score." msgstr "Google Kütüphanelerini kullanarak sık kullanılan JavaScript kütüphanelerini oradan yükletebilirsiniz. İlginçtir, bu YSlow skorunuzu düşürebilir." #: wp-cache.php:966 msgid "Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules." msgstr "Yalnızca ileri düzey kullanıcılar için: \"Speed up your site with Caching and cache-control\" isimli belge (İngilizce), sitenizin önbelleklenme sürecini geliştirmek için .htaccess önerileri barındırıyor." #: wp-cache.php:967 msgid "Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others." msgstr "Yalnızca ileri düzey kullanıcılar için: Bir obje önbellekleme yöntemi kullanın. Memcached, XCache, eAcccelerator ve benzeri örnekler mevcuttur." #: wp-cache.php:978 msgid "Make WordPress Faster" msgstr "WordPress'i hızlandır!" #: wp-cache.php:979 msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s, %2$s tarafından geliştirilmiştir ve diğer birçok kullanıcının katkısıyla hala gelişmektedir." #: wp-cache.php:980 msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Blogu %1$s ve fotoğrafları %2$s adreslerindedir." #: wp-cache.php:981 msgid "Please say hi to him on %s too!" msgstr "%s adresinden bi' selam çakmayı da unutmayın!" #: wp-cache.php:982 msgid "Need Help?" msgstr "Yardıma mı İhtiyacınız Var?" #: wp-cache.php:984 msgid "Installation Help" msgstr "Kurulum Yardımı" #: wp-cache.php:985 msgid "Frequently Asked Questions" msgstr "Sık Sorulan Sorular" #: wp-cache.php:986 msgid "Support Forum" msgstr "Destek Forumu" #: wp-cache.php:988 msgid "Rate This Plugin!" msgstr "Bu Eklentiyi Derecelendirin!" #: wp-cache.php:989 msgid "Please rate this plugin and tell me if it works for you or not. It really helps development." msgstr "Lütfen eklentinin işinize yarayıp yaramadığını derecelendirin. Eklentinin gelişimine katkıda bulunmuş olacaksınız." #: wp-cache.php:998 msgid "Cached pages since %1$s : %2$s" msgstr "%1$s 'den/'dan beri önbelleklenen sayfalar: %2$s" #: wp-cache.php:999 msgid "Newest Cached Pages:" msgstr "Son Önbelleklenen Sayfalar:" #: wp-cache.php:1003 msgid "Cached %s seconds ago" msgstr "%s saniye önce önbelleklendi" #: wp-cache.php:1006 msgid "(may not always be accurate on busy sites)" msgstr "(çok ziyaret edilen sitelerde tam olarak doğru olmayabilir)" #: wp-cache.php:1025 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Bu eklentiler, WP Super Cache eklenti dizininin içerisinde bir başka eklentiler klasöründe bulunan PHP betikleridir. Etkinleştirildiğinde, WP Super Cache yüklendikten hemen sonra yüklenirler." #: wp-cache.php:1026 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Bu ileri düzey bir özelliktir ve PHP ile WordPress konusunda engin bilgi ve tecrübeye sahip kişiler tarafından yaratılmalıdır." #: wp-cache.php:1036 msgid "Available Plugins" msgstr "Mevcut Eklentiler" #: wp-cache.php:1053 msgid "Easy" msgstr "Kolay" #: wp-cache.php:1053 msgid "CDN" msgstr "CDN" #: wp-cache.php:1053 msgid "Contents" msgstr "İçerik" #: wp-cache.php:1053 msgid "Preload" msgstr "Önyükleme" #: wp-cache.php:1053 msgid "Plugins" msgstr "Eklentiler" #: wp-cache.php:1053 msgid "Debug" msgstr "Hata Ayıklama" #: wp-cache.php:1084 msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Not: WP Super Cache mod_rewrite kural kontrolleri, blog ağının ana sitesi haricinde devre dışıdır." #: wp-cache.php:1086 msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Not: WP Super Cache mod_rewrite kural kontrolleri, blog ağının ana sitesi haricinde devre dışıdır." #: wp-cache.php:1096 msgid "Mod Rewrite Rules" msgstr "Mod_Rewrite Kuralları" #: wp-cache.php:1102 msgid "WordPress MU Detected" msgstr "WordPress MU Saptandı" #: wp-cache.php:1102 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Ne yazık ki, WordPress MU ile çalışırken mod_rewrite kuralları otomatik olarak güncellenememektedir. Lütfen .htaccess dosyanızı açın ve aşağıdaki mod_rewrite kurallarını, diğer kuralların üstüne yerleştirin." #: wp-cache.php:1104 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod_Rewrite kuralları güncellenemiyor!" #: wp-cache.php:1105 msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Kuralların otomatik olarak güncellenebilmesi için %s.htaccess dosyası içerisindeki kurallar BEGIN ve END yorum satırlarının arasında bulunmalıdır. Aşağıdaki gibi gözükürler ve WordPress'in kendi mod_rewrite kurallarının üstündedirler:" #: wp-cache.php:1107 msgid "Refresh this page when you have updated your .htaccess file." msgstr ".htaccess dosyanızı güncelledikten sonra bu sayfayı yenileyin." #: wp-cache.php:1111 msgid "Thank you for upgrading." msgstr "Yükselttiğiniz için teşekkürler." #: wp-cache.php:1111 msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Eklentiyi yüklediğinizden beri mod_rewrite kuralları değişti. Yenilerinin konabilmesi için öncekileri kaldırmanız gerekiyor. .htaccess dosyanızı düzenledikten sonra bu sayfayı yenileyin. Elle düzenlemek isterseniz, şu satırı şu şekilde değiştirin: %1$s ki şu şekilde gözüksün: %2$s Yapılan değişiklikler şöyle: \"HTTP_COOKIE\" yerine \"HTTP:Cookie\" yazılıyor ve \"wordpressuser\" yerine de \"wordpress\" geliyor. Bu WordPress 2.5 ile ilgili bir değişikliktir ama kendinizi cesur hissediyorsanız önceki sürümlerle de uyumludur." #: wp-cache.php:1115 msgid "Trailing slash check required." msgstr "Son taksim (/ karakteri) kontrolü gerekli." #: wp-cache.php:1115 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Anlaşılan blog sayfalarınızın adreslerinin sonu \"/\" ile bitiyor (buna son taksim denir). Maalesef siz bu eklentiyi yükledikten sonra WordPress içerisinde, \"/\" ile bitmeyen adreslerin \"/\" ile biten sayfalara yönlenmediği bir bug bulundu. Bunu düzeltmek için, .htaccess dosyanızı açıp aşağıdaki kuralları, orada iki grup halinde bulunan Super Cache kurallarına eklemelisiniz:" #: wp-cache.php:1117 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Kuralların nereye konacağını ve tüm kuralları, aşağıdaki \"mod_rewrite kurallarını görüntüle\" düğmesine tıklayarak görebilirsiniz." #: wp-cache.php:1131 msgid "Mod Rewrite rules updated!" msgstr "Mod_Rewrite kuralları güncellendi!" #: wp-cache.php:1132 msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "%s.htaccess dosyası, uygun mod_rewrite kuralları eklenecek şekilde düzenlendi. Lütfen aşağıdakiyle karşılaştırıp doğru olduğunu kontrol edin:" #: wp-cache.php:1134 msgid "Mod Rewrite rules must be updated!" msgstr "Mod_Rewrite kuralları güncellenmeli!" #: wp-cache.php:1135 msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "%s.htaccess dosyanız sunucunuz tarafından düzenlenemiyor ama gerekli mod_rewrite kurallarının düzenlenmesi şart. Dosya içerisindeki normal WordPress kurallarının üstüne yazılması gereken kodlar şu şekilde:" #: wp-cache.php:1140 msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "%s.htaccess dosyanızda WP Super Cache'nin mod_rewrite kuralları saptandı.
    Aşağıdaki bağlantıya tıklayarak dosyaya hangi satırların eklendiğini görüntüleyebilirsiniz. Eğer eklentinin sürümünü güncellediyseniz, bu kuralların eklenip eklenmediğini kontrol etmelisiniz." #: wp-cache.php:1143 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "Eklentinin yazmış olması gereken ile .htaccess dosyanızda var olan mod_rewrite kurallarının birbirinden farklı olduğu saptandı. Arada boşluk veya boş satır farkları da olsa, dosyada yazılı kurallarla olması gereken kuralları karşılaştırmanızı öneririz. \"Mod_rewrite Kurallarını Güncelle\" düğmesine tıklayıp kuralları güncelleyebilirsiniz." #: wp-cache.php:1146 msgid "View Mod_Rewrite Rules" msgstr "Mod_Rewrite Kurallarını Görüntüle" #: wp-cache.php:1150 #: wp-cache.php:2380 msgid "Rules must be added to %s too:" msgstr "Kurallar %s dosyasına da eklenmeli:" #: wp-cache.php:1158 msgid "Gzip encoding rules in %s.htaccess created." msgstr "%s.htaccess dosyasında gzip'leme kuralları oluşturuldu." #: wp-cache.php:1165 msgid "Fix Configuration" msgstr "Ayarları Düzelt" #: wp-cache.php:1168 msgid "Restore Default Configuration" msgstr "Varsayılan Ayarları Geri Yükle" #: wp-cache.php:1176 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Yorum onaylama sistemi etkin; yorumunuzun yayınlanması biraz zaman alabilir." #: wp-cache.php:1201 msgid "Lock Down:" msgstr "Tecrit:" #: wp-cache.php:1201 #: plugins/awaitingmoderation.php:35 #: plugins/badbehaviour.php:66 #: plugins/domain-mapping.php:61 msgid "Disabled" msgstr "Etkisiz" #: wp-cache.php:1201 #: plugins/awaitingmoderation.php:34 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:60 msgid "Enabled" msgstr "Etkin" #: wp-cache.php:1202 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Büyük ziyaretçi akınları için tecrit modunu etkinleştirebilirsiniz. Etkinleştirildiğinde; yeni yorum girilse bile sayfa, önbellekli haliyle sunulur yani yeni yorumlar gözükmez, önbellekteki sabit dosya görüntülenir." #: wp-cache.php:1203 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Eklenti Geliştiricilerine: Eklentinizin tecrit moduyla uyum sağlaması için \"WPLOCKDOWN\" sabitini inceleyin. Aşağıdaki kodu eklentinize eklediğinizde eklentiniz WPLOCKDOWN ayarlarıyla uyumlu davranacaktır." #: wp-cache.php:1205 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Üzgünüm; blog'umu kilit altına aldım. Güncellemeler sonra görüntülenebilecek." #: wp-cache.php:1209 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "Blog'unuz tecrit moduna alındı. Yeni yorumlar gelse bile yalnızca Super Cache'nin önbellekli sayfaları görüntülenecek." #: wp-cache.php:1211 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "Blog'unuz tecrit modunda değil. Yeni yorumlar her zamanki gibi Super Cache önbellek dosyalarını yenileyecek." #: wp-cache.php:1214 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 msgid "Disable" msgstr "Etksizileştir" #: wp-cache.php:1214 #: plugins/searchengine.php:74 msgid "Enable" msgstr "Etkinleştir" #: wp-cache.php:1217 msgid "Lock Down" msgstr "Tecrit" #: wp-cache.php:1225 msgid "Directly Cached Files" msgstr "Direkt Önbelleklenen Dosyalar" #: wp-cache.php:1283 msgid "%s removed!" msgstr "%s kaldırıldı!" #: wp-cache.php:1291 #: wp-cache.php:1293 #: plugins/badbehaviour.php:83 msgid "Warning!" msgstr "Uyarı!" #: wp-cache.php:1291 msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Bu ayarı etkinleştirebilmeniz için %s yazılabilir olmalı. Güvenlik açısından sayfanız oluşturulduğunda lütfen yazma ayarlarını geri alın." #: wp-cache.php:1293 msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s yazılabilir durumda. Güvenlik açısından sayfanız oluşturulduktan sonra yazılabilirlik ayarlarını geri almanız önerilir." #: wp-cache.php:1307 msgid "Existing direct page" msgstr "Var olan direkt sayfa" #: wp-cache.php:1307 msgid "Delete cached file" msgstr "Önbellekli dosyayı sil" #: wp-cache.php:1312 msgid "Add direct page:" msgstr "Direkt sayfa ekle:" #: wp-cache.php:1314 msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Direkt olarak önbelleklenen dosyalar %s dizininden, blogunuzun yaşadığı yerden yaratılmıştır. Bu özellik sadece bir anda çok yüksek trafik almayı beklediğiniz zamanlarda işe yarar. (örn. Ekşi Sözlük, İnci Sözlük gibi yerlerden gelen toplu ziyaretler)" #: wp-cache.php:1316 msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Örnek: %1$sabout/ sayfasını önbelleklemek için, %1$shakkinda/ veya /hakkinda/ yazmalısınız. Sayfa, bir sonraki ziyaretçinin ziyaretinde önbelleğe alınacaktır." #: wp-cache.php:1317 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Direkt sayfaları silmek ve önbelleği boşaltmak için metin kutusunu boş bırakın." #: wp-cache.php:1322 msgid "Update Direct Pages" msgstr "Direkt Sayfaları Güncelle" #: wp-cache.php:1360 msgid "Expiry Time & Garbage Collection" msgstr "Zaman Aşımı & Çöp Toplama" #: wp-cache.php:1362 msgid "Expire time:" msgstr "Önbelleklenen dosyaların zaman aşımı:" #: wp-cache.php:1363 msgid "seconds" msgstr "saniye" #: wp-cache.php:1364 msgid "Garbage Collection" msgstr "Çöp Toplama" #: wp-cache.php:1364 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Zaman aşımını 1800 saniyeden (yarım saat) fazla olacak şekilde ayarladıysanız, çöp toplama 10 dakikada bir yapılır. Yarım saatten daha az ise, zaman aşımı süresinden 10 saniye sonra yapılır." #: wp-cache.php:1365 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Süresi dolmuş önbellek sayfalarının silinmesi sunucuyu biraz yorar ama silinmemesi de yorar. Kalabalık bir sitede 300 saniye değeri uygundur. Farklı farklı süreleri test edip, süresi dolan sayfaların ne kadar durduğunu görebilirsiniz. Eski tarz önbelleklemeyi kullanıyorsanız, 500 önbellek sayfasını aşmamaya dikkat edin. PHP veya mod_rewrite ile önbellekleme yapıyorsanız, birkaç kat daha fazla dosya olmasının bir önemi yoktur." #: wp-cache.php:1366 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Çöp toplamayı devre dışı bırakmak için bitiş süresini 0 yapın." #: wp-cache.php:1367 msgid "Change Expiration" msgstr "Zaman Aşımını Değiştir" #: wp-cache.php:1411 msgid "Rejected User Agents" msgstr "Reddedilecek Kullanıcı Temsilcisi (User Agent)" #: wp-cache.php:1412 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." #: wp-cache.php:1419 msgid "Save UA Strings" msgstr "KT Dizgilerini Kaydet" #: wp-cache.php:1442 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Aşağıdaki sayfa türlerini hiçbir zaman önbellekleme. (Koşul Etiketleri (İngilizce) sayfasını ziyaret ederek tüm sayfa türleri hakkında bilgi edinebilirsiniz.)" #: wp-cache.php:1445 msgid "Single Posts" msgstr "Tekil yazı sayfaları" #: wp-cache.php:1446 msgid "Pages" msgstr "Sayfalar" #: wp-cache.php:1447 msgid "Front Page" msgstr "Ön Sayfa" #: wp-cache.php:1448 msgid "Home" msgstr "Anasayfa" #: wp-cache.php:1449 msgid "Archives" msgstr "Arşivler" #: wp-cache.php:1450 msgid "Tags" msgstr "Etiketler" #: wp-cache.php:1451 msgid "Category" msgstr "Kategori sayfaları" #: wp-cache.php:1452 msgid "Feeds" msgstr "Beslemeler" #: wp-cache.php:1453 msgid "Search Pages" msgstr "Arama sayfaları" #: wp-cache.php:1455 #: wp-cache.php:1569 msgid "Save" msgstr "Kaydet" #: wp-cache.php:1472 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Buraya, içeren sayfaları önbelleğe alınmamasını sağlayacak metinler (dosyalar DEĞİL) ekleyin. Örneğin, kalıcı bağlantı yapınızda yıl değişkeni kullandıysanız (yani yazı adreslerinizde yıllar varsa) ve geçen yılın yazılarını önbelleğe almak istemiyorsanız, örneğin '2004' yazmanız yeterli olacaktır. Eklenti, adresin içerisinde bu metinlerin varlığını kontrol edecek ve varsa o sayfayı önbelleğe almayacaktır." #: wp-cache.php:1478 msgid "Save Strings" msgstr "Dizgileri Kaydet" #: wp-cache.php:1494 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Yukarıda belirtilen kurallara uysa da önbelleklenebilmesi için buraya dosya isimleri ekleyebilirsiniz." #: wp-cache.php:1500 msgid "Save Files" msgstr "Dosyaları kaydet" #: wp-cache.php:1541 msgid "Currently logging to: %s" msgstr "Şuraya kayıt yapılıyor: %s" #: wp-cache.php:1544 msgid "Fix problems with the plugin by debugging it here. It can log them to a file in your cache directory." msgstr "Eklentiyle ilgili sorunları, hata ayıklama modunu açarak buraya kaydettirebilirsiniz. Önbellek dizininizde oluşturulacak bir dosyaya kayıt yapılacaktır." #: wp-cache.php:1548 msgid "Debugging" msgstr "Hata Ayıklama" #: wp-cache.php:1548 #: plugins/awaitingmoderation.php:40 #: plugins/badbehaviour.php:71 #: plugins/searchengine.php:69 #: plugins/domain-mapping.php:66 msgid "enabled" msgstr "etkin" #: wp-cache.php:1549 msgid "IP Address" msgstr "IP Adresi" #: wp-cache.php:1549 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(yalnızca bu IP adresinden yapılan raporlama isteklerini kabul et. Şu anki IP adresiniz %s)" #: wp-cache.php:1550 msgid "Log level" msgstr "Raporlama aşaması" #: wp-cache.php:1556 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = hafif, 5 = ağır - sunucuya yük bindirebilir)" #: wp-cache.php:1559 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "Çok nadir durumlarda, bloglarda iki farklı problem baş gösterebiliyor:
    1. Anasayfanın bir zip dosyası halinde inebilir.
    2. Anasayfa olarak sabit bir sayfa göstermeyi seçtiyseniz ve kalıcı bağlantı yapınız /%category%/%postname%/ şeklindeyse, anasayfa diye başka bir sayfa önbelleklenebilir.
    " #: wp-cache.php:1560 msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "WP Super Cache eklentisinde hata bulunmadığından aşağı yukarı eminim, varsa da çok nadir durumlarda görülüyordur ama bu konuda endişeleriniz varsa 5 dakikada bir kontrol edip sitenizin çalışır durumda olduğunu görebilirsiniz. Bir sorun çıkarsa size e-posta yollanacaktır." #: wp-cache.php:1562 msgid "Check front page every 5 minutes." msgstr "5 dakikada bir ön sayfayı kontrol edin." #: wp-cache.php:1563 msgid "Front page text" msgstr "Ön sayfa yazısı" #: wp-cache.php:1563 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Anasayfanızda aranacak metin - eğer bu metin anasayfada bulunamazsa önbellek temizlenir. Devre dışı bırakmak için boş bırakın." #: wp-cache.php:1564 msgid "Clear cache on error." msgstr "Bir hatayla karşılaşıldığında önbelleği temizle." #: wp-cache.php:1565 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Kontroller yapıldığında blog sahibine e-posta gönder. (test etmek için yararlı bir özellik)" #: wp-cache.php:1579 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Hata: GZIP sıkıştırması etkin; wp-cache'i kullanabilmek için lütfen bu ayarı etkisizleştirin." #: wp-cache.php:1626 #: wp-cache.php:1792 msgid "Warning" msgstr "Uyarı" #: wp-cache.php:1626 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "GZIP sıkıştırması Wordpress için etkin durumda, onu etkisizleştirene kadar wp-cache atlanacak." #: wp-cache.php:1688 #: wp-cache.php:1693 #: wp-cache.php:1725 #: wp-cache.php:1730 #: wp-cache.php:1736 msgid "Error" msgstr "Hata" #: wp-cache.php:1688 msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Önbellek dizininiz ($cache_path) bulunamadı ve sunucu tarafından da oluşturulamadı. %s dosya izinlerini kontrol edin." #: wp-cache.php:1693 msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Önbellek dizininiz (%1$s) veya %2$s, eklentinin çalışabilmesi için yazılabilir olmalıdır. Lütfen tekrar kontrol edin." #: wp-cache.php:1725 msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "WP-Cache ayar dosyanız (%s) çok eski ve yenisi de sunucu tarafından oluşturulamıyor. Lütfen dosyayı silip bu sayfayı yenileyin." #: wp-cache.php:1730 msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Ayar dosyası bulunamıyor ve %1$s dizini (%2$s) sunucu tarafından yazılamıyor. Lütfen izinleri kontrol edin." #: wp-cache.php:1736 msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Örnek WP-Cache ayar dosyası (%s) yerinde yok. Lütfen yüklemenizi gözden geçirin." #: wp-cache.php:1792 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php bulunamadı veya güncellenemiyor." #: wp-cache.php:1793 msgid "1. If it already exists please delete the file first." msgstr "1. Eğer hala varsa lütfen ilk satırı silin." #: wp-cache.php:1794 msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. %1$s dizinini, FTP veya sunucu yazılımınızla yazılabilir hale getirin (chmod 777 %1$s) ve sayfayı yenileyin. Bu yalnızca geçici bir işlem; sonrasında ayarı geri almanız gerekecek (bu sefer 777 yerine 755 ile chmod'layın)" #: wp-cache.php:1795 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. %s/advanced-cache.php dosyasını güncellemek için bu sayfayı yenileyin." #: wp-cache.php:1796 msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Eğer bu çalışmazsa, %s/advanced-cache.php dosyasının var olmadığından emin olun:" #: wp-cache.php:1797 msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. %1$s$wp_cache_file dosyasını bir düzenleyicide açın.
  • 2. CACHEHOME metnini %2$s ile değiştirin.
  • 3. Dosyayı kaydedin ve %3$s dizinine aktarın; sonra sayfayı yenileyin.
    • " #: wp-cache.php:1820 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    WP_CACHE sabiti 'false' değerinde

    WP_CACHE sabiti, önbelleklenmiş dosyaları sunmak için gerekli kodun sağlanıp sağlanmayacağına karar verir. Ne yazık ki bu şu anda 'false' konumunda. Lütfen wp-config.php dosyanızı açın ve require_once diye başlayan son satırdan hemen önce bu kodu ekleyin (veya bu kodun bir benzeri varsa onu bu şekilde düzenleyin) :

    define('WP_CACHE', true);

    " #: wp-cache.php:1822 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Hata: WP_CACHE, wp-config.php dosyanızda etkin değil ve ben dosyayı düzenleyemiyorum." #: wp-cache.php:1823 msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "%s kodunu düzenleyin ve şu satırı ekleyin:
    define('WP_CACHE', true);
    Bu olmadan, WP-Cache çalışmayacaktır." #: wp-cache.php:1827 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    WP_CACHE sabiti, wp-config.php dosyasına eklendi

    Bu uyarı mesajını görmeye devam ederseniz lütfen FAQ sayfasındaki 5. maddeye bakın. WP_CACHE ile ilgili satır yukarı kaymış olmalı." #: wp-cache.php:1851 msgid "Cache Contents" msgstr "Önbellek İçeriği" #: wp-cache.php:1854 msgid "Object cache in use. No cache listing available." msgstr "Nesne önbellekleme devrede, listelenecek önbellek yok." #: wp-cache.php:1878 msgid "Deleting supercache file: %s
    " msgstr "Şu supercache dosyası siliniyor: %s
    " #: wp-cache.php:1895 msgid "Deleting wp-cache file: %s
    " msgstr "Şu wp-cache dosyası siliniyor: %s
    " #: wp-cache.php:1960 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Önbellek istatistikleri otomatik olarak üretilmez. Aşağıdaki bağlantıya tıklayarak istatistikleri bu sayfaya yeniden yüklemelisiniz." #: wp-cache.php:1961 msgid "Regenerate cache stats" msgstr "Önbellek istatistiklerini güncelle" #: wp-cache.php:1963 msgid "Cache stats last generated: %s minutes ago." msgstr "Önbellek istatistiklerinin son güncellenişi: %s dakika önce." #: wp-cache.php:1969 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:1970 #: wp-cache.php:1985 msgid "%s Cached Pages" msgstr "%s Önbellekli Dosya" #: wp-cache.php:1971 #: wp-cache.php:1990 msgid "%s Expired Pages" msgstr "%s Süresi Dolmuş Sayfa" #: wp-cache.php:1984 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1994 msgid "Fresh WP-Cached Files" msgstr "Yeni Önbellekli Dosyalar" #: wp-cache.php:1995 #: wp-cache.php:2011 #: wp-cache.php:2027 #: wp-cache.php:2043 msgid "URI" msgstr "Adres" #: wp-cache.php:1995 #: wp-cache.php:2011 msgid "Key" msgstr "Anahtar" #: wp-cache.php:1995 #: wp-cache.php:2011 #: wp-cache.php:2027 #: wp-cache.php:2043 msgid "Age" msgstr "Yaş" #: wp-cache.php:1995 #: wp-cache.php:2011 #: wp-cache.php:2027 #: wp-cache.php:2043 msgid "Delete" msgstr "Sil" #: wp-cache.php:2010 msgid "Stale WP-Cached Files" msgstr "Süresi Dolmuş Önbellekli Dosyalar" #: wp-cache.php:2026 msgid "Fresh Super Cached Files" msgstr "Yeni Süper-Önbellekli Dosyalar" #: wp-cache.php:2042 msgid "Stale Super Cached Files" msgstr "Süresi Dolmuş Süper-Önbellekli Dosyalar" #: wp-cache.php:2058 msgid "Hide file list" msgstr "Dosya listesini gizle" #: wp-cache.php:2060 msgid "Too many cached files, no listing possible." msgstr "Çok fazla önbelleklenen sayfa var, listeleme yapılamaz." #: wp-cache.php:2062 msgid "List all cached files" msgstr "Önbelleğe alınmış tüm dosyaları göster" #: wp-cache.php:2068 msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Çöp Toplama
    Son çöp toplama %s dakika önce yapıldı
    " #: wp-cache.php:2069 msgid "Next GC in %s minutes" msgstr "Sonraki çöp toplama %s dakika sonra" #: wp-cache.php:2072 msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Zaman aşımına uğrayan sayfalar %s saniyeden daha eski. Hala eklenti tarafından kullanılıyorlar ve düzenli aralıklarla siliniyor." #: wp-cache.php:2083 msgid "Delete Expired" msgstr "Süresi Dolan Önbelleği Temizle" #: wp-cache.php:2101 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Super Cache ile önbelleklenmiş dosyaları silin (yeni pencerede açılır)" #: wp-cache.php:2240 msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s, %2$s eklentisi sayesinde dağ gibi sağlam!" #: wp-cache.php:2273 msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache ayarları yapılmamış. Ayarlar sayfasına gidip ayarlarını yapmalısınız." #: wp-cache.php:2279 msgid "Settings" msgstr "Ayarlar" #: wp-cache.php:2289 msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache pasif durumda. Önbelleklemeye devam etmek için lütfen ayarlar sayfasına gidip etkinleştirin." #: wp-cache.php:2292 msgid "Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct." msgstr "Uyarı! WP Super Cache önbellekleme bozuk! advanced-cache.php betiği wp-cache-phase1.php dosyasını yükleyemiyor.

    Lütfen %1$s/advanced-cache.php dosyasını düzenleyin ve %2$swp-cache-phase1.php yolunun doğru olduğundan emin olun." #: wp-cache.php:2311 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Ön sayfa gzip'lendi, lütfen önbelleği boşaltın!" #: wp-cache.php:2311 msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Lütfen sitenizin indirdiği önbellekli ön sayfayı temizlemek için şurayı ziyaret edin: %s" #: wp-cache.php:2314 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Ön sayfa gzip'lendi, Önbellek Temizlendi!" #: wp-cache.php:2314 msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Sitenizin anasayfası şu anda indirildiği için önbelleğiniz temizlendi. Lütfen önbelleğin temizlendiğini doğrulamak için %s sayfasını ziyaret edin." #: wp-cache.php:2321 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Ön sayfa doğru değil! Lütfen önbelleği temizleyin!" #: wp-cache.php:2321 msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Lütfen %1$s sayfasına gidip önbelleğinizi temizleyin çünkü ön sayfanız doğru değil ve \"%2$s\" metni gözükmüyor!" #: wp-cache.php:2324 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Ön sayfa doğru değil! Önbellek Temizlendi!" #: wp-cache.php:2324 msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Önbelleğiniz temizlendi çünkü ana sayfanızda \"%2$s\" metni bulunmuyor. Lütfen %1$s sayfasını ziyaret edip önbelleğin temizlendiğini doğrulayın." #: wp-cache.php:2329 msgid "[%s] Front page check!" msgstr "[%s] Ön sayfa kontrolü!" #: wp-cache.php:2329 msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache anasayfanızı kontrol etti. Bu özelliği devre dışı bırakmak için lütfen %s ziyaret edin." #: wp-cache.php:2372 msgid "Cannot update .htaccess" msgstr ".htaccess güncellenemiyor" #: wp-cache.php:2372 msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "%s.htaccess dosyası sunucu tarafından düzenlenemiyor. Lütfen bu hatayı, chmod kullanarak FTP istemcinizle düzeltin." #: wp-cache.php:2372 msgid "Refresh this page when the file permissions have been modified." msgstr "İzinleri düzenledikten sonra bu sayfayı yenileyin." #: wp-cache.php:2372 msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Veya, %s.htaccess dosyanızı, dosyaya aşağıdaki kodları ekleyerek düzenleyin (en sona yeni bir satır açıp eklein):" #: wp-cache.php:2376 msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Statik HTML dosyalarını sunabilmek için sunucunuzda doğru mod_rewrite kurallarının bulunması ve %s.htaccess adlı bir dosyanın olması gerekiyor." #: wp-cache.php:2377 msgid "You can edit the file yourself add the following rules." msgstr "Dosyayı kendiniz düzenleyebilir ve aşağıdaki kuralları ekleyebilirsiniz." #: wp-cache.php:2378 msgid " Make sure they appear before any existing WordPress rules. " msgstr "WordPress'in oluşturduğu kuralların üstünde durmasına dikkat edin." #: wp-cache.php:2386 msgid "Update Mod_Rewrite Rules" msgstr "Mod_Rewrite Kurallarını Güncelle" #: wp-cache.php:2511 msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Önbellek Önyükleme Başladı" #: wp-cache.php:2513 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] %2$d ile %3$d arasındaki yazılar güncelleniyor" #: wp-cache.php:2531 msgid "[%1$s] Cache Preload Stopped" msgstr "[%1$s] Önbellek Önyüklemesi Durduruldu" #: wp-cache.php:2540 msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d yazı güncellendi" #: wp-cache.php:2540 msgid "Refreshed the following posts:" msgstr "Şu yazılar yenilendi:" #: wp-cache.php:2549 msgid "Scheduling next preload refresh in %d minutes." msgstr "Yeniden önyükleme %d dakika içinde yapılacak." #: wp-cache.php:2559 msgid "[%s] Cache Preload Completed" msgstr "[%s] Önbellek Önyüklemesi Tamamlandı" #: wp-cache.php:2559 msgid "Cleaning up old supercache files." msgstr "Eski supercache dosyaları temizleniyor." #: wp-cache.php:2601 msgid "[%s] Preload may have stalled." msgstr "[%s] Önyükleme takılı kalmış olabilir." #: wp-cache.php:2601 msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Önyükleme yeniden başlatıldı.\n" "%s" #: wp-cache.php:2644 msgid "Supercache Uninstall Problems" msgstr "Super Cache Kaldırma Sorunları" #: wp-cache.php:2644 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" msgstr "" "Değerli Kullanıcı,\n" "\n" "WP Super Cache blogunuzdan kaldırıldı fakat .htaccess dosyanızdaki mod_rewrite kuralları silinmedi.\n" "\n" "Lütfen aşağıdaki dosyayı düzenleyerek 'BEGIN WPSuperCache' ile 'END WPSuperCache' arasındaki kodları temizleyin. Yedek almayı unutmayın!\n" "\n" "%s\n" "\n" "Saygılar,\n" "WP Super Cache Eklentisi\n" "http://wordpress.org/extend/plugins/wp-super-cache/" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Yorumunuz onay bekliyor." #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "Onay Kuyruğunda" #: plugins/awaitingmoderation.php:36 msgid "Enables or disables plugin to Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment." msgstr "Bir yorum gönderildiğinde, \"Yorumunuz onay kuyruğuna alındı.\" yazısını yorumun içinden kaldıran eklentiyi açıp kapatır." #: plugins/awaitingmoderation.php:42 #: plugins/badbehaviour.php:73 #: plugins/searchengine.php:67 #: plugins/domain-mapping.php:68 msgid "disabled" msgstr "ektisizleştirilmiş" #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "Onay Kuyruğu Eklentisi %s" #: plugins/awaitingmoderation.php:45 #: plugins/badbehaviour.php:76 #: plugins/domain-mapping.php:71 msgid "Update" msgstr "Güncelle" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "Bad Behaviour eklentisi bulunamadı. Lütfen tekrar kontrol edin." #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "Bad Behaviour" #: plugins/badbehaviour.php:68 msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Sadece eski tarz önbellekleme desteklenir, sıkıştırma etkin değildir ve \"%s/plugins/bad-behavior/\" dizininde Bad Behavior olması gerekir)" #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "Bad Behaviour desteği %s" #: plugins/searchengine.php:71 msgid "No Adverts for Friends plugin is %s." msgstr "No Adverts for Friends eklentisi %s" #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(friendsadverts.php gerekir) " #: plugins/domain-mapping.php:58 msgid "Domain Mapping" msgstr "Alan Adı Haritalama" #: plugins/domain-mapping.php:63 msgid "Provides support for Domain Mapping plugin to map multiple domains to a blog." msgstr "Alan Adı Haritalama eklentisini destekler." #: plugins/domain-mapping.php:69 msgid "Domain Mapping support is now %s" msgstr "Alan Adı Haritalama desteği %s" #: plugins/domain-mapping.php:83 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Alan Adı Haritalama eklentisi tespit edildi! Lütfen WP Super Cache eklenti ayarları sayfasına gidip ilgili eklentiyi etkinleştirin." #~ msgid "(support for multiple domains on multisite websites) " #~ msgstr "(çoklu sitelerde birden fazla alan adı kullanımına olanak sağlar)" #~ msgid "Tester & Contents" #~ msgstr "Testçi & İçerik" #~ msgid "" #~ "Logging to a file is easier but faces the problem that clearing the cache " #~ "will clear the log file." #~ msgstr "" #~ "Dosyaya raporlama daha kolaydır ama önbellek temizlendiğinde dosya da " #~ "temizlenecektir." #~ msgid "Logging Type" #~ msgstr "Raporlama Türü" #~ msgid "Email" #~ msgstr "E-posta" #~ msgid "file" #~ msgstr "dosya" #~ msgid "WP Super Cache Manager" #~ msgstr "WP Super Cache Yönetimi" #~ msgid "Why your configuration may not be changed" #~ msgstr "Ayarlarınız niye değişmemiş olabilir" #~ msgid "Why" #~ msgstr "Neden" #~ msgid "ON" #~ msgstr "AÇIK" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "WP Cache ve Super Cache etkin" #~ msgid "HALF ON" #~ msgstr "YARI-AÇIK" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Super Cache devre dışı, yalnızca WP-Cache önbelleklemesi çalışıyor." #~ msgid "OFF" #~ msgstr "KAPALI" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "Hem WP Cache, hem Super Cache devre dışı." #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "En son önbelleklenmiş dosyaları görüntüle (Çok ziyaret edilen sitelerde " #~ "bu seçenek sunucuyu yorabilir, dikkatle kullanın.)" #~ msgid "Thanks in advance!" #~ msgstr "Şimdiden teşekkürler!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Tamam, hızlandırmayacak ama eklenti sahibini acayip mutlu edeceksiniz!" #~ msgid "Don’t show me this again." #~ msgstr "Bunu bana bir daha gösterme." #~ msgid "Hide" #~ msgstr "Sakla" #~ msgid "" #~ "He blogs at %1$s, posts photos at %2$s and wishes he " #~ "had more time to read and relax." #~ msgstr "" #~ "%1$s sitesinde blog yazar, %2$s adresinde fotoğraflarını yayınlar ve " #~ "kitap okuyup rahatlamayı diler." #~ msgid "Super Cache Compression" #~ msgstr "Super Cache Sıkıştırması" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "" #~ "YARI AÇIK mod etkin olduğunda sıkıştırma varsayılan olarak " #~ "etkindir." #~ msgid "Super Cache compression is now disabled." #~ msgstr "Super Cache sıkıştırması şu an etkisiz." #~ msgid "Super Cache compression is now enabled." #~ msgstr "Super Cache sıkıştırması şu an etkin." #~ msgid "Update Compression" #~ msgstr "Sıkıştırma Seçeneklerini Güncelle" #~ msgid "Debug Settings" #~ msgstr "Hata Ayıklama Ayarları" #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "Dosyayı kendiniz düzenlemeli ve aşağıdaki kuralları eklemelisiniz." #~ msgid "" #~ "Mobile device support using WordPress Mobile Edition." #~ msgstr "" #~ "WordPress Mobile Edition ile mobil aygıt desteği." languages/wp-super-cache-zh_CN.mo000066600000206313152133035240012700 0ustar00l 0!<1!3n!M!!"`" r"~~"?"=#L#*#7$5P$ $=%b%j5&-&$& &r''v+((u)K'*s*K+,,S-B-wA.%../.K0z1&32Z2:k2n3p45555&6 /6<6N6b6 6636667 7 7?7j7,h88^F9p9+:B:I:_:n:/N;~; ; ;G;`;+F<r<3<<<<x<=g=!==!?B?@@@I@@AXAsAQBB%BCJCdD jDtD {DDDD5D DE/E3E1#FUFFGGGGHuH Ij-IGIII*J?JKKSKoK}wKKNKJL_LntL$LAMJMQMWMtMMMeM%NNOO OO<OgPwP+PP*PPPyP uQbQQR&ST T"Tk"VWWWWEWEX*[XX@Y `Y jYuYLY]Y$6Z[Z zZZZZZb[[\$(\"M\p\!\\ n]y]h^D}^^(^_<_bE_ _y`.aBa0Ea va!a-aka?c Pc [cfclcmcTcHdUhddpleUe3f;fCfUfgfJf.fgdgxBhdh ipi.j0@j qj {jj7jSj?1k<qkkkkk7ljl:mXmvmYmm m n nng)n(n+n,n o.ofLo o/o0o!p?p8pq %q2qqnrs/s:tAtZtpt2uPu Uu;`uquv'v wwTxxyzz<|G"}#j}}S~uf~ ~T<~C+€ KRf %'d WnƄ݄jb`ÅlgRLJiBLj*b[b FɊ7rHM Œ/Eujo*8$eG> )Jf1)Җ9*P/{.3ڗ-1:B J|k03;MZ v<Λ54Ĝ0*:1blQϞ%!GgWߟ tKt|QUUw)#M|(9OZUi. 5Bí ʭ ׭ ;2nr ( 5BGUk! +HZJ' ͱױt^3 +8KE^c9B=Xfδ@5v*K $Q->a"%Ϻj q{ ļ=ڼ4JDB`E[ kAUY23J K gvqTD`eyEDK"Q%t% ]+r 9[U6e >e iPs%l <s`qgVF-e!Tv }?Z171i $?"R$u$F ?DIpw Zg<j %<bzpO>"TgR h u!J'DWoJn)z7$P u.I*>C$6}u*="YV| Qj##,b h3u*~7S6 ybPW3B-p7O V0crk.ys'66R!Nja2T T_* +/{` #*>0ZaWE_Xu[*UJSbWjUUB%?* &5d\b $J16|tI(r`nt`uX!R\t~5P    8 .0 2_   2 5 )% )O &y      gb^N4p F.\1Siq\JmLkux&}]0>CfNBhs  w<B;Z^a8tz $AM8-2+&GKb* )'pve5<#+gc/,XV$vF(OUnV]El IU?9EhA|L|[a!7zok:W   .~{cYy=jM%"nH614l-@iHW?tO{fm#uT,5o% (DCRJK_dDXr~Q_'" Z[YQ=s:!)Pr2Pe}*3RS/9``wxjI; @6703GydqT> Make sure they appear before any existing WordPress rules. %1$s is Stephen Fry proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumCron View is a useful plugin to use when trying to debug garbage collection and preload problems.Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WPSCMin, a Supercache plugin that minifies cached pages by removing whitespaces and extra characters Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.This page explains how to change file permissions.UTC time is %sGarbage collection is the simple act of throwing out your garbage. For this plugin that would be old or stale cached files that may be out of date. New cached files are described as fresh.

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.DO NOT CACHE PAGE secret key: %sError: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAuthor PagesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache TesterCache TimeoutCache expiry cron job failed. Job will run again in 10 seconds.Cache expiry cron job took more than 30 seconds. You should probably run the garbage collector more often.Cache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.CachedCached %s seconds agoCached files are fresh for a limited length of time. You can set that time in the Cache Timeout text box on this page.Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below.Cached pages since %1$s : %2$sCachingCaching OffCaching OnCaching has been disabled on this blog on the Network Admin Sites page.Caching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck for stale cached files at this time (UTC) or starting at this time every interval below.Check for stale cached files every interval seconds.Check front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 600 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published or updated.Clear cache on error.Clock:Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.ContentsCurrently caching from post %d to %d.Currently logging to: %sDear User, WP Super Cache was removed from your blog but the mod_rewrite rules in your .htaccess were not. Please edit the following file and remove the code between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first! %s Regards, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggingDeleteDelete CacheDelete Cache On All BlogsDelete Cached PagesDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cache of the current pageDelete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.Don’t cache pages with GET parameters. (?x=y at the end of a url)EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. Email me when the garbage collection runs.Email the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnable logging on the Debug page here. That should help you track down the problem.EnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExisting direct pageExpired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionExtra homepage checks. (Very occasionally stops homepage caching)FAILEDFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.HH:MMHe blogs at %1$s and posts photos at %2$s.Hide file listHomeHow long should cached pages remain fresh? Set to 0 to disable garbage collection. A good starting point is 3600 seconds.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesInterval:It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match.Local time is %1$sLock DownLock Down:Make WordPress FasterMake known users anonymous so they’re served supercached static files.Make the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile BrowsersMobile PrefixesMobile device support. (External plugin or theme required. See the FAQ for further details.)Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next scheduled garbage collection will be at %s UTCNo Adverts for FriendsNo Adverts for Friends support is now %sNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.Notification EmailsOKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preload tags, categories and other taxonomies.Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Proudly tell the world your server is Stephen Fry proof! (places a message in your blog’s footer)Provides support for No Adverts for Friends.Provides support for Domain Mapping plugin to map multiple domains to a blog.Provides support for WPTouch mobile theme and plugin.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRemove UTF8/blog charset support from .htaccess file. Only necessary if you see odd characters or punctuation looks incorrect. Requires rewrite rules update.Required to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache almost cancelled. It may take up to a minute for it to cancel completely.Scheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.SchedulerScheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSites that want to serve lots of newly generated data should set the Cache Timeout to 60 and use the Timer scheduler set to 90 seconds.Sites where an external data source updates at a particular time every day should set the timeout to 86400 seconds and use the Clock scheduler set appropriately.Sites with lots of static content, no widgets or rss feeds in their sidebar can use a timeout of 86400 seconds or even more and set the timer to something equally long.Sites with widgets and rss feeds in their sidebar should probably use a timeout of 3600 seconds and set the timer to 600 seconds. Stale files will be caught within 10 minutes of going stale.Skip https URLs to avoid "mixed content" errorsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStale cached files are not removed as soon as they become stale. They have to be removed by the garbage collecter. That is why you have to tell the plugin when the garbage collector should run.Supercache Uninstall ProblemsTagsTest CacheTest your cached website by clicking the test button below.Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin.The Timer scheduler tells the plugin to run the garbage collector at regular intervals. When one garbage collection is done, the next run is scheduled.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!There are no best garbage collection settings but here are a few scenarios. Garbage collection is separate to other actions that clear our cached files like leaving a comment or publishing a post.Things you can do:This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.Timer:To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.Use the Timer or Clock schedulers to define when the garbage collector should run.Use the debug system in the Debug tab above. It will tell you what the plugin is doing.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWPTouchWPTouch plugin detected! Please go to the Supercache plugins page and enable the WPTouch helper plugin.WPTouch support is now %sWarningWarning!Warning! %s is writeable!Warning! 304 browser caching is only supported when not using mod_rewrite caching.Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age.Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d[%1$s] Refreshing posts from %2$d to %3$d[%1$s] WP Super Cache GC Report[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledsecondstimezone date formatY-m-d G:i:sProject-Id-Version: Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2012-05-23 10:16:26+00:00 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PO-Revision-Date: 2012-06-20 18:36+0800 Last-Translator: Language-Team: Christopher Meng X-Poedit-Language: Chinese X-Poedit-Country: CHINA 确保它们在已有的 WordPress 规则前。%1$s is Stephen Fry proof thanks to caching by %2$s%1$s 由 %2$s 与众多贡献人员一同开发并维护。%s 已缓存页面%s 已过期页面%s 可被写入。由于存在安全风险，请在页面生成后设置为只读权限。%s 已移除！%s.htaccess 已经被必需的 mod_rewrite 规则更新。请检查它们是否正确。它们应该看上去这样：%s/advanced-cache.php 不存在或者不可被更新。(实验室功能)(仅支持传统模式，并且需要禁用压缩以及确保 Bad Behavior 插件在 "%s/plugins/bad-behavior/" 目录中) (在某些繁忙的大型站点上可能会不准确)(仅记录来自该 IP 的请求，您的 IP 是 %s)1. 如果文件已经存在请先删除它们。2. 将 %1$s 通过 chmod 或者 ftp 客户端设置为可被写入(chmod 777 %1$s) 并刷新本页。这只是一个临时的操作，您需要随后恢复该文件之前的只读权限。(将之前括号内的777改为755，并执行修改后的命令)3. 刷新本页以便更新 %s/advanced-cache.php304 Not Modified 浏览器缓存。声明一个页面自从上一次被请求后还未被变更。304支持默认已禁用，因为 GoDaddy 对有些网页头部处理有问题。常见问题解答安装帮助论坛支持Cron View 是一款调试垃圾回收器和预缓存问题的利器。使用 Google Libraries 允许您从 Google 的服务器加载某些流行 Javascript 库。不过这很荒谬，会降低您的 Yslow 评估分数。WPSCMin，一个可以通过移除空白部分和不必要的字符来缩小缓存页面大小的 Supercache 插件Yahoo! Yslow 是一款火狐浏览器扩展 Firebug 的插件。它会通过一组高性能网页来分析网页的表现并给您改善网页的建议。您也可以在线使用表现检查工具 GTMetrix。这个页面 讲述了如何修改文件权限。UTC时间是%s垃圾回收器 是一个减少垃圾的工具。因为插件产生的缓存会随着时间推移而过期，因此新生成的缓存文件因此是新鲜的。
  • 1. 用文本编辑器打开 %1$s$wp_cache_file 。
  • 2. 修改从 CACHEHOME 到 %2$s 的文字
  • 3. 保存并把文件复制到 %3$s 然后刷新本页。
    • 警告： 请测试一些静态地址比如 %s 以便确保您的 CDN 服务在保存设置前正在工作。只允许高级用户： Speed up your site with Caching and cache-control 讲述了如何使您的网站通过 .htaccess 规则更容易被缓存。只允许高级用户： 安装对象缓存系统。您可以选择 Memcached， XCache， eAcccelerator 或更多。访问这个链接将不会显示缓存内容： %s错误：您的 wp-config.php 文件中 WP_CACHE 未被启用 并且插件无法变更。页面最后缓存： %s警告！您尝试启用压缩但是 zlib.output_compression 参数已被启用。请查看 readme 文件的疑难问题解决部分的第21号解答。本插件需要正确的自定义链接或者固定链接结构才能正常工作。请前往 固定链接设置 页面进行配置。您服务器上的 .htaccess 文件和插件存在不同的重写规则。也许这不重要，但是您应该尽快对比一下。点击’更新 Mod_Rewrite 规则’ 按钮更新这些规则。最简单的方法就是通过 ftp 客户端使用 CHMOD 命令临时修改文件权限。请确保文件全局可被写入，然后就可以了。已被接受的文件名和拒绝的 URI添加跳转页面：在这里添加强制禁止缓存的页面的地址关键字。例如，如果您的地址包含年份并且您不想缓存上一年的文章，您可以直接填写 ’/2004/’。WP-Cache 将会搜索所有符合条件的页面并且不缓存它们。添加想要被缓存的文件名，即使它们出现在上面的被拒绝列表里面。请自行添加规则。编辑 %s.htaccess 并找到从 # BEGIN WPSuperCache 开始到 # END WPSuperCache 结束的这部分代码。请注意有两部分很相似，请在 %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ 下方添加这些规则： (请执行该操作两次，每一部分一次)附加 CNAME 记录高级有效时间另外，您还可以自行编辑您的 %s.htaccess 文件并添加以下代码 (在任何 WordPress 规则之前):存档作者页面可用插件Awaiting ModerationAwaiting Moderation %sBad BehaviorBad Behavior 兼容%s没有找到 Bad Behavior 插件。请检查您的安装。CDNCDN 功能由 Mark Kubacki 编写的 OSSDL CDN Off Linker 插件提供。缓存内容缓存测试缓存超时时间清理到期缓存计划任务执行失败，将会在10秒后重试。缓存到期检查任务已经执行了不少于30秒。您可能需要更经常地运行垃圾回收期。启用缓存以便加快访问。这些对第三方插件的兼容本质都是位于 wp-super-cache 目录内 plugins 子目录内的 PHP 文件，它们在 Supercache 运行时即被加载，比这些第三方插件本身被加载稍微提前。缓存重建。当新缓存生成时调用缓存文件给匿名用户。缓存统计信息不是自动生成的，您需要点击下面的链接来重新生成。缓存统计已于 %s分钟前生成。已缓存%s秒前已缓存缓存都是有一定的新鲜时间的，您可以在本页的 缓存过期时间 文本框进行设置。已缓存的页面以 html 页面或者 PHP 文件的形式存储在您的服务器上。如果您需要删除它们，请使用下方按钮来完成。从 %1$s 已缓存的页面：%2$s缓存功能禁用缓存功能启用缓存功能在该博客的站点网络管理页面上缓存功能已被禁用。缓存只是让站点运行更快的一种方法，这里有一些其它插件提供类似功能：这项功能必须在启用缓存功能后方可使用。取消预加载缓存无法继续... 清修复之前遇到的问题然后重试。无法更新 .htaccess 文件分类修改过期设置每当到了您设定的 (UTC) 时间或者任务间隔检查过期的缓存文件。每隔 interval 秒定期检查过期的缓存文件。每5分钟检查一次首页。检查并删除过期文件的确是一件很难做的事情，但是留着这些文件同样也是不必要的。在一个十分繁忙的站点上您应该设置到期时间为600秒。一天内可以在不同的时候设置不同的数值，访问本页来看看剩下多少到期的文件。如果您使用传统模式进行缓存，如果有可能的话，尽量保持500个以下文件。如果想缓存更多文件，请选择 PHP 模式或者 mod_rewrite 模式进行缓存。正在清理过期的 supercache 文件。当有新文章或页面的发布或更新时清除之前的缓存文件。即使出错也清除缓存。时间：粗略文件锁定。您可能不需要该功能，但是它对小型站点很有帮助。警告！某些情况下您的服务器会被锁住！评论审核已启用。您的评论可能需要一段时间后才能被显示。压缩页面以便让来访者更快浏览。压缩默认已禁用，因为有些主机对压缩过的文件处理有问题。勾选或取消勾选该功能会清除缓存。设置文件已变更，有些数值可能是错误的。请通过 "设置" 菜单重新加载。Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.内容正在缓存文章 %d 到文章 %d。当前登录至：%s亲爱的用户， WP Super Cache 已在您的博客上被移除，但是被 mod_rewrite 调用的 .htaccess 文件中的重定向规则尚未被移除。 请编辑下列文件并且移除 位于 'BEGIN WPSuperCache' 和 'END WPSuperCache' 之间的代码。请首先备份该文件以防不测！ %s 此致， WP Super Cache 插件 http://wordpress.org/extend/plugins/wp-super-cache/调试调试中删除删除缓存删除所有博客上的缓存删除已缓存页面删除已过期文件删除 Super Cache 插件的缓存文件 (新窗口中打开)删除当前页面的缓存删除已缓存文件删除插件的 mod_rewrite 规则，它们是 %s.htaccess 文件中从 # BEGIN WPSuperCache 开始到 # END WPSuperCache 结束的代码块，随后请刷新本页来重建规则。正在删除 supercache 的相关文件： %s
    正在删除 wp-cache 的相关文件： %s
    对开发者：为了使您自己的插件与锁定功能兼容，请检查 "WPLOCKDOWN" 常量。以下代码将会确保您的插件遵守 WPLOCKDOWN 设置。直接缓存的文件Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.禁用已禁用不要缓存例如下列格式的页面。请见 Conditional Tags 文档查看所有格式的具体说明。Domain Mapping已检测到 Domain Mapping 插件！请前往本插件的设置首页启用 Domain Mapping 插件支持。Domain Mapping 兼容%s不要为已知用户缓存。不要为 GET 请求缓存。(地址结尾为?x=y)通用编辑 %s 并添加如下内容：
    define('WP_CACHE', true);
    WP-Cache 将不会被执行    。当垃圾回收器运行时发送邮件通知我。当有检查时发送邮件提醒站点管理员。(对测试十分有用)启用开启 CDN 支持在这里启用调试页面的日志记录。这会帮助您跟踪问题。已启用启用或禁用该插件以便移除当新的待审核评论产生时的 "您的评论正在等待审核。" 提示。错误错误：GZIP 压缩已启用，如果您想启用 wp-cache 请禁用 gzip 压缩。如果是之前有则排除已存在的跳转页面到期文件是那些存在时间大于%s秒的文件。它们仍在被调用并会定期被删除。到期时间和垃圾回收器首页额外检查。 (极少数情况下会停止对首页的缓存)失败Feeds正在抓取 %s 的初始缓存：抓取 %s 的第一份缓存拷贝：抓取 %s 的第二份缓存拷贝：修复设置通过在这里调试来修复故障，调试功能会在缓存文件目录下生成日志。为了更好的访问体验，您应该启用 "手机设备支持" 或者删除 .htaccess. 文件中的手机重写规则。请查找 "2.0\ MMP|240x320" 文本并删除它们。例如：为了缓存 %1$sabout/，您需要访问 %1$sabout/ 或 /about/。缓存文件将会在下次匿名用户来访时再次生成。最新的 Super Cached 文件最新的 WP-Cached 文件首页首页文字缓存全部刷新将会在%d小时%d分%d秒后开始。WordPress 已启用 GZIP 压缩，wp-cache 将会自动忽略直到您禁用 gzip 压缩。垃圾回收器Gzip 编码规则已经添加至 %s.htaccess 文件。小时:分钟他有一个博客 %1$s 并会把自己的照片放在 %2$s。隐藏文件列表主页哪些缓存页面是没有过期的？设置为0可以禁用垃圾回收器。建议数值为3600。IP 地址如果不能工作，请确保文件 %s/advanced-cache.php 不存在：如果要卸载该插件，请确保 %s 目录可被服务器程序写入，这样的话 advanced-cache.php 和 cache-config.php 可被自动删除。(当然也请确保这两个文件可被写入！)在预缓存模式下，垃圾回收器将只会对已知用户清理传统模式产生的旧文件，而不是预缓存的 supercache 文件。当缓存被预缓存时，本功能建议启用。在某些情况下，有以下2个问题可能会发生：
    1. 加载首页时会变成 zip 档案下载。
    2. 如果您的博客使用静态首页，并且固定链接结构类似于 /%category%/%postname%/ ，某些错误的页面会被当做首页进行缓存。
    包含目录任务间隔：貌似 mod_rewrite 模块尚未安装。也许情况并不是这样，尤其是当您不使用 Apache 作为服务器程序的时候。请检查 mod_rewrite 模块是否被加载。这对于 Super Cache 的静态文件的调用是必需的。不过您可以使用 PHP 缓存模式或者传统模式运行本插件。貌似您博客的地址结尾有 "/"。很遗憾，自从您安装本插件时，一个内容重复故障就已经被发现。地址结尾包含 "/" 和不包含 "/" 的页面都显示相同的内容，但没有跳转到正确的地址。要想修复该问题，您需要自行编辑您的 .htaccess 文件并把下面两条规则添加至两组 Super Cache 规则中：密钥延迟初始化。该功能是指在 WordPress 加载后显示已缓存的文件。在传统模式下很有用。传统缓存模式。少量邮件，缓存第一篇发送1封邮件，缓存结束时发送再1封邮件。列出所有已缓存的文件在该页列出所有最新的缓存页面。它会在一个已经登出的浏览器环境中加载首页并检查 html 文件结尾的时间戳，然后再次加载页面并对比时间戳。如果时间戳相符则缓存正在工作。本地时间是 %1$s锁定锁定：让 WordPress 更快让已知用户匿名使他们浏览的内容是缓存文件。如果文本框留空，将会移除直接页面列表中内容的并删除缓存文件。大量邮件，每100篇文章发送2封邮件。适量邮件，每100篇文章发送1封邮件。杂项找不到 Apache 模块手机浏览器手机号段移动设备支持。(需要第三方插件或主题，请访问 FAQ 页面以了解更多信息。)检测到针对手机的重写规则若要对手机用户进行配置，需要额外添加规则到 .htaccess 文件中，或者您启用传统模式。这是您的选择(有些困难)：Mod Rewrite 规则无法更新 Mod Rewrite 规则！Mod Rewrite 规则必须被更新！Mod Rewrite 规则已更新！Mod rewrite 模块可能未安装！Mod_rewrite 方式最快；PHP 方式几乎与前者一样快并且容易部署；传统模式比它们稍慢，但是更灵活且部署简单。建议新用户使用 PHP 缓存模式。需要帮助？需要帮助？请查看 Super Cache 的 readme 文件。它包含了安装文档，常见问题解答以及某些故障排除提示。还有建议您查看论坛支持，您的问题也许已经被解答过了。最新的已缓存页面：下次垃圾收集计划任务将会在 %s UTC 开始No Adverts for FriendsNo Adverts for Friends 兼容%s提示：提示：将会启用 PHP 缓存模式，缓存重建和手机支持注意：由于 Mod_rewrite 模式或者传统模式已启用，默认将显示高级设置选项卡。注意：PHP 缓存模式已启用，但是检测到遗留的 mod_rewrite 规则。已缓存的文件将会被这些规则调用。如果您的站点运行正常，请忽略本提示，否则请自行编辑 .htaccess 文件。注意：除非运行在 主站点，WP Super Cache 的 mod_rewrite 规则检查功能将被禁用 。邮件通知OK对象缓存正处于使用中。没有缓存列表可用。Off-site URL1个或多个页面的请求失败：当某页面有新评论时，只刷新该页面的缓存。PHP 正在压缩发送到来访者的数据。建议禁用该功能，因为本插件已经缓存了压缩后的输出数据而不是重复压缩多次它们。同时请查看 readme 文件的疑难问题解决部分的第21号问题。查看 这个页面 以了解配置 php.ini 的介绍。页面 %d: %d (%s)第一页： %s第二页： %s页面固定链接结构出错请 对这个插件评分 并告诉我您的需求。这对我们的开发真的十分有用。请把 wp-super-cache/wp-cache-config-sample.php 改为 %s /wp-cache-config.php欢迎您在 %s 上与他交流！请查看 readme.txt 中 疑难问题解决部分 的第16号问题请查看 readme.txt 以了解卸载流程。请在文件中搜索 "How to uninstall WP Super Cache"以便快速浏览。请访问 %1$s 以清除您的站点的首页缓存，该缓存是错误的或者缺失文字 "%2$s"！由于您的首页正在被加载，请自行访问 %s 以清除首页的缓存！插件兼容预缓存预缓存 %s 篇文章。立即预加载缓存预缓存已经重新启动。 %s预缓存模式(垃圾回收器只会在传统模式上生效。推荐。)预缓存标签，分类以及其他。预缓存将会创建大量新文件，并且会将所有文章进行缓存。如果您有10000篇以上文章，不建议您使用该功能，尤其是在共享主机上。预缓存功能已禁用。请禁用传统模式或者与您的主机管理员联系。自豪地告诉世界Stephen Fry proof！(在您的博客底部显示一行感谢作者信息)点击查看 No Adverts for Friends 插件的支持。点击查看 Domain Mapping 插件对同主机多站点的支持。点击查看 WPTouch 的手机主题和插件本身的支持。给插件评个分吧！只读模式。设置无法更改。只读：推荐有用的链接和插件缓存将会在 %d小时%d分%d秒后刷新。每%s分钟刷新预缓存文件(设置为0则禁用，至少%d分钟。)当文件权限更改后请刷新本页。当您更新完您的 .htaccess 文件时，请刷新本页。以下文章已被刷新：重新生成缓存统计信息已拒绝的用户代理(User Agent)移除 .htaccess 文件中的 UTF8/blog 字符集。这个功能只适用于当您发现文件中字符不正确时。本功能需要更新重写规则。这是必需的以便能够正确调用缓存文件。该模块的作用是设定 supercache 页面的缓存信息。没有该模块，IE7用户将只会看见旧页面。恢复默认设置重写规则必须被更新规则必须也被添加至 %s ：Sample WP-Cache 设置文件(%s) 不存在。请检查您的安装。保存保存修改保存文件保存保存用户代理(UA)字段预缓存计划任务马上就会被取消，这可能需要花费一点时间。预缓存计划任务已取消预缓存任务在%d秒后启动。预缓存任务在10秒后启动。计划下次预缓存任务将在%d分后开始。滚动查看高级选项卡，找到并点击 更新 Mod_Rewrite 规则 按钮。搜索页面当缓存文件刷新完毕后发送邮件通知。发送不安全的(非 https) 首页请求设定缓存文件的到期时间。没有该模块时，当来访者刷新或者留下评论时可能不会看到新页面。设置到期时间为0秒以便禁用垃圾回收器。设置插件为传统模式并且启用手机支持。设置单一文章有大量新数据产生的站点应该设置缓存超时时间为60并设置定时器时间为90秒。每天有固定更新产生的站点应该设缓存超时时间86400并正确设置时钟时间。有大量静态内容且在侧边栏没有挂件和 rss 输出的站点，应该设置超时时间为86400秒或更长并设置定时器为一个很长的时间。在侧边栏有挂件和 rss 输出的站点应该设置超时时间为3600秒，并设置定时器为600秒。过期缓存将会在10分钟内随时被收集。忽略 https 地址以避免 "mixed content" 错误抱歉，本博客目前处于锁定中，稍后会进行更新。过期的 Super Cached 文件过期的 WP-Cached 文件过期的缓存文件并会被立刻删除。它们会被垃圾回收器清除。这就是您需要对垃圾回收器进行配置的原因。Supercache 卸载问题标签测试缓存点击下面的测试按钮测试缓存效果。这是您将要在首页寻找的文字。如果您找不到，缓存将会被清除。留空则禁用该功能。感谢您的升级。如果您不需要文件自动传输到 CDN 功能(origin pull)，CDN Sync Tool 插件将会帮助有关文件上传至 Amazon S3/Cloudfront 。如果您有意见或者需求，请访问插件支持论坛。定时器 告诉插件间隔多久运行垃圾回收器。当一次回收完毕时，下次任务将会被设计划。WP Super Cache 的设置文件 %s/wp-cache-config.php 无法被变更。这个文件必须被设置为可被写入权限才能正常工作。由于首页缺失 "%2$s" ，所有缓存已被清除。请访问 %1$s 以检查缓存是否已被清除。由于首页正在被加载，您的博客的所有缓存已被清除。请访问 %s 以检查缓存是否已被清除。%s.htaccess 文件无法被服务器变更。请使用 chmod 命令或 ftp 客户端来修正权限。由于下列 Apache 模块缺失，本插件只能运行于传统模式。如果强制在完整的运行模式下，来访者将会浏览不正确的页面。自从您上次安装本插件后，mod_rewrite 规则已变更。非常抱歉，您必须在新规则更新前移除旧版本 supercache 的规则。在您编辑完成 .htaccess 文件后请刷新本页。如果您想要手动升级，修改一下几行: %1$s 比方说是这样： %2$s 其实所有修改都是将 "HTTP_COOKIE" 变为 "HTTP:Cookie" 以及将 "wordpressuser" 变为 "wordpress"。这是 WordPress 2.5 的变化，但是它理论上和旧版本兼容。(如果您愿意尝试的话)页面不相符！时间戳有差异或者不存在！插件需要的重写规则已被更改或者缺失。两个页面的时间戳相符！没有十分完美的垃圾回收器设置，不过它已被单独分离出来，这样清理缓存文件就像留下一条评论或者发布文章一样简单。您可以做的：严格意义上讲这是一个高级功能，您必须十分了解 PHP 和 WordPress 才能正确使用。预缓存的功能是缓存所有已发布的页面和文章。它会创建 supercache 静态文件，这样的话，未知用户(包括搜索引擎蜘蛛)将会获得缓存后的页面。这将帮助您的站点的 Google PR 提升，因为 Google 会把网站的响应速度作为评判网站的标准。这将不会影响电脑用户，但是手机用户将会访问未缓存的页面。定时器:如果要使缓存页面生效，您的服务器必须要有包含正确的 mod_rewrite 规则的 %s.htaccess 文件缓存文件太多，没有列表可用。需要结尾的斜杠检查。URI很遗憾，找不到 wp-cron.php。该文件是垃圾回收器正常工作，WordPress 定时发布任务以及其他活动的关键。很遗憾，在 WordPress 多站点模式下无法自动更新重写规则。请打开您的 .htaccess 文件并在其最上方手动添加下列 mod_rewrite 规则。请前往插件管理页面卸载本插件，插件会自动清除。如果需要您的手动操作，稍后会有提示。更新更新直接链接页面更新 Mod_Rewrite 规则更新设置更新PHP 缓存模式。mod_rewrite 缓存模式。使用对象缓存系统来存储缓存文件。使用 定时器 或 时钟 选项来设定垃圾回收器何时应该运行。在调试选项卡中使用调试工具。这将会告诉您插件正在如何工作。查看 Mod_Rewrite 规则WP Super Cache 设置WP Super Cache 已经检查您的博客的首页。如果您想禁用，请访问 %s 。WP Super Cache 已禁用。请去 插件管理首页 开启缓存功能。WP Super Cache 的 mod rewrite 规则已存在于您的 %s.htaccess 文件中。
    点击下面链接查看新添加进去的内容。如果您已经升级了本插件，确保这些规则符合。WP Super Cache 需要设置。请前往 插件管理页面 设置。WP-CacheWP-Super-CacheWPTouch已检测到 WPTouch 插件！请前往插件设置首页启用 WPTouch 插件支持。WPTouch 兼容%s警告警告!警告！ %s 可被写入！警告！304浏览器缓存功能只有不使用 mod_rewrite 缓存模式时生效。警告！预缓存模式 已激活！Supercache 的缓存文件由于缓存的有效时间而不会被删除。警告！由于未找到 gzencode() 函数，压缩已被禁用。警告！PHP 安全模式已启用！警告！WP Super Cache 缓存功能损坏！advanced-cache.php 无法加载 wp-cache-phase1.php。

    请编辑 %1$s/advanced-cache.php 并确保 %2$swp-cache-phase1.php的路径是正确的。警告！您的主机 "%s" 被解析至 %s已检测到 WordPress 多站点模式WordPress 已被锁定。当产生新评论时，Super Cache 的静态文件将不会被检测到。WordPress 没有被锁定。新的评论将会像往常一样刷新 Super Cache 的静态文件。可写的：您可以对多站点中的每个站点定义不同的 CDN 服务地址。您可以自行编辑该文件并添加下列规则。您可以查看规则时如何生效的并且点击 "View mod_rewrite rules" 链接来测试下方的所有规则。由于启用了安全模式,在插件运行时您可能会遇到问题。您必须确定在 %s.htaccess 文件中，有BEGIN 和 END 标记以便程序能够自动更新规则。比如：您必须将 %s 设置为可被写入才能使用此功能。由于该功能存在安全风险，请在页面生成后设置为只读权限。您或者管理员也许能通过修改插件的用户组属主为服务器软件用户来使得插件正常工作。%s/cache/ 目录的用户组属主同样需要修改。更多信息请访问 PHP 安全模式手册 页面。您或者管理员必须禁用该功能。更多信息请访问 PHP 安全模式手册 。很遗憾这个操作不能在 .htaccess 文件中修改，您必须修改 php.ini 文件。您应该通过 ftp 客户端或者以下命令更改 %s 的权限并确保它被严格限制：您应该在出错前检查页面1和页面2。您的本地服务器设置可能不允许您的网站读取。您的服务器的 %s.htaccess 文件不可被服务器程序写入，但是它需要正确的 mod_rewrite 规则：您的 WP-Cache 设置文件(%s) 已过期且不可被 Web 服务器读取。请删除该文件并刷新本页。您的缓存目录 (%1$s) 不存在且 Web 服务器无法创建。请检查 %1$s 的权限设置。您的缓存目录 (%1$s) 或者 %2$s需要被设置为可写入权限。请检查有关设置。您的评论正在等待审核。在 PHP 代码读取或者写入文件之前，您的服务器程序将会检查其属主。您的服务器认为您的主机解析至 %s。有些服务比如垃圾回收器和定时发布功能将无法正常工作。您的网站可能使用了大量的静态文件。图像，Javascript 和 CSS 文件通常都是可供其他站点或者 CDN 方便调用的静态文件。因此，本插件使用下方您提供的地址替换了站点的所有 wp-content 和 wp-includes 目录地址(PHP 文件除外) 。这样即可以使您复制所有静态内容到独立主机，又可以通过 文件自动传输到 CDN 功能 为文件做镜像到 CDN。Zlib 输出压缩已启用！[%1$s] %2$d 篇文章已刷新[%1$s] 预缓存已开始[%1$s] 预缓存已停止[%1$s] 正在刷新 从 %3$d 到 %4$d 的 %2$s 分类法[%1$s] 正在刷新从 %2$d 到 %3$d 的文章[%1$s] [%1$s] WP Super Cache 垃圾回收器报告[%s] 预缓存完成[%s] 首页检查！[%s] 首页已被 gzip 压缩！缓存已清除！[%s] 首页已经被 gzip 压缩！请清除缓存！[%s] 首页不正确！缓存已清除！[%s] 首页不正确！请清除缓存！[%s] 预缓存可能已失去响应。全部已禁用已启用秒Y-m-d G:i:slanguages/wp-super-cache-de_DE.po000066600000234371152133035240012647 0ustar00# Translation of the WordPress plugin by . # Copyright (C) 2010 # This file is distributed under the same license as the package. # FIRST AUTHOR , 2010. # msgid "" msgstr "" "Project-Id-Version: wp-super-cache 1.2\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2011-02-23 17:57:46+00:00\n" "PO-Revision-Date: 2011-02-24 16:42+0100\n" "Last-Translator: \n" "Language-Team: Blog-Lounge.org \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: en, er,\n" "X-Poedit-Language: German\n" "X-Poedit-Country: GERMANY\n" "X-Poedit-SourceCharset: utf-8\n" #: plugins/badbehaviour.php:47 msgid "Bad Behaviour not found. Please check your install." msgstr "\"Bad Behaviour\" nicht gefunden. Bitte überprüfe deine Installation." #: plugins/badbehaviour.php:63 msgid "Bad Behavior" msgstr "Schlechtes Verhalten (Bad Behavior)" #: plugins/badbehaviour.php:65 #: plugins/awaitingmoderation.php:34 #: plugins/domain-mapping.php:60 #: wp-cache.php:1205 msgid "Enabled" msgstr "Aktiviert" #: plugins/badbehaviour.php:66 #: plugins/awaitingmoderation.php:35 #: plugins/domain-mapping.php:61 #: wp-cache.php:1205 msgid "Disabled" msgstr "Deaktiviert" #: plugins/badbehaviour.php:68 msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Nur Legacy-Caching wird unterstützt, Komprimierung deaktiviert, und benötigt Bad Behavior in \"%s/plugins/bad-behavior/\") " #: plugins/badbehaviour.php:71 #: plugins/awaitingmoderation.php:40 #: plugins/searchengine.php:69 #: plugins/domain-mapping.php:66 #: wp-cache.php:1552 msgid "enabled" msgstr "aktiviert" #: plugins/badbehaviour.php:73 #: plugins/awaitingmoderation.php:42 #: plugins/searchengine.php:67 #: plugins/domain-mapping.php:68 msgid "disabled" msgstr "deaktiviert" #: plugins/badbehaviour.php:74 msgid "Bad Behavior support is now %s" msgstr "\"Bad Behaviour\"-Support ist jetzt %s. " #: plugins/badbehaviour.php:76 #: plugins/awaitingmoderation.php:45 #: plugins/domain-mapping.php:71 msgid "Update" msgstr "Aktualisieren" #: plugins/badbehaviour.php:83 #: wp-cache.php:1295 #: wp-cache.php:1297 msgid "Warning!" msgstr "Warnung!" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Dein Kommentar wird vor der Freigabe moderiert." #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "Wartet auf Freigabe " #: plugins/awaitingmoderation.php:36 msgid "Enables or disables plugin to Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment." msgstr "Aktiviert oder deaktiviert: Entferne den Text \"Dein Kommentar wird vor der Freigabe moderiert.\" wenn jemand einen zu moderierenden Kommentar hinterlässt. " #: plugins/awaitingmoderation.php:43 msgid "Awaiting Moderation is now %s" msgstr "\"Awaiting Moderation\"-Plugin ist jetzt %s. " #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1218 msgid "Disable" msgstr "Deaktiviere" #: plugins/searchengine.php:71 msgid "No Adverts for Friends plugin is %s." msgstr "No Adverts for Friends-Plugin ist %s. " #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(friendsadverts.php ebenfalls erforderlich) " #: plugins/searchengine.php:74 #: wp-cache.php:1218 msgid "Enable" msgstr "Aktiviere" #: plugins/domain-mapping.php:58 msgid "Domain Mapping" msgstr "Domain-Mapping" #: plugins/domain-mapping.php:63 msgid "Provides support for Domain Mapping plugin to map multiple domains to a blog." msgstr "Unterstützt das Domain Mapping-Plugin, um verschiedene Domains auf einen Blog einzutragen." #: plugins/domain-mapping.php:69 msgid "Domain Mapping support is now %s" msgstr "\"Domain Mapping\"-Support ist %s. " #: plugins/domain-mapping.php:83 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "\"Domain Mapping\"-Plugin gefunden! Bitte gehe zur Supercache Plugins-Page und aktiviere das \"Domain Mapping\" Hilfs-Plugin." #: ossdl-cdn.php:146 msgid "Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull." msgstr "Deine Webseite nutzt evtl. viele statische Dateien. Bilder, Javascript- und CSS-Dateien sind normalerweise statische Dateien, die genausogut von einer anderen (Sub-)Domain oder einem CDN (Content Distribution Network) ausgeliefert werden können. Deshalb ersetzt dieses Plugin alle Pfade in den Verzeichnissen wp-content und wp-includes (ausnahmsweise der PHP-Dateien) deiner Seite mit dem URL, den Du unten eingibst. Auf diese Art können die statischen Inhalte auf einen dedizierten Server kopiert werden, oder die Dateien über ein \"CDN\" via origin pull gespiegelt werden." #: ossdl-cdn.php:147 #: wp-cache.php:968 msgid "The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin." msgstr "Das CDN Sync-Tool Plugin wird den Dateiupload zu Amazon S3/Cloudfront unterstützen, wenn Du lieber vom Orginalzugriff unabhängig bist. Lies das plugin support forum, wenn Du zu diesem Plugin irgendwelche Fragen hast." #: ossdl-cdn.php:148 msgid "WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes." msgstr "WARNUNG: Teste erst ein paar statische URLs, z.B.: %s - um vor dem Speichern deiner Änderungen sicherzustellen, daß dein CDN-Service voll funkionsfähig ist." #: ossdl-cdn.php:149 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "Du kannst verschiedene CDN-URLs für jede Seite eines Multsite-Blognetzwerks definieren." #: ossdl-cdn.php:157 msgid "Enable CDN Support" msgstr "Aktiviere CDN Support" #: ossdl-cdn.php:160 msgid "Off-site URL" msgstr "Off-site URL" #: ossdl-cdn.php:163 msgid "The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s." msgstr "Der neue URL anstelle von %1$s für das Rewriting. Kein führendes Zeichen / bitte.
    Als Beispiel: %2$s." #: ossdl-cdn.php:167 msgid "Include directories" msgstr "Schließe Verzeichnisse mit ein" #: ossdl-cdn.php:170 msgid "Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty." msgstr "Verzeichnisse, die in Static File Matching mit einbezogen werden sollen. Benutze das Komma als Trennzeichen. Die Vorgabe ist wp-content, wp-includes, zwangsläufig eingesetzt, wenn das Feld leer gelassen wird." #: ossdl-cdn.php:174 msgid "Exclude if substring" msgstr "Verbergen falls Substring" #: ossdl-cdn.php:177 msgid "Excludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default)." msgstr "Schließt etwas vor Revisionen aus, wenn eine der obengenannten Zeichenketten im Ergebnis gefunden wird. Benutze ein Komma als Trennzeichen, wie hier: .php, .flv, .do, und binde immer .php mit ein (Standard)." #: ossdl-cdn.php:181 msgid "Additional CNAMES" msgstr "Weitere CNAMES" #: ossdl-cdn.php:184 msgid "These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$s" msgstr "Diese CNAMES werden anstatt der %1$s für Rewriting genutzt (als Ergänzung zu dem Off-Site URL weiter oben). Benutze ein Komma als Trennzeichen. Für Seiten mit einer großen Anzahl statischer Dateien kann sich dadurch die Leistung des Browsers verbessern. Es kann sein, das CNAMEs auch in deinem CDN konfiguriert werden müssen.
    Als Beispiel: %2$s" #: ossdl-cdn.php:188 msgid "Skip https URLs to avoid \"mixed content\" errors" msgstr "Überspringt https URLs um \"mixed content\" Fehler zu vermeiden" #: ossdl-cdn.php:192 msgid "Save Changes" msgstr "Änderungen speichern" #: ossdl-cdn.php:194 msgid "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "CDN-Funktionen bereitgestellt durch OSSDL CDN Off Linker von Mark Kubacki." #: wp-cache.php:99 msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Bitte erstelle %s /wp-cache-config.php aus der wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:162 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Achtung! PHP Safe-Modus ist aktiviert!!" #: wp-cache.php:163 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Kann sein dass es zu Probleme mit diesem Plugin kommt, da SAFE MODE aktiviert ist." #: wp-cache.php:167 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Dein Server ist so eingestellt, dass erst die Besitzrechte des PHP-Skripts überprüft werden, bevor Schreib- und Lese-Zugriff gestattet wird." #: wp-cache.php:168 msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Du oder ein Administrador könnten es ans Laufen kriegen, wenn die Besitzrechte des Plugin-Skripts entsprechend den Einstellungen auf dem Webserver (Gruppe/Besitzer) angepasst werden. Die Besitzergruppe des %s/cache/-Verzeichnisses muss ebenfalls geändert werden. Weitere Details unter Safe-Modus Anleitung." #: wp-cache.php:170 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Du oder ein Administrator müssen das deaktivieren. Bitte besuche die Seite Safe-Modus Anleitung für weitere Details. Leider kann das nicht per .htaccess ausgeschaltet werden, sondern muss in der php.ini konfiguriert werden." #: wp-cache.php:176 msgid "Permlink Structure Error" msgstr "Fehler in Permalink-Struktur" #: wp-cache.php:177 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Benutzerdefinierte Struktur oder Permalink-Struktur ist für korrektes Funkionieren des Plugins erforderlich. Bitte gehe zu Einstellungen > Permalinks um deine Permalinks zu konfigurieren." #: wp-cache.php:189 msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Achtung! Dein Host-Name \"%s\" wird in %s aufgelöst" #: wp-cache.php:190 msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Dein Server glaubt, dein Host-Name wird zu %s aufgelöst. Einige Dienste, z.B. die Garbage-Collection dieses Plugins und in WordPress eingebundene Beiträge, werden evtl. nicht korrekt funktionieren." #: wp-cache.php:191 #: wp-cache.php:205 msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Bitte lese den Eintrag Nº16 im Bereich: Troubleshooting der readme.txt" #: wp-cache.php:204 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Leider kann WordPress die Datei wp-cron.php nicht finden. Dieses Skript wird für einwandfreies Funktionieren der Garbage-Collection dieses Plugins, der zeitlichen Einbindung von Beiträgen in WordPress und andere kritische Aktionen benötigt." #: wp-cache.php:219 msgid "Cannot continue... fix previous problems and retry." msgstr "Geht nicht weiter... vorausgegangene Probleme beheben und noch einmal versuchen." #: wp-cache.php:228 msgid "Zlib Output Compression Enabled!" msgstr "\"Zlib Output Compression\" (Dateiausgabe komprimiert) ist aktiviert!!" #: wp-cache.php:229 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP komprimiert die Daten, die an die Besucher deiner Seite gesendet werden. Deaktivierung wird hier empfohlen, da das Plugin ansonsten einmalig die komprimierte Ausgabe cached statt die gleiche Seite immer und immer wieder zu cachen. Beachte dazu auch #21 im Bereich \"Troubleshooting\". Lese diese Seite mit Anweisungen zur Bearbeitung deiner php.ini." #: wp-cache.php:233 msgid "Mod rewrite may not be installed!" msgstr "Mod Rewrite ist wahrscheinlich nicht installiert!" #: wp-cache.php:234 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Scheint als wäre mod_rewrite nicht installiert. Manchmal ist dieser Check nicht zuverlässig, besonders wenn dein Webserver nicht mit Apache arbeitet. Bitte stelle sicher, dass das Modul mod_rewrite aktiviert ist. Es wird benötigt, um statische Supercache-Dateien zu erstellen. Du kannst dann immer noch Legacy oder PHP-Modi benutzen." #: wp-cache.php:239 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Nur Leserechte (Read-Only Modus). Die Konfiguration kann nicht geändert werden." #: wp-cache.php:240 msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Die WP-Super-Cache Konfigurationsdatei %s/wp-cache-config.php kann nicht bearbeitet werden. Für jegliche Änderung muss der Webserver Schreibrechte für die Datei besitzen." #: wp-cache.php:241 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Eine einfache Art das zu tun ist, die Berechtigungen temporär per CHMOD über die Konsole oder mit deinem FTP-Programmm zu ändern. Sorge dafür dass sie global beschreibbar ist, dann soll es wohl klappen." #: wp-cache.php:242 #: wp-cache.php:258 msgid "This page explains how to change file permissions." msgstr "Diese Seite erklärt, wie Datei-Zugriffsrechte geändert werden können (Englisch)." #: wp-cache.php:243 msgid "Writeable:" msgstr "Beschreibbar: " #: wp-cache.php:244 msgid "Readonly:" msgstr "Nur Leserechte: " #: wp-cache.php:256 msgid "Warning! %s is writeable!" msgstr "Warnung! %s ist beschreibbar!" #: wp-cache.php:257 msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Du solltest die Zugriffsrechte in %s ändern, stelle sie etwas restriktiver ein. Benutze dein FTP-Programm, oder die folgende Anweisung um das zu erledigen:" #: wp-cache.php:267 msgid "Mobile rewrite rules detected" msgstr "\"Rewrite Rules\" für mobile Endgeräte gefunden" #: wp-cache.php:268 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Für optimale Performance solltest Du \"Mobile Endgeräte unterstützen\" aktivieren oder die \"Rewrite Rules für mobile Endgeräte\" in der .htaccess löschen. Suche die beiden Zeilen mit dem Text \"2.0\\ MMP|240x320\" und entferne sie." #: wp-cache.php:268 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Hat keinen Einfluss auf normale Besucher, nur Handy-Benutzer bekommen ungecachede Seiten angezeigt." #: wp-cache.php:274 #: wp-cache.php:285 msgid "Rewrite rules must be updated" msgstr "\"Rewrite Rules\" müssen aktualisiert werden!" #: wp-cache.php:275 #: wp-cache.php:286 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Die \"Rewrite Rules\" für dieses Plugin wurden geändert oder sind nicht vorhanden." #: wp-cache.php:276 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Die Unterstützung mobiler Endgeräte benötigt Extra-Regeln in der Datei .htaccess, oder Du setzt das Plugin in den Legacy-Modus. Hier sind deine Oprionen (sortiert nach Schwierigkeitsgrad):" #: wp-cache.php:277 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Setze das Plugin auf den half-on-Modus und aktiviere \" Unterstützung mobiler Endgeräte\"." #: wp-cache.php:278 #: wp-cache.php:287 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Scroll zum Ende der \"Erweitere Einstellungen\"-Seite und klicke auf den Schalter Mod_Rewrite Rules aktualisieren." #: wp-cache.php:279 msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Lösche die mod_rewrite rules des Plugins in %s.htaccess zwischen # BEGIN WPSuperCache und # END WPSuperCache und lass sie dann vom Plugin neu generieren. Dazu musst Du nur diese Seite im Browser neu laden." #: wp-cache.php:280 msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Trage die Regeln selbst ein. Bearbeite %s.htaccess und finde den Block zwischen den Zeilen # BEGIN WPSuperCache und # END WPSuperCache. Da gibt es zwei Bereiche, die sich sehr ähneln. Direkt unterhalb der Zeile %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ diese Zeilen einfügen: (zweimal, jeweils eine in beiden Bereichen)" #: wp-cache.php:293 msgid "Required to serve compressed supercache files properly." msgstr "Erforderlich um komprimierte Supercache-Dateien sauber zu erstellen." #: wp-cache.php:293 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Erforderlich um Caching-Infos in Supercache-Seiten zu schreiben. IE7-User bekommen ohne dieses Modul nur alte Seiten zu sehen." #: wp-cache.php:293 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Setzt das Ablaufdatum für Supercache-Seiten. Besucher bekommen unter Umständen ohne diese Modul neue Seiten nicht angezeigt oder verlieren Kommentare, wenn sie den Browser neu laden." #: wp-cache.php:300 msgid "Missing Apache Modules" msgstr "Fehlende Apache-Module" #: wp-cache.php:301 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Folgende Apache-Module fehlen. Das Plugin arbeitet ohne sie im Legacy-Modus. Im vollen Supercache-Modus kann es ansonsten passieren, dass deine Besucher beschädigte Seiten oder veraltete Inhalte sehen." #: wp-cache.php:459 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Achtung! Du hast versucht die Datei-Komprimierung zu aktivieren, aber zlib.output_compression ist aktiv. Lese dazu #21 im Bereich Troubleshooting der Datei readme.txt." #: wp-cache.php:550 msgid "WP Super Cache Settings" msgstr "WP-Super-Cache Einstellungen" #: wp-cache.php:561 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Hinweis: Mod_rewrite oder Legacy-Caching aktiviert. Die Seite \"Erweiterte-Einstellungen\" wird standardmässig angezeigt." #: wp-cache.php:572 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Die Konfigurationsdatei wurde geändert, einige Werte sind vielleicht falsch. Bitte die Seite neu laden im Menü \"Einstellungen\", um sie zurückzusetzen." #: wp-cache.php:597 msgid "Caching must be enabled to use this feature" msgstr "Caching muss aktiviert sein, um diese Option nutzen zu können" #: wp-cache.php:615 #: wp-cache.php:746 msgid "Cancel Cache Preload" msgstr "Cache-Preload abstellen" #: wp-cache.php:623 #: wp-cache.php:634 msgid "Scheduled preloading of cache cancelled." msgstr "Planmässiges Vorladen des Cache abgebrochen." #: wp-cache.php:660 #: wp-cache.php:744 msgid "Preload Cache Now" msgstr "Cache jetzt vorladen" #: wp-cache.php:664 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Planmässiges Vorladen des Cache in 10 Sekunden" #: wp-cache.php:669 msgid "Scheduled preloading of cache in %d minutes" msgstr "Planmässiges Vorladen des Cache in %d Minuten" #: wp-cache.php:673 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Dadurch werden alle publizierten Seiten und Beiträge gecached. Es werden statische Supercache-Dateien erstellt, so dass anonyme Besucher (inklusive Bots) eine gecachede Seite aufrufen. Das kann möglicherweise dein Google-Ranking verbessern, da kurze Ladezeiten als Maßstab für die Beurteilung von Webseiten relevant sind." #: wp-cache.php:674 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "\"Vorladen\" produziert aber auch eine Menge Dateien. Es wird vom ältesten bis zum neuesten Beitrag gecached, also bedenke bitte nur die Neuesten zu cachen, wenn Du viele (10.000+) Einträge hast. Das spielt vor allem auf virtuellen Servern (shared hosting) eine entscheidende Rolle." #: wp-cache.php:675 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "Im \"Preload-Modus\" wird die normale \"Garbage Collection\" (Leeren des abgelaufenen Cache) nur alte Legacy-Dateien für schon bekannte Benutzer bereinigen, nicht die vorab geladenen Supercache-Dateien. Das ist die empfohlene Einstellung wenn der Cache vorgeladen wird." #: wp-cache.php:679 msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Erneuere vorab geladene Cache-Dateien alle %s Minuten. (0 zum deaktivieren, Minimum %d Minuten.)" #: wp-cache.php:692 msgid "all" msgstr "Alle" #: wp-cache.php:705 msgid "Preload %s posts." msgstr "Lade %s Beiträge vorab." #: wp-cache.php:712 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Preload-Modus (Garbage-Collection nur für Legacy Cache-Dateien. Empfohlen.)" #: wp-cache.php:715 msgid "Send me status emails when files are refreshed." msgstr "Sende mir E-Mails zum Status, wenn Dateien erneuert wurden." #: wp-cache.php:720 msgid "Many emails, 2 emails per 100 posts." msgstr "Viele E-Mails, 2 E-Mails pro 100 Beiträge." #: wp-cache.php:723 msgid "Medium, 1 email per 100 posts." msgstr "Mittel, 1 E-Mail pro 100 Beiträge." #: wp-cache.php:726 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Weniger E-Mails, 1 am Anfang und 1 am Ende des Preloads aller Beiträge." #: wp-cache.php:730 msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Erneuern des Cache in %d Stunden %d Minuten und %d Sekunden." #: wp-cache.php:731 msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Vollständiges Erneuern des Cache in %d Stunden %d Minuten und %d Sekunden." #: wp-cache.php:737 msgid "Currently caching from post %d to %d." msgstr "Momentan wird von Beitrag %d bis %d gecached." #: wp-cache.php:741 msgid "Page last cached: %s" msgstr "Seite zuletzt gecached: %s" #: wp-cache.php:744 msgid "Update Settings" msgstr "Einstellungen aktualisieren" #: wp-cache.php:752 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Cache-Preloading deaktiviert. Bitte deaktiviere Legacy-Caching oder kläre das mit deinem Hosting-Administrator." #: wp-cache.php:769 #: wp-cache.php:865 msgid "Caching" msgstr "Caching" #: wp-cache.php:773 msgid "Cache hits to this website for quick access." msgstr "Cache Treffer auf diese Webseite für schnellen Zugriff." #: wp-cache.php:773 #: wp-cache.php:774 #: wp-cache.php:791 #: wp-cache.php:796 #: wp-cache.php:799 #: wp-cache.php:800 #: wp-cache.php:813 #: wp-cache.php:868 msgid "Recommended" msgstr "Empfohlen" #: wp-cache.php:774 msgid "Use mod_rewrite to serve cache files." msgstr "Nutze mod_rewrite um Cache-Dateien auszuliefern." #: wp-cache.php:775 msgid "Use PHP to serve cache files." msgstr "Nutze PHP um Cache-Dateien auszuliefern." #: wp-cache.php:776 msgid "Legacy page caching." msgstr "Legacy Page-Caching." #: wp-cache.php:777 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching." msgstr "Mod_rewrite ist am schnellsten, PHP ist fast genau so schnell und einfacher ans Laufen zu kriegen, währen Legacy-Caching langsamer läuft, aber flexibler und ebenso leicht zu aktivieren. Neulinge sollten PHP-Caching wählen." #: wp-cache.php:783 msgid "Miscellaneous" msgstr "Sonstiges" #: wp-cache.php:789 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "Warnung! Komprimierung ist deaktiviert, weil die Funktion gzencode() nicht vorhanden ist." #: wp-cache.php:791 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Komprimiere Seiten, so das sie schneller an Besucher ausgeliefert werden." #: wp-cache.php:792 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Die Komprimierung ist standardmässig deaktiviert, da manche Hosts Probleme mit komprimierten Dateien haben. An- und abschalten leert den Cache." #: wp-cache.php:796 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Not Modified Browser Caching. Stelle fest wenn eine Seite seit dem letzten Aufruf nicht modifiziert wurde." #: wp-cache.php:797 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "304-Support ist standardmässig deaktiviert, da \"GoDaddy\" in der Vergangenheit Probleme mit ein paar der eingesetzten Header hatte." #: wp-cache.php:799 msgid "Don’t cache pages for known users." msgstr "Seiten für bekannte Benutzer nicht cachen." #: wp-cache.php:800 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Cache neu erstellen. Liefert eine Supercache-Datei an anonyme Besucher aus, während eine neue Datei erstellt wird." #: wp-cache.php:801 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Proudly tell the world your server is Digg proof! (zeigt einen kleinen Hinweis im Footer deines Blogs, dass dein Server \"hieb- und stichfest\" ist)" #: wp-cache.php:807 #: wp-cache.php:1056 #: wp-cache.php:1563 msgid "Advanced" msgstr "Erweitert" #: wp-cache.php:811 msgid "Mobile device support." msgstr "Unterstützung mobiler Endgeräte." #: wp-cache.php:812 msgid "Clear all cache files when a post or page is published." msgstr "Alle Cache-Dateien bereinigen, wenn ein Beitrag oder eine Seite publiziert wird." #: wp-cache.php:813 msgid "Extra homepage checks. (Very occasionally stops homepage caching)" msgstr "Extra Startseiten-Checks. (Stoppt in sehr seltenen Fällen Startseiten-Caching)" #: wp-cache.php:814 msgid "Only refresh current page when comments made." msgstr "Aktuelle Seite nur erneuern, wenn Kommentare geschrieben werden." #: wp-cache.php:815 msgid "List the newest cached pages on this page." msgstr "Auflistung der zuletzt gecacheden Pages auf dieser Seite." #: wp-cache.php:817 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Datei \"stumpf\" sperren. Brauchst Du wahrscheinlich nicht, aber es könnte helfen wenn dein Server schwächelt. Achtung! Kann in seltenen Fällen dazu führen das dein Server abstürzt!" #: wp-cache.php:819 msgid "Late init. Display cached files after WordPress has loaded. Most useful in legacy mode." msgstr "Verzögerte Initiierung. Zeige gecachede Dateien nachdem WordPress geladen ist. Meistens nützlich im Legacy-Modus." #: wp-cache.php:821 msgid "Use object cache to store cached files." msgstr "Nutze Objekt-Cache um gecachede Dateien zu speichern." #: wp-cache.php:821 msgid "(Experimental)" msgstr "(Experimentell)" #: wp-cache.php:828 msgid "Note:" msgstr "Hinweis: " #: wp-cache.php:830 msgid "Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided." msgstr "Deinstalliere das Plugin in der Plugins-Verwaltung. Es wird dabei automatisch hinter sich aufräumen. Wenn ein manueller Eingriff nötig ist, gibt es einfache Anweisungen." #: wp-cache.php:831 msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Wenn Du das Plugin deinstallierst, stelle sicher dass Verzeichnis %s für den Webserver beschreibbar ist, so das die Dateien advanced-cache.php und cache-config.php automatisch entfernt werden können. (..die Dateien ebenfalls beschreibbar zu machen ist dabei eine gute Idee!)" #: wp-cache.php:832 msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Bitte werfe einen Blick in readme.txt für Anleitungen zur Deinstallation dieses Skripts. Suche nach der Überschrift \"How to uninstall WP Super Cache\"." #: wp-cache.php:833 msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Hilfe benötigt? Check die Datei Super Cache readme. Sie enthält die Dokumenration zur Installation, FAQ und Troubleshooting-Tipps. Das Supportforum steht ebenso zur Verfügung. Vielleicht ist deine Frage dort schon beantwortet worden." #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "Update-Status" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "Akzeptierte Dateinamen & Abgewiesene URIs" #: wp-cache.php:868 msgid "Caching On" msgstr "Caching An" #: wp-cache.php:869 msgid "Caching Off" msgstr "Caching Aus" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Hinweis: aktiviert PHP-Caching, Cache-Rebuild und Mobile-Support" #: wp-cache.php:880 msgid "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Hinweis: PHP-Caching ist aktiviert, es wurden aber Supercache mod_rewrite rules gefunden. Cache-Dateien werden nach diesen Regeln erstellt. Wenn deine Seite funkioniert, kannst Du diesen Hinweis gerne ignorieren. Oder bearbeite die Datei .htaccess - auf der \"root\" (oberste Ebene im Webverzeichnis) deiner Installation - und entferne die Supercache-Regeln." #: wp-cache.php:885 msgid "Cache Tester" msgstr "Cache-Tester" #: wp-cache.php:886 msgid "Test your cached website by clicking the test button below." msgstr "Teste deine gecachede Webseite durch anklicken des Schalters \"Cache testen\" hier unten." #: wp-cache.php:892 msgid "Fetching %s to prime cache: " msgstr "Lädt %s um den Cache zu priorisieren: " #: wp-cache.php:894 #: wp-cache.php:902 #: wp-cache.php:910 msgid "OK" msgstr "OK" #: wp-cache.php:897 msgid "Fetching first copy of %s: " msgstr "Lädt die erste Kopie von %s: " #: wp-cache.php:905 msgid "Fetching second copy of %s: " msgstr "Lädt die zweite Kopie von %s: " #: wp-cache.php:913 msgid "One or more page requests failed:" msgstr "Ein oder mehrere Seitenaufrufe fehlgeschlagen: " #: wp-cache.php:932 #: wp-cache.php:933 msgid "Page %d: %d (%s)" msgstr "Seite %d: %d (%s)" #: wp-cache.php:939 msgid "Page 1: %s" msgstr "Seite 1: %s" #: wp-cache.php:940 msgid "Page 2: %s" msgstr "Seite 2: %s" #: wp-cache.php:941 msgid "The timestamps on both pages match!" msgstr "Die Zeitstempel auf beiden Seiten stimmen überein!" #: wp-cache.php:943 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Die Seiten stimmen nicht überein! Die Zeitstempel sind unterschiedlich oder wurden nicht gefunden!" #: wp-cache.php:950 msgid "Send non-secure (non https) request for homepage" msgstr "Sende \"Non-Secure\"-Anfrage (kein https) für Homepage" #: wp-cache.php:951 msgid "Test Cache" msgstr "Cache testen" #: wp-cache.php:955 msgid "Delete Cached Pages" msgstr "Lösche gecachede Seiten" #: wp-cache.php:956 msgid "Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below." msgstr "Gecachede Seiten werden auf deinem Server als HTML- und PHP-Dateien gespeichert. Wenn Du sie löschen mußt, nutze den Button hier unten." #: wp-cache.php:959 #: wp-cache.php:2093 #: wp-cache.php:2105 #: wp-cache.php:2268 msgid "Delete Cache" msgstr "Cache leeren" #: wp-cache.php:963 msgid "Recommended Links and Plugins" msgstr "Empfohlene Links und Plugins" #: wp-cache.php:964 msgid "Caching is only one part of making a website faster. Here are some other plugins that will help:" msgstr "Caching ist nur eine Möglichkeit, eine Webseite \"schneller\" zu machen. Hier ein paar weitere hilfreiche Plugins:" #: wp-cache.php:965 msgid "WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together." msgstr "WP Minify reduziert die Anzahl der von deinem Webserver ausgelieferten Dateien durch Kombination der Javascript- und CSS-Dateien. Alternativ dazu kannst Du WPSCMin, ein Supercache-Plugin zur Minimierung gecacheder Seiten nutzen. Dieses bündelt JS/CSS-Dateien in keiner Weise." #: wp-cache.php:966 msgid "Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix." msgstr "Yahoo! Yslow ist eine Erweiterung des Firefox add-on Firebug. Sie analysiert Webseiten und bietet Möglichkeiten zur Verbesserung der Performanz an, die auf einer Reihe von Regeln für hoch-performante Webseiten bestehen. Probiere auch die Performance-Online-Tools unter GTMetrix." #: wp-cache.php:967 msgid "Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score." msgstr "Nutze Google-Libraries ermöglicht es, einige der allgemein gebräuchlichen Javascript-Bibliotheken von Google Webservern zu laden. Ironischerweise kann das deine Werte im Yslow-Score verschlechtern." #: wp-cache.php:969 msgid "Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules." msgstr "Nur für Fortgeschrittene: Speed up your site with Caching and cache-control erklärt, wie deine Seite über Regeln in der .htaccess-Datei cache-fähiger gemacht wird." #: wp-cache.php:970 msgid "Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others." msgstr "Nur für Fortgeschrittene: Installiere einen \"Objekt-Cache\". Wähle Memcached, XCache, eAcccelerator und andere." #: wp-cache.php:981 msgid "Make WordPress Faster" msgstr "Mach WordPress schneller!" #: wp-cache.php:982 msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s wurde entwickelt/wird gewartet von %2$s unter Beteiligung vieler Anderer." #: wp-cache.php:983 msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Er bloggt unter %1$s und publiziert Photos in %2$s" #: wp-cache.php:984 msgid "Please say hi to him on %s too!" msgstr "Bitte sag auch \"Hallo\" zu ihm bei %s!" #: wp-cache.php:985 msgid "Need Help?" msgstr "Hilfe benötigt?" #: wp-cache.php:987 msgid "Installation Help" msgstr "Hilfe zur Installation" #: wp-cache.php:988 msgid "Frequently Asked Questions" msgstr "Frequently Asked Questions" #: wp-cache.php:989 msgid "Support Forum" msgstr "Support-Forum" #: wp-cache.php:991 msgid "Rate This Plugin!" msgstr "Bitte bewerte dieses Plugin!" #: wp-cache.php:992 msgid "Please rate this plugin and tell me if it works for you or not. It really helps development." msgstr "Bitte bewerte dieses Plugin und berichte mir, ob es für dich funktioniert oder nicht. Damit unterstützt Du die Weiterentwicklung wirklich und wahrhaftig." #: wp-cache.php:1001 msgid "Cached pages since %1$s : %2$s" msgstr "Cached-Pages seit %1$s : %2$s" #: wp-cache.php:1002 msgid "Newest Cached Pages:" msgstr "Neueste Cached-Pages: " #: wp-cache.php:1006 msgid "Cached %s seconds ago" msgstr "Vor %s Sekunden gecached" #: wp-cache.php:1009 msgid "(may not always be accurate on busy sites)" msgstr "(auf besucherstarken Seiten vielleicht nicht immer exakt)" #: wp-cache.php:1028 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Cache-Plugins sind PHP-Skripte, die sich im Plugin-Verzeichnis innerhalb des Ordners \"wp-super-cache\" befinden. Sie werden zusammen mit Supercache geladen, viel früher als reguläre WordPress-Plugins." #: wp-cache.php:1029 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Das ist definitiv nur eine Option für sehr weit \"Fortgeschrittene\". Kenntnisse sowohl in PHP als auch zu WordPress-Actions sind Vorraussetzung, um sie zu erstellen." #: wp-cache.php:1039 msgid "Available Plugins" msgstr "Verfügbare Plugins" #: wp-cache.php:1056 msgid "Easy" msgstr "Easy" #: wp-cache.php:1056 msgid "CDN" msgstr "CDN" #: wp-cache.php:1056 msgid "Contents" msgstr "Inhalte" #: wp-cache.php:1056 msgid "Preload" msgstr "Preload" #: wp-cache.php:1056 msgid "Plugins" msgstr "Plugins" #: wp-cache.php:1056 msgid "Debug" msgstr "Debug" #: wp-cache.php:1091 msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Hinweis: WP-Super-Cache mod_rewrite rule Checks sind deaktiviert, insofern sie nicht auf der Hauptseite dieses Blog-Netzwerks laufen." #: wp-cache.php:1100 msgid "Mod Rewrite Rules" msgstr "Mod Rewrite Rules" #: wp-cache.php:1106 msgid "WordPress MU Detected" msgstr "WordPress MU (WP Multi-Sites) festgestellt" #: wp-cache.php:1106 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Leider können die \"Rewrite-Rules\" nicht automatisch aktualisiert werden, wenn Du WordPress MU benutzt. Bitte öffne deine .htaccess und füge die folgenden mod_rewrite Regeln oberhalb aller anderen Einträge in die Datei ein." #: wp-cache.php:1108 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite Rules können nicht aktualisiert werden!" #: wp-cache.php:1109 msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Es müssen die Markierungen BEGIN und END in %s.htaccess stehen, damit das Auto-Update funktioniert. Sie sehen so aus und umgeben die WordPress mod_rewrite Regeln: " #: wp-cache.php:1111 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Lade die Seite neu, wenn Du die Datei .htaccess aktualisiert hast." #: wp-cache.php:1115 msgid "Thank you for upgrading." msgstr "Danke für das Upgrade." #: wp-cache.php:1115 msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Die mod_rewrite-Regeln haben sich verändert, seit Du das Plugin installiert hast. Leider musst Du die alten Supercache-Regeln entfernen, bevor die Neuen aktualisiert werden können. Lade die Seite neu, wenn Du deine .htaccess aktualisiert hast. Wenn Du händisch aktualisieren willst, ändere die folgende Zeile: %1$s so dass sie hinterher so aussieht: %2$s Die einzigen Änderungen: \"HTTP_COOKIE\" wird zu \"HTTP:Cookie\" und \"wordpressuser\" wird zu \"wordpress\". Dies wurde in WordPress 2.5 geändert, ist aber abwärtskompatibel mit älteren Versionen - wenn Du mutig genug bist, sie zu benutzen." #: wp-cache.php:1119 msgid "Trailing slash check required." msgstr "Überprüfung des \"trailing slash\" (Schrägstrich am Ende des URL) erforderlich." #: wp-cache.php:1119 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Sieht aus als hätte dein Blog URLs, die mit \"/\" aufhören. Dummerweise wurde ein Bug entdeckt, nachdem Du das Plugin installiert hast: URLs, die ohne \"/\" enden liefern den gleichen Inhalt wie URLs mit \"/\", und werden nicht auf den eigentlichen URL weitergeleitet (Dublicate Content). Um das zu beheben, bearbeite deine .htaccess und füge diese beiden Regeln den zwei Super-Cache-Gruppen hinzu: " #: wp-cache.php:1121 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Du kannst sehen wo die Regeln eingetragen werden, wenn Du den \"View mod_rewrite rules\"-Link hier unten anklickst." #: wp-cache.php:1135 msgid "Mod Rewrite rules updated!" msgstr "Mod Rewrite Rules aktualisiert!" #: wp-cache.php:1136 msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "%s.htaccess wurde mit den nötigen mod_rewriteRegeln aktualisiert. Bitte überprüfe, ob sie korrekt sind. So sollten sie aussehen: " #: wp-cache.php:1138 msgid "Mod Rewrite rules must be updated!" msgstr "Mod Rewrite Rules müssen aktualisiert werden!" #: wp-cache.php:1139 msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Deine %s.htaccess ist für den Webserver nicht beschreibbar und muss mit den nötigen mod_rewrite rules aktualisiert werden. Die neuen Regeln werden, wie hier im Code angezeigt, oberhalb der regulären WordPress-Regeln eingetragen: " #: wp-cache.php:1144 msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "WP-Super-Cache mod_rewrite rules in der Datei %s.htaccess gefunden.
    Klicke auf den folgenden Link, um die Einträge die dieser Datei hinzugefügt wurden, anzuzeigen. Wenn Du ein Upgrade des Plugins gemacht hast, stelle sicher dass diese Regeln zutreffen." #: wp-cache.php:1147 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "Eine Abweichung zwischen den Regeln in deiner .htaccess file und den Rewrite Rules im Plugin wurde festgestellt. Dabei kann es sich nur um unterschiedliche Abstände oder Leerzeichen handeln, Du solltest aber die Regeln in der Datei mit den hier unten angezeigten möglichst bald abgleichen. Klicke den \"Mod_Rewrite Rules\"-Button um die Regeln zu aktualisieren." #: wp-cache.php:1150 msgid "View Mod_Rewrite Rules" msgstr "Mod_Rewrite Rules anzeigen" #: wp-cache.php:1154 #: wp-cache.php:2384 msgid "Rules must be added to %s too:" msgstr "Regeln müssen auch noch zu %s hinzugefügt werden: " #: wp-cache.php:1162 msgid "Gzip encoding rules in %s.htaccess created." msgstr "\"Gzip encoding rules\" in %s.htaccess erstellt." #: wp-cache.php:1169 msgid "Fix Configuration" msgstr "Repariere Konfiguration" #: wp-cache.php:1172 msgid "Restore Default Configuration" msgstr "Ursprüngliche Konfiguration wieder herstellen" #: wp-cache.php:1180 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Kommentare werden moderiert. Es kann etwas dauern, bis dein Kommentar angezeigt wird." #: wp-cache.php:1205 msgid "Lock Down:" msgstr "Sperren: " #: wp-cache.php:1206 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Bereite deinen Server auf eine zu erwartende Höchstlast an Traffic vor, indem Du \"Sperren\" aktivierst. In dieser Einstellung werden die statischen Dateien im Cache nicht erneuert, wenn zu den Beiträgen Kommentare veröffentlicht werden." #: wp-cache.php:1207 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting: " #: wp-cache.php:1209 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "
    Entschuldigung. Mein Blog ist im \"Gesperrt\"-Modus. Updates werden in Kürze angezeigt" #: wp-cache.php:1213 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress ist im \"locked down\" Modus. Statische Super-Cache-Dateien werden nicht gelöscht, wenn neue Kommentare geschrieben werden." #: wp-cache.php:1215 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress ist nicht im \"locked down\" Modus. Neue Kommentare werden ganz normal die statischen Super-Cache-Dateien erneuern." #: wp-cache.php:1221 msgid "Lock Down" msgstr "Sperre" #: wp-cache.php:1229 msgid "Directly Cached Files" msgstr "Direkt gecachede Dateien" #: wp-cache.php:1287 msgid "%s removed!" msgstr "%s entfernt!" #: wp-cache.php:1295 msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Du musst %s beschreibbar machen, um diese Option zu nutzen. Da es sich dabei um ein Sicherheitsrisiko handelt, ändere das bitte wieder auf \"Nur Leserechte\" nachdem die Seite generiert ist." #: wp-cache.php:1297 msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s ist beschreibbar! Da es sich dabei um ein Sicherheitsrisiko handelt, ändere das bitte wieder auf \"Nur Lesen\" nachdem die Seite generiert ist." #: wp-cache.php:1311 msgid "Existing direct page" msgstr "Direkt-Seite existiert" #: wp-cache.php:1311 msgid "Delete cached file" msgstr "Lösche gecachede Datei" #: wp-cache.php:1316 msgid "Add direct page:" msgstr "Direkt-Seite hinzufügen: " #: wp-cache.php:1318 msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Direkt gecachede Seiten sind Dateien, die direkt in %s erzeugt werden, da wo dein Blog liegt. Diese Option ist nur sinnvoll, wenn Du auf dem Niveau von Facebook oder Digg Traffic auf einer Seite oder auf einem Beitrag erwartest." #: wp-cache.php:1320 msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Als Beispiel: Um %1$sabout/ zu cachen, würdest Du %1$sabout/ oder /about/ eingeben. Die Cache-Datei wird dann erstellt, sobald ein anonymer Besucher die Seite aufruft." #: wp-cache.php:1321 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Leere die Textbox, um sie von der Liste der Direkt-Seiten zu entfernen und die Cache-Datei zu löschen." #: wp-cache.php:1326 msgid "Update Direct Pages" msgstr "Direkt-Seiten aktualisieren" #: wp-cache.php:1364 msgid "Expiry Time & Garbage Collection" msgstr "Expiry-Time & Garbage-Collection" #: wp-cache.php:1366 msgid "Expire time:" msgstr "Laufzeitende:" #: wp-cache.php:1367 msgid "seconds" msgstr "Sekunden" #: wp-cache.php:1368 msgid "Garbage Collection" msgstr "Müll-Entsorgung (Garbage-Collection)" #: wp-cache.php:1368 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Wenn die Laufzeit länger als 1800 Sekunden (halbe Stunde) ist, wird \"Garbage Collection\" alle 10 Minuten ausgeführt, andernfalls passiert das 10 Sekunden nach Ablauf der oben angegebenen Zeit." #: wp-cache.php:1369 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Suchen und Entfernen von abgelaufenen Dateien kostet ressourcen, sie einfach da zu belassen aber auch. Auf einer sehr gut besuchten Seite solltest Du die Laufzeit auf 300 Sekunden setzen. Experimentiere mit verschiedenen Werten und besuche diese Seite mehrmals um zu überprpüfen, wieviele \"expired\"-Dateien sich zu welcher Zeit im Laufe des Tages ansammeln. Wenn Du Legacy-Caching benutzt, versuche möglich unter 500 Cache-Dateien zu bleiben. Du kannst um ein Vielfaches mehr Dateien haben, wenn Du mod_rewrite oder PHP-Caching einsetzt." #: wp-cache.php:1370 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Setze die Laufzeit auf 0 Sekunden um die Garbage-Collection zu deaktivieren." #: wp-cache.php:1371 msgid "Change Expiration" msgstr "Laufzeit ändern" #: wp-cache.php:1415 msgid "Rejected User Agents" msgstr "Abgewehrte User-Agents" #: wp-cache.php:1416 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Strings im HTTP \"User Agent\"-Header die WP-Cache davon abhalten, Anfragen von Bots, Spidern und Crawlern zu cachen. Vermerke, das Super-Cache-Dateien weiter an diese Agents ausgeliefert werden wenn sie schon existieren." #: wp-cache.php:1423 msgid "Save UA Strings" msgstr "User-Agenten-Strings speichern" #: wp-cache.php:1446 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Folgende Page-Typen nicht cachen. Studiere zu jedem Typ die ausführliche Diskussion in der Dokumentation Conditional Tags." #: wp-cache.php:1449 msgid "Single Posts" msgstr "Einzelne Beiträge" #: wp-cache.php:1450 msgid "Pages" msgstr "Seiten" #: wp-cache.php:1451 msgid "Front Page" msgstr "Startseite" #: wp-cache.php:1452 msgid "Home" msgstr "Home" #: wp-cache.php:1453 msgid "Archives" msgstr "Archive" #: wp-cache.php:1454 msgid "Tags" msgstr "Suchworte (tags)" #: wp-cache.php:1455 msgid "Category" msgstr "Kategorie" #: wp-cache.php:1456 msgid "Feeds" msgstr "Feeds" #: wp-cache.php:1457 msgid "Search Pages" msgstr "Suchseiten" #: wp-cache.php:1459 #: wp-cache.php:1573 msgid "Save" msgstr "Speichern" #: wp-cache.php:1476 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Hier Strings (Zeichenketten, keine Dateinamen) einfügen, um so dafür zu sorgen dass eine Seite nicht gecached wird. Als Beispiel: Wenn deine URLs das Jahresdatum enthalten und Du die Beiträge vom vergangenen Jahr nicht cachen willst, reicht es das Jahr, z.B. \"/2004/\" anzugeben. WP-Cache wird überprüfen, ob diese Zeichenkette im URI enthalten ist und in dem Fall diese Seite dann nicht cachen." #: wp-cache.php:1482 msgid "Save Strings" msgstr "Strings speichern" #: wp-cache.php:1498 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Hier die Dateinamen angeben, die gecached werden sollen, auch wenn sie einer oben auszusortierenden Zeichenkette entsprechen." #: wp-cache.php:1504 msgid "Save Files" msgstr "Dateien speichern" #: wp-cache.php:1545 msgid "Currently logging to: %s" msgstr "Aktuelle Protokolle (Logs) in: %s" #: wp-cache.php:1548 msgid "Fix problems with the plugin by debugging it here. It can log them to a file in your cache directory." msgstr "Versuche Probleme mit dem Plugin durch den Debugger hier zu lösen. Das System kann sie in eine Log-Datei in deinem Cache-Verzeichnis schreiben." #: wp-cache.php:1552 msgid "Debugging" msgstr "Debuggen" #: wp-cache.php:1553 msgid "IP Address" msgstr "IP-Addresse" #: wp-cache.php:1553 msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(nur Abfragen dieser IP protokollieren. Deine IP ist %s)" #: wp-cache.php:1554 msgid "Log level" msgstr "Log-Level" #: wp-cache.php:1560 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = weniger, 5 = mehr, kann heftige Serverlast verursachen)" #: wp-cache.php:1563 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "In sehr seltenen Fällen können zwei Probleme auf manchen Blogs auftreten:
    1. Die Startseite kann anfangen sich als zip.Archiv herunterzuladen.
    2. Eine falsche Seite wird nach dem Zufallsprinzip als Startseite gecached, wenn dein Blog eine statische Seite als Startseite benutzt und deine Permalinks mit /%category%/%postname%/ strukturiert sind.
    " #: wp-cache.php:1564 msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "Ich bin zu 99% sicher, dass das keine von WP-Super-Cache verursachten Bugs sind, und sie kommen nur in extrem seltenen Fällen vor. Du kannst aber alle 5 Minuten einen simplen Check laufen lassen, um sicherzugehen dass deine Seite ok ist, wenn Du dir Sorgen machst. Du bekommst dann eine E-Mail Benachrichtigung, falls ein Problem auftaucht." #: wp-cache.php:1566 msgid "Check front page every 5 minutes." msgstr "Check die Startseite alle 5 Minuten." #: wp-cache.php:1567 msgid "Front page text" msgstr "Text der Startseite" #: wp-cache.php:1567 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Text, um danach auf der Front-Page zu suchen: Wenn nicht gefunden, wird der Cache geleert. Leer lassen um das zu deaktivieren." #: wp-cache.php:1568 msgid "Clear cache on error." msgstr "Bei \"Error\" Cache leeren." #: wp-cache.php:1569 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "E-Mail an den Administrator wenn die Überprüfung beendet. (hilfreich für Tests)" #: wp-cache.php:1583 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Error: GZIP-Komprimierung ist aktiv, deaktiviere sie wenn Du wp-cache nutzen willst." #: wp-cache.php:1630 #: wp-cache.php:1796 msgid "Warning" msgstr "Warnung" #: wp-cache.php:1630 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "GZIP-Komprimierung ist in WordPress aktiviert - wp-cache wird überbrückt, bis Du \"gzip compression\" deaktiviert hast." #: wp-cache.php:1692 #: wp-cache.php:1697 #: wp-cache.php:1729 #: wp-cache.php:1734 #: wp-cache.php:1740 msgid "Error" msgstr "Fehler" #: wp-cache.php:1692 msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Dein Cache-Verzeichnis ($cache_path) existiert nicht und konnte nicht erstellt werden. Prüfe %s Benutzerrechte." #: wp-cache.php:1697 msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Dein Cache-Verzeichnis (%1$s) oder %2$s muss beschreibbar sein, damit das Plugin funktioniert. Doppelt überprüfen." #: wp-cache.php:1729 msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Deine WP-Cache Konfigurationsdatei (%s) ist nicht aktuell und nicht beschreibbar für den Webserver. Bitte lösche sie und lade diese Seite neu." #: wp-cache.php:1734 msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Deine WP-Cache Konfigurationsdatei fehlt und %1$s Verzeichnis (%2$s) ist nicht beschreibbar für den Webserver. Bitte überprüfe die Berechtigungen für den Webserver." #: wp-cache.php:1740 msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "WP-Cache Konfigurations-Beispieldatei (%s) existiert nicht. Überprüfe die Installation." #: wp-cache.php:1796 msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php existiert nicht oder kann nicht aktualisiert werden." #: wp-cache.php:1797 msgid "1. If it already exists please delete the file first." msgstr "1. Wenn es sie schon gibt, bitte die Datei zuerst löschen." #: wp-cache.php:1798 msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Vergebe %1$s Schreibrechte per CHMOD in der Konsole oder mit deinem FTP-Programm. (chmod 777 %1$s) und lade diese Seite neu. Das ist nur eine zeitweilige Massnahme und Du musst sie danach wieder auf \"Nur Lesen\" setzen (ändere 777 zu 755 im vorhergehenden Befehl)." #: wp-cache.php:1799 msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Lade diese Seite neu um %s/advanced-cache.php zu aktualisieren." #: wp-cache.php:1800 msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Wenn das nicht hilft, stelle sicher dass die Datei %s/advanced-cache.php nicht existiert: " #: wp-cache.php:1801 msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Öffne %1$s$wp_cache_file in einem Texteditor (Notepad++ oder das blaue Teil von Windows..)
  • 2. Ändere den Text CACHEHOME in %2$s
  • 3. Speichere die Datei, kopiere sie nach %3$s und lade diese Seite neu.
    • " #: wp-cache.php:1824 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    WP_CACHE-Konstante auf \"False\" gesetzt

    Die WP_CACHE-Konstante wird von WordPress genutzt, um den Code der Cache-Seiten erstellt zu laden. Unglücklicherweise ist das auf \"Nein\" gestellt. Bitte bearbeite deine wp-config.php und ändere bzw. füge die folgende Zeile oberhalb der abschliessenden \"require_once\"-Anweisung dazu:

    define('WP_CACHE', true);

    " #: wp-cache.php:1826 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Fehler: WP_CACHE ist nicht aktiviert in deiner wp-config.php und ich kann sie nicht modifizieren." #: wp-cache.php:1827 msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Bearbeite %s und füge folgende Zeile hinzu:
    define('WP_CACHE', true);
    Ansonsten wird WP-Cache nicht ausgeführt durch Wordpress." #: wp-cache.php:1831 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    WP_CACHE-Konstante zu wp-config.php hinzugefügt

    Wenn diese Warnung wiederholt angezeigt wird, lese bitte zu Punkt 5 in den FAQ nach. Die WP_CACHE-Zeile muss nach oben verschoben werden.\"

    " #: wp-cache.php:1855 msgid "Cache Contents" msgstr "Cache-Inhalte" #: wp-cache.php:1858 msgid "Object cache in use. No cache listing available." msgstr "Objekt-Cache im Gebrauch. Cache-Listing steht nicht zur Verfügung." #: wp-cache.php:1882 msgid "Deleting supercache file: %s
    " msgstr "Supercache-Datei löschen: %s
    " #: wp-cache.php:1899 msgid "Deleting wp-cache file: %s
    " msgstr "Datei wp-cache löschen: %s
    " #: wp-cache.php:1964 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Cache-Statistiken werden nicht automatisch erzeugt. Du musst auf den Link hier unten klicken, um die Statistik für diesen Blog neu zu generieren." #: wp-cache.php:1965 msgid "Regenerate cache stats" msgstr "Regeneriere Cache-Statistik" #: wp-cache.php:1967 msgid "Cache stats last generated: %s minutes ago." msgstr "Cache-Statistik zuletzt generiert vor %s Minuten." #: wp-cache.php:1973 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:1974 #: wp-cache.php:1989 msgid "%s Cached Pages" msgstr "%s Seiten im Cache" #: wp-cache.php:1975 #: wp-cache.php:1994 msgid "%s Expired Pages" msgstr "%s Expired-Pages im Cache" #: wp-cache.php:1988 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1998 msgid "Fresh WP-Cached Files" msgstr "Neue WP-Cache-Dateien" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "URI" msgstr "URI" #: wp-cache.php:1999 #: wp-cache.php:2015 msgid "Key" msgstr "Schlüssel" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "Age" msgstr "Alter" #: wp-cache.php:1999 #: wp-cache.php:2015 #: wp-cache.php:2031 #: wp-cache.php:2047 msgid "Delete" msgstr "Lösche" #: wp-cache.php:2014 msgid "Stale WP-Cached Files" msgstr "Abgelaufene WP-Cache Dateien" #: wp-cache.php:2030 msgid "Fresh Super Cached Files" msgstr "Neue Super-Cached Dateien" #: wp-cache.php:2046 msgid "Stale Super Cached Files" msgstr "Abgelaufene Super-Cached Dateien" #: wp-cache.php:2062 msgid "Hide file list" msgstr "Datei-Liste verbergen" #: wp-cache.php:2064 msgid "Too many cached files, no listing possible." msgstr "Zu viele Cache-Dateien, Auflistung nicht möglich." #: wp-cache.php:2066 msgid "List all cached files" msgstr "Alle Cache-Dateien auflisten" #: wp-cache.php:2072 msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Garbage Collection
    Letzte \"Entmüllung\" war vor %s Minuten
    " #: wp-cache.php:2073 msgid "Next GC in %s minutes" msgstr "Nächste \"Entmüllung\" in %s Minuten" #: wp-cache.php:2076 msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Abgelaufene Dateien sind Dateien die älter als %s Sekunden sind. Sie werden noch vom Plugin genutzt und in regelmässigen Abständen gelöscht." #: wp-cache.php:2087 msgid "Delete Expired" msgstr "Abgelaufene löschen" #: wp-cache.php:2105 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Lösche Super-Cache gecachede Dateien (öffnet in neuem Fenster)" #: wp-cache.php:2244 msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s ist \"schlag- und rüttelfest\" dank dem Caching von %2$s" #: wp-cache.php:2277 msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP-Super-Cache muss konfiguriert werden. Gehe zu den Einstellungen, um das Plugin zu aktivieren und zu konfigurieren." #: wp-cache.php:2283 msgid "Settings" msgstr "Einstellungen" #: wp-cache.php:2293 msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP-Super-Cache ist deaktiviert. Bitte gehe zur Seite der Plugin-Administration um Caching zu aktivieren." #: wp-cache.php:2296 msgid "Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct." msgstr "Achtung! WP Super-Cache Caching abgebrochenn! Das Skript advanced-cache.php konnte wp-cache-phase1.php nicht aufrufen.

    Bitte bearbeite %1$s/advanced-cache.php und stelle sicher, daß der Pfad %2$swp-cache-phase1.php korrekt ist." #: wp-cache.php:2315 msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Startseite mit Gzip komprimiert! Bitte den Cache leeren." #: wp-cache.php:2315 msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Bitte gehe zu %s um den Cache zu leeren, da die Startseite deiner Website gerade heruntergeladen wird!" #: wp-cache.php:2318 msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Startseite mit Gzip komprimiert! Cache geleert!" #: wp-cache.php:2318 msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Der Cache deines Blogs wurde geleert, da die Startseite gerade runterlädt. Bitte gehe zu %s um sicherzustellen, dass der Cache bereinigt ist." #: wp-cache.php:2325 msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Startseite ist nicht in Ordnung! Bitte den Cache leeren!" #: wp-cache.php:2325 msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Bitte gehe zu %1$s um den Cache zu leeren, da deine Startseite nicht in Ordnung zu sein scheint und der Text fehlt, \"%2$s\"!" #: wp-cache.php:2328 msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Startseite nicht in Ordnung! Cache geleert!" #: wp-cache.php:2328 msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Der Cache deines Blogs wurde geleert, da der Text \"%2$s\" nicht auf der Startseite ist. Bitte gehe zu %1$s um sicherzustellen, dass der Cache bereinigt ist." #: wp-cache.php:2333 msgid "[%s] Front page check!" msgstr "[%s] Startseiten-Check!" #: wp-cache.php:2333 msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP-Super-Cache hat die Startseite deines Blogs überprüft. Bitte gehe zu %s, wenn Du die Funktion deaktivieren möchtest." #: wp-cache.php:2376 msgid "Cannot update .htaccess" msgstr "Kann .htaccess nicht aktualisieren" #: wp-cache.php:2376 msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Die Datei %s.htaccess kann vom Webserver nicht aktualisiert werden. Bitte ändere das per CHMOD-Command oder FTP-Programm." #: wp-cache.php:2376 msgid "Refresh this page when the file permissions have been modified." msgstr "Lade diese Seite neu, wenn die Datei-Berechtigungen geändert wurden." #: wp-cache.php:2376 msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Alternativ dazu kannst Du deine %s.htaccess manuell bearbeiten und folgenden Code einfügen (oberhalb aller WordPress-Einträge): " #: wp-cache.php:2380 msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Um statische HTML-Dateien zu erstellen, benötigt dein Server die korrekten \"mod_rewrite rules\" in der Datei %s.htaccess." #: wp-cache.php:2381 msgid "You can edit the file yourself add the following rules." msgstr "Du kannst die Datei selbst bearbeiten und folgende Regeln hinzufügen." #: wp-cache.php:2382 msgid " Make sure they appear before any existing WordPress rules. " msgstr " Stelle sicher dass sie oberhalb sämtlicher WordPress-Regeln stehen. " #: wp-cache.php:2390 msgid "Update Mod_Rewrite Rules" msgstr "Mod Rewrite Rules aktualisieren" #: wp-cache.php:2515 msgid "[%1$s] Cache Preload Started" msgstr "Cache-Preload gestartet" #: wp-cache.php:2517 msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Beiträge von %2$d bis %3$d werden aktualisiert" #: wp-cache.php:2535 msgid "[%1$s] Cache Preload Stopped" msgstr "Cache-Preload abgestellt" #: wp-cache.php:2544 msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d Beiträge aktualisiert" #: wp-cache.php:2544 msgid "Refreshed the following posts:" msgstr "Folgenende Beiträge aktualisiert: " #: wp-cache.php:2553 msgid "Scheduling next preload refresh in %d minutes." msgstr "Nächste \"Preload\"-Aktualisierung in %d Minuten eingeplant." #: wp-cache.php:2563 msgid "[%s] Cache Preload Completed" msgstr "[%s] Cache-Preload abgeschlossen!" #: wp-cache.php:2563 msgid "Cleaning up old supercache files." msgstr "Alte Supercache-Dateien bereinigen." #: wp-cache.php:2605 msgid "[%s] Preload may have stalled." msgstr "\"Preload\" evtl. unterbrochen." #: wp-cache.php:2605 msgid "" "Preload has been restarted.\n" "%s" msgstr "" "\"Preload\" wurde neu gestartet \n" "%s" #: wp-cache.php:2648 msgid "Supercache Uninstall Problems" msgstr "Supercache Probleme beim Deinstallieren" #: wp-cache.php:2648 msgid "" "Dear User,\n" "\n" "WP Super Cache was removed from your blog but the mod_rewrite rules\n" "in your .htaccess were not.\n" "\n" "Please edit the following file and remove the code\n" "between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!\n" "\n" "%s\n" "\n" "Regards,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" msgstr "" "Lieber Benutzer,\n" "\n" "WP Super Cache wurde von deinem Blog entfernt, aber die mod_rewrite rules\n" "in deiner .htaccess nicht.\n" "\n" "Bitte bearbeite fogende Datei und lösche den Code\n" "zwischen 'BEGIN WPSuperCache' und 'END WPSuperCache'. Und bitte erst die Datei sichern!\n" "\n" "%s\n" "\n" "Mit freundlichem Gruß,\n" "WP Super Cache Plugin\n" "http://wordpress.org/extend/plugins/wp-super-cache/" #~ msgid "" #~ "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on " #~ "on the main site of this network." #~ msgstr "" #~ "Hinweis: WP-Super-Cache mod_rewrite rule Checks sind deaktiviert, " #~ "insofern sie nicht auf der Hauptseite dieses Blog-" #~ "Netzwerks laufen." #~ msgid "Tester & Contents" #~ msgstr "Teste & Cache" #~ msgid "" #~ "Logging to a file is easier but faces the problem that clearing the cache " #~ "will clear the log file." #~ msgstr "" #~ "Das Protokoll in eine Datei zu schreiben ist einfacher, bringt aber das " #~ "Problem mit sich, dass die Log-Datei beim Cache-Leeren ebenfalls entfernt " #~ "wird." #~ msgid "Logging Type" #~ msgstr "Protokoll-Typ" #~ msgid "Email" #~ msgstr "E-Mail" #~ msgid "file" #~ msgstr "Datei" languages/wp-super-cache-zh_TW.mo000066600000222204152133035240012727 0ustar00 #("<)"3f"M"""` # j#~v#?#5$D$*$7%5H% ~%=&b&j-'-'$' 'r ((v#))u*K+k+C,?>-~.I//0B11wt1%1224.O5~6&77^7:o7n8p9::::*; 3;@;R;f; ;;3;;;<< < <?<j=,==^`>p>+0?\?c?y?n?/h@@ @ @G@`@+`AA3AAAAxB=B!BB!DBDE1E8EIE@1FrFsFkGGAG%6H\HJuHI II IIIJ5!J WJxJJ3KK1KKYLoL.MMM4M'NNuN \Oj}OGO0P5P*P?QQQXQSkQQ}QERNKRRRSnS$TA)TkTrTxTTTTeTFUVVV VV<Vg0WW+WW*WXXyXX YbYZ[&[] ]"#]kF^_W_`E#`i`*``da a aaLa]a$Zbb bbbbbcc:d$Ld"qdd!dd eefDff(f&g<,gbig gyhRifi0ii i!i-i:ik2kl l lllmlTRmmUmnpnU Ԣ.1K)}ǣ*/&.V3ؤܤ A٦"A>fj#9Ȩר'n<*ө@[U\.Nonެ{ jM{ɯs Dϵ)W&ub%غSlhFռ : G|Sо ׾# /<8Z CP c pK}l*6aZlm2 x+-%S Z gKtW*C1\o3/c|!%?G Kt*~ejh9E@,S )0 7$Di|742#$+02cpxd@ =J+E%krQ_Mf^Ddkr c* <_ n${p!4i;PG  Y( \B?'X!-O V`BxW-'Aip!Xz"!5!Wy! ui6 D^@{ *78> w'-e>S f t nOgBRH: % MF0N^%dy$ -H0[>,*6ua!w"U  & 3@KQ!,' ,`K *+69 17uE, 9xgw]vsw~* </ l  S7  j  i  z  $$C hs29L f s,KT%zdQa\-b  &0IIhB%?e-<j\_ >GK-p92l) jx#Cr@!M=\ @" a"""3"+"(#H#`#5u#5#)#) $#5$Y$ `$ j$t$ x$ f]!Z]L&UwdC=y8.$:)Jf(uSA6zxi GQY 0sk 'M/DIahNSW@ g5LlKOE7j,PG5NmkVT`pv"r{;~#jvtaE?FMql}R 9tnP[ 0BKB=%Co e-Abcds/;1. > |V$Z4oYH33e _<"\\n[,7g D?~h2:QbXpF}w<4_-+I'y|6(#OmUx>J&`THXu9{qiR+r@c^^z1W8)2%*!* Make sure they appear before any existing WordPress rules. %1$s is Stephen Fry proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumCron View is a useful plugin to use when trying to debug garbage collection and preload problems.Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WPSCMin, a Supercache plugin that minifies cached pages by removing whitespaces and extra characters Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.This page explains how to change file permissions.UTC time is %sGarbage collection is the simple act of throwing out your garbage. For this plugin that would be old or stale cached files that may be out of date. New cached files are described as fresh.

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the Troubleshooting Guide. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.DO NOT CACHE PAGE secret key: %sError: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.Warning! Due to the way WordPress upgrades plugins the plugins you upload to wp-super-cache/plugins/ will be deleted when you upgrade WP Super Cache. You can avoid this by loading the plugins from elsewhere. Set $wp_cache_plugins_dir to the new location in wp-config.php and WP Super Cache will look there instead.
    More info available in the developer documentation.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAuthor PagesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache Status MessagesCache TesterCache TimeoutCache expiry cron job failed. Job will run again in 10 seconds.Cache expiry cron job took more than 30 seconds. You should probably run the garbage collector more often.Cache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.CachedCached %s seconds agoCached files are fresh for a limited length of time. You can set that time in the Cache Timeout text box on this page.Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below.Cached pages since %1$s : %2$sCachingCaching OffCaching OnCaching has been disabled on this blog on the Network Admin Sites page.Caching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck for stale cached files at this time (UTC) or starting at this time every interval below.Check for stale cached files every interval seconds.Check front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 600 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published or updated.Clear cache on error.Clock:Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.ContentsCould not update %s! WPCACHEHOME must be set in config file.Currently caching from post %d to %d.Currently logging to: %sDear User, WP Super Cache was removed from your blog but the mod_rewrite rules in your .htaccess were not. Please edit the following file and remove the code between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first! %s Regards, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggingDeleteDelete CacheDelete Cache On All BlogsDelete Cached PagesDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cache of the current pageDelete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDisplay comments at the end of every page like this:Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.Don’t cache pages with GET parameters. (?x=y at the end of a url)EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. Email me when the garbage collection runs.Email the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnable logging on the Debug page here. That should help you track down the problem.EnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExcludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default).Existing direct pageExpired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionExtra homepage checks. (Very occasionally stops homepage caching)FAILEDFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.HH:MMHe blogs at %1$s and posts photos at %2$s.Hide file listHomeHow long should cached pages remain fresh? Set to 0 to disable garbage collection. A good starting point is 3600 seconds.I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesInterval:It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match.Local time is %1$sLock DownLock Down:Make WordPress FasterMake known users anonymous so they’re served supercached static files.Make the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile BrowsersMobile PrefixesMobile device support. (External plugin or theme required. See the FAQ for further details.)Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next scheduled garbage collection will be at %s UTCNo Adverts for FriendsNo Adverts for Friends support is now %sNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.Notification EmailsOKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.Or, the Clock scheduler allows the garbage collection to run at specific times. If set to run hourly or twicedaily the garbage collector will be first scheduled for the time you enter here. It will then run again at the indicated interval. If set to run daily it will run once a day at the time specified.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preload tags, categories and other taxonomies.Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Stephen Fry proof! (places a message in your blog’s footer)Provides support for No Adverts for Friends.Provides support for Domain Mapping plugin to map multiple domains to a blog.Provides support for WPTouch mobile theme and plugin.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRemove UTF8/blog charset support from .htaccess file. Only necessary if you see odd characters or punctuation looks incorrect. Requires rewrite rules update.Required to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache almost cancelled. It may take up to a minute for it to cancel completely.Scheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.SchedulerScheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSites that want to serve lots of newly generated data should set the Cache Timeout to 60 and use the Timer scheduler set to 90 seconds.Sites where an external data source updates at a particular time every day should set the timeout to 86400 seconds and use the Clock scheduler set appropriately.Sites with lots of static content, no widgets or rss feeds in their sidebar can use a timeout of 86400 seconds or even more and set the timer to something equally long.Sites with widgets and rss feeds in their sidebar should probably use a timeout of 3600 seconds and set the timer to 600 seconds. Stale files will be caught within 10 minutes of going stale.Skip https URLs to avoid "mixed content" errorsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStale cached files are not removed as soon as they become stale. They have to be removed by the garbage collecter. That is why you have to tell the plugin when the garbage collector should run.Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Supercache Uninstall ProblemsTagsTest CacheTest your cached website by clicking the test button below.Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin.The Timer scheduler tells the plugin to run the garbage collector at regular intervals. When one garbage collection is done, the next run is scheduled.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!There are no best garbage collection settings but here are a few scenarios. Garbage collection is separate to other actions that clear our cached files like leaving a comment or publishing a post.These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$sThings you can do:This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.Timer:To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.Use the Timer or Clock schedulers to define when the garbage collector should run.Use the debug system in the Debug tab above. It will tell you what the plugin is doing.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWPTouchWPTouch plugin detected! Please go to the Supercache plugins page and enable the WPTouch helper plugin.WPTouch support is now %sWarningWarning!Warning! %s is writeable!Warning! 304 browser caching is only supported when not using mod_rewrite caching.Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age.Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d[%1$s] Refreshing posts from %2$d to %3$d[%1$s] WP Super Cache GC Report[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledsecondstimezone date formatY-m-d G:i:sProject-Id-Version: WP Super Cache (Traditional Chinese) Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2012-06-21 09:44:46+00:00 PO-Revision-Date: Last-Translator: Liang, Jih-Kai Language-Team: privism MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Chinese X-Poedit-Country: TAIWAN X-Poedit-SourceCharset: utf-8 確認它們出現在任何已存在的 WordPress 規則之前。%1$s 使用的快取程式為 %2$s%1$s由%2$s開發及維護，並得到許多人的幫助貢獻。%s 個頁面已快取%s 個頁面已過期%s 可寫入。由於這牽涉到一個安全風險，請在你的網頁產生後把它設為唯讀。%s 已移除！%s.htaccess 已更新必要的 mod_rewrite 規則。請確保它們是正確的。它們應該像這樣：%s/advanced-cache.php 不存在或是無法更新。(實驗選項)（只支援傳統模式，停用壓縮，Bad Behavior 路徑必須為 "%s/plugins/bad-behavior/"）（在忙碌的網站上未必準確）（僅記錄來自此IP位址的請求。你的 IP 是 %s）1. 如果它已經存在，請先刪除。2. 請使用你的FTP程式或伺服器軟體，以 chmod 指令使%1$s可寫入。（chmod 777 %1$s），並重新整理此頁面。這只是一個暫時的作法，你事後必須再把它變更為唯讀。（使用前面的指令，將權限從 777 變更為 755）3. 重新整理此頁面以更新 %s/advanced-cache.php304 未修改支援。當一個頁面在上次被要求後沒有被更改的時候送出。304 支援預設為停用，因為過去GoDaddy在它使用的某些檔頭會產生問題。常見問題安裝指南支援論壇Cron View 外掛，在你想要針對垃圾回收及預先載入問題除錯時相當有用。Use Google Libraries可以讓你從 Google 的伺服器上載入一些常用的 Javascript 函式庫。很諷刺的是它會降低你的 Yslow 分數。WPSCMin，一個 Supercache 的外掛，藉由移除多餘的空白和無用的字元將頁面最小化。Yahoo! Yslow 是 Firefox 附加元件 Firebug 的一個延伸套件。它可以分析你的網頁，並根據一些高效率網頁規則，建議你增加效能的方式。 你也可以試試一個線上效能分析工具 GTMetrix。這邊解釋如何變更檔案權限。UTC 時間是 %s垃圾回收就是將你的垃圾丟掉的簡單動作。以此外掛來說，垃圾就是指舊的或失效 (stale) 的檔案。新的快取檔案則稱為有效 (fresh) 快取。

    WP_CACHE 不斷被新增到 wp-config.php

    如果你持續看到此警告訊息，請參閱 常見問答 第五點。WP_CACHE 原始碼必須往前移動。

    WP_CACHE 變數被設為 false

    WP_CACHE 變數被WordPress用來載入快取程式，可是它被設為 false(關閉)。請編輯你的 wp-config.php 檔並把以下的內容放在最後的 require_once 命令之前。

    define('WP_CACHE', true);

  • 1. 以文字編輯器開啟 %1$s$wp_cache_file。
  • 2. 將 CACHEHOME 變更為 %2$s
  • 3. 儲存檔案並複製為 %3$s，然後重新整理此頁面。
    • 警告： 請先測試一些固定的網址，例如%s。在儲存變更前，確定你的 CDN 服務完全正常。進階使用者專用： 使用快取及快取控制加速你的網站，解釋怎麼讓你的網站更適用 .htaccess 規則來進行快取。進階使用者專用： 安裝物件快取。 你可以從 Memcached、XCache、eAcccelerator 或其它的加速器中選擇一個。存取非快取頁面 密鑰： %s錯誤：在你的 wp-config.php 檔案裡 WP_CACHE 是停用狀態，且無法修改。最新快取頁面： %s警告！ 你試著要開啟壓縮，但是 zlib.output_compression 已被啟用。 參見讀我檔案裡錯誤排除段落第21條。警告！ 肇因於 WordPress 升級外掛的方式，上傳至 wp-super-cache/plugins 的外掛在升級 WP Super Cache 將會被刪除。你可以把外掛放到別的地方以避免此一問題。在 wp-config.php 中設定 $wp_cache_plugins_dir 至新的位置，WP Super Cache 將會改用此一新位置。
    開發者文件中有更多的資訊。外掛要正常運作，必須有自定 url 或固定網址。請到固定網址選項設定你的固定網址。發現 .htaccess 的 rewrite 規則和外掛 rewrite 規則的不一致。有可能只是單純空白字元的差別，但是你應該立即比較以下的規則。 點擊「更新 Mod_Rewrite 規則」按鈕以更新規則。最簡單的方式是使用 CHMOD 指令或透過 FTP 程式來變更權限。請確保它們正確並可以寫入。接受的檔案名稱和拒絕的 URI新增直接頁面：在下方輸入框內新增字串（不是檔案名稱），控制不要被快取的頁面。舉例來說，如果你的 URL 中包含年份，但你不想快取去年的文章，那麼就指定年份，例如 ’/2004/’ 。WP-Cache 將會搜尋這個字串是否包含在URI之中，如果是的話則不會快取這個頁面。這是可以被快取的檔案名，即使它們與上方設定的拒絕字串相符時也仍將被快取。自行加入規則。編輯 %s.htaccess 並找到 # BEGIN WPSuperCache 和 # END WPSuperCache 之間的原始碼區段。有兩個區段非常相似。緊接著 %%{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ 的下方新增這幾行(要做兩次，一個區段一次)：額外的正規名稱(CNAMES)進階選項時間(秒)或者，你可以手動編輯 %s.htaccess 檔案並加入以下原始碼（在任何 WordPress 規則前）：存檔作者頁面可使用的外掛Awaiting ModerationAwaiting Moderation 外掛模組 %sBad BehaviorBad Behaviour 外掛模組 %s找不到 Bad Behaviour。請檢查是否正確安裝。CDNCDN 功能由OSSDL CDN Off Linker提供，作者為Mark Kubacki快取內容快取狀態訊息快取測試快取逾時執行清除過期快取的排程時失敗。將在十秒內再次執行。定時清除快取花費了超過三十秒以上的時間。你可能需要更常執行垃圾回收功能。啟用快取以加速對本網站的存取快取外掛是 wp-super-cache 裡 plugin 資料夾中的一些 PHP 程式。它們在 Supercache 載入的時候就會被載入，比一般的 WordPress plugin 要早得多。重建快取。當新檔案重建的時候，提供 supercache 檔案給匿名使用者。快取統計不會自動產生，你必須點擊以下的連結，本頁的統計資料才會重新產生。快取統計最後產生時間：%s分鐘以前。已快取於 %s 秒前快取快取檔案有一定限度的有效期限。你可以在本頁的快取逾時文字方塊設定這個期限。快取頁面以 html 和 PHP 檔案的形式儲存在你的伺服器上。如果你需要刪除它們，請按下面的按鈕。快取頁面自 %1$s ：%2$s快取關閉快取開啟快取這個部落格的快取，已經在站台網路管理頁面中被關閉。快取只是讓網站變快的方法之一。這邊是一些其它有幫助的外掛：必須啟用快取才能使用這個功能取消快取預先載入無法繼續... 解決前述問題然後重試。無法更新 .htaccess分類變更過期時間在下列時間 (UTC) 檢查失效快取，或從此時間開始每段間隔檢查。每隔幾秒檢查失效的快取檔案。每五分鐘檢查首頁檢查和刪除過期檔案代價高昂，但把這些檔案留在那裡也一樣。在非常忙碌的網站，你應該將過期時間設定為 600 秒。嘗試使用不同的數值，並注意這些頁面一天裡在不同時段產生多少過期檔案，如果使用傳統快取，可能的話盡量不要讓快取檔案數多於 500 個。若使用 mod_rewrite 或 PHP 快取，快取數量可以增加數倍。清除舊的 supercache 檔案。當發布或更新文章、網誌分頁時清除所有快取。清除快取時發生錯誤。時刻：粗略檔案鎖定。你大概不會用到這個功能，但如果你的伺服器效能較差，開啟後可能會有所幫助。警告！可能在少數情況下鎖死你的伺服器！迴響審核已啟用。您的迴響可能需要一些時間才會顯示。壓縮網頁，讓訪客能更快速觀看壓縮預設為停用，因為某些主機在壓縮檔案時可能發生問題。啟用或停用這項功能會清除快取。設定檔已變更，某些數值可能錯誤。再次從"設定"選單讀取頁面以重設選項。設定檔遺失，%1$s 目錄（%2$s）也無法被伺服器寫入。請檢查權限。內容無法更新 %s！ WPCACHEHOME 必須在設定檔中被設定。目前正在快取第 %d 到 %d 篇文章。正在記錄到：%s親愛的使用者， WP Super Cache 已從你的部落格被移除，但是 .htaccess 中的 mod_rewrite規則仍然存在。 請編輯下列檔案並移除 'BEGIN WPSuperCache' 及 'END WPSupercache' 之間的原始碼。 請先備份這個檔案！ %s WP Super Cache Plugin 敬上 http://wordpress.org/extend/plugins/wp-super-cache/除錯設定除錯刪除刪除快取刪除所有部落格的快取頁面刪除快取頁面刪除過期檔案刪除 Super Cache 快取檔案（在新視窗打開）刪除目前頁面的快取刪除快取檔案從 %s.htaccess 內刪除 # BEGIN WPSuperCache 和 # END WPSuperCache 之間原始碼區段的 mod_rewrite 規則，之後重新載入本頁讓外掛再次產生規則。刪除 supercache 檔案：%s
    刪除 wp-cache 檔案：%s
    開發者：透過檢查 "WPLOCKDOWN"，讓你的外掛與鎖定功能相容。下面的原始碼將確保你的外掛遵守 WPLOCKDOWN 設定。直接快取檔案直接快取檔案是從你的部落格 %s 產生直接建立的檔案。這項功能只在你預測將會有從 Digg 或 Slashdot 大量流量進入某篇文章或頁面時才有用。靜態檔案比對包含的目錄。使用逗號作為分隔符號。預設為 wp-content, wp-includes ，當這個欄位空白時會強制套用。停用停用顯在每頁的頁尾顯示像這樣的評論：不快取以下頁面類型。查看條件標籤文件中對每個類型的完整探討。Domain MappingDomain Mapping 外掛模組已被偵測到！請到 Supercache 外掛頁面啟用 domain mapping 支援外掛。Domain Mapping 外掛模組 %s不要為已知使用者快取。不快取使用 GET 參數的頁面。(結尾有 ?x=y 的網址)簡易模式編輯 %s 並加入以下原始碼：
    define('WP_CACHE', true);
    否則，WP-Cache 將無法被 WordPress 核心執行。在垃圾回收執行時寄 email 給我。當檢查時寄送電子郵件給網站管理員。（供測試用）啟用啟用 CDN 支援在本除錯頁面開啟記錄功能，應該可以幫助你找出問題所在。啟用啟動或關閉此外掛，決定當有人發佈需審核的迴響時，是否去除「您的迴響正等待審核中」字樣。錯誤錯誤：GZIP 壓縮已啟用，如果你想啟用 wp-cache，請停用它。若含有以下字串則排除若網址中包含以上的字串，則不會被重寫。使用逗號作為分隔符號，像這樣：.php, .flv, .do，並請永遠包含.php (預設值)。已存在的直接頁面過期檔案是超過 %s 秒鐘的檔案。它們仍然會被外掛使用並會定期刪除。過期時間與垃圾回收額外的首頁檢查(有很小的機會導致首頁快取停止)。失敗訂閱抓取 %s 至主要快取：抓取第一份%s：抓取第二份%s：修復設定在這裡使用外掛除錯模式解決問題。它可以在你的快取目錄內產生紀錄檔。為了獲得最好的效能，你應該啟用"行動裝置支援"，或從你的 .htaccess 刪除行動裝置重寫規則。尋找包含 "2.0\ MMP|240x320" 字串的兩行並刪除它們。舉例來說：快取 %1$sabout/, 你應該輸入 %1$sabout/ 或 /about/ 。快取檔案將在下一個匿名使用者訪問該頁面時產生。有效的 Super Cached 檔案有效的 WP-Cached 檔案首頁首頁文字完整更新快取，耗費了 %d 小時 %d 分鐘 %d 秒。在 WordPress 上 GZIP 壓縮已啟用，wp-cache 將被繞過，直到你停用 gzip 壓縮。垃圾回收%s.htaccess 內 gzip 規則建立。HH:MM (時:分)我的部落格在 %1$s，相簿在 %2$s。繁體中文翻譯問題請洽priv隱藏檔案清單主頁設定快取的有效期限。設定 0 以關閉垃圾回收功能。可以從 3600 秒先開始嘗試。我有十足的把握肯定，它們不是 WP Super Cache 的錯誤。它只會發生在極少數的情況下，但如果你擔心的話，你可以每5分鐘進行一次簡單的檢查，以確保你的網站是正常的。如果有問題，你將會收到電子郵件。IP位址如果無法運作，請確認 %s/advanced-cache.php 檔案不存在：如果移除這個外掛，請確認目錄 %s 為伺服器可以寫入，advanced-cache.php 和 cache-config.php 檔案會自動刪除。（確認這些檔案是可寫入的，也是個好主意！）在「預先載入」模式，通常的垃圾回收只會清除給已知使用者的傳統快取檔案，而不會清除預先載入的 supercache 檔案。這是預先載入的建議設定。在極少數的部落格可能會出現兩個問題：
    1. 在首頁可能會以一個 zip 檔案開始下載。
    2. 如果你的部落格使用一個靜態的首頁，或以 /%category%/%postname%/ 作為固定網址結架構的話，那麼錯誤的頁面有時候會被當成首頁被快取起來。
    包含以下目錄間隔：看來 mod_rewrite 沒有安裝。有時候這種檢查並非 100% 可信，特別是當你不是使用 Apache 時。請重新檢查 mod_rewrite 模組已經載入。執行 Super Cache 靜態檔案時必須要有它。但你仍然可以使用傳統或PHP快取模式。看起來你的部落格有以"/"結束的 URL。不幸地在你安裝這個外掛後，在URL不是以"/"結束的頁面，發現了一個重複內容的 bug，也就是相同的內容卻不是被指向正確的 URL。你必須修改你的 .htaccess 檔案以修復這個問題，在兩個 Super Cache 規則區段內新增下面兩個規則：關鍵字延遲初始化，在 WordPress 載入之後再顯示快取。通常使用在傳統模式。傳統快取模式較少信件，開始的時候一封還有結束的時候一封。列出所有快取檔案在本頁列出最新的快取頁面。在已登出的瀏覽器載入你的首頁，檢查html結尾的時間標籤，並再次載入頁面並比較時間標籤。快取如果有效時間標籤會是一致的。本地時間是 %1$s鎖定鎖定：讓 WordPress 更快速讓已知使用者匿名化，以靜態快取檔案服務他們。將輸入框清空，就能將它從直接頁面清單中移除並刪除快取檔案。很多信件，每一百篇文章二封信。中等，每一百篇文章一封信。雜項Apache 模組遺失行動瀏覽器行動前置字串行動裝置支援 (需要外掛或額外的主題來支援。 參見常見問答以獲得更多資訊。)偵測到行動裝置重寫規則行動裝置支援必須在你的 .htaccess 檔案裡新增額外規則，或是你可以將外掛設定為傳統模式。這是你的選擇（依難易度排列）：Mod Rewrite 規則Mod Rewrite 規則無法更新！Mod Rewrite 規則必須更新！Mod Rewrite 規則已更新！Mod rewrite 可能沒有安裝！Mod_rewrite 快取是最快的，PHP 快取幾乎一樣快且較容易上手；傳統模式較慢，但是有更多的彈性且同樣容易上手。新使用者應該使用 PHP 快取。需要幫助?需要幫助？ 看看Super Cache 讀我檔案。 它包含了安裝資訊，常見問題及錯誤排除小技巧。另外在支援論壇上，你的問題可能也已經有人回答過了。最新的快取頁面：下次垃圾回收排程時間 %s UTCNo Adverts for FriendsNo Adverts for Friends 支援 %s備註：說明：啟用 PHP 快取，重建快取，以及行動裝置支援注意：Mod_rewrite 或傳統快取已被開啟。 預設顯示進階選項頁面。注意：PHP 快取已被啟用，但偵測到 Supercache mod_rewrite 規則。快取檔案會用這些規則來服務。如果你的網站動作正常，你可以忽略這個訊息，否則請編輯站台安裝根目錄下的 .htaccess 檔以移除 SuperCache 規則。注意：除非在這個網路的主站上執行，WP Super Cache mod_rewrite 規則檢查會被關閉。s通知郵件完成正在使用 Object 快取。無法顯示快取清單。站外 URL一個或以上的頁面要求失敗：當迴響發佈時，只更新目前頁面。而時刻排程器，可以讓外掛在指定的時刻執行垃圾回收。如果設定為每小時 (hourly) 或兩天一次 (twicedaily) 執行，垃圾回收會在你輸入的時刻第一次被執行，接下來會在設定的間隔時間後再執次行。如果設定為每日 (daily) 執行，那他會在每天你設定的時刻執行一次。PHP頁面壓縮啟用中。建議將它關閉，因為外掛針對一個頁面只需要壓縮一次，而不需要反覆的壓縮。另請參見錯換排除段落第21條。 這邊有如何修改php.ini的說明。頁面 %d: %d (%s)頁面1： %s頁面2： %s網誌分頁固定網址結構錯誤請為這個外掛評分，並告訴我它是否運作正常。這對開發非常有幫助。請以 wp-super-cache/wp-cache-config-sample.php 建立 %s /wp-cache-config.php在%s上向我問好！請參閱 readme.txt 第 16 項錯誤排除段落反安裝資訊請參見 readme.txt，尋找 "How to uninstall WP Super Cache" 標題。請前往 %1$s 清除快取，部落格的首頁不正確，缺少文字 "%2$s"！請前往 %s 清除快取，網站的首頁正在下載！外掛預先載入預先載入 %s 篇文章。馬上開始預先載入預先載入已經被重新啟動. %s預先載入模式(只對傳統模式快取做垃圾回收。建議選項。)預載標籤，類別，以及其它的分類。不過預先載入會產生很多檔案。快取會從最新的文章開始做到最早的文章，所以當你有非常多 (10,000+) 文章的時候，可能只會有新文章被快取到。這在共享主機上特別重要。預先載入已被關閉。請關閉傳統模式或和主機管理員連絡。如果你預測會有流量高峰到來時，可以啟用鎖定功能。當這個功能啟用時，在文章裡發佈新迴響將不會更新靜態快取檔案。告訴全世界你的伺服器不怕 Stephen Fry (一個名人)攻擊！（在你的部落格底部放置一段訊息）No Adverts for Friends 外掛支援。Domain Mapping外掛支援，映射多個網域至一個 blog。WPTouch 行動裝置主題外掛支援。為這個外掛評分！唯讀模式。設定無法變更。唯讀：建議選項建議連結及外掛在%d小時%d分鐘%d秒之後更新快取。每 %s 分鐘更新預載快取檔案。(0 關閉，最低 %d 分鐘。)在權限修改後請重新整理這個頁面。當你已更新你的 .htaccess 檔案後重新整理此頁。已更新下列文章：重新產生快取統計被拒絕的使用者代理（User Agents）從 .htaccess 中移除 UTF8 字元集支援。只在你看到奇怪的字元或錯誤的標點時才需要。必須更新重寫規則。需要此模組以正確提供 supercache 壓縮檔。需要此模組以設定在 supercache 頁面的快取資訊。若無此模組，IE7使用者將會看到舊頁面。還原到預設選項Mod Rewrite 規則必須更新！也必須新增到 %s 的規則：WP-Cache 設定檔範本（%s）不存在。請確認你的安裝。儲存儲存變更儲存檔案儲存字串儲存 UA 字串預載快取排程即將取消。完全取消可能要花費至一分鐘。預載快取排程已被取消。下次預載快取排程時間：%d分鐘後預載快取將在十秒之後開始。排程器下次更新預載快取時間：%d分鐘後捲動到進階選項頁面的下方並點擊更新 Mod_Rewrite 規則按鈕。搜尋頁面當檔案被更新的時候寄信給我。以非加密 (非 https) 傳輸請求首頁設定 supercache 快取頁面過期時間。沒有這個模組，訪客在重新整理或留下迴響時可能看不到新頁面。把過期時間設定為 0 以關閉垃圾回收功能將外掛設為傳統模式並開啟行動裝置支援。設定單篇文章希望提供大量動態資料的站台，應該將快取逾時設定為 60 秒，並使用 90 秒的計時排程。在每天固定時刻使用外部資料來源更新的站台，則應該將逾時設為86400秒，並將時刻排程設定在適當的時間。有大量靜態內容，邊欄沒有小工具及 rss 饋料的站台，可以使用 86400 或更長的逾時，並將計時排程設定為等長的時間。在邊欄有小工具及 rss 饋料的站台，也許應該設定 3600 的逾時，以及 600 秒的計時排程。失效的檔案會在失效十分鐘後被清除。跳過 https 網址以避免「混合的內容」錯誤抱歉。我的部落格已經鎖定。將會在短時間後更新。失效的 Super Cached 檔案失效的 WP-Cached 檔案失效的快取檔案並不會在失效的時候馬上就被移除。他們必須被垃圾回收機制移除。這就是為什麼你必須告訴外掛何時執行垃圾回收。HTTP User Agent；防止快取機器人、蜘蛛或抓取器對於 WP-Cache 的請求。請注意，如果快取檔案已經存在，仍然會發送給這些代理。Supercache 反安裝問題標籤測試快取請按下面的測試按鈕以測試你的網站快取。在你的首頁裡要搜尋的文字。如果缺少這些文字時快取將被清除。保留空白停用這個功能。感謝升級。如果你不希望依賴 origin pull，CDN Sync Tool 是一個幫助你上傳檔案到 Amazon S3/Cloudfront 的外掛。 如果你對此外掛有任何問題，請參見 外掛支援論壇。計時排程器以一定的時間間隔執行垃圾回收。當一次垃圾回收完成後，就會再度進行下一次的排程。WP Super Cache 設定檔 %s/wp-cache-config.php 無法修改。該檔案必須允許從伺服器端進行寫入以進行設定變更。你的部落格已被清除快取，因為你的部落格首頁缺少文字 "%2$s"。請前往 %1$s 確認快取已被清除。你的部落格快取已被清除。因為你的部落格首頁正在下載，請前往 %s 確認快取已被清除。%s.htaccess 檔案無法被網頁伺服器更新。請使用 chmod 指令或透過 FTP 程式修正。以下的 Apache 模組遺失。沒有它們外掛將在傳統模式下工作。若在完整的 Supercache 模式，你的訪客可能會看到損壞的網頁或是過時的內容。從你上次安裝此外掛，mod_rewrite 規則已經變更。在新的 supercache 規則更新前，你必須先刪除舊的 supercache 規則。在你修改你的 .htaccess 檔案後重新整理此頁。如果你希望手動更新，更改以下幾行：%1$s 使它看起來像這樣：%2$s ，唯一改變的地方是 "HTTP_COOKIE" 變成 "HTTP:Cookie" 以及 "wordpressuser" 變成 "wordpress"。這是 WordPress 2.5 的改變，但如果你敢使用，它與舊版本相容。這個新的 URL 在會重寫時用來取代 %1$s。請不要加上結尾的 /。
    例： %2$s無頁面時間標籤或標籤不相符！這個外掛所需的重寫規則已被變更或不存在。頁面時間標籤相符！並沒有最佳的垃圾回收設定，不過這裡列出幾個情境。垃圾回收和其它會造成清除快取的情形，例如留言和發佈文章，是有區別的。這些 正規名稱記錄(CNAMES) 會在重寫時用來取代 %1$s (和上面的站外URL一起)。 使用逗號作為分隔符號。 在有大量靜態檔案的網頁中，這可以增進瀏覽器效能。 這些正規名稱可能也需要在你的 CDN 被設定。
    例： %2$s你可以做的事：這是一個非常進階的功能，只有對 PHP 和 Wordpress 動作都非常了解的人才能撰寫。這會快取你網站上所有已發布的文章和頁面。它會產生 supercache 靜態檔案，匿名訪客(包括機器人)會命中快取頁面。這有可能會對你的 Google 排名有幫助，因為他們也將網站速度納入衡量項目之一。這不會對一般使用者造成任何影響，但行動裝置使用者將會看到未快取的頁面。計時：為了使用靜態的 HTML 檔案，你的伺服器上必須有正確的 mod_rewrite 規則，新增到一個名為 %s.htaccess 的檔案。快取檔案過多，無法列出。尾端斜線的檢查是必須的。URI 網址很抱歉，WordPress 找不到 wp-cron.php 檔案。必須要有這個程式才能正確執行垃圾回收、排程文章及其他重要活動。抱歉，當執行 WordPress MU 時重寫規則無法自動更新。請開啟你的 .htaccess，並在上述檔案中任何位置加入下方的 mod_rewrite 規則。請在外掛頁面反安裝此外掛。它將會在反安裝後將設定清除。如需手動介入，亦會提供簡單的指示。更新更新直接頁面更新 Mod_Rewrite 規則更新狀態更新狀態使用 PHP 快取使用 mod_rewrite 快取使用 object 快取來儲存快取檔案。使用計時或時刻來決定何時執行垃圾回收。請使用上方除錯分頁的除錯系統，它會告訴你這個外掛的功能。查看 Mod_Rewrite 規則WP Super Cache 狀態WP Super Cache 已檢查過你部落格的首頁。如果你想停用這項功能，請前往 %s 。WP Super Cache 停用。請前往 外掛管理員啟用快取。在你的 %s.htaccess 檔案中已經檢測到 WP Super Cache 重寫規則。
    點選以下連結，查看新增到該檔案的內容。如果你已經升級外掛，請確保與這些規則相同。WP Super Cache 必須設定。請前往管理後台啟用和設定外掛。WP-CacheWP-Super-CacheWPTouchWPTouch 外掛模組已被偵測到！請到 Supercache 外掛頁面啟用 WPTouch 支援外掛。WPTouch 支援 %s警告警告！警告！%s 可寫入！警告! 304 瀏覽器快在不使用 mod_rewrite 快取時才能支援。警告 預載模式 已被啟用。Supercache檔案將不會由於過期而被刪除。警告！因為找不到 gzencode() 函式，壓縮已被停用。警告！PHP 安全模式已啟用！警告！ WP Super Cache 快取毀損！ advanced-cache.php 腳本無法載入 wp-cache-phase1.php。

    請編輯 %1$s/advanced-cache.php 並且確認指向 %2$swp-cache-phase1.php 的路徑是正確的。警告！你的主機名稱 "%s" 解析到 %s偵測到 WordPress MUWordPress 已鎖定。新的迴響產生時將不會刪除 Super Cache 靜態快取檔案。WordPress 未鎖定。新的迴響產生時將會正常更新 Super Cache 靜態快取檔案。可寫入：你可以為多站台網路中的每個站台定義不同的 CDN URL。你可以自行編輯並新增以下規則。你可以看到規則去向，透過點選下方的「查看 mod_rewrite 規則」連結來看到完整的規則在安全模式下，你的外掛可能會遭遇錯誤。要讓它自動工作，你必須在 %s.htaccess 上有 BEGIN 和 END 標記，它們看起來像這樣，圍繞 WordPress 的主要 mod_rewrite 規則：啟用這項功能前必須確認 %s 是可寫入狀態。由於這牽涉到一個安全風險，請在你的網頁產生後把它設為唯讀。你或管理員可以透過變更外掛程式群組的所有者使其與伺服器使用者一致，進而讓其運作。%s/cache/ 目錄的所有者也必須變更。查看安全模式使用手冊以取得更多說明。你或管理員必須先停用此項目。查看安全模式使用手冊以取得更多說明。很抱歉，這無法在 .htaccess 檔案裡停用。它必須在 php.ini 設定檔中完成。你應該變更 %s 權限使其更加嚴密。使用你的FTP程式，或是按照以下指令來解決：檢查上面第一頁及第二頁的錯誤。你的本機伺服器設定可能不允許你的網站存取自己本身。你的 %s.htaccess 無法由伺服器寫入，必須更新 mod_rewrite 規則。新的規則必須在一般的 WordPress 規則之上，如下面的原始碼所示：你的 WP-Cache 設定檔（%s）已經過期，且無法由伺服器端寫入，請刪除它並重新整理此頁面。你的快取目錄（%1$s）不存在，且無法從伺服器端建立。請檢查 %1$s 權限。你的快取目錄（%1$s）或 %2$s 必須讓外掛可寫入才能正常運作。請重新檢查一次。您的迴響正等待審核中。你的伺服器設定為先檢查 PHP 程式擁有者才可以存取檔案。你的伺服器認為你的主機名稱解析到 %s 。 WP Super Cache 外掛的某些服務，例如垃圾回收、WordPress 排程文章可能無法正常執行。你的網站可能使用了許多的靜態檔案。圖片、Javascript、CSS 檔案通常都是靜態檔案，可以很簡單地使用另一個站台或 CDN (內容傳遞網路)來服務。所以這個外掛會根據你下面所提供的 URL，取代你的網站中 wp-content 和 wp-includes 目錄下除了 PHP 檔案以外的任何連結。用這個方式，你可以把所有的靜態內容拷貝到一個專用的主機或或使用 origin pull 鏡射到 CDN 上。Zlib 輸出壓縮已被啟用！[%1$s]%2$d 篇文章已被更新[%1$s] 快取預載已經開始[%1$s] 快取預載已停止[%1$s] 更新 %2$s 分類第%3$d 到 %4$d 篇文章[%1$s] 更新第 %2$d 到第 %3$d 篇文章[%1$s] WP Super Cache 垃圾回收報告[%s] 預載快取完成[%s] 首頁檢查！[%s] 首頁已使用 gzip 壓縮！快取已清除！[%s] 首頁已使用 gzip 壓縮！請清除快取！[%s] 首頁不正確！快取已清除！[%s] 首頁不正確！請清除快取！[%s] 預先載入可能已經停止所有已停用已啟用秒Y-m-d G:i:slanguages/wp-super-cache-it_IT.po000066600000237401152133035240012714 0ustar00# WP Super Cache Translation File # GPL # Donncha O Caoimh, http://ocaoimh.ie/ # msgid "" msgstr "" "Project-Id-Version: WP Super Cache in italiano\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2010-11-22 17:30+0000\n" "PO-Revision-Date: 2010-11-23 20:55+0100\n" "Last-Translator: Gianni Diurno (aka gidibao) \n" "Language-Team: Gianni Diurno | gidibao.net \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Italian\n" "X-Poedit-Country: ITALY\n" "X-Poedit-KeywordsList: __;_e\n" "X-Poedit-Basepath: ..\n" "X-Poedit-SearchPath-0: .\n" #: ossdl-cdn.php:105 msgid "Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull." msgstr "Probabilmente il tuo sito fa uso di molti file statici. I file immagine, Javascript e CSS sono generalmente dei file statici che potrebbero essere facilmente serviti da un altro sito o CDN. Quindi questo plugin sostituirà ogni link presente nelle cartelle wp-content e wp-includes (ad eccezione dei file PHP) del tuo sito con l'URL fornito qui sotto. In quel modo potrai copiare tutti i contenuti statici presso un host dedicato o fare un mirror dei file verso un CDN via origin pull." #: ossdl-cdn.php:106 #, php-format msgid "WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes." msgstr "ATTENZIONE: Prova alcuni url statici ad esempio, %s prima di salvare le modifiche giusto per assicurarti che il tuo servizio CDN funzioni correttamente." #: ossdl-cdn.php:107 msgid "You can define different CDN URLs for each site on a multsite network." msgstr "Puoi definire dei differenti URL CDN per ogni sito di un network multi-sito." #: ossdl-cdn.php:134 msgid "Save Changes" msgstr "Salva le modifiche" #: ossdl-cdn.php:136 msgid "CDN functionality provided by OSSDL CDN Off Linker by Mark Kubacki" msgstr "La funzionalità CDN é fornita da OSSDL CDN Off Linker di Mark Kubacki" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Il tuo commento é in attesa di moderazione." #: plugins/awaitingmoderation.php:32 msgid "Awaiting Moderation" msgstr "In attesa di moderazione" #: plugins/awaitingmoderation.php:34 #: plugins/badbehaviour.php:63 #: plugins/domain-mapping.php:60 #: wp-cache.php:1164 msgid "Enabled" msgstr "Attivato" #: plugins/awaitingmoderation.php:35 #: plugins/badbehaviour.php:64 #: plugins/domain-mapping.php:61 #: wp-cache.php:1164 msgid "Disabled" msgstr "Disattivato" #: plugins/awaitingmoderation.php:36 msgid "Enables or disables plugin to Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment." msgstr "Attiva/disattiva il plugin per rimuove il testo \"Il tuo commento é in attesa di essere moderato.\" quando viene lasciato un commento da moderare." #: plugins/awaitingmoderation.php:40 #: plugins/badbehaviour.php:69 #: plugins/domain-mapping.php:66 #: plugins/searchengine.php:69 #: wp-cache.php:1523 msgid "enabled" msgstr "attivato" #: plugins/awaitingmoderation.php:42 #: plugins/badbehaviour.php:71 #: plugins/domain-mapping.php:68 #: plugins/searchengine.php:67 msgid "disabled" msgstr "disattivato" #: plugins/awaitingmoderation.php:43 #, php-format msgid "Awaiting Moderation is now %s" msgstr "Il plugin Awaiting Moderation é %s" #: plugins/awaitingmoderation.php:45 #: plugins/badbehaviour.php:74 #: plugins/domain-mapping.php:71 msgid "Update" msgstr "Aggiorna" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "Non é stato trovato Bad Behaviour. Effettua una verifica." #: plugins/badbehaviour.php:61 msgid "Bad Behavior" msgstr "Bad Behavior" #: plugins/badbehaviour.php:66 #, php-format msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(utilizzare la sola cache parziale, non attivare la compressione ed installare Bad Behavior sotto \"%s/plugins/bad-behavior/\") " #: plugins/badbehaviour.php:72 #, php-format msgid "Bad Behavior support is now %s" msgstr "Il supporto Bad Behaviour é %s." #: plugins/badbehaviour.php:81 #: wp-cache.php:1254 #: wp-cache.php:1256 msgid "Warning!" msgstr "Attenzione!" #: plugins/domain-mapping.php:58 msgid "Domain Mapping" msgstr "Informazioni autore" #: plugins/domain-mapping.php:63 msgid "Provides support for Domain Mapping plugin to map multiple domains to a blog." msgstr "Provvede il supporto per il plugin Domain Mapping per la mappatura dei domini multipli di un blog." #: plugins/domain-mapping.php:69 #, php-format msgid "Domain Mapping support is now %s" msgstr "Il supporto Domain Mapping é %s" #: plugins/domain-mapping.php:83 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Il plugin Domain Mapping é stato rilevato! Vai alla pagina dei plugin di Supercache ed attiva il plugin di supporto a domain mapping." #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1177 msgid "Disable" msgstr "Disattiva" #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s." msgstr "Il plugin No Adverts for Friends é %s." #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(é necessario anche friendsadverts.php) " #: plugins/searchengine.php:74 #: wp-cache.php:1177 msgid "Enable" msgstr "Attiva" #: wp-cache.php:91 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Crea %s /wp-cache-config.php da wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:146 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Attenzione! Il PHP Safe Mode é attivo!" #: wp-cache.php:147 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Attivando questo plugin potresti andare incontro ad alcuni problemi poiché il SAFE MODE é attivo." #: wp-cache.php:151 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Prima che sia possibile la lettura e la scrittura dei file, il tuo server richiede che venga effettuata una verifica circa il proprietario degli script PHP." #: wp-cache.php:152 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "L'amministratore del sito ha la possibilità di cambiare il proprietario del gruppo che fa capo agli script di questo plugin facendo sì che esso coincida con l'utente web del server. Anche il proprietario del gruppo per la cartella %s/cache/ può essere cambiato. Per ulteriori informazioni, consulta la pagina del manuale safe mode." #: wp-cache.php:154 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "L'amministratore del sito ha la possibilità di disattivare questa funzione. Per ulteriori informazioni, consulta la pagina del manuale safe mode. La disattivazione non potrà avvenire via file .htaccess. L'operazione dovrà essere effettuata nel file di configurazione php.ini." #: wp-cache.php:160 msgid "Permlink Structure Error" msgstr "Errore struttura permalink" #: wp-cache.php:161 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Affinché il plugin possa funzionare correttamente sarà necessario un url personalizzato oppure la struttura del permalink. Vai alla pagina per le opzioni dei Permalink per configurare i tuoi permalink." #: wp-cache.php:173 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Attenzione! Il tuo hostname \"%s\" viene convertito in %s" #: wp-cache.php:174 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Il tuo server ritiene che il tuo hostname venga convertito in %s. Alcuni servizi quali ad esempio la garbage collection fornita da questo plugin e la pubblicazione programmata dei post di WordPress potrebbero non funzionare correttamente." #: wp-cache.php:175 #: wp-cache.php:189 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Leggi il punto numero 16 nella sezione Troubleshooting del file readme.txt" #: wp-cache.php:188 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "WordPress non é in grado di trovare il file wp-cron.php. Questo script é necessario script per un corretto funzionamento della garbage collection fornita da questo plugin, per la pubblicazione programmata dei post di WordPress così come per tutte le altre attività di rilevante importanza." #: wp-cache.php:203 msgid "Cannot continue... fix previous problems and retry." msgstr "Non é possibile proseguire l'operazione. Correggi i problemi precedenti prima di riprovare." #: wp-cache.php:212 msgid "Zlib Output Compression Enabled!" msgstr "Compressione Zlib (output) attivata!" #: wp-cache.php:213 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "Il PHP sta comprimendo i dati inviati ai visitatori del tuo sito. E' preferibile disattivare questa opzione qualora il plugin comprimesse la cache per l'output al posto di comprimere più volte la stessa pagina.. Consultare la n.ro 21 della sezione Troubleshooting. Leggi questa pagina per le istruzioni sul come modificare il tuo php.ini." #: wp-cache.php:217 msgid "Mod rewrite may not be installed!" msgstr "Il Mod rewrite potrebbe non essere stato installato!" #: wp-cache.php:218 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Pare che il mod_rewrite non sia installato. Considera che questa affermazione potrebbe non essere attendibile al 100%, specialmente qualora non venisse utilizzato Apache. Verifica che sia stato caricato il modulo mod_rewrite. Il modulo sarà necessario per potere servire i file statici di Super Cache. Avrai comunque ancora la possibilità di poter utilizzare la modalità parziale o PHP." #: wp-cache.php:223 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Modalita di sola lettura. La configurazione non può essere modificata." #: wp-cache.php:224 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Il file di configurazione di WP Super Cache é %s/wp-cache-config.php e non può essere modificato. Affinché possa essere modicato, il file in questione deve essere scrivibile." #: wp-cache.php:225 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Un modo semplice per compiere l'operazione é quello di modificare temporaneamente i permessi facendo uso del comando CHMOD oppure via il tuo client ftp. Assicurati che sia scrivibile affinché il tutto possa funzionare propriamente." #: wp-cache.php:226 msgid "Writeable:" msgstr "Scrivibile:" #: wp-cache.php:227 msgid "Readonly:" msgstr "Sola lettura:" #: wp-cache.php:239 #, php-format msgid "Warning! %s is writeable!" msgstr "Attenzione! %s é scrivibile!" #: wp-cache.php:240 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "E' necessario modificare i permessi per %s per renderli maggiormente restrittivi. Utilizza per la correzione il tuo client ftp oppure il seguente comando:" #: wp-cache.php:248 msgid "Mobile rewrite rules detected" msgstr "Sono state rilevate le regole Mobile rewrite" #: wp-cache.php:249 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Per una migliore prestazione attivare il \"Supporto mobile device\" oppure cancellare le regole mobile rewrite presenti nel tuo file .htaccess. Cerca le 2 linee contenenti il testo \"2.0\\ MMP|240x320\" e cancellale." #: wp-cache.php:249 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Questa operazione non avrà alcun effetto per gli utenti comuni mentre gli utenti via mobile non visualizzeranno le pagine nella cache." #: wp-cache.php:255 #: wp-cache.php:266 msgid "Rewrite rules must be updated" msgstr "E' necessario aggiornare le regole Mod Rewrite!" #: wp-cache.php:256 #: wp-cache.php:267 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Le regole di scrittura richieste da questo plugin sono state modificate oppure non sono presenti. " #: wp-cache.php:257 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Il supporto mobile necessita della aggiunta di alcune regole extra nel tuo file .htaccess oppure che tu imposti il plugin nella modalità parziale. Qui puoi trovare le opzioni disponibili (in ordine di difficoltà):" #: wp-cache.php:258 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Imposta il plugin nella modalità parziale ed attiva il supporto mobile." #: wp-cache.php:259 #: wp-cache.php:268 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Vai al fondo della pagina delle impostazioni avanzate e clicca il pulsante Aggiorna le regole Mod_Rewrite." #: wp-cache.php:260 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Cancella le regole mod_rewrite del plugin in %s.htaccess presenti tra # BEGIN WPSuperCache e # END WPSuperCache quindi, permetti al plugin di rigenerarle al momento della ricarica di questa pagina." #: wp-cache.php:261 #, php-format msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Aggiungi tu stesso le regole. Modifica il file %s.htaccess e trova il blocco del codice contenuto tra le linee # BEGIN WPSuperCache e # END WPSuperCache. Troverai due sezioni particolarmente simili tra loro. Proprio sotto la linea %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ aggiungi queste linee: (per due volte, una per ogni sezione)" #: wp-cache.php:274 msgid "Required to serve compressed supercache files properly." msgstr "E' necessario fornire correttamente i file compressi supercache." #: wp-cache.php:274 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "E' necessario impostare le informazioni cache per le pagine supercache. In assenza di questo modulo, gli utenti che utilizzano IE7 visualizzeranno le pagine non aggiornate." #: wp-cache.php:274 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Imposta la data di scadenza per le pagine supercached. Senza questo modulo, i visitatori potrebbero non visualizzare le nuove pagine sebbene venga ricaricata la pagina oppure inviare dei commenti." #: wp-cache.php:281 msgid "Missing Apache Modules" msgstr "Moduli Apache mancanti" #: wp-cache.php:282 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Non sono presenti i seguenti moduli Apache. Senza di essi, il plugin funzionerà in modalità parziale. Qualora facessi uso della modalita Supercache attiva, i tuoi visitatori potrebbero visualizzare delle pagine non aggiornate e/o corrotte." #: wp-cache.php:433 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Attenzione! hai provato ad attivare la compressione mentre la zlib.output_compression é attiva. Vai alla n.ro 21 della sezione Troubleshooting presente nel file readme." #: wp-cache.php:524 msgid "WP Super Cache Settings" msgstr "Impostazioni WP Super Cache" #: wp-cache.php:535 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Avviso: Mod_rewrite o cache parziale attivi. Le impostazioni avanzate sono la pagina di avvio predefinita." #: wp-cache.php:546 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "La configurazione del file é stata modificata: alcuni valori potrebbero essere errati. Ricarica nuovamente la pagina dal menu delle \"Impostazioni\" per ripristinare." #: wp-cache.php:566 #: wp-cache.php:640 msgid "Caching must be enabled to use this feature" msgstr "Attiva la cache per utilizzare questa funzione" #: wp-cache.php:568 msgid "Cache Tester" msgstr "Verifica cache" #: wp-cache.php:569 msgid "Test your cached website by clicking the test button below." msgstr "Verifica la cache del tuo sito cliccando sul pulsante qui sotto." #: wp-cache.php:576 #, php-format msgid "Fetching %s to prime cache: " msgstr "Analisi %s cache di base: " #: wp-cache.php:578 #: wp-cache.php:585 #: wp-cache.php:592 msgid "OK" msgstr "OK" #: wp-cache.php:583 #, php-format msgid "Fetching first copy of %s: " msgstr "Analisi prima copia di %s: " #: wp-cache.php:590 #, php-format msgid "Fetching second copy of %s: " msgstr "Analisi seconda copia di %s: " #: wp-cache.php:596 msgid "One or more page requests failed:" msgstr "La richiesta di una o più pagine é fallita:" #: wp-cache.php:615 #: wp-cache.php:616 #, php-format msgid "Page %d: %d (%s)" msgstr "Pagina %d: %d (%s)" #: wp-cache.php:622 #, php-format msgid "Page 1: %s" msgstr "Pagina 1: %s" #: wp-cache.php:623 #, php-format msgid "Page 2: %s" msgstr "Pagina 2: %s" #: wp-cache.php:624 msgid "The timestamps on both pages match!" msgstr "La timestamp (data) delle due pagine coincide!" #: wp-cache.php:626 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Le pagine non coincidono! La timestamp differisce oppure non é presente!" #: wp-cache.php:632 msgid "Send non-secure (non https) request for homepage" msgstr "Invia una richiesta non crittografata (non https) per la homepage" #: wp-cache.php:633 msgid "Test Cache" msgstr "Test cache" #: wp-cache.php:658 #: wp-cache.php:789 msgid "Cancel Cache Preload" msgstr "Annulla pre-carica cache" #: wp-cache.php:666 #: wp-cache.php:677 msgid "Scheduled preloading of cache cancelled." msgstr "Il pre-caricamento programmato della cache é stato annullato." #: wp-cache.php:703 #: wp-cache.php:787 msgid "Preload Cache Now" msgstr "Pre-carica la cache adesso" #: wp-cache.php:707 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Pre-caricamento programmato della cache tra 10 secondi." #: wp-cache.php:712 #, php-format msgid "Scheduled preloading of cache in %d minutes" msgstr "Pre-caricamento programmato della cache tra %d minuti" #: wp-cache.php:716 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Questa operazione effettuerà la cache di ogni articolo e pagina pubblicati nel tuo sito. Verranno quindi creati dei file statici supercache in modo tale che i visitatori sconosciuti (bot compresi) visualizzeranno la pagina nella cache. Tutto questo potrebbe esserti utile per quanto concerne il ranking di Google nel caso in cui essi utilizzasero la velocità come metro di valutazione per il giudizio dei siti web." #: wp-cache.php:717 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Il pre-caricamento crea comunque un gran numero di file. La cache verrà effettuata a partire dell'articolo più recente sino a giungere a quello più datato quindi, prendi in considerazione il fatto di effettuare la cache del più recente qualora avessi molti articoli (+ 10.000). Tutto ciò é particolarmente importante per gli hosting condivisi." #: wp-cache.php:718 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "Nella ’Modalità precarica’ la garbage collection verrà svuotata per i soli utenti conosciuti, non per i file supercache precaricati. Preferisci questa configurazione se la cache fosse pre-caricata." #: wp-cache.php:722 #, php-format msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Ricarica i file della cache pre-caricata ogni %s minuti. (0 per disattivare, minimo %d minuti.)" #: wp-cache.php:735 msgid "all" msgstr "tutto" #: wp-cache.php:748 #, php-format msgid "Preload %s posts." msgstr "Pre-carica %s articoli." #: wp-cache.php:755 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Modalità pre-carica (garbage collection solo per file cache parziale. Raccomandato.)" #: wp-cache.php:758 msgid "Send me status emails when files are refreshed." msgstr "Inviami una email di notifica alla ricarica dei file." #: wp-cache.php:763 msgid "Many emails, 2 emails per 100 posts." msgstr "Numerose email, 2 email ogni 100 articoli." #: wp-cache.php:766 msgid "Medium, 1 email per 100 posts." msgstr "Medio, 1 email ogni 100 articoli." #: wp-cache.php:769 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Poche email, 1 all'avvio ed 1 al termine della operazione di precarica per tutti gli articoli." #: wp-cache.php:773 #, php-format msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Ricarica della cache tra %d ore %d minuti e %d secondi." #: wp-cache.php:774 #, php-format msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Ricarica completa della cache tra %d ore %d minuti e %d secondi." #: wp-cache.php:780 #, php-format msgid "Currently caching from post %d to %d." msgstr "Cache in corso dal post %d a %d." #: wp-cache.php:784 #, php-format msgid "Page last cached: %s" msgstr "Ultima cache pagina: %s" #: wp-cache.php:787 msgid "Update Settings" msgstr "Aggiorna le impostazioni" #: wp-cache.php:795 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "La pre-carica della cache non é attiva. Disattiva la cache parziale oppure conferisci con l'amministratore del tuo host." #: wp-cache.php:810 #: wp-cache.php:904 msgid "Caching" msgstr "Cache" #: wp-cache.php:814 msgid "Cache hits to this website for quick access." msgstr "Cache hit di questo sito per accesso rapido." #: wp-cache.php:814 #: wp-cache.php:815 #: wp-cache.php:832 #: wp-cache.php:837 #: wp-cache.php:840 #: wp-cache.php:841 #: wp-cache.php:907 msgid "Recommended" msgstr "Raccomandato" #: wp-cache.php:815 msgid "Use mod_rewrite to serve cache files." msgstr "Utilizza mod_rewrite per servire i file in cache." #: wp-cache.php:816 msgid "Use PHP to serve cache files." msgstr "Utilizza PHP per servire i file in cache." #: wp-cache.php:817 msgid "Legacy page caching." msgstr "Pagina cache parziale." #: wp-cache.php:818 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching." msgstr "Il Mod_rewrite é il più veloce, il PHP é piuttosto veloce e semplice da fare funzionare mentre, nonstante la cache parziale sia la più lenta, essa é da ritenersi la più flessibile e semplice da fare funzionare. I nuovi utenti dovrebbero utilizzare la cache PHP." #: wp-cache.php:824 msgid "Miscellaneous" msgstr "Varie" #: wp-cache.php:830 msgid "Warning! Compression is disabled as gzencode() function not found." msgstr "Attenzione! La compressione non é attiva - non trovata la funzione gzencode()." #: wp-cache.php:832 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Compressione delle pagine in modo che esse siano servite più rapidamente ai visitatori." #: wp-cache.php:833 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "La compressione é disattivata come predefinita poiché alcuni host riscontrano dei problemi con i file compressi. La commutazione attivo/non attivo svuoterà la cache." #: wp-cache.php:837 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Not Modified browser caching. Indica quando una pagina non é stata modificata dalla sua ultima richiesta." #: wp-cache.php:838 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "Il supporto 304 non é attivo (predefinita) poiché GoDaddy ha riscontrato dei problemi con alcuni header utilizzati." #: wp-cache.php:840 msgid "Don’t cache pages for known users." msgstr "Non servire pagine cache per gli utenti conosciuti." #: wp-cache.php:841 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Rigenerazione cache. Serve un file supercache agli utenti anonimi quando un nuovo file é stato generato." #: wp-cache.php:842 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Fai sapere a tutti che il tuo sito é a prova di Digg! (inserisce un messaggio nel footer del tuo blog)" #: wp-cache.php:848 #: wp-cache.php:1016 #: wp-cache.php:1536 msgid "Advanced" msgstr "Avanzato" #: wp-cache.php:852 msgid "Mobile device support." msgstr "Supporto " #: wp-cache.php:853 msgid "Clear all cache files when a post or page is published." msgstr "Svuota tutti i file di cache quando viene pubblicato un articolo o una pagina." #: wp-cache.php:854 msgid "Only refresh current page when comments made." msgstr "Ricarica la sola pagina in uso quando vengono effettuati dei commenti." #: wp-cache.php:855 msgid "List the newest cached pages on this page." msgstr "Elenca su questa pagina la lista delle nuove pagine cache." #: wp-cache.php:857 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Blocco grezzo del file. Sebbene questa funzione non sia particolarmente necessaria potrebbe tornarti utile qualora il tuo server non avesse una potenza sufficiente. Attenzione! In alcuni casi molto rari potrebbe bloccare il tuo server!" #: wp-cache.php:859 msgid "Late init. Display cached files after WordPress has loaded. Most useful in legacy mode." msgstr "Late init. Mostra i file in cache dopo che WordPress é stato caricato. Utile nella modalità legacy." #: wp-cache.php:861 msgid "Use object cache to store cached files." msgstr "Utilizza l'oggetto cache per conservare i file in cache." #: wp-cache.php:861 msgid "(Experimental)" msgstr "(Sperimentale)" #: wp-cache.php:868 msgid "Note:" msgstr "Nota:" #: wp-cache.php:870 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Qualora desiderassi disinstallare questo plugin, assicurati che la cartella %s sia scrivibile in modo tale che i file advanced-cache.php e cache-config.php possano venire cancellati automaticamente. (l'accertarsi che anche questi due file siano scrivibile é probabilmente una buona idea!)" #: wp-cache.php:871 #, php-format msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Leggi il readme.txt per le istruzioni su come disinstallare questo script. Vedi anche, \"Come disinstallare WP Super Cache\"." #: wp-cache.php:872 #, php-format msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Serve aiuto? Leggi il file Super Cache readme. In esso sono contenute le info sulla installazione, le FAQ e numerosi suggerimenti. Puoi anche utilizzare il forum di supporto: qui potresti trovare una risposta alle tue domande." #: wp-cache.php:875 #: wp-cache.php:922 msgid "Update Status" msgstr "Aggiorna lo stato" #: wp-cache.php:882 msgid "Accepted Filenames & Rejected URIs" msgstr "Nomi file consentiti e URL respinti" #: wp-cache.php:907 msgid "Caching On" msgstr "Cache attiva" #: wp-cache.php:908 msgid "Caching Off" msgstr "Cache non attiva" #: wp-cache.php:909 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Nota: attiva cache PHP, rigenerazione cache e supporto mobile" #: wp-cache.php:919 msgid "Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Avviso: la cache PHP é attiva ma sono state rilevate delle regole Supercache mod_rewrite. I file della cache saranno serviti utilizzando queste regole. Ignora questo messaggio qualora il tuo sito funzionasse correttamente oppure modifica il file .htaccess file allocato nella root della tua installazione e rimuovi le regole di SuperCache." #: wp-cache.php:924 msgid "Recommended Links and Plugins" msgstr "Link e plugin consigliati" #: wp-cache.php:925 msgid "Caching is only one part of making a website faster. Here are some other plugins that will help:" msgstr "La cache é solamente uno tra i modi per potere rendere un sito più veloce. Ecco alcuni plugin plugin utili:" #: wp-cache.php:926 #, php-format msgid "WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together." msgstr "WP Minify riduce il numero dei file serviti dal tuo web server unendo insieme i file Javascript e CSS. Come alternativa, potresti utilizzare WPSCMin, un plugin Supercache che rimpicciolisce le pagine cache (non unisce insieme i file JS/CSS)." #: wp-cache.php:927 #, php-format msgid "Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix." msgstr "Yahoo! Yslow é una estensione per Firebug (add-on per Firefox). Analizza le pagine web e suggerisce come migliorare le loro prestazioni basandosi su di una serie di regole per il miglioramento delle pagine web. Potresti anche provare il tool online a nome GTMetrix." #: wp-cache.php:928 #, php-format msgid "Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score." msgstr "L'utilizzo delle Google Libraries ti permette di caricare le librerie Javascript di comune uso direttamente dai server di Google. Potrebbe ironicamente ridurre il tuo punteggio Yslow." #: wp-cache.php:929 #, php-format msgid "Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules." msgstr "Solo per utenti esperti: Speed up your site with Caching and cache-control spiega come rendere il tuo sito più cacheable grazie alle regole .htaccess." #: wp-cache.php:930 #, php-format msgid "Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others." msgstr "Solo per utenti esperti: Installa un object cache. Scegli tra Memcached, XCache, eAcccelerator ed altri." #: wp-cache.php:941 msgid "Make WordPress Faster" msgstr "Rendi più veloce WordPress" #: wp-cache.php:942 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "Il plugin %1$s viene aggiornato e sviluppato da %2$s grazie anche al contributo di molte altre persone." #: wp-cache.php:943 #, php-format msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Il suo blog é %1$s e le sue foto le trovi %2$s." #: wp-cache.php:944 #, php-format msgid "Please say hi to him on %s too!" msgstr "Mandagli un saluto su %s!" #: wp-cache.php:945 msgid "Need Help?" msgstr "Serve un aiuto?" #: wp-cache.php:947 #, php-format msgid "Installation Help" msgstr "Info installazione" #: wp-cache.php:948 #, php-format msgid "Frequently Asked Questions" msgstr "FAQ" #: wp-cache.php:949 #, php-format msgid "Support Forum" msgstr "Forum di supporto" #: wp-cache.php:951 msgid "Rate This Plugin!" msgstr "Vota questo plugin!" #: wp-cache.php:952 #, php-format msgid "Please rate this plugin and tell me if it works for you or not. It really helps development." msgstr "Vota questo plugin e dimmi se funziona oppure no. Il tuo feedback mi aiuterà nello sviluppo di questo progetto." #: wp-cache.php:961 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Pagine in cache da %1$s : %2$s" #: wp-cache.php:962 msgid "Newest Cached Pages:" msgstr "Pagine recenti nella cache:" #: wp-cache.php:966 #, php-format msgid "Cached %s seconds ago" msgstr "Cache effettuata %s secondi fa" #: wp-cache.php:969 msgid "(may not always be accurate on busy sites)" msgstr "(il dato potrebbe essere non sempre accurato per quei siti ad alto traffico)" #: wp-cache.php:988 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "I plugin di cache sono degli scripts PHP che risiedono in una cartella a nome plugins allocata nella cartella wp-super-cache. Questi plugin saranno caricati al momento del caricamento di Supercache in un modo più rapido dei regolari plugin di WordPress." #: wp-cache.php:989 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Questa é una funzione strettamente avanzata e necessita di una valida conoscenza sul come operare in ambito di PHP e WordPress." #: wp-cache.php:999 msgid "Available Plugins" msgstr "Plugin disponibili" #: wp-cache.php:1016 msgid "Easy" msgstr "Facile" #: wp-cache.php:1016 msgid "CDN" msgstr "CDN" #: wp-cache.php:1016 msgid "Tester & Contents" msgstr "Verifiche e contenuti" #: wp-cache.php:1016 msgid "Preload" msgstr "Pre-carica" #: wp-cache.php:1016 msgid "Plugins" msgstr "Plugins" #: wp-cache.php:1016 msgid "Debug" msgstr "Debug" #: wp-cache.php:1047 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Avviso: la regola mod_rewrite per WP Super Cache non sarà attiva eccetto che per il sito principale di questo network." #: wp-cache.php:1049 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Avviso: la regola mod_rewrite per WP Super Cache non sarà attiva eccetto che sul sito principale di questo network." #: wp-cache.php:1059 msgid "Mod Rewrite Rules" msgstr "Regole Mod Rewrite" #: wp-cache.php:1065 msgid "WordPress MU Detected" msgstr "E' stata rilevata una installazione WordPress MU" #: wp-cache.php:1065 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Sfortunatamente, le rewrite rule non possono essere aggiornate in automatico quando WordPress MU é in funzione. Apri il tuo file .htaccess ed aggiungi le seguenti regole mod_rewrite in cima ad ogni altra regola presente nel file." #: wp-cache.php:1067 msgid "Mod Rewrite rules cannot be updated!" msgstr "Le regole Mod Rewrite non possono essere aggiornate!" #: wp-cache.php:1068 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Affinché l'aggiornamento automatico possa funzionare, sono necessari i marcatori BEGIN ed END nel file %s.htaccess. Sono simili a questa ed avvolgono le principali regole mod_rewrite di WordPress:" #: wp-cache.php:1070 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Ricarica questa pagina una volta aggiornato il file .htaccess." #: wp-cache.php:1074 msgid "Thank you for upgrading." msgstr "Grazie per avere effettuato l'aggiornamento." #: wp-cache.php:1074 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Le regole mod_rewrite sono cambiate dalla tua ultima installazione di questo plugin. E' necessario che tu rimuova le regole supercache precedenti prima che le nuove siano aggiornate. Ricarica questa pagina una volta che avrai modificato il tuo file .htaccess. Qualora desiderassi effettuare un aggiornamento manuale, modifica la seguente linea: %1$s rendendola simile a questa: %2$s Le sole modifiche sono \"HTTP_COOKIE\" che diventa \"HTTP:Cookie\" e \"wordpressuser\" che va sostituito con \"wordpress\". Questa é una modifica relativa a WordPress 2.5 comunque, la sua validità é estesa anche alle versioni precedenti (qualora avessi il coraggio di utilizzarle)." #: wp-cache.php:1078 msgid "Trailing slash check required." msgstr "E' necessaria una verifica sullo slash di chiusura." #: wp-cache.php:1078 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Pare che il tuo URL termini con uno \"/\". Dal momento in cui hai installato questo plugin, é stato rilevato un bug che duplica il contenuto laddove l'URL non termina con uno \"/\"; di fatto, vengono proposti gli stessi contenuti di quelli con lo \"/\" e non viene altresì effettuato un reindirizzamento all'URL appropriato. Per la correzione, sarà necessario modificare il tuo file .htaccess aggiungendo queste due regole ai due gruppi di regole di Super Cache:" #: wp-cache.php:1080 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Puoi vedere dove posizionare ed esaminare nella loro completezza le regole cliccando il link qui sotto a nome \"Visualizza le regole Mod_Rewrite\"." #: wp-cache.php:1094 msgid "Mod Rewrite rules updated!" msgstr "Le regole Mod Rewrite sono state aggiornate!" #: wp-cache.php:1095 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "Il file %s.htaccess é stato aggiornato con l'inserimento delle regole mod_rewrite necessarie. Verifica la loro correttezza. Ecco come dovrebbero essere:" #: wp-cache.php:1097 msgid "Mod Rewrite rules must be updated!" msgstr "E' necessario aggiornare le regole Mod Rewrite!" #: wp-cache.php:1098 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Il tuo file %s.htaccess non é scrivibile e deve essere aggiornato con le regole mod_rewrite necessarie. Le nuove regole andranno inserite al di sopra di quelle regolari di WordPress così come nel codice qui sotto:" #: wp-cache.php:1103 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Sono state rilevate le regole mod rewrite di WP Super Cache nel tuo file %s.htaccess.
    Clicca il seguente link per vedere le linee aggiunte a quel file. Nel caso in cui avessi aggiornato il plugin assicurati che esse coincidano." #: wp-cache.php:1106 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "E' stata rilevata una differenza tra le regole del tuo file .htaccess e quelle rewrite del plugin. Questo potrebbe dipendere anche da una sola spaziatura nel testo: effettua quanto prima una comparazione tra le regole presenti nel file con quelle qui sotto. Premi il pulsante ’Update Mod_Rewrite Rules’ per aggiornare." #: wp-cache.php:1109 msgid "View Mod_Rewrite Rules" msgstr "Visualizza le regole Mod_Rewrite" #: wp-cache.php:1113 #: wp-cache.php:2350 #, php-format msgid "Rules must be added to %s too:" msgstr "Le regole devono essere aggiunte anche a %s:" #: wp-cache.php:1121 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Sono state create nel file %s.htaccess le regole per la codifica Gzip." #: wp-cache.php:1128 msgid "Fix Configuration" msgstr "Correggi la configurazione" #: wp-cache.php:1131 msgid "Restore Default Configuration" msgstr "Ripristina la configurazione predefinita" #: wp-cache.php:1139 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Moderazione dei commenti attiva. Il tuo commento non apparirà immediatamente." #: wp-cache.php:1164 msgid "Lock Down:" msgstr "Blocco di protezione:" #: wp-cache.php:1165 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Proteggi il tuo server da un inatteso picco di traffico attivando il blocco. Quando il blocco é attivo, i nuovi commenti non ricaricheranno i file statici nella cache." #: wp-cache.php:1166 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Sviluppatori: é possibile rendere compatibile il plugin con il blocco di protezione grazie alla costante \"WPLOCKDOWN\". Il seguente codice farà sì che il plugin sia in grado di sopperire alle impostazioni WPLOCKDOWN." #: wp-cache.php:1168 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Il mio blog ha attivato un blocco di protezione. Gli aggiornamenti appariranno a breve" #: wp-cache.php:1172 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress ha un blocco di protezione. Quando verranno effettuati dei nuovi commenti, i file statici di Super Cache non saranno cancellati." #: wp-cache.php:1174 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress ha un blocco di protezione. I nuovi commenti rigenereranno come al solito i file statici di Super Cache." #: wp-cache.php:1180 msgid "Lock Down" msgstr "Blocco di protezione" #: wp-cache.php:1188 msgid "Directly Cached Files" msgstr "File cache diretta" #: wp-cache.php:1246 #, php-format msgid "%s removed!" msgstr "%s rimosso!" #: wp-cache.php:1254 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "E' necessario rendere scrivibile %s affinché questa opzione possa essere attivata. Per ragioni di sicurezza, rendi di sola lettura una volta che la pagina é stata generata." #: wp-cache.php:1256 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s é scrivibile. Assicurati che essa sia di sola lettura una volta che la pagina verrà generata (limita i problemi di sicurezza)." #: wp-cache.php:1270 msgid "Existing direct page" msgstr "Pagina diretta esistente" #: wp-cache.php:1270 msgid "Delete cached file" msgstr "Cancella i file nella cache" #: wp-cache.php:1275 msgid "Add direct page:" msgstr "Aggiungi una pagina diretta:" #: wp-cache.php:1277 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "I file di cache diretta sono dei file creati direttamente sotto %s ossia laddove il tuo blog risiede. Questa opzione é particolarmente utile qualora ti aspettassi un alto livello di traffico proveniente da Digg o Slashdot verso un articolo/pagina." #: wp-cache.php:1279 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Esempio: per la cache di %1$sabout/, sarà necessario che tu inserisca %1$sabout/ oppure /about/. Il file di cache verrà generato la prima volta che un utente anonimo visiterà quella pagina." #: wp-cache.php:1280 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Svuota la casella di testo per rimuovere l'indirizzo dalla lista delle pagine dirette e cancellare dalla cache il file." #: wp-cache.php:1285 msgid "Update Direct Pages" msgstr "Aggiorna le pagine dirette" #: wp-cache.php:1323 msgid "Expiry Time & Garbage Collection" msgstr "Periodo scadenza e Garbage Collection" #: wp-cache.php:1325 msgid "Expire time:" msgstr "Periodo scadenza:" #: wp-cache.php:1326 msgid "seconds" msgstr "secondi" #: wp-cache.php:1327 msgid "Garbage Collection" msgstr "Garbage Collection" #: wp-cache.php:1327 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Qualora il periodo di scadenza fosse maggiore di 1800 secondi (mezz'ora), la garbage collection verrà effettuata ogni 10 minuti diversamente, l'operazione verrà effettuata 10 secondi dopo il periodo di scadenza indicato qui sopra." #: wp-cache.php:1328 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "La ricerca e la cancellazione dei file scaduti é particolarmente dispendiosa così come lo é il lasciarli lì scaduti. Qualora avessi un sito con un traffico rilevante, imposta il tempo di scadenza a 300 secondi. Effettua eventualmente più prove con valori differenti e controlla in questa pagina (più volte durante l'arco della giornata) il totale dei file scaduti presenti. Il numero ottimale dovrebbe essere inferiore a circa 500 file di cache (lmodalità parziale). Il numero dei file nella cachepotrà essere comunque superiore utilizzando mod_rewrite o PHP caching." #: wp-cache.php:1329 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Imposta a 0 il tempo di scadenza per disattivare la garbage collection." #: wp-cache.php:1330 msgid "Change Expiration" msgstr "Modifica la scadenza" #: wp-cache.php:1374 msgid "Rejected User Agents" msgstr "User Agents " #: wp-cache.php:1375 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Le stringhe presenti nella header HTTP degli ’User Agent’ che impediscono a WP-Cache di fornire i dati nella cache alle richieste da parte dei bot, degli spider e dei crawler. Nota che anche i file super cached saranno inviati a questi agent qualora esistessero." #: wp-cache.php:1382 msgid "Save UA Strings" msgstr "Salva le stringhe UA" #: wp-cache.php:1405 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Non effettuare la cache per i tipi di pagine a seguire. Per maggiori informazioni, leggi la documentazione circa i tag condizionali." #: wp-cache.php:1408 msgid "Single Posts" msgstr "Articoli singoli" #: wp-cache.php:1409 msgid "Pages" msgstr "Pagine" #: wp-cache.php:1410 msgid "Front Page" msgstr "Pagina principale" #: wp-cache.php:1411 msgid "Home" msgstr "Home" #: wp-cache.php:1412 msgid "Archives" msgstr "Archivi" #: wp-cache.php:1413 msgid "Tags" msgstr "Tag" #: wp-cache.php:1414 msgid "Category" msgstr "Categoria" #: wp-cache.php:1415 msgid "Feeds" msgstr "Feed" #: wp-cache.php:1416 msgid "Search Pages" msgstr "Pagine ricerca" #: wp-cache.php:1418 #: wp-cache.php:1546 msgid "Save" msgstr "Salva" #: wp-cache.php:1435 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Aggiungi qui le stringhe (non il nome del file) per forzare il blocco della cache per quella data pagina. Ad esempio, se il tuo URL contenesse l'anno e tu non gradissi la cache per gli articoli pubblicati in quel dato periodo, sarà sufficiente specificare l'anno, ad es. ’/2004/’. WP-Cache effettuerà una ricerca in modo tale da verificare la presenza di quella stringa nell'URI quindi, la cache per quella pagina non verrà generata." #: wp-cache.php:1441 msgid "Save Strings" msgstr "Salva le stringhe" #: wp-cache.php:1457 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Aggiungi qui i nomi dei file per i quali potrà essere effettuata la cache (anche in caso di corrispondenza con una delle stringhe specificate più sopra)." #: wp-cache.php:1463 msgid "Save Files" msgstr "Salva i file" #: wp-cache.php:1508 msgid "Currently logging to: " msgstr "Log attuale:" #: wp-cache.php:1518 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Correggi qui i problemi con il debugging del plugin. Potrai sceglie tra l'invio delle tue email di debug oppure consultare il registro contenuto in un file allocato nella cartella della cache." #: wp-cache.php:1519 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Consultare il file di registro é semplice ma ricordati che, una volta svuotata la cache, verrà cancellato anche il file di registro." #: wp-cache.php:1523 msgid "Debugging" msgstr "Debugging" #: wp-cache.php:1524 msgid "Logging Type" msgstr "Tipo di logging" #: wp-cache.php:1524 msgid "Email" msgstr "Email" #: wp-cache.php:1525 msgid "file" msgstr "file" #: wp-cache.php:1526 msgid "IP Address" msgstr "Indirizzo IP" #: wp-cache.php:1526 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(richieste per il registro provenienti da questo solo indirizzo IP. Il tuo IP é %s)" #: wp-cache.php:1527 msgid "Log level" msgstr "Livello log" #: wp-cache.php:1533 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = minore, 5 = maggiore, può essere causa di un maggior carico sul server.)" #: wp-cache.php:1536 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "In alcuni casi molto rari, é possibile che si verifichino in alcuni blog due problematiche:
    1. La front page potrebbe giungere come download di un file zip.
    2. La pagina errata può essere in certi casi custodita nella cache quale front page qualora il tuo blog facesse uso di una front page statica e la struttura del permalink fosse /%category%/%postname%/.
    " #: wp-cache.php:1537 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "Sono certo al 99% che non si tratta di bug in WP Super Cache e questo problema può accadere in casi veramente molto rari. Puoi attivare comunque un controllo ogni 5 minuti in modo tale che sia possibile monitorare il tuo sito. In caso di problemi, ti verrà inviata una email." #: wp-cache.php:1539 msgid "Check front page every 5 minutes." msgstr "Controlla la front page ogni 5 minuti." #: wp-cache.php:1540 msgid "Front page text" msgstr "Testo front page" #: wp-cache.php:1540 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "il testo da cercare nella tua front page. La cache verrà svuotata in assenza del testo. Lascia vuoto per disattivare" #: wp-cache.php:1541 msgid "Clear cache on error." msgstr "Svuota la cache in caso di errore." #: wp-cache.php:1542 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Invia una email di notifica all'aministratore del blog per l'avvenuto controllo. (utile per il testing) " #: wp-cache.php:1556 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Errore: la compressione GZIP é attiva: disattivala qualora desiderassi attivare wp-cache." #: wp-cache.php:1603 #: wp-cache.php:1765 msgid "Warning" msgstr "Attenzione" #: wp-cache.php:1603 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "La tua installazione di WordPress ha la compressione GZIP attiva: wp-cache non sarà disponibile sino a quando la compressione gzip non verrà disattivata." #: wp-cache.php:1661 #: wp-cache.php:1666 #: wp-cache.php:1698 #: wp-cache.php:1703 #: wp-cache.php:1709 msgid "Error" msgstr "Errore" #: wp-cache.php:1661 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "La tua cartella per la cache ($cache_path) non esiste e non può essere creata nel server. Verifica i permessi %s." #: wp-cache.php:1666 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "La tua cartella per la cache (%1$s) oppure %2$s é necessario renderla scrivibile affinché il plugin possa funzionare. Verifica con attenzione." #: wp-cache.php:1698 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Il tuo file di configurazione WP-Cache (%s) non é aggiornato e non é scrivibile. Cancellalo e ricarica questa pagina." #: wp-cache.php:1703 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Non é presente il file di configurazione e la cartella %1$s (%2$s) non é scrivibile. Verifica i suoi permessi." #: wp-cache.php:1709 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Il file campione per la configurazione di WP-Cache (%s) non esiste. Effettua una verifica." #: wp-cache.php:1765 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "Il file %s/advanced-cache.php non esiste oppure non può essere aggiornato." #: wp-cache.php:1766 msgid "1. If it already exists please delete the file first." msgstr "1. Nel caso fosse già esistente, cancellalo." #: wp-cache.php:1767 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Rendi il file %1$s scrivibile utilizzando il comando chmod via ftp oppure grazie al software del server. (chmod 777 %1$s) e ricarica questa pagina. Questa é una misura temporanea: ad operazione compiuta, rendi il file di sola lettura. (modificando da 777 a 755 il comando precedente)" #: wp-cache.php:1768 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Ricarica questa pagina per aggiornare il file %s/advanced-cache.php" #: wp-cache.php:1769 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Nel caso in cui non funzionasse, accertati che il file %s/advanced-cache.php non esista:" #: wp-cache.php:1770 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Apri %1$s$wp_cache_file con un editor di testo.
  • 2. Modifica il testo da CACHEHOME a %2$s
  • 3. Salva il file e copialo in %3$s quindi, ricarica questa pagina.
    • " #: wp-cache.php:1793 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    Costante WP_CACHE impostata a false

    La costante WP_CACHE viene utilizzata da WordPress per caricare il codice necessario per servire le pagine in cache. Sfortunatamente, l'impostazione é a false. Modifica il tuo wp-config.php ed aggiungi o modifica la seguente linea al di sopra del comando require_once:

    define('WP_CACHE', true);

    " #: wp-cache.php:1795 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Errore: WP_CACHE non é attivo nel tuo file wp-config.php ed il plugin non é in grado di modificarlo." #: wp-cache.php:1796 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Modifica %s aggiungendo la seguente linea:
    define('WP_CACHE', true);
    Diversamente, WP-Cache non verrà eseguito dal core di Wordpress." #: wp-cache.php:1800 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    La costante WP_CACHE é stata aggiunta al file wp-config.php

    Nel caso in cui continuassi a visualizzare questo messaggio consulta il punto 5 delle FAQ. La riga WP_CACHE deve essere spostata." #: wp-cache.php:1822 msgid "Cache Contents" msgstr "Contenuti cache" #: wp-cache.php:1825 msgid "Object cache in use. No cache listing available." msgstr "Oggetto cache in uso. Nessun elenco cache disponibile." #: wp-cache.php:1849 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Sto cancellando il file supercache: %s
    " #: wp-cache.php:1866 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Sto cancellando il file wp-cache: %s
    " #: wp-cache.php:1931 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Le statistiche della cache non sono generate in automatico. E' necessario che tu prema il link qui sotto per potere rigenerare in questa pagina le statistiche." #: wp-cache.php:1932 msgid "Regenerate cache stats" msgstr "Rigenera statistiche della cache" #: wp-cache.php:1934 #, php-format msgid "Cache stats last generated: %s minutes ago." msgstr "Ultima statistica cache generata: %s minuti fa." #: wp-cache.php:1940 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:1941 #: wp-cache.php:1957 #, php-format msgid "%s Cached Pages" msgstr "%s pagine nella cache" #: wp-cache.php:1942 #: wp-cache.php:1962 #, php-format msgid "%s Expired Pages" msgstr "%s pagine scadute" #: wp-cache.php:1956 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1967 msgid "Fresh WP-Cached Files" msgstr "Aggiorna file WP-Cached" #: wp-cache.php:1968 #: wp-cache.php:1984 #: wp-cache.php:2000 #: wp-cache.php:2016 msgid "URI" msgstr "URI" #: wp-cache.php:1968 #: wp-cache.php:1984 msgid "Key" msgstr "Chiave" #: wp-cache.php:1968 #: wp-cache.php:1984 #: wp-cache.php:2000 #: wp-cache.php:2016 msgid "Age" msgstr "Età" #: wp-cache.php:1968 #: wp-cache.php:1984 #: wp-cache.php:2000 #: wp-cache.php:2016 msgid "Delete" msgstr "Cancella" #: wp-cache.php:1983 msgid "Stale WP-Cached Files" msgstr "Ordina i file WP-Cached" #: wp-cache.php:1999 msgid "Fresh Super Cached Files" msgstr "Aggiorna file Super Cached" #: wp-cache.php:2015 msgid "Stale Super Cached Files" msgstr "Scadenza file Super Cached" #: wp-cache.php:2031 msgid "Hide file list" msgstr "Nascondi la lista dei file" #: wp-cache.php:2033 msgid "Too many cached files, no listing possible." msgstr "Sono presenti troppi file cache: non é possibile mostrare l'elenco." #: wp-cache.php:2035 msgid "List all cached files" msgstr "Lista di tutti i file presenti nella cache" #: wp-cache.php:2041 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Garbage Collection
    L'ultima GC é stata effettuata %s minuti fa
    " #: wp-cache.php:2042 #, php-format msgid "Next GC in %s minutes" msgstr "La prossima GC verrà effettuata tra %s minuti" #: wp-cache.php:2045 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "I file scaduti sono file più vecchi di %s secondi. Sebbene questi file vengano comunque utilizzati dal plugin sappi che sono cancellati periodicamente." #: wp-cache.php:2056 msgid "Delete Expired" msgstr "Cancella la cache scaduta" #: wp-cache.php:2062 #: wp-cache.php:2074 #: wp-cache.php:2237 msgid "Delete Cache" msgstr "Cancella la cache" #: wp-cache.php:2074 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Cancella i file cache di Super Cache (apre in una nuova finestra)" #: wp-cache.php:2213 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s é a prova di Digg grazie alla cache fornita da %2$s" #: wp-cache.php:2246 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "E' necessario configurare WP Super Cache. Vai alla pagina di amministrazione per attivare e configurare il plugin." #: wp-cache.php:2252 msgid "Settings" msgstr "Impostazioni" #: wp-cache.php:2262 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache non é attivo. Vai alla pagina di amministrazione del plugin per attivare la funzione di caching." #: wp-cache.php:2281 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] La front page é stata gzipped! Svuota la cache!" #: wp-cache.php:2281 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Visita %s per svuotare la cache!" #: wp-cache.php:2284 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] La front page é stata gzipped! La cache é stata svuotata!" #: wp-cache.php:2284 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "La cache del blog é stata svuotata perché la front page del tuo sito é sotto downloading. Visita %1$s per controllare se la cache sia stata svuotata." #: wp-cache.php:2291 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] La front page non é corretta! Svuota la cache!" #: wp-cache.php:2291 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Visita %1$s per svuotare la cache nel caso in cui la front page del tuo sito non fosse corretta e mancasse del testo, \"%2$s\"!" #: wp-cache.php:2294 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] La front page non é corretta! La cache é stata svuotata!" #: wp-cache.php:2294 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "La cache del blog é stata svuotata perché manca il testo \"%2$s\" nella front page del tuo sito. Visita %1$s per controllare se la cache sia stata svuotata." #: wp-cache.php:2299 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Controllo Front page!" #: wp-cache.php:2299 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache ha controllato la front page del tuo blog. Visita %s qualora gradissi disattivare la funzione." #: wp-cache.php:2342 msgid "Cannot update .htaccess" msgstr "Non é possibile aggiornare il file .htaccess" #: wp-cache.php:2342 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Il file %s.htaccess non può essere modificato. Correggi utilizzando il comando chmod oppure il tuo client ftp." #: wp-cache.php:2342 msgid "Refresh this page when the file permissions have been modified." msgstr "Ricarica questa pagina una volta che i permessi per il file sono stati modificati." #: wp-cache.php:2342 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Come alternativa, puoi modificare manualmente il file %s.htaccess aggiungendo il seguente codice (prima di ogni regola WordPress):" #: wp-cache.php:2346 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Affinché il tuo server possa fornire dei file html statici é necessario che le regole mod_rewrite vengano aggiunte al file %s.htaccess" #: wp-cache.php:2347 msgid "You can edit the file yourself add the following rules." msgstr "Puoi modificare tu stesso il file aggiungendo le seguenti regole." #: wp-cache.php:2348 msgid " Make sure they appear before any existing WordPress rules. " msgstr " Accertati che appaiano prima di ogni regola WordPress già presente. " #: wp-cache.php:2356 msgid "Update Mod_Rewrite Rules" msgstr "Aggiorna le regole Mod_Rewrite" #: wp-cache.php:2463 #, php-format msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] La pre-carica della cache ha avuto inizio" #: wp-cache.php:2465 #, php-format msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Ricarica articoli da %2$d a %3$d" #: wp-cache.php:2483 #, php-format msgid "[%1$s] Cache Preload Stopped" msgstr "[%1$s] Pre-carica cache arrestata" #: wp-cache.php:2492 #, php-format msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d articoli sono stati ricaricati" #: wp-cache.php:2492 msgid "Refreshed the following posts:" msgstr "I seguenti post sono stati aggiornati:" #: wp-cache.php:2501 #, php-format msgid "Scheduling next preload refresh in %d minutes." msgstr "Prossima ricarica programmata tra %d minuti." #: wp-cache.php:2511 #, php-format msgid "[%s] Cache Preload Completed" msgstr "[%s] La pre-carica della cache é stata completata" #: wp-cache.php:2511 msgid "Cleaning up old supercache files." msgstr "Cancella i vecchi file supercache." #: wp-cache.php:2553 #, php-format msgid "[%s] Preload may have stalled." msgstr "[%s] La pre-carica potrebbe avere dei problemi." #: wp-cache.php:2553 #, php-format msgid "" "Preload has been restarted.\n" "%s" msgstr "" "La pre-carica é stata riavviata.\n" "%s" #~ msgid "" #~ "Scheduled preloading of cache cancelled. If a job is currently running it " #~ "will not shutdown until the current 100 pages are complete." #~ msgstr "" #~ "Il pre-caricamento programmato della cache é stato annullato. Nel caso in " #~ "cui l'operazione fosse in corso, essa non verrà terminata sino al " #~ "completamento delle 100 pagine in uso." #~ msgid "(support for multiple domains on multisite websites) " #~ msgstr "(supporto per domini multipli o siti multi sito)" #~ msgid "" #~ "Scroll down this page and click the Update Mod_Rewrite Rules button." #~ msgstr "" #~ "Scorri verso il basso la pagina e premi il pulsante Update " #~ "Mod_Rewrite Rules." #~ msgid "WP Super Cache Manager" #~ msgstr "Gestione WP Super Cache" #~ msgid "Why your configuration may not be changed" #~ msgstr "Perché la tua configurazione non può essere modificata" #~ msgid "Why" #~ msgstr "Perché" #~ msgid "ON" #~ msgstr "ATTIVO" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "WP Cache e Super Cache sono attivi" #~ msgid "HALF ON" #~ msgstr "PARZIALE" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Super Cache non attivo, WP-Cache attivo" #~ msgid "OFF" #~ msgstr "NON ATTIVO" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "WP Cache e Super Cache non sono attivi" #~ msgid "Don’t cache pages for logged in users." #~ msgstr "Non effettuare la cache delle pagine per gli utenti collegati." #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "Rigenerazione della cache. Proponi agli utenti anonimi un file di " #~ "supercache quando un nuovo file sta per essere generato. L'attivazione di " #~ "questa funzione é preferibile per quei siti ad alto traffico e " #~ "con molti commenti. Questa opzione rende di fatto obsoleta la \"cache " #~ "diretta pagine\" e la \"modalità Lockdown\"." #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "Lista delle nuove pagine nella cache (non indicato per i siti ad alto " #~ "traffico - usare con cautela)" #~ msgid "" #~ "Mobile device support using WordPress Mobile Edition." #~ msgstr "" #~ "Il supporto Mobile device fa uso del WordPress Mobile " #~ "Edition." #~ msgid "" #~ "Uninstall using the uninstall script to remove files and directories created by the " #~ "plugin. (Please see readme." #~ "txt for instructions on uninstalling this script.)" #~ msgstr "" #~ "Utilizzando lo script di disinstallazione verranno rimossi tutti i file e tutte le cartelle " #~ "create dal plugin. (per maggiori informazioni sul come effettuare la " #~ "disinstallazione, consulta il readme.txt.)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s rende veramente più veloce il tuo blog. Rendilo più rapido* offrendomi una Amazon gift card! Partecipa a \"%" #~ "3$s\" con un qualsiasi importo tu desideri offrire. Ogni centesimo é di " #~ "aiuto!" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "Non ti piacesse Amazon, utilizza PayPal. Clicca sul pulsante \"Donazione" #~ "\" qui sotto oppure fai un salto alla mia wishlist." #~ msgid "Thanks in advance!" #~ msgstr "Un grazie anticipato!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Ok, considera che sebbene il tuo sito non sarà più veloce avrai almeno " #~ "reso più felice l'autore di questo plugin!" #~ msgid "Don’t show me this again." #~ msgstr "Non mostrarmelo più." #~ msgid "Hide" #~ msgstr "Nascondi" #~ msgid "" #~ "He blogs at %1$s, posts photos at %2$s and wishes he " #~ "had more time to read and relax." #~ msgstr "" #~ "Oltre al tempo dedicato alla lettura ed al relax, Donncha cura il blog %1" #~ "$s, pubblica le sue foto nel sito %2$s e riceve anche dei doni." #~ msgid "Super Cache Compression" #~ msgstr "Compressione Super Cache" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "" #~ "La compressione viene attivata come predefinita quando é in uso la " #~ "modalità PARZIALE." #~ msgid "Super Cache compression is now disabled." #~ msgstr "La compressione Super Cache é stata disattivata." #~ msgid "Super Cache compression is now enabled." #~ msgstr "La compressione Super Cache é stata attivata." #~ msgid "Update Compression" #~ msgstr "Aggiorna la compressione" #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "" #~ "E' necessario che tu modifichi il file aggiungendo le seguenti regole." #~ msgid "Debug Settings" #~ msgstr "Impostazioni debug" languages/wp-super-cache-sr_RS.mo000066600000245565152133035240012743 0ustar00, -<"<"3.#Mb###`# 2$~>$?$$ %*%7%#&54& j&=x'b'j(&(-($( (r))v6**u+K2,~,V-?Q./\001BD2w2%2%335.b67&J8q8:8n9_,:;;;;,< 5<B<T<h< <<3<<<== = =?=j>,>>^b?p?+2@^@e@{@n@/jAA A AGA`B+bBB3BBBBx C=C!CC!EBEF3F:FIF@3GtGsGmHHAH%8I^IJwIJ JJ JJKK5#K YKzKK3ML1LL[MqM0NNNN4N1OOuO fPjPGP:Q?Q*Q?R[RbRuRSSqS}ySSNSLTaT2UnGU$UAUV$V*VGVcVVeVVW[XtX XX<XgXJY]Y+YZ*#ZNZ]ZybZZ [b[M\V]&$^K_ __"i_`k)bc&ccWc-dEBdd*dde e eeLe]f$yff ffffgggYh$kh"hh!hh iijDjk(kEk<Kkbk kylqmm0m m!m-m:nkQop p pppmqTqqqUqUjmbؖ;lr{g%R?iB-?m*db[ dFo7rMah/ТZޣ$be> ϧ )1F)x¨ߨ*/!.Q3өש MM_YGOdw @ޮ0@߯* 4KD~ݱs\#в3)($Rw/} j|kt4bkFau/N% ,P7,dJrg !&$%EJDSj|Vz/aiTt63 jtz+1 i`zC"KB& Ph("N#!rfe< 2 Z)2\c{ ! *8XrB32 > 3!%sk= CO: PF  !Z+F?lZ!T >Jb^P ,8AJn:4#9I T.O~F  t7|.QO'<5" A MZ_tb)7 a,u-."# -9KiG2- .[8_I6R9Y.8 9 L Yfmd %x |  y [p     + pJ ?   vHg'XF6 KX9vf2:J"B#{/&d [etu/'/W1B/@3FL* wWUJ )k'y)n   D t o!!"J#$$;%%8&(Yd)P):*J*l(+,y,<,-`i...5a/'///0n1 #2.2I2h2~2)212E2~23|3.4M4lg44T536666v6R7 q7 |7&7m78O8-8=)9g9-m::g:g;;W;4;(<[<==?>?@A)BCC8DD{DuE(F&HH+H0"I4SI*I@I+I J0:J:kJ0J:J+K>K BK NKYKaK5 P.;)taFvB!rA%vSl]Hj NoBQE_LZ?1=xe'I<-bRCy3][ # (uY#6p Jg~k"DX/V4:Md9StfA"ay{& m2`; Uscj1(~08D^WMi >,9$F: $|fs2!Eqki-{ZYGm|n@}l [^8&.IRrKNc>hxHOo%u<`*h'Cb\Qwe*On}6qX57\WwT@,PJ=?L+d0z VU_K4T)G37z+/gp Make sure they appear before any existing WordPress rules. %1$s is Stephen Fry proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s).htaccess file may need to be moved1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because some hosts have had problems with the headers used in the past.Development VersionFrequently Asked QuestionsInstallation HelpSupport ForumCron View is a useful plugin to use when trying to debug garbage collection and preload problems.Use Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WPSCMin, a Supercache plugin that minifies cached pages by removing whitespaces and extra characters Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.This page explains how to change file permissions.UTC time is %sGarbage collection is the simple act of throwing out your garbage. For this plugin that would be old or stale cached files that may be out of date. New cached files are described as fresh.

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the Troubleshooting Guide. The WP_CACHE line must be moved up.

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.DO NOT CACHE PAGE secret key: %sError: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.Warning! Due to the way WordPress upgrades plugins the plugins you upload to wp-super-cache/plugins/ will be deleted when you upgrade WP Super Cache. You can avoid this by loading the plugins from elsewhere. Set $wp_cache_plugins_dir to the new location in wp-config.php and WP Super Cache will look there instead.
    More info available in the developer documentation.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|%s|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAuthor PagesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache Status MessagesCache TesterCache TimeoutCache expiry cron job failed. Job will run again in 10 seconds.Cache expiry cron job took more than 30 seconds. You should probably run the garbage collector more often.Cache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.CachedCached %s seconds agoCached files are fresh for a limited length of time. You can set that time in the Cache Timeout text box on this page.Cached pages are stored on your server as html and PHP files. If you need to delete them use the button below.Cached pages since %1$s : %2$sCachingCaching OffCaching OnCaching has been disabled on this blog on the Network Admin Sites page.Caching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck for stale cached files at this time (UTC) or starting at this time every interval below.Check for stale cached files every interval seconds.Check front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 600 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published or updated.Clear cache on error.Clock:Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.ContentsCould not update %s! WPCACHEHOME must be set in config file.Currently caching from post %d to %d.Currently logging to: %sDear User, WP Super Cache was removed from your blog but the mod_rewrite rules in your .htaccess were not. Please edit the following file and remove the code between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first! %s Regards, WP Super Cache Plugin http://wordpress.org/extend/plugins/wp-super-cache/DebugDebuggingDeleteDelete CacheDelete Cache On All BlogsDelete Cached PagesDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cache of the current pageDelete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDismissDisplay comments at the end of every page like this:Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.Don’t cache pages with GET parameters. (?x=y at the end of a url)EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. Email me when the garbage collection runs.Email the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnable dynamic caching (mfunc, mclude, dynamic-cached-content). See the FAQ for further details.)Enable logging on the Debug page here. That should help you track down the problem.EnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExcludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default).Existing direct pageExpired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionExtra homepage checks. (Very occasionally stops homepage caching)FAILEDFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGarbage collection by this plugin clears out expired and old cached pages on a regular basis. Use this form to enable it.Gzip encoding rules in %s.htaccess created.HH:MMHe blogs at %1$s and posts photos at %2$s.Hide file listHomeHow long should cached pages remain fresh? Set to 0 to disable garbage collection. A good starting point is 3600 seconds.I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesInterval:It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It appears you have WordPress installed in a sub directory as described here. Unfortunately WordPress writes to the .htaccess in the install directory, not where your site is served from.
    When you update the rewrite rules in this plugin you will have to copy the file to where your site is hosted. This will be fixed in the future.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:Jetpack Mobile ThemeJetpack Mobile Theme support is now %sKeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match.Local time is %1$sLock DownLock Down:Make WordPress FasterMake known users anonymous so they’re served supercached static files.Make the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile BrowsersMobile PrefixesMobile device support. (External plugin or theme required. See the FAQ for further details.)Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next scheduled garbage collection will be at %s UTCNo Adverts for FriendsNo Adverts for Friends support is now %sNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.Notification EmailsOKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.Or, the Clock scheduler allows the garbage collection to run at specific times. If set to run hourly or twicedaily the garbage collector will be first scheduled for the time you enter here. It will then run again at the indicated interval. If set to run daily it will run once a day at the time specified.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preload tags, categories and other taxonomies.Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Stephen Fry proof! (places a message in your blog’s footer)Provides support for No Adverts for Friends.Provides support for Domain Mapping plugin to map multiple domains to a blog.Provides support for WPTouch mobile theme and plugin.Provides support for the Jetpack mobile theme and plugin. PHP caching mode and mobile support will be enabled too.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRemove UTF8/blog charset support from .htaccess file. Only necessary if you see odd characters or punctuation looks incorrect. Requires rewrite rules update.Required to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache almost cancelled. It may take up to a minute for it to cancel completely.Scheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.SchedulerScheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSites that want to serve lots of newly generated data should set the Cache Timeout to 60 and use the Timer scheduler set to 90 seconds.Sites where an external data source updates at a particular time every day should set the timeout to 86400 seconds and use the Clock scheduler set appropriately.Sites with lots of static content, no widgets or rss feeds in their sidebar can use a timeout of 86400 seconds or even more and set the timer to something equally long.Sites with widgets and rss feeds in their sidebar should probably use a timeout of 3600 seconds and set the timer to 600 seconds. Stale files will be caught within 10 minutes of going stale.Skip https URLs to avoid "mixed content" errorsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStale cached files are not removed as soon as they become stale. They have to be removed by the garbage collecter. That is why you have to tell the plugin when the garbage collector should run.Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.Supercache Uninstall ProblemsTagsTest CacheTest your cached website by clicking the test button below.Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The CDN Sync Tool plugin will help upload files to Amazon S3/Cloudfront if you would rather not depend on origin pull. See the plugin support forum if you have any queries about this plugin.The Timer scheduler tells the plugin to run the garbage collector at regular intervals. When one garbage collection is done, the next run is scheduled.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!There are no best garbage collection settings but here are a few scenarios. Garbage collection is separate to other actions that clear our cached files like leaving a comment or publishing a post.These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$sThings you can do:This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.Timer:To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required then simple instructions are provided.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.Use the Timer or Clock schedulers to define when the garbage collector should run.Use the debug system in the Debug tab above. It will tell you what the plugin is doing.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWPTouchWPTouch plugin detected! Please go to the Supercache plugins page and enable the WPTouch helper plugin.WPTouch support is now %sWarningWarning!Warning! %s is writeable!Warning! 304 browser caching is only supported when not using mod_rewrite caching.Warning! PRELOAD MODE activated. Supercache files will not be deleted regardless of age.Warning! Compression is disabled as gzencode() function not found.Warning! Garbage collection is not scheduled!Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory (%1$s) did not exist and couldn’t be created by the web server. Check %1$s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing %2$s taxonomy from %3$d to %4$d[%1$s] Refreshing posts from %2$d to %3$d[%1$s] WP Super Cache GC Report[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledsecondstimezone date formatY-m-d G:i:sProject-Id-Version: WP super cache plugin Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2013-04-16 12:02:02+00:00 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PO-Revision-Date: 2013-05-07 19:00+0100 Last-Translator: Anja Skrba Language-Team: Anja Skrba Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2); Language: Srpski / Serbian X-Generator: Poedit 1.5.5 X-Poedit-SourceCharset: UTF-8 Postarajte se da se ona pojave pre bilo kakvih postojećih WordPress pravila.%1$s je Stephen Fry proveren (Stephen Fry proof), zahvaljujući keširanju od strane %2$s%1$s je održavan i razvijen od strane %2$s, uz doprinos mnogih drugih.%s keširanih strana%s isteklih stranaU %s je moguć upis podataka. Molim vas, onemogućite upis podataka u ovaj fajl, nakon što se generiše vaša strana, jer je to sigurnosni rizik.%s uklonjeno!%s.htaccess je dopunjen sa neophodnim mod_rewrite pravilima. Molim vas, potvrdite da su ona ispravna. Trebalo bi da ovako izgledaju:%s/advanced-cache.php ne postoji i ne može da se ažurira.(Eksperimentalno)(Podržano je samo nasleđeno keširanje, kompresija je isključena, i traži se Bad Behaviour u direktorijumu "%s/plugins/bad-behavior/") (može biti neprecizno kod opterećenih sajtova)(zahtevi za logove samo sa ove IP adrese. Vaša IP adresa je %s).htaccess fajl možda treba da se premesti1. Ako već postoji, molim vas da ga prvo obrišete.2. Omogućite upis podataka u %s-e, koristeći naredbu chmod, preko vašeg ftp, ili serverskog softvera. (chmod 777 %1$s) i osvežite ovu stranu. Ovo je samo privremena mera, i moraćete posle da opet onemogućite upis u njega. (U prethodnoj naredbi promenite 777 u 755)3. Osvežite ovu stranu da ažurirate %s/advanced-cache.php304 Ne modifikovano (Not Modified) keširanje od strane pregledača. Ukazuje kada strana nije izmenjena od poslednjeg zahteva.Podrška za 304 je u startu isključena, jer neki hostinzi imaju problema sa zaglavljima korišćenim u prošlosti.razvojna verzijaČesto postavljana pitanja (FAQ)Pomoć oko instalacijeforum za podrškuCron View je koristan dodatak, za korišćenje onda kada pokušavate da otklonite programske greške koje prave probleme sa uklanjanjem smeća i učitavanjem unapred.Use Google Libraries vam omogućava da učitate neke često korišćene Javascript biblioteke sa Google web servera. Ironija je što to može umanjiti vaš Yslow rezultat.WPSCMin, Supercache dodatak koji minimizira keširane strane, uklanjajući prazan prostor i višak karakteraYahoo! Yslow je proširenje za Firefox nadgradnju, Firebug. Ono analizira web strane i predlaže načine za unapređivanje njihovih performansi, prema pravilima za web strane visokih performansi. Takođe probajte onlajn alate za performanse, na GTMetrix.Ova strana objašnjava kako promeniti dozvole za fajlove.UTC (usklađeno univerzalno vreme) vreme je %sSakupljanje smeća je jednostavno čin izbacivanja vašeg smeća. Za ovaj dodatak, to bi bili stari, ili nekorišćeni keširani fajlovi koji bi mogli biti zastareli. Novi keširani fajlovi se nazivaju svežim.

    WP_CACHE konstanta je dodata u wp-config.php

    Ako i dalje budete videli ovu poruku sa upozorenjem, molim vas, pogledajte tačku 5 Vodiča za otklanjanje problema (Troubleshooting Guide). WP_CACHE linija se mora pomeriti na gore.

    WP_CACHE konstanta je podešena na vrednost false

    WP_CACHE konstantu WordPress koristi da učita kod koji servira keširane strane. Na žalost, ona je podešena na vrednost false. Molim vas, uredite vaš wp-config.php fajl i dodajte ili uredite sledeće linije, iznad završne naredbe require_once:

    define('WP_CACHE', true);

  • 1. Otvorite fajl %1$s$wp_cache_file u nekom uređivaču teksta.
  • 2. Izmenite tekst CACHEHOME u %2$s
  • 3. Sačuvajte fajl i kopirajte ga u %3$s, a zatim osvežite ovu stranu.
    • UPOZORENJE: Pre nego snimite izmene, isprobajte nekoliko statičnih url-ova, npr. %s , da budete sigurni da vaš CDN servis radi u potpunosti.Samo za napredne korisnike: Speed up your site with Caching and cache-control (Ubrzajte vaš sajt pomoću keširanja i kontrole keša) objašnjava kako da vaš sajt učinite pogodnijim za keširanje, pomoću .htaccess pravila.Samo za napredne korisnike: Instalirajte neki objektni keš. Odaberite između Memcached, XCache, eAcccelerator i drugih.NE KEŠIRATI STRANU tajni ključ: %sGreška: WP_CACHE nije uključen u vašem wp-config.php fajlu, i ne mogu da ga izmenim.Poslednja keširana strana: %sUpozorenje! Pokušali ste da uključite kompresiju, ali je zlib.output_compression uključeno. Pogledajte #21 u sekciji o otklanjanju problema (Troubleshooting section), readme fajla.Upozorenje! Zbog načina na koji WordPress unapređuje dodatke, dodaci koje prenesete u wp-super-cache/plugins/ će biti obrisani kada unapredite WP Super Cache. Ovo možete izbeći učitavanjem dodataka sa neke druge lokacije. U fajlu wp-config.php podesite $wp_cache_plugins_dir na novu lokaciju, i WP Super Cache će tražiti tu, umesto na staroj lokaciji.
    Više informacija je dostupno u dokumentaciji za programere.Da bi ovaj dodatak pravilno radio, potreban je prilagođeni url, ili prilagođena permalink struktura. Molim vas, idite na Stranu sa opcijama vezanim za permalinkove (Permalinks Options Page), da konfigurišete vaše permalinkove.Pronađena je razlika između pravila u vašem .htaccess fajlu i pravila dodatka, za ponovni upis. Ovo može biti jednostavno razlika u praznom prostoru, ali bi što pre trebalo da uporedite pravila u fajlu sa ovim donjim. Da ažurirate pravila, kliknite na dugme ’Ažurirati Mod_Rewrite pravila (Update Mod_Rewrite Rules)’.Jednostavan način da se to uradi je privremeno menjanje dozvola, koristeći naredbu CHMOD, ili preko vašeg ftp klijenta. Postarajte se da u njega globalno bude omogućen upis podataka, i trebalo bi sve da bude u redu.Prihvaćena imena fajlova i odbačeni URI-jiDodati direktnu stranu:Ovde dodajte stringove (ne ime fajla), koji forsiraju da strana ne bude keširana. Na primer, ako vaši URL-ovi uključuju godinu, a ne želite da keširate prošlogodišnje objave, dovoljno je navesti godinu, npr. ’/2004/’. WP-Cache će tražiti da li je taj string deo URI-ja, i ako jeste, neće keširati tu stranu.Ovde dodajte imena fajlova koji mogu da se keširaju, čak i ako sadrže neki od gornjih stringova za odbacivanje.Sami dodajte pravila. Otvorite fajl %s.htaccess u uređivaču, i pronađite blok koda koji se nalazi između linija # BEGIN WPSuperCache i # END WPSuperCache. Tu se nalaze dve sekcije koje izgledaju vrlo slično. Odmah ispod linije %%{HTTP:Cookie} !^.*(comment_author_|%s|wp-postpass_).*$ dodajte ove linije: (uradite to dva puta - za svaku sekciju)Dodatni CNAME zapisiNaprednoStarostAlternativno, možete manuelno urediti vaš fajl %s.htaccess, i dodati sledeći kod (pre bilo kakvih WordPress pravila):ArhiveStrane o autorimaRaspoloživi dodaciČekanje na moderacijuČekanje na moderaciju je sada %sBad Behaviour (nepristojno ponašanje)Podrška za Bad Behaviour je sada %sBad Behaviour nije pronađen. Molim vas, proverite vašu instalaciju.CDNCDN funkcionalnost koju daje OSSDL CDN Off Linker od Mark Kubacki-aSadržaj kešaPoruke o statusu kešaProverivač kešaVreme isteka kešaCron zadatak za istek keša nije uspeo. Zadatak će se ponovo pokrenuti za 10 sekundi.Cron zadatku za istek keša je trebalo više od 30 sekundi. Verovatno bi trebalo da češće pokrećete sakupljač smeća.Keš pogoci na ovom web sajtu, za brzi pristup.Keš dodaci su PHP skripte koje se nalaze u folderu sa dodacima (plugins), unutar wp-super-cache foldera. One se učitavaju kada se učitava Supercache, mnogo pre nego obični WordPress dodaci.Ponovna izgradnja keša. Servirati anonimnim korisnicima superkeširani fajl, dok se generiše novi fajl.Statistike keša se ne generišu automatski. Morate kliknuti na donji link da na ovoj strani generišete statistike.Poslednje generisanje statistika keša: pre %s minuta.KeširanoKeširano pre %s sekundiKeširani fajlovi ostaju sveži ograničeno vreme. To vreme možete podesiti u tekstualnom polju Vreme isteka keša (Cache Timeout), na ovoj strani.Keširane strane se čuvaju na vašem serveru, kao html i PHP fajlovi. Ako morate da ih obrišete, upotrebite donje dugme.Keširano strana, od %1$s : %2$sKeširanjeKeširanje isključenoKeširanje uključenoKeširanje na ovom blogu je isključeno na strani za mrežnu administraciju sajtova (Network Admin Sites)Keširanje je samo jedan deo ubrzavanja web sajta. Evo i nekih drugih dodataka koji će pomoći:Da bi se koristilo ovo svojstvo, keširanje mora da bude uključenoOtkazati učitavanje keša unapredNije moguće nastaviti... otklonite prethodne probleme i pokušajte ponovo.Fajl .htaccess ne može da se ažuriraKategorijaIzmeniti isticanjeTražiti keširane fajlove koji se ne koriste u ovo vreme (UTC), ili, počevši od ovog vremena, svakih interval nadalje.Tražiti keširane fajlove koji se ne koriste, svakih interval sekundi.Proveravati prvu stranu svakih 5 minuta.Traženje i brisanje isteklih fajlova je skupo, ali je takođe skupo ostavljati ih gde jesu. Na veoma posećenom sajtu, trebalo bi da podesite vreme isteka na 600 sekundi. Eksperimentišite sa različitim vrednostima i posećujte ovu stranu, da vidite koliko isteklih fajlova ostaje u različito vreme, tokom dana. Ako koristite staro keširanje (legacy caching), ciljajte na to da imate manje od 500 keširanih fajlova, ako je to moguće. Kada koristite mod_rewrite ili PHP keširanje, možete imati mnogo više keširanih fajlova.Brisanje starih superkeš fajlova.Obrisati sve keš fajlove, onda kada se objava ili strana objavi ili ažurira.Obrisati keš u slučaju greške.Sat:Grubo zaključavanje fajlova. Ovo vam verovatno ne treba, ali može pomoći ako je vaš server slabijih mogućnosti. Upozorenje! U vrlo retkim slučajevima može izazvati zaključavanje servera!Uključena je moderacija komentara. Vašem komentaru može biti potrebno određeno vreme da se pojavi.Komprimovati strane, tako da se brže serviraju posetiocima.Kompresija je u startu isključena, jer neki hostinzi imaju problema sa komprimovanim fajlovima. Njeno uključivanje i isključivanje brišu keš.Konfiguracioni fajl je izmenjen, neke vrednosti bi mogle biti pogrešne. Učitajte stranu ponovo, iz menija "Podešenja (Settings", da ih resetujete.Konfiguracioni fajl nedostaje, a u %1$-ov direktorijum (%2$s) nije moguć upis podataka od strane web servera. Proverite njegove dozvole.Sadržaji%s nije mogao da se ažurira! WPCACHEHOME mora da se podesi u konfiguracionom fajlu.Trenutno se keširaju objave od %d do %d.Trenutno se prijavljuje na: %sDragi korisniče, WP Super Cache je uklonjen sa vašeg bloga, ali mod_rewrite pravila u vašem .htaccess nisu. Molim vas, uredite sledeći fajl i uklonite kod između 'BEGIN WPSuperCache' i 'END WPSuperCache'. Molim vas, prvo napravite backup kopiju fajla! %s Sa poštovanjem, WP Super Cache dodatak http://wordpress.org/extend/plugins/wp-super-cache/Otklanjanje programskih grešakaOtklanjanje programskih grešakaObrisatiObrisati kešObrisati keš na svim blogovimaObrisati keširane straneObrisati istekloObrisati Super Cache keširane fajlove (otvara se u novom prozoru)Obrisati keš aktuelne straneObrisati keširani fajlU %s.htaccess fajlu obrišite mod_rewrite pravila dodatka, smeštena između # BEGIN WPSuperCache i # END WPSuperCache, i pustite da ih dodatak opet generiše, učitavajući ponovo ovu stranu.Brisanje superkeš fajla: %s
    Brisanje wp-cache fajla: %s
    Programeri: Učinite vaš dodatak kompatibilnim sa zaključavanjem, čekiravši "WPLOCKDOWN" konstantu. Sledeći kod će se postarati da vaš dodatak poštuje WPLOCKDOWN podešenje.Direktno keširani fajloviDirektno keširani fajlovi se kreiraju direktno iz %s, gde se nalazi vaš blog. Ovo svojstvo je korisno samo ako očekujete značajan nivo Digg ili Slashdot saobraćaja ka jednoj objavi, ili strani.Direktorijumi koje treba uključiti pri statičkom upoređivanju fajlova. Koristite zapetu kao razdvajač. Podrazumevani su wp-content, wp-includes, koji će se uključiti ako se ovo polje ostavi prazno.IsključitiIsključenoOdbacitiPrikazivati komentare na kraju svake strane, ovako:Ne keširati sledeće tipove strana. Pogledajte dokumentaciju o Uslovnim tagovima (Conditional Tags), za kompletnu diskusiju o svakom tipu.Domain Mapping (mapiranje domena)Pronađen je dodatak Domain Mapping! Molim vas, idite na stranu Supercache dodataka i uključite pomoćni dodatak za mapiranje domena.Podrška za Domain Mapping je sada %sNe keširati strane za poznate korisnike.Ne keširati strane sa GETparametrima. (?x=y, na kraju url-a)JednostavnoUredite %s i dodajte sledeću liniju:
    define('WP_CACHE', true);
    U suprotnom, WP-Cache se neće izvršiti od strane WordPress jezgra. Obavestiti me e-mailom kada se pokrene sakupljanje smeća.Poslati e-amil administratoru bloga, kada se urade provere. (korisno za proveru)UključitiUključiti CDN podrškuUključiti dinamičko keširanje (mfunc, mclude, dynamic-cached-content). Pogledajte često postavljana pitanja (FAQ) za više detalja.)Omogućiti prijavu na strani za otklanjanje programskih grešaka (Debugging page), ovde. To bi trebalo da vam pomogne da pronađete problem.UključenoUključuje ili isključuje dodatak za uklanjanje teksta "Vaš komentar čeka moderaciju (Your comment is awaiting moderation).", kada neko ostavi moderisani komentar.GreškaGreška: GZIP kompresija je uključena, isključite je ako hoćete da uključite wp-cache.Isključiti ako je pod-nizIsključuje nešto da ne bude presnimljeno, ako se jedan od gornjih stringova pronađe među rezultatima koji se podudaraju. Upotrebite zapetu kao razdvajač, ovako: .php, .flv, .do, i uvek uključite .php (podrazumevano).Postojeća direktna stranaIstekli fajlovi su stariji od %s sekundi. Oni se i dalje koriste od strane dodatka, i brišu se periodično.Vreme isteka i sakupljanje smećaDodatne provere početne strane. (Veoma retko zaustavlja keširanje početne strane)NIJE USPELOIzvori podataka (feeds)Preuzimanje %s u primarni keš:Preuzimanje prve kopije %s:Preuzimanje druge kopije %s:Popraviti konfiguracijuRešava probleme sa dodatkom, otklanjajući ovde programske greške. Može napraviti dnevnički zapis o njima u vašem keš direktorijumu.Za najbolje performanse treba da uključite "Podršku za mobilne uređaje (Mobile device support)", ili da obrišete mobilna pravila za ponovni upis u vašem fajlu .htaccess. Potražite 2 linije sa tekstom "2.0\ MMP|240x320", i obrišite ih.Na primer: da keširate %1$sabout/, unećete %1$sabout/ ili /about/. Keširani fajl će se generisati sledeći put kada anonimni posetilac poseti tu stranu.Sveži superkeširani fajloviSveži WP-Cache fajloviPrva stranaTekst prve stranePotpuno osvežavanje keša za %d časova, %d minuta i %d sekundi.GZIP kompresija je uključena u WordPress-u, wp-cache će biti zaobilažen dok ne isključite gzip kompresiju.Sakupljanje smećaSakupljanje smeća od strane ovog dodatka redovno briše istekle i stare keširane strane. Upotrebite ovaj obrazac da ga uključite.U %s.htaccess fajlu su kreirana pravila za Gzip kodiranje.HH:MMOn bloguje na %1$s i objavljuje fotografije na %2$s.Sakriti listu fajlovaPočetna stranaKoliko dugo keširane strane treba da ostanu sveže? Da isključite sakupljanje smeća, postavite vrednost 0. Dobra polazna tačka je 3600 sekundi.99% sam siguran da to nisu programske greške u WP Super Cache-u, i do njih dolazi samo u veoma retkim slučajevima, ali možete pokrenuti jednostavnu proveru svakih 5 minuta, da potvrdite da je vaš sajt u redu, ako ste zabrinuti. Biće vam poslat e-mail ako bude problema.IP adreseAko to ne funkcioniše, proverite da li fajl %s/advanced-cache.php postoji:Ako de-instalirate ovaj dodatak, postarajte se da u direktorijum %s bude omogućen upis od strane web servera, tako da fajlovi advanced-cache.php i cache-config.php mogu automatski da budu obrisani. (Osiguravanje da i u ove fajlove bude moguć upis je verovatno dobra ideja!)U ’Modu za učitavanje unapred (Preload Mode&)#8217; redovno sakupljanje smeća će očistiti samo stare zaostale (legacy) fajlove, za poznate korisnike., a ne unapred učitane superkeš fajlove. Ovo je podrazumevano podešenje, onda kada se keš učitava unapred.U veoma retkim slučajevima, na nekim blogovima se mogu pojaviti dva problema:
    1. Prva strana može da počne da se preuzima kao zip fajl.
    2. Povremeno se kao prva strana kešira pogrešna strana, ako vaš blog koristi statičnu prvu stranu, a permalink struktura teme je /%category%/%postname%/.
    Uključiti direktorijumeInterval:Izgleda da mod_rewrite nije instaliran. Ponekad ova provera nije 100% pouzdana, posebno ako ne koristite Apache. Molim vas, potvrdite da je učitan modul mod_rewrite. On je potreban za serviranje Super Cache statičnih fajlova. I dalje ćete moći da koristite zastarele ili PHP modove.Izgleda da vam je WordPress instaliran u pod-folderu, kao što je opisano ovde. Na žalost, WordPress upisuje podatke u .htaccess fajl u instalacionom direktorijumu, a ne tamo odakle se vaš sajt servira.
    Kada ažurirate pravila za ponovni upis u ovom dodatku, moraćete da kopirate ovaj fajl na lokaciju na kojoj se hostuje vaš sajt. Ovo će u budućnosti biti rešeno.Izgleda da vaš blog ima URL-ove koji završavaju sa "/". Na žalost, pošto ste instalirali ovaj dodatak, programska greška sa dupliranim sadržajem se pojavljuje tamo gde URL-ovi ne završavaju sa "/", i servira se isti sadržaj kao za one sa "/", a ne vrši se usmeravanje na odgovarajući URL. Da popravite ovo, morate urediti vaš .htaccess fajl, i dodati ova pravila dvema grupama Super Cache pravila:Jetpack tema za mobilne uređajePodrška za Jetpack temu za mobilne uređaje je sada %sKljučKasna inicijalizacija. Prikazuje keširane fajlove nakon što se učita WordPress. Najkorisnije u starom modu (legacy mode).Staro keširanje strana (legacy page caching).Manje e-mailova, 1 na početku i 1 na kraju prethodnog učitavanja svih objava.Prikazati listu svih keširanih fajlovaPrikazati listu poslednjih keširanih strana na ovoj strani.Učitajte vašu početnu stranu u odjavljen pregledač i proverite vremensku oznaku na kraju html izvornog koda. Učitajte istu stranu ponovo, i uporedite vremensku oznaku. Keširanje funkcioniše ako se vremenske oznake podudaraju.Lokalno vreme je %1$sZaključatiZaključati:Učinite WordPress bržimUčiniti poznate korisnike anonimnim, tako da im se serviraju superkeširani statički fajlovi.Ispraznite tekstualno polje, da ga uklonite sa liste direktnih strana, i obrišete keširani fajl.Mnogo e-mailova, 2 e-maila na 100 objava.Srednje, 1 e-mail na 100 objava.RaznoNedostaju Apache moduli Mobilni pregledačiMobilni prefiksiPodrška za mobilne uređaje. (Potreban je spoljni dodatak, ili tema. Pogledajte često postavljana pitanja (FAQ) za više detalja.)Otkrivena su mobilna pravila za ponovni upisPodrška za mobilne uređaje zahteva dodatna pravila u vašem fajlu .htaccess, ili možete podesiti dodatak na zastareli mod (legacy mode). Evo vaših opcija (poređanih po težini):Mod Rewrite pravilaMod Rewrite pravila ne mogu da se ažuriraju!Mod Rewrite pravila moraju da budu ažurirana!Mod Rewrite pravila su ažurirana!Mod rewrite možda nije instaliran!Mod_rewrite je najbrži, PHP je skoro isto tako brz, a jednostavniji za stavljanje u rad, dok je, opet, staro keširanje (legacy caching) sporije, ali je fleksibilnije i, takođe, jednostavnije za stavljanje u rad. Novi korisnici bi trebalo da koriste PHP keširanje.Treba vam pomoć?Treba vam pomoć? Pogledajte Super Cache readme fajl. On uključuje instalacionu dokumentaciju, često postavljana pitanja (FAQ) i savete za otklanjanje problema. Takođe je dostupan i forum za podršku. Na vaše pitanje je možda već odgovoreno.Najnovije keširane strane:Sledeće zakazano sakupljanje smeća će biti u %s UTCNo Adverts for Friends (bez reklama za prijatelje)Podrška za No Adverts for Friends je sada %sNapomena:Napomena: uključuje PHP keširanje, ponovnu izgradnju keša i podršku za mobilne uređajeObratite pažnju: Uključeni su Mod_rewrite, ili zastarelo keširanje (Legacy caching). Podrazumevano je prikazivanje strane sa naprednim podešenjima (Advanced Settings).Obratite pažnju: Uključeno je PHP keširanje, ali su pronađena Supercache mod_rewrite pravila za ponovni upis. Keširani fajlovi će biti servirani koristeći ta pravila. Ako vaš sajt dobro funkcioniše, molim vas, ignorišite ovu poruku, ili možete urediti .htaccess fajl u osnovnom direktorijumu vaše instalacije i ukloniti SuperCache pravila.Obratite pažnju: Provere WP Super Cache mod_rewrite pravila su iksljučene, osim ako vam glavni sajt radi na ovoj mreži.E-mailovi sa obaveštenjimaU reduU upotrebi je objektni keš. Nije dostupan listing keša.Spoljašnji URLJedan ili više zahteva za stranu nije uspelo:Osvežiti aktuelnu stranu samo kada se ostave komentari.Ili, Sat (Clock) planer, koji omogućava da se sakupljač smeća pokreće u određeno vreme. Ako je podešen da radi na svaki sat, ili dva puta na dan, pokretanje sakupljača smeća će prvo biti zakazano u vreme koje unesete ovde. Nakon toga će biti pokretan u navedenim intervalima. Ako je podešen da se pokreće jednom dnevno, on će se pokretati jednom dnevno - u navedeno vreme.PHP komprimuje podatke koji se šalju posetiocima vašeg sajta. Isključivanje ovoga se preporučuje, jer dodatak kešira komprimovani izlaz jednom, umesto komprimovanja iste strane iznova i iznova. Takođe pogledajte #21 u sekciji o otklanjanju problema (Troubleshooting section). Pogledajte ovu stranu za instrukcije o modifikovanju vašeg php.ini fajla.Strana %d: %d (%s)Strana 1: %sStrana 2: %sStraneGreška permalink struktureMolim vas, ocenite ovaj dodatak i recite mi da li, u vašem slučaju, funkcioniše, ili ne. Ovo stvarno pomaže razvoju.Molim vas, napravite fajl %s /wp-cache-config.php iz fajla wp-super-cache/wp-cache-config-sample.phpMolim vas, pozdravite i njega, na %s!Molim vas, pogledajte stavku 16 u Troubleshooting section (Sekciji o otklanjanju problema) readme.txt fajlaMolim vas, pogledajte readme.txt fajl, za instrukcije o de-instaliranju ove skripte. otražite naslov "How to uninstall WP Super Cache (Kako de-instalirati WP Super Cache)".Molim vas, posetite %1$s da obrišete keš, pošto prva strana vašeg sajta nije ispravna, i nedostaje joj tekst, "%2$s"!Molim vas, posetite %s da obrišete keš, pošto se prva strana vašeg sajta sada preuzima.DodaciUčitavanje unapredUnapred učitati %s objava.Učitati keš unapred sadaUčitavanje unapred je ponovo započeto. %sMod za učitavanje unapred (Preload mode) (sakupljanje smeća samo nad zastarelim keš fajlovima. Preporučeno.)Unapred učitati oznake (tags), kategorije i druge taksonomije.Međutim, učitavanje unapred kreira dosta fajlova. Keširanje se radi od najnovije do najstarije objave, tako da, molim vas, ako imate mnogo (10,000+) objava, razmislite o tome da keširate samo one najnovije. Ovo je naročito važno kod deljenog hostinga.Isključeno je učitavanje keša unapred. Molim vas, isključite keširanje zastarelih strana, ili razgovarajte sa vašim hosting administratorom.Pripremite vaš server za neočekivani saobraćajni špic, omogućivši zaključavanje. Kada je ono uključeno, novi komentari na objave neće osvežavati keširane statičke fajlove.Ponosno recite svetu da je vaš server Stephen Fry proof! (postavlja poruku u podnožju vašeg bloga)Obezbeđuje podršku za No Adverts for Friends.Obezbeđuje podršku za Domain Mapping dodatak, za uparivanje (mapiranje) više domena sa blogom.Obezbeđuje podršku za WPTouch temu, i dodatak, za mobilne uređajeObezbeđuje podršku za Jetpack temu, i dodatak, za mobilne uređaje.Ocenite ovaj dodatak!Mod u kome je moguć samo pregled. Konfiguracija ne može da se menja.Moguć samo pregled:PreporučenoPreporučeni linkovi i dodaciOsvežavanje keša za %d časova, %d minuta i %d sekundi.Osvežavati unapred učitane keš fajlove svakih %s minuta. (0 za isključivanje, najmanje %d minuta.)Osvežiti ovu stranu kada se dozvole fajla izmene.Kada ažurirate vaš .htaccess fajl, osvežite ovu stranu.Osvežene su sledeće objave:Ponovo generisati statistike kešaOdbačeni korisnički agentiUkloniti UTF8/blog karakter-set podršku iz .htaccess fajla. Potrebno je samo ako vidite neobične karaktere, ili interpunkcija izgleda nepravilno. Zahteva ažuriranje pravila ponovnog upisa (rewrite rules).Potrebno da se pravilno serviraju komprimovani supercache fajlovi.Potrebno da bi se na supercache stranama postavile informacije o keširanju. Korisnici IE7 će videti stare strane, bez ovog modula.Vratiti podrazumevanu konfiguracijuPravila za ponovni upis moraju da se ažurirajuPravila se takođe moraju dodati u %s:WP-Cache konfiguracioni fajl - primer (%s) ne postoji. Proverite vašu instalaciju.SačuvatiSnimiti izmeneSačuvati fajloveSačuvati stringoveSačuvati UA stringoveZakazano učitavanje keša unapred je skoro otkazano. Može potrajati još najviše minut dok se ono potpuno otkaže.Zakazano učitavanje keša unapred je otkazano.Zakazano učitavanje keša unapred za %d minutaZakazano učitavanje keša unapred za 10 sekundi.PlanerSledeće osvežavanje učitavanja unapred se zakazuje za %d minutaSkrolujte na dole, na strani sa naprednim podešenjima (Advanced Settings), i kliknite na dugme Ažurirati mod_rewrite pravila (Update Mod_Rewrite Rules).Strane za pretraguSlati mi e-mailove kada se fajlovi osvežavaju.Slati neobezbeđene (koji nisu https) zahteve za početnu stranuodešavanje datuma isteka na superkeširanim stranama. Posetioci mogu da ne vide nove strane kada osvežavaju sadržaj u pregledaču ili ostavljaju komentare, bez ovog modula.Da isključite sakupljanje smeća, podesite vreme isteka na 0 sekundi.Podesite dodatak na zastareli mod i uključite podršku za mobilne uređaje.PodešavanjaPojedinačne objaveSajtovi koji žele da pruže dosta novo generisanih podataka, treba da podese Vreme isteka keša (Cache Timeout) na 60, i da koriste Tajmer (Timer), podešen na 90 sekundi.Sajtovi čiji se neki spoljni izvor podataka ažurira svakog dana u isto vreme, treba da podese vreme isteka na 86400 sekundi, i da koriste Sat (Clock) planer u skladu sa tim.Sajtovi sa dosta statičkog sadržaja, bez vidžeta i rss tokova u svojoj bočnoj traci, mogu da koriste vreme isteka od 86400 sekundi, pa čak i više, i da podese tajmer na neko podjednako dugo vreme.Sajtovi sa vidžetima i sa rss tokovima u svojoj bočnoj traci, verovatno treba da koriste vreme isteka od 3600 sekundi, i da podese tajmer na 600 sekundi. Fajlovi koji se ne koriste će se uhvatiti u roku od 10 minuta, od kako postanu "ustajali".Preskočiti https URL-ove, da se izbegnu "pomešani sadržaj (mixed content)" greškeŽao mi je. Moj blog je zaključan. Ispravke/dopune će se pojaviti uskoroSuperkeširani fajlovi koji se ne koristeWP-keširani fajlovi koji se ne koristeKeširani fajlovi koji se ne koriste, ne uklanjaju se čim postanu "ustajali". Njih mora da ukloni sakupljač smeća. Zato morate reći dodatku kada sakupljač smeća treba da se pokrene.Stringovi u HTTP ’User Agent’ zaglavlju, koji sprečavaju WP-Cache da kešira zahteve botova, tragača (spiders) i pretraživača (crawlers). Imajte na umu da se superkeširani fajlovi i dalje šalju ovim agentima, ako već postoje.Problemi sa de-instaliranjem Supercache-aOznake (tags)Proveriti kešProverite svoj keširani web sajt, klikom na donje dugme za proveru.Tekst za traženje na prvoj strani. Ako ovaj tekst nedostaje, keš će biti obrisa. Da isključite, ostavite prazno.Hvala vam za unapređivanje.Dodatak CDN Sync Tool će vam pomoći da prenesete fajlove na Amazon S3/Cloudfront, ako radije ne biste da zavisite od origin pull-a. Pogledajte forum za podršku dodatku, ako imate bilo kakvih pitanja u vezi sa ovim dodatkom.Tajmer (Timer) planer govori dodatku da pokreće sakupljač smeća u pravilnim intervalima. Kada jedan sakupljač smeća završi sa radom, zakazuje se sledeće pokretanje.WP Super Cache konfiguracioni fajl je %s/wp-cache-config.php, i ne može se menjati. U taj fajl mora da bude omogućen upis podataka od strane web servera, da bi se pravile bilo kakve izmene.Keš na vašem blogu je obrisan, pošto na prvoj strani vašeg sajta nedostaje tekst "%2$s". Molim vas, posetite %1$s, da potvrdite da je keš obrisan.Keš na vašem blogu je obrisan, pošto se prva strana vašeg sajta sada preuzima. Molim vas, posetite %s, da potvrdite da je keš obrisan.Fajl %s.htaccess nije mogao da bude izmenjen od strane web servera. Molim vas, ispravite ovo, koristeći naredbu chmod, ili vaš ftp klijent.Nedostaju sledeći Apache moduli. Bez njih će ovaj dodatak raditi u zastarelom modu. Međutim, u punom Supercache modu, vaši posetioci mogu da vide nepotpune strane, ili sadržaj koji više nije važeći.Mod_rewrite pravila su se promenila od kada ste poslednji put instalirali ovaj dodatak. Na žalost, morate ukloniti stara superkeš pravila pre nego se nova ažuriraju. Kada završite uređivanje vašeg .htaccess fajla, osvežite ovu stranu. Ako želite da uradite manuelno unapređivanje, izmenite sledeću liniju: %1$s, da izgleda ovako: %2$s Jedine izmene su to što "HTTP_COOKIE" postaje "HTTP:Cookie" i "wordpressuser" postaje "wordpress". Ovo je WordPress 2.5 izmena, ali ona je komaptibilna unazad sa starijim verzijama, ako ste dovoljno hrabri da ih koristite.Novi URL koji će se koristiti umesto %1$s, za ponovno upisivanje. Bez prateće /, molim vas. Primer: %2$s.Strane se ne podudaraju! Vremenske oznake (timestamps) se razlikuju, ili nisu pronađene!Pravila za ponovni upis, koja zahteva ovaj dodatak, su izmenjena, ili nedostaju.Vremenske oznake (timestamps) na obe strane se podudaraju!Ne postoje najbolja podešenja za sakupljanje smeća, ali evo nekoliko scenarija. Sakupljanje smeća je odvojeno od drugih akcija koje brišu keširane fajlove, kao što je ostavljanje komentara, ili objavljivanje objave.Ovi CNAME zapisi će se koristiti umesto %1$s, za ponovno upisivanje (uz gornji spoljašnji URL). Koristite zapetu kao razdvajač. Za strane sa velikim brojem statičkih fajlova, ovo može poboljšati performanse pregledača. Takođe, možda treba konfigurisati CNAME zapise na vašem CDN-u.
    Primer: %2$sStvari koje možete uraditi:Ovo je, striktno, samo jedno napredno svojstvo, i potrebno je poznavanje i PHP i WordPress akcija, da bi se ona kreirala.Ovo će keširati svaku objavljenu objavu, ili stranu, na vašem sajtu. Napraviće superkeš statične fajlove, tako da će nepoznati posetioci (uključujući i botove) pogoditi keširanu stranu. Ovo će vam verovatno pomoći kod Google rangiranja, pošto oni sada koriste brzinu kao meru, kada sude o web sajtovima.Ovo se neće odraziti na obične korisnike, ali mobilni korisnici će videti nekeširane strane.Tajmer:Da bi servirao statičke html fajlove, vaš server mora imati ispravna mod_rewrite pravila, dodata u fajl pod nazivom %s.htaccessPreviše keširanih fajlova, nije moguć prikaz listePotrebna je provera prateće kose crte.URINa žalost, WordPress ne može da pronađe fajl wp-cron.php. Ova skripta je potrebna za pravilno funkcionisanje sakupljanja smeća od strane ovog dodatka, WordPress zakazanih objava, i drugih kritičnih aktivnosti.Na žalost, pravila za ponovni upis ne mogu da se ažuriraju automatski, kada se koristi WordPress MU. Molim vas, otvorite .htaccess i dodajte sledeća mod_rewrite pravila, iznad svih drugih pravila u tom fajlu.De-instalirati ovaj dodatak na strani sa dodacima (plugins). On će automatski počistiti za sobom. Ako je potrebna manuelna intervencija, obezbedeđene su jednostavne instrukcije.AžuriratiAžurirati direktne straneAžurirati Mod_Rewrite pravilaAžurirati podešenjaAžurirati statusKoristiti PHP za serviranje keš fajlova.Koristiti mod_rewrite za serviranje keš fajlova.Koristiti objektni keš (object cache) za čuvaje keširanih fajlova.Koristite planere Tajmer (Timer) ili Sat (Clock), da definišete kada sakupljač smeća treba da se pokrene.Koristite sistem za otklanjanje grešaka u gornjoj kartici Otklanjanje grešaka (Debug). On će vam reći šta dodatak radi.Pregledati Mod_Rewrite pravilaWP Super Cache podešenjaWP Super Cache je proverio prvu stranu vašeg bloga. Molim vas, posetite %s, ako želite da ovo isključite.WP Super Cache je isključen. Molim vas, idite na stranu za administraciju dodataka, da omogućite keširanje.U vašem %s.htaccess fajlu su pronađena WP Super Cache mod rewrite pravila.
    Kliknite na sledeći link da vidite linije koje su dodate u taj fajl. Ako ste unapredili dodatak, postarajte se da se ova pravila poklapaju.WP Super Cache mora biti konfigurisan. Idite na stranu za administraciju, da uključite i konfigurišete ovaj dodatak.WP-CacheWP-Super-CacheWPTouchPronađen je dodatak WPTouch! Molim vas, idite na stranu Supercache dodataka i uključite pomoćni dodatak za WPTouch.Podrška za WPTouch je sada %sUpozorenjeUpozorenje!Pažnja! u %s je moguć upis podataka!Upozorenje! 304 keširanje od strane pregledača je podržano samo kada se ne koristi mod_rewrite keširanje.Upozorenje! PRELOAD MODE (mod za učitavanje unapred) je aktiviran. Superkeš fajlovi se neće brisati, nevezano za starost.Upozorenje! Kompresija je isključena, jer nije pronađena funkcija gzencode().Upozorenje! Sakupljanje smeća nije zakazano!Upozorenje! Uključen je PHP siguran način rada (safe mode)!Upozorenje! WP Super Cache keširanje je neispravno! Skriptin fajl advanced-cache.php nije mogao da učita wp-cache-phase1.php.

    Molim vas, uredite %1$s/advanced-cache.php fajl i postarajte se da putanja ka %2$swp-cache-phase1.php fajlu bude ispravna.Upozorenje! Vaše host ime "%s" ukazuje na %sPronađen je WordPress MUWordPress je zaključan. Super Cache statički fajlovi se neće brisati kada se postave novi komentari.WordPress nije zaključan. Novi komentari će osvežavati Super Cache statičke fajlove, kao i obično.Moguć upis podataka:Možete definisati različite CDN URL-ove za svaki sajt iz mreže višestrukih sajtova.Možete sami urediti fajl, dodajte sledeća pravila.Možete videti gde pravila idu, i ispitati kompletna pravila, klikom na donji link "Pregledati mod_rewrite pravila (View mod_rewrite rules)".Možete imati problema pri radu sa ovim dodatkom, jer je uključen SIGURAN MOD (safe mode).Da bi automatsko ažuriranje funkcionisalo, morate imati BEGIN i END markere u %s.htaccess fajlu. Oni izgledaju ovako, i okružuju glavna WordPress mod_rewrite pravila:Morate omogućiti upis podataka u %s, da biste omogućili ovo svojstvo. Pošto je to sigurnosni rizik, molim vas da ponovo onemogućite upis podataka u fajl, nakon što se vaša strana generiše.Vi, ili administrator, možda možete učiniti da proradi, menjanjući grupnog vlasnika skripti tako da se poklopi sa korisnikom web servera. Grupni vlasnik direktorijuma %s/cache/ takođe mora da se promeni. Za još detalja pogledajte stranu sa uputstvom za siguran mod.Vi, ili administrator, morate isključiti ovo. Za dalje informacije pogledajte stranu sa uputstvom za siguran mod. Na žalost, ovo se ne može isključiti u fajlu .htaccess. To se mora uraditi u konfiguracionom fajlu php.ini.Trebalo bi da na %s promenite dozvole, i učinite ih restriktivnijim. Da popravite stvari, upotrebite vaš ftp klijent, ili sledeću naredbu:Trebalo bi da proverite ima li grešaka na strani 1 i strani 2, gore. Konfiguracija vašeg lokalnog servera možda ne dozvoljava vašem web sajtu da pristupa sam sebi.U vaš %s.htaccess fajl nije omogućen upis podataka od strane web servera, a on se mora ažurirati sa neophodnim mod_rewrite pravilima. Nova pravila dolaze iznad uobičajenih WordPress pravila, kao što je prikazano u donjem kodu:Vaš WP-Cache konfiguracioni fajl (%s) je star i web server ne može da vrši upis u njega. Molim vas, obrišite ga i osvežite ovu stranu.Vaš keš direktorijum (%1$s) ne postoji, i nije mogao da bude kreiran od strane web servera. Proverite %1$-ove dozvole.Upis u vaš keš direktorijum (%1$s), ili %2$s, mora da bude omogućen da bi ovaj dodatak funkcionisao. Proverite ga dva puta.Vaš komentar čeka moderaciju.Vaš server je podešen tako da proverava vlasnika PHP skripti, pre nego im dozvoli da čitaju i upisuju podatke u fajlove.Vaš server "misli" da vaše host ime ukazuje na %s. Neki servisi, poput sakupljanja smeća od strane ovog dodatka, i WordPress zakazanih objava, možda ne funkcionišu ispravno.Vaš web sajt verovatno koristi dosta statičnih fajlova. Slikovni, Javascript i CSS fajlovi su obično statični fajlovi koji lako mogu da se "povlače" sa drugog sajta, ili CDN-a. Iz tog razloga ovaj WordPress dodatak zamenjuje sve linkove u wp-content i wp-includes direktorijumima (izuzev PHP fajlova) vašeg sajta, URL-om koji dajete dole. Na taj način možete, ili kopirati sav statičan sadržaj na poseban hosting server, ili "preslikati" (mirror) fajlove na CDN, pomoću origin pull-a.Zlib izlazna kompresija je uključena![%1$s] %2$d objava je osveženo[%1$s] Učitavanje keša unapred je počelo[%1$s] Učitavanje keša unapred je zaustavljeno[%1$s] Osvežavanje %2$s taksonomije od %3$d do %4$d[%1$s] Osvežavanje objava od %2$d do %3$d[%1$s] WP Super Cache izveštaj o sakupljanju smeća (GC Report)[%s] Učitavanje keša unapred je završeno[%s] Provera prve strane![%s] Prva strana je gzip-ovana! Keš je obrisan![%s] Prva strana je gzip-ovana! Molim vas, obrišite keš![%s] Prva strana nije ispravna! Keš je obrisan![%s] Prva strana nije ispravna! Molim vas, obrišite keš![%s] Učitavanje unapred je možda zastalo.sveisključenouključenosekundiY-m-d (G-m-d) G:i:slanguages/wp-super-cache-lt_LT.po000066600000215354152133035240012725 0ustar00# Translation of the WordPress plugin by . # Copyright (C) 2010 # This file is distributed under the same license as the package. # FIRST AUTHOR , 2010. # msgid "" msgstr "" "Project-Id-Version: WP Super Cache\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2010-09-27 13:58+0000\n" "PO-Revision-Date: 2011-07-30 20:42+0200\n" "Last-Translator: Natalija Strazdauskienė \n" "Language-Team: Nata Strazda \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Lithuanian\n" "X-Poedit-Country: LITHUANIA\n" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Jūsų komentaras laukia patvirtinimo." #: plugins/awaitingmoderation.php:23 #: plugins/awaitingmoderation.php:38 #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:47 #: plugins/domain-mapping.php:62 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1114 msgid "Disable" msgstr "Išjungti" #: plugins/awaitingmoderation.php:29 #: plugins/badbehaviour.php:55 #: plugins/domain-mapping.php:53 #: plugins/searchengine.php:67 msgid "disabled" msgstr "išjungtas" #: plugins/awaitingmoderation.php:31 #: plugins/badbehaviour.php:57 #: plugins/domain-mapping.php:55 #: plugins/searchengine.php:69 #: wp-cache.php:1460 msgid "enabled" msgstr "įjungtas" #: plugins/awaitingmoderation.php:33 #, php-format msgid "Awaiting Moderation plugin is %s" msgstr "Laukiamas patvirtinimo įskiepis yra %s" #: plugins/awaitingmoderation.php:34 msgid "(Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment.) " msgstr "(Pašalinti tekstą \"Jūsų komentaras laukia patvirtinimo.\", kai kas nors palieka komentarą peržiūrai.)" #: plugins/awaitingmoderation.php:36 #: plugins/badbehaviour.php:63 #: plugins/domain-mapping.php:60 #: plugins/searchengine.php:74 #: wp-cache.php:1114 msgid "Enable" msgstr "Įjungti" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "Bad Behaviour nerasta. Prašome patikrinti jūsų įdiegimą." #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s." msgstr "Bad Behaviour parama yra %s." #: plugins/badbehaviour.php:61 #, php-format msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Šis įskiepis funkcionuos tik vidutinio talpinimo režimu, atjunkite suspaudimą ir įdiekite įskiepį Bad Behavior \"%s/plugins/blogas-elgesio/\")" #: plugins/badbehaviour.php:69 #: wp-cache.php:1191 #: wp-cache.php:1193 msgid "Warning!" msgstr "Dėmesio!" #: plugins/domain-mapping.php:57 #, php-format msgid "Domain Mapping support plugin is %s" msgstr "Domain Mapping įskiepio palaikymas yra is %s" #: plugins/domain-mapping.php:58 msgid "(support for multiple domains on multisite websites) " msgstr "(palaiko daugybinius domenus ir daugybines svetaines)" #: plugins/domain-mapping.php:72 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Domain Mapping įskiepis aptiktas! Prašome grįžti į įskiepių Supercache puslapį ir įjungti domeno žemėlapių padėjėjo įskiepį." #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s." msgstr "No Adverts for Friends įskiepis yra %s." #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(reikalingas friendsadverts.php taip pat) " #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Prašome sukurti %s /wp-cache-config.php iš wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:138 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Įspėjimas! PHP Saugus režymas įjungtas!" #: wp-cache.php:139 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Jums gali kilti problemų naudojant šį įskiepį, nes Safe Mode yra įjungtas." #: wp-cache.php:143 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Jūsų serveris patikrins PHP skriptų savininką, prieš leidžiant jiems skaityti ir rašyti failus." #: wp-cache.php:144 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Jūs arba administratorius galite padaryti jį dirbantį, keisdami įskiepio skriptų grupės savininką, kad atitiktų žiniatinklio serverio vartotoją. %s/cache/ katalogas taip pat turi būti pakeistas. Žiūrėti saugaus rėžimo puslapį dėl papildomos informacijos." #: wp-cache.php:146 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Jūs arba administratorius turite atjungti tai. Žiūrėkite saugaus rėžimo puslapį dėl papildomos informacijos. Dėja, tai negali būti atjungta .htaccess faile. Tam reikia papildyti php.ini konfiguracijos failą." #: wp-cache.php:152 msgid "Permlink Structure Error" msgstr "Nuolatinės nuorodos struktūra" #: wp-cache.php:153 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Teisingui įskiepio darbui reikalingas korektiškas url ar pastovios nuorodos struktūros nustatymas.. Prašome eiti į Pastovių nuorodų puslapį, kad sukonfiguruoti pastovias nuorodas." #: wp-cache.php:165 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Įspėjimas! Jūsų prieglobos vardas \"%s\" atsako %s" #: wp-cache.php:166 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Jūsų serveris galvoja, jog jūsų prieglobos vardas pasikeitė į %s. Kai kurie servisai, kaip pavyzdžiui, šiukšlių surinkimas šiame įskiepyje ir WordPress planuojamuose žinutėse gali neveikti tinkamai." #: wp-cache.php:167 #: wp-cache.php:181 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Prašau žiūrėti 16 eilutę problemų sekcijoje readme.txt" #: wp-cache.php:180 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Dėja, WordPress negali rasti wp-cron.php failą. Šis skriptas reikalingas korektiškam šiukšlynės išvalymo operacijos rodymui šiam įskiepiui, WordPress reguliariose žinutėse bei kitose svarbiose vietose." #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "Negalima tęsti...ištaisykite bųvusias problemas ir pabandykite iš naujo." #: wp-cache.php:204 msgid "Zlib Output Compression Enabled!" msgstr "Zlib Išėjimo suspaudimas įjungtas!" #: wp-cache.php:205 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP naudoja duomenų suspaudimą dėl jūsų svetainės lankytojų puslapių atvaizdavimui. Šios parinkties atjungimas yra rekomenduojamas, kad išvengti daugkartinio puslapių suspaudimo su įskiepiu. Taipogi žiūrėkite #21 Problemų sekcijoje. Žiūrėkite šį puslapį, kad sekti instrukcijas modifikuotame jūsų php.ini." #: wp-cache.php:209 msgid "Mod rewrite may not be installed!" msgstr "Mod rewrite negali būti įdiegtas!" #: wp-cache.php:210 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Įvyko klaida, susijusi su tuo, kad modulis mod_rewrite neegzistuoja arba nėra įdiegtas. Prašome patikrinti modulio mod_rewrite serverio konfiguracijoje. Modulis reikalingas korektiškam įskiepio darbui su statistiniais failais. Be prijungto mod_rewrite jūs galite naudoti tik režimus su PHP palaikymu arba vidutinį talpinimą." #: wp-cache.php:215 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Tik skaitymo režimas. Konfigūracija negali būti pakeista." #: wp-cache.php:216 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "Konfiguracijos įskiepio failas WP Super Cache %s/wp-cache-config.php negali būti pakeistas. Kad tęsti, jūs turite nustatyti rašymo teises." #: wp-cache.php:217 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Paparsčiausias būdas tai išspręsti - pakeisti prieigos teises, naudojant CHMOD, per FTP-klientą. Pakanka nustatyti globalias teises rašymui." #: wp-cache.php:218 msgid "Writeable:" msgstr "Įrašomieji:" #: wp-cache.php:219 msgid "Readonly:" msgstr "Tik skaitymui:" #: wp-cache.php:231 #, php-format msgid "Warning! %s is writeable!" msgstr "Įspėjimas! %s yra įrašomas!" #: wp-cache.php:232 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Jums reikia pakeisti teises %s, ir padaryti jį labiau ribojamu. Naudokite savo FTP klientą arba šią komandą:" #: wp-cache.php:240 msgid "Mobile rewrite rules detected" msgstr "Mobiliai perrašytų taisyklių pažeidimai" #: wp-cache.php:241 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Geriausiu atvėju turėtumėte įjungti \"Mobiliojo prietaiso parama\" arba ištrinti .htaccess mobiliojo perrašymo taisykles. Ieškoti 2 eilutę su tekstu \"2.0\\MMP|240x320\" ir ištrinti." #: wp-cache.php:241 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Tai nedaro jokios įtakos paprastiems vartotojams, tačiau mobiliojo ryšio vartotojai galės matyti netalpinamus puslapius." #: wp-cache.php:247 #: wp-cache.php:258 msgid "Rewrite rules must be updated" msgstr "Perrašomos taisyklės turi būti atnaujinamos" #: wp-cache.php:248 #: wp-cache.php:259 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Šis įskiepis reikalauja perrašomų taisyklių pasikeitimą arba jų nėra." #: wp-cache.php:249 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Mobilusis palaikymas reikalauja papildomų taisyklių jūsų .htaccess faile arba galite nustatyti įjungtu režimą. Čia yra jūsų parinktys (sudėtingumo tvarka):" #: wp-cache.php:250 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Nustatykite vidutinio talpynimo režimu ir kad būtų mobiliojo ryšio palaikymas." #: wp-cache.php:251 #: wp-cache.php:260 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Slinkite žemyn puslapį Išplėstiniai nustatymai ir spustelėkite mygtuką Atnaujinti mod_rewrite taisykles." #: wp-cache.php:252 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Ištrinti įskiepio mod_rewrite taisykles %s.htaccess tarp # BEGIN WPSuperCache ir # END WPSuperCache ir tegul įskiepis regeneruoja juos kraunantis puslapiui." #: wp-cache.php:253 #, php-format msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Pridėkite taisykles patys. Redaguoti %s.htaccess ir rasti kodo bloką tarp # BEGIN WPSuperCache ir # END WPSuperCache . Yra du skyriai, kurie atrodo labai panašiai. Tiesiog žemiau linijos %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ pridėkite šias eilutes: (tai padaryti du kartus, vieną kartą kiekviename skyriuje)" #: wp-cache.php:266 msgid "Required to serve compressed supercache files properly." msgstr "Reikalaujama tinkamai suspaustiems supercache failams." #: wp-cache.php:266 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Privalo nustatyti talpyklos informaciją supercache puslapiuose. IE7 vartotojai be šio modulio matys senus puslapius." #: wp-cache.php:266 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Nustatyti galiojimo supercached puslapių pabaigos datą. Lankytojai nematys naujų puslapių, kai jie atsinaujins ar palikti komentarus be šio modulio." #: wp-cache.php:273 msgid "Missing Apache Modules" msgstr "Trūksta Apache modulių" #: wp-cache.php:274 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Trūksta šių Apache modulių. Įskiepis dirbs vidutiniu režimu be jų. Pilnu Supercache režimu jūsų lankytojai gali pamatyti sugadintus puslapius ar pasibaigusios datos turinį." #: wp-cache.php:413 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Įspėjimas! Jūs bandėte įjungti suspaudimą, bet zlib.output_compression zlib.output_compression yra įjungtas . Žr. #21 skyrių \"Problemų diagnostika\" readme failą." #: wp-cache.php:501 msgid "WP Super Cache Settings" msgstr "WP Super talpyklos nustatymai" #: wp-cache.php:512 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Pranešimas: mod_rewrite arba vidutinės talpyklos įjungimas. Rodyti išplėstinius nustatymų puslapį pagal nutylėjimą." #: wp-cache.php:523 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Konfigūracijos failas pakeistas, kai kurios reikšmės gali būti klaidingos. Pakraukite puslapį iš naujo iš \"Nustatymai \" meniu, kad tai ištaisyti." #: wp-cache.php:540 #: wp-cache.php:614 msgid "Caching must be enabled to use this feature" msgstr "Talpykla turi būti įjungta jei norite naudoti šią funkciją" #: wp-cache.php:542 msgid "Cache Tester" msgstr "Talpyklos patikra" #: wp-cache.php:543 msgid "Test your cached website by clicking the test button below." msgstr "Pasitikrinkite savo išsaugotą svetainę, paspaudę žemiau esantį mygtuką testavimui." #: wp-cache.php:550 #, php-format msgid "Fetching %s to prime cache: " msgstr "Patikra %s svarbiausios talpyklos:" #: wp-cache.php:552 #: wp-cache.php:559 #: wp-cache.php:566 msgid "OK" msgstr "OK" #: wp-cache.php:557 #, php-format msgid "Fetching first copy of %s: " msgstr "Pirmosios kopijos %s patikra:" #: wp-cache.php:564 #, php-format msgid "Fetching second copy of %s: " msgstr "Antrosios kopijos %s patikra:" #: wp-cache.php:570 msgid "One or more page requests failed:" msgstr "Viena ar daugiau puslapio užklausų nepavyko:" #: wp-cache.php:589 #: wp-cache.php:590 #, php-format msgid "Page %d: %d (%s)" msgstr "Puslapis %d:%d (%s)" #: wp-cache.php:596 #, php-format msgid "Page 1: %s" msgstr "Puslapis 1: %s" #: wp-cache.php:597 #, php-format msgid "Page 2: %s" msgstr "Puslapis 2: %s" #: wp-cache.php:598 msgid "The timestamps on both pages match!" msgstr "Laikini abiejų puslpių štampai sutampa!" #: wp-cache.php:600 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Puslapiai nesutampa! Laikinas štampas skiriasi arba nebuvo rastas!" #: wp-cache.php:606 msgid "Send non-secure (non https) request for homepage" msgstr "Išsiųsti neapsaugotą (ne per https) užklausą pagrindiniam puslapiui" #: wp-cache.php:607 msgid "Test Cache" msgstr "Patikrinti" #: wp-cache.php:632 #: wp-cache.php:755 msgid "Cancel Cache Preload" msgstr "Atšaukti bendrąją talpyklą" #: wp-cache.php:638 msgid "Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete." msgstr "Bendroji talpykla pagal tvarkaraštį atjungta. Jeigu darbas yra paleistas, jis nebus uždarytas tol, kol einamosios 100 puslapių nebus talpykloje." #: wp-cache.php:649 msgid "Scheduled preloading of cache cancelled." msgstr "Bendroji talpykla pagal tvarkaraštį atjungta." #: wp-cache.php:675 #: wp-cache.php:753 msgid "Preload Cache Now" msgstr "Sukūrti bendrąją talpyklą dabar" #: wp-cache.php:678 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Bendroji talpykla pradės darbą po 10 sek." #: wp-cache.php:682 #, php-format msgid "Scheduled preloading of cache in %d minutes" msgstr "Bendroji talpykla pradės veikti po %d min" #: wp-cache.php:686 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Tai bus talpykloje po kiekvieno žinutės ir puslapio patalpinimo jūsų svetainėje. Ji sukurs supercache statinius failus, kad nežinomų lankytojų (įskaitant botų) lankys išsaugotą puslapį. Tai tikriausiai padės Google reitingavimui, nes jie kaip rodiklį naudoja greičio metriką, sprendžiant iš puslapio." #: wp-cache.php:687 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Tačiau, naudojant šio tipo talpyklą sukūriama daug daugiau failų. Rekomenduojama naudoti tokį būdą, jei pas jus labai daug įrašų (10,000+) bloge. Ypač tai svarbu, jeigu jūs naudojatės virtualaus hostingo paslaugomis." #: wp-cache.php:688 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "Režime ’Bendro talpinimo’ planuotas šiukšlių išvalymas ištrins tik talpykloje esančius paprasto tipo įrašus (talpykla iš Super Cache nebus pašalintas). Tai yra rekomenduojama naudojimui." #: wp-cache.php:692 #, php-format msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Atnaujinti bendrą talpyklą kas %s min (įveskite 0, kad atjungti, minimalus min skaičius %d)." #: wp-cache.php:705 msgid "all" msgstr "visi" #: wp-cache.php:718 #, php-format msgid "Preload %s posts." msgstr "Saugoti %s įrašus." #: wp-cache.php:725 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Preliminarus režimas (šiukšlių išvalymas veikia ne pilnai, Rekomenduojama.)" #: wp-cache.php:728 msgid "Send me status emails when files are refreshed." msgstr "Siųsti man statusą elektroniniu paštu, kai failai yra atnaujinami." #: wp-cache.php:733 msgid "Many emails, 2 emails per 100 posts." msgstr "Daug laiškų, 2 laiškai į 100 žinučių." #: wp-cache.php:736 msgid "Medium, 1 email per 100 posts." msgstr "Vidutinis lygis: 1 email į 100 žinučių." #: wp-cache.php:739 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Žemas lygis: 1 e-mail pradžioje ir 1 gale po visų žinučių apkrova." #: wp-cache.php:743 #, php-format msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Talpyklos atnaujinimas po %d val %d min ir %d sek." #: wp-cache.php:744 #, php-format msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Pilnas saugyklos atnaujinimas:%d val %d min ir %d sekundžių." #: wp-cache.php:750 #, php-format msgid "Currently caching from post %d to %d." msgstr "Šiuo metu saugoma iš %d į %d." #: wp-cache.php:753 msgid "Update Settings" msgstr "Atnaujinti nustatymus" #: wp-cache.php:761 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Saugyklos prieškrova atjungta. Prašome įjungti pilną įskiepio darbą arba susisiekite su administratorium." #: wp-cache.php:776 #: wp-cache.php:865 msgid "Caching" msgstr "Saugyklos statusas" #: wp-cache.php:780 msgid "Cache hits to this website for quick access." msgstr "Saugoti svetainės peržiūras greitai prieigai." #: wp-cache.php:780 #: wp-cache.php:781 #: wp-cache.php:795 #: wp-cache.php:799 #: wp-cache.php:802 #: wp-cache.php:803 #: wp-cache.php:868 msgid "Recommended" msgstr "Rekomenduojama" #: wp-cache.php:781 msgid "Use mod_rewrite to serve cache files." msgstr "Naudoti mod_rewrite talpyklos failų aptarnavimui." #: wp-cache.php:782 msgid "Use PHP to serve cache files." msgstr "Naudokite PHP talpyklos failų aptarnavimui." #: wp-cache.php:783 msgid "Legacy page caching." msgstr "Supaprastintas saugojimas." #: wp-cache.php:784 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching." msgstr "Naudojimas mod_rewrite padės paspartinti blogo darbą, negu PHP (nors šis variantas irgi ne toks lėtas). Šis režimas paprastesnis ir patogesnis, bet pradedančiajam geriau naudoti saugojamą PHP." #: wp-cache.php:790 msgid "Miscellaneous" msgstr "Įvairūs" #: wp-cache.php:795 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Suspausti puslapius, kad paspartinti darbą." #: wp-cache.php:796 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Suspaudimas yra išjungtas pagal nutylėjimą, nes kai kurie hostingai turi problemų su suspaustais failais. Perjungimas tarp įjungimo ir išjungimo išvalo talpyklą." #: wp-cache.php:799 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Ne modifikuota naršyklės talpykla. Nurodoma, kai puslapis nebuvo pakeistas nuo paskutinio užklausimo." #: wp-cache.php:800 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "304 palaikymas yra išjungtas pagal nutylėjimą, nes pastaruoju metu GoDaddy turėjo problemų su kai kuriom naudojamom antraštėm." #: wp-cache.php:802 msgid "Don’t cache pages for known users." msgstr "Negalima saugoti puslapių žinomiems vartotojams." #: wp-cache.php:803 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Talpykla atstatyta. Pateikti talpyklos failai anoniminiams vartotojams, kol naujas failas yra generuojamas." #: wp-cache.php:804 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Papasakoti visiems, kad naudojatės įskiepiu (pranešimas bus patalpintas blogo poraštėje)." #: wp-cache.php:810 #: wp-cache.php:957 #: wp-cache.php:1473 msgid "Advanced" msgstr "Išplėstinė" #: wp-cache.php:814 msgid "Mobile device support." msgstr "Mobiliojo prietaiso palaikymas." #: wp-cache.php:815 msgid "Clear all cache files when a post or page is published." msgstr "Išvalyti visus talpyklos failus, kai skelbiama žinutė ar puslapis." #: wp-cache.php:816 msgid "Only refresh current page when comments made." msgstr "Tik atnaujinti dabartinį puslapį, kai atsiranda nauji komentarai." #: wp-cache.php:817 msgid "List the newest cached pages on this page." msgstr "Sąrašas naujausių talpyklos puslapių šiame puslapyje." #: wp-cache.php:819 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Failų blokiravimas. Jms tikriausiai nereikia, tačiau ji gali padėti, jei jūsų serveris yra silpnas. Įspėjimas! Gali sukelti jūsų serverio užrakinimą labai retais atvejais!" #: wp-cache.php:822 msgid "Use object cache to store cached files." msgstr "Naudokite objekto talpyklą talpyklos failams saugoti." #: wp-cache.php:822 msgid "(Experimental)" msgstr "(Eksperimentinis)" #: wp-cache.php:829 msgid "Note:" msgstr "Pastaba:" #: wp-cache.php:831 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "Jeigu pašalinti šį įskiepį, įsitikinkite, kad katalogo %s yra įrašomi serveryje, todėl advanced-cache.php ir cache-config.php failai gali būti ištrinti automatiškai . (Įsitikinkite, kad tie failai yra įrašomi!)" #: wp-cache.php:832 #, php-format msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Prašome žiūrėti readme.txt instrukcijas, kaip pašalinti šį scenarijų . Ieškoti pozicijoje, \"Kaip pašalinti WP Super Cache\"." #: wp-cache.php:833 #, php-format msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Reikia pagalbos? Patikrinkite Super Cache failą readme . Jis apima įdiegimo dokumentaciją, DUK ir trikčių diagnostikos patarimų. Palaikymo forumas. Į jūsų klausimą galbūt jau buvo atsakyta." #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "Atnaujinti statusą" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "Priimami failų pavadinimai & Atmesti URI" #: wp-cache.php:868 msgid "Caching On" msgstr "Talpykla įjungta" #: wp-cache.php:869 msgid "Caching Off" msgstr "Talpykla išjungta" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Pastaba: leidžia įjungti PHP talpinimą ir judriojo ryšio palaikymą" #: wp-cache.php:880 msgid "Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Pastaba: Supercache mod_rewrite taisyklių aptikimas. Talpykliniai failai bus aptarnaujami naudojant šias taisykles. Redaguoti .htaccess failą jūsų pirminėje direktorijoje ir pašalinti SuperCache taisykles." #: wp-cache.php:892 msgid "Make WordPress Faster" msgstr "Padaryti WordPress spartesniu" #: wp-cache.php:893 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s sukurtas ir palaikomas %2$s ir daugelis kitų." #: wp-cache.php:894 #, php-format msgid "He blogs at %1$s and posts photos at %2$s." msgstr "Apsilankykite įskiepio autoriaus bloge %1$s ir publikuokite nuotraukas %2$s." #: wp-cache.php:895 #, php-format msgid "Please say hi to him on %s too!" msgstr "Prašome aplankyti ir autoriaus %s!" #: wp-cache.php:903 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Puslapių talpykloje %1$s : %2$s" #: wp-cache.php:904 msgid "Newest Cached Pages:" msgstr "Nauji talpyklos puslapiai:" #: wp-cache.php:908 #, php-format msgid "Cached %s seconds ago" msgstr "Įdėta į talpyklą prieš %s sek" #: wp-cache.php:911 msgid "(may not always be accurate on busy sites)" msgstr "(sąrašas nerekomenduojamas didelioms svetainėms)" #: wp-cache.php:930 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Talpyklos įskiepiai yra PHP skriptai, kurie gyvena įskiepio aplanko viduje wp-super-cache aplanke. Jie pakraunami, kai pasikrauna Supercache, daug greičiau nei reguliarūs WordPress įskiepiai." #: wp-cache.php:931 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Šiai parinkčiai naudoti reikalingi PHP ir WordPress žinios." #: wp-cache.php:941 msgid "Available Plugins" msgstr "Turimi įskiepiai" #: wp-cache.php:957 msgid "Easy" msgstr "Lengvas" #: wp-cache.php:957 msgid "Tester & Contents" msgstr "Testeris & Turinys" #: wp-cache.php:957 msgid "Preload" msgstr "Prieškrūvis" #: wp-cache.php:957 msgid "Plugins" msgstr "Įskiepiai" #: wp-cache.php:957 msgid "Debug" msgstr "Derinimas" #: wp-cache.php:984 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Pastaba: taisylių WP Super Cache mod_rewrite tikrinimas atjungtas, kol nebus paleistas pagrindiniame bloge." #: wp-cache.php:986 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Pastaba: Taisyklių WP Super Cache mod_rewrite tikrinimas atjungtas, kol nebus paleistas pagrindiniame bloge." #: wp-cache.php:996 msgid "Mod Rewrite Rules" msgstr "Mod Rewrite taisyklės" #: wp-cache.php:1002 msgid "WordPress MU Detected" msgstr "WordPress MU aptiktas" #: wp-cache.php:1002 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Dėja, mod_rewrite negalima atnaujinti auto režimu WordPress MU. Jums teks rankiniu būdu tai atlikti: atidarykite failą .htaccess ir įterpkite sekančią taisyklę." #: wp-cache.php:1004 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Rewrite taisyklės negali būti atnaujintos!" #: wp-cache.php:1005 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Korektiškam darbui jūsų %s.htaccess faile turi būti įrašyti BEGIN ir END. Tarp jų randasi pagrindinės WordPress mod_rewrite taisyklės, pvz.:" #: wp-cache.php:1007 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Atnaujinkite puslapį po to, kai atredaguosite .htaccess failą." #: wp-cache.php:1011 msgid "Thank you for upgrading." msgstr "Dėkojame už modernizaciją." #: wp-cache.php:1011 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Po paskutinio įskiepio atnaujinimo mod_rewrite taisyklės buvo pakeistos. Dėja, jums teks rankiniu būdu pašalinti senas taisykles. Atnaujinkite puslapį, kai baigsite redagavimą .htaccess failo. Jeigu norite atnaujinti viską patys, tuomet pakeiskite sekančią eilutę: %1$s į šią: %2$s . Vienintelis skirtumas - tai pakeitimas \"HTTP_COOKIE\" į \"HTTP:Cookie\" ir \"wordpressuser\" į \"wordpress\". Šie pakeitimai susiję su nauja WordPress 2.5 versija. " #: wp-cache.php:1015 msgid "Trailing slash check required." msgstr "Reikalinga trailing slash patikra." #: wp-cache.php:1015 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Rodos, visos jūsų blogo nuorodos baigiasi simboliu \"/\". Dėja, kai tik jūs įdiegėte įskiepį, suveikė funkcija, radusi nuorodų kopijas be \"/\" gale, ir dabar negali perkelti teisingu adresu. Problemą pašalinti padėsfailo .htaccess redagavimas ir 2 naujų taisyklių įterpimas prie pagrindinių Supercache įskiepio taisyklių:" #: wp-cache.php:1017 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Kad pamatyti pilną veikiančių taisyklių sąrašą, paspauskite mygtuką \"Pažiūrėti mod_rewrite taisykles\"." #: wp-cache.php:1031 msgid "Mod Rewrite rules updated!" msgstr "Mod_rewrite taisyklės atnaujintos!" #: wp-cache.php:1032 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "failas %s.htaccess buvo sėkmingai atnaujintas, reikalingos mod_rewrite taisyklės pridėtos. Prašome patikrinti jas. Jos turi atrodyti taip:" #: wp-cache.php:1034 msgid "Mod Rewrite rules must be updated!" msgstr "Taisyklės mod_rewrite turi būti atnaujintos!" #: wp-cache.php:1035 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "Jūsų failas %s.htaccess nepasiekiamas įrašymui (serverio nustatymuose) ir negali būti atnaujintas auto režimu. Jūs turite rankiniu būdu pridėti naujas taisykles prie pagrindinių WordPress taip, kaip nurodyta žemiau:" #: wp-cache.php:1040 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "Taisyklės mod_rewrite įskiepiui WP Super Cache buvo aptiktos faile %s.htaccess.
    Paspauskite mygtuką, kad peržiūrėti eilutes. Jeigu jūs ką tik atnaujinote įskiepį, patikrinkite visas taisykles." #: wp-cache.php:1043 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "Tarp taisyklių jūsų faile .htaccess ir taisyklių pačio įskiepio rasti nesutapimai. Tai gali būti papildomas simbolis eilutėje, bet jūs patys turite sulyginti originalias taisykles su savo kuo greičiau. Paspauskite mygtuką ’Atnaujinti Mod_Rewrite taisykles’, kad padaryti tai ato režimu." #: wp-cache.php:1046 msgid "View Mod_Rewrite Rules" msgstr "Žiūrėti mod_rewrite taisykles" #: wp-cache.php:1050 #: wp-cache.php:2287 #, php-format msgid "Rules must be added to %s too:" msgstr "Taisyklės taip pat bus įterptos į %s:" #: wp-cache.php:1058 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Gzip-suspaudimo taisyklės patalpintos į %s.htaccess." #: wp-cache.php:1065 msgid "Fix Configuration" msgstr "Nustatyti konfigūravimą" #: wp-cache.php:1068 msgid "Restore Default Configuration" msgstr "Atkurti numatytąją konfigūraciją." #: wp-cache.php:1076 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Komentarų tikrinimas įjungtas. Po kiek laiko jūsų komentarai bus apublikuoti." #: wp-cache.php:1101 msgid "Lock Down:" msgstr "Uždaras režimas:" #: wp-cache.php:1101 msgid "Disabled" msgstr "Atjungta" #: wp-cache.php:1101 msgid "Enabled" msgstr "Įjungta" #: wp-cache.php:1102 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Paruoškite savo blogą planuojamiems dideliems apsilankymų skaičiams, aktyvuojant šį režimą. Aktyvioje būsenoje naujų komentarų ir žinučių talpinimas neatnaujins talpykloje statinių failų." #: wp-cache.php:1103 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Programuotojams: Padarykite savo įskiepį uždarytu režimu ir suderintu su mūsų įskiepiu, įterpus \"WPLOCKDOWN\". Žemiau esantis kodas padės jums adaptuoti įskiepį prie mūsų." #: wp-cache.php:1105 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Atsiprašome. Mano blogas laikinai nedirba. Užeikite vėliau" #: wp-cache.php:1109 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress nenaudoja saugaus režimo. Nauji komentarai neatnaujina visus talpyklos elementus." #: wp-cache.php:1111 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress nenaudoja saugaus režimo. Nauji komentarai atnaujina visus talpyklos elementus." #: wp-cache.php:1117 msgid "Lock Down" msgstr "Uždaras režimas" #: wp-cache.php:1125 msgid "Directly Cached Files" msgstr "Tiesioginis failų saugojimas" #: wp-cache.php:1183 #, php-format msgid "%s removed!" msgstr "%s pašalintas!" #: wp-cache.php:1191 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Jūs turite nustatyti teises į %s įrašomais, kad įjungti šią funkciją. Tačiau tai potenciali rizika. Po puslapio atnaujinimo grąžinkite teises." #: wp-cache.php:1193 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s įrašomas. Prašome pakeisti teises į \"Ti skaitymui\" jūsų blogo saugumui." #: wp-cache.php:1207 msgid "Existing direct page" msgstr "Esamas tiesioginis puslapis" #: wp-cache.php:1207 msgid "Delete cached file" msgstr "Ištrinti talpyklos failą" #: wp-cache.php:1212 msgid "Add direct page:" msgstr "Pridėti tiesioginį puslapį:" #: wp-cache.php:1214 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Toks saugojimas sukuriamas tiesiogiai iš katalogo %s. Ši parinktis naudinga tuomet, kai laukiamas lankytojų antplūdis iš populeresnio blogo į jūsų blogo konkrečią žinutę ar puslapį." #: wp-cache.php:1216 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "Pavyzdžiui: kad patalpinti puslapį %1$sabout/ į talpyklą, reikia įrašyti %1$sabout/ arba /about/. Puslapis bus išsaugotas iš karto, kai pirmą kartą jis aplankytas." #: wp-cache.php:1217 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Kad pašalinti puslapį iš tokios talpyklos, išvalykite tekstinį laukelį ir pašalinkite talpyklą." #: wp-cache.php:1222 msgid "Update Direct Pages" msgstr "Atnaujinti puslapius" #: wp-cache.php:1260 msgid "Expiry Time & Garbage Collection" msgstr "Pasibaigęs laikas & Šiukšlių valymas" #: wp-cache.php:1262 msgid "Expire time:" msgstr "Baigiasi laikas:" #: wp-cache.php:1263 msgid "seconds" msgstr "sekundžių" #: wp-cache.php:1264 msgid "Garbage Collection" msgstr "Šiukšlių valymas" #: wp-cache.php:1264 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "Jeigu taupyklos aktualumas daugiau nei 1800 sek (pusė valandos), tuomet šiukšlių šalinimas bus vykdomas kas 10 min." #: wp-cache.php:1265 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Pasibaigusių failų tikrinimas ir šalinimas užtrunka, bet ir palikti tokius failus sistemoje neverta. Dideliuose bloguose reikia nurodyti \"gyvavimo laiką\" kiekvienos kopijos 300 sek. Jūs galite eksperimentuoti su nustatymais ir pažiūrėti, kiek pasibaigusių puslapių kopijų lieka talpykloje dienos metu. Optimalus tokių puslapių skaičius ne daugiau nei 500. Naudokite saugojimą su mod_rewrite arba PHP, Jūs galėsite padidinti saugomų puslapių skaičių." #: wp-cache.php:1266 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Nustatyti galiojimo laiką į 0 sekundžių, kad išjungti šiukšlių surinkimą." #: wp-cache.php:1267 msgid "Change Expiration" msgstr "Keisti galiojimo pabaigą" #: wp-cache.php:1311 msgid "Rejected User Agents" msgstr "Atmesti botai" #: wp-cache.php:1312 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Kad uždrausti įskiepiui saugoti paieškos ir kitų botų užklausas, įveskite jų pavadinimus į laukelį žemiau. Jeigu puslapio kopija jau egzistuoja Super Cache talpykloje, ji visvien bus nusiųsta botui." #: wp-cache.php:1319 msgid "Save UA Strings" msgstr "Išsaugoti nustatymus" #: wp-cache.php:1342 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Ne saugoti tokių tipų puslapius. Palyginkite su Sąlyginiai tegai dokumentacija, kad sužinoti daugiau." #: wp-cache.php:1345 msgid "Single Posts" msgstr "Tik žinutės" #: wp-cache.php:1346 msgid "Pages" msgstr "Puslapiai" #: wp-cache.php:1347 msgid "Front Page" msgstr "Pagrindinis puslapis" #: wp-cache.php:1348 msgid "Home" msgstr "Pradinis puslapis" #: wp-cache.php:1349 msgid "Archives" msgstr "Archyvai" #: wp-cache.php:1350 msgid "Tags" msgstr "Žymos" #: wp-cache.php:1351 msgid "Category" msgstr "Kategorija" #: wp-cache.php:1352 msgid "Feeds" msgstr "Kanalai" #: wp-cache.php:1353 msgid "Search Pages" msgstr "Paieškos puslapiai" #: wp-cache.php:1355 #: wp-cache.php:1483 msgid "Save" msgstr "Išsaugoti" #: wp-cache.php:1372 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Laukelį žemiau galite užpildyti puslapių adresų fragmentais (arba puslapių grupėmis, pvz. archyvas už metus/mėnesį ir t.t.), kurie nebus saugojami. Įskiepis skanuos puslapių adresus ir ieškos fragmentus, nurodytus žemiau, prieš saugojimą." #: wp-cache.php:1378 msgid "Save Strings" msgstr "Išsaugoti uždraustus fragmentus" #: wp-cache.php:1394 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Laukelį, esantį žemiau, jūs galite užpildyti failų vardais, kurie bus saugojami net tuo atveju, jei pavadinimuose bus draudžiami fragmentai." #: wp-cache.php:1400 msgid "Save Files" msgstr "Išsaugoti failus" #: wp-cache.php:1445 msgid "Currently logging to: " msgstr "Šiuo metu prisijungta prie:" #: wp-cache.php:1455 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Čia galite išspręsti kai kurias problemas, iškylusias darbo su įskiepiu metu, derinimo pagalba. Jūs galite įrašyti logus į failus, esančius talpyklos kataloge." #: wp-cache.php:1456 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Gauti priėimą prie failo logo paprasta, tačiau išvalant talpyklą logas taip pat bus ištrintas." #: wp-cache.php:1460 msgid "Debugging" msgstr "Derinimas" #: wp-cache.php:1461 msgid "Logging Type" msgstr "Įėjimo būdas" #: wp-cache.php:1461 msgid "Email" msgstr "Email" #: wp-cache.php:1462 msgid "file" msgstr "failas" #: wp-cache.php:1463 msgid "IP Address" msgstr "IP adresas" #: wp-cache.php:1463 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(tik logo užklausos iš šio IP. Jūsų IP - %s)" #: wp-cache.php:1464 msgid "Log level" msgstr "Logo lygis" #: wp-cache.php:1470 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = mažiausias, 5 = didžiausias, gali sukelti per didelį krūvį serveriui)" #: wp-cache.php:1473 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "Ypač retais atvėjais bloge gali iškilti dvi problemos:
    1. Vietoj pradinio puslapio vartotojai gali matyti siūlymą įkrauti su ja .zip archyvą
    2. Vietoj pradinio puslapio į talpyklą gali būti įdėtas visiškai kitas (tik tuo atvėju, jeigu blogas naudoja sekančią nuorodų struktūrą /%category%/%postname%/).
    " #: wp-cache.php:1474 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "I’m 99% certain! Kalidos, kurios gali iškilti dirbant su WP Super Cache, nesusijusios su pačiu įskiepiu. Jos atsiranda retais atvėjais, bet jūs galite apsisaugoti, paleidžiant kas 5 min automatinį blogo tikrinimą. Atsiradus klaidai, jums apie tai bus pranešta per email." #: wp-cache.php:1476 msgid "Check front page every 5 minutes." msgstr "Patikrinkite pirmąjį puslapį kas 5 minutes." #: wp-cache.php:1477 msgid "Front page text" msgstr "Pirmo puslapio tekstas" #: wp-cache.php:1477 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Įveskite tekstą, kurį ieškos įskiepis pagrindiniame puslapyje. Jeigu tekstas nebus rastas, tuomet talpykla automatiškai išsivalys. Palikite laukelį tuščią, kad atjungti šią parinktį." #: wp-cache.php:1478 msgid "Clear cache on error." msgstr "Valyti talpyklą klaidos metu." #: wp-cache.php:1479 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Praneškite blogo administratoriui po patikrinimo (naudinga testuojant)." #: wp-cache.php:1493 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Klaida: GZIP suspaudimas įjungtas, atjunkite jį, jeigu norite pajungti wp-cache." #: wp-cache.php:1540 #: wp-cache.php:1702 msgid "Warning" msgstr "Dėmesio" #: wp-cache.php:1540 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "Suspaudimas GZIP įjungtas WordPress nustatymuose, įskiepis nedirbs tol, kol neatjungsite suspaudimą." #: wp-cache.php:1598 #: wp-cache.php:1603 #: wp-cache.php:1635 #: wp-cache.php:1640 #: wp-cache.php:1646 msgid "Error" msgstr "Klaida" #: wp-cache.php:1598 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Katalogas ($cache_path) neegzistuoja ir negali būti sukūrtas serveryje. Patikrinkite %s teises." #: wp-cache.php:1603 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Aplankas (%1$s) arba %2$s turi būti įrašomi, kad šis įskiepis veiktų. Pertikrinkite juos." #: wp-cache.php:1635 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Konfiguracijos WP-Cache failas (%s) negaliojantis ir negali būti įrašomas. Prašome pašalinti jį ir perkrauti puslapį." #: wp-cache.php:1640 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Konfiguracijos failas nerastas ir katalogas %1$s (%2$s) nėra įrašomas į serverį. Patikrinkite teises." #: wp-cache.php:1646 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Failas WP-Cache (%s) nerastas. Patikrinkite jūsų įdiegimą." #: wp-cache.php:1702 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php neegzistuoja arba negali būti atnaujintas." #: wp-cache.php:1703 msgid "1. If it already exists please delete the file first." msgstr "1. Jeigu jau egzistuoja, prašome pirmą pašalinti failą." #: wp-cache.php:1704 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Pakeiskite prieigos teises į %1$s, kad galima būtų šrašyti duomenis auto režimu (teisės turi būti: chmod 777 %1$s), patikrinkite teises ir atnaujinkite puslapį. Tai laikina taisyklė, po puslapio atnaujinimo teises reikės grąžinti į pradinius nustatymus (iš 777 į 755)." #: wp-cache.php:1705 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Atnaujinkite puslapį, failas %s/advanced-cache.php atsinaujins pats" #: wp-cache.php:1706 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Jei tai neveikia, įsitikinkite, kad failas %s/advanced-cache.php neegzistuoja:" #: wp-cache.php:1707 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Atverti \"%1$s$wp_cache_file teksto redaktoriumi.
  • 2. Keisti tekstą CACHEHOME%2$s
  • 3. Išsaugokite failą ir nukopijuokite jį į %3$s ir perkraukite šį puslapį.
    • " #: wp-cache.php:1730 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    WP_CACHE konstanta nustatyta į false

    WP_CACHE konstanta naudojama WordPress kodo įkelimui, kuris tarnauja puslapių talpyklai. Deja, tai klaidinga. Prašome redaguoti savo wp-config.php ir pridėti arba redaguoti šią eilutę virš galutinės require_once komandos:

    define('WP_CACHE', true);

    " #: wp-cache.php:1732 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Klaida: WP_CACHE nėra įjungtas jūsų wp-config.php faile ir aš negalėjau jį pakeisti." #: wp-cache.php:1733 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Redaguoti %s ir pridėti šią eilutę:
    apibrėžti('WP_CACHE', true);
    Priešingu atveju, WP-cache negali būti vykdomas WordPress Core ." #: wp-cache.php:1737 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    WP_CACHE konstanta pridėta į wp-config.php

    Jei ir toliau matysite šį įspėjamąjį pranešimą, prašome žiūrėti 5 punkteDUK. WP_CACHE linija turi būti perkelta." #: wp-cache.php:1759 msgid "Cache Contents" msgstr "Talpyklos turiniai" #: wp-cache.php:1762 msgid "Object cache in use. No cache listing available." msgstr "Talpyklos objektas naudojamas. Talpyklos sąrašas nėpasiekiamas." #: wp-cache.php:1786 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Ištrinamas supercache failas: %s
    " #: wp-cache.php:1803 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Ištrynamas wp-cache failas: %s
    " #: wp-cache.php:1868 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Cache statistika nėra automatiškai sugeneruojama. Jūs turite paspausti nuorodą žemiau, kad šiame puslapyje regeneruotusi statistika." #: wp-cache.php:1869 msgid "Regenerate cache stats" msgstr "Atnaujinti talpyklos statistiką" #: wp-cache.php:1871 #, php-format msgid "Cache stats last generated: %s minutes ago." msgstr "Talpyklos statistika sugeneruota: %s min atgal." #: wp-cache.php:1877 msgid "WP-Cache" msgstr "WP-Cache" #: wp-cache.php:1878 #: wp-cache.php:1894 #, php-format msgid "%s Cached Pages" msgstr "%s talpykliniai puslapiai" #: wp-cache.php:1879 #: wp-cache.php:1899 #, php-format msgid "%s Expired Pages" msgstr "%s pasibaigę puslapiai" #: wp-cache.php:1893 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1904 msgid "Fresh WP-Cached Files" msgstr "Šviežia WP-failų talpykla" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "URI" msgstr "URI" #: wp-cache.php:1905 #: wp-cache.php:1921 msgid "Key" msgstr "Raktas" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Age" msgstr "Amžius" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Delete" msgstr "Panaikinti" #: wp-cache.php:1920 msgid "Stale WP-Cached Files" msgstr "Pasenusi WP-failų talpykla" #: wp-cache.php:1936 msgid "Fresh Super Cached Files" msgstr "Šviežia Super failų talpykla" #: wp-cache.php:1952 msgid "Stale Super Cached Files" msgstr "Pasenusi Super failų talpykla" #: wp-cache.php:1968 msgid "Hide file list" msgstr "Slėpti failų sąrašą" #: wp-cache.php:1970 msgid "Too many cached files, no listing possible." msgstr "Per daug failų talpykloje, juos dėti į sąrašą nebegalima." #: wp-cache.php:1972 msgid "List all cached files" msgstr "Visų talpyklos failų sąrašas" #: wp-cache.php:1978 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Šiukšlių valymas
    Paskutinis šiukšlių valymas buvo prieš %s min
    " #: wp-cache.php:1979 #, php-format msgid "Next GC in %s minutes" msgstr "Sekantis Šiukšlių valymas bus po %s min" #: wp-cache.php:1982 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Pasibaigęs failai - tai failai, senesni nei %s sekundžių. Jie vis dar naudojami įskiepio ir trinami periodiškai." #: wp-cache.php:1993 msgid "Delete Expired" msgstr "Ištrinti pasibaigusį" #: wp-cache.php:1999 #: wp-cache.php:2011 #: wp-cache.php:2174 msgid "Delete Cache" msgstr "Ištrinti talpyklą" #: wp-cache.php:2011 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Pašalinti Super Cache talpyklos failus (atsidarys naujam lange)" #: wp-cache.php:2150 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s dėkingas įskiepiui %2$s už atliktą darbą" #: wp-cache.php:2183 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "WP Super Cache turi būti sukonfiguruotas! Prašome apsilankyti įskiepio admino puslapyje." #: wp-cache.php:2189 msgid "Settings" msgstr "Nustatymai" #: wp-cache.php:2199 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "WP Super Cache išjungtas. Prašome apsilankyti įskiepio admino puslapyje, kad įjungti talpinimą." #: wp-cache.php:2218 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Pradinis puslapis suspaustas! Išvalykite talpyklą!" #: wp-cache.php:2218 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Prašome apsilankyti %s, kad išvalyti talpyklą, nes jūsų svetainės pradinis puslapis dabar siunčiamas!" #: wp-cache.php:2221 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Pradinis puslapis buvo suspaustas! Talpykla išvalyta!" #: wp-cache.php:2221 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Jūsų blogo talpykla buvo išvalyta, kadangi jūsų svetainės pradinis puslapis šiuo metu siunčiamas. Prašome apsilankyti %s, kad patikrinti, ar talpykla buvo išvalyta." #: wp-cache.php:2228 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Pradinis puslapis nėra korektiškas! Prašome išvalyti talpyklą!" #: wp-cache.php:2228 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "Prašome apsilankyti %1$s, kad išvalyti talpyklą, nes jūsų svetainės pradinis puslapis nėra korektiškas ir trūksta teksto - \"%2$s\"!" #: wp-cache.php:2231 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Pradinis puslapis nėra korektiškas! Talpykla išvalyta!" #: wp-cache.php:2231 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "Jūsų blogo talpykla buvo išvalyta, kadangi jūsų blogo pradinis puslapis neturi teksto \"%2$s\"! Prašome aplanakyti %1$s, kad patikrinti, ar talpykla yra išvalyta." #: wp-cache.php:2236 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Pradinis puslapis patikrintas!" #: wp-cache.php:2236 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache patikrino jūsų pradinį dienoraščio puslapį. Prašome aplankyti %s, jeigu norite atjungti tai." #: wp-cache.php:2279 msgid "Cannot update .htaccess" msgstr "Negali atnaujinti .htaccess" #: wp-cache.php:2279 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Failas %s.htaccess negali būti atnaujintas automatiniu būdu. Prašome pataisyti jį, naudojant chmod komandą arba ftp klientą." #: wp-cache.php:2279 msgid "Refresh this page when the file permissions have been modified." msgstr "Atnaujinkite šį puslapį, kai failo prieigos teisės bus modifikuoti." #: wp-cache.php:2279 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Jūs taip pat galite redaguoti failą %s.htaccess rankiniu būdu ir asmeniškai įrašyti reikalingas taisykles (iki esančių ten WordPress taisyklių):" #: wp-cache.php:2283 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Kad įskiepis galėtų teisingai dirbti su statiniais html failais, jūs turite įrašyti į failą %s.htaccess įskiepio mod_rewrite taisykles" #: wp-cache.php:2284 msgid "You can edit the file yourself add the following rules." msgstr "Jūs galite redaguoti failą, savarankiškai pridedant sekančias taisykles." #: wp-cache.php:2285 msgid " Make sure they appear before any existing WordPress rules. " msgstr "Įsitikinkite, kad jie eina prieš bet kurią WordPress egzistuojančią taisyklę. " #: wp-cache.php:2293 msgid "Update Mod_Rewrite Rules" msgstr "Atnaujinti mod_rewrite teises" #: wp-cache.php:2389 #, php-format msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Bendrasis talpinimas prasidėjo" #: wp-cache.php:2391 #, php-format msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Atnaujinamos žinutės nuo %2$d iki %3$d" #: wp-cache.php:2402 #, php-format msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d žinučių atnaujinta" #: wp-cache.php:2402 msgid "Refreshed the following posts:" msgstr "Atnaujintos sekančios žinutęs:" #: wp-cache.php:2411 #, php-format msgid "Scheduling next preload refresh in %d minutes." msgstr "Sekantis planinis bendros talpyklos atnaujinimas įvyks po:% d minučių." #: wp-cache.php:2421 #, php-format msgid "[%s] Cache Preload Completed" msgstr "[%s] Talpyklos prieškrūvis baigtas" #: wp-cache.php:2421 msgid "Cleaning up old supercache files." msgstr "Valymas senų supercache failų." #: wp-cache.php:2462 #, php-format msgid "[%s] Preload may have stalled." msgstr "[%s] Prieškrūvis gali būti vilkinamas." #: wp-cache.php:2462 #, php-format msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Išankstinė apkrova turi būti iš naujo paleista.\n" "%s" #~ msgid "" #~ "Scroll down this page and click the Update Mod_Rewrite Rules button." #~ msgstr "" #~ "Пролистайте страницу вних и нажмите кнопку Обновить правила " #~ "Mod_Rewrite." #~ msgid "WP Super Cache Manager" #~ msgstr "Управление плагином WP Super Cache" #~ msgid "Why your configuration may not be changed" #~ msgstr "Почему конфигурации не могут быть изменены" #~ msgid "Why" #~ msgstr "Почему" #~ msgid "ON" #~ msgstr "ВКЛ" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "Плагины WP Cache и Super Cache включены" #~ msgid "HALF ON" #~ msgstr "РАБОТАЕТ НАПОЛОВИНУ" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Плагин Super Cache отключен, работает только кэшировани WP-Cache" #~ msgid "OFF" #~ msgstr "ВЫКЛ" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "Плагины WP Cache и Super Cache отключены" #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "Восстановление кэша. При включенной опции, гости сайта будут получать " #~ "старые страницы из плагина Super Cache, пока формируются новые. " #~ "Рекомендуется использовать данную опцию только для очень " #~ "посещаемых блогов, где много комментариев. После включения опции в " #~ "настройках \"прямое кэширование страниц\" и \"закрытый режим\" нет нужды " #~ "(они устаревают)" #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "Создавать список новых кэшированных страниц (использовать на свой страх и " #~ "риск, может затормозить сайты с большим количеством посетителей)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s действительно ускоряет Ваш блог. Вы можете сделать его еще " #~ "быстрее*, купив мне подарочную карту сервиса " #~ "Amazon! Можете выбрать \"%3$s\" любое значение, какое хотите. Каждая " #~ "копейка поможет мне!" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "Если Вы не хотите иметь дело с Amazon , то можно сделать пожертвование " #~ "через PayPal. Нажмите кнопку \"Пожертвовать\" или выберите подарок для " #~ "меня из моего списка желаний." #~ msgid "Thanks in advance!" #~ msgstr "Заранее благодарю!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Ладно, он не будет быстрее, но Вы все равно сделаете автора плагина очень " #~ "счастливым!" #~ msgid "Don’t show me this again." #~ msgstr "Не показывать больше это сообщение." #~ msgid "Hide" #~ msgstr "Спрятать" #~ msgid "" #~ "He blogs at %1$s and posts photos at %2$s. He would really appreciate a " #~ "donation to encourage development of this plugin." #~ "
    Even a penny will help." #~ msgstr "" #~ "Блог автора - %1$s, фотоблог - %2$s. Автор плагина будет благодарен любой " #~ "поддержке от Вас.
    Даже копейка может помочь в " #~ "его работе." #~ msgid "Super Cache Compression" #~ msgstr "Сжатие кэша Super Cache" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "" #~ "Сжатие кэша отключено по умолчанию в режиме РАБОТАЕТ НАПОЛОВИНУ." #~ msgid "Super Cache compression is now disabled." #~ msgstr "Сжатие кэша Super Cache теперь отключено." #~ msgid "Super Cache compression is now enabled." #~ msgstr "Сжатие кэша Super Cache теперь включено." #~ msgid "Update Compression" #~ msgstr "Обновить настройки сжатия" #~ msgid "Debug Settings" #~ msgstr "Параметры отладки" #~ msgid "" #~ "

    WP_CACHE constant in wp-config.php set to false

    The WP_CACHE " #~ "constant is defined in your wp-config.php but must be set to true, not " #~ "false for this plugin to work correctly.

    " #~ msgstr "" #~ "

    Значение для WP_CACHE в конфигурационном файле WordPrees wp-config." #~ "php установлено на \"false\"

    Чтобы плагин заработал, значение " #~ "WP_CACHE в wp-config.php нужно поставить на \"true\".

    " #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "" #~ "Вы должны вручную отредактировать файл и добавить необходимые правила." languages/wp-super-cache-ro_RO.po000066600000221012152133035240012713 0ustar00# Translation of the WordPress plugin by . # Copyright (C) 2010 # This file is distributed under the same license as the package. # FIRST AUTHOR , 2010. # msgid "" msgstr "" "Project-Id-Version: WP Super Cache\n" "Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache\n" "POT-Creation-Date: 2010-09-27 13:58+0000\n" "PO-Revision-Date: 2011-06-13 18:44+0200\n" "Last-Translator: Alexandr K.\n" "Language-Team: Michail Bogdanov \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Romanian\n" "X-Poedit-Country: MOLDOVA, REPUBLIC OF\n" #: plugins/awaitingmoderation.php:4 msgid "Your comment is awaiting moderation." msgstr "Comentariul dvs. este în aşteptarea moderaţie." #: plugins/awaitingmoderation.php:23 #: plugins/awaitingmoderation.php:38 #: plugins/badbehaviour.php:47 #: plugins/badbehaviour.php:65 #: plugins/domain-mapping.php:47 #: plugins/domain-mapping.php:62 #: plugins/searchengine.php:61 #: plugins/searchengine.php:76 #: wp-cache.php:1114 msgid "Disable" msgstr "Off" #: plugins/awaitingmoderation.php:29 #: plugins/badbehaviour.php:55 #: plugins/domain-mapping.php:53 #: plugins/searchengine.php:67 msgid "disabled" msgstr "off" #: plugins/awaitingmoderation.php:31 #: plugins/badbehaviour.php:57 #: plugins/domain-mapping.php:55 #: plugins/searchengine.php:69 #: wp-cache.php:1460 msgid "enabled" msgstr "activat" #: plugins/awaitingmoderation.php:33 #, php-format msgid "Awaiting Moderation plugin is %s" msgstr "Aşteaptă moderarea plug-in este %s" #: plugins/awaitingmoderation.php:34 msgid "(Remove the text \"Your comment is awaiting moderation.\" when someone leaves a moderated comment.) " msgstr "(Scoateţi textul \"Comentariul dvs. este în aşteptarea moderaţie.\", atunci când cineva lasă un comentariu moderat.)" #: plugins/awaitingmoderation.php:36 #: plugins/badbehaviour.php:63 #: plugins/domain-mapping.php:60 #: plugins/searchengine.php:74 #: wp-cache.php:1114 msgid "Enable" msgstr "Activat" #: plugins/badbehaviour.php:45 msgid "Bad Behaviour not found. Please check your install." msgstr "Bad Comportamentul nu a fost găsită. Vă rugăm să verificaţi a vă instala." #: plugins/badbehaviour.php:60 #, php-format msgid "Bad Behaviour support is %s." msgstr "Sprijin Bad Behaviour este %s." #: plugins/badbehaviour.php:61 #, php-format msgid "(Only legacy caching supported, disabled compression and requires Bad Behavior in \"%s/plugins/bad-behavior/\") " msgstr "(Numai cache moştenire a sprijinit, de compresie cu handicap şi necesită Bad Behavior în \"%s/plugins/bad-behavior/\")" #: plugins/badbehaviour.php:69 #: wp-cache.php:1191 #: wp-cache.php:1193 msgid "Warning!" msgstr "Atenţie!" #: plugins/domain-mapping.php:57 #, php-format msgid "Domain Mapping support plugin is %s" msgstr "Domeniu Mapping suport plug-in este %s" #: plugins/domain-mapping.php:58 msgid "(support for multiple domains on multisite websites) " msgstr "(suport pentru mai multe domenii pe site-uri multisite)" #: plugins/domain-mapping.php:72 msgid "Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin." msgstr "Domeniu Mapping plugin detectate Vă rugăm să mergeţi la pagina Supercache plugin-uri şi pentru a permite helper cartografiere domeniu plugin." #: plugins/searchengine.php:71 #, php-format msgid "No Adverts for Friends plugin is %s." msgstr "Nu Anunţuri pentru prietenii plug-in este %s." #: plugins/searchengine.php:72 msgid "(requires friendsadverts.php too) " msgstr "(Necesită friendsadverts.php prea) " #: wp-cache.php:87 #, php-format msgid "Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php" msgstr "Vă rugăm să creaţi %s /wp-cache-config.php din wp-super-cache/wp-cache-config-sample.php" #: wp-cache.php:138 msgid "Warning! PHP Safe Mode Enabled!" msgstr "Avertisment PHP Safe Mode Enabled!" #: wp-cache.php:139 msgid "You may experience problems running this plugin because SAFE MODE is enabled." msgstr "Este posibil să apară probleme de funcţionare, deoarece acest plug-in Safe Mode este activat." #: wp-cache.php:143 msgid "Your server is set up to check the owner of PHP scripts before allowing them to read and write files." msgstr "Serverul este configurat pentru a verifica proprietarul de scripturi PHP înainte de a le permite să citească şi să scrie fişiere." #: wp-cache.php:144 #, php-format msgid "You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details." msgstr "Ai sau un administrator ar putea să facem să funcţioneze prin schimbarea proprietar al grupului de plugin-ul script-uri pentru a se potrivi cel al utilizatorului server de web. Proprietar al grupului de %s/cache/ dosar trebuie să fie, de asemenea, schimbat. Se vedea modul de siguranţă pagina de manual pentru detalii suplimentare." #: wp-cache.php:146 msgid "You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file." msgstr "Ai sau un administrator trebuie să dezactivaţi această. Consultaţi pagina de siguranţă modul manual pentru detalii suplimentare. Acest lucru nu poate fi dezactivat într-un fişier. htaccess, din păcate. Aceasta trebuie să fie în fişierul de configurare php.ini. " #: wp-cache.php:152 msgid "Permlink Structure Error" msgstr "Permlink Structura Error" #: wp-cache.php:153 msgid "A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks." msgstr "Un URL-ul personalizat sau structura Permalink este necesar pentru acest plug-in pentru a funcţiona corect. Vă rugăm să mergeţi la Permalinks pagina Opţiuni pentru a configura permalinks dumneavoastră." #: wp-cache.php:165 #, php-format msgid "Warning! Your hostname \"%s\" resolves to %s" msgstr "Avertisment! Hostname \"%s\" rezolvă la %s" #: wp-cache.php:166 #, php-format msgid "Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly." msgstr "Serverul crede hostname rezolvă la %s. Unele servicii, cum ar fi colectarea gunoiului de acest plugin, şi WordPress posturi programate să nu funcţioneze corect." #: wp-cache.php:167 #: wp-cache.php:181 #, php-format msgid "Please see entry 16 in the Troubleshooting section of the readme.txt" msgstr "Vă rugăm să consultaţi de intrare 16 în secţiunea Rezolvare Probleme de readme.txt" #: wp-cache.php:180 msgid "Unfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities." msgstr "Din pacate WordPress nu poate găsi fişierul wp-cron.php Acest script este necesar pentru funcţionarea corectă de colectare a gunoiului de acest plug-in, WordPress posturi programate, precum şi alte activităţi critice." #: wp-cache.php:195 msgid "Cannot continue... fix previous problems and retry." msgstr "Nu se poate continua... rezolva problemele anterioare şi încercaţi din nou." #: wp-cache.php:204 msgid "Zlib Output Compression Enabled!" msgstr "Compresie de ieşire Zlib Enabled!" #: wp-cache.php:205 msgid "PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini." msgstr "PHP este comprimarea datelor trimise de vizitatorii site-ului. Dezactivarea acest lucru este recomandat ca plugin-ul cache de ieşire comprimat o dată în loc de comprimare aceeaşi pagină de peste si peste din nou. Vedea, de asemenea #21 în secţiunea Depanare. Consultaţi această pagină pentru instrucţiuni referitoare la modificarea fişierul php.ini." #: wp-cache.php:209 msgid "Mod rewrite may not be installed!" msgstr "Mod rescrie nu poate fi instalat!" #: wp-cache.php:210 msgid "It appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes." msgstr "Se pare că mod_rewrite nu este instalat. Uneori, această verificare nu este 100% de încredere, mai ales dacă nu sunteţi folosind Apache. Vă rugăm să verificaţi că mod_rewrite modulul este încărcat. Este necesar pentru a servi fişiere statice Super Cache. Veţi fi în continuare posibilitatea de a utiliza moduri de moştenire sau PHP." #: wp-cache.php:215 msgid "Read Only Mode. Configuration cannot be changed." msgstr "Doar în citire Mode. Configurare nu poate fi schimbat." #: wp-cache.php:216 #, php-format msgid "The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes." msgstr "WP Super Cache fişier de configurare este de %s/wp-cache-config.php şi nu pot fi modificate. Acest dosar trebuie să fie inscriptibile de către webserver să facă orice modificări." #: wp-cache.php:217 msgid "A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine." msgstr "Un mod simplu de a face asta este de a schimba permisiunile utilizând comanda chmod temporar sau prin intermediul dvs. de client FTP. Asiguraţi-vă că la nivel global inscriptibile şi ar trebui să fie bine." #: wp-cache.php:218 msgid "Writeable:" msgstr "Inscriptibile:" #: wp-cache.php:219 msgid "Readonly:" msgstr "Readonly:" #: wp-cache.php:231 #, php-format msgid "Warning! %s is writeable!" msgstr "Atenţie: %s este inscriptibile!" #: wp-cache.php:232 #, php-format msgid "You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:" msgstr "Ar trebui să schimbaţi permisiunile pe% s şi să-l mai restrictive utilizarea clientului de FTP, sau următoarea comandă pentru a remedia lucrurile:" #: wp-cache.php:240 msgid "Mobile rewrite rules detected" msgstr "Mobile regulile de rescriere detectat" #: wp-cache.php:241 msgid "For best performance you should enable \"Mobile device support\" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text \"2.0\\ MMP|240x320\" and delete those." msgstr "Pentru cele mai bune performanţe ar trebui să permită \"Mobile sprijin dispozitiv de\" sau şterge mobil rescrie regulile în dumneavoastră htaccess Uita-te pentru cele 2 linii cu textul \" 2.0\\MMP|240x320\" şi ştergeţi-le." #: wp-cache.php:241 msgid "This will have no affect on ordinary users but mobile users will see uncached pages." msgstr "Acest lucru va avea nici o afecta pe utilizatorii obişnuiţi, dar utilizatorii de telefonie mobilă vor vedea paginile uncached." #: wp-cache.php:247 #: wp-cache.php:258 msgid "Rewrite rules must be updated" msgstr "Regulile de rescriere trebuie să fie actualizate" #: wp-cache.php:248 #: wp-cache.php:259 msgid "The rewrite rules required by this plugin have changed or are missing. " msgstr "Rescriere normele impuse de acest plugin-au schimbat sau lipsesc." #: wp-cache.php:249 msgid "Mobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):" msgstr "Suport pentru dispozitive mobile necesită norme suplimentare în fişierul htaccess, sau puteţi seta modul de plug-in pentru moştenirea Aici sunt opţiunile dumneavoastră (în ordine de dificultate):" #: wp-cache.php:250 msgid "Set the plugin to legacy mode and enable mobile support." msgstr "Setaţi plug-in pentru modul de moştenire şi pentru a permite suport mobil." #: wp-cache.php:251 #: wp-cache.php:260 msgid "Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button." msgstr "Derulaţi în jos pagina Setări avansate şi faceţi clic pe butonul Update mod_rewrite Reguli." #: wp-cache.php:252 #, php-format msgid "Delete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page." msgstr "Şterge plugin mod_rewrite normele în %s.htaccess închise de către # BEGIN WPSuperCache şi # END WPSuperCache şi lăsaţi plugin-ul regenera le reîncărcaţi această pagină." #: wp-cache.php:253 #, php-format msgid "Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)" msgstr "Adăugaţi regulile de tine liniile. Editare %s.htaccess şi pentru a găsi bloc de cod închisă de # BEGIN WPSuperCache şi # END WPSuperCache. Există două secţiuni, care arata foarte similar linie. Doar sub %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ adăugaţi aceste linii: (o fac de două ori, o dată pentru fiecare secţiune) " #: wp-cache.php:266 msgid "Required to serve compressed supercache files properly." msgstr "Necesar pentru a servi fişiere comprimate supercache în mod corespunzător." #: wp-cache.php:266 msgid "Required to set caching information on supercache pages. IE7 users will see old pages without this module." msgstr "Necesare pentru a seta informaţii cache de pe paginile supercache IE7 utilizatorii vor vedea paginile vechi, fără acest modul." #: wp-cache.php:266 msgid "Set the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module." msgstr "Setaţi data de expirare de pe paginile supercached Vizitatorii nu pot vedea noi pagini atunci când reîmprospătare sau lăsaţi comentarii, fără acest modul." #: wp-cache.php:273 msgid "Missing Apache Modules" msgstr "Missing Module Apache" #: wp-cache.php:274 msgid "The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however." msgstr "Următoarele module Apache lipsesc plugin va. Lucra în modul de moştenire fără ele. În modul complet Supercache, vizitatorii dvs. pot vedea paginile corupt sau din data de conţinut cu toate acestea." #: wp-cache.php:413 msgid "Warning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file." msgstr "Atenţie încercat! Puteţi să activaţi de compresie, dar zlib.output_compression este activată. Vedea în secţiunea Troubleshooting (#21) din fişierul readme." #: wp-cache.php:501 msgid "WP Super Cache Settings" msgstr "Setări WP Super Cache" #: wp-cache.php:512 msgid "Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default." msgstr "Nota: mod_rewrite activat sau caching Legacy. Rezultate Advanced Settings Page implicit." #: wp-cache.php:523 msgid "Configuration file changed, some values might be wrong. Load the page again from the \"Settings\" menu to reset them." msgstr "Fişier de configurare schimbat, unele valori ar putea fi greşită Încărcaţi a doua pagină din nou. De la \"Settings\" meniu pentru a le reseta." #: wp-cache.php:540 #: wp-cache.php:614 msgid "Caching must be enabled to use this feature" msgstr "Stocarea trebuie să fie activată pentru a utiliza această funcţie" #: wp-cache.php:542 msgid "Cache Tester" msgstr "Cache Tester" #: wp-cache.php:543 msgid "Test your cached website by clicking the test button below." msgstr "Testaţi-vă site-ul cache făcând clic pe butonul de test de mai jos." #: wp-cache.php:550 #, php-format msgid "Fetching %s to prime cache: " msgstr "Se preiau %s la cache prim:" #: wp-cache.php:552 #: wp-cache.php:559 #: wp-cache.php:566 msgid "OK" msgstr "OK" #: wp-cache.php:557 #, php-format msgid "Fetching first copy of %s: " msgstr "Exemplar preiau primul %s:" #: wp-cache.php:564 #, php-format msgid "Fetching second copy of %s: " msgstr "Copie preiau doilea lui %s:" #: wp-cache.php:570 msgid "One or more page requests failed:" msgstr "Una sau mai multe cereri de start a eşuat:" #: wp-cache.php:589 #: wp-cache.php:590 #, php-format msgid "Page %d: %d (%s)" msgstr "Pagina %d: %d (%s)" #: wp-cache.php:596 #, php-format msgid "Page 1: %s" msgstr "Pagina 1: %s" #: wp-cache.php:597 #, php-format msgid "Page 2: %s" msgstr "Pagina 2: %s" #: wp-cache.php:598 msgid "The timestamps on both pages match!" msgstr "Marcajele de timp pe ambele pagini meci!" #: wp-cache.php:600 msgid "The pages do not match! Timestamps differ or were not found!" msgstr "Paginile nu se potrivesc sau marcajele de timp diferă! Nu au fost găsit!" #: wp-cache.php:606 msgid "Send non-secure (non https) request for homepage" msgstr "Trimite non-sigură (https non) cererea pentru pagina de start" #: wp-cache.php:607 msgid "Test Cache" msgstr "Test Cache" #: wp-cache.php:632 #: wp-cache.php:755 msgid "Cancel Cache Preload" msgstr "Cancel Cache preîncărcate" #: wp-cache.php:638 msgid "Scheduled preloading of cache cancelled. If a job is currently running it will not shutdown until the current 100 pages are complete." msgstr "Preîncărcându programate de cache anulat cazul în care un loc de muncă este în prezent rulează acesta nu va shutdown până când curentul 100 de pagini sunt complete." #: wp-cache.php:649 msgid "Scheduled preloading of cache cancelled." msgstr "Preîncărcându programate de cache anulate." #: wp-cache.php:675 #: wp-cache.php:753 msgid "Preload Cache Now" msgstr "Preîncărcate Cache Now" #: wp-cache.php:678 msgid "Scheduled preloading of cache in 10 seconds." msgstr "Preîncărcându programate de cache în 10 secunde." #: wp-cache.php:682 #, php-format msgid "Scheduled preloading of cache in %d minutes" msgstr "Preîncărcându programate de cache în %d minute" #: wp-cache.php:686 msgid "This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now." msgstr "Acest lucru va cache fiecare post publicat şi pe pagina site-ul dvs. Acesta va crea fişiere supercache statice astfel vizitatori necunoscut (inclusiv roboţi) va lovi o pagina din cache. Acest lucru va ajuta, probabil, rang dvs. Google ca le folosesc de viteză, ca metric atunci când judecă site-uri web acum." #: wp-cache.php:687 msgid "Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting." msgstr "Preincarcarea creează o mulţime de fişiere cu toate acestea. Caching se face de la cel mai nou post la cea mai veche deci vă rugăm să ia în considerare numai caching mai nou, dacă aveţi o mulţime (10.000 +) de posturi. Acest lucru este important mai ales pe shared hosting." #: wp-cache.php:688 msgid "In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded." msgstr "În ’General caching’ colectare a gunoiului regulat va curata doar la fişierele vechi moştenire pentru utilizatorii cunoscuţi nu, fişierele preîncărcate supercache. Aceasta este o setare recomandată atunci când memoria cache este preîncărcate." #: wp-cache.php:692 #, php-format msgid "Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)" msgstr "Reîmprospătare cache preîncărcat fişiere minute la fiecare %s (0 dezactiva, minim %d minute.)" #: wp-cache.php:705 msgid "all" msgstr "toate" #: wp-cache.php:718 #, php-format msgid "Preload %s posts." msgstr "Preîncărcate mesaje %s." #: wp-cache.php:725 msgid "Preload mode (garbage collection only on legacy cache files. Recommended.)" msgstr "Preîncărcate modul (de colectare a gunoiului numai pe fisiere cache moştenirea recomandate.)" #: wp-cache.php:728 msgid "Send me status emails when files are refreshed." msgstr "Trimite-mi email-uri de stare atunci când fişierele sunt actualizate." #: wp-cache.php:733 msgid "Many emails, 2 emails per 100 posts." msgstr "Multe e-mailuri, 2 email-uri la 100 de posturi." #: wp-cache.php:736 msgid "Medium, 1 email per 100 posts." msgstr "Medium, 1 e-mail la 100 de posturi." #: wp-cache.php:739 msgid "Less emails, 1 at the start and 1 at the end of preloading all posts." msgstr "Mai e-mailuri, 1 la începutul şi 1 la sfârşitul preîncărcarea toate mesajele." #: wp-cache.php:743 #, php-format msgid "Refresh of cache in %d hours %d minutes and %d seconds." msgstr "Reîmprospătare de cache în %d ore %d minute şi %d secunde." #: wp-cache.php:744 #, php-format msgid "Full refresh of cache in %d hours %d minutes and %d seconds." msgstr "Refresh completă a memoriei cache în ore %d %d minute şi %d secunde." #: wp-cache.php:750 #, php-format msgid "Currently caching from post %d to %d." msgstr "În prezent, caching de la post %d la %d." #: wp-cache.php:753 msgid "Update Settings" msgstr "Setări de update" #: wp-cache.php:761 msgid "Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator." msgstr "Preincarcarea de cache cu handicap. Vă rugăm să dezactivaţi memorarea paginilor în cache moştenire sau vorbiti cu administratorul gazdă." #: wp-cache.php:776 #: wp-cache.php:865 msgid "Caching" msgstr "Caching" #: wp-cache.php:780 msgid "Cache hits to this website for quick access." msgstr "Cache hit-uri la acest site pentru acces rapid." #: wp-cache.php:780 #: wp-cache.php:781 #: wp-cache.php:795 #: wp-cache.php:799 #: wp-cache.php:802 #: wp-cache.php:803 #: wp-cache.php:868 msgid "Recommended" msgstr "Recomandat" #: wp-cache.php:781 msgid "Use mod_rewrite to serve cache files." msgstr "Foloseste mod_rewrite pentru a servi fişiere cache." #: wp-cache.php:782 msgid "Use PHP to serve cache files." msgstr "Utilizarea PHP pentru a servi fişiere cache." #: wp-cache.php:783 msgid "Legacy page caching." msgstr "Legacy caching pagina." #: wp-cache.php:784 msgid "Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should go with PHP caching." msgstr "Mod_rewrite este cel mai rapid, PHP este aproape la fel de rapid şi mai uşor de lucru pentru a obţine, în timp ce caching moştenirea este mai lent din nou, dar este mai flexibilă şi, de asemenea, uşor pentru a obţine de lucru. Utilizatorii noi ar trebui să meargă cu caching PHP." #: wp-cache.php:790 msgid "Miscellaneous" msgstr "Diverse" #: wp-cache.php:795 msgid "Compress pages so they’re served more quickly to visitors." msgstr "Comprimare fişiere cache pentru a accelera de lucru." #: wp-cache.php:796 msgid "Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache." msgstr "Compresia este dezactivată în mod implicit, deoarece unele gazdele au probleme cu fişiere comprimate. Pornirea-l pe şi în afara şterge memoria cache." #: wp-cache.php:799 msgid "304 Not Modified browser caching. Indicate when a page has not been modified since last requested." msgstr "304 Not Modified browser caching. Indice când o pagină nu a fost modificat de la ultima solicitate." #: wp-cache.php:800 msgid "304 support is disabled by default because in the past GoDaddy had problems with some of the headers used." msgstr "Sprijin pentru eroarea 304 este dezactivată în mod implicit (din cauza unei probleme de unele servicii)." #: wp-cache.php:802 msgid "Don’t cache pages for known users." msgstr "Nu paginile în cache pentru utilizatorii cunoscuţi." #: wp-cache.php:803 msgid "Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated." msgstr "Cache reconstrui servesc un fişier supercache. Utilizatorilor anonimi în timp ce un fişier nou este generat." #: wp-cache.php:804 msgid "Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)" msgstr "Spune cu mândrie lumea server-ul dvs. este dovada Digg! (Locuri un mesaj în subsol blog-ului dvs.)" #: wp-cache.php:810 #: wp-cache.php:957 #: wp-cache.php:1473 msgid "Advanced" msgstr "Advanced" #: wp-cache.php:814 msgid "Mobile device support." msgstr "Mobile sprijin dispozitiv." #: wp-cache.php:815 msgid "Clear all cache files when a post or page is published." msgstr "Ştergeţi toate fişierele cache atunci când un post sau pagină se publică." #: wp-cache.php:816 msgid "Only refresh current page when comments made." msgstr "Numai reincarca pagina curentă atunci când observaţiile făcute." #: wp-cache.php:817 msgid "List the newest cached pages on this page." msgstr "Lista de cele mai noi paginile stocate în cache de pe această pagină." #: wp-cache.php:819 msgid "Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!" msgstr "Fişier de blocare grosier. Ai face, probabil, nu este necesar acest lucru, dar ar putea ajuta dacă serverul este underpowered Atenţie! Poate provoca server-ul dvs. pentru a bloca in cazuri foarte rare!" #: wp-cache.php:822 msgid "Use object cache to store cached files." msgstr "Utilizarea cache obiect pentru a stoca fişierele din cache." #: wp-cache.php:822 msgid "(Experimental)" msgstr "(Experimental)" #: wp-cache.php:829 msgid "Note:" msgstr "Notă:" #: wp-cache.php:831 #, php-format msgid "If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)" msgstr "În cazul în dezinstalarea acest plug-in, asiguraţi-vă că %s dosar este inscriptibile de către serverul web astfel încât fişierele avansate-cache.php şi config.php cache-pot fi şterse în mod automat idee. (Asigurându-vă că aceste fişiere sunt inscriptibile prea este, probabil, un bun.)." #: wp-cache.php:832 #, php-format msgid "Please see the readme.txt for instructions on uninstalling this script. Look for the heading, \"How to uninstall WP Super Cache\"." msgstr "Vă rugăm să citiţi readme.txt pentru instrucţiuni privind dezinstalarea acest script. Uita-te pentru rubrica, \"Cum să dezinstalaţi WP Super Cache\"." #: wp-cache.php:833 #, php-format msgid "Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered." msgstr "Aveti nevoie de ajutor? Verificaţi Super Cache fişier Readme. Acesta include documentaţia de instalare, o şi depanare sfaturi FAQ. forum de suport este de asemenea disponibil. întrebarea dvs. poate au fost deja răspuns." #: wp-cache.php:836 #: wp-cache.php:883 msgid "Update Status" msgstr "Status Update" #: wp-cache.php:843 msgid "Accepted Filenames & Rejected URIs" msgstr "Nume de fişiere acceptate & URI respins" #: wp-cache.php:868 msgid "Caching On" msgstr "Cache On" #: wp-cache.php:869 msgid "Caching Off" msgstr "Cache Off" #: wp-cache.php:870 msgid "Note: enables PHP caching, cache rebuild, and mobile support" msgstr "Notă: PHP permite caching, reconstrui cache, şi suport mobil" #: wp-cache.php:880 msgid "Notice: Supercache mod_rewrite rules detected. Cached files will be served using those rules. Edit the .htaccess file in the root of your install and remove the SuperCache rules." msgstr "Nota: Supercache mod_rewrite normele detectate fişierele din cache va fi servite cu aceste norme. Editaţi fişierul htaccess în rădăcina dvs. de a instala şi de a elimina normele SuperCache." #: wp-cache.php:892 msgid "Make WordPress Faster" msgstr "A face WordPress mai repede" #: wp-cache.php:893 #, php-format msgid "%1$s is maintained and developed by %2$s with contributions from many others." msgstr "%1$s este menţinut şi dezvoltat de %2$s, cu contribuţii de la multe altele." #: wp-cache.php:894 #, php-format msgid "He blogs at %1$s and posts photos at %2$s." msgstr "El a blog-uri la %1$s şi fotografii de mesaje de la %2$s." #: wp-cache.php:895 #, php-format msgid "Please say hi to him on %s too!" msgstr "Vă rugăm să-l salut pe %s prea!" #: wp-cache.php:903 #, php-format msgid "Cached pages since %1$s : %2$s" msgstr "Paginile stocate în cache de la %1$s : %2$s" #: wp-cache.php:904 msgid "Newest Cached Pages:" msgstr "Cele mai noi Pagini cache:" #: wp-cache.php:908 #, php-format msgid "Cached %s seconds ago" msgstr "Cache %s secunde în urmă" #: wp-cache.php:911 msgid "(may not always be accurate on busy sites)" msgstr "(Pot să nu fie întotdeauna exacte pe site-urile ocupat)" #: wp-cache.php:930 msgid "Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins." msgstr "Cache plugin-uri sunt scripturi PHP care trăiesc într-un folder plugin-uri în interiorul folderul wp-super-cache. Ele sunt încărcate atunci când încarcă Supercache, mult mai devreme decât regulate WordPress plugin-uri." #: wp-cache.php:931 msgid "This is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them." msgstr "Acest lucru este strict o funcţie avansată doar şi cunoştinţe atât de PHP şi acţiuni WordPress este obligată să le creeze." #: wp-cache.php:941 msgid "Available Plugins" msgstr "Plugin-uri disponibile" #: wp-cache.php:957 msgid "Easy" msgstr "Easy" #: wp-cache.php:957 msgid "Tester & Contents" msgstr "Tester & Continut" #: wp-cache.php:957 msgid "Preload" msgstr "Preîncărcate" #: wp-cache.php:957 msgid "Plugins" msgstr "Plugin-uri" #: wp-cache.php:957 msgid "Debug" msgstr "Debug" #: wp-cache.php:984 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network." msgstr "Nota: WP Super Cache mod_rewrite controale regulă cu handicap cu excepţia cazului în care rulează pe site-ul principal al acestei reţele." #: wp-cache.php:986 #, php-format msgid "Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network." msgstr "Nota: WP Super Cache mod_rewrite controale regulă cu handicap cu excepţia cazului în care rulează pe pe site-ul principal al acestei reţele." #: wp-cache.php:996 msgid "Mod Rewrite Rules" msgstr "Mod Reguli de rescriere" #: wp-cache.php:1002 msgid "WordPress MU Detected" msgstr "WordPress MU Detected" #: wp-cache.php:1002 msgid "Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file." msgstr "Din păcate, rescrie regulile nu pot fi actualizate automat atunci când rulează WordPress UM. Vă rugăm să vă deschide htaccess şi. Se adaugă următoarele mod_rewrite regulile de mai sus a oricăror alte norme în acel fişier." #: wp-cache.php:1004 msgid "Mod Rewrite rules cannot be updated!" msgstr "Mod Regulile de rescriere nu poate fi actualizat!" #: wp-cache.php:1005 #, php-format msgid "You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:" msgstr "Trebuie să aveţi şi END markeri incepe in %s.htaccess pentru auto update la locul de muncă. Acestea arata ca acest lucru şi surround principal WordPress mod_rewrite normele:" #: wp-cache.php:1007 msgid "Refresh this page when you have updated your .htaccess file." msgstr "Reîmprospătare această pagină atunci când aţi actualizat fişierul htaccess." #: wp-cache.php:1011 msgid "Thank you for upgrading." msgstr "Vă mulţumim pentru upgrade." #: wp-cache.php:1011 #, php-format msgid "The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are \"HTTP_COOKIE\" becomes \"HTTP:Cookie\" and \"wordpressuser\" becomes \"wordpress\". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them." msgstr "Mod_rewrite normele modificate de la ultima ta instalat acest plug-in. Din păcate, trebuie să eliminaţi vechile reguli supercache înainte de cele noi sunt actualizate reîmprospăta această pagină. După ce aţi editat fişierul .htaccess. Dacă doriţi să faceţi upgrade manual, modificaţi următoarea linie: %1$s astfel se pare ca aceasta: %2$s. Singurele modificări sunt \"HTTP_COOKIE\"devine\"HTTP:Cookie\" şi \"wordpressuser\"devine\"WordPress\". Acesta este un WordPress 2.5. schimbare, dar este compatibil cu versiunile mai vechi daca esti destul de curajos să le folosească." #: wp-cache.php:1015 msgid "Trailing slash check required." msgstr "Trailing slash verifica necesare." #: wp-cache.php:1015 msgid "It looks like your blog has URLs that end with a \"/\". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a \"/\" end serve the same content as those with the \"/\" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:" msgstr "Se pare ca blog-ul dvs. are adresele URL care se termină cu o \"/\". Din păcate, din moment ce ai instalat acest plug-un duplicat bug conţinut a fost găsit în cazul în care nu adresele URL se termină într-o \"/\" sfârşitul servesc acelaşi conţinut ca şi cele cu \"/\" şi nu redirecţionare a URL-ul propriu Pentru a repara, trebuie să editaţi fişierul htaccess şi adăugaţi aceste două reguli pentru cele două grupe de reguli Super Cache:" #: wp-cache.php:1017 msgid "You can see where the rules go and examine the complete rules by clicking the \"View mod_rewrite rules\" link below." msgstr "Puteţi vedea în cazul în care normele de du-te şi să examineze normele complet, făcând clic pe \"View mod_rewrite normele\" link-ul de mai jos." #: wp-cache.php:1031 msgid "Mod Rewrite rules updated!" msgstr "Mod Regulile de rescriere actualizate!" #: wp-cache.php:1032 #, php-format msgid "%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:" msgstr "%s.htaccess a fost actualizat cu normele necesare mod_rewrite. Va rugam a verifica dacă sunt corecte ar trebui să arate acest lucru:" #: wp-cache.php:1034 msgid "Mod Rewrite rules must be updated!" msgstr "Mod Regulile de rescriere trebuie să fie actualizate!" #: wp-cache.php:1035 #, php-format msgid "Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:" msgstr "%s.htaccess ta nu poate fi scris de serverul web şi trebuie să fie actualizate cu normele necesare mod_rewrite. Noile norme du-te mai presus de reguli WordPress regulate aşa cum se arată în codul de mai jos:" #: wp-cache.php:1040 #, php-format msgid "WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match." msgstr "WP Super Cache mod regulile de rescriere au fost detectate în fişierul% s.htaccess.
    Faceţi clic pe link-ul următor pentru a vedea liniile de adăugat la acel fişier. Dacă aţi actualizat plugin-ul asiguraţi-vă că aceste reguli se potrivesc." #: wp-cache.php:1043 msgid "A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules." msgstr "O diferenţă între normele în fişierul htaccess. Şi plugin-ul regulile de rescriere a fost găsit Acest lucru ar putea fi diferenţele de simplu, dar spaţiu. Ar trebui să comparaţi normele în dosarul cu cele de mai jos cât mai curând posibil. Faceţi clic pe ’Update normele Mod_Rewrite’, pentru a face acest lucru în mod automat." #: wp-cache.php:1046 msgid "View Mod_Rewrite Rules" msgstr "Vezi mod_rewrite Reguli" #: wp-cache.php:1050 #: wp-cache.php:2287 #, php-format msgid "Rules must be added to %s too:" msgstr "Regulile trebuie să fie adăugată la %s prea:" #: wp-cache.php:1058 #, php-format msgid "Gzip encoding rules in %s.htaccess created." msgstr "Gzip reguli de codare în %s.htacces creat." #: wp-cache.php:1065 msgid "Fix Configuration" msgstr "Fix de configurare" #: wp-cache.php:1068 msgid "Restore Default Configuration" msgstr "Restore de configurare implicite" #: wp-cache.php:1076 msgid "Comment moderation is enabled. Your comment may take some time to appear." msgstr "Este activată moderarea comentariilor. Comentariul dvs. poate lua ceva timp să apară." #: wp-cache.php:1101 msgid "Lock Down:" msgstr "Lock Down:" #: wp-cache.php:1101 msgid "Disabled" msgstr "Disabled" #: wp-cache.php:1101 msgid "Enabled" msgstr "Enabled" #: wp-cache.php:1102 msgid "Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files." msgstr "Pregătiţi-server-ul dvs. pentru un vârf aşteptată a traficului prin activarea blocare în jos. Cand este activat, noi comentarii pe un post care nu va actualiza fişierele cache static." #: wp-cache.php:1103 msgid "Developers: Make your plugin lock down compatible by checking the \"WPLOCKDOWN\" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting." msgstr "Dezvoltatorii: Asiguraţi-vă plugin bloca compatibil prin verificarea \"WPLOCKDOWN\". Constanta urmatorul cod va asiguraţi-vă că plugin respectă setarea WPLOCKDOWN." #: wp-cache.php:1105 msgid "Sorry. My blog is locked down. Updates will appear shortly" msgstr "Imi pare rau. Blog-ul meu este blocat. Actualizări va apărea în scurt timp" #: wp-cache.php:1109 msgid "WordPress is locked down. Super Cache static files will not be deleted when new comments are made." msgstr "WordPress este blocat. Super fişiere statice Cache nu vor fi şterse atunci când noi comentarii sunt făcute." #: wp-cache.php:1111 msgid "WordPress is not locked down. New comments will refresh Super Cache static files as normal." msgstr "WordPress nu este blocat în jos comentariile noi vor reîmprospăta Super Cache fişiere statice, ca de obicei." #: wp-cache.php:1117 msgid "Lock Down" msgstr "Lock Down" #: wp-cache.php:1125 msgid "Directly Cached Files" msgstr "Fişiere direct cache" #: wp-cache.php:1183 #, php-format msgid "%s removed!" msgstr "%s eliminat!" #: wp-cache.php:1191 #, php-format msgid "You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated." msgstr "Trebuie să facă %s writable pentru a activa această facilitate. Deoarece acesta este un risc de securitate vă rugăm să-l doar în citire după ce pagina este generat." #: wp-cache.php:1193 #, php-format msgid "%s is writable. Please make it readonly after your page is generated as this is a security risk." msgstr "%s este writable Vă rugăm să-l doar în citire după ce pagina este generat ca acesta este un risc de securitate." #: wp-cache.php:1207 msgid "Existing direct page" msgstr "Directe existente pagina" #: wp-cache.php:1207 msgid "Delete cached file" msgstr "Şterge cache file" #: wp-cache.php:1212 msgid "Add direct page:" msgstr "Adauga pagina direct:" #: wp-cache.php:1214 #, php-format msgid "Directly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page." msgstr "Fişiere direct din cache sunt fişiere create direct de pe %s în cazul în care locuieşte blog-ul dvs. Această caracteristică este. Util numai dacă se asteapta la o Digg majore sau Slashdot nivel de trafic pentru un post sau pagină." #: wp-cache.php:1216 #, php-format msgid "For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page." msgstr "De exemplu: pentru cache %1$sabout/ ar trebui să introduceţ %1$sabout/ or /about/. Cache la dosar va fi generat în următorii un timp anonim vizite că pagina utilizatorului." #: wp-cache.php:1217 msgid "Make the textbox blank to remove it from the list of direct pages and delete the cached file." msgstr "Asiguraţi-casuta necompletat pentru a-l scoate din lista de pagini directe şi a şterge fişierul cache." #: wp-cache.php:1222 msgid "Update Direct Pages" msgstr "Update Pagini Direct" #: wp-cache.php:1260 msgid "Expiry Time & Garbage Collection" msgstr "Expirat pagina & Clar de moloz" #: wp-cache.php:1262 msgid "Expire time:" msgstr "Expirare timp:" #: wp-cache.php:1263 msgid "seconds" msgstr "secunde" #: wp-cache.php:1264 msgid "Garbage Collection" msgstr "Clar de moloz" #: wp-cache.php:1264 msgid "If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above." msgstr "În cazul în care ora de expirare este mai mare de 1800 secunde (o jumătate de oră), de colectare a gunoiului se va face la fiecare 10 minute, altfel se va întâmpla 10 secunde după ora de expirare de mai sus." #: wp-cache.php:1265 msgid "Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching." msgstr "Verificarea şi ştergerea fişierelor expirat este scump, dar e scump lasandu-le acolo. Pe foarte ocupat un site care ar trebui să stabilească expirarea timp pentru 300 secunde. Experiment cu valori diferite şi să vizitaţi această pagină pentru a vedea modul în care a expirat mai multe fişiere rămân la diferite ori în timpul zilei. Dacă folosiţi caching scopul de moştenire să aibă mai puţin de 500 de fişiere cache, dacă este posibil. Puteţi avea fişiere de multe ori mai mult cache atunci când se utilizează mod_rewrite sau caching PHP." #: wp-cache.php:1266 msgid "Set the expiry time to 0 seconds to disable garbage collection." msgstr "Seta ora de expirare la 0 de secunde pentru a dezactiva colectare a gunoiului." #: wp-cache.php:1267 msgid "Change Expiration" msgstr "Schimbarea de expirare" #: wp-cache.php:1311 msgid "Rejected User Agents" msgstr "Respins de agenţi de utilizare" #: wp-cache.php:1312 msgid "Strings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists." msgstr "Pentru a preveni plug-in pentru interogări cache-ul de la roboţii motoarelor de căutare şi altor roboţi în reţea, introduceţi numele acestora în caseta de mai jos (câte unul pe linie). În cazul în care o copie a paginii există deja în cache, Super Cache, acesta va fi trimis la bot." #: wp-cache.php:1319 msgid "Save UA Strings" msgstr "Salvaţi Strings UA" #: wp-cache.php:1342 msgid "Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type." msgstr "Nu cache pagina de următoarele tipuri. Consultaţi Condiţionat Tag-uri documentaţia pentru o discuţie completă pentru fiecare tip." #: wp-cache.php:1345 msgid "Single Posts" msgstr "Posturi Single" #: wp-cache.php:1346 msgid "Pages" msgstr "Pagini" #: wp-cache.php:1347 msgid "Front Page" msgstr "Home" #: wp-cache.php:1348 msgid "Home" msgstr "Home" #: wp-cache.php:1349 msgid "Archives" msgstr "Arhivele" #: wp-cache.php:1350 msgid "Tags" msgstr "Tag-uri" #: wp-cache.php:1351 msgid "Category" msgstr "Categorie" #: wp-cache.php:1352 msgid "Feeds" msgstr "Feeds" #: wp-cache.php:1353 msgid "Search Pages" msgstr "Paginile de căutare" #: wp-cache.php:1355 #: wp-cache.php:1483 msgid "Save" msgstr "Salvare" #: wp-cache.php:1372 msgid "Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page." msgstr "Adăugaţi aici siruri de caractere (nu un nume de fisier) că forţele o pagină nu trebuie să fie în cache. De exemplu, dacă URL-urile includ an şi tu dont doriţi să cache posturi de anul trecut, este suficient să se precizeze an, adică ’/2011/’. WP-Cache va căuta în cazul în care şir este parte a URI şi, dacă acest lucru nu, se va cache acea pagină." #: wp-cache.php:1378 msgid "Save Strings" msgstr "Salvaţi Strings" #: wp-cache.php:1394 msgid "Add here those filenames that can be cached, even if they match one of the rejected substring specified above." msgstr "Adăugaţi aici acele numele de fişiere care pot fi memorate în cache, chiar dacă acestea se potrivesc unul dintre respins subşir specificate mai sus." #: wp-cache.php:1400 msgid "Save Files" msgstr "Salvaţi Files" #: wp-cache.php:1445 msgid "Currently logging to: " msgstr "În prezent, logare la:" #: wp-cache.php:1455 msgid "Fix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory." msgstr "Fix probleme cu plugin-ul de depanare-l aici poate trimite e-mailuri sau debug log-le într-un fişier în directorul cache-ul dumneavoastră." #: wp-cache.php:1456 msgid "Logging to a file is easier but faces the problem that clearing the cache will clear the log file." msgstr "Conectarea la un fişier este mai uşor, dar se confruntă cu problema că golirea memoriei cache va şterge fişierul jurnal." #: wp-cache.php:1460 msgid "Debugging" msgstr "Debugging" #: wp-cache.php:1461 msgid "Logging Type" msgstr "Logging Tipul" #: wp-cache.php:1461 msgid "Email" msgstr "Email" #: wp-cache.php:1462 msgid "file" msgstr "file" #: wp-cache.php:1463 msgid "IP Address" msgstr "Adresa IP" #: wp-cache.php:1463 #, php-format msgid "(only log requests from this IP address. Your IP is %s)" msgstr "(jurnal numai cereri de la această adresă IP. IP-ul tau este - %s)" #: wp-cache.php:1464 msgid "Log level" msgstr "Jurnal nivel" #: wp-cache.php:1470 msgid "(1 = less, 5 = more, may cause severe server load.)" msgstr "(1 = mai puţin, 5 = mai mult, poate provoca de încărcare server severe.)" #: wp-cache.php:1473 msgid "In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    " msgstr "În cazuri foarte rare pot apărea două probleme pe unele blog-uri:
    1. Pagina de faţă poate începe descărcarea ca un fişier zip.
    2. Pagina este greşit ocazional cache ca pagina de faţă dacă blog-ul dvs. foloseşte o pagină statică şi structura Permalink este /%category%/%postname%/.
    " #: wp-cache.php:1474 #, php-format msgid "I’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem." msgstr "I’m 99% certain that they aren’t Bug-uri în WP Super Cache şi ele se întâmplă numai în cazuri foarte rare, dar puteţi rula o verificare simplă o dată la fiecare 5 minute pentru a verifica dacă site-ul dvs. este ok, dacă sunteţi îngrijorat. Tu va fi trimisă în cazul în care există o problemă." #: wp-cache.php:1476 msgid "Check front page every 5 minutes." msgstr "Check prima pagina la fiecare 5 minute." #: wp-cache.php:1477 msgid "Front page text" msgstr "Prima pagină text" #: wp-cache.php:1477 msgid "Text to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable." msgstr "Text pentru a căuta pe pagina dvs. Dacă acest text lipseşte cache va fi şters. Lăsaţi necompletat pentru a dezactiva." #: wp-cache.php:1478 msgid "Clear cache on error." msgstr "Clear cache la eroare." #: wp-cache.php:1479 msgid "Email the blog admin when checks are made. (useful for testing)" msgstr "Email blog-ul admin, atunci când controalele sunt efectuate. (util pentru testarea)" #: wp-cache.php:1493 msgid "Error: GZIP compression is enabled, disable it if you want to enable wp-cache." msgstr "Eroare: compresie gzip este activat, dezactivati-l dacă doriţi să activaţi wp-cache." #: wp-cache.php:1540 #: wp-cache.php:1702 msgid "Warning" msgstr "Atenţie" #: wp-cache.php:1540 msgid "GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression." msgstr "GZIP compresie este activată în WordPress, WP-cache vor fi ocolite până când compresie gzip dezactivaţi." #: wp-cache.php:1598 #: wp-cache.php:1603 #: wp-cache.php:1635 #: wp-cache.php:1640 #: wp-cache.php:1646 msgid "Error" msgstr "Eroare" #: wp-cache.php:1598 #, php-format msgid "Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions." msgstr "Cache director ($ cache_path) nu există şi nu poate fi creat de către serverul de web. Verificarea %s permisiunilor." #: wp-cache.php:1603 #, php-format msgid "Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it." msgstr "Cache dosar (%1$s) sau %2$s trebuie să fie writable pentru acest plugin pentru a lucra. Double-check." #: wp-cache.php:1635 #, php-format msgid "Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page." msgstr "Your WP-Cache fişier de configurare (%s) este de actualitate şi nu poate fi scris de către server. Please Web ştergeţi-l şi a reîmprospăta această pagină." #: wp-cache.php:1640 #, php-format msgid "Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions." msgstr "Fişier de configurare lipsă şi %1$s dosar (%2$s) nu poate fi scris de server. Check Web permisiunile sale." #: wp-cache.php:1646 #, php-format msgid "Sample WP-Cache config file (%s) does not exist.Verify you installation." msgstr "Exemplu de WP-Cache fişier de configurare (%s) nu exista. Va rugam sa verificati vă de instalare." #: wp-cache.php:1702 #, php-format msgid "%s/advanced-cache.php does not exist or cannot be updated." msgstr "%s/advanced-cache.php nu există sau nu pot fi actualizate." #: wp-cache.php:1703 msgid "1. If it already exists please delete the file first." msgstr "1. În cazul în care există deja vă rugăm să ştergeţi primul fişier." #: wp-cache.php:1704 #, php-format msgid "2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)" msgstr "2. Asiguraţi %1$s scriere utilizând comanda chmod prin ftp sau software de tip server şi. (Chmod 777 %1$s) reîmprospăta această pagină. Aceasta este doar o măsură temporară şi va trebui să-l citesc numai ulterior din nou. (Schimbaţi 777-755 în comenzii precedente) " #: wp-cache.php:1705 #, php-format msgid "3. Refresh this page to update %s/advanced-cache.php" msgstr "3. Refresh această pagină pentru a actualiza %s/avansat-cache.php" #: wp-cache.php:1706 #, php-format msgid "If that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:" msgstr "Dacă acest lucru nu funcţionează, asiguraţi-vă că %s/avansat-cache.php doar nu există:" #: wp-cache.php:1707 #, php-format msgid "
  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • " msgstr "
  • 1. Deschideţi fişierul %1$s$wp_cache_file într-un editor de text.
  • 2. Schimbaţi linia CACHEHOME pe %2$s
  • 3. Salvaţi fişierul şi copiaţi %3$s, apoi reîmprospătaţi pagina.
    • " #: wp-cache.php:1730 msgid "

    WP_CACHE constant set to false

    The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

    define('WP_CACHE', true);

    " msgstr "

    WP_CACHE opţiune nu este activată

    Această opţiune trebuie să fie activat pentru a WordPress poate lucra corect cu fişierul cache. In acest moment este dezactivat. Pentru a activa aceasta, deschideţi fişierul wp-config.php şi adăugaţi următoarea linie:

    define('WP_CACHE', true);

    " #: wp-cache.php:1732 msgid "Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it." msgstr "Eroare: WP_CACHE Variabila nu fie activate în comun configuraţiile wp-config.php." #: wp-cache.php:1733 #, php-format msgid "Edit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. " msgstr "Editare codul %s şi adăugaţi următoarele:
    define('WP_CACHE', true);
    . În caz contrar, WP-Cachenu va porni." #: wp-cache.php:1737 msgid "

    WP_CACHE constant added to wp-config.php

    If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up." msgstr "

    Parţial WP_CACHE adăugat la fişierul de configurare wp-config.php

    Dacă vedeţi în continuare acest mesaj, apoi verificaţi cu punctul 5 din FAQ (în limba engleză). Rând cu WP_CACHE ar trebui să fie plasat mai mare." #: wp-cache.php:1759 msgid "Cache Contents" msgstr "Cache Cuprins" #: wp-cache.php:1762 msgid "Object cache in use. No cache listing available." msgstr "Lista de caching disponibile." #: wp-cache.php:1786 #, php-format msgid "Deleting supercache file: %s
    " msgstr "Ştergerea supercache fişier: %s
    " #: wp-cache.php:1803 #, php-format msgid "Deleting wp-cache file: %s
    " msgstr "Ştergerea wp-cache fişier: %s
    " #: wp-cache.php:1868 msgid "Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page." msgstr "Cache statisticile nu sunt generate automat. Trebuie să faceţi clic pe link-ul de mai jos pentru a regenera statisticile de pe aceasta pagina." #: wp-cache.php:1869 msgid "Regenerate cache stats" msgstr "Stats Regenerare cache" #: wp-cache.php:1871 #, php-format msgid "Cache stats last generated: %s minutes ago." msgstr "Cache statistici ultima generat: %s minute în urmă." #: wp-cache.php:1877 msgid "WP-Cache" msgstr "WP-Cache Status" #: wp-cache.php:1878 #: wp-cache.php:1894 #, php-format msgid "%s Cached Pages" msgstr "%s pagini cached" #: wp-cache.php:1879 #: wp-cache.php:1899 #, php-format msgid "%s Expired Pages" msgstr "%s pagini expirat" #: wp-cache.php:1893 msgid "WP-Super-Cache" msgstr "WP-Super-Cache" #: wp-cache.php:1904 msgid "Fresh WP-Cached Files" msgstr "Fresh Files WP-Cache" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "URI" msgstr "URI" #: wp-cache.php:1905 #: wp-cache.php:1921 msgid "Key" msgstr "Cheie" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Age" msgstr "Age" #: wp-cache.php:1905 #: wp-cache.php:1921 #: wp-cache.php:1937 #: wp-cache.php:1953 msgid "Delete" msgstr "Delete" #: wp-cache.php:1920 msgid "Stale WP-Cached Files" msgstr "Viciat Files WP-Cache" #: wp-cache.php:1936 msgid "Fresh Super Cached Files" msgstr "Fresh Super fişierele din cache" #: wp-cache.php:1952 msgid "Stale Super Cached Files" msgstr "Viciat Super fişierele din cache" #: wp-cache.php:1968 msgid "Hide file list" msgstr "Ascunde listă de fişiere" #: wp-cache.php:1970 msgid "Too many cached files, no listing possible." msgstr "Prea multe fişiere cache, nici un anunţ este posibil." #: wp-cache.php:1972 msgid "List all cached files" msgstr "Lista toate fişierele din cache" #: wp-cache.php:1978 #, php-format msgid "Garbage Collection
    Last GC was %s minutes ago
    " msgstr "Garbage Collection
    Ultima GC a fost %s minute în urmă
    " #: wp-cache.php:1979 #, php-format msgid "Next GC in %s minutes" msgstr "Next GC în câteva minute %s" #: wp-cache.php:1982 #, php-format msgid "Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically." msgstr "Expirate fişiere sunt fişierele mai vechi %s secunde. Ele sunt încă utilizate de către plugin-ul şi se elimină periodic." #: wp-cache.php:1993 msgid "Delete Expired" msgstr "Şterge expirat" #: wp-cache.php:1999 #: wp-cache.php:2011 #: wp-cache.php:2174 msgid "Delete Cache" msgstr "Delete Cache" #: wp-cache.php:2011 msgid "Delete Super Cache cached files (opens in new window)" msgstr "Şterge Super Cache cache fişierele (se deschide într-o fereastră nouă)" #: wp-cache.php:2150 #, php-format msgid "%1$s is Digg proof thanks to caching by %2$s" msgstr "%1$s să-i mulţumesc %2$s pentru munca lor" #: wp-cache.php:2183 #, php-format msgid "WP Super Cache must be configured. Go to the admin page to enable and configure the plugin." msgstr "Plugin WP Super Cache ar trebui să fie configurat: Pentru a activa şi configura, du-te la pagina de management plug-in." #: wp-cache.php:2189 msgid "Settings" msgstr "Setări" #: wp-cache.php:2199 #, php-format msgid "WP Super Cache is disabled. Please go to the plugin admin page to enable caching." msgstr "Plugin WP Super Cache nu este activat. Pentru a activa aceasta, mergeţi la pagina de management plug-in." #: wp-cache.php:2218 #, php-format msgid "[%s] Front page is gzipped! Please clear cache!" msgstr "[%s] Home comprimate folosind gzip. Delete Cache!" #: wp-cache.php:2218 #, php-format msgid "Please visit %s to clear the cache as the front page of your site is now downloading!" msgstr "Eroare!\" Vizita %s pentru a elimina cache!" #: wp-cache.php:2221 #, php-format msgid "[%s] Front page is gzipped! Cache Cleared!" msgstr "[%s] Home comprimate folosind gzip. Cache eliminat!" #: wp-cache.php:2221 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared." msgstr "Cache tot blog-ul dvs. a fost eliminat, ca plugin-ul observat o eroare pe pagina principală (aceasta descărcări arhivă). Pentru a verifica cache-ul, vă rugăm să vizitaţi această strnitsu %s." #: wp-cache.php:2228 #, php-format msgid "[%s] Front page is not correct! Please clear cache!" msgstr "[%s] Pagina Prima nu este corect. Vă rugăm să goliţi memoria cache!" #: wp-cache.php:2228 #, php-format msgid "Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, \"%2$s\"!" msgstr "A apărut o eroare pe pagina principală a blog-ul dvs. nu a fost detectat text cheie \"%2$s\". Pentru a corecta o greşeală, puteţi vizita această pagină %1$s şi clar manual memoria cache." #: wp-cache.php:2231 #, php-format msgid "[%s] Front page is not correct! Cache Cleared!" msgstr "[%s] Prima pagină este afişată cu o eroare! Cache eliminat!" #: wp-cache.php:2231 #, php-format msgid "The cache on your blog has been cleared because the front page of your site is missing the text \"%2$s\". Please visit %1$s to verify the cache has been cleared." msgstr "A apărut o eroare pe pagina principală a blog-ul dvs. nu a fost detectat text cheie \"%2$s\". Vizitaţi această pagină %1$s pentru a verifica cache." #: wp-cache.php:2236 #, php-format msgid "[%s] Front page check!" msgstr "[%s] Prima pagina a verifica!" #: wp-cache.php:2236 #, php-format msgid "WP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this." msgstr "WP Super Cache a verificat prima pagină a blog-ul dvs. Vă rugăm să vizitaţi %s dacă doriţi să dezactivaţi acest lucru." #: wp-cache.php:2279 msgid "Cannot update .htaccess" msgstr "Nu se poate actualiza. Htaccess" #: wp-cache.php:2279 #, php-format msgid "The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client." msgstr "Fişier %s.htaccess nu poate fi modificat de către Web Server. Vă rugăm să corectaţi acest lucru, folosind chmod sau comanda dvs. client FTP." #: wp-cache.php:2279 msgid "Refresh this page when the file permissions have been modified." msgstr "Reîmprospătare această pagină atunci când permisiunile pentru fisiere au fost modificate." #: wp-cache.php:2279 #, php-format msgid "Alternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):" msgstr "Alternativ, puteţi edita %s.htaccess fişier manual şi adăugaţi următorul cod (înainte de orice reguli WordPress):" #: wp-cache.php:2283 #, php-format msgid "To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccess" msgstr "Pentru a servi statice HTML server de fişiere dvs. trebuie să aibă corect mod_rewrite normele adăugat într-un fişier numit %s.htaccess" #: wp-cache.php:2284 msgid "You can edit the file yourself add the following rules." msgstr "Aveţi posibilitatea să editaţi fişierul singur adăuga următoarele reguli." #: wp-cache.php:2285 msgid " Make sure they appear before any existing WordPress rules. " msgstr "Asiguraţi-vă că ele apar înainte de orice reguli WordPress existent." #: wp-cache.php:2293 msgid "Update Mod_Rewrite Rules" msgstr "Update mod_rewrite reguli" #: wp-cache.php:2389 #, php-format msgid "[%1$s] Cache Preload Started" msgstr "[%1$s] Cache preîncărcate începute" #: wp-cache.php:2391 #, php-format msgid "[%1$s] Refreshing posts from %2$d to %3$d" msgstr "[%1$s] Refreshing mesajele de la %2$d la %3$d" #: wp-cache.php:2402 #, php-format msgid "[%1$s] %2$d posts refreshed" msgstr "[%1$s] %2$d mesaje împrospătat" #: wp-cache.php:2402 msgid "Refreshed the following posts:" msgstr "Actualizat următoarele posturi:" #: wp-cache.php:2411 #, php-format msgid "Scheduling next preload refresh in %d minutes." msgstr "Programarea minute refresh preload următoare în %d." #: wp-cache.php:2421 #, php-format msgid "[%s] Cache Preload Completed" msgstr "[%s] Cache preîncărcate Completed" #: wp-cache.php:2421 msgid "Cleaning up old supercache files." msgstr "Curăţarea fişierele vechi supercache." #: wp-cache.php:2462 #, php-format msgid "[%s] Preload may have stalled." msgstr "[%s] preîncărcate poate fi stagnat." #: wp-cache.php:2462 #, php-format msgid "" "Preload has been restarted.\n" "%s" msgstr "" "Preîncărcate a fost repornit.\n" "%s" #~ msgid "" #~ "Scroll down this page and click the Update Mod_Rewrite Rules button." #~ msgstr "" #~ "Пролистайте страницу вних и нажмите кнопку Обновить правила " #~ "Mod_Rewrite." #~ msgid "WP Super Cache Manager" #~ msgstr "Управление плагином WP Super Cache" #~ msgid "Why your configuration may not be changed" #~ msgstr "Почему конфигурации не могут быть изменены" #~ msgid "Why" #~ msgstr "Почему" #~ msgid "ON" #~ msgstr "ВКЛ" #~ msgid "WP Cache and Super Cache enabled" #~ msgstr "Плагины WP Cache и Super Cache включены" #~ msgid "HALF ON" #~ msgstr "РАБОТАЕТ НАПОЛОВИНУ" #~ msgid "Super Cache Disabled, only legacy WP-Cache caching." #~ msgstr "Плагин Super Cache отключен, работает только кэшировани WP-Cache" #~ msgid "OFF" #~ msgstr "ВЫКЛ" #~ msgid "WP Cache and Super Cache disabled" #~ msgstr "Плагины WP Cache и Super Cache отключены" #~ msgid "" #~ "Cache rebuild. Serve a supercache file to anonymous users while a new " #~ "file is being generated. Recommended for very busy websites with " #~ "lots of comments. Makes \"directly cached pages\" and \"Lockdown mode\" " #~ "obsolete." #~ msgstr "" #~ "Восстановление кэша. При включенной опции, гости сайта будут получать " #~ "старые страницы из плагина Super Cache, пока формируются новые. " #~ "Рекомендуется использовать данную опцию только для очень " #~ "посещаемых блогов, где много комментариев. После включения опции в " #~ "настройках \"прямое кэширование страниц\" и \"закрытый режим\" нет нужды " #~ "(они устаревают)" #~ msgid "" #~ "List the newest cached pages (may be expensive to run on busy sites, use " #~ "with caution.)" #~ msgstr "" #~ "Создавать список новых кэшированных страниц (использовать на свой страх и " #~ "риск, может затормозить сайты с большим количеством посетителей)" #~ msgid "" #~ "%1$s really makes your blog go faster. Make it go faster* by " #~ "buying me an Amazon gift card! Make it out to \"%3$s" #~ "\" for whatever amount you want. Every penny helps!" #~ msgstr "" #~ "%1$s действительно ускоряет Ваш блог. Вы можете сделать его еще " #~ "быстрее*, купив мне подарочную карту сервиса " #~ "Amazon! Можете выбрать \"%3$s\" любое значение, какое хотите. Каждая " #~ "копейка поможет мне!" #~ msgid "" #~ "If Amazon isn’t your thing, there’s also PayPal. Click the " #~ "\"Donate\" button below or take a quick peek at my wishlist." #~ msgstr "" #~ "Если Вы не хотите иметь дело с Amazon , то можно сделать пожертвование " #~ "через PayPal. Нажмите кнопку \"Пожертвовать\" или выберите подарок для " #~ "меня из моего списка желаний." #~ msgid "Thanks in advance!" #~ msgstr "Заранее благодарю!" #~ msgid "" #~ "Ok, it won’t go any faster but you’ll make this plugin author " #~ "very happy!" #~ msgstr "" #~ "Ладно, он не будет быстрее, но Вы все равно сделаете автора плагина очень " #~ "счастливым!" #~ msgid "Don’t show me this again." #~ msgstr "Не показывать больше это сообщение." #~ msgid "Hide" #~ msgstr "Спрятать" #~ msgid "" #~ "He blogs at %1$s and posts photos at %2$s. He would really appreciate a " #~ "donation to encourage development of this plugin." #~ "
    Even a penny will help." #~ msgstr "" #~ "Блог автора - %1$s, фотоблог - %2$s. Автор плагина будет благодарен любой " #~ "поддержке от Вас.
    Даже копейка может помочь в " #~ "его работе." #~ msgid "Super Cache Compression" #~ msgstr "Сжатие кэша Super Cache" #~ msgid "Compression is enabled by default when in HALF ON mode." #~ msgstr "" #~ "Сжатие кэша отключено по умолчанию в режиме РАБОТАЕТ НАПОЛОВИНУ." #~ msgid "Super Cache compression is now disabled." #~ msgstr "Сжатие кэша Super Cache теперь отключено." #~ msgid "Super Cache compression is now enabled." #~ msgstr "Сжатие кэша Super Cache теперь включено." #~ msgid "Update Compression" #~ msgstr "Обновить настройки сжатия" #~ msgid "Debug Settings" #~ msgstr "Параметры отладки" #~ msgid "" #~ "

    WP_CACHE constant in wp-config.php set to false

    The WP_CACHE " #~ "constant is defined in your wp-config.php but must be set to true, not " #~ "false for this plugin to work correctly.

    " #~ msgstr "" #~ "

    Значение для WP_CACHE в конфигурационном файле WordPrees wp-config." #~ "php установлено на \"false\"

    Чтобы плагин заработал, значение " #~ "WP_CACHE в wp-config.php нужно поставить на \"true\".

    " #~ msgid "You must edit the file yourself add the following rules." #~ msgstr "" #~ "Вы должны вручную отредактировать файл и добавить необходимые правила." wp-cache-base.php000066600000002366152133035240007665 0ustar00\'\"\r\n\t\(\)]/', '', $_SERVER['REQUEST_URI'] ) ); if( strpos( $request_uri, '/', 1 ) ) { if( $base == '/' ) { $blogcacheid = substr( $request_uri, 1, strpos( $request_uri, '/', 1 ) - 1 ); } else { $blogcacheid = str_replace( $base, '', $request_uri ); if ( $blogcacheid != '' ) $blogcacheid = substr( $blogcacheid, 0, strpos( $blogcacheid, '/', 1 ) ); } if ( '/' == substr($blogcacheid, -1)) $blogcacheid = substr($blogcacheid, 0, -1); } $blogcacheid = str_replace( '/', '', $blogcacheid ); } } ?>