CodeCanyon EventOn - WordPress Plugin

Guide to Setting Up and Using CodeCanyon EventOn

CodeCanyon EventOn is best treated not as a decorative calendar, but as an event publishing system inside WordPress: you create events in the admin panel, define the date, venue, organizer, recurrence, status, card layout, and display rules, then place the calendar on the right page with a block, shortcode, or template. This guide walks through the practical path from your first site check to a fully usable events page where visitors can see current events, filter them, open the details, and understand what happens next.

This is not a generic product overview. The practical questions matter more here: which settings to enable right away, which ones to leave for later, how to avoid losing events because of filters, why EventCard may not show every field, when you need the Google Maps API, how to choose the right event opening mode, and how to troubleshoot JavaScript, cache, maps, and performance issues.

In the examples below, I am assuming a typical site for an organization, training center, club, conference, or local project that needs a calendar for meetups, classes, webinars, and special events. If you use EventON extensions for tickets, RSVP, venues, bookings, or user-submitted events, the setup logic is similar, but before enabling commercial workflows, you should separately verify your server requirements, WooCommerce setup, email delivery, and expected load.

When the EventON Calendar Is the Right Choice

EventON works well when events are a standalone content type rather than just lines in a schedule. An event has a title, description, date, time, status, venue, organizer, image, color, category, extra fields, and a specific way visitors can interact with it. That makes it a strong fit for event listings, schools, fitness clubs, online seminars, church communities, conferences, museums, tourism projects, nonprofits, or internal portals with recurring meetings.

The plugin's main strength is the chain of "event -> card -> calendar -> filter." You are not placing each event manually into a page. Instead, you create events as entries, and on the calendar page you control which ones appear: all upcoming events, only a selected category, an image-based tile layout, a list of upcoming sessions, a calendar with expandable cards, or a version that opens in a lightbox or links to a dedicated event page.

EventON becomes especially useful when your events share a lot of recurring details. For example, a training center may have fixed subject areas, classrooms, and instructors; a club may run recurring sessions in different locations; a conference may offer multiple participation formats and different organizers. In those cases, reusable locations, organizers, event types, custom meta data, and EventCard Designer save time and reduce content chaos.

There are also cases where the plugin may be more than you need. If your site only has two dates per year, a regular text block may be easier. If you need a full ticketing platform with seating, complex refunds, accounting integrations, and heavy traffic, the core plugin alone may not be enough: you may need separate EventON add-ons, a WooCommerce integration, or an alternative solution. And if your editors do not have time to keep dates, statuses, and images up to date, any calendar will quickly turn into outdated storefront content.

What the Basic Setup Solves

In a basic scenario, CodeCanyon EventOn helps solve four tasks. First, it lets you manage events inside the familiar WordPress admin panel. Second, it helps structure the event's top row and expandable card so visitors can quickly understand the date, location, and action. Third, it lets you place the calendar on a page with a shortcode or block. Fourth, it gives you control over event visibility through categories, dates, statuses, filters, opening mode, and sorting.

The key practical takeaway is this: before installation, do not just check the server - decide in advance which events you actually want to display. A calendar with five webinars can run on a simple shortcode. A full event catalog with multiple topics needs categories, a filter bar, and a clean EventTop layout. Larger schedules require more thought about performance, images, limiting the number of events per month, and whether details should open on a separate event page.

Who Should Start with a Test Page

If the calendar is going on your homepage or inside an important conversion path, do not replace the live version immediately. Create a draft page, add 2-3 test events, and check the tile layout, list layout, expandable card, and mobile view. This is a simple step, but it gets skipped often: many EventON issues show up not in the admin panel, but in the interaction between the theme, cache, JavaScript, images, and real content.

A good first test: one standard event, one all-day event, one recurring event, one location with a map, and one calendar with the past-event hiding option enabled. That mix quickly shows where the logic breaks.

What to Check Before Installing on WordPress

Before installing EventON, it is worth running through a short technical checklist. This is not just a formality: calendar plugins often deal with dates, recurrences, database queries, maps, images, JavaScript, and additional data tables. If the site is already running close to its limits, a calendar with a large number of events may expose problems that were not obvious before.

Server, Memory, and PHP Version

EventON's official system requirements distinguish between the core plugin, setups with add-ons, and ticketing or WooCommerce integrations. The logic is simple: the more events, images, recurrences, tickets, and user actions you have, the higher the requirements for memory, the database, and the WordPress task scheduler. For the main calendar, a stable modern WordPress host is usually enough, but for a broader add-on stack, it is better to check your memory limit, current PHP support, MySQL or MariaDB, HTTPS, permalinks, and WP-Cron before you begin.

Do not enable tickets, RSVP, bookings, or large-scale recurrence on weak shared hosting without testing first. Even if the page opens, the admin panel may become slow when editing large events, and visitors may experience sluggish card expansion. Calendar optimization does not start with CSS. It starts with clear limits on the data: how many events you show, which images you load, and which opening mode you use.

Theme, Cache, and JavaScript

EventON relies heavily on frontend scripts for expandable cards, lightboxes, filters, search, and month navigation. Before installation, it is worth checking that your theme correctly calls the standard WordPress footer and that optimization plugins are not breaking the script loading order. EventON's official troubleshooting also specifically mentions problems with outdated or replaced jQuery, JavaScript conflicts, and missing required files in the page source.

If your site uses aggressive minification, deferred script loading, JavaScript merging, or AJAX page transitions, test the calendar separately. Start by placing the plugin on a draft page without additional optimization. Then enable cache and optimization rules one by one. That will quickly show which mechanism is interfering with event expansion or navigation.

Content Planning Before the First Event

Do not start by adjusting colors. Define your content model first:

• Which event types you will use: classes, webinars, meetups, concerts, conferences, services, tours, internal sessions.
• Whether you need separate categories for filtering or just one general calendar.
• Whether you will use recurring events and whether each recurrence needs to be shown to visitors.
• Whether you need locations, organizers, images, extra fields, and links to related materials.
• Whether the visitor should simply read the information, open a lightbox, go to a dedicated page, or leave via an external link.

This preparation affects every decision that follows. For example, if you run many recurring classes, it is important to think through exceptions and recurrence display from the start. If events take place in different cities, locations and maps are worth setting up. If each webinar has a recording, a presentation, and an access link, custom meta fields and a clean EventCard layout will help.

Installation, Activation, and the First Check

Installing CodeCanyon EventOn is technically similar to installing other premium WordPress plugins: you upload the archive in the Plugins section, activate it, and get a separate EventON menu. This guide does not cover purchase, payment, or licensing. From a practical standpoint, something else matters more: after activation, do not try to build the perfect calendar right away. First, make sure the plugin appears in the admin panel, saves settings, creates events, and outputs a basic shortcode properly.

Minimum Post-Activation Path

1. Open the WordPress admin panel and confirm that EventON and Events appear in the left menu.
2. Go to EventON -> Settings and save the basic settings without making complex changes.
3. Create a test event through Events -> Add New.
4. Enter the title, description, start date, end date, and, if needed, an image, color, and simple location.
5. Create a draft page and insert the basic shortcode [add_eventon] with either the Shortcode block or the EventON generator.
6. Open the page in preview mode and check that the event appears, expands, and looks correct on mobile width.

If the calendar does not display even at this stage, do not move on to the card designer. First, check the event publication status, date, shortcode, and cache. If the calendar is visible but does not expand, the issue is probably not the content itself, but scripts, a theme conflict, or an optimization rule.

Which Settings to Touch First

EventON has many tabs, and it is tempting to configure every color, field, and workflow at once. On the first run, it is enough to review a few areas:

• Time Settings. Check the base timezone and past-event behavior. If the site serves one country or city, this is simpler. If your audience is international, you should separately test the visitor's local time behavior.
• Location or Google Maps API. If maps matter, add the API key, enable generating the map from the address, and verify the map inside the event card.
• EventTop. Decide which elements appear in the top event row: date, title, location, status, image, custom data.
• EventCard Design. Build the expandable card from the fields you actually need, not the entire available set.
• Sorting and Filtering. Enable only the filters that help the visitor, and do not show empty taxonomies.
• Styles. Add CSS last, once the structure already works.

