EventON Weekly View - WordPress Plugin

Guide to Setting Up and Using EventON Weekly View

EventON Weekly View is not just about making the calendar look nicer. Its main purpose is to display EventON events on a week-by-week basis, so visitors can see the coming days, switch between weeks, quickly understand how busy the schedule is, and open an event card without digging through a long monthly list. In this guide, we will walk through how to prepare your site, enable weekly event display, configure the shortcode, choose a display style, verify the output, and troubleshoot common issues.

This guide is for site owners, WordPress administrators, and developers who already use EventON and want to make schedules easier to understand for classes, conferences, workshops, club meetings, sports programs, schools, studios, venues, and any project where the week is the natural planning unit. We will not repeat the short product description that already appears above on the page. Instead, we will go from the first events to a working calendar page.

An important detail about EventON Weekly View is that it does not replace the main EventON plugin. It adds a separate way to display events through its own shortcode, [add_eventon_wv]. That means setup should start not with appearance, but with the underlying data: events need correct dates, times, categories, locations, organizers, and a consistent color system. If your source events are organized inconsistently, the weekly view will expose that inconsistency faster than a standard monthly calendar.

When a Weekly Calendar Works Better Than a Monthly List

A weekly view is useful when visitors make decisions within a short time frame. A monthly calendar is good for showing the big picture, but it often forces people to click through dates and guess where the event they need might be. A weekly grid shifts the focus: it presents the coming days as a working schedule. This is especially helpful when a site has many events, but the visitor cares less about the entire archive and more about the upcoming week, a specific day, and quick access to details.

The official product page describes Weekly View as an addon that brings a weekly grid to the EventON calendar, along with color-coded day tabs, continuous week navigation, and faster access to future or past weeks. The shortcode documentation confirms a separate [add_eventon_wv] shortcode and a set of parameters for filtering, locking the calendar to a specific week, choosing a table style, setting event order, defining event-card behavior, and restricting access to logged-in users only. In practice, that means the plugin is best understood as a controlled weekly interface layered on top of events you have already created, not as a standalone calendar engine.

A typical example is a training center. The site has classes on Mondays, Wednesdays, and Fridays, several instructors, different subject areas, and recurring groups. A monthly calendar shows lots of dots, but it is hard for a new visitor to tell what they can attend this week. Weekly View places the days side by side, and the events are grouped within a short time range. If the visitor is choosing a class for the next few days, this kind of interface reduces clicks.

Another example is a conference with multiple tracks. Event color, or the color assigned to an event type, can act as a visual cue for each track. The visitor looks at the week, sees the busier days, opens the event card they need, and uses filters if necessary. It is not a full room-by-room schedule with time-slot cells, but for many programs where events do not require complex slot-based booking, a weekly view is enough.

Where Weekly View Usually Makes Sense

• Schedules for classes, training sessions, club meetings, lectures, and recurring workshops.
• Event pages for venues where visitors need to see the next few days rather than the full year.
• Conferences and intensive programs where events are spread across weekdays and may use color-coded categories.
• Internal pages for logged-in users, when the calendar is meant only for members or staff.
• Pages filtered by event types, locations, or organizers, if the source EventON taxonomies are already filled in.

When Another View Is a Better Fit

If visitors need to plan for an entire season, a yearly program, or a festival calendar, Weekly View may be too narrow. In that case, Yearly View or Full Cal is often a better fit. If someone only needs to see today's classes or move through the schedule one day at a time, Daily View is usually clearer. If you need a true booking board with time rows and open slots, Weekly View's grid may not cover the task without separate customization.

Practical check: before installing it, define the visitor's main question. If it sounds like "What's happening this week, and on which day?", Weekly View is a good match. If it sounds like "What hourly openings are available?" or "What's happening all year?", you need a different format.

What to Check Before Installing It on WordPress

EventON Weekly View depends on the main EventON plugin. That is the first limitation, and it is not optional. The addon does not create an independent event system. It pulls events, categories, locations, organizers, dates, images, and card behavior from EventON. That means preparation starts with WordPress and server compatibility, the main EventON installation, and the quality of the events themselves.

The official EventON system requirements list separate minimum requirements for the core plugin and higher requirements for sites that use addons. For EventON with addons, the developer recommends a current version of WordPress, a modern PHP version, a sufficient memory limit, enabled permalinks, and working WP-Cron. If the site has a large number of events, multiple addons, ticketing, or WooCommerce, the requirements may be higher. This guide does not lock itself to a specific number as if it were a permanent rule, but before rolling out the weekly view, you should check your server settings against the developer's current documentation.

Minimum Product Preparation

Before installation, do a content check, not just a technical one. Weekly View will display the week, but it will not fix poorly created events. If an event is unpublished, tied to a past date, hidden by a filter, or missing correct time data, the issue will show up as an empty day, incorrect order, or the impression that the plugin is not outputting anything.

• The main EventON plugin is installed and active. The WordPress admin area should include an events section and EventON settings.
• Create test events. For testing, it is best to create 5 to 8 events on different days of the same week, including at least one day with no events.
• Start date and end date are filled in. EventON documentation specifically warns that missing an end date can cause display issues for multi-day events.
• Categories and colors are intentional. If you plan to use color-coded tabs and filtering, configure event types and colors in advance.
• The calendar page is not overloaded. On a single page, it is best not to mix many heavy widgets, complex tables, maps, and multiple calendars without a clear reason.
• Cache can be cleared or temporarily disabled during testing. EventON documentation and support cases often reduce initial diagnostics to checking cache, conflicting scripts, and compatibility mode.

User Permissions and a Safe Test Location

It is easier to configure a weekly calendar while logged in as an administrator or editor who is allowed to edit pages and work with blocks. If the EventON block or shortcode generator does not appear in the editor, first check whether EventON is active, whether the user role has the right permissions, and whether optimization plugins are interfering. The official shortcode generator documentation recommends testing complex combinations on a draft page. This is especially important for Weekly View because parameters like fixed_week, week_style, table_style, event_type, and ux_val are easy to combine but hard to debug on a live page with real traffic.

The best setup is a separate test page that is hidden from indexing or available only to editors. There, you can output a simple [add_eventon_wv], then add parameters one at a time and compare what changes. That helps you separate a plugin issue from a content issue, theme issue, cache issue, or an overly complex shortcode.

Installing the Addon and Running the First Check Without Advanced Parameters

EventON Weekly View is installed like a standard WordPress plugin: go to Plugins, choose Add New, upload the ZIP file, and activate it. The official EventON addon instructions describe exactly that flow. This guide does not cover purchasing, licensing, or obtaining the paid version. We assume you already have a valid installation archive and access to a site where you can test the extension safely.

After activation, do not start with a large set of parameters right away. The first goal is to confirm that the addon is connected to EventON and can output a basic weekly calendar. To do that, create or open a test page, add an EventON block or a standard shortcode block, and paste in the minimal shortcode:

[add_eventon_wv]

Save the page and open it on the public side of the site. If there are events in the current week, you should see the weekly interface. If no events appear, that is not automatically an error: the selected week may actually be empty, the events may be in a different week, or global settings may be hiding past events. That is why your first check should rely on test events you created in advance.

How to Tell the Addon Is Connected Correctly

• The page displays a weekly calendar instead of raw shortcode text.
• Days of the week appear as separate interface elements, and events are attached to the correct dates.
• When you switch weeks, the calendar does not disappear or freeze during loading.
• When you click an event, the selected EventON behavior works: the card expands, a popup opens, or the event page loads, depending on your parameters.
• Event colors match the event settings or the event type, if category color override is enabled.

Why a Simple Test Matters More Than an Instant Polished Result

Many weekly calendar issues look like design problems, but they actually start with the data. A wrong date, a hidden filter, a past event, a cache conflict, or another shortcode on the same page can all produce the same symptom: no events, events opening the wrong way, the table rendering like a list, or navigation jumping to the wrong week. A minimal shortcode helps you see the baseline state without extra noise.

Quick takeaway: if [add_eventon_wv] does not output a weekly calendar on a page with published test events, do not move on to styling. First check whether EventON is active, whether event dates are correct, whether user permissions are sufficient, whether cache is involved, and whether the theme or nearby plugins are causing JavaScript errors.

Configuring the Shortcode: From Basic Output to a Controlled Weekly View

The shortcode is the main working area of EventON Weekly View. The official shortcode guide lists the [add_eventon_wv] parameters that control which events appear in the weekly calendar, how they open, which week style to use, and whether filters should be displayed. EventON's shortcode generator helps assemble those parameters through the interface, but it is still useful to understand what each one actually changes.

Start with the page's purpose. A "This Week's Schedule" page usually needs the current week, visible filters, and clear event cards. A "Conference Week" page may need to be locked to a specific week and filtered by category. A "Members-Only Classes" page may need to be restricted to logged-in users. These use cases rely on the same addon, but with different parameters.

Parameters Worth Starting With

Do not turn the shortcode into a long string of every possible parameter. If a parameter does not solve a real need on the page, leave it out. The fewer unnecessary conditions you add, the easier the calendar will be to maintain after an EventON, theme, or caching-plugin update.

Examples of Working Shortcodes

For a standard weekly schedule page, you can start like this:

[add_eventon_wv week_style="1" table_style="1"]

For a page tied to one specific event week, use a fixed date. The important point is that a fixed week should be used together with month and year:

[add_eventon_wv fixed_week="2" fixed_month="7" fixed_year="2026" week_style="1" table_style="1"]

