Recent ShortStack upgrades

Previously, if a Field Widget was hidden via that widget’s timed visibility settings, we would still try to validate it on our server. Now, when a form is submitted to our server, we won’t attempt to validate such widgets.

We have indefinitely suspended Twitter hashtag feeds and Retweet feeds. As you may have heard, Elon Musk recently announced new API pricing for Twitter/X, which has made it considerably more expensive to use the Twitter/X API for our business. After careful consideration, we decided that the added cost was too high–the level of access we need starts at $42K a month–and we don’t want to pass that cost on to our customers. Additionally, the new Twitter/X API won’t provide the same functionality as the current version, which limits our ability to offer the same quality of service you rely on. We know many customers use Twitter/X hashtag and Retweet feeds for contests planned well in advance, and this change may be frustrating. We apologize for any inconvenience it may cause, and we’re happy to work with you to get these contests over the finish line.

In a normal Form Container Widget, the default Submit button and the sending/error messages appear at the bottom of the widget, so they always appear together. To help prevent any potential confusion when building complex forms, the Sending and Error messages now appear in the Builder. They only appear in Build mode; in Preview mode they will disappear.

Rather than outright rejecting entries with low reCaptcha scores–which can prevent legitimate entries as well as make it easier for bots to fine-tune their submissions to bypass reCaptcha–we wanted to make it easier to accept entries with lower scores, but reject them for Instant Win or when picking winners after the campaign is over. You can find these new tweaks in the reCaptcha settings.

You can now submit forms with a hidden submit button by pressing the Enter/Return key. In order for this to work though, the Action Widget responsible for submitting the form must have a visible fields are valid trigger. This is the trigger we commonly use to advance to the next set of fields in multi-step forms.

All query parameters in the parent page URL are now passed to embedded campaigns and can be used in Action Widgets exactly the same as if those parameters were part of the campaign URL.