Errors and Warnings

If you see an error or a warning message after adding the shortcode, do not panic.
This page exists to show you:

  • What the message looks like
  • Why the message was shown, and
  • How to fix it

Errors & warnings

TypeMessageCauseHow to fix it
errorCalendly shortcode needs a non-empty calendar parameter…The shortcode couldn’t infer the calendar name from direct parameters or site configuration parameters, front matter parameters, or a data file.Provide a calendar value. Either in the shortcode, or through other sources. See also configuring parameters.
errorInvalid type parameter (*) for calendly shortcode…Unkown value for shortcode parameter type.Use a valid type value as shown on the parameters page.
warningMissing or empty parameter ‘type’ for calendly shortcode…The type parameter has not been set. The shortcode will assume the value is popupLinkSet an explicit type parameter value. Either as direct parameter, or through global config, front matter parameters, or data files. See the parameters pages for more details.
warningUnknown badgeStyle.align value…A badgeStyle.align parameter has been set on the shortcode, but the value is not known. The value will be ignored and the default (right) assumed.Either remove the parameter (defaults to right), or set it to left, right, or center.
warningUnable to find data file starting with…A dataSet parameter has been set on the shortcode, but the shortcode could not find a matching data file.Make sure the file exists in the right location. See the section on configuring parameters.

Other known issues

Other issues may arise without any error or warning message. Below are the ones I am aware of.

I added the shortcode, but it doesn’t render on the page

This might happen for the following reasons:

  • Forgot to close the shortcode tag

    Make sure to properly (self-)close the shortcode tag: {{< calendly ... />}} (note the />}} part).
    Otherwise it will try to interpret everything after the opening tag as inner text. And since the tag never closes, the Hugo engine will not render it.
    Alternatively, use opening and closing tags separately: {{< calendly ... >}} (opening) and {{< /calendly >}} (closing).

  • The text value contains unescaped apostrophes or double quotes (' or ")

    This has to do with limitations on how the text is sent to Calendly.
    In particular, the text is sometimes sent as Javascript parameter, and that call fails when unescaped (single or double) quotes are used.
    You can prevent the issue by using HTML escaped characters instead (e.g. &#39; for apostrophe, &quot; for double quotes).

Similar to above, this means the Hugo engine cannot determine the right closing position for the tag.

Make sure to properly self-close the shortcode tag: {{< calendly ... />}} (note the />}} part).
Or use opening and closing tags separately: {{< calendly ... >}} (opening) and {{< calendly >}} (closing).

Still stuck?

Check out the Help and Support page. It will show you how to best contact me to get you unstuck again.