For a page dedicated to one track, such as lectures or training sessions only, add an EventON category. The category ID should come from the WordPress admin area, not from guesswork:

[add_eventon_wv event_type="23" week_style="1" table_style="1" exp_so="yes"]

If you want to display the weekly calendar only to registered participants, you can use:

[add_eventon_wv members_only="yes" week_style="1"]

How to Work Through the Shortcode Generator

EventON documentation describes several entry points to the Shortcode Generator: through the classic editor, the EventON block in Gutenberg, and the EventON - Settings - Shortcodes section. For Weekly View, this is a convenient and safe option if you do not want to remember parameters manually. Insert the EventON block, open the calendar generator, choose the matching calendar type, and enable parameters one by one. After each change, look at how the shortcode string changes.

If the generator does not show the setting you need, do not try to compensate with a random parameter from someone else's example. First check whether Weekly View is active, whether EventON is up to date, whether an editor plugin is hiding the button, and whether that option is available in your version of the addon. For a complex page, save the final shortcode in a separate note so you can easily compare the working and broken versions after an update.

Two Weekly Styles: List, Table, and Color Cues

One reason to use EventON Weekly View is the ability to choose between a simpler weekly layout and a table-style format where events are understood as a distribution across days. The official product page specifically mentions a weekly grid, week style, color-coded tabs, day strip, and table style with bold, color-rich events. The changelog confirms that the table style evolved as a separate area, with new design work, fixes to event order, card opening behavior, grid styles, and display issues when switching weeks.

In practice, that means you should choose the weekly style not by how pretty it looks in a demo, but by how visitors read the schedule. If there are only a few events and the detailed cards matter most, the list style may feel calmer. If the page contains many short events, classes, and sessions, the table style is usually better at making each weekday feel like its own container.

When to Choose the Table Style

The table style makes sense if you have 3 to 7 events per week spread across different days, and visitors need to compare the schedule quickly. For example, a sports school may want to show training sessions by group, while a conference may want to show sessions by day. In that case, the combination of week_style="1" and table_style="1" gives you a more expressive weekly layout.

But the table style has a catch: it is more sensitive to the theme, container width, custom CSS, and JavaScript conflicts. In support discussions, there are cases where the table did not render the way users expected, and updating EventON, resaving events, or testing in diagnostic mode helped separate a data issue from a styling issue. That is why, after enabling the table, you should test not only on desktop but also on mobile screens.

When to Keep the Default Weekly Output

The default style is easier to read when events have long titles, images, descriptions, organizers, and different card-opening methods. It may work better for a site where visitors choose a day first and then read event details. This format feels less like a dense schedule board and tends to work better on pages with limited content width.

Event Color vs. Event Type Color

Weekly View uses color cues for both days and events. The shortcode documentation lists the etc_override parameter, which lets you override event colors with event-type colors if those colors are configured. This can be useful for conferences, schools, studios, and venues where color represents a track or subject area, for example lectures, practical sessions, kids groups, or open meetings. But this parameter should only be enabled after your event types themselves are set up cleanly.

If every event has its own manually assigned color and categories also have colors, visitors may end up with a contradictory visual system. Decide in advance what color means. One level should be primary: either event color indicates status or importance, or category color indicates subject area. Color should help visitors choose an event, not just decorate the page.

What to Check After Switching Styles

1. Open the calendar page outside admin mode so you see it the way a visitor does.
2. Check a week with several events and a week with only one event, because empty days often reveal grid problems.
3. Click an event in each day and make sure ux_val behaves the same way throughout.
4. Narrow the browser window or open the page on a phone to check wrapping, card height, and navigation access.
5. Clear the page cache if styles or scripts were updated but the appearance did not change.

Filters, Categories, and Fixed Weeks Without Accidental Omissions

Weekly View becomes especially powerful when the weekly calendar shows not every event at once, but the right slice of the schedule. The documentation confirms parameters such as event_type, event_type_2, event_location, event_organizer, filter_type, exp_so, and hide_so. These let you build pages around specific tracks, venues, presenters, or use cases. But filters are also the source of the most common false impression that the calendar is broken.

If the shortcode includes event_type="23", Weekly View will show only events from that category. If an event was created correctly but belongs to a different category, it will disappear from the calendar. If past events are hidden, older entries may also drop out of the output. If a fixed week is set without month and year, the calendar may start somewhere other than where you expect. That is why filters should be handled as rule-based configuration, not as a cosmetic option.

How to Safely Build a Single-Track Page

Suppose you need a page called "This Week's Yoga Classes." In EventON, create an event type or category for yoga classes, assign it to every relevant event, and note the ID. Then, on a test page, first output the full weekly calendar with no filter. Make sure the yoga events are there. Only after that should you add event_type.