After each change, click Save Changes, clear the site cache, and check the public page in a normal browser window. If you use a caching plugin, do not judge the result only in the admin preview: a logged-in user may see the page differently from a regular visitor.

How to Roll Back a Questionable Setting Safely

Any setting that changes calendar behavior should be tested on a separate page. For example, hiding past events may seem obvious, but it can easily create an "events disappeared" situation if the test event is already in the past or the timezone is set incorrectly. Lightbox mode looks convenient, but on some themes it can conflict with JavaScript optimization. The filter bar is useful for a large event catalog, but on a small calendar it may just create extra noise.

A rollback should be simple: restore the previous shortcode, disable the questionable option, save the settings, clear the cache, and check the page while logged out. If the problem disappears, record the reason in the project notes. That approach is faster than changing five parameters at once and then trying to figure out which one had the effect.

The Event as the Core Content Unit

In EventON, an event resembles a WordPress post, but with additional calendar logic. The editor content controls the description, while the event meta boxes control the date, time, recurrences, location, organizer, status, image, color, and additional fields. How well each event is filled out affects not only the appearance of one card, but also filters, sorting, search, structured data, and calendar exports.

Start Date and End Date

The most common mistake when creating a first event is not paying attention to the ending. The EventON documentation recommends setting an end date because for multi-day and more complex events, leaving it out can produce unexpected results. For a one-day meeting, that may seem minor, but the calendar still needs to understand how long the event exists, where it belongs in sorting, and how it should be displayed after it ends.

For an all-day event, use the appropriate time type rather than trying to imitate it manually. For an event that starts in the evening and ends after midnight, test the calendar display separately. For recurring meetings, first create one correct event, confirm that it displays properly, and only then enable recurrence.

Status and Attendance Mode

EventON supports event statuses, including scheduled, canceled, postponed, online, and other values. This is useful when the calendar is not just storing dates, but communicating the current state of the event to visitors. If an event is canceled, it is usually better not to remove it silently. A better workflow is to set a status, add a reason or explanation, and decide whether canceled events should be hidden in that specific calendar.

Attendance mode helps separate in-person, online, and hybrid events. That improves clarity for visitors and may also contribute to search-engine-facing event data. But this only works if your editors are actually going to maintain it consistently. If half of your webinars are not marked as online, the virtual-event filter becomes useless.

Locations and Organizers

Locations and organizers in EventON can be saved and reused. That is better than manually writing the address into the description every time. For an in-person event, a location can display a name, address, map, and image. For an online event, it is better to use separate virtual-location logic or an access link rather than filling in a random physical address.

If you use Google Maps, you need to do more than add the API key. You also need to make sure the map is enabled in the event settings and added in EventCard Designer. Otherwise the address may be filled in, but the map still will not appear in the expandable card. This is a typical EventON pattern: a field inside the event does not automatically guarantee public output.

Event Images

An image in EventON can improve the tile layout, the expandable card, and the single event page, but large images can also slow the calendar down quickly. The official size recommendation depends on the calendar width on your actual site: if the content area is roughly the same width as the calendar, there is no need to load images much wider than that. For a mobile audience, you can use more modest images as long as they stay clear.

The main rule: choose images based on their real display context. If the calendar shows tiles in three columns, huge photos add unnecessary load. If the event opens on a dedicated page and the image spans a wide area, a file that is too small will look poor. After setup, check the page with speed tools and see whether images have become the heaviest part of the calendar.

EventTop and EventCard: How to Build a Clear Event Card

The two key EventON concepts are EventTop and EventCard. EventTop is the top row or tile that the visitor sees in the calendar. EventCard is the expandable details block. If EventTop is overloaded, the calendar becomes hard to scan. If EventCard is missing key fields, the visitor clicks but does not get the answer: where the event takes place, who is organizing it, whether there is a link, what is happening with the map, or how to add the event to a calendar.

EventTop Designer

EventTop Designer lets you configure the top part of the event without manually editing code. The documentation describes the screen at EventON -> Settings -> EventTop -> EventTop Settings, where you can add and remove fields, control how date, location, custom data, edit button, progress bar, and current-event icon are displayed. This is not just visual styling: the fields you choose determine whether a visitor can make a decision without opening the card.

