shainanz

You can see how the live site is structured here. Maybe that will help.

I don’t think this is relevant to my problem, and it’s a long boring explanation, but the site is actually two WP installs. One is the public-facing one that anyone can access. The other one is a members-only area (the “Trade Orders” link). Both of them have an e-commerce store using the same plugin, but they show different levels of product information (one uses it as a catalogue, the other as an ordering area). For lack of a better idea, they are separate installs.

The menus on both installs are the same, however; both mostly point to pages on the public-facing site. To do this, I had to use “Links” instead of “Pages” in the menu on the members-only WP install, since the pages themselves sit on the public-facing site.

The problem is with the public-facing site’s menu.

Thanks for the idea, vizou. Sadly it did not fix my problem ??

It’s on a private test site–I haven’t updated my live site yet–but here’s another screenshot. If you look at the HTML being outputted, you can see by looking at the classes and ids of some of the elements that the menu being used in the messed up menu is a different menu than what is being used in the working menu.

I am calling the menu with <div id="menu2"><?php wp_nav_menu( array('menu' => 'Primary Menu' )); ?></div>, and the correct menu is set as “Primary Menu” in WP-Admin.

Let me know if you want me to screenshot anything in particular. Thanks for taking a look ??

Thanks, Ipstenu. I’ve refreshed my caching plugin’s caches and done a hard refresh in my browser–is there something else I should be doing?

Hi mbrsolution. I ended up switching to a different plugin that made it much easier to get the solution I needed.

Hi,
I have had a look at that URL, but am having trouble implementing it on my form as it is more complicated than the example given. Is there a live demo you have of this in action?

Additionally, it looks like that by using position: relative to move some of the fields, it will force those fields to stay positioned even as the page resizes, rather than dropping down below the first column as they would do if it were floated. Is that the case?

Thanks!

PS – The link above is to our live site, which still has the table-style two-column layout. I am making changes on a separate test site.

Not sure if this will help anyone else, but my issue ended up being with a special character (the degree symbol). I converted it to the html code for the symbol and it worked fine.

Did anyone have any luck with this?

Hi again,
That wasn’t my point. My point is that the phrasing sounds like they are opting out of that particular message, not all messages, which is what the button actually does.

From a website designer or developer’s perspective, it makes no sense to let people opt out of all messages, and have no way to have them see it again. Once a user clicks that button, the popup plugin becomes useless when I want to interact with that user again.

I hope that makes more sense.

Thanks for the fast reply.

At the moment, I only have one pop up going at a time, but I know in the future I will require two. At that time, I may need to switch to another plugin.

For what it’s worth, I feel that this isn’t a feature request, but actually an essential part of functionality that was overlooked during development. It just doesn’t make sense to have a button on one popup turn off all other popups, especially when the default message is “Never see this message again” and not “Never see a popup message again”.

Thanks ?? In the meantime I’ve had to switch to a different plugin, but I really liked the simplicity of yours so I may switch back if there’s a fix.

Hey, @yoxalld, did you ever figure this one out?

@kshirod patel – did you ever figure this out?

The most recent update to the plugin did that to me too.

I fixed it by moving <tr> and <td> from Basic Settings>Welcome Introduction to “HTML before form field” under my first field.

I then moved </table> to the end of my last field, so that there was nothing in Advanced>After Form Message. (Because I had removed <tr> and <td> from the Welcome Introduction, I no longer needed to close them in After Form Message.)

I never ended up resolving the issue with this plugin. Instead I used the plugin Restricted Site Access.