[add_eventon_wv event_type="23" week_style="1" table_style="1"]

After saving, compare the number of events in the admin area with the public page. If some events disappear, do not blame Weekly View first. Check the category assignment, the event date, and the settings that hide past events. This order saves time: you do not argue with the visual output until you have confirmed that the source data actually matches the filter.

How to Use a Fixed Week

A fixed week is useful for pages tied to a specific event, conference, festival block, or weekly program. In a developer support reply about Weekly View, it was noted that fixed_week works correctly together with fixed_year and fixed_month. That matches the logic of the official shortcode guide: a week number by itself is not enough, because the same week number across different months and years can produce ambiguous output.

[add_eventon_wv fixed_week="4" fixed_month="7" fixed_year="2026" week_style="1" table_style="1"]

Do not use a fixed week on a page that should always show the current schedule. For that kind of page, it is better to leave the current week in place or use week_incre if you need to start with the nearest future week. A fixed week is useful for a static event, but it is a poor fit for a schedule that updates continuously.

When to Expand Filters Immediately

The parameter exp_so="yes" can be helpful if visitors need to see filter options right away. For example, a conference weekly program may include several tracks, and without an expanded filter panel, users may not realize they can narrow the schedule. But on a simple single-track page, an open panel may be unnecessary.

If you want to hide sorting and filters completely, use hide_so carefully. Hiding them makes for a cleaner schedule, but it reduces self-service discovery when there are many events. The rule is simple: filters are useful when visitors are choosing among different event types. If the page is already filtered by the shortcode itself, the public filter panel may not be needed.

Practical Example: A Conference Weekly Program

Let us walk through a complete working example, because this is where EventON Weekly View shows how it functions not as a standalone visual, but as a combination of EventON data, shortcode settings, and public-side verification. The task is to create a weekly conference program page where visitors can see sessions by day, distinguish tracks by color, and open the event card for details.

Goal

The goal is a page called "Week Program" where conference events appear in a table-style weekly layout. Each event has a title, date, time, track or category, color cue, and a detail card. Visitors should immediately understand which day a session takes place, click the event, and see more information.

Preparation

First, create test events in EventON. Do not build the full hundred-session program right away. For the first check, 8 to 12 events in a single week are enough. For each event, set the start date, end date, time, description, organizer or speaker, location, track category, and color system. If you have images, add a featured image only to part of the events so you can see how it affects card height and load time.

Then configure event types. For example: "Main Hall," "Workshop," "Beginner-Friendly," and "Partner Session." If you want to use category color, assign colors to those types and later enable etc_override="yes". If color should stay unique to each event, do not enable event-type color override.

Setup Steps

1. Create a test page and insert the minimal shortcode [add_eventon_wv].
2. Check that the conference events appear in the correct week and open when clicked.
3. Add the table style: week_style="1" and table_style="1".
4. If the page is dedicated to one specific conference week, add fixed_week, fixed_month, and fixed_year together.
5. If you need to show only conference events, add event_type with the ID of the matching category.
6. If visitors need to filter tracks, enable the expanded filter panel with exp_so="yes".
7. Choose the card behavior through ux_val: expand on the page, popup, or event page.
8. Check the mobile layout and week-switching behavior.

The final shortcode may look like this:

[add_eventon_wv event_type="31,32,34" fixed_week="4" fixed_month="7" fixed_year="2026" week_style="1" table_style="1" exp_so="yes" ux_val="3" etc_override="yes"]

This example should not be copied blindly. What matters here is the structure: filtering by categories, a fixed week, table style, expanded filters, popup event opening, and color override from event types. If you do not use color categories, remove etc_override. If the page should always show the current week, remove the fixed parameters.

Verifying the Output

Open the page on the public side of the site and compare it with a checklist. Events should appear under the correct days of the week. An empty day should look clean rather than breaking the grid. The event card should open according to the selected ux_val. Filters should not just appear, but actually change the event set. If etc_override is enabled, colors should match the event types.

Common pitfall: if the table style places events under the wrong days, first resave the test events, check the dates, and confirm EventON is updated. In support cases, some issues looked like layout bugs but were resolved by updating or resaving events after a date change.

Checking the Output on the Page, in the Theme, and on Mobile

Testing Weekly View should go beyond simply confirming that "the calendar appeared." The weekly view interacts with the theme, container width, EventON scripts, cache, event images, the event card, filters, and click behavior. If you only check it from the admin side, you may miss what a regular visitor will actually see.

Public-Side Check

Open the page in a regular browser window where you are not logged in. If members_only="yes" is enabled, check both the logged-in and guest views separately. Make sure the calendar does not output raw shortcode text, does not disappear after loading, and does not require a confusing first click from the visitor. If you enabled hide_events_onload="yes", add a short explanation to the page telling visitors to choose a weekday. Without that context, they may assume there are no events.

