WordPress.org

New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Stable Readme (latest release): Portuguese (Portugal)

Filter ↓ Sort ↓ All (524) Translated (1) Untranslated (500) Waiting (29) Fuzzy (0) Warnings (2)
1 2
Prio Original string Translation
A very fast caching engine for WordPress that produces static html files. Um mecanismo de cache muito rápido para WordPress que produz arquivos HTML estáticos. Details
A very fast caching engine for WordPress that produces static html files.
Comment

Short description.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:41:13 GMT
Translated by:
tiagopmartins
Priority of the original:
high
Preload as many posts as you can and enable "Preload Mode". Garbage collection of old cached files will be disabled. 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. Even with preload mode enabled cached files will still be deleted when posts are modified or comments made. Da mesma forma, pré-carregar o máximo de mensagens que você pode e ativar o "Modo Preload". A coleta de lixo ainda vai ocorrer, mas isso não afetará os arquivos de pré-carregados. Se você não se preocupam com widgets da barra lateral de actualização muitas vezes definir o intervalo de pré-carga para 2880 minutos (2 dias) para que todos os seus posts não são recached muito frequentemente. Quando o pré-carregamento ocorre os arquivos de cache para o cargo sendo atualizada é excluído e, em seguida, regenerado. Depois de uma coleta de lixo de todos os arquivos antigos é realizada para limpar cache de envelhecer files. Com o pré-carregamento de arquivos em cache ainda serão eliminados quando as mensagens são feitas ou editados ou comentários feitos. Details
Preload as many posts as you can and enable "Preload Mode". Garbage collection of old cached files will be disabled. 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. Even with preload mode enabled cached files will still be deleted when posts are modified or comments made.
Comment

Found in description paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:41:42 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
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. If Supercaching is disabled and 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". WPCache cached files will have the header, "WP-Super-Cache: Served WPCache cache file". 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. The pagespeed module for Apache may cause problems when testing. Disable it if you notice any problems running the cache tester. Ativar a depuração na página de configurações do plugin e carregar o arquivo de log em uma nova aba do navegador. Em seguida, ver o seu blog enquanto estiver conectado e desconectado. Você deve ver atividade no registro. Ver a fonte de qualquer página de seu site. Quando uma página é criada pela primeira vez, você verá o texto "página dinâmica gerada em XXXX segundos." e "página gerada por WP-Super-Cache em AAAA-MM-DD HH em cache: MM: SS" no final do código fonte. Na recarga, uma página em cache irá mostrar a mesma hora de modo aguarde alguns segundos antes de verificar. No modo de cache legado, se você tiver a compactação ativada, o texto "Compression = gzip" será adicionado. Se a compressão é desativada ea página é servido como um arquivo HTML estático, o texto "super cache" será adicionado. A única outra maneira de verificar se o seu arquivo em cache foi servido por script PHP ou do cache estática é por olhar para os cabeçalhos HTTP. PHP em cache páginas terão o cabeçalho "WP-Super-Cache: arquivo supercache Servido a partir de PHP". Arquivos legados em cache terá o cabeçalho, "WP-Super-Cache: Servido arquivo de cache legado". Eu usei extensão os <a href="https://addons.mozilla.org/en-US/firefox/addon/3829"> Vivo cabeçalhos HTTP </a> para o Firefox para examinar os cabeçalhos. Você também deve verificar o seu diretório de cache em wp-content / cache / supercache / hostname / para files. de cache estática Se as regras de plugin estão faltando em seu arquivo .htaccess, o plugin irá tentar servir a página super em cache se ele é encontrado. O cabeçalho "WP-Super-Cache: Servido arquivo supercache de PHP" se isso acontecer. Details
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. If Supercaching is disabled and 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". WPCache cached files will have the header, "WP-Super-Cache: Served WPCache cache file". 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. The pagespeed module for Apache may cause problems when testing. Disable it if you notice any problems running the cache tester.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:43:04 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
"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)" "Seu blog não suporta o armazenamento em cache do cliente (não 304 resposta a Se-Modified-Since)." "O feed não suporta o armazenamento em cache (não 304 resposta a Se-Modified-Since)" Details
"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)"
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:43:37 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
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. Há um filtro WordPress regular também. Use a "do_createsupercache" filtro para personalizar os controlos efectuados antes de armazenamento em cache. O filtro aceita um parâmetro. A função de saída de wp_cache_get_cookies_values ​​do WP-Cache (). Details
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.
Comment

