| 开发者 | wptechnology |
|---|---|
| 更新时间 | 2026年10月9日 05:43 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
.ics file for whoever does not click.[aero_board] or [aero_agenda] shortcode, the "Operations board" and "Agenda" blocks in the block editor, or the same two elements in Avada Builder under "WPTechnology". Nothing to configure: the Avada elements appear only when Fusion Builder is active.Yes, and it steps aside for them. On a site running either one, aero-courses follows the language they decide for the request, not the one the visitor happens to have in their profile, and course, location and programme texts are translated in their own string translation screen, alongside the rest of the site. The plugin registers those strings for you; you will find them under the "aero-courses" group.
Translations you had already typed into the plugin's own language tabs are not lost: they keep being used wherever Polylang or WPML has nothing yet. If you would rather keep using the built-in tabs, the aero_courses_delegate_translations filter turns the delegation off without uninstalling anything.
E-mail templates stay in the plugin's own editor: a message body is a document with placeholders, not a string, and a string translation screen is a poor place to write one.
Without either plugin, aero-courses translates content on its own, with nothing to install.
Yes. When Fusion Builder is active, aero-courses registers two elements, "Operations board" and "Booking agenda", in the "WPTechnology" category, with the same options as the shortcode attributes. They are not a second implementation: each element hands its options straight to the shortcode, so what Avada renders is what the shortcode renders. If Fusion Builder is not installed, nothing is registered and nothing is loaded.
No. aero-courses is self-contained: it stores its own data in dedicated database tables and does not depend on Events Manager, The Events Calendar or any other calendar plugin.
Booking is per session. A student can book any number of sessions across any number of modules, as long as each session still has room.
The booking endpoint refuses the request as soon as capacity is reached; the front-end views show the session as full rather than letting a student attempt to book it.
Yes, as many as the school teaches. PPL(H), PPL(A), CPL, ATPL and IR can run side by side, each with its own modules, semesters and students, and there is no cap on how many are active at once.
The interface strings are fully translatable with standard WordPress tools (Loco Translate, or community translations on translate.wordpress.org). Course, location and e-mail content can be translated language by language directly in the plugin, independently of the interface language.
Your schedule, your students and your bookings never leave your site. Nothing about your school is sent anywhere. The plugin bundles the Freemius SDK, which contacts freemius.com for two things and two only: checking a Premium licence and, if you agreed to it when you activated the plugin, anonymous usage statistics such as your WordPress version. You are asked before anything is sent, you may decline, and declining changes nothing about how the plugin works. On the free version with no licence, the plugin runs without contacting anyone. See https://freemius.com/privacy/.
Aero\Courses\Api.[aero_progress] shortcode shows nothing to students (administrators see a short note in its place), and the agenda no longer shows an "Add to calendar" menu.Removal: its former file name, includes/Uninstall.php, was mistaken for a WordPress uninstall.php by the Freemius deployment check. Nothing changes in what it does; uninstalling still runs through the Freemius after_uninstall hook.aero_core_menu_base filter.th { display: block }, which takes a header cell out of the table's column algorithm: seven clean headers and seven clean cells rendered as nine columns, three of them empty. You do not get to choose the plugins a school installs, so the tables no longer rely on the browser default alone.post_id column no longer reports an empty site: the column is looked for before it is asked for. A failed query returns nothing, which the screen would have read as "nothing to import".plugin_icon filter and lives in the plugin's own assets, so it survives every SDK update.uninstall.php. WordPress executes that file instead of the uninstall hook, which left Freemius believing the plugin was still installed. The cleanup is unchanged; only where it hangs from.