EventON Include Anything - WordPress Plugin

EventON Include Anything Guide: How to Add Posts and Other Content Types to an EventON Calendar

EventON Include Anything is not meant to create yet another calendar. Its purpose is to neatly pull regular WordPress content into an existing EventON calendar. In this guide, we will walk through how the addon works, where the Include in Events metabox appears, how to set the display window, what the custom title, subtitle, color, link, and tracking code control, and why the calendar page must include the include_any="yes" parameter.

This guide is written for a site owner, editor, marketer, or developer who needs to connect an EventON calendar with site content such as courses, products, announcements, campaign pages, blog posts, or internal landing pages. We are not going to repeat the product's marketing copy. Instead, we will go through the full workflow: preparation, installation, setup, a practical use case, result verification, troubleshooting, and choosing alternatives.

The key thing to understand about EventON Include Anything is that it does not turn a WordPress post into a full EventON event with a location, organizer, repeating schedule, and the full set of event fields. It inserts that post into the calendar stream as a special item that appears next to events and sends the visitor to the right page. You need to understand this before you configure it, because that boundary shapes your content model, filters, validation process, and your editors' expectations.

This article covers only confirmed functionality: including post types in the calendar, the metabox on the post edit screen, start and end display dates, a custom title and subtitle, color, a custom link, opening the link in a new window, tracking code, the include_any="yes" parameter, setup through the Shortcode Generator, and known limitations from support threads. Where the documentation is not explicit, the recommendation is phrased carefully as a practical check rather than a promise that a feature exists.

What the Addon Actually Does and Where Its Limits Are

EventON itself builds a calendar around its own event posts. An event has a date, time, EventTop, EventCard, status, location, organizer, image, click behavior, and other fields configured in the EventON admin panel. Include Anything solves a different problem: it lets you take a regular WordPress post or another post type and display it in an EventON calendar as a separate calendar item.

This is useful when the calendar on a site serves not only as an event schedule but also as a navigation hub for content with a time-sensitive purpose. For example, a training center can show course pages in an enrollment calendar, a store can place a product or promotion inside an event calendar, a club can surface announcement posts, a media site can feature curated collections, and a nonprofit can highlight campaign pages. The point of the addon is to avoid creating a duplicate event just to surface an existing page.

EventON documentation describes this as including WordPress post types in the calendar. In WordPress, a post type is a content type: posts, pages, attachments, and custom types registered by plugins. One important example from the official instructions is WooCommerce, which registers the products post type, so a product can also be a candidate for calendar display if that fits your use case.

At the same time, Include Anything does not give a regular post the full set of event fields. In a product support discussion, the developer explains directly that the addon is meant to add, for example, posts to the calendar so that a visitor clicks through to the single post page. A request for location, organizer, and category on those included posts was described as an unsupported use case. Because of that, do not plan to use Include Anything as a replacement for EventON events if you need full event fields, event-based filters, recurring events, or a more complex event card.

Input, Processing, and Output

The workflow is easiest to understand as a short chain. You start with a regular post, page, or custom post type. The editor includes it in the calendar through the Include in Events metabox, sets the display window, and defines its presentation. Then the calendar page must request those items through the shortcode parameter include_any="yes". The end result is that the visitor sees an extra row or tile in the calendar next to events and follows the link defined on the post itself.

If any part of that chain is missing, nothing will appear. A post may be published but not included in Events. The metabox may be filled out, but the display dates may already have passed. The post settings may be correct, but the calendar page may use a shortcode without include_any="yes". Or the item may render, but look wrong because of a CSS conflict between the theme and EventON settings. The guide below is structured around that exact chain because it is the fastest way to find problems.

How This Differs from a Regular EventON Event

A regular EventON event is created in the Events menu and gets the full event set: date and time, advanced time settings, location, organizer, EventTop, EventCard, custom interaction, image, and other fields. Include Anything works more simply: it takes existing WordPress content and gives it a calendar display window. That is useful for promoting content pages, but it does not replace an event when visitors need to see the venue, organizer, recurring schedule, status, ticketing flow, or a detailed EventCard structure.

Here is the practical rule: if the content is an event in itself, create an EventON event. If the content is a page, product, course, article, or announcement that should appear in the calendar during a specific period, use EventON Include Anything. The addon works best as a bridge between content and the calendar, not as a tool for creating new event entities.

Who EventON Include Anything Is For and When Another Approach Makes More Sense

This addon is especially useful for sites where the calendar is already a familiar entry point for the audience. If visitors open the calendar to understand what is happening in the coming weeks, it makes sense to place not only events there, but also related content such as course enrollment, a new program, a product of the week, a registration page, a post with participation details, or an event recap. In that kind of workflow, Include Anything saves editors time and keeps the visitor journey unified.

For a content team, the value of the addon is that the publication remains a regular WordPress post. It can still be edited in the usual editor, built with blocks, optimized with SEO fields, enriched with images and internal links, and kept inside the theme templates already in use. The calendar becomes a storefront rather than the place where all information lives. A visitor clicks the item and lands on a full content page where you can place details, a form, a video, a product block, or a long-form description.

For a marketer, the key controls are color, custom title, and link. Color helps distinguish a type of announcement in the calendar, title and subtitle make the message more precise, and a custom link can send visitors not only to the post permalink, but to the exact landing page you want. The tracking code field in the metabox can be useful when you need to measure user behavior through third-party analytics tools, but it should be used carefully and in line with the site's policies.

Good-Fit Use Cases

• An education site shows course pages in an enrollment calendar so visitors can see the start date and click through to the course program.
• A WordPress store adds products or promo pages to a seasonal campaign calendar without creating separate events for every product page.
• An editorial site surfaces important posts, special projects, or announcements in the calendar when the content has a meaningful relevance window.
• A community site displays meetup posts, reports, registration pages, and announcements next to events so the calendar acts as a single navigation layer.
• An event organizer adds a page with detailed package information, sponsor details, a schedule overview, or participant instructions instead of creating a separate event.

When the Addon May Not Be the Right Fit

If you need posts to be filtered like events by EventON event type, or to have location, organizer, recurring behavior, and a full EventCard structure, Include Anything will not solve that. In that case, it is better to create standard EventON events or consider another solution where the content is designed as an event from the start.

You should also avoid relying on the addon for mission-critical registrations if the visitor needs to go through a precise event form, ticketing flow, payment step, or attendance tracking system. Include Anything can send the user to the right page, but the registration business logic itself should live in the tool built for that purpose: EventON Event Tickets, WooCommerce, a registration form, or another dedicated module.

The addon is also not a substitute for editorial discipline. If you start pushing everything into the calendar, it quickly stops being a calendar and turns into a feed of random links. Only surface content that has a clear time-based purpose and a concrete benefit for the visitor.

What to Check Before Installing and Enabling the Addon

Before installing EventON Include Anything, make sure the base EventON plugin is already installed, activated, and correctly displaying regular events on a site page. The official addon page lists EventON as a requirement, and the general EventON addons documentation makes it clear that these extensions do not work on their own. So first confirm that the standard calendar works, and only then add Include Anything.

The second check is versions and updates. There is no point hard-coding specific version numbers in this article because they change quickly, but in your source review you should check the product page, changelog, and latest version information. In practice, the rule is simple: base EventON and Include Anything need to come from a compatible set, and the site itself should meet EventON and WordPress system requirements. If the calendar is already unstable, adding another addon will only make troubleshooting harder.

