Description
Più valore al sito della tua impresa. Più vicinanza alle famiglie.
Con annuncifunebri per l’impresa, gli annunci di AnnunciFunebri.it trovano spazio anche nel tuo sito WordPress. Le famiglie possono consultare le informazioni sulle cerimonie, condividere un ricordo e accedere ai servizi disponibili, in un ambiente che porta il nome della tua impresa.
Un sito utile alle famiglie ogni giorno
Il tuo sito può diventare un punto di riferimento anche per chi cerca un annuncio, vuole conoscere l’orario di una cerimonia o desidera esprimere la propria vicinanza.
Ogni annuncio raccoglie in una pagina dedicata le informazioni e i contenuti disponibili. Un’esperienza ordinata, che aiuta i visitatori a trovare ciò di cui hanno bisogno anche da smartphone.
Meno lavoro per la tua impresa
Gli annunci pubblicati sulla piattaforma arrivano anche sul tuo sito, senza doverli ricopiare uno a uno. Dedichi meno tempo alla gestione delle pagine e mantieni le informazioni collegate alla stessa fonte.
Puoi dare spazio agli ultimi annunci già in homepage, rendendoli subito accessibili a chi visita il sito.
Più modi per esprimere vicinanza
Accanto all’annuncio, le famiglie possono trovare strumenti per partecipare e ricordare:
- Un messaggio di cordoglio, per far sentire la propria presenza.
- Una fotografia, per condividere un ricordo.
- La diretta della cerimonia, per chi non può essere presente.
- Un omaggio floreale, da scegliere attraverso il servizio collegato.
- Un gesto di solidarietà, seguendo le indicazioni per opere di bene e donazioni.
La disponibilità di queste funzioni dipende dai servizi attivati per l’impresa e dal singolo annuncio.
Una presenza online che ti rappresenta
Gli annunci entrano nel sito della tua impresa con una presentazione curata e possibilità di personalizzazione. Puoi scegliere una soluzione pronta all’uso oppure, in base al servizio attivato, adattare il layout all’identità del tuo sito con Elementor, i blocchi WordPress o template personalizzati.
Il risultato è un percorso più coerente per le famiglie, che ritrovano la tua impresa anche quando cercano informazioni e servizi online.
Annunci pensati per essere trovati
Ogni annuncio dispone di una pagina dedicata, con contenuti organizzati per essere letti anche dai motori di ricerca. Una base utile per rendere gli annunci del tuo sito più facilmente reperibili online.
Come iniziare
Il plugin è pensato per i siti WordPress delle imprese che utilizzano AnnunciFunebri.it/Cas-Per. Per utilizzarlo occorrono l’accesso al servizio e una chiave API fornita per la tua impresa. Una volta installato e collegato, puoi scegliere la presentazione e verificare quali funzioni mettere a disposizione delle famiglie.
Porta gli annunci sul tuo sito e rendilo un servizio in più per le famiglie. Per informazioni sull’attivazione, visita AnnunciFunebri.it.
Routes, Gutenberg, Elementor, and shortcodes
The public URLs are virtual routes handled by the plugin. You do not need to create WordPress pages for:
/annunci-funebri/annuncio/{comune}/{slug}/diretta/{slug}
The af_imp_template route templates allow layout editing with Elementor while keeping the public URLs virtual.
Gutenberg blocks are available in the AnnunciFunebri inserter category for normal WordPress pages:
- notice archive;
- latest notices slider;
- single notice;
- notice search;
- main single-notice components such as name, photo, opening, quote, text, closing, ceremonies, and interactions.
Shortcodes are provided as technical fallbacks:
[af_imp_annunci]renders the notice archive;[af_imp_ultimi_annunci]renders the latest notices slider;[af_imp_annuncio]uses the dynamic route slug when used inside/annuncio/{comune}/{slug};[af_imp_annuncio slug="notice-slug"]renders one notice inside a manual page;[af_imp_diretta]uses the dynamic route slug when used inside/diretta/{slug};[af_imp_diretta slug="notice-slug"]renders a live streaming view inside a manual page.
External Services
This plugin connects to the AnnunciFunebri.it/Cas-Per service.
Default API endpoint:
https://api.cas-per.it/api
Local or alternative environments may be configured through project-specific settings when available.
The service is used to:
- validate the API key;
- retrieve the company profile linked to the API key;
- retrieve the declarative presentation profile linked to the API key;
- automatically synchronize that profile through signed service notifications and a 15-minute WP-Cron recovery check;
- retrieve notice lists, single notices, and related data;
- count notice views from the browser, including pages served from customer-site caches;
- retrieve and submit condolences;
- create photo condolence albums, upload photos, finalize albums, and verify albums;
- retrieve flower catalogs when enabled;
- create flower orders and initialize payment when the backend returns the required Stripe data;
- send operational health/status data only when the administrator explicitly enables that option.
Data sent to the service:
- API key, only through the
X-API-KeyHTTP header; - WordPress callback URL for automatic configuration notifications (no extra user credentials);
- notice slug, archive filters, and pagination parameters;
- public notice hash, source
plugin, and a random visitor identifier for view counting; - data entered by visitors in condolence forms;
- files and metadata entered by visitors in photo condolence forms;
- flower order data entered by visitors when the flower module is enabled;
- minimal operational health/status payload, only when enabled.
No API key or private company identifier is exposed to the presentation JavaScript.
The API key is never sent in query strings and is never included in the health/status payload.
Service terms:
https://www.annuncifunebri.it/termini-di-servizio/
Service privacy policy:
https://www.iubenda.com/privacy-policy/29932518
Service cookie policy:
https://www.iubenda.com/privacy-policy/29932518/cookie-policy<h3>Payments</h3>
The plugin does not ask for Stripe secret keys and does not store Stripe configuration.
When the flower module is enabled, payment is initialized by the AnnunciFunebri.it/Cas-Per backend/API. Card data is handled in the browser by Stripe using publishable payment data returned by the backend. The company private API key and Stripe Connect configuration stay on the backend/API.
The file https://js.stripe.com/v3/ is loaded only in the flower order flow, after the backend has created an order that requires browser payment and has returned a Stripe publishable key with a client secret. If the backend returns a checkout URL, the plugin redirects to checkout without exposing inline Stripe data.
Stripe terms: https://stripe.com/legal
Stripe privacy policy: https://stripe.com/privacy
Privacy
The plugin lets administrators customize the privacy text shown next to public form consents. Privacy acceptance can be required in the plugin settings.
The health/status module is disabled by default. When enabled, it sends only minimal operational data:
- site URL;
- plugin version;
- WordPress and PHP versions;
- token validation status;
- sitemap URL;
- rewrite/cache version;
- detected builder, SEO plugin, and cache plugin status;
- timestamp and last report status.
The health/status payload does not include the API key, administrator email addresses, visitor personal data, or full stack traces.
Notice detail and streaming views send a browser request to the public AnnunciFunebri.it/Cas-Per visit endpoint without an API key. A random identifier is stored in the hosting site’s localStorage under af_visitor and reused across visits. The service deduplicates the same visitor and notice for 2 minutes. The request also exposes the visitor’s IP address and browser HTTP headers to the service. If localStorage is blocked, an identifier is generated for the current page only. Site owners should include this processing in their privacy information.
On uninstall, the plugin removes its settings, derived connection and presentation data, rewrite markers, last health report, and scheduled health event. Technical route-template posts are intentionally preserved because they may contain Elementor or Gutenberg customizations. Administrators who want to remove them should delete those templates before uninstalling the plugin.
Cache, CDN, and SEO
The plugin uses WordPress transients with namespaced cache keys and a non-reversible token fingerprint. The raw API key is not stored in cache keys.
The sitemap and public cache are invalidated when relevant routes, visual settings, templates, labels, or cache settings change. The plugin can notify supported cache/CDN integrations and bypass aggressive cache for live streaming and sitemap routes.
View counting uses a separate JavaScript beacon and does not require disabling the customer’s HTML cache. It requires the AF-1270 backend visit endpoint and workers to be deployed first. Purge existing page/CDN caches once when installing this change so cached pages include the script. The plugin sends X-AF-Visite: client on detail API requests to avoid counting both the server render and the browser view. Preview pages are excluded. Browser blocking of JavaScript or network requests can still prevent a view from being recorded.
SEO metadata is generated server-side. Compatibility adapters are included for Yoast SEO, Rank Math, All in One SEO, SEOPress, and The SEO Framework.
Installation
- Upload the
annuncifunebri-impresafolder towp-content/plugins. - Activate the plugin in WordPress.
- Open
AnnunciFunebri > Settings. - Enter the API key.
- Use
Save and refresh company datato validate the key and read the company profile. - Review routes, templates, privacy text, and public labels.
FAQ
Do I need to create a WordPress page for `/annunci-funebri`?
No. The main public URLs are virtual plugin routes. Manual pages and shortcodes are only needed when you want to place AnnunciFunebri content inside another page.
Is the API key exposed on the public website?
No. Authenticated requests are handled by the WordPress server and use the X-API-Key HTTP header.
Is Elementor supported?
Yes. The plugin registers AnnunciFunebri Elementor widgets for archive, latest notices slider, single notice, and dynamic notice components. Route templates can be edited with Elementor.
Is Gutenberg supported?
Yes. The plugin registers dynamic server-side blocks for archive, latest notices slider, single notice, search, and the main single-notice components. Blocks use the same renderer as routes, Elementor widgets, and shortcodes.
Can I use Divi or WPBakery?
Native Divi and WPBakery adapters are planned. Until then, shortcodes are available as technical fallbacks.
Do I need to configure Stripe in the plugin?
No. Stripe and Stripe Connect are handled by the backend/API. The plugin only uses publishable payment data returned by the API when a browser payment flow is required.
Is the public credit shown automatically?
No. The “Powered by AnnunciFunebri.it” credit is disabled by default and is shown only after explicit administrator opt-in.
Changelog
1.0.12
- Count announcement and streaming views from cached pages using the public browser beacon, with backend deduplication of 2 minutes.
- Render charitable works supplied by the announcement API, including optional descriptions, logos, and donation links.
- Restore document titles on virtual block-theme pages and correct SEO metadata integration with Yoast, Rank Math, and SEOPress.
- Align code with WordPress coding standards and expand public form and SEO integration checks.
1.0.11
- Refresh the flower checkout nonce for the current WordPress session before creating an order, including on cached pages.
1.0.10
- Send flower delivery place and street separately and clarify the greeting card message.
1.0.9
- Format the funeral date and time consistently in the flower delivery form.
1.0.8
- Show all available product images in the flower detail modal.
- Prefill cemetery delivery details after the funeral when the announcement provides them.
1.0.7
- Keep Basic interaction forms clear of sticky headers and prevent ceremony cards and form fields from overlapping nearby content.
1.0.6
- Give Basic interaction forms the full announcement width instead of squeezing them into the action sidebar.
1.0.5
- Hide the pre-funeral delivery warning after the ceremony has passed.
1.0.4
- Update the FloreMoria delivery form and adapt flower choices to narrow template columns.
1.0.3
- Use the municipality province abbreviation for flower delivery and prevent editing it.
- Reject full province names instead of silently truncating them to two letters.
1.0.2
- Automatically synchronize presentation settings independently from API key saves.
- Add signed configuration notifications, callback ownership verification, periodic recovery and page cache invalidation.
1.0.1
- Completa la compatibilita Basic con JS2026 2026.09.8: opzioni responsive, colori, sezioni, streaming e cordogli.
1.0.0
- First stable release for the WordPress.org Plugin Directory.
- Added API-key presentation profiles with Basic, Pro, and Custom rendering modes.
- Added the shared JS2026 visual contract with server-side rendering, validated scoped CSS, and local progressive enhancement.
- Added local custom-template providers with version checks and safe fallback rendering.
- Invalidated public caches when presentation configuration changes and removed derived presentation data on uninstall.
- Display ended HLS recordings when available instead of keeping the waiting poster visible.
- Enforce streaming passwords before exposing YouTube, HLS, or external video sources.
0.1.18
- Regenerated Elementor template CSS after plugin updates so responsive widget dimensions are applied on public routes.
0.1.17
- Added a standalone Elementor streaming button with customizable labels for scheduled, live, and ended broadcasts.
0.1.16
- Added a compact mobile announcement filter with an accessible link for optional fields.
- Stacked announcement interaction buttons on mobile screens.
0.1.15
- Added essential Elementor style controls for streaming, forms, condolences, participations, photo galleries, social links, announcement cards, and the full detail widget.
- Added responsive slider card counts, spacing, navigation visibility, and arrow states.
0.1.0
- Initial scaffold with API client, server-side rendering, virtual routes, sitemap, shortcodes, widget, minimal Elementor integration, and tests.