| 开发者 | farowp |
|---|---|
| 更新时间 | 2026年11月10日 01:58 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
uploads/encadena-sif-certs/, and its
password is encrypted too: it is read from the ENCASI_CERT_PASS constant in wp-config.php when you define it, or
from the encrypted copy the plugin keeps next to the certificate./wp-content/plugins/, or install it from the zip.define('ENCASI_CERT_PASS', '…'); to wp-config.php and upload your .p12.guia/GUIA-DE-INSTALACION.pdf and
guia/INSTALL-GUIDE.pdf. It covers the two modes, the two environments, the ten-minute check and what to do
when something does not add up.No. This covers the billing record system (Veri*factu). Business-to-business electronic invoicing is a different regulation (Law 18/2022 and Royal Decree 238/2026).
There is no such homologation. The manufacturer signs a responsible declaration (art. 15 RRSIF), which is reproduced inside the plugin, in the Help tab.
Settings are removed, billing records are not: the law requires keeping them.
It issues and chains records but cannot submit them. The panel warns about it in the header and in the summary.
Only to the two services described in External services: the AEAT endpoint you select (test or production), and only if you enable it, your own Telegram bot. Nothing else leaves the site.
index.php left in the data folder by an earlier version is rewritten empty on upgrade, not
only on a fresh install. The folder keeps its .htaccess with Require all denied.uploads no longer writes a non-empty index.php. It was the last
place doing it (includes/class-encasi-remision.php): the directory protection file is now created empty
(0 bytes), which is the only form the guidelines allow. The folder keeps its .htaccess with Require all denied, so nothing inside can be listed or fetched.ENCASI_VERSION was still 1.4.6, so the panel, the record header and the
AEAT submission reported an older version than the release. It now follows the plugin version.index.php with content. It is created empty, which is the only form the directory allows; the folder keeps its .htaccess (deny) and an empty index.html, so the certificate stays unreachable from the browser.VFRUNTIME and VFRUNTIME_VERSION, are now ENCASI_RUNTIME and ENCASI_RUNTIME_VERSION. No behaviour changes: it is the same runtime marker, renamed as the review guidelines require.wp_enqueue_script() / wp_add_inline_script(): no raw <script> tags are printed.esc_html, esc_attr, esc_url, wp_kses_post).wp_remote_post()); the client
certificate is attached with the http_api_curl hook.uploads/encadena-sif-certs/, not in wp-content/; the file of an older installation
is moved there automatically on the first upload or on the first request.<Fault>) are stored as rejections with their code and reason.