Check the Calendar Page

Open the page where the EventON calendar is already embedded. Make sure the shortcode is actually rendering events, month switching works, the styling is intact, and clicking an event behaves as expected. EventON relies heavily on shortcode attributes: the calendar can show a single month, a list, an extended list, filters, custom click behavior, and other variants. If there is already a problem at this stage, fix it first. Otherwise, it will be difficult to tell whether Include Anything is actually responsible.

Check where the shortcode lives. It may be inserted into a regular page, a block, the classic editor, a widget, or through the EventON Shortcode Generator. For Include Anything, the important part is that you can edit the shortcode or enable the corresponding option in the generator. If the calendar page is powered by a page builder or a custom template, identify in advance where that shortcode is stored.

Check the Post Types

Make a list of the post types you want to display. On a standard site, that may be Posts and Pages. On an education site, it may be courses if the LMS plugin registers its own post type. In a store, it may be products if you use WooCommerce. On a portal, it may be announcements, job listings, projects, catalog items, or some other custom post type.

Then evaluate each content type with two questions. First: does the content have a relevance window that makes sense to display in a calendar? Second: where should the user land after clicking it? If the answer to the second question is the single post page or a separate landing page, Include Anything is a good fit. If the answer is an EventCard with location, organizer, and event categories, a full event is the better option.

Check the Theme, Cache, and Editor Roles

Official EventON materials about EventCard, CSS, and display issues show that some problems are not caused by the event itself, but by the theme, cache, display settings, and saving EventON settings. So before rollout, it is helpful to prepare a test calendar page, disable aggressive minification during diagnostics, check the result in a private browser window, and make sure the editor has permission to edit the target post type.

If your site uses complex access roles, do not assume every editor will see the Include Anything metabox. Test that with the actual role that will manage the content. If the metabox is visible only to an administrator, set up the publishing workflow so that the final inclusion in the calendar is handled by the appropriate user with sufficient permissions.

Installation and Initial Verification in WordPress

EventON Include Anything is installed like a regular WordPress plugin through Plugins and a ZIP upload. The official EventON addon installation guide describes the usual path: Plugins - Add New - Upload Plugin, select the ZIP file, click Install Now, and activate it. For macOS, the documentation also notes that the browser must not automatically unzip the archive after download, or WordPress will not receive the ZIP file it expects.

Do not start configuration on the live page if the site has active traffic. It is better to create a test post and a separate test calendar page, or use a non-public draft. That lets you validate the workflow without exposing extra content to visitors. The first check should prove not that the item looks polished, but that the chain itself works: the post is included, the shortcode requests it, the calendar displays it, and the click goes where it should.

Basic Installation Order

1. Make sure the main EventON plugin is installed, active, and already displaying regular events.
2. Back up the site, or at least the database and plugin directory, if you are rolling this out on a production project.
3. Go to Plugins - Add New - Upload Plugin and upload the addon ZIP file.
4. Click Install Now, then activate the plugin.
5. Open a standard WordPress post and confirm that the Include in Events metabox is now available.
6. Create or open a page with an EventON shortcode and prepare to add include_any="yes".

What to Check Right After Activation

Open the editor for a post, page, or other post type you plan to use. Find the Include Anything metabox. If it does not appear, check that the addon is active, that your user role has permission, that you are editing the correct post type, and that there are no admin errors. There is no need to jump straight to complex explanations. Very often the issue is simply that the user is editing the wrong post type or that the calendar page is not yet configured to request included posts.

Then build a minimal test: a short post with a clear title, a display period, and a distinct color. Do not use a real campaign as your first test. The test post should be easy to recognize inside the calendar so you can distinguish it from regular events and quickly remove or disable it after validation.

The Include in Events Metabox: Settings That Determine the Visible Outcome

The main working area of EventON Include Anything is not a general settings page, but the post you are editing. The official instructions show the path through WP Dashboard - Posts - Add New, then the Include in Events metabox. In a real project, this may apply not only to Posts, but also to another post type if it is editable and fits your site workflow.

First you enable the toggle that makes the post visible to the calendar. Then you define the date range, the window during which the post should appear. The documentation emphasizes that the post will be visible in the calendar only during that specified period, after which the calendar returns to its normal structure. This is not just a decorative date. It is the main filter that determines whether the item appears in the calendar at all.

Display Window

The start and end dates should match the actual purpose of the content. For a course, this might be the enrollment period or the window before the first class. For a product, it might be the duration of a promotion. For a campaign page, it might be the active application period. For an article, it might be the period during which the post is genuinely relevant inside the calendar. If you set the window too long, the calendar fills up with stale content. If you set it too short, visitors will miss the content when it matters.

After saving, always check the calendar on the month that falls within the date range. If the calendar opens by default on a different month, the item may be configured correctly but simply not visible to you. In that case, switch months or temporarily use a test period that lands in the current calendar view.

Title and Subtitle

The title field lets you set the text shown in the calendar grid or row instead of the default post title. This matters because the title of an article or product does not always work well in calendar context. For example, a post might be called "Complete Beginner Course Program," while the calendar label works better as "Beginner Course Enrollment Opens." That title is shorter, clearer, and immediately ties the content to a specific date.

The subtitle gives you a second layer of meaning: format, audience, a short clarification, seat availability, or context. Do not turn the subtitle into a long description. In the calendar, it should support quick scanning, not replace the destination page. A good title and subtitle pair answers two questions: what this is, and why it is worth opening now.

Color and HEX Code

Color is used to visually distinguish the item in the calendar. The Include Anything changelog mentions the addition of a HEX color code field, and the official product page refers to custom colors. That gives you a simple way to differentiate included content types: one color for courses, another for products, a third for announcements. But color should be part of a system, not a random decoration.

Choose three to five working colors and document them in your editorial guidelines. For example, educational content could be blue, products green, and important announcements amber. Check contrast on the public site, especially if your theme overrides EventON styles. Color should help visitors identify the item, not make the title harder to read.

Link and Open in a New Window

By default, a calendar item may point to the post permalink, but the metabox also lets you define a custom link. This is useful when the calendar item should lead not to the post itself, but to a registration form, product page, landing page, member area, or a page with UTM parameters. If the link goes to an external resource, a separate campaign, or a document, you can enable opening it in a new window. For internal destinations, the current window is usually better so the user stays within the site context.

Before publishing, test the link manually. Open the calendar as a visitor, click the included item, and make sure the destination matches the goal. If you use a custom link, do not rely on the post title alone: the title may still be correct while the link is outdated. This happens especially often when old content is copied forward.

Tracking Code

The official instructions describe the optional tracking code as a field for analytics, including user behavior data. In practice, you should use this field only when you have a clear analytics purpose and your site's security rules allow that code. Do not paste in random scripts or pass personal data without both legal and technical review.

If a marketer asks you to add tracking code, clarify three things: which tool is collecting the data, where the metric should appear, and how the code can be disabled if something goes wrong. Test it on a separate post first, then check the browser console and the analytics platform. If the site uses a strict security policy or optimization plugins, the tracking code may require additional setup.

Shortcode and Shortcode Generator: Why the Post Will Not Appear Without include_any

Filling out the metabox does not guarantee that the post will appear in the calendar. The official documentation states directly that to display selected posts, you must modify the shortcode and pass the include_any="yes" parameter. This is a separate step, and it is exactly the one people tend to forget when the editor checks the post but never touches the calendar page.