What to Look for on Desktop

• The week displays the correct range, especially if a fixed week is being used.
• Events do not overflow the container or overlap neighboring days.
• Day tabs, color markers, and hover cues are readable.
• Filters do not cover an important part of the calendar or disappear beneath theme elements.
• Switching weeks does not leave the page stuck in endless loading.

What to Look for on Mobile

The official product page says Weekly View is responsive, but the final behavior still depends on the theme and page container. Check the width on a real phone or in browser dev tools. Look not only at the overall layout, but also at interaction: does the event card open, can visitors tap a day, is the navigation area large enough, and does a sticky header cover dropdown elements.

Performance Check

Weekly View may feel nearly invisible on a page with only a few events, but on a large schedule it becomes more sensitive to images, filters, multiple calendars on the same page, and third-party scripts. EventON's official requirements note that sites with a high volume of events and multiple addons may need more memory and caching support. So do not test against an empty calendar. Test against real data volume.

The practical order is this: first test a page with 10 to 20 events, then test with the real program, then test with images and filters enabled. If loading becomes noticeably slower after adding many events, do not reinstall the plugin blindly. Check image size, the number of calendars on the page, cache, PHP memory, and unnecessary page scripts.

Detailed Post-Install Setup: Appearance, Event Card, and Click Behavior

After the first check comes the most important part of the setup. Weekly View has several control layers: global EventON settings, WeeklyView appearance settings in the Appearance section, parameters in the specific shortcode, and event card settings. New users often mix these layers together and try to solve everything with a single parameter. A more practical approach is top-down: first make sure the events are correct, then choose the weekly style, then configure the color system, then define the click behavior, and only after that add CSS.

The official Weekly View page says the appearance of the weekly layout can be adjusted through EventON Settings - Appearance - WeeklyView. EventON documentation also separates Appearance, Event Card Designer, Language, and Styles into different areas. For an administrator, that means the color of the weekly grid, the labels, and the event card may live in different parts of the interface, and not every appearance change is made directly in the shortcode.

Start With the Elements That Shape How the Week Is Read

In a weekly calendar, visitors read three things first: the week range, the day tabs, and the events themselves. If those elements compete with one another in color, size, or contrast, the calendar loses clarity. So begin with baseline readability, not decorative details.

• Week range. It should stand out, because visitors need to know which week they are looking at after using the arrows or selecting a future week.
• Day tabs. They should clearly show both days with events and empty days. If an empty day looks like an error, visitors lose trust in the schedule.
• Event color. Color should communicate one thing: type, track, status, or individual formatting. Do not use it as random decoration.
• Event title. It should fit within the card or row without cutting off key words, especially on mobile.
• Card opening behavior. Pick one clear pattern: expand, popup, or separate page. Mixing expectations on the same page frustrates visitors.

Configuring the Event Card

Weekly View gives users a weekly entry point into an event, but the event details usually open through EventCard or the event page. That means the usefulness of the weekly calendar depends on what people see after they click. EventON includes Event Card Designer and EventTop Designer to control the structure and appearance of the card. If the card does not include the time, location, organizer, or a next-step button, the weekly grid may look good but still fail to help users make a decision.

For a weekly schedule, it is usually best for the event card to include a short description, time, location, organizer, an image only when it adds real value, and a link to details. If every event includes a large image and a long text block, the page can become heavier and visually noisy. But if the card is too sparse, visitors are forced to keep clicking. Aim for balance: show what helps users choose an event in the weekly view, and leave the deeper material for the event page.

Which Event Fields to Check

1. The event title clearly explains what will happen, rather than consisting only of an internal program code.
2. The start date and end date are filled in, and the time matches the real schedule.
3. Location and organizer are set where they affect the visitor's choice.
4. The event type is assigned correctly if you use filtering or category color.
5. A featured image is added only when it truly helps distinguish the event or strengthen the card.

Click Behavior Through ux_val

The ux_val parameter matters just as much as appearance. The documentation lists interaction options such as no action, event card expansion, popup, separate event page, and opening in a new window. The best choice depends on how much detail the visitor needs. For a short program, expanding the card may be enough. For a conference with long speaker bios, materials, and registration, a separate page or popup may be a better fit.

Test ux_val in the exact weekly style you are using. The Weekly View changelog includes fixes related to opening events in table style, so you should not assume that click behavior is identical in every combination. If you use week_style="1" and table_style="1", click events across different days, at the beginning and end of the week, with and without images.

Setup guideline: the weekly calendar should answer the question "where should I go next?" If visitors get too little information after clicking, improve the EventCard. If they get too much and lose the schedule page, try a different opening mode.

Calendar Language and Labels