For most sites, EventTop should answer three questions: what this event is, when it happens, and why it matters to the visitor. Everything else is better left for EventCard. If you add too much data to the top row, the calendar becomes heavy, especially on phones. In tile mode, some fields may be unavailable or less visible, so after setup, make sure to compare the row layout and tile layout.

Basic EventTop Formula

For a simple calendar, start with the date, title, short subtitle, status or event type, and, if needed, the location. Enable the image in EventTop only if a visual event listing genuinely helps people choose. For a webinar catalog, you can add attendance mode or category. For a class schedule, time, topic, and place are often more important than a large image.

EventCard Designer

EventCard Designer is a visual builder for the expandable event card. It supports different row and column schemes: one column, two or three columns, and mixed layouts. Inside it, you can remove fields, hide them temporarily, change a field background, rearrange rows, and add unused elements. That is better than trying to edit the plugin template manually.

Build EventCard around the visitor's task. For an in-person event, you need the description, location, map, organizer, and directions button. For an online session, the important pieces are the time, access link or instructions, status, speaker, and extra materials. For a course or class series, recurrence, a list of dates, and a note about the format are helpful. If a field exists in the event but has not been added in EventCard Designer, it may not appear on the public page. So whenever you add a custom meta field, always go back to the card designer.

How Not to Overload the Card

Do not turn EventCard into a full duplicate of the event page. Visitors open the card inside the calendar to confirm details quickly. A long program, participation rules, and gallery content usually work better on a separate page or in the event description if the card opens as a lightbox or single event. Inside the card, keep concise blocks: address, map, organizer, format, action link, additional data, and a clear status.

Custom Meta Fields

EventON lets you create additional custom fields for events. The documentation describes the path through EventON -> Settings -> Custom Meta Data, where you can enable a field, set its name, choose the content type and icon, and then add the field to EventCard Designer. After that, the field appears in the event editor, and the editor can fill it in for a specific event.

Custom meta fields are best used for data that repeats across multiple events and should appear in one consistent place: skill level, class duration, links to materials, speaker name, access format, age group, event language. Do not use extra fields for long text that is easier to keep in the main description. And do not create fields "just in case": empty or forgotten fields make the editor more complicated and increase the chance that EventCard will look inconsistent.

Shortcodes, Blocks, and Calendar Display Modes

Calendar output in EventON revolves around shortcodes. The basic option, [add_eventon], displays the main calendar. The shortcode generator helps you choose the calendar type and parameters visually, and in the block editor you can use either the EventON block or a regular shortcode block. For more advanced integration, the documentation describes a PHP template tag, but for most sites it is safer to keep the calendar in the page content.

Basic Shortcode and the First Parameters

Start with the simplest version:

[add_eventon]

Once the calendar displays reliably, you can add parameters. For example:

[add_eventon event_type="23" hide_past="yes" event_count="5"]

This shortcode shows events from a selected category, hides past events, and limits the total number displayed. But each parameter can also become the reason events appear to be "missing." If the calendar is empty, temporarily go back to [add_eventon]. If the basic calendar works, the issue is not the plugin itself, but the filter, date, category, status, or count limit.

Multiple Calendars on One Page

If you place multiple calendars on one page, assign a unique cal_id. The documentation emphasizes that this identifier is needed to separate calendars. Otherwise, interactive elements may behave unpredictably, especially if the calendars use different parameters, filters, or opening modes.

[add_eventon cal_id="main_events" event_count="5"]
[add_eventon cal_id="workshops" event_type="23" hide_past="yes"]

From a practical standpoint, it is usually better not to place too many calendars on one page. If visitors need different directions or topics, one calendar with filtering is often easier. Multiple calendars make sense when they serve clearly different purposes: a main event listing, a separate webinar list, a block of upcoming sessions, or a fixed month view.

Tiles, Images, and Lightbox

For a more visual event listing, you can enable tile view and event images. For detailed viewing without sending the user to a separate page, you can use lightbox mode. For heavier events with long descriptions and many fields, it is often better to consider opening a dedicated event page instead. EventON's official speed guidance specifically notes that when the calendar loads all EventCard content up front, the page can become heavier. Opening a separate event page helps avoid loading all details in the first calendar view.

