sevenspark

Hi Franz,

Glad you’re enjoying the plugin ??

You’ve submitted a few tickets over the years, and we’ve always had positive interactions.

We’ve always replied to your support tickets sent through our support center within a few business hours, including the one you just sent over the weekend (our support hours are Monday-Friday 9am-5pm ET).

Please note that this www.ads-software.com forum is only for the Lite version of ShiftNav; it is not checked anywhere near as frequently, and we are not permitted by WordPress to provide Pro users support here. That’s why we have the support center for Pro users and always provide fast support there, and include a link directly to the Pro support ticket form in the plugin’s admin interface itself. It’s also why we have a sticky topic at the top of this forum explaining that Pro support requests must be sent through the ticket system.

To your question – as I explained in the email reply I sent yesterday (Monday) morning in regard to your ticket, the shift occurs because the height of the toggle bar is measured dynamically via Javascript, since it is unknown before rendering, which naturally causes the items below it to shift. That’s generally not an issue, but in order to prevent that, we can add a CSS snippet which sets the height explicitly, which I sent you in response to your ticket, along with some other recommendations. If you have any questions about those, feel free to reply to that ticket email and we’ll be happy to help.

If you have any questions or need assistance in the future, please be sure to Submit a Ticket so that we will see your question and can assist you promptly.

Hope that helps. Take care ??

Chris

Hi takkularapsis,

The plugin allows you to programmatically control the default value of a text input field in Contact Form 7, via a shortcode.

If you have a shortcode that produces the unique reference number you want, you could add that into the form, either as a text or hidden field. (You can use any shortcode that returns a text value, or write your own custom shortcode to generate the value you need – there is no built in shortcode for unique reference number generation).

You could then include that value in the email that gets sent to you via mail tags, just like any Contact Form 7 field.

That said, if you want to generate a number *after* form submission, this plugin won’t help you, as these values are generated when the form is generated (on page load), not on form submission.

Hope that helps

Hi Frank,

The default toggle button is given a tabindex of 1 so that it will be the first element focused when tabbing through the site, since it appears visually at the top.

This is because the button is actually injected into the document in the footer, then positioned via CSS at the top. If the tabindex were set to 0, it would actually be the last thing you’d focus when tabbing through the page. Generally you want the user to be able to access the menu early on for the best UX.

If you add a custom Toggle within the flow of the document (within your header, for example, rather than using the default toggle), then the tabindex will be set to 0 so that it will be focused within the normal flow.

Hope that makes sense ??

Hi Frank,

What element are you trying to change the tabindex on?

Awesome, glad it helped!

Hi there,

The out of the box option will be to use the CF7_URL option which will include the entire URL

[dynamichidden url "CF7_URL"]

If you want to get just the query string itself, you could use a custom shortcode like this

add_shortcode( 'MY_URL_QUERY', 'my_url_query');
function my_url_query(){
    return sanitize_text_field(parse_url($_SERVER['REQUEST_URI'], PHP_URL_QUERY));
}

And then use MY_URL_QUERY as your shortcode in your form tag.

That said, I’d probably use the built in CF7_GET shortcode to pull individual values from the query string, assuming you know which keys you want included in the email.

Hope that helps!

Sorry for the late reply, just pushed a new update ??

Hi Tessa,

Thanks very much for your contributions to the plugin, they look great

I do apologize for any misunderstandings, and want to clear a couple up:

1. There was never an intention on my part to abandon the plugin
2. I never gave permission for the plugin to be adopted, and did not “change my mind” at any point.

What happened was the WP plugin team attempted to get in touch regarding your request for adoption, but unfortunately I never saw the email. Therefore when they didn’t receive a response they assumed I wanted the plugin to be adopted. It was a shock for me when I realized what had happened last week, and I contacted them as soon as I found out to rectify the issue.

I’m sure it must be frustrating to have this reversed; I do apologize for the confusion, unfortunately I simply wasn’t aware of what was going on until after the transfer. I certainly wish I had received that email from them so this could have been avoided.

Anyway, this week I’ll be working on going through the code updates you’ve made and reconciling them with my own git repo before pushing a new update to reflect the original authorship in the WP repository. I want to make sure there are no hiccups for the CF7 DTX users of course. The plugin is not in limbo, I’ll continue to maintain it from here on out.

I want to reiterate that I appreciate your code contributions and how you’ve helped users in the forum – thank you! If you’d like to continue to contribute to the plugin, I think that could be great as well. Please feel free to get in touch and we can discuss the best way to make that happen. You can email me at chris at sevenspark dot com if you are interested ??

All the best,

Chris

Apologies for the late reply, this should be resolved in the latest version ??

Apologies for the late reply, this should be resolved in the latest version ??

Hi there,

Making the entire parent item a toggle can be achieved in the Pro version menu item settings: Disable Link / Full Item Toggle, there isn’t an option for it in the Lite version

Just confirming this should have been resolved with the 1.4.1 update back in October ??

Sorry for the very late reply, I looked into this with the latest version, and the best I can tell from the information available is that wp_nav_menu() may be called at some point without any $args. My best guess would be that something is filtering them incorrectly and returning an empty array, rather than the proper $args object. I think that’s most likely why you’re getting the ‘non-object’ notice, so I’d be looking for any filters (could be in any plugin, theme, custom code) that is filtering the nav menu args object. Best I could tell from reviewing the core wp_nav_menu() code, it shouldn’t be possible to have a non-object there unless there’s a bad filter someplace.

Hope that helps!

If you’re getting a 404 for the custom.css, it simply means the file does not exist at that location. So either it was not created or created in the wrong location. Naturally I can’t assess anything without seeing the site and knowing where you placed the file, but the first thing you should do is check that your custom.css is actually in the proper location on your server.

If the file is in the proper location then it’ll work properly. Compare the path in the URL to the file path on your server for starters.

Hope that helps

Hi @raoulunger

If you’re using anchor links within the page, you’ll want to set them up using the Scroll To feature. Once the scroll completes, the menu will close automatically.

Hope that helps!