A basic EventON calendar may be rendered with [add_eventon]. Once Include Anything is in use, the shortcode needs an extra attribute. The simplest example looks like this:

[add_eventon include_any="yes"]

If your calendar already uses other parameters, add include_any="yes" to the existing shortcode without removing the settings you need. For example, if you already have a separate calendar ID or a custom month count, keep those in place:

[add_eventon cal_id="main_program" number_of_months="2" include_any="yes"]

When It Makes Sense to Use the Shortcode Generator

The EventON Shortcode Generator helps you assemble a shortcode visually. The documentation describes it as an interactive tool that updates the shortcode based on the options you select and expands based on the active addons. If you do not want to edit attributes manually, open the generator and look for the Include Anything setting there. That reduces the risk of typos and helps you see which other parameters are already affecting the calendar.

For complex calendars, the generator is also useful as an audit tool. It shows that the shortcode is not just a random string of text, but a set of parameters controlling calendar behavior. If included posts are not appearing, compare the shortcode on the live page with a minimal test shortcode. Sometimes the issue is not Include Anything at all, but filters, date ranges, hidden empty months, a custom event list, or another attribute.

Multiple Calendars on One Site

If your site has multiple calendars, do not enable Include Anything everywhere automatically. One calendar might be an event schedule, another a publication calendar, and a third an internal page for editors. Add the include_any="yes" parameter only where regular posts are actually supposed to appear next to events.

When you have multiple calendars, use clear naming for pages and tests. For example, a "main events calendar" might show only events, while a "programs and announcements calendar" shows events plus selected posts. That is easier to explain to editors and much easier to troubleshoot. If every calendar mixes everything together, issues become harder to spot.

How to Build a Content Model: Post Types, Dates, Colors, and Links

The most common weakness in an Include Anything rollout is that everything works technically, but the calendar becomes noisy. To avoid that, decide in advance which materials are allowed into the calendar and how they should look. The addon gives you inclusion tools, but it does not replace an editorial model.

Start with a content planning table. It should define the post type, display purpose, time window, color, calendar wording, link, and the condition for removing or disabling the item. This is not bureaucracy. It is protection against calendar chaos. On a site with multiple editors, a table like that saves more time than any technical instruction.

Working model for different content types in EventON Include Anything

Content type	When to display it	What to put in the title/subtitle	Where the link should go	How to verify it
Course page	Enrollment period or the start of the next cohort.	A short course name and participation format.	To the course program or registration form.	A click from the calendar opens a page with current registration details.
WooCommerce product	Promotion period, launch window, or themed campaign.	The offer name and a short reason to open it.	To the product page or promo landing page.	Price and availability are validated on the product page, not in the calendar.
Blog post	The relevance window for the content, such as the week of an event.	The topic of the post and its connection to the calendar date.	To the post itself.	The calendar shows a clear title, and the article delivers what the label suggests.
Campaign page	The active period for applications, donations, or registrations.	The campaign name and the visitor action.	To the campaign landing page.	The form, button, or main call to action works after the click.

Use Colors as Navigation, Not Decoration

EventON Include Anything lets you assign a color to an included post. Use that as part of the calendar language. If regular events already follow a color system, included posts should complement it rather than break it. For example, events might be colored by event type, while included posts are colored by content type. In that setup, the visitor can immediately tell the difference between an event and a page or content item.

Do not give every post its own unique color. That may look good in a single example, but it works poorly in a real calendar. A limited palette is better. Test contrast across different backgrounds and document what each color means. If the theme or EventON styles override colors, validate the final look on the public site, not just in the admin panel.

Links and Visitor Expectations

Visitors expect a click on a calendar item to continue the meaning they saw in the title and subtitle. If the calendar says "Workshop Registration," the link should take them to the registration page or form, not to a general category archive. If it says "New Course Enrollment Open," the user should land on the course page with current information. Include Anything gives you a custom link, but the editor is still responsible for making sure the wording and the destination match.

Use opening in a new window intentionally for external links. It makes sense for partner pages, external registration forms, and documents. For internal pages, keeping normal navigation is usually better so analytics, breadcrumbs, back navigation, and the site structure work as expected.

Practical Example: A Training Center Calendar with Courses and Regular Events

Imagine a WordPress site for a training center. EventON already contains regular events such as open classes, webinars, and meetups. Separately, the site has course pages that are not events: they include a full syllabus, instructors, testimonials, an application form, and an SEO-friendly structure. The goal is to show course enrollment in the calendar so a visitor sees it next to webinars and can click through to the course page.

The goal here is not simply to "add a post." We want to keep the course page as the main source of information while making it visible in the calendar path. That avoids duplication: the editor does not create a separate event with the same content, but instead adds a calendar visibility window to an existing page.

Goal

Build a calendar where regular EventON events display webinars and meetups, while a selected course page appears as a separate calendar item during the enrollment period. When a visitor clicks it, they should land on the course page or the signup form if that form lives separately.

Preparation

• The main EventON plugin is installed, active, and already showing regular events.
• EventON Include Anything is installed and activated.
• The course page is published or ready to be published.
• The course page has a clear goal: application, reading the syllabus, starting payment, or contacting a program advisor.
• The calendar page is editable, and the shortcode can be updated.

Setup Steps

1. Open the course page in the WordPress admin panel.
2. Find the Include in Events metabox and enable calendar display.
3. Set the date range to the enrollment period. Do not leave it open-ended if the course has a specific launch window.
4. In the title field, enter a short calendar headline such as "Course Enrollment Opens."
5. Use the subtitle to add a clarification: format, level, duration, or another short detail.
6. Choose the color that represents educational programs in your editorial palette.
7. Leave the link pointing to the course page permalink or set a custom link to the signup form.
8. Save the page.
9. Open the calendar page and add the include_any="yes" attribute to the shortcode.
10. Save the calendar page, clear the cache, and verify the result as a regular site visitor.

Verification

Open the calendar for a period that falls within the date range. Find the course item and compare it with the regular events. It should appear alongside them, display the expected title and subtitle, use the correct color, and behave properly on click. If the link goes to the course page, confirm that the page contains a current form, contact details, or a clear next step.

Quick post-publish check: open the calendar in a private window, switch months, click the included post, go back, and make sure regular EventON events have not disappeared or become mixed with irrelevant content.

Common Pitfall

If the training center wants to filter the course page by EventON categories, location, or organizer, Include Anything is not the right tool for that part of the job. A support thread for the product shows that adding location, organizer, and category to regular posts through Include Anything is not supported as a full event model. If you need a filterable schedule, create an EventON event and use the course page as a related link or a detailed description.

Verifying the Result: How to Tell Whether the Setup Actually Worked

Validation for EventON Include Anything should go from the public outcome back to the cause, not from the admin panel to assumed success. An editor can fill out every field correctly and the user may still not see the item because of the shortcode, date range, cache, filters, conflicting styles, or a wrong link. So after setup, use a short outcome-based checklist.

What Should Be Visible in the Calendar

• The included post appears in the correct period and does not appear outside it.
• The text in the calendar matches the title and subtitle from the metabox, if those fields are set.
• The color helps distinguish the content type and does not hurt readability.
• A click goes to the post permalink or the custom link selected in the settings.
• Regular EventON events continue to display and behave as before.
• There are no visible CSS issues on the page: missing text, strange spacing, overlaps, or invisible links.

Check the Shortcode

If the included post is not visible, open the calendar page and inspect the shortcode. It must include include_any="yes". If the shortcode is complex, temporarily create a separate test page with the minimal version [add_eventon include_any="yes"]. If the post appears there, the problem is in the extra parameters of the main shortcode or in the page context.

If the shortcode was inserted through the Shortcode Generator, make sure the corresponding option is actually enabled and saved. In EventON, settings may be distributed across the shortcode, EventON settings, and specific event card designers. Do not change everything at once. First confirm one part of the chain.

Check the Date Range

The date range in Include Anything controls visibility. If the calendar is open to a month outside that display window, the item should not appear. That is normal behavior. To rule out a mistake, set a test window that definitely falls within the current calendar view, save the post, clear the cache, and reload the page.

If the site hides past events or uses special list parameters, factor that into your test. Include Anything inserts the post into the EventON calendar environment, so the result can depend on how the calendar queries and sorts items.

Check the Click and Analytics

Once the item appears, always test the click. That is a separate success criterion. If the visitor sees the post but lands on an outdated page, the setup is not complete. If the custom link opens an external site, confirm whether a new window is actually needed. If tracking code is used, verify that it does not generate console errors or conflict with caching or optimization rules.

Compatibility with EventTop, EventCard, Filters, and EventON Styles

EventON includes many design layers and settings: EventTop Designer, EventCard Designer, shortcode attributes, styles, and additional addons. Include Anything exists within that ecosystem, but it does not automatically inherit every property of a regular event. That is the main source of incorrect expectations.

EventTop is the upper part of an event in the calendar list or tile. EventCard is the expandable or detailed area showing event data. EventON documentation explains that EventCard Designer controls field visibility on the public site, and addon fields appear there after activation and configuration. But for Include Anything, you need to separate event fields from an included post. If a regular post points to a single post page, do not expect it to suddenly gain organizer, location, or every EventCard field.

EventCard Designer Does Not Solve Every Include Anything Need

If information from a regular event is missing in the calendar, EventCard Designer may indeed be the right place to check: the field may need to be added, positioned, and saved. But if the problem is that an included post does not have a location or organizer, that is not an EventCard Designer problem. That is simply the boundary of Include Anything. For those kinds of data, you need an EventON event entity or a different content architecture.

The practical takeaway is simple: use EventCard Designer for standard EventON events and for addons that add data to events. For included posts, manage only the settings actually available in the Include Anything metabox: title, subtitle, color, link, new window, tracking code, and date range.

Filters and Categories

If your calendar relies heavily on EventON event types, filters, and categories, included posts may not behave like regular events. A support response about Include Anything states that requests for selecting Location, Organiser, and Category for regular posts are not supported in the current addon behavior. So do not build navigation as if an included post will automatically participate in every event filter.

If you need to show a course as a filterable event, create an EventON event such as "Course Launch" and add a link to the course page. If you only need to highlight the course page inside the general calendar, use Include Anything. Those are two different architectures, and it is better not to blur them.

Styles, Theme, and Spacing

In a support thread about hidden text in Include Anything, a user shared a shortcode with include_any="yes", and the support response included checking whether the title and other fields were filled in, along with a CSS adjustment for description spacing. That is a useful example: sometimes the addon is working, but the appearance breaks because of the interaction between a featured image, list view, theme, and calendar styles.

EventON officially documents the CSS override workflow through browser inspection and the EventON - Styles field. That does not mean you should start writing CSS blindly. First confirm that the item exists in the HTML and that the problem is visual. Then use the browser inspector, identify the exact selector, and apply the smallest possible override.

Editorial Process: How to Keep the Calendar from Becoming a Link Dump

EventON Include Anything makes it technically easy to include a post, but that simplicity is exactly what creates risk. If every editor can add any publication to the calendar without rules, the calendar loses its primary purpose: helping visitors orient themselves in time. That is why it is worth documenting the editorial workflow before rolling this out broadly. It does not need to be complex, but it should answer basic questions: what content is allowed, who sets the date range, who chooses the color, who checks the link, and who removes the item when it is no longer relevant.

For a small site, a short policy in the shared editorial instructions is enough. On a site with several departments, it is better to create a simple content matrix by content type. For example, the education team includes course pages, marketing includes campaign pages, the store includes only special products or collections, and regular news does not go into the calendar unless it is tied to a specific time window. That preserves the meaning of the EventON calendar and avoids conflicts with standard events.

Criteria for Letting Content into the Calendar

Before including a post, ask four questions. First: does the content have a date or period that matters to the visitor? Second: does the calendar help the visitor choose the right moment to act? Third: would it make more sense to create a regular EventON event? Fourth: does the destination page already contain a clear next step? If at least two answers are weak, the content is better left in the regular site navigation rather than added to the calendar.

A good example is a page called "Enrollment Open for an Intensive Web Design Course." It has an enrollment period, a cohort start date, a visitor action, and a clear calendar context. A weak example is a permanent "About Us" page. It may be important, but the calendar adds no time-based meaning to it. If you place it in EventON, visitors will simply wonder why a general site page is sitting next to webinars and meetups.

Main inclusion rule: a calendar item should answer the question "why does this content need to be seen right now?" If you cannot explain that in one sentence, Include Anything is probably the wrong tool for it.

Team Roles

Even if one administrator can technically set everything up alone, it is still useful to separate responsibility. The content author is responsible for the page content and the accuracy of the link. The calendar editor is responsible for the date range, title, subtitle, and color. The technical specialist is responsible for the shortcode, cache, styles, and conflict checks. On a small site, that may all be one person, but it is still worth thinking in roles. Otherwise, it is easy to update the page text and forget to verify the calendar.

For recurring campaigns, create a reusable check template. It can be as simple as six lines: content published, metabox enabled, date range set, title/subtitle filled in, custom link checked, item found in the calendar. That template is more useful than a long technical guide because editors need a repeatable workflow.

How to Name Included Items

The post title and the calendar item title often should not be the same. A page may need an SEO-friendly title with full detail, while the calendar needs a short action-focused label. For example, "Beginner WordPress Course Program: Modules, Practice, and Learning Format" is better shortened in the calendar to "WordPress Course Starts Soon." The subtitle can then clarify it further: "New cohort enrollment, online format."

Do not treat the title like an ad banner. Words such as "best," "unique," or "urgent" quickly reduce trust in the calendar. It is better to be specific: "Workshop Registration," "Open House Day," "Spring Program Launch," or "Enrollment Promo Period." The visitor should understand the action before clicking, and read the details on the destination page.

When to Disable a Post

The date range handles the automatic part of the job, but editorial oversight is still necessary. If a course is canceled, a product sells out, a campaign closes, or the link is no longer valid, disable the post before the display window ends. If the content still has value as an archive, let it remain on the site, but do not assume it should stay in the calendar. One of the advantages of Include Anything is that calendar visibility is separate from the existence of the page.

After a campaign ends, confirm that the item disappears from the calendar and that the page itself does not create false expectations. If users can no longer enroll in the course page, add a clear status or point them to the next cohort. The calendar should never send users into a dead end.

Use Cases for Custom Post Types: Courses, Products, Announcements, and Campaign Pages

The official Include Anything instructions explicitly note that popular plugins register their own custom post types and use WooCommerce products as an example. That opens up a strong use case: the calendar can show not only standard posts and pages, but also entities that already exist elsewhere on the site. But those should not be included mechanically. Each one has to be evaluated based on what it means.