The right mode depends on visitor behavior:

• A list with expandable cards works well for a small calendar with limited detail.
• A tile layout with images fits an event listing where visual appeal helps visitors choose.
• A lightbox works well when the visitor should quickly view details and stay on the same page.
• A separate page is better for long descriptions, program details, SEO text, images, and a more complex registration flow.

Filters and Sorting

EventON supports global Sorting and Filtering settings and a filter bar on the calendar itself. Filters can include upcoming and past events, virtual events, statuses, event type categories, locations, organizers, tags, and speakers if those data points are filled in. One important nuance: a filter only makes sense when the underlying data is actually being maintained. Empty categories and random tags just get in the way.

For a site with several content tracks, filters can become the main navigation tool. For example, at a training center, the visitor may choose "online," "beginner," or "weekend." At a club, they may choose the activity, location, and coach. At a conference, they may choose the track, room, and status. But if you only have one kind of event, it is better to hide the filter bar or leave only search.

Recurrences, Locations, Statuses, and Extra Data

EventON's real flexibility shows up most clearly in advanced scenarios: recurring events, maps, custom meta fields, statuses, attendance mode, filtering, and different display options. These features should not be enabled immediately just to make the calendar feel "richer." They should be added when the content has a real reason to use them.

Recurring Events

Recurrence supports multiple patterns: hourly, daily, weekly, monthly, yearly, and custom dates. The documentation describes the path through event editing and enabling Repeating Event. For weekly repeats, you can choose a single day or multiple weekdays; for monthly repeats, the day of the month or the weekday within the month; for custom repeats, your own date set.

One practical tip: create the recurring event as a normal event first and confirm that it looks right, then enable recurrence. If you need to exclude specific dates, it is often convenient to move to custom repeats after the basic rule is working. That way, you are not building a complex schedule from scratch - you get a working starting point first and then refine it.

Recurrence matters most for classes, worship services, regular webinars, sports training, club meetings, and serialized event series. But it also creates a risk of flooding the calendar. If each recurrence is visible as a separate entry, visitors may end up seeing too many near-identical rows. Check the recurrence display options and the "show current instance" mode in the card if it fits your use case.

Maps and Addresses

For in-person events, a map is useful, but it comes with several dependencies. You need to add the Google Maps API key in EventON settings, enable map generation from the address in the event, make sure a Location is selected, and add Google Maps in EventCard Designer. If you miss one step, the visitor may not see the map even though the address is filled in.

If events always happen in one place, do not overload every card with a large map. Sometimes the address, directions button, and a separate venue page are enough. If events are frequent and spread across a city, the map in the card and location-based filtering become more valuable. For online events, the map is unnecessary; it is better to show the format, access link, or instructions if those should be visible to registered users.

Statuses and Hiding Canceled Events

EventON can work with event status and hide canceled events through calendar parameters. This is useful when the calendar needs to stay truthful. Deleting a canceled event may confuse visitors who already saw the original date. A "cancelled" status or similar value helps preserve the record and explain what changed.

But the status needs to be visible in EventTop or EventCard. If the status is filled in at the event level but not output in the design, it does not help the visitor. For important events, add a short explanation in the description or card, especially if the event moved online, changed its date, or requires a separate action.

Languages and Multilingual Setup

EventON has its own language settings and can connect languages with WPML through shortcode variables. For a simple Russian-language site, it is enough to translate the frontend strings in EventON -> Language. For a multilingual site, it is important not to mix interface string translation with the event content itself. If different languages point to different event sets, think through language corresponding events and separate output parameters.

Do not translate system strings directly inside your theme templates. Start with EventON language settings, then use WordPress translation tools or WPML. That way, plugin updates will not wipe out your edits, and editors can manage the text without code access.

Practical Example: An Events Page for a Training Center

Let us walk through a concrete scenario. You have a training center that runs in-person workshops, online webinars, and weekly classes. You need an "Events Calendar" page where visitors can see upcoming events, filter for online format, open a card, and view the location, format, and brief attendee requirements.

Goal

Create a page with upcoming events: either tiles or a compact list, images for key events, past dates hidden, filtering by format, and an expandable card with the description, location, organizer, and a custom field for "Skill Level."

