maxfoundry

Marking as resolved.

Every visitor starts by going to the original page, but then MaxA/B kicks in and decides whether or not to keep the user on the original page or redirect them to one of the variation pages.

This is done by checking for a MaxA/B cookie and the value of that cookie, which correlates to which page the user should see.

This is on our to-do list, marking as resolved.

Marking as resolved.

Marking as resolved.

Yes, you can use MaxButtons Pro in as many WP sites as you want.

Every button created is specific to the site it was created in. This is because each site gets its own buttons table; therefore, button IDs are specific to each site.

For example, the shortcode [maxbutton id=”1″] used on site A will render a different button than the shortcode [maxbutton id=”1″] used on site B.

Marking as resolved.

Marking as resolved.

Marking this as resolved.

That isn’t something the plugin itself can do (although it is a pretty good idea). You’d have to write some logic in your main menu to do it.

Can you provide a link to the page with the buttons? That will help us see what’s going on.

It should work in multisite, we know there are people using it that way. Do you have any specifics about the issues you are seeing?

Are you still having this issue? We’d like to try and track this down.

Yes, MaxButtons is definitely supported and moving forward – we have more updates coming out soon.

As for versions lower than IE9, we don’t make any promises. It’s just too time-consuming to do so, sorry. We are aware of a couple of the other issues people have had with IE9 and are working on addressing those.