sevenspark

Hi @malae ,

Thanks for letting me know. You can fix this by making a simple change in that functions.php file on line 714. Just change the function signature from:

function shiftnav_html_atts(array $attr, callable $callback = null)

to:

function shiftnav_html_atts(array $attr, ?callable $callback = null)

(add a ? before callable)

and that should resolve the deprecation notice. I’ll also include this with the next update.

Thanks!

Chris

Hi Justin,

There isn’t a setting for this in the lite version, but in the Pro version there’s an option called “Toggle Content Left Edge” that would allow you to add text in that position.

I suppose an alternative would be to use an ::after pseudo-selector with the content property in some custom CSS to add that text if you prefer. Something like this:

#shiftnav-toggle-main-button::after {
    content: "Menu";
    margin-left: 8px;
}

Note that the text itself won’t be screen-reader accessible, but the toggle button has its own aria label for that purpose.

Hope that helps!

Chris

Thanks for letting me know, guys!

That zip is built by ww.wp.xz.cn from the svn repo, so it sounds like something went wrong on the wp servers when the last release was pushed.

I just pushed a small readme update to svn to force it to re-build, and now the zip download seems to be working for me when I test. It’s possible you’d need to clear the cache for it to resolve since the zip name/URL will be the same.

Hopefully that does the trick for you!

Hi @girdy74 !

The plugin is still maintained 🙂 I’d estimate the next update will be out in the next few weeks.

Thanks!

Well, I wrote out a detailed reply, which was then auto-held for moderation by the WP forum system. Not sure when it’ll be reviewed/approved, so in the meantime I’d recommend reading through the guide we’ve linked to in the changelog and admin panel (post-update).

Hopefully this one doesn’t get held up as well.

There was a security vulnerability (which required an authorized user with Contributor+ credentials to exploit) that exposed a potential XSS attack. A fix was implemented as soon as it was reported and the WP Plugin Team reinstated it on the 3rd just a few hours after you opened this actually 🙂

Thanks!

Hi Rolf,

Is “UACF7_POSTINFO” a custom shortcode that you’ve written? If so, what is your code? Are you sure you’re returning the proper value? (Shortcodes must return, not print/echo, their value).

Without knowing any more, my best guess given what you’ve described is that you have a custom shortcode that is mistakenly echoing rather than returning its value.

Hi @guglielmirent ,

The plugin only works with text fields, so it won’t be relevant for a selectbox

Presumably the order number is a variable available during your page generation process. If you can grab that order number via a shortcode (either with an existing on in your setup, or by writing a Custom Shortcode), then you can add it into the form via the DTX. You could potentially write some code to try to parse it out of the URL, but it’d likely be more robust to pull that value from the actual source than from the URL.

Hope that helps!