I am curious how easily these Event Manager can work with Bookings Plugin. I am putting together a site that is mainly a year-round campsite reservation system for a property that also hosts events on occasion (concerts, festivals, corporate retreats, etc.). Basically, I am looking for something that can combine the two options seamlessly and work together so that if we have an event onsite that also includes the option to camp onsite, they can purchase their event tickets, ancillary items, and reserve their camping spots at the same time. Ideally, we would like to block off stand-alone camping reservations during events and just have the event side of things allow campsite reservations at those times. If anyone has ideas on how well WooCommerce can handle this, some of the event management software companies I talked to said their systems don’t handle both at the same time well so I am trying to find the best options to make these work together. Suggestions are appreciated or if you have experience with these and have had issues or successes that is great info as well.
]]>We use Events Manager (EM), together with the plugin Ultimate Member (UM) , for an annual arts festival. Each year there are approx 150 artists and a similar number of events. Artists register and create profiles with UM and then we schedule events with EM. However, we want to dynamically link artist meta data (e.g. profile image) with the custom event posts (i.e. for events featuring that artist) in EM’s single event template. For EM we can create custom placeholders and use the Attributes function to do this.
We want to make UM profile fields / user meta (e.g. for the field “profile image” or others we define in the UM profile form) available for this task in EM? That would mean, for example, that when an artist changes their image, it automatically appears in the corresponding event post(s).
(Have also posted a complementary support request on the UM forum. Note that we are also pursuing an alternative approach, not reliant on UM, but for now, it would be useful to have any tips on a fallback option).
Thanks.
]]>It seems that BuddyPress supports emojis, but Events Manager (free) doesn’t?? Is this true? If a user adds an event and type something in the event description with an emoji, it gets rejected by the system. It shows up on the home page, but not on the Events or My Events page.
]]>I’m experimenting with Event Manager and like what I see so far bu I’m wondering how the create an event with a price of “100% free“. So far I’ve had no luck as events can only be saved/published with a numeric value in the price field. Any help would be appreciated.
]]>I’m using Events Manager 6.6.3 with WordPress 6.7.
Today I got a White Screen on WordPress and the help FAQ suggests to deactivate all plugins in the wp_options table – what I did. Next step: re-activate the plugins in the WP dashboard.
This worked for all other plugins, activating Events Manager resulted in a “fatal error”.
How to solve: trying to uninstall and install again – then all the event items in the database may be gone. Maybe best to replace all files of the plugin.
I downloaded the plugin files, renamed the events-manager folder among the plugins and unzipped the downloaded files to a new events-manager folder.
Activating Events Manager in the Plugins panel of the dashboard worked well and all features of the Events Manager work – but the dashboard shows another plugin entry for Events Manager.
The active_plugins column of the wp_options table shows only a single instance of the Events Manager.
Why are multiple instances shown in the dashboard and how to get rid of the “old” ones?
]]>Is there a way to display events for a specific date like above?
e.g. the 18th of june 2025 or 18 to 23 of june 2025
]]>My Events Search page is corrupted. Please take a look and see the mess for yourself.
I’m running the latest WordPress with Astra theme. What corrections can I make to get the page looking the way it should?
I’ve been testing plugins including this one and I fail to figure out a cleanest way to completely remove this plugin and all its traces from my WP instance. I tried to manually cleanup the database (and tables within – for ex. everything that has em_ string or events string et al) but I cannot use any other events plugin after I uninstall this plugin.)
What’s the manual procedure to COMPLETELY remove this plugin? Ideally plugins such as this is definitely expected to have a built-in feature to “remove plugin data when uninstalled”.
]]>Hi There
Been using the plugin for some time and happy with it but have just encountered a strange problem. Creating events for January and February 2025 – they don’t appear in the calendar view but the events for March onwards do appear.
Your urgent assistance would be greatly appreciated. I have tried copying an event from March and changing the date but it doesn’t work. I have tried creating it from scratch but it doesn’t work.
]]>When a person is logged in, but not a paid user, I want it so that he shouldn’t be able to Add an Event. Is there a way to hide the “Add an Event” button? I’m using BuddyPress and Paid Membership Pro together on the site, but I thought that this issue may just be an Events Manager problem.
]]>Hey Event Managers Team,
I’m building my website and use your plugin to show the upcoming events. This looks good on the desktop and tablet view, however, when changing to mobile view for mobile devices, the events are only shown 1 at a time and take up a lot of the screen.
I use Brizy wordpress plugin as my wordpress editor and this plugin uses shortcodes to integrate other plugins inside their editor. Is there a way to ensure that the event grid displays 2 columns of events when in mobile view?
]]>In version 6.4.9, a change was made to escape the JSON data in templates/templates/map-global.php
.
This was not the correct fix. The JSON data should not be (directly) in a div
element. Instead it should be in a script
element with type=application/json
. If it is in the correct element type, it does not need escaping (and should not be).
The existence of the data in a display element (regadless of the inline style hack with display: none; visibility: hidden
) causes SEO issues. Search engines regard it as content for the page (they often ignore CSS and style
properties), include it in indexing, and may even include it in a snippet in search results.
This is a bug report. (I don’t know where else to report bugs.)
]]>Using the events_calender shortcode with advanced search enabled, any advanced search or filters applied are not carried over when switching the month.
Can this be fixed please?
]]>See screenshot above. I have “German” (“Deutsch”) as wordpress language, yet for the advanced search it shows “X selected” and “Clear selection” as labels. When I check the translation files with loco translate, they are properly mapped to German strings, yet it seems they are not used properly.
]]>I have the following shortcode which does not show the search: [events_list full="1" has_search="1" sorting="0" show_advanced="0" search_geo="0" show_search="1" long_events="1"]
However right above I have this shortcode which works fine and shows the search:
[events_calendar full="1" has_search="1" sorting="0" show_advanced="1" search_geo="0" show_search="1" long_events="1"]
Is this a bug? According to the documentation, the [events_list] should also support all search parameters ??
]]>I can’t figure this out. I want people to be able to submit events on the front end, but I also want them to be able to edit them. The submissions page is here https://myrunclub.co.uk/events/event-submission/, but unless I set it to anonymous submissions, no one can actually see the page.
]]>Hi
This error message is being logged repeatedly (multiple times a minute):
PHP Warning: Undefined array key “calendar_size” in …/plugins/events-manager/classes/em-calendar.php on line 218
The calendar is set to ‘responsive’ at the moment
Can you help please? Thank you
]]>Dear events-manager team,
I like your plugin a lot and use it for our non-profit private choir.
While rearranging an events page, I came across the situation that both conditional placeholders, {all_day} and {not_all_day} showed the same behavior.
Checking your code, I think that I found the following error in events-manager/classes/em-event.php starting from line 2206:
elseif ($condition == 'all_day'){
//is it an all day event
$show_condition = !empty($this->event_all_day);
}elseif ($condition == 'not_all_day'){
//is not an all day event
$show_condition = !empty($this->event_all_day);
}
It would be great to correct this code in order to have the related conditional placeholder work as expected.
I tried the following solution, which seemed to work for me but of course, I cannot be sure whether this would work under all circumstances:
elseif ($condition == 'all_day'){
//is it an all day event
$show_condition = !empty($this->event_all_day);
}elseif ($condition == 'not_all_day'){
//is not an all day event
$show_condition = empty($this->event_all_day);
}
Thanks and kindest regards
Michael
]]>I am using Event Manager and for some reason I cannot get the Front end form to work for vistors to the site. It keeps saying “Unauthorised Access, You do not have the rights to manage this Event.” I have tried to change the User Role settings but I am apparently not doing it right as its not working still.
I am sure it is a simple thing in WordPress I am missing but any help would be great.
]]>I am using Event Manager and for soem reason I cannto get teh Front end form to work for people. It keeps saying “Unauthorised Access, You do not have the rights to manage this Event.” I have tried to change the User Role settings but I am apparently not doing it right as its nto working still.
]]>Hi,
when creating a virtuel event (event-type = URL), the plugin automatically creates an empty physical venue. That not only leads to a messed up list of venues, it also crashes frontend as conditional placeholders not work anymore.
Could you check please?
]]>I have been tasked by the site owner to breakup the current calendar into three separate calendars. I plan to do that based on category for each calendar.
Can I have more than one calendar on a page? Is there shortcode for that?
I tried adding the short code twice, but only one calendar showed.
Thank you
I’m running a WordPress 6.6.2 multisite with Events Manager 6.6.3 (latest version as of today) and when I attempt to delete a site within the multisite it is failing due to a Fatal Error thrown by Events Manager.
Fatal error: Uncaught TypeError: get_class(): Argument #1 ($object) must be of type object, int given in /var/www/wp-content/plugins/events-manager/classes/em-events.php:257
This is in the delete method that is expected to receive an array of event_ids or EM_Events objects, however when the line 257 conditional check receives an array of ids and calls get_class (which expects its only parameter to be an object) it causes a fatal error.
I changed this line from:
if( !empty($array) && @get_class(current($array)) != 'EM_Event' ){
to:
if( !empty($array) && is_numeric(current($array))){
This fixes the problem, however I’m hoping this or another solution can be integrated into future updates so that this can be fixed permanently.
]]>Hi,
how can I take an attendee list from an event? We have bookings with multiple attendees and when we export the bookings list, we get in the attendee fields not the names but “multipe attendees”.
Thanks,
Manja
Hi, I have an installation of Events Manager and Events Manager Pro. One of my users asked if he could search for past events. I fiddled with the settings under Pages and set the default event scope under “default event list options” to “all events”. Sure enough all events appear in the event list. However that’s not a solution that would work for the majority of users who only want to see future events. I tried unsetting the Events page so that event archives would be activated, but that didn’t work. Viewing the default event list url as described in the settings just gave a blank page, so I couldn’t see future OR past events.
Is there a simple way to split event display into two different pages, one for future, one for all events?
Thanks
Nick
]]>I installed the plugin on a fresh WP. When i add new event, i see these warnings, please let me know how can it is solved:
[09-Nov-2024 17:28:47 UTC]?PHP Deprecated: key(): Calling key() on an object is deprecated in /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event-post-admin.php on line 124
[09-Nov-2024 17:28:47 UTC]?PHP Deprecated: reset(): Calling reset() on an object is deprecated in /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event-post-admin.php on line 129
[09-Nov-2024 17:28:47 UTC]?PHP Deprecated: key(): Calling key() on an object is deprecated in /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event-post-admin.php on line 131
[09-Nov-2024 17:28:47 UTC]?PHP Warning?Cannot modify header information – headers already sent by (output started at /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event-post-admin.php:124) in /home/visaone/domains/visaone.ir/public_html/wp-admin/post.php on line 231
[09-Nov-2024 17:28:47 UTC]?PHP Warning?Cannot modify header information – headers already sent by (output started at /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event-post-admin.php:124) in /home/visaone/domains/visaone.ir/public_html/wp-includes/pluggable.php on line 1435
[09-Nov-2024 17:28:47 UTC]?PHP Warning?Cannot modify header information – headers already sent by (output started at /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event-post-admin.php:124) in /home/visaone/domains/visaone.ir/public_html/wp-includes/pluggable.php on line 1438
when i add recurring event
Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event.php on line 3717 Warning: Undefined array key “” in /home/visaone/domains/visaone.ir/public_html/wp-content/plugins/events-manager/classes/em-event.php on line 3720 Current Recurrence Pattern: From 2024-11-09 to 2024-11-13, every week
Modifications to event dates will cause all recurrences of this event to be deleted and recreated, previous bookings will be deleted.
]]>Hi,
I’m using the “Astra” theme with the “Love Nature” template. I’m unable to modify the events-page from the plugin to look like the pages from the template. So I thought I would use an existing page to have the events displayed, but I seem unable to do so. Is it possible at all ?
Thanks.
]]>Hi,
when exporting booking data we get some fields, f.e. the city field, with css styles included:
<span style="color:red;">Düsseldorf </span>
How can we fix this issue?
Thanks,
Manja
Estoy utilizando Events Manager para la venta de tickets a través de woocomerce. La pasarela de pago que utilizo es la de woocomerce. Desde que he actualizado los plugins, al intentar pagar un evento salta un error: “Se produjo un error al procesar tu pedido. Comprueba si hay cargos en tu método de pago y revisa tu?historial de pedidos?antes de volver a realizar el pedido.”
Si lo que hay en el carrito de la compra es un producto de la tienda de woocommerce no me sale ningún error y me envía directamente a la pasarela de pago seleccionada, el pedido llega correctamente y el pago también.
Debe haber algún error de sincronización entre woocomerce y events manager.
Plugins instalados:
Events manager: Versión 6.6.3
Events manager for woocommerce: Versión 0.13
Events manager pro: Versión 3.4.1?
Woocommerce Legacy REST API: Versión 1.0.4
Woocommerce Stripe Getaway: Versión 8.8.2
Woocommerce: Versión 9.3.3
Pasarela unificada de Redsys para Woocommerce: Versión 1.5.4
WordPress versión 6.6.2
PHP actualizado a la última versión por mi servicio técnico.
Informe del estado del sistema:
]]>WordPress Environment<br><br>WordPress address (URL): https://alamarsailing.com<br>Site address (URL): https://alamarsailing.com<br>WC Version: 9.3.3<br>Legacy REST API Package Version: ? 1.0.4<br>Action Scheduler Version: ? 3.8.2<br>Log Directory Writable: ?<br>WP Version: 6.6.2<br>WP Multisite: –<br>WP Memory Limit: 1 GB<br>WP Debug Mode: –<br>WP Cron: ?<br>Language: es_ES<br>External object cache: – Server Environment<br><br>Server Info: LiteSpeed<br>PHP Version: 8.1.30<br>PHP Post Max Size: 1 GB<br>PHP Time Limit: 30<br>PHP Max Input Vars: 1000<br>cURL Version: 8.9.1<br>OpenSSL/1.1.1w<br><br>SUHOSIN Installed: –<br>MySQL Version: 8.0.37<br>Max Upload Size: 1 GB<br>Default Timezone is UTC: ?<br>fsockopen/cURL: ?<br>SoapClient: ?<br>DOMDocument: ?<br>GZip: ?<br>Multibyte String: ?<br>Remote Post: ?<br>Remote Get: ? Database<br><br>WC Database Version: 9.3.3<br>WC Database Prefix: wp_<br>Tama?o total de la base de datos: 4682.31MB<br>Tama?o de los datos de la base de datos: 4573.04MB<br>Tama?o del índice de la base de datos: 109.27MB<br>wp_woocommerce_sessions: Datos: 2.02MB + índice: 0.02MB + Motor InnoDB<br>wp_woocommerce_api_keys: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_woocommerce_attribute_taxonomies: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_woocommerce_downloadable_product_permissions: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB<br>wp_woocommerce_order_items: Datos: 0.50MB + índice: 0.19MB + Motor InnoDB<br>wp_woocommerce_order_itemmeta: Datos: 4.52MB + índice: 6.03MB + Motor InnoDB<br>wp_woocommerce_tax_rates: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB<br>wp_woocommerce_tax_rate_locations: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_woocommerce_shipping_zones: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_woocommerce_shipping_zone_locations: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_woocommerce_shipping_zone_methods: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_woocommerce_payment_tokens: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_woocommerce_payment_tokenmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_woocommerce_log: Datos: 4216.00MB + índice: 48.59MB + Motor InnoDB<br>wp_actionscheduler_actions: Datos: 1.52MB + índice: 1.23MB + Motor InnoDB<br>wp_actionscheduler_claims: Datos: 0.08MB + índice: 0.06MB + Motor InnoDB<br>wp_actionscheduler_groups: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_actionscheduler_logs: Datos: 1.52MB + índice: 0.55MB + Motor InnoDB<br>wp_aioseo_cache: Datos: 0.14MB + índice: 0.03MB + Motor InnoDB<br>wp_aioseo_crawl_cleanup_blocked_args: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_aioseo_crawl_cleanup_logs: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_aioseo_notifications: Datos: 0.23MB + índice: 0.06MB + Motor InnoDB<br>wp_aioseo_posts: Datos: 2.52MB + índice: 0.09MB + Motor InnoDB<br>wp_aioseo_writing_assistant_keywords: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_aioseo_writing_assistant_posts: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_booking: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_bookingdates: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_commentmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_comments: Datos: 3.52MB + índice: 2.17MB + Motor InnoDB<br>wp_e_events: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_e_notes: Datos: 0.02MB + índice: 0.17MB + Motor InnoDB<br>wp_e_notes_users_relations: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_e_submissions: Datos: 0.13MB + índice: 0.27MB + Motor InnoDB<br>wp_e_submissions_actions_log: Datos: 0.05MB + índice: 0.11MB + Motor InnoDB<br>wp_e_submissions_values: Datos: 0.05MB + índice: 0.03MB + Motor InnoDB<br>wp_easywpsmtp_debug_events: Datos: 0.09MB + índice: 0.00MB + Motor InnoDB<br>wp_easywpsmtp_tasks_meta: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_ee_ai_reportdata: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_ee_pmax_campaign: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_ee_product_feed: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_ee_product_sync_call: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_ee_product_sync_data: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_ee_products_sync_list: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_ee_tiktok_catalog: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_em_automation: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_em_bookings: Datos: 1.52MB + índice: 0.34MB + Motor InnoDB<br>wp_em_bookings_meta: Datos: 2.52MB + índice: 2.91MB + Motor InnoDB<br>wp_em_bookings_relationships: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_em_coupons: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_em_email_queue: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_em_events: Datos: 1.52MB + índice: 0.34MB + Motor InnoDB<br>wp_em_io: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB<br>wp_em_io_log: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_em_io_sync: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_em_locations: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB<br>wp_em_meta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_em_tickets: Datos: 0.09MB + índice: 0.05MB + Motor InnoDB<br>wp_em_tickets_bookings: Datos: 0.27MB + índice: 0.38MB + Motor InnoDB<br>wp_em_tickets_bookings_checkins: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_em_tickets_bookings_meta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_em_transactions: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_evf_entries: Datos: 1.52MB + índice: 0.02MB + Motor InnoDB<br>wp_evf_entrymeta: Datos: 0.31MB + índice: 0.17MB + Motor InnoDB<br>wp_evf_sessions: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_gla_budget_recommendations: Datos: 0.22MB + índice: 0.14MB + Motor InnoDB<br>wp_gla_merchant_issues: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_gla_shipping_rates: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_gla_shipping_times: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_jetpack_sync_queue: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB<br>wp_links: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_litespeed_avatar: Datos: 0.09MB + índice: 0.06MB + Motor InnoDB<br>wp_litespeed_img_optm: Datos: 0.25MB + índice: 0.16MB + Motor InnoDB<br>wp_litespeed_img_optming: Datos: 0.16MB + índice: 0.30MB + Motor InnoDB<br>wp_litespeed_url: Datos: 0.30MB + índice: 0.39MB + Motor InnoDB<br>wp_litespeed_url_file: Datos: 1.52MB + índice: 5.58MB + Motor InnoDB<br>wp_mailpoet_automation_run_logs: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_mailpoet_automation_run_subjects: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_mailpoet_automation_runs: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB<br>wp_mailpoet_automation_triggers: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_mailpoet_automation_versions: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_automations: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_mailpoet_custom_fields: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_dynamic_segment_filters: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_feature_flags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_forms: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_mailpoet_log: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_mailpoet_mapping_to_external_entities: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_migrations: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_newsletter_links: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_mailpoet_newsletter_option: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_newsletter_option_fields: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_newsletter_posts: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_newsletter_segment: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_newsletter_templates: Datos: 2.52MB + índice: 0.00MB + Motor InnoDB<br>wp_mailpoet_newsletters: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_mailpoet_scheduled_task_subscribers: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_scheduled_tasks: Datos: 0.22MB + índice: 0.19MB + Motor InnoDB<br>wp_mailpoet_segments: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_mailpoet_sending_queues: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_mailpoet_settings: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_statistics_bounces: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_mailpoet_statistics_clicks: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_mailpoet_statistics_forms: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_statistics_newsletters: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_mailpoet_statistics_opens: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB<br>wp_mailpoet_statistics_unsubscribes: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_mailpoet_statistics_woocommerce_purchases: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB<br>wp_mailpoet_stats_notifications: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_mailpoet_subscriber_custom_field: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_subscriber_ips: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_subscriber_segment: Datos: 0.09MB + índice: 0.06MB + Motor InnoDB<br>wp_mailpoet_subscriber_tag: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_mailpoet_subscribers: Datos: 0.16MB + índice: 0.33MB + Motor InnoDB<br>wp_mailpoet_tags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_user_agents: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_mailpoet_user_flags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_options: Datos: 11.20MB + índice: 1.53MB + Motor InnoDB<br>wp_postmeta: Datos: 143.56MB + índice: 23.06MB + Motor InnoDB<br>wp_posts: Datos: 52.52MB + índice: 3.58MB + Motor InnoDB<br>wp_redsys_order: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_seopress_significant_keywords: Datos: 0.48MB + índice: 0.61MB + Motor InnoDB<br>wp_term_relationships: Datos: 0.28MB + índice: 0.20MB + Motor InnoDB<br>wp_term_taxonomy: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_termmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_terms: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_tutor_earnings: Datos: 0.09MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_gradebooks: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_gradebooks_results: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_notifications: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_quiz_attempt_answers: Datos: 3.52MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_quiz_attempts: Datos: 1.52MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_quiz_question_answers: Datos: 1.52MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_quiz_questions: Datos: 1.52MB + índice: 0.00MB + Motor InnoDB<br>wp_tutor_withdraws: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_userfeedback_survey_responses: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_userfeedback_surveys: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_usermeta: Datos: 3.52MB + índice: 4.03MB + Motor InnoDB<br>wp_users: Datos: 0.19MB + índice: 0.16MB + Motor InnoDB<br>wp_wc_activecampaign: Datos: 0.22MB + índice: 0.14MB + Motor InnoDB<br>wp_wc_admin_note_actions: Datos: 0.08MB + índice: 0.02MB + Motor InnoDB<br>wp_wc_admin_notes: Datos: 0.13MB + índice: 0.00MB + Motor InnoDB<br>wp_wc_category_lookup: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_wc_customer_lookup: Datos: 0.16MB + índice: 0.13MB + Motor InnoDB<br>wp_wc_download_log: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_wc_order_addresses: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB<br>wp_wc_order_coupon_lookup: Datos: 0.08MB + índice: 0.09MB + Motor InnoDB<br>wp_wc_order_operational_data: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_wc_order_product_lookup: Datos: 0.42MB + índice: 0.47MB + Motor InnoDB<br>wp_wc_order_stats: Datos: 0.39MB + índice: 0.38MB + Motor InnoDB<br>wp_wc_order_tax_lookup: Datos: 0.22MB + índice: 0.22MB + Motor InnoDB<br>wp_wc_orders: Datos: 0.02MB + índice: 0.11MB + Motor InnoDB<br>wp_wc_orders_meta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB<br>wp_wc_product_attributes_lookup: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_wc_product_download_directories: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_wc_product_meta_lookup: Datos: 0.23MB + índice: 0.55MB + Motor InnoDB<br>wp_wc_rate_limits: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_wc_reserved_stock: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_wc_tax_rate_classes: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_wc_webhooks: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB<br>wp_wcpdf_invoice_number: Datos: 0.05MB + índice: 0.00MB + Motor InnoDB<br>wp_wcpdf_invoice_number_2021: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_wcpdf_invoice_number_2022: Datos: 0.05MB + índice: 0.00MB + Motor InnoDB<br>wp_wcpdf_invoice_number_2023: Datos: 0.06MB + índice: 0.00MB + Motor InnoDB<br>wp_wcpdf_packing_slip_number: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_wpforms_logs: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_wpforms_payment_meta: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB<br>wp_wpforms_payments: Datos: 0.02MB + índice: 0.14MB + Motor InnoDB<br>wp_wpforms_tasks_meta: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_wpmailsmtp_debug_events: Datos: 0.08MB + índice: 0.00MB + Motor InnoDB<br>wp_wpmailsmtp_tasks_meta: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB<br>wp_wpml_mails: Datos: 102.52MB + índice: 0.16MB + Motor InnoDB Post Type Counts<br><br>attachment: 839<br>courses: 8<br>custom_css: 1<br>elementor_library: 8<br>event: 759<br>event-recurring: 22<br>everest_form: 3<br>lesson: 482<br>location: 8<br>mailpoet_page: 1<br>nav_menu_item: 16<br>oembed_cache: 42<br>page: 56<br>post: 8<br>product: 730<br>product_variation: 706<br>revision: 2440<br>shop_coupon: 297<br>shop_order: 3538<br>shop_order_refund: 25<br>topics: 72<br>tribe_events: 12<br>tribe_organizer: 4<br>tribe_rsvp_attendees: 1<br>tribe_rsvp_tickets: 1<br>tribe_venue: 2<br>tutor_enrolled: 566<br>tutor_quiz: 58<br>wp_global_styles: 1 Security<br><br>Secure connection (HTTPS): ?<br>Hide errors from visitors: ? Active Plugins (35)<br><br>ActiveCampaign for WooCommerce: por ActiveCampaign – 2.7.10<br>ActiveCampaign: por ActiveCampaign – 8.1.16<br>Akismet Anti-spam: Spam Protection: por Automattic - Equipo Anti-spam – 5.3.3<br>All in One SEO: por All in One SEO Team – 4.7.4.2<br>GTM4WP - A Google Tag Manager (GTM) plugin for WordPress: por Thomas Geiger – 1.20.2<br>Elementor Pro: por Elementor.com – 3.25.2<br>Elementor: por Elementor.com – 3.25.4<br>Essential Addons for Elementor: por WPDeveloper – 6.0.9<br>Events Manager Pro: por Pixelite – 3.4.1<br>Events Manager for WooCommerce: por Pixelite SL – 0.13<br>Events Manager: por Pixelite – 6.6.3<br>Everest Forms: por WPEverest – 3.0.4.2<br>Facebook for WooCommerce: por Facebook – 3.3.0<br>Google Analytics para WordPress por MonsterInsights: por MonsterInsights – 9.2.1<br>Lawwwing: por ibamu – 1.2.4<br>Jetpack: por Automattic – 13.9.1<br>LeadConnector: por LeadConnector – 1.9<br>LiteSpeed Cache: por LiteSpeed Technologies – 6.5.2<br>PHP Compatibility Checker: por WP Engine – 1.6.3<br>PixelYourSite: por PixelYourSite – 10.0.0<br>Really Simple Security: por Really Simple Security – 9.1.1.1<br>Pasarela Unificada de Redsys para WooCommerce: por Redsys Servicios de Procesamiento S.L. – 1.5.4<br>Page Builder by SiteOrigin: por SiteOrigin – 2.30.0<br>Tutor LMS Certificate Builder: por Themeum – 1.0.4<br>Tutor LMS Pro: por Themeum – 2.7.0<br>Tutor LMS: por Themeum – 2.7.6<br>WooCommerce.com Update Manager: por Automattic – 1.0.3<br>WooCommerce Stripe Gateway: por Stripe – 8.8.2<br>WooCommerce Legacy REST API: por WooCommerce – 1.0.4<br>PDF Invoices & Packing Slips for WooCommerce: por WP Overnight – 3.9.0<br>WooCommerce: por Automattic – 9.3.3<br>WP FullCalendar: por Pixelite – 1.5<br>WP Mail Logging: por El equipo de WP Mail Logging – 1.13.1<br>WP Mail SMTP: por WP Mail SMTP – 4.2.0<br>WPForms Lite: por WPForms – 1.9.2.1 Inactive Plugins (4)<br><br>Events Manager - Zoom Integration: por Pixelite – 1.6<br>Events Manager Pro - Stripe: por Pixelite – 2.5<br>SEOPress: por The SEO Guys at SEOPress – 8.3.1<br>SEOPress PRO: por The SEO Guys at SEOPress – 7.3.1 Dropin Plugins ()<br><br>advanced-cache.php: advanced-cache.php Must Use Plugins (1)<br><br>WordPress automation by Installatron: por – Settings<br><br>Legacy API Enabled: ?<br>Force SSL: –<br>Currency: EUR (€)<br>Currency Position: right_space<br>Thousand Separator: .<br>Decimal Separator: ,<br>Number of Decimals: 2<br>Taxonomies: Product Types: external (external)<br>grouped (grouped)<br>simple (simple)<br>variable (variable)<br><br>Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)<br>exclude-from-search (exclude-from-search)<br>featured (featured)<br>outofstock (outofstock)<br>rated-1 (rated-1)<br>rated-2 (rated-2)<br>rated-3 (rated-3)<br>rated-4 (rated-4)<br>rated-5 (rated-5)<br><br>Connected to WooCommerce.com: ?<br>Enforce Approved Product Download Directories: –<br>HPOS feature enabled: –<br>Order datastore: WC_Order_Data_Store_CPT<br>HPOS data sync enabled: – Logging<br><br>Enabled: ?<br>Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2<br>Retention period: 30 días<br>Level threshold: –<br>Log directory size: 111 MB WC Pages<br><br>Base de la tienda: #209 - /tienda/<br>Carrito: #2181 - /carrito-de-la-compra/ - Contiene el shortcode [woocommerce_cart]<br>Finalizar compra: #2183 - /pasarela-de-pago/ - Contiene el shortcode [woocommerce_checkout]<br>Mi cuenta: #2185 - /mi-cuenta/<br>Términos y condiciones: #2187 - /terminos-y-condiciones/ Theme<br><br>Name: Hello Elementor<br>Version: 3.1.1<br>Author URL: https://elementor.com/?utm_source=wp-themes&utm_campaign=author-uri&utm_medium=wp-dash<br>Child Theme: ? – Si estás modificando WooCommerce en un tema padre que no has creado personalmente<br>te recomendamos utilizar un tema hijo. Ver: Cómo crear un tema hijo<br><br>WooCommerce Support: ? Templates<br><br>Overrides: – Admin<br><br>Enabled Features: activity-panels<br>analytics<br>product-block-editor<br>coupons<br>core-profiler<br>customize-store<br>customer-effort-score-tracks<br>import-products-task<br>experimental-fashion-sample-products<br>shipping-smart-defaults<br>shipping-setting-tour<br>homescreen<br>marketing<br>mobile-app-banner<br>navigation<br>onboarding<br>onboarding-tasks<br>pattern-toolkit-full-composability<br>product-custom-fields<br>remote-inbox-notifications<br>remote-free-extensions<br>payment-gateway-suggestions<br>printful<br>shipping-label-banner<br>subscriptions<br>store-alerts<br>transient-notices<br>woo-mobile-welcome<br>wc-pay-promotion<br>wc-pay-welcome-page<br>launch-your-store<br><br>Disabled Features: experimental-blocks<br>minified-js<br>product-pre-publish-modal<br>settings<br>async-product-editor-category-field<br>product-editor-template-system<br>blueprint<br>reactify-classic-payments-settings<br><br>Daily Cron: ? Next scheduled: 2024-11-08 11:50:12 +01:00<br>Options: ?<br>Notes: 215<br>Onboarding: completed Action Scheduler<br><br>Complete: 1.392<br>Oldest: 2024-10-08 01:33:16 +0200<br>Newest: 2024-11-07 23:59:54 +0100<br><br>Failed: 2.032<br>Oldest: 2022-05-25 10:44:50 +0200<br>Newest: 2024-11-07 19:51:57 +0100<br><br>Pending: 14<br>Oldest: 2024-11-08 00:14:54 +0100<br>Newest: 2025-01-01 00:00:01 +0100 Status report information<br><br>Generated at: 2024-11-08 00:03:30 +01:00<br>
When trying to email attendees it says, ‘Successfully queued 1 email(s) for sending. These will be sent within a few minutes.’ But they never get sent, and when I click the option to ‘Send messages immediately and skip queueing, not advised for large list of emails as this could fail during the process but after having sent some emails already.’ it brings up this error:
Email sending failed. Please see error messages below:
Even though I tried various formats to send the email.
How can I make it work?? The page is when you click an event booking and then click send email
]]>