A custom post type often has its own internal behavior: a product has price, availability, and variations; a course has a syllabus and instructors; a job listing has conditions and an application form; a project has a gallery and milestones; a directory item has attributes. Include Anything does not transfer that behavior into the calendar. It simply creates a calendar entry point. That is why the public page for the custom post type must be ready to receive visitors after the click.

WooCommerce Products: When a Product Belongs in the Calendar

A product only makes sense in Include Anything when there is a calendar reason for it: a sales launch, a limited promotion window, a new collection release, an availability date, a sale tied to an event, or a seasonal campaign. If you just dump all products into the calendar, you end up with a bad catalog and a bad calendar at the same time.

For products, the link is especially important. In most cases, it should point to the product page, where WooCommerce already displays the price, availability, variations, shipping, and buy button. If the product is part of a campaign, a custom link can point to a promo landing page with campaign details, a collection, and related materials. But the calendar should not promise something the product page does not deliver. If the title says "Product Launch Starts Today," the product page should confirm availability or clearly explain when it begins.

It is also a good idea to keep product colors separate from the colors used for regular events. For example, if EventON events are colored by category, products can use a separate campaign palette. That helps visitors quickly distinguish an event from a commerce-related item. This matters especially on sites where the calendar is used for education, events, and commercial launches at the same time.

Courses and Educational Programs

For educational projects, Include Anything is often a better fit than creating a duplicate event. A course page usually contains a lot of evergreen information: syllabus, who it is for, learning outcomes, instructors, FAQs, and an application form. Creating an event with the same content just for calendar visibility is inconvenient and risky, because the two versions will quickly drift apart. The addon lets you keep the course page as the source of truth and display it in the calendar during the enrollment period.

When setting up a course, it is important to separate the display window from the class schedule. The date range in Include Anything controls when the page appears in the calendar, not the full schedule of the course itself. If a course includes several classes, recurring sessions, or a day-by-day timetable, that is a job for standard EventON events or for a schedule inside the course page. Include Anything works well for "enrollment is open now" or "the program starts soon," but it is not a replacement for a detailed schedule.

Announcements and Editorial Campaigns

On nonprofit, club, and editorial sites, the calendar often acts as an activity hub. Include Anything makes it possible to place important content there: participation rules, a contest page, a report with registration, or a partner program announcement. Those items are not always events, but they do have a relevance period.

Here, title and subtitle matter especially. Visitors should immediately understand what they are opening: not "News Post #43," but "Contest Applications Open"; not "Program Update," but "New Meetup Schedule"; not "Partner Content," but "Partner Registration Now Open." If the editor leaves the original article title unchanged, the calendar becomes harder to understand.

Campaign Pages and Landing Pages

A campaign page may be built with a page builder, Gutenberg, a theme template, or a regular WordPress page. Include Anything can display it in the calendar if the metabox is available for pages. For these pages, a custom link is often unnecessary because the permalink already points to the correct landing page. But if the campaign has multiple versions, a language-specific page, or a separate form, a custom link gives you more precise traffic routing.

Make sure the landing page does not depend on authentication unless that is intentional. If the calendar is public but the page is accessible only to logged-in users, that should be a conscious product decision. Otherwise, the user sees the calendar item, clicks it, and lands on a closed page with no explanation.

Using It Alongside Other EventON Features

Include Anything rarely exists in isolation. On a real site, EventON may already be using EventTop Designer, EventCard Designer, filters, different shortcode layouts, Event Lists, FullCal, Event Tickets, or other addons. It helps to understand where the responsibility of each tool begins and ends so you do not expect Include Anything to solve problems that belong to a different module.

The basic model is straightforward: Include Anything is responsible for bringing a regular post into the calendar and giving it lightweight calendar presentation. EventON core is responsible for events and the overall calendar structure. The shortcode controls which items are displayed and how. EventTop and EventCard control event design and event data. Other addons handle their own specialized use cases.

Include Anything Plus Event Lists

If the calendar is rendered not with the classic [add_eventon] shortcode, but with an advanced list shortcode, it becomes especially important to verify parameter support and interaction. A support thread about hidden text showed an example of a complex shortcode using Event Lists together with include_any="yes". That does not mean every possible combination of attributes will behave perfectly. It means your troubleshooting should take both Include Anything and the selected calendar view into account.

For list-based views, check three things: whether the item appears in the correct position, whether text is hidden by the image or spacing, and whether the click works properly. If the list view uses a featured image, a tile-like layout, or a complex EventTop style, the included post may require a separate CSS review. Keep that review targeted rather than redesigning the whole calendar.

Include Anything Plus EventTop Designer

EventTop Designer controls which data is shown in the top area of a regular event. For an included post, you mainly control title, subtitle, color, and link through the Include Anything metabox. If regular events and included posts appear side by side, it is important to maintain visual balance: the included post should stand out clearly, but it should not look like a broken event missing data.

In some calendar views, a visitor may interpret an included post as a normal event. To reduce that risk, use the subtitle as an honest clarification: "Course Page," "Feature of the Week," "Promo Page," or "Registration Open." That works better than trying to hide the difference. Clear labeling helps users understand why clicking takes them to a post page rather than an EventCard with place and time details.

Include Anything Plus EventCard Designer

If your page contains regular events with a rich EventCard, do not overload included posts with the same expectations. You can configure EventCard for events so location, organizer, FAQ, or tickets are visible, but included posts still operate by their own rules. If an editor says "the field is not showing," the first question should be what entity they mean: an event or a regular post included in the calendar.

That distinction is especially important in support work. When someone says "details are missing in the calendar," clarify whether it is an EventON event or an included post. For an event, check EventCard Designer. For an included post, check the metabox, shortcode, link, and the expected click behavior.

Include Anything Plus EventON Custom Fields

EventON lets you add custom meta fields to events and display them through EventCard. That is not the same thing as Include Anything. If you need to add an extra data line to an event, use custom fields and EventCard Designer. If you need to display an existing page in the calendar, use Include Anything.

Sometimes the best result comes from combining both approaches. For example, you can create an EventON event called "Open Class" with location and time, and also include the course page through Include Anything for the full enrollment period. That way, the calendar shows both the specific event and the course program page. But the title and subtitle must clearly distinguish them, or visitors will see two similar entries and not understand the difference.

Pre-Publication Checklist for the Live Site

Before adding Include Anything to a production calendar, treat the validation like a small release. That is not because the addon itself is unusually complex, but because the calendar is public-facing and directly affects navigation. An error in the title, date, or link may not break the site technically, but it can still send users to the wrong place.

It is helpful to split the check into admin settings, public output, click behavior, and rollback. That order makes it easier to understand exactly what needs to be fixed. If you check everything in a random order, it becomes easy to confuse caching, shortcode issues, and post settings.

Admin Panel

• The Include in Events metabox is enabled only on the intended content item.
• The date range matches the real relevance period and was not accidentally copied from an old post.
• The title is short and clear in calendar context.
• The subtitle clarifies the format or action instead of repeating the title.
• The color comes from the approved palette.
• The link points to the correct page, and opening in a new window is enabled only when needed.
• Tracking code is added only when there is a confirmed analytics need.

Public View

Open the calendar as a visitor. It is better to use a private window or a different browser so you are not relying on the state of the admin session. Navigate to the month or period where the item should appear. Make sure the item does not look like an accidental error: the text is readable, the color works against the background, neighboring events are not pushed out of place, and the visual difference between a regular event and an included post is not misleading.

If the calendar is used on mobile devices, check the responsive view as well. Even if the product is not mobile-first, visitors often open calendars on phones. This is where short titles and subtitles matter most. Long text can get cut off or wrap in awkward ways.

Click Behavior

The click is the primary user outcome. Click the included post and verify the URL, the target page heading, the form, or the button. If the custom link points to a form, submit a test entry only if that is safe within your process. If the page requires authentication, make sure that is intentional. If opening in a new window is enabled, make sure it does not create an unnecessary trail of tabs.

For analytics, check only the signal you actually need. There is no value in stacking multiple tracking tools "just in case." The more third-party behavior you attach to a calendar item, the harder it becomes to identify the real cause when something breaks.

Rollback

Rolling back Include Anything is usually simple: turn off the metabox toggle or remove include_any="yes" from the shortcode. But those actions operate at different scales. Disabling the toggle removes one specific post. Removing the shortcode parameter removes all included posts from that calendar. So when the issue is local, do not disable the parameter for the entire page if the real fix is just to correct one entry.

If the problem is caused by CSS, roll back the CSS. If the problem is caused by the link, correct the link. If the problem is caused by the wrong architecture, convert the content into a normal EventON event. That targeted approach keeps the calendar stable and avoids breaking content that is already working correctly.

How to Explain the Addon to Editors and Clients

A technically accurate explanation can still be too complicated to be useful in rollout. Editors do not need to know every internal detail about post types, shortcode attributes, and EventCard Designer. They need to understand one thing: Include Anything adds a page or post to the calendar for a selected period and lets them assign a short calendar title, a color, and a link. Everything else is usage policy.

For clients, it helps to explain the boundary with a simple example. "If it is an event, we create an event. If it is a page that needs to appear in the calendar because it matters during this period, we include it through Include Anything." That single sentence prevents most incorrect feature requests. It also helps align the budget, because you do not end up building custom workarounds for something the product is not supposed to do when the real solution is choosing the right content type.

Short Instructions for an Editor

1. Open the content item that needs to appear in the calendar.
2. Enable Include in Events.
3. Set the period when the item should be visible.
4. Write a short calendar title and a clear subtitle.
5. Choose a color from the editorial palette.
6. Check the link and save the content.
7. Open the calendar as a visitor and make sure the item is visible and clickable.

These steps do not replace the technical guide, but they work well as an everyday reminder. If an editor has to remember shortcode details every time, the process is set up incorrectly. The shortcode should be configured once by an administrator or developer, while the editor works with the metabox and verifies the public outcome.

How to Explain the Limitation Without Starting a Technical Argument

When a client asks why an included post does not have a location or organizer, do not just say "the plugin cannot do that." It is better to explain the model: "This page remains a WordPress page. The calendar simply shows it during the right period and sends users to that page. If you need an event with a location, organizer, and filters, we create an EventON event instead." That framing moves the conversation away from "something is broken" and toward "we need the right tool for the job."

This is especially important on projects that have used EventON for a long time. People are used to the idea that a calendar means "events." Include Anything expands that into "calendar-relevant content." If that distinction is not explained, some users will expect different behavior. Clear titles and subtitles plus a careful color system help communicate that difference at the interface level.

Safe Enhancements and Careful Visual Adjustments

With Include Anything, it is usually best to avoid heavy PHP customization. Official EventON documentation offers examples of CSS overrides and separate hooks for adding custom EventCard data, but Include Anything does not require extending PHP behavior for most use cases. It is safer to work through the addon settings, shortcode, EventON Styles, and the content structure itself.

Below is a cautious custom CSS adjustment based on public EventON styling practice and a support example where an included post had spacing issues in list view. It does not modify WordPress core, EventON, or Include Anything. You should apply it only after confirming in the browser inspector that the selector matches your calendar.

CSS for a More Readable Included Post in List View

Goal: make the included post more compact and readable if the theme or featured image creates too much spacing in the calendar row. Where to add it: EventON - Styles or another standard custom CSS field already used on the site. Basis: the official EventON CSS override documentation and a support example using the .anypost selector.

#evcal_list .eventon_list_event.anypost a.sin_val.hasFtIMG .evcal_desc {
  padding-left: 20px;
}

#evcal_list .eventon_list_event.anypost .evcal_desc .evcal_desc2 {
  line-height: 1.35;
}

After adding the CSS, save the styles, clear the cache, and open the calendar in a private window. Check only the item you added the CSS for: title, subtitle, color, and click behavior. If the spacing gets worse or the selector starts affecting regular events, remove the snippet and save the settings again. The rollback should be just as simple as the change itself: delete the CSS, save, clear the cache.

When You Should Not Add Code

Do not add a PHP snippet that tries to turn an included post into an event with location, organizer, or recurring behavior. That contradicts the confirmed product boundary and can break future updates. Do not paste in arbitrary tracking scripts without approval. Do not edit plugin files directly, because updates will overwrite those changes and troubleshooting will become harder.

If the addon does not have the feature you need, the right move is to change the content architecture: create a regular EventON event, use a custom link to the correct page, add an EventON custom meta field to the event, or choose another calendar plugin. Code should be the last resort, not a workaround for choosing the wrong tool.

How to Choose Between an Included Post and a Full Event

The most important architectural decision when working with EventON Include Anything is not "how to include a post," but "should this thing really be a post at all?" A bad choice is not always obvious on day one. The content appears in the calendar and everything seems fine. Then a week later, an editor asks for a location, then a filter, then a status, then recurrence, then a ticket button. That is when it becomes clear that this should have been an EventON event, not an included post.

To avoid rework, use a simple decision map before setup. You do not need special tools. Just work through a few questions and answer honestly based on what information the visitor needs within the calendar flow.

Question 1: Does the Visitor Need an Event Date or a Content Relevance Window?

If you are dealing with a real event that has a start time, end time, location, participation format, and possibly registration, it should be an EventON event. If you are dealing with a page that only needs to be visible in the calendar during a certain window, it is a candidate for Include Anything. The difference is subtle, but practical. "Webinar at 3:00 PM" is an event. "Course registration open through Friday" is calendar-relevant content.

If the content sits somewhere between those two, decide based on what the visitor should do after clicking. If they should read the details and submit an application on the course page, an included post makes sense. If they should see the time, place, organizer, status, and be able to add it to their calendar, create an event.

Question 2: Are EventON Filters Required?

Filters are valuable when the calendar contains many events and visitors choose by topic, location, format, or event type. If an included post needs to participate in that kind of navigation as a full event, Include Anything may become the weak point. The support limitation around location, organizer, and categories shows that included posts should not be designed as peer events in a complex filtering system.

If filtering is essential, create an event and connect it to the content page. For example, an event called "Course Open House" can have a location, organizer, and event type, while the description or Learn More link points to the course page. That preserves the event model without losing the richer content page.

Question 3: Will the Content Repeat?

Recurring classes, regular meetups, weekly webinars, and event series are better modeled as events using the appropriate EventON recurrence features. Include Anything gives you a display window, but that is not the same thing as a recurring event. If an editor wants the same page to appear in the calendar every week as a separate date, stop and ask whether that creates a false model.

Sometimes a hybrid approach works. A course page can be included through Include Anything for the entire enrollment period, while individual class sessions are created as events. That way, visitors see both the campaign layer and the specific meetings. But the title and subtitle must clearly distinguish those entries. For example, "Course Enrollment Open" and "Open Class" should not look like the same thing.

Question 4: What Should Remain After the Period Ends?

For events, archival behavior is usually straightforward: the event has ended, but it can be hidden, marked as past, or retained in an archive. For included posts, everything depends on the page itself. A course page may remain as a permanent program description while its calendar visibility disappears. A product may stay in the catalog while the promotion ends. A post may continue to be useful even after its calendar reason has passed.

If the page should change meaning substantially after the period ends, prepare that update in advance. Include Anything does not control the content on the destination page. It only routes visitors there during the right window. That means post-campaign cleanup is part of the editorial workflow, not an addon setting.

Maintenance After EventON, Theme, and Cache Updates

EventON and its addons evolve, and the Include Anything changelog shows fixes to the color picker, metabox behavior, EventON compatibility, PHP compatibility, title handling, and saving meta values. That is normal WordPress plugin life: updates fix bugs and change implementation details. What matters for a site owner is not avoiding updates, but having a clear verification process after them.

Maintaining Include Anything comes down to four steps: update base EventON and the addon through the normal process, preserve settings if needed, validate a test post, and then validate real calendar items. There is no need to rewrite every shortcode or redo your CSS each time. But you should have one control scenario that tells you whether the chain still works.

Control Post for Regression Testing

Create an internal post or page that can safely be included in the calendar during testing. Fill in every core Include Anything field on it: toggle, date range, title, subtitle, color, and link. After updating EventON or Include Anything, enable it for a test period and open a test page with a minimal shortcode. If the control post appears, the basic mechanism is still working.

Then check the live calendar page. If there is a problem there, compare not the addon in general, but the exact parameters: list view, filters, Event Lists, EventTop style, cache, CSS. That saves time because you already know Include Anything itself is functioning.

What to Do After Updating the Addon

1. Back up the site before updating, especially on production.
2. Update base EventON and Include Anything in a compatible way, without manually mixing old and new plugin files unless there is a specific reason.
3. Open Plugins and confirm that both plugins are active.
4. Save EventON settings if you notice display or style issues after the update.
5. Clear the site cache and browser cache.
6. Check the control included post and one real content item.
7. Review only the CSS overrides that affect .anypost or the calendar list.

If titles disappear after the update or special characters display strangely, compare your behavior with the Include Anything changelog and the current version in use. The changelog includes a fix related to special characters being removed from the title field. That is not a reason to write new code, but it is a reason to confirm that the site is running the current addon files.

Cache and Minification

Cache plugins, a CDN, and minification can serve outdated HTML, old CSS, or old JavaScript. With Include Anything, the symptom is simple: the post is already configured in the admin panel, but the visitor still sees the old calendar output. That is why you should clear cache after changing the date range, shortcode, or CSS. If the site uses object cache, page cache, and a CDN at the same time, verify them in order.

Do not disable all optimization permanently. For diagnostics, you can temporarily turn off minification or exclude the calendar page, but the final solution should be targeted. If the issue is only in custom CSS, fix the selector. If it is stale HTML, configure cache purging after page updates. If it is a third-party tracking code issue, disable that code specifically.

How to Document the Setup for Future Editors

A few months after rollout, no one will remember why those specific colors were chosen, why the shortcode lives on that page, or why some items are events while others are included posts. That is why even lightweight internal documentation pays off quickly. It should be practical, not theoretical.

The best format is a short page in the project knowledge base. It should record where the main calendar lives, which shortcode is used, which post types are allowed for Include Anything, who owns the configuration, which colors are used, how to verify the result, and how to disable an item. If the site is handed off to a new editor or contractor, that page helps prevent accidental breakage.

What to Include in the Internal Instructions

• Purpose: Include Anything is used for calendar-relevant pages and posts, not for full event entities.
• Allowed post types: for example posts, pages, products, course pages, or campaign pages.
• Disallowed use cases: content without a relevance window, internal utility pages, archives, or gated posts without explanation.
• Palette: which HEX colors represent courses, products, campaigns, and announcements.
• Title/subtitle template: a short action-oriented title plus a format clarification.
• Link rule: where users should land and when to enable opening in a new window.
• Validation: private window, correct month, click test, destination page, cache check.
• Rollback: disable the toggle for one post, or remove include_any="yes" for the whole calendar only when there is a system-wide issue.

Example of a Mini Policy

You can use wording like this: "We add only published pages and posts to the calendar through Include Anything, and only when they have a limited relevance period. For items that need time, location, organizer, or filters, we create EventON events instead. After enabling a content item, the editor checks the calendar in a private window and performs a test click on the item. If the content is no longer relevant, we turn off Include in Events or shorten the date range."

That kind of instruction takes less than a minute to read but solves the core problem. It explains not only what to click, but why this path was chosen. That matters especially with EventON Include Anything because the setup itself is short, while most mistakes come from the wrong expectations.

Troubleshooting: The Post Does Not Appear, the Link Goes to the Wrong Place, or the Item Looks Broken

Problems with EventON Include Anything are easiest to diagnose as a chain: post - metabox - date - shortcode - calendar - click - style - cache. If you jump straight to CSS or reinstalling the plugin, you can waste time and still miss a forgotten include_any="yes" or an expired date range.

The Post Is Configured but Missing from the Calendar

Symptom: the Include in Events metabox is enabled on the post, but the item does not appear on the calendar page.

Possible causes: include_any="yes" was not added, the date range does not fall within the displayed month, the post is not published, the calendar page is cached, or the shortcode uses additional filters. Start with the smallest possible check. Create a test post with a current display window, add a simple shortcode to a separate test page, and verify the result without extra parameters.

Fix: add include_any="yes" to the live shortcode or enable the option through the Shortcode Generator, save the page, and clear the cache. If the item appears on the test page, add the other parameters back one by one and see which one changes the output.

The Item Appears in the Wrong Time Period

Symptom: the post is visible earlier or later than expected, or disappears too quickly.

A likely cause is an incorrect date range or the wrong expectation about the current calendar view. Include Anything shows the post during the defined window, while the calendar may be open to a different month, display multiple months, or hide some entries because of shortcode behavior.

Fix: check the dates in the metabox, then open the calendar to the exact period. For testing, use a short, obvious interval and make sure the behavior changes after saving. If the site uses caching, clear it after every date change.

The Click Goes to the Wrong Page

Symptom: the visitor clicks the calendar item but lands somewhere different from what the editor intended.

Possible causes: the custom link is outdated, the URL was copied from an older campaign, the post permalink changed, or the editor expected an EventCard instead of a single post page. Based on the product behavior, an included post usually leads to the post page or the custom link, not to a full event detail view.

Fix: open the Include in Events metabox and check the link field and new window setting. If you need full event behavior, create an EventON event and use the content page link as a supplemental action.

The Title, Subtitle, or Color Is Missing

Symptom: the item appears in the calendar, but the text is blank, hidden, cut off, or the color is not applied.

Possible causes: the fields were not filled out, the theme overrides EventON styles, the CSS is not specific enough, the cache is serving an old version, or the selected calendar view does not display some data the same way the standard list does. The Include Anything changelog includes fixes related to the color picker, metabox behavior, and special characters in the title field, so if behavior looks strange, make sure the addon is up to date.

Fix: explicitly fill in the title and subtitle, set a simple HEX color, save the post, and clear the cache. If the HTML element is present but not visible, inspect it and use a minimal CSS override through EventON Styles. If the problem happens only on an outdated addon version, update Include Anything through the normal process.

Expected Event Fields Did Not Appear on a Regular Post

Symptom: an editor wants to add location, organizer, event categories, or recurring settings to a regular post included through Include Anything.

Cause: this is outside the supported boundary of the product. A support response for Include Anything states that those data belong to standard events, while included posts are intended for showing posts in the calendar and sending visitors to the single post page.

Fix: rethink the architecture. If you need event fields and filters, create an EventON event. If you need a content page to be visible in the calendar, keep Include Anything and limit the setup to the metabox, link, and clear presentation.

The Calendar Looks Different After an Update or Style Change

Symptom: after updating EventON, the addon, the theme, or a cache plugin, included posts no longer look the way they did before.

Possible causes: EventON styles changed, the theme is overriding rules, the cache is serving stale CSS, or saved settings did not rebuild the style output. EventON FAQ guidance recommends saving settings after updates if the appearance or custom styles need to refresh.

Fix: save EventON settings, clear the site and browser cache, and check the page again. If the issue affects a specific Include Anything item, find the selector with the browser inspector and apply a targeted override that can be removed easily.

Limitations You Should Account for Early

Include Anything looks like a simple addon, but its limitations matter precisely because it sits between two different content models: WordPress content and EventON events. If you do not make that boundary explicit, editors will expect a regular post to behave like an event, and developers will waste time looking for settings that do not exist.

The first limitation is that an included post remains a regular post. It can appear in the calendar, but its source page, template, SEO fields, and content still belong to its own post type. That is a strength for content and a limitation for anyone expecting event fields. The second limitation is that output is controlled by the shortcode. The addon does not push posts into every calendar automatically. The third is that the visual outcome depends on the theme and EventON styles.

SEO and Indexing

Displaying a post in the calendar does not replace the SEO structure of the page itself. If a course, product, or announcement page needs to rank, treat it as a real content page: unique title, description, internal links, useful content, and a proper template. The calendar creates an additional path to the page, but it should not be the only place where users understand what the page is for.

Do not promise improved visibility just because of Include Anything. The real value is different: the calendar connects time and content, improves navigation, and may increase clicks to important pages. From an SEO perspective, it matters far more that the user lands on a useful page than on an empty post with one line of text.

Performance and Cache

Any calendar with a large number of entries can become heavier. Include Anything adds more records to the output, so do not turn the calendar into an archive of the entire site. If the page already includes regular events, included posts, images, filters, and complex interactions, test performance after rollout.

Cache usually helps the public site, but it makes troubleshooting harder. After changing the shortcode, metabox settings, color, or CSS, always clear the cache. If the changes are visible to an administrator but not to a visitor, cache should be the first thing you check.

Tracking Code Security

The tracking code field may look like a convenient marketing tool, but it requires discipline. Only insert code that is permitted by the site's policy and understood by the technical team. Do not use this field as a universal place for widgets, forms, or random third-party scripts. If you need to embed a complex form or interactive block, it is better to place it on the destination page than to try managing it from the calendar item.

After adding tracking code, check the browser console, your cookie or consent policy, and the calendar behavior. If an error appears, temporarily remove the code from the metabox and see whether the problem disappears. That is the fastest way to separate an analytics issue from a calendar issue.

How to Make the Decision Before Rollout

The decision to use EventON Include Anything should be based on three questions. First: do you already have a working EventON calendar? If not, choose the calendar system first. Second: do you need to display regular posts or custom post types inside the calendar stream? If yes, the addon fits the problem. Third: do those materials need full event fields, filters, location, and organizer? If yes, it is better to create EventON events or choose a different architecture.

For most content-driven use cases, Include Anything works well because it does not force you to duplicate content. A course page stays a course page, a product stays a product, and an article stays an article. The calendar simply gets an additional item during the right period. That is a clean model if editors understand its boundaries.

Before launching on a live site, test one pilot use case. Pick a lower-risk content item, include it in the calendar, add include_any="yes", verify the public output, and collect feedback. If visitors understand that this is not an event but a useful link tied to a calendar date, the pattern is safe to scale.

Questions About EventON Include Anything That Usually Come Up After Initial Setup

Can I display not only posts, but also pages or custom post types in the calendar?

The official materials refer to WordPress post types, including standard posts, pages, and custom post types registered by other plugins. In practical terms, that means you should check the desired post type in the admin panel and see whether the Include in Events metabox appears. If the post type is internal, technical, or not meant for public content, putting it in the calendar may not make sense.

Why does the post not appear in the calendar after I enable it?

The most common reason is that the calendar page is not requesting included posts. Check whether the shortcode contains include_any="yes". Then check the date range, publication status, cache, and any additional calendar filters. Do not start with reinstalling the plugin until this basic chain is confirmed.

Can I add location, organizer, and EventON categories to an included post?

A support response for the product states that Include Anything is meant to add posts to the calendar with a click-through to the single post page, not to turn posts into full events with location, organizer, and other event fields. If those data are required, create a standard EventON event instead.

Do I need to configure EventCard Designer for Include Anything?

EventCard Designer is used to control fields on regular events and some EventON addons. For Include Anything, the main settings are in the post metabox: enable/disable, date range, title, subtitle, color, link, new window, and tracking code. If the problem is that a regular event field is missing, EventCard Designer matters. If the problem is expecting event fields on a regular included post, EventCard Designer will not fix that.

Can I use Include Anything with WooCommerce products?

The official instructions mention WooCommerce products as an example of a custom post type registered by a popular plugin. That makes the use case valid in principle, but you still need to test it on your site: the product page, promotion period, link, store cache, and product availability all need to be correct. The calendar does not replace WooCommerce logic for stock, pricing, or checkout.

What if the item is visible, but the text is shifted or missing?

First make sure the title and subtitle are actually filled in. Then inspect the page in the browser. If the HTML is present but the text is hidden by styles, use a minimal CSS override through EventON Styles. Do not edit plugin files and do not add broad CSS that affects all events without testing.

Can I use tracking code on every included post?

Technically, the metabox includes an optional tracking code field, but it should be used carefully. Add only code that is understood and approved, and always check the browser console, cookie consent behavior, and cache compatibility. If the analytics goal can be handled through a standard analytics event setup or through URL parameters, that is often the safer option.

When is it better not to use Include Anything?

Do not use the addon if the content needs to be a full event with location, organizer, recurring settings, event status, tickets, or event type filters. In that case, it is more appropriate to create an EventON event and connect it to the content page through a link, the description, or a custom field.

When EventON Include Anything Is the Right Choice

EventON Include Anything is a good choice when a site already uses EventON and you need to carefully add content that lives as standard WordPress posts, pages, or custom post types into the calendar. It works especially well for courses, products, campaigns, publications, and announcements that have a relevance period and a clear destination page.

The key is not expecting it to behave like a full event system. Include Anything is not supposed to add location, organizer, repeating settings, or event filters to regular posts. Its strength lies elsewhere: it ties a calendar date to existing content and gives editors a fast way to surface an important page inside the calendar path.

If your use case clearly matches that model, you can download EventON Include Anything, install the addon on a staging copy or a non-public page, and walk through the chain from this guide: enable the post, set the date range, configure the title, subtitle, color, and link, add include_any="yes", and verify the public result.

The final test is simple: the visitor opens the calendar, sees the right content during the right period, understands why it is there, and after clicking lands on a page that actually solves their task. If that happens, the addon is integrated correctly. If it does not, go back to the boundary between a regular post and an EventON event and choose the more appropriate architecture.