patrickhealy

OK, so I went for broke and since I only had a handful of redirects in place I switched the plugin option for the REST API to Form Request, opened the redirects page to keep that on screen, opened the plugins menu in a new tab, deleted the plugin, wiped the dbs, reinstalled and it worked fine. I then went back in and added the handful of redirects in manually.

This is certainly not an optimal solution by any means so I got lucky that I only had a few to do. I wouldn’t want to export these and try to import them for fear that the problem lied in that table.

Something must have become corrupted. It may be an Avada patch, it may not. It may have nothing to do with Avada. I am not sure but it’s working now and worth keeping an eye on for future development.

Thanks for the helpful insights and the great plugin. I use it on every site we manage/build.

Looks like that last push did it. I updated and cleared the cache and it all seems to be working properly now. FYI, the plugin being used in tandem is MaxButtons. We are launching a popup off of a style we put in the button so when you click on it, it triggers Popup Maker.

Not sure if you tend to monitor popular plugins that are used with this one but that one is a really good complement to this since they started messing with the sharing aspect of the button. It lends itself now to just using the button as a button and setting your own triggers and abandoning much of the rest of the plugin.

I believe what we did was we we created a simple container in one of the genesis simple hooks and dropped the short code for the button in there. We’ve done it this way for a few sites and they are all still working. I’m wondering if the button (or container) are butting heads with the popup creator that we have the button launching…..

We tried the social share when you released it originally but we couldn’t, for whatever reason, just get the button to float in a fixed position and have nothing else in the bar. The social share, ironically, wants something in there to share. 🙂

I do but I have the site rolled back to before the update so I don’t know if that will be helpful. Personally, I’d rather not post it publicly. Could I email it to you if you feel it would be helpful?

let me try dropping the MaxButton shortcode in one of the Simple Hooks and wrapping some CSS around it. That might do the job. I’m kinda surprised that nobody really used the button itself as a locked position float. Sharing buttons are almost ubiquitous and we don’t even use a plugin for them. We plug it in through Cloudflare and call it a day. No need to have that stuff wearing on your own servers when CF will carry the load and inject it on every page so easily.

No, that’s awesome. I think it’s great. If you are able to include specific exceptions (like the page the button points to) that would be even better. But the button that I built in THIS plugin (MaxButton) cannot be placed in that sharing float – which is why this question started. MaxButton enabled you to create a great little custom button. I just want to float that on the right hand side of every page on the site (potentially every page except the one that the button links to)

Maybe I approach this from a different direction. I’m trying to put a button that floats at the same spot on every page of the site (except maybe one) that drives users to a particular page (get a quote, make an appointment, etc). Is there any way to do this with Sticky Menu? All I need is a customization element that will stay put all the time.