Found in description paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:44:38 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
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 <a href="http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php">dynamic-cache-test.php</a> 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 <a href="https://odd.blog/y/6j">this post</a> for a more technical and longer explanation. To execute WordPress functions you must enable the 'Late init' feature on the advanced settings page. WP Super Cache 1.4 introduziu um filtro chamado cacheAction wpsc_cachedata. A página em cache a ser exibido passa por esse filtro e permite a modificação da página. Se a página contém uma marca de marcador de posição o filtro pode ser utilizado para substituir a etiqueta com o seu html. gerado dinamicamente A função que ganchos para o filtro wpsc_cachedata deve ser colocado em um arquivo no WP Super Cache plugins pasta a menos que você use o recurso late_init. Um exemplo plugin está incluído. Editar <a href="http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php">dynamic-cache-test.php</a> para ver os exemplos de code. Existem duas funções exemplo lá. Há uma função simples que substitui a string (ou tag) você definir quando a página em cache é servido. A outra função exemplo usa um buffer de saída para gerar o conteúdo dinâmico. Devido a uma limitação na forma como funciona o código PHP buffer de saída deve ser executado antes do filtro wpsc_cachedata é atingido, pelo menos para quando uma página é armazenada em cache. Não importa quando servir páginas em cache. Consulte <a href="http://z9.io/y/6j"> este post para um explanation. </a> mais técnica e mais Para executar funções WordPress você deve habilitar o recurso "Tarde de init 'na página de configurações avançadas. Details
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 <a href="http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php">dynamic-cache-test.php</a> 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 <a href="https://odd.blog/y/6j">this post</a> for a more technical and longer explanation. To execute WordPress functions you must enable the 'Late init' feature on the advanced settings page.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:43:26 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
Supercache doesn't support 304 header checks in Expert mode but does support it in Simple 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 https://redbot.org/ for further analysis. Não SuperCache não suporta 304 verificações de cabeçalho no modo mod_rewrite, mas suporta-lo no modo PHP. Este é o cache feito pelo seu navegador, não o servidor. É uma verificar o seu navegador faz para pedir o servidor se uma versão atualizada da página atual está disponível. Se não, ele não baixar a versão antiga novamente. A página ainda está em cache pelo seu servidor, não apenas por browsers. dos seus visitantes Experimente o motor de Cacheabilidade em http://www.ircache.net/cgi-bin/cacheability.py ou http://redbot.org/ para análise posterior. Details
Supercache doesn't support 304 header checks in Expert mode but does support it in Simple 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 https://redbot.org/ for further analysis.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:43:48 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
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. Você pode ter os "claros todos os arquivos armazenados em cache quando novas mensagens são feitas" conjunto de opções. Limpando esses arquivos pode levar tempo mais os visitantes vão agora ser visitar páginas fora do cache. Você está usando campanha do Google Analytics com utm_source na url? Essas páginas não são armazenados em cache. Veja a pergunta: "Como devo usar melhor as ferramentas de monitoramento utm_source no Google Analytics com este plugin" acima para saber como usá-los properly. Páginas em cache tem que ser atualizado quando as mensagens são feitas. Talvez o seu servidor simplesmente não está à altura da tarefa de servir a quantidade de tráfego que você começa. Habilite o recurso "cache reconstruir" que isso possa ajudar Details
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.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:44:00 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
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. Você tem a opção de "apagar todos os arquivos armazenados em cache quando novos artigos são criados". Limpar esses ficheirosos pode levar algum tempo e os seus visitantes vão agora visitar páginas sem cache. Você está usando a campanha do Google Analytics com utm_source na url? Essas páginas não são armazenados em cache. Veja a pergunta: "Como devo usar melhor as ferramentas de monitoramento utm_source no Google Analytics com este plugin" acima para saber como usá-los adequadamente. Páginas em cache tem que ser atualizadas quando os artigoss são feitos. Talvez o seu servidor simplesmente não esteja à altura da tarefa de gerir a quantidade de tráfego que você recebe. Habilite o recurso "reconstruir a cache" talvez possa ajudar. Details
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.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-02-12 05:39:23 GMT
Translated by:
FLopes
Priority of the original:
normal
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. Também há um filtro WordPress normal. Use o filtro "do_createsupercache" para personalizar os controlos efectuados antes de armazenamento em cache. O filtro aceita um parâmetro. A função de saída do WP-Cache wp_cache_get_cookies_values(). Details
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.
Comment

Found in description paragraph.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-02-12 06:08:15 GMT
Translated by:
FLopes
Priority of the original:
normal
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. A pasta cache não pode ser colocado em um NFS ou Samba ou compartilhamento NAS. Tem que estar em um disco local. Bloqueio de arquivos e excluir arquivos expirados não funcionará corretamente a menos que a pasta de cache está na máquina local. Details
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.
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:44:55 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
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. Try disabling supercache mode. Caching não funciona. O timestamp no meu blog continua a mudar quando eu recarregar. Verifique se o caminho no seu .htaccess regras partidas onde o diretório supercache é. Você pode ter que codificá-lo. Ou usar o plugin em PHP ou legado modo de armazenamento em cache. Details
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. Try disabling supercache mode.
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:45:22 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings-&gt;Permalink page and saving that form again. Após a desinstalação, os permalinks pode quebrar se você remover as regras de mod_rewrite WordPress também. Regenerar essas regras, visitando o Configurações- & gt; Permalink página e salvar essa forma novamente. Details

Original waiting 1 warning

After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings-&gt;Permalink page and saving that form again.
Comment

Found in description list item.

Warning: Translation should not end on newline.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-01-09 01:46:17 GMT
Translated by:
tiagopmartins
Priority of the original:
normal
The "white screen of death" or a blank page when you visit your site is almost always caused by a PHP error but <a href="http://www.johnberns.com/2010/03/19/wp-super-cache-blank-page-problem-fixed/">it may also be caused by APC</a>. Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache. A "tela branca" ou uma página em branco quando você visitar o seu site é quase sempre causada por um erro de PHP, mas <a href="http://www.johnberns.com/2010/03/19/wp-super-cache-blank-page-problem-fixed/"> também pode ser causada por APC </a>. Desativar essa extensão PHP se você tiver problemas e substituir com eAccelerator ou Xcache. Details
The "white screen of death" or a blank page when you visit your site is almost always caused by a PHP error but <a href="http://www.johnberns.com/2010/03/19/wp-super-cache-blank-page-problem-fixed/">it may also be caused by APC</a>. Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache.
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-02-12 05:41:57 GMT
Translated by:
FLopes
Priority of the original:
normal
After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings-&gt;Permalink page and saving that form again. Após a desinstalação, os permalinks podem quebrar se você remover também as regras de mod_rewrite no WordPress. Para repor essas regras visite a página Configurações- & gt;Permalink e guardar novamente. Details
After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings-&gt;Permalink page and saving that form again.
Comment

Found in description list item.

You have to log in to edit this translation.

Meta

Status:
waiting
Date added:
2016-02-12 05:47:16 GMT
Translated by:
FLopes
Priority of the original:
normal
1 2
Legend:
Current
Waiting
Rejected
Fuzzy
Old
With warnings

Export as