midwestdev
Forum Replies Created
-
Forum: Plugins
In reply to: [Safety Exit] Recent Update Caused Button Not To ShowWant to jump in here and also say thank you for the plugin as well, but we were also experiencing issues with v1.6.3 and v1.6.4 where the button no longer shows on our site.
We’re using a custom theme for our client that was built 5+ years ago. This was before the action ‘wp_body_open’ was added as a function, so when you removed the do_action(‘wp_body_open’); in v1.6.3, it stopped working.
I added
<?php wp_body_open(); ?>into the header.php file in my theme and the plugin started working again, so it should look like this (or something similar depending on your theme.<body <?php body_class(); ?>> <?php wp_body_open(); ?>Hope this helps! And you can likely close this ticket, as it’s a probably more of a theme development issue than a plugin issue. wp_body_open() has been around since 5.2 released in 2019.
Forum: Plugins
In reply to: [Age Gate] Error while attempting to save Access rulesAlright, sorry it wasn’t entirely clear if it was going to have it’s own space in the customizer so that it only loads when the Age Gate loads or not. Appreciate the info, thanks.
Forum: Plugins
In reply to: [Age Gate] Error while attempting to save Access rulesHi @philsbury,
Thanks, I can verify that my initial issue is fixed, but as for the customizer, I maybe should have been a little clearer, the customizer is there, but I don’t see a dedicated area in for Age Gate’s CSS anywhere, and it’s not in any of the dropdowns there.
The site shouldn’t be using the customizer in any strange way, either, as far as I know.
Just in case, I did add your code in, but it didn’t change anything of note. Let me know if there’s another solution you’d like me to try. Thanks!
@eugenecleantalk –
Yes, I believe the issue is that the aforementioned apbct_visible_fields field is added and is an extra unknown field submitted to the third party which breaks. I think any extra information is considered a security risk by the third party provider.I downloaded and installed the fix plugin as you requested on two sites, both have login forms that work prior to activation and break after activation.
I will open a ticket through support, thank you.
@dimitrycleantalk – I did, but I still see the apbct_visible_fields field in that form after re-activation.
I’m curious as to what that was supposed to accomplish, or if there is a specific setting I was supposed to disable/enable before running the complete deactivation/reactivation.
While we use Gravity Forms for all our contact forms, the third party forms are created by the company who manages the secure banking site that we are passing this information off to. They are hard-coded, and not created via plugin.
Forum: Plugins
In reply to: [Disable Blog] Preventing 3rd Party Sitemaps@joshuadnelson – Appreciate the quick feedback! It absolutely might only be All In One SEO, I guess I assumed that it would throw an issue for anyone trying to get to the sitemap located at domain.com/sitemap.xml, but perhaps not.
While I’m perfectly comfortable using filters, my client wanted an immediate solution, which was to unfortunately disable your plugin (for the time being). Once you dive in and test it out, I’ll check back in the next few updates to see if you found a workaround so I can re-enable it!
Thanks for your hard work!
Forum: Plugins
In reply to: [Age Gate] Age Gate hacked on multiple sites, multiple serversCan confirm this was the cause here too.
Someone had overwritten the Yes/No button text (in mine) to implement a script that would auto-redirect the site to a 3rd party spam site.
Once I cleared that out (and had to reset all my styling because that was gone too), I believe it’s fixed.
I believe that your XSS update for imports in 2.17.1 may have fixed it, but I can’t say for certain. All I know is the text for the headline, custom CSS, and Yes/No button text had all changed. The yes/no buttons were implementing <script src=”garbage JS file here”></script> and causing a redirect.
Sure, in case it’s more helpful, one of the uses I have that wasn’t working is adding a custom length of time per post created on a Gravity Forms submission. The blanket post expiration isn’t what was requested, so I had to resort to setting the expiration programmatically after the form is submitted and the post is created. Otherwise, I typically use it as an admin tool on most other sites, so that level of programming isn’t needed. Hope this information helps.
@stevejburge No worries, I’m just glad you’re responsive! Dealt with a lot of un-responded support tickets in my day. Love the plugin and keep up the good work!
@stevejburge Function name changes are pretty common, so I understand, and luckily, I am able to change it in my case.
However, that being said, I didn’t do any dives into the code to find what the new function name was, there was no notes about it in your changelog, and as far as I can tell, there was no deprecation process to let developers know that it was changing, and what it was changing to.
Maybe adding a passthrough function with the old function name with a deprecation warning and adding something about it in your changelog would be a good first step and then drop it when you feel you’ve given enough warning? Just a suggestion.