Preparation

Before setup, create the structure:

• Event Type Category: "Webinars," "Workshops," "Recurring Classes."
• Locations: "Main Hall," "Online," "Partner Venue."
• Organizers: the training center administrator and instructors, if they should be displayed.
• Custom meta field: "Skill Level" with a short value such as "Beginner" or "Intermediate."
• Test images sized to match the actual calendar area on the site.

Setup Steps

1. Create three test events: one webinar, one in-person workshop, and one recurring class.
2. For each event, set the start and end date, format, category, image, and status.
3. For the in-person event, choose a location, enable the map if needed, and verify the API key.
4. Enable the custom meta field "Skill Level" and add it to EventCard Designer.
5. In EventTop Designer, keep the date, title, short subtitle, and either the format or category so the row is easy to scan.
6. On the draft page, insert a shortcode limited to upcoming events and the needed category if the calendar should not show everything.
7. Enable filters only after categories and formats are filled in for all test events.

Example of a starter shortcode for the test page:

[add_eventon cal_id="training_calendar" hide_past="yes" event_count="8" show_et_ft_img="yes"]

After validation, you can add category filtering or use the generator so you do not make mistakes in the parameters. Do not blindly copy a category ID from someone else's example: every site has its own term IDs.

Checking the Result

Open the page as a regular visitor and check five things:

• All upcoming test events are visible, and past ones are hidden only if that is the expected behavior.
• The format filter shows the correct events and does not leave the calendar empty because of category mismatches.
• EventTop remains readable on mobile: the date, title, and format do not break into awkward lines.
• EventCard shows the description, skill level, location, map, or online instructions.
• After clearing cache and refreshing the page, the calendar keeps its styles and interactivity.

A Nuance That Often Comes Up

If the "Skill Level" field is filled in on the event but does not appear on the site, the cause is usually not the event itself. Check whether the field was added in EventCard Designer. If the map does not appear, check not only the address, but also the API key, the map generation option, and whether the Google Maps field is present in the card. If a webinar disappears from the calendar, temporarily remove hide_past, the category filter, and the event_count limit.

Checking Results, Performance, and Safe Improvements

Once the calendar looks correct, you need to validate more than appearance alone. EventON affects the user flow, page speed, event SEO data, accessibility of interactive elements, and cache behavior. Good testing separates "it opened for me in the admin panel" from "the visitor actually sees an accurate event listing."

Public Check While Logged Out

Check the page in a normal browser window or a private window. A logged-in administrator often sees the page without cache and with the extra WordPress toolbar, so they do not always notice what a regular visitor sees. Open the calendar, switch the month, expand an event, use the filter, try search, check the lightbox, and navigate back.

If the calendar only breaks after cache is enabled, do not change the events. Look for a conflict in deferred JavaScript loading, merged files, cache exclusions, or script order. Disable one optimization mechanism first, test again, then re-enable it with exclusions.

Performance and Images

The main factors that affect the calendar are the number of events in the initial output, image size, and how details are opened. If you display many events with full cards, the page can become heavier. For dense schedules, try limiting the number of events per month, enabling additional event loading as needed, or choosing a separate-page opening mode for detailed content.

Choose images based on the real calendar width. If the calendar area is 700 pixels wide, there is no reason to load oversized poster files for every tile. For cards with multiple images, check the total page weight. Cache helps, but it will not fix media files that are simply too heavy.

SEO and Structured Data

EventON claims support for schema SEO content for calendar events. That does not mean rankings will increase automatically. The real value is that the event should have correct dates, format, venue or online mode, description, and status. If the data is filled in carelessly, structured markup will not save the page.

For SEO, what matters more is not just displaying the calendar, but creating a clear page: a short introduction, current events, filters, separate pages for important events, unique descriptions, solid images, and no outdated dates. If an event has its own landing page, use it for the full program, participation terms, and answers to common questions.

A Safe CSS Tweak for Appearance

EventON lets you add custom CSS through the style settings. Use that only for small visual adjustments once the structure already works. For example, you can improve the readability of the top event row without touching PHP templates:

.ajde_evcal_calendar .eventon_list_event .evcal_desc {
  line-height: 1.45;
}

