GF Form Notices 1.0.3

GF Form Notices shows custom messages above Gravity Forms during set date ranges. Each notice is its own feed, with rich text formatting, recurring dates like *-12-25, date merge tags, and one weekday of advance notice. Overlapping notices display together.

VERSION:
1.0.3
UPDATED:
2026-11-20
DEVELOPER:
Gravity Wiz
LICENSE:
GPLv2 or greater
AUTO UPDATE:
Yes

Description

What if your forms could announce the holiday closure before anyone asks?

Picture a customer filling out a support request on December 23rd. Your office closes the next day, replies won’t arrive until the 27th, and nothing on the form tells them so. They submit, wait, and then write a second, irritated message. GF Form Notices fixes that gap. This Gravity Forms add-on puts a custom message above your form during the date range you choose, then removes it when the range ends. No one has to remember to switch it on or off.

The GF Form Notices WordPress plugin treats every notice as its own feed. That one decision shapes the whole tool. You can run a holiday closure, a sale deadline, and a maintenance warning at the same time, each with its own dates and wording, and edit one without touching the others.

Recurring dates that never need re-entering

The most distinctive thing about this plugin is how it handles dates that come around every year. Enter a specific date such as 2024-12-25 and the notice fires once. Replace the year with a wildcard, *-12-25, and it matches December 25th every year without any further attention. The same goes for *-07-04 on Independence Day, or any other fixed calendar date your business observes.

Anyone who has built a holiday banner by hand knows the usual routine: set it up in November, forget to remove it in January, then rebuild it all next year. Wildcard dates remove that cycle. You write the notice once, and it comes back on schedule year after year.

One weekday of warning, built in

Notices don’t wait until the start date to appear. They show one weekday earlier, so visitors get a heads-up before the change takes effect. If your office closes on a Monday, people see the message the preceding weekday rather than discovering the closure on the day itself. For a form that collects requests, bookings, or orders, that small head start prevents a lot of confusion.

Merge tags that write the dates for you

Typing dates into a message by hand invites mistakes, especially when the notice repeats annually. GF Form Notices includes three date merge tags that pull the dates from the feed settings and format them as you specify:

  • {start_date:FORMAT} prints the first date of the range.
  • {end_date:FORMAT} prints the last date of the range.
  • {next_date:FORMAT} prints the next business day after the end date, which is handy for telling people when you’ll be back.

The format portion uses standard PHP date strings. A tag like {start_date:l, F jS} produces something like “Monday, December 25th”, while m/d/Y gives you 12/25/2024. Since the dates come from the feed itself, the wording stays accurate even when you adjust the range later.

The complete feature set

Beyond recurring dates and merge tags, the plugin covers the practical details that make notices manageable once you have more than one.

  • Feed-based management: every notice is a separate feed with independent settings, so you can create, edit, or retire them one at a time.
  • Specific and wildcard dates: use the YYYY-MM-DD format for one-off events and wildcard years for annual ones.
  • Rich text messages: compose each notice in the familiar WordPress editor, with bold text, links, lists, and other formatting that makes the message readable.
  • Date merge tags: insert start, end, and next business day dates in whatever format suits your tone.
  • Feed ordering: sort your notices so the most important one sits where you want it.
  • Advance notice: messages appear one weekday before the start date.
  • Multiple active notices: when date ranges overlap, every applicable message displays together.

Overlap deserves a closer look. Say a spring sale runs through the end of the month and your office also closes for a long weekend inside that window. Both notices show. Visitors see the sale and the closure, and neither message knocks the other out. Feed ordering then lets you decide which appears first. The plugin is released under the GPL, so you can inspect or adapt the code the way you would with any other WordPress plugin.

How it fits your workflow

Because the plugin works through Gravity Forms feeds, setup feels familiar if you’ve configured notifications or confirmations before. You open a form, add a notice feed, write the message in the editor, and enter the date range. That’s the whole process. There’s no separate dashboard to learn and no shortcode to paste around your pages.

The notice sits on the form itself, which matters more than it sounds. A site-wide banner can be ignored or dismissed, and it may not even appear on the page where the form lives. A message directly above the fields is read at the moment someone is deciding whether to submit. If the form is embedded on three different pages, the notice follows it to all three.

For teams, the feed structure also helps with handoffs. A colleague can open the form, scan the list of feeds, and see which notices exist, what each says, and when each runs. Old notices can be deleted or left dormant, and recurring ones simply wait for their next date. Planning ahead is easy too: you can write December’s closure notice in the spring, set its dates, and move on.

Ideal use cases

Offices and service businesses

A dental practice, law firm, or repair shop can post holiday hours above its appointment request form. With a wildcard date for each holiday, the notices return every year. The {next_date} tag can tell visitors exactly when someone will respond, so the message stays correct even if you stretch a closure by a day.

Stores and promotions

If you take orders or quotes through Gravity Forms, a limited-time offer can run above the form for exactly its duration. Use bold text for the deadline and the end date merge tag to state when the offer expires. When the range finishes, the message disappears and the form goes back to normal.

Events and deadlines

Registration forms benefit from reminders such as “Sign-ups close Friday, March 14th.” Put the date in a merge tag, and the message follows the feed settings rather than a sentence someone typed months earlier.

Maintenance and support updates

When a booking system will be offline for a few hours, or support availability shifts for a stretch, a short notice above the relevant form saves you from answering the same question repeatedly. Seasonal messages, from summer shipping delays to winter schedule changes, work the same way.

Frequently asked questions

How do I make a notice repeat every year?

Put a wildcard in the year position of your date fields. Entering *-12-25 matches December 25th in any year, so a single feed covers every future Christmas. The same pattern works for any fixed date, such as *-07-04. Specific dates in YYYY-MM-DD format remain available for one-time events.

Can more than one notice appear on the same form?

Yes. When date ranges overlap, every applicable message displays together above the form. A sale and a holiday closure can both be visible at once, for example. You can use feed ordering to control which notice comes first, so the most important message gets the top position.

When does a notice start showing?

Messages appear one weekday before the start date you set. This gives visitors advance warning instead of surprising them on the day a change begins. It’s useful for closures and deadlines, where a little notice lets people act before the date arrives.

Category: