| 开发者 | tepee |
|---|---|
| 更新时间 | 2026年10月31日 07:29 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[tepee_for_helloasso] shortcode for the classic editor, page builders and widgets.[tepee_for_helloasso] shortcode.No. Tepee for HelloAsso is an independent plugin that reads public data from the HelloAsso API. "HelloAsso" is the name of the platform it works with, and is used here only to say so.
They do different jobs, and both are useful. The plugin published by HelloAsso embeds HelloAsso's own forms (ticketing, donations, memberships, crowdfunding) into a page, one campaign at a time. Tepee for HelloAsso reads your organization's public events through the HelloAsso API and shows them as an agenda (list or cards) that you can style, and that is refreshed regularly without you having to create one block per event. If you want a donation or membership form on a page, HelloAsso's plugin is the right tool. If you want an events listing that keeps itself up to date, this one is.
Yes. They do not depend on each other, and we have run them side by side on the same site and the same page.
Yes. You need a Client ID and a Client Secret, created once in your organization's HelloAsso back office, under "Integrations and API". That is a few more steps than pasting an organization name, but it lets the plugin read your event data directly and keep it up to date.
No. Registration and payment stay on HelloAsso: the "Register" button opens your event's HelloAsso page in a new tab.
Public events (ticketing campaigns). Donation, membership, shop and crowdfunding campaigns are not displayed; HelloAsso's own plugin covers those.
In your HelloAsso back office, open "Integrations and API" to get your Client ID and Client Secret. The organization slug is the identifier in your public HelloAsso URL: https://www.helloasso.com/associations/YOUR-SLUG.
No. All calls to the HelloAsso API are made server-side. The secret is never sent to the browser, not even on the settings page.
Yes: TFHA_CLIENT_ID, TFHA_CLIENT_SECRET, TFHA_ORG_SLUG, TFHA_CACHE_TTL and TFHA_MAX_EVENTS. These constants take priority over the settings page, and the related fields are locked.
From your site: at each refresh, the plugin saves an optimized copy of each image in your uploads folder, so visitors never contact the HelloAsso image server (blocked by some networks and VPNs). If a download fails, the HelloAsso image is shown instead. On hosting spread over several servers without a shared uploads folder, add define( 'TFHA_LOCAL_IMAGES', false ); to wp-config.php to always use the HelloAsso images.
The real display, with your events (from the last refresh), your settings and your colors. It is not clickable in the editor, so that a click selects the block, and very long displays are shortened. The complete, interactive display appears on the published page.
No. It sets no cookies, stores no data about visitors and sends no statistics anywhere. The only data stored on your site is the public information about your events (cached), and your HelloAsso API credentials.
Yes. After each refresh of the events or each settings change, the cache of the pages is cleared automatically for the main cache plugins (option in the Advanced tab).
The events already retrieved stay displayed from the cache, and the Dashboard shows the error. The plugin is then updated, when possible, to follow the change. See "Third-party service and limitation of liability" in the description.
The free plugin is complete on its own, with no limit in time or in number of events. A separate PRO add-on, sold on tepee.dev, adds calendar views and a few extras (see "PRO add-on" in the description).
Yes. Available hooks:
tfha_events (filter): the events displayed by an instance, after period filtering.tfha_render_config (filter): the configuration passed to the display.tfha_jsonld_event (filter): the schema.org object of an event; return an empty value to leave the event out.tfha_after_refresh (action): fired after a manual or scheduled refresh, with the events, the context and whether the data changed.shortcode_atts_tepee_for_helloasso (WordPress core filter): the shortcode attributes.tfha_settings_defaults, tfha_sanitize_setting, tfha_form_sections (filters): add your own settings.tfha_views, tfha_i18n, tfha_style_vars, tfha_display_settings (filters): add views, texts and CSS variables to the display. In JavaScript, window.tfhaExtensions receives the display class (loaded before the plugin's script).tfha_block_attributes, tfha_upcoming_block_attributes (filters) and the tfha.* JavaScript hooks (wp.hooks): extend the blocks.tfha_admin_* actions and tfha_dashboard_cards, tfha_shortcode_doc (filters): add rows, sections and cards to the settings pages.