| 开发者 | damasoft |
|---|---|
| 更新时间 | 2026年11月3日 04:16 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
No. FiscoSend's interface is currently Italian because the plugin targets Italian electronic-invoicing workflows. This readme is in English. An English WordPress installation does not change the plugin interface to English.
No. The provider portal is used to configure or renew the required password. For example, Aruba's two-step verification requires a mail-program password. The wizard links to the supported providers' official setup guides.
The default workflow is automatic after checks. You may instead choose review mode and confirm multiple eligible documents together. A problem with one order does not block other valid orders.
No. This version supports manual import and comparison with your PEC mailbox or official portal. Import alone does not verify a receipt. Confirming the comparison updates the outcome. A credit note requires the original invoice's outcome to be established first.
For rejection codes 00001 and 00002, after comparison with official evidence, the correction workflow can prepare a compliant new file name while retaining the document number, date, fiscal data and history. For 00002, first verify that the invoice has not already been acquired. Uncertain transmission does not authorise a resend.
No. It reads refunds recorded in WooCommerce and supported gateway indicators; it never issues a money refund. Incomplete data, uncertain fiscal attribution or unverified outcomes require review. Do not infer universal gateway compatibility or real-transaction testing from these checks.
Fiscal checks use amounts persisted in the order. Prepared documents keep their snapshot. Inconsistent fiscal amounts are blocked and explained. Universal compatibility with every rounding extension or precision setting is not claimed.
Operations require the appropriate WooCommerce capabilities and security tokens. Authorised administrators and shop managers can access the operations permitted to them. Ordinary customers cannot use the administrative screens or reserved document-download endpoints.
Back up the database and private document directory together. Encryption keys and settings are part of the database. A transferred or staging copy must not inherit live transmission: confirm the operating site again through the wizard after a move.
New archives use the damasoft-fiscosend folder under this site's runtime WordPress uploads directory. Files are authenticated encrypted data, not executable PHP. An actual same-site HTTP check must return 403 before document storage is enabled; unavailable loopback requests or servers that ignore the access rules fail closed. The plugin never creates or changes .htaccess, PHP guards or server configuration. Ask the hosting administrator to deny all direct HTTP access to that archive folder and its descendants before enabling invoicing. Do not make documents public to pass the check. Previously configured private archives and older containers remain supported in place; no existing evidence is moved or overwritten automatically. Temporary signing, PDF and ZIP work requires a private temporary directory outside the public web roots.
No. Open the setup wizard from FiscoSend when you are ready. Its operational indicator is limited to FiscoSend screens; the native Dashboard widget can be hidden with WordPress Screen Options.
No. Uninstall preserves documents and configuration under the documented retention policy, but removes the saved PEC credential. Make and verify a complete backup before removing or transferring the plugin.