Blog New Events

When you create a new event, automatically cross post it to your blog as a post.

Enable Blog New Events by checking ‘Copy new events as posts’

Blog New Event Settings

Settings for templating & timing your blog posts.

The settings for blogging new events are all about mapping your event data to become a post.

Blog Post Content: What content from your event should get submitted as the post content? Options include the event description alone, the entire event content, or custom text entered at event creation.

Blog Post Excerpt: What to create as the post excerpt.

Blog Post Title: Use the event title, or pass a custom format (that can include a template tag for the event title.)

Custom Title Format: A custom format to post to your blog, e.g. “Event Scheduled: {title}”

Custom Post Excerpt or Content: A custom format to post to your blog including template tags from the event, but with original formatting or copy included.

Blog Post Author: Customize the author used for the post.

Blog Post Status: Publish immediately, or post as in an unpublished format for further editing.

Use post permalink for Event URL: Set the link in the Event settings to this blog post.

Post Type: Publish as a post type other than a blog post.

Post publish date: Manipulate the date of the post in relation to the event.

Custom Post Time: Sets a specific time for the post that’s different from the event’s published date. (E.g., if you want an event on your calendar immediately, but want the post published at a scheduled time the next day.)

Payments Reporting

Table showing keys and usage information.

My Calendar Pro produces a simple report showing sales, dates, and how many times a given key has been used. As a key is used, the remaining uses will be shown.

You can edit any payment to grant additional event licenses or adjust information about the payment:

Editable fields for editing payments

Quantity: The number of event submissions currently available on the event key.

Submissions Purchased: The total number of submissions allowed on this key.

You cannot change the event submissions key once it has been granted.

Search Payments

Searchable fields for payments

Name/Email: Name and email as provided.

Transaction ID: The transaction ID provided from the payment gateway. (Not shown.)

Payment Key: Their event submission key.

After/Before: Get all payments within a date range.

Status: Get payments having a specific status.

Search results

Search results showing results, totals shown, and search limits applied.

Earnings Summary

Summary of payments made

My Calendar Pro provides a brief summary of the current month, current year, previous month, previous year, and all time sales totals.

Manual Entry Payments

Manual payments allow you to accept payments via any method – cash, check, crypto, or alternative online payment – and use those payments to provide event keys. You can also use them to grant free keys at any time, to any user.

Manual payment entry form

Quantity: How many events can be submitted using this key. Each event submitted will reduce this value by one.

Price Paid: The total price paid for this key. There’s no enforcement of a relationship between the price of a key and the number of usages it allows; this value is purely for your own tracking.

Name/Email: Required to send information about the new purchase to the recipient.

Transaction Date: Defaults to today’s date, but doesn’t have any direct impact on the use of the key. A transaction dated in the future will still be usable today.

Requiring Payments

Event submission is a free service by difficult. There are many membership plugins that can be used to control access to your site or to pages of your site for a fee, but if you simply want to grant a variety of users access to pay to submit events, My Calendar Pro allows that.

Enable payments for Event submissions.

Check the box ‘Require payment to submit an event’ under the ‘Payments’ tab to require payments.

Payment settings are broken into four areas:

  1. Payment Settings
  2. New purchase settings
  3. Pricing
  4. Payment Gateways
  5. Configure a Sale

Payment Settings

  • Set your payment gateway into testing mode.
  • Payment required message.

New Purchase Settings

New purchase notification settings.

Predictability enough, My Calendar Pro sends a message to the administrator and to the purchaser following a new purchase. These fields accept a handful of template tags for dynamic values:

  • {first_name}, {last_name} – as provided by the purchaser.
  • {blogname} – Your site title as configured at WordPress > Settings.
  • {price} – The total amount paid.
  • {key} – The new event submission key the user should use to submit an event.
  • {quantity} – If allowing multiple purchase, how many event submissions this key is good for.
  • {receipt} – Link to the purchase receipt.

Pricing

Pricing options

Each event submission has a base price, which is the default price charged for any event submission.

To more finely configure options, you can set a unique price for each user role and/or set a percentage discount for logged-in members, that will apply to all members.

This is also where you’d set the currency you’re processing payments in.

Payment Gateways

Configure payment gateways

At this time, My Calendar Pro only supports PayPal basic payments. Set your primary PayPal email (this must match the primary email as configured in your PayPal account settings), and add your merchant ID.

Configure a Sale

Set a temporary sale

Configure a special sale or limited-time discount period by entering a start and end date and a percentage discount. My Calendar Pro only supports one sale at a time, and it applies equally to all purchasers.

Public Event Management

Logged-in users can be given access to view and edit events that they submitted to your site.

Event management for public users

The front-end event manager uses the same default sorting as the admin event manager. It can be access using the [submitted_events] shortcode.

[submitted_events]
Display a message to users who don't have access to edit events.
[/submitted_events]

Logged-in users can filter events by location or category, can view their events from the lists, or can edit or delete an event. Deletion is not instantaneous, and will require confirmation:

Pre-deletion warning in editor.

Submission Notifications

General settings

Set options for event notifications
  • Set whether the submitter should be notified about their submission.
  • Set whether the administrator should be notified about new submissions.
  • Enable HTML notifications (text-only email by default.)
  • Define sending email address.

Messages sent to administrators

Settings for administrator notifications

There are two types of notifications that are sent: one for newly submitted events, and a second if a submitted event is edited. Each option has a separate subject and message text.

The new event notification is sent whenever an event is posted using the front-end submissions form.

The edited event notification is sent whenever an event is edited using the front-end editing form. It is not sent for edits in the admin Event Manager.

Message sent to submitters

Settings for email notifications sent to submitters.

There are three notifications sent to submitters following submission.

  1. Message sent following a new submission.
  2. A message sent if the event is edited by an administrative user in the Event Manager.
  3. A message sent to notify the user that their submission has been published.

Submission Permissions

Set the user group allowed to submit events.

As of version 2.1.0, the submission form requires users to be logged-in to submit events as a default. Previously, it was open to the general public by default.

The third setting allows finer control over who has the ability to add events to your calendar. The ‘Add Events’ capability is configured in the My Calendar Permissions Settings.

Use the [submit_event] shortcode to display a custom message to users without sufficient permissions:

[submit_event]
Hey, you can't submit events! Create an account to submit an event.
[/submit_event]

Required Fields

Checkboxes to set specific event fields as required.

By default, no event fields are required except for the start date. If you require additional information from your visitors, you can uses these checkboxes to set some fields as required.

Making any field required will make it required on all public submission forms. If you have excluded a required field from a form, it will be automatically added back in.

Event Submissions Settings

General Submissions form settings

Review pending events: By default, events submitted via the public submission forms are assigned “Pending” status, and require approval for publication. This link points to the My Calendar Events Management screen with ‘Pending’ events shown.

Create a submissions form: Although a basic shortcode is automatically created when you in-stall the plug-in, you may want to customize it. This link goes to the shortcode generator so that you can more easily configure the settings for your submission form.

View Event submissions form: Links to your currently defined submissions form. It’s not required to use the primary submissions form, but if you’re offering front-end event editing, then you will need this form to support all of the front-end eligible fields. Set the ID for your event submissions form page in the “Event Submission Page ID” field.

View event editing form: Event submissions can also be edited on the front-end if your users are logged-in. Event editing is not available for users without a log-in. Set the ID for your event editing form page in the “Event Editing Page ID” field.

Date Format hint: What date format is used in the My Calendar date selector.

Time format hint: What time format is used in the My Calendar time selector.

Prevent Conflicting Events: If checked, My Calendar: Submissions will reject event submissions that conflict with a previously scheduled event (in the same location, when location information is being submitted as well.)

Copy submitted locations into locations tables: If a user submits a new location, it will be copied into the location table for other users to choose.

Allow public event submitters to upload images: If checked, submitters will be able to upload images to your site for their event image when that field is included in your form. Otherwise, they must provide a URL to the image.

Automatically publish submitted events: Normally, all events are expected to go through approval. If you want them to just go immediately to the calendar, however, you can allow all events to be automatically approved.

By default, any events submitted by users who already have permission to post events to the calendar will be automatically approved. E.g., if you publish an event from the front-end form while logged-in as an administrator, that event will be immediately published.

Shortcode Generator

The My Calendar Submissions Form shortcode generator

The shortcode generator allows you to generate a heavily customized form with My Calendar’s event fields. You can use the up and down arrows to modify the order of fields, customize labels, set default category or location, and choose which fields are included.

Some types of fields don’t support custom labeling through shortcodes. These fields (registration and recurring settings) are compound fields, and the section of the form you enable with that setting includes multiple form inputs, rather than just a single input.