.ajde_evcal_calendar .eventon_list_event .evcal_desc .evcal_event_title {
  font-weight: 700;
}

Before adding CSS, check the class in the browser inspector because the theme or design version may change the context. Add the tweak in EventON -> Settings -> Styles or in a safe theme location, and do not edit plugin files. To roll the change back, remove the snippet, save the settings, and clear the cache.

Video on EventCard Designer

For a more visual understanding of the card builder, the official EventCard Designer video is useful. It answers the practical intent of "how to set up EventCard in EventON": where the designer is located, what the layouts look like, and how to move and add fields. Watch it after you have created a test event, otherwise the interface will be harder to follow.

Common EventON Problems and How to Diagnose Them

EventON has several recurring problems that are almost never caused by a single button. They usually come from a chain of factors: event data, shortcode parameters, designer settings, cache, JavaScript, theme, maps, or server behavior. Troubleshoot from simple to complex. Start by restoring the basic shortcode and one test event. Then add filters, designers, maps, and optimization back one by one.

The calendar is empty or does not show all events

Symptom: the event exists in the admin panel, but it does not appear on the calendar page. Possible causes: the event is in the past, past-event hiding is enabled, the date or timezone is incorrect, the shortcode is filtering a different category, event_count is limiting the result, or the event has a status or type excluded by the settings.

What to check: temporarily replace the shortcode with [add_eventon], confirm that the event is published, verify the start and end date, disable the category filter, and clear cache. If the event appears, add the parameters back one at a time. If it still does not appear even in the basic calendar, create a new minimal event without recurrence, maps, or custom fields.

The card expands, but required fields are missing

Symptom: the event has a location, map, custom meta field, or "add to calendar" data filled in, but those items do not appear on the public page. A common cause is that the field was not added in EventCard Designer. EventON separates data storage from output, so filled-in metadata does not automatically have to be displayed.

Fix: open EventON -> Settings -> EventCard Design, add the needed field to the layout, save the changes, clear the cache, and check the card again. If the custom meta field was created recently, reload the settings page and confirm that it appears among the unused fields.

The Google map is gray or does not load

Symptom: the location is specified, but the map is missing or replaced by a gray block. Check three levels: the Google Maps API key in EventON settings, the generate-map-from-address option inside the event, and the presence of the Google Maps field in EventCard Designer. Then open the browser console, because Google Maps JavaScript API errors often appear there first.

If the map is not essential, the safest rollback is to remove it from EventCard temporarily and leave only the address with a directions link. For sites with many events, that can even be better for performance. If the map is necessary, restrict the API key to the site domain and make sure the required APIs are enabled in Google Cloud.

The calendar is visible, but clicks, lightbox, or filters do not work

Symptom: events display, but they do not expand, filters do not respond, the lightbox closes strangely, or month navigation breaks. Possible causes: a JavaScript conflict, outdated or replaced jQuery, script optimization, AJAX page loading, or missing EventON files in the theme footer.

Check: open the browser console and look for red errors, temporarily disable JavaScript merging and deferred loading, and test the page on a default theme or with conflicting plugins disabled. You can look for EventON scripts in the page source, but do not make broad theme edits. If the problem disappears after optimization is disabled, set exclusions for EventON files.

Styles are not being applied

Symptom: CSS was added in EventON settings, but nothing changes on the public page. The official FAQ points to a possible issue with dynamic stylesheet generation caused by hosting restrictions. A safe solution is to enable the option in EventON -> Settings -> Scripts & Styling that writes dynamic styles to the header, then clear the cache.

If the issue persists, check CSS specificity and your theme's stylesheet load order. Do not add !important everywhere. It is better to refine the selector in the inspector, apply a small change, and validate it on one calendar.

The calendar page became slow

Symptom: the calendar opens noticeably slower after events were added. Causes include too many events in the initial output, heavy images, large EventCards expanding on the same page, too many add-ons, weak hosting, or an unoptimized database. The official documentation suggests cache, database optimization, removing inactive plugins, and opening heavy events on a separate page.

Start fixing it at the data level: reduce the number of events in the initial output, optimize images, check ux_val for the opening mode, and enable cache only after excluding conflicts. If the calendar is tied to tickets, RSVP, or WooCommerce, validate server requirements separately.

How to Maintain the Calendar After Launch

Once the calendar is published, it should not be considered finished. Unlike a static page, EventON changes along with the schedule: old events move into the past, new ones are added, recurring dates shift, venues close, online links get updated, and organizers may reschedule sessions. If no one is watching that process, even a well-configured calendar quickly starts undermining trust in the site.

A Simple Editorial Process

Assign one person to own the calendar and define a few simple rules. For each new event, the editor should enter the start and end date, format, category, status, location or online instructions, image, and a short description. If you use a custom meta field such as skill level or audience type, that field should be filled in for every event of the same kind. If a field is no longer relevant, it is better to remove it from EventCard Designer than leave an empty block in place.

Once a week, or before a busy period begins, check the upcoming events on the public page. Not just in the admin panel, but as a visitor would: open the calendar, expand a card, click a filter, check the mobile view, and make sure past events are hidden or remain visible exactly as intended. For organizations with dense schedules, a separate draft calendar is useful so the editor can test new categories, recurrences, and fields before they go live.

What to Do with Past and Canceled Events

Deleting all past events is not always the right choice. Past events may still matter for archives, internal reporting, or SEO pages. But on a homepage event listing, they often get in the way. So separate event storage from event output. One calendar can display only upcoming events, while another can show an archive or past events list if that is useful to visitors.

Canceled events should usually not be deleted immediately if visitors may already have seen the announcement. Set the appropriate status, add a short explanation, and decide whether those events should appear in the main calendar. If canceled events are hidden through a calendar parameter, make sure visitors still get the information through a news post, email, or a dedicated page if that matters.

Checks After Updates

After updating EventON, the theme, the cache plugin, or WordPress itself, repeat the basic test: the calendar is visible, events expand, filters work, the map displays, custom fields are present in the card, and styles are applied. The official EventON changelog regularly includes fixes related to search, lightbox, ICS, EventTop, maps, translations, and field display. That is normal for a complex calendar plugin, but it also means you should not treat "the site opened" as sufficient testing.

The safest update order: back up first, then update on a staging copy or during a low-traffic period, then check the draft calendar page, clear the cache, and validate the public version. If a problem appears only in one display mode, such as the lightbox or tile view, temporarily switch to a simpler output mode while you investigate the cause.

How to Keep the Calendar from Turning into Chaos

Every few months, review the structure of categories, locations, organizers, and custom meta fields. If categories duplicate each other, the filter becomes confusing. If locations are created in inconsistent ways, maps and filtering start behaving inconsistently. If editors add new fields without alignment, EventCard turns into a collection of random details.

For a large site, it helps to maintain a simple rules table: which categories are allowed, which locations should be reused, what image size is needed for tiles, which fields are required for online events, how cancellations are handled, and who checks the page after publication. That is not bureaucracy - it is how you keep the calendar readable. EventON offers a lot of flexibility, and that is exactly why it needs editorial discipline.

If the calendar is used for important events, create a small pre-publication checklist: date, time, end time, timezone, status, image, category, card, filter, mobile view, cache. Five minutes of review can save hours of support time when visitors start saying they cannot find the event, cannot open the map, or are seeing outdated information.

When CodeCanyon EventOn Is Worth Using on Your Site

CodeCanyon EventOn is a strong choice if you need more than a simple list of dates - you need a manageable event calendar inside WordPress, with cards, recurrences, locations, filters, statuses, images, shortcodes, and control over what visitors actually see. The plugin is especially useful when editors regularly add events in the admin panel and visitors need to quickly find the right date or format.

Before rolling it out, check the server, theme, cache, JavaScript, category model, and test events. After installation, do not try to use every feature immediately. First, get a stable core calendar working. Then configure EventTop, EventCard, filters, recurrences, maps, and appearance. If the calendar becomes an important part of the site, establish a small process: who creates events, who checks past dates, who updates statuses, and who handles images.

If that review matches your use case, you can get the CodeCanyon EventOn file and test the plugin on a site copy or draft page. That is safer than changing the live event listing right away: you will see the real settings, verify compatibility, and understand whether the core feature set is enough or whether you need add-ons.