EventON documentation notes support for language variations through the lang parameter and the Language settings. For a Russian-language site, it is important to check not only the general EventON strings, but also the text that appears in the weekly view: empty-event labels, day names, navigation elements, cues, and messages. If part of the text remains in English, first check the EventON language settings. If a specific string does not change, document it as a version limitation and avoid making risky edits to plugin files.

For a multilingual site, do not force one calendar to serve all languages if the events and labels need to differ. It is better to create separate pages or shortcodes with the appropriate lang and filters, then test each page separately. That helps avoid a situation where the Russian page shows the correct week but opens a card with the wrong interface strings.

How to Prepare Events So the Weekly Grid Does Not Mislead Visitors

Weekly View is especially demanding about event quality because it shows a narrow date range. In a monthly view, a date mistake can sometimes get lost among other elements. In a weekly view, it stands out immediately: an event falls on the wrong day, a recurrence spreads too broadly, a category hides the needed block, or an empty week looks like a malfunction. That is why event preparation should be treated as its own stage.

Dates, Event End Times, and Events That Run Past Midnight

The official EventON event-creation guide recommends always setting an end date, because otherwise multi-day events may display incorrectly. This matters even more in Weekly View. If an event starts in the evening and ends after midnight, visitors may think of it as part of one day, while the calendar logic needs to understand the real date range. Check where you want that event to appear: on the start day, on both days, or inside the card with a clear time range.

Do not try to fix a date issue with Weekly View parameters. If an event lands in the wrong place, open the event itself and check Time & Date. If it repeats, check Repeat Event. If it is hidden as a past event, check the global Time Settings and the shortcode parameters. Fixing the source event is always more reliable than hiding the problem with a filter.

Recurring Events

Recurring events are one of the most common causes of unexpected output. EventON supports recurring events, and Weekly View should show the instances that fall within the selected week. If the recurrence is configured incorrectly, you will see either extra events or empty days. So treat recurring events as a separate test case: create one recurring template, verify the weekly output, and only then add your real recurring classes.

For regular classes, it helps to decide in advance what counts as one event: the full series or each individual session. If every meeting needs its own description, instructor, or location, it may be simpler to create separate events. If the sessions are identical, recurrence may be more convenient. Either way, review the finished week through a visitor's eyes, not just through the admin list.

Categories, Locations, and Organizers as Navigation Layers

Weekly View supports filtering by event_type, event_type_2, event_location, and event_organizer. These parameters are useful only when EventON taxonomies are used consistently. If one event is labeled by subject area, another by format, and a third by audience, the filter becomes unpredictable. Visitors select one category and do not understand why part of the schedule disappears.

For a weekly calendar, a better structure is this: the first event type handles the primary category, the second event type handles additional grouping, the location identifies the venue, and the organizer identifies the presenter. Do not mix those layers. That way, you can build multiple pages: the full week, one subject area, one venue, or one organizer. They all use the same Weekly View, just with different parameters.

Mini Event Audit Before Publishing

• The selected week includes at least a few events so you can verify both empty and filled days.
• Every event has an end date and correct time.
• Event types follow one consistent system instead of being assigned randomly.
• Locations and organizers are filled in only where they actually help with filtering or event choice.
• Recurring events are checked on the public side of the site, not only in the admin area.
• Events with and without images both look equally clean.

This audit is best done before final styling. Otherwise, you may spend time on colors and CSS only to discover that the main usability problem was an inconsistent event structure.

Safe Appearance Improvements Without Editing the Plugin

EventON lets you adjust appearance through its own Appearance and Styles sections. For Weekly View, the official product FAQ points to EventON Settings - Appearance - WeeklyView as the place to change colors, fonts, and styles. EventON documentation also describes a Styles section for custom CSS. That means safe customization should start with settings, not with editing addon files.

The code below is a small CSS adjustment for the table-style weekly layout. It is based on public developer support examples for the .EVOWV_content.wk_1 class, but it still needs to be tested on a site copy or test page, because your theme may override styles differently. Put the CSS in a safe location: EventON - Settings - Styles, the theme's Additional CSS area, or a child theme. Do not edit EventON or Weekly View files directly.

.EVOWV_content.wk_1 .evowv_col_events .event .time {
  font-size: 16px;
  float: left;
  padding-right: 10px;
}

.EVOWV_content.wk_1 .evowv_col_events .event {
  line-height: 1.35;
}

This tweak makes the event time more prominent and helps separate the time from the title in table style. After adding it, check the page on both desktop and phone. If the time starts overlapping the title or the card looks worse, remove the CSS or keep only the first line with the font size. Rollback should be just as simple as insertion: remove the snippet, clear the cache, and recheck the page.

When CSS Is Not the Right Fix

Do not add CSS if the problem is not visual, but instead comes from missing events, a wrong date, broken click behavior, slow loading, or a script conflict. CSS can hide a symptom, but it cannot fix the cause. If the calendar disappears after loading, events open the wrong way, or the week switches incorrectly, you first need to diagnose the data, the shortcode, and JavaScript conflicts.

Using It Alongside Filters Plus and Event Tickets

The official Weekly View page suggests pairings with Filters Plus and Event Tickets. In practice, these should be treated not as required installations, but as separate use cases. Filters Plus can help if the weekly program includes many event types and visitors need more advanced filtering. Event Tickets makes sense if events are actually being sold through the EventON, Tickets, and WooCommerce stack. In both cases, the rollout should be gradual: first a stable weekly grid, then filters or tickets, then testing clicks, cache, and performance.

If you add Filters Plus, first configure categories and the basic EventON filter panel, then add the advanced filtering layer. If you add Event Tickets, test the event card, button presence, WooCommerce behavior, and site load separately. Do not roll all changes into one pass. The more addons are involved on the page, the more important it becomes to use a separate test page and maintain a clear rollback plan.

Troubleshooting and Fixing Common Weekly View Issues

Most Weekly View issues come from one of five places: event data, shortcode parameters, display style, cache, or script conflicts. The Weekly View changelog shows that the developer has fixed bugs related to fixed weeks, week switching, the table layout, the loader, event order, EventON compatibility, and hiding events on load. Support discussions add practical symptoms: a fixed week does not work without the full parameter set, the table may conflict with third-party JavaScript, and events may land on the wrong day because of dates or stale event data.

The Calendar Does Not Render and the Shortcode Is Visible on the Page

Symptom: instead of a calendar, visitors see the text [add_eventon_wv] or an empty block. A likely cause is that the addon is not active, the main EventON plugin is not working, the shortcode was inserted in a place where WordPress does not process shortcodes, or the page was created inside a builder that escapes the text.

What to check: whether EventON and Weekly View are active, whether the Events section exists in the admin area, whether the shortcode was inserted through a shortcode block or EventON block, and whether there are stray spaces inside the square brackets. If the shortcode is inserted into a theme template, use the standard WordPress approach with do_shortcode() only in a child theme or safe snippet.

How to fix it: output the minimal shortcode on a normal WordPress test page. If it works there, the problem is the insertion point or the page builder. If it does not work there either, go back to the addon installation and activation.

A Fixed Week Still Shows the Current Week

Symptom: you set fixed_week, but the calendar still opens the current week. In a Weekly View support reply, the developer noted that a fixed week requires fixed_year, fixed_month, and fixed_week together.

What to check: whether all three parameters are present in the same shortcode, whether the values were pasted without smart quotes, whether spaces separate the parameters, and whether events actually exist in the specified range.

How to fix it: start with a short test and no filters:

[add_eventon_wv fixed_week="4" fixed_month="7" fixed_year="2026"]

If the correct week opens, add week_style, table_style, and filters one at a time.

Events Do Not Appear or Only Some of Them Show Up

Symptom: events exist in the admin area, but Weekly View shows an empty week or an incomplete list. For similar cases, the official EventON documentation recommends checking the shortcode, filter parameters, event dates, and the global past-event hiding setting.

What to check: the event start and end date, publication status, event_type category, event_location, event_organizer, past-event hiding settings, and the selected week.

How to fix it: temporarily remove filters from the shortcode and see whether the event appears. If it does, the filter is the cause. If it does not, open the event, check the dates, and save it again. For recurring events, also review the recurrence settings in EventON.

The Table Style Turns Into a Wide List

Symptom: you expect events under day columns, but instead you see them as wide rows. In Weekly View support cases, users were advised to use both parameters: week_style="1" and table_style="1". There were also cases where updating and resaving events normalized the output.

What to check: whether both parameters are present, whether the shortcode contains conflicting values, whether EventON and Weekly View are up to date, whether the theme is breaking the CSS grid, and whether the events have correct dates.

How to fix it: first test the short shortcode [add_eventon_wv table_style="1" week_style="1"]. If that works, the problem is in additional filters or page content. If it does not, check for updates, switch to a temporary default theme in safe diagnostic mode, and rule out a CSS conflict.

The Calendar Loads and Then Disappears

Symptom: Weekly View begins to render, but then vanishes or freezes. One support case linked this behavior to a JavaScript error from another product on the page, and testing in diagnostic mode showed that EventON itself was working.

What to check: the browser console, caching and optimization plugins, deferred JavaScript loading, nearby tables, maps, page builders, custom scripts, and whether the same issue appears on a clean test page.

How to fix it: temporarily disable script combining and deferred loading for the calendar page, clear the cache, and check the conflict in safe mode. If the issue disappears only when a specific plugin is disabled, configure exceptions for EventON scripts or keep the calendar on a separate page without the conflicting element.

Styles Do Not Apply on the Public Site

Symptom: you changed colors or CSS, but the calendar still looks the same on the live page. The official EventON documentation describes a situation where the dynamic stylesheet is not generated because of hosting restrictions, and recommends enabling output of dynamic styles in the page header through the Scripts & Styling settings.

What to check: where the CSS was added, whether cache was cleared, whether CSS minification is active, the priority of theme styles, and the EventON dynamic styles setting.

How to fix it: save the EventON settings, clear the cache, and temporarily disable CSS minification for testing. If the dynamic stylesheet is not updating, use the official option to output dynamic styles in the header, and keep your custom CSS in one clear location.

The Weekly Calendar Is Slow

Symptom: the week takes a long time to load, especially when there are many events, images, or extra filters. Possible causes include heavy images, too many events in one date range, multiple calendars on one page, a low memory limit, complex queries, cache, other addons, and third-party scripts.

What to check: featured image size, the number of events in the selected week, the number of calendars on the page, filter parameters, EventON's server requirements with addons, page cache, and object cache. If you use Event Tickets and WooCommerce, the load will be higher.

How to fix it: reduce image sizes, avoid showing multiple heavy calendars on the same page, keep only the filters you actually need, and check the PHP memory limit and cache. If the calendar has to display a large program, it is usually better to split it into pages by track or by week than to force everything into one output.

Limitations Worth Knowing Up Front

EventON Weekly View works very well for weekly schedule browsing, but it should not be treated as a universal booking system. In one support discussion, a user wanted a grid with days as columns and time as rows, where empty intervals showed venue availability. The response made it clear that this kind of use case requires separate customization. That leads to an important practical conclusion: Weekly View shows a week's events, but it does not turn EventON into a full free-slot scheduling board.

Not Every Scheduling Use Case Is the Same

If your site sells bookings for specific time intervals, checks resource availability, blocks overlaps, and shows open time windows, you may need a booking plugin or a custom integration. Weekly View can serve as an event showcase, but it is not required to manage availability. For a studio publishing class schedules, that is completely fine. For court rentals or room bookings in 30-minute intervals, it may not be enough.

A Current-Day Filter Is Not the Same as a Weekly View

In one support case, a user wanted Weekly View to show only the current day when the page first loaded. The answer pointed to hide_events_onload="yes" as a way to hide events until a click, and suggested looking at Daily View for a true day-only focus. So if the page's main purpose is "today only," do not force Weekly View into it. Use a daily format if it better matches visitor behavior.

The Impact of Updates

The Weekly View changelog shows a long history of fixes, including compatibility with EventON versions, week calculation, event order in the table, initial loading, and styling. This is not a weakness of the product. It is the normal reality of a calendar addon: dates, time zones, recurrences, and interactive navigation create a lot of edge cases. So before updating EventON and its addons, make a backup, test on a site copy, and save your working shortcodes.

How to Decide and Move to Download

EventON Weekly View is a strong choice if your site already uses EventON, your events are filled in cleanly, and visitors need a clear weekly view instead of a large monthly calendar. The strongest use cases are recurring classes, conference programs, club meetings, venue schedules, single-track pages, and private weekly calendars for members.

Before rollout, check three things. First, the main EventON plugin and your events work correctly without Weekly View. Second, the weekly interface truly answers the visitor's question. Third, you are ready to maintain the shortcode as part of the page: keep the working parameters documented, test updates, and avoid piling on too many filters without a reason.

If, after testing, you can see that the weekly grid fits the job, you can get the EventON Weekly View file and test the addon on a site copy or a separate test page. Do not move the new calendar straight onto a key traffic page. First build one simple shortcode, confirm the dates are correct, then add style, filters, and card behavior.

Final pre-publish check: visitors should be able to see the week, understand which days have events, open an event card, apply a filter if needed, and move to a neighboring week without guidance. If any one of those steps is unclear, refine the page before publishing.

When EventON Weekly View Is the Right Choice

Use EventON Weekly View if you already have an EventON event base and want to give visitors a short, clear weekly path: day, event, card, neighboring week, and filter if needed. This addon works especially well when the week is a real decision-making unit, not just an arbitrary midpoint between day and month.

Do not choose it just because a weekly grid looks compact. Start by checking the use case: recurring classes, an event program, a venue schedule, a conference week, or a private member calendar. Then build a simple shortcode, add the necessary style, configure filters, and test the public page. That order gives you a controlled outcome and helps you quickly see whether the issue is in the events, the parameters, the theme, the cache, or unrealistic expectations of the format itself.

If testing shows that visitors find the right event faster, spend less time wandering through the month, and confidently open the details they need, Weekly View is doing its job. If instead the user needs a day-focused view, a year-level overview, or a board of open time intervals, it is better to choose a different format honestly than to overload the weekly calendar with tasks it was never designed to handle.