If you’re using a mail tag for a dynamic text or hidden input in the To: field, you will get warnings from Contact Form 7 If you click the link provided by CF7 beside the error notice, it explains why: Invalid mailbox syntax is used In short, CF7 expects you to enter either a valid mail address, or a mail tag for an *email* form tag. The CF7 DTX form tags are not email tags. So CF7 considers these to be “invalid”. CF7 does not provide a way to register valid tags, so there is no way around the warning. But it’s just a warning, nothing is actually broken. As long as you are sure the tag you’ve created will always return a valid email address, you can safely ignore the warning.
UberMenu Extensions are now sold through sevenspark.com, and are no longer available on CodeCanyon – don’t worry, though, Envato licenses will still be honored.
ShiftNav introduced a javascript fallback in v1.4, which allows the plugin to recover in most cases even when other scripts on the site are malfunctioning. Since this has worked very well, this message has now been removed from the plugin in v1.5 When the page loads, you may see a flash of the message “Loading ShiftNav…” or “ShiftNav is Waiting to Load…” This message is only visible to logged in administrators. Your end users will never see it This message serves an important purpose. If there is a javascript error on your page, the message will remain, alerting you to this fact. Hovering over the message reveals more information: If the message disappears, then ShiftNav was able to initialize. If you really don’t want to see this message, you can add this custom CSS to hide it: If the message does not disappear, it means you either have a javascript error that prevents ShiftNav from loading, or else ShiftNav’s javascript was not run at all – which would indicate that either the resource is not being served properly, or your site is missing the wp_footer() hook and therefore not requesting the script at all.
Your transaction failed, please try again or contact site support.