squidz

The plugin conflict is with Wordfence BTW. So that part is resolved…in that we know what the conflict is. It is not resolved in that the live site will continue to use Wordfence and WPDataTables and Wordfence are not playing nice. I’d have to turn off WF every time a table needed to be edited.

This was the error in the console with the blank page on saving with Wordfence turned on: Failed to load resource: the server responded with a status of 403 ()

Now I will test whether the mobile responsive features actually work for this plugin by changing to a non-bootstrap theme.

I really need to know if this thing will work if I’m going to buy a license moving forward.

• This reply was modified 1 year, 8 months ago by squidz.
• This reply was modified 1 year, 8 months ago by squidz.

Yeah. I killed that page. New link is here. I have determined that it is likely a plugin conflict, as I turned all others off and the issue is gone. I haven’t turned them all back on yet to check which one is the issue because this is just a test/proof of concept experiment so far.

HOWEVER, is the paid version having trouble with Bootstrap 5?

Possibly related: I have NOT been able to see the expandable blocks on mobile with any settings changes I’ve made. That will definitely be a major road block.

Clarification: It is actually sending these errors when NO emails are even being submitted.

You getting this message because an error detected while delivered your email.

The log to paste when you open a support issue:
5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message. 0.35250:0A002E88, 1.36674:0A000000, 1.61250:00000000, 1.45378:02000000, 1.44866:96300000, 1.36674:0E000000, 1.61250:00000000, 1.45378:9B300000, 1.44866:DE020000, 16.55847:3A160000, 17.43559:0000000024020000000000000000000000000000, 20.52176:140F698D2D00F01F00000000, 20.50032:140F698D9D17F01F00000000, 0.35180:140F698D, 255.23226:0A00218C, 255.27962:0A000000, 255.27962:0E000000, 255.31418:0A004D8C, 0.35250:1F001432, 1.36674:0A000000, 1.61250:00000000, 1.45378:02000000, 1.44866:4C000000, 1.36674:32000000, 1.61250:00000000, 1.45378:51000000, 1.44866:01000000, 16.55847:B8000000, 17.43559:0000000070030000000000000100000000000000, 20.52176:140F698D2D00101053000000, 20.50032:140F698D9D170000F1300000, 0.35180:58000000, 255.23226:4800D13D, 255.27962:0A000000, 255.27962:32000000, 255.17082:DC040000, 0.27745:FB300000, 4.21921:DC040000, 255.279

I’m curious where should this JS be placed and what does #pum-123 refer to?

I very much understand. I’ll adjust the review. I’d asked about the future of the plugin but received no response.

Whether files were specifically supported or not, during our application period last year, they did remain until the form was submitted. It served the purpose perfectly for a 12 page form.

Matt/Devin, while trying to work through this, a plugin update alert popped up. The version downloaded just a few days ago was 1.7.2 I believe. But the update jumped to 1.8.1. It seems that either that update or upgrading PHP and SOAP on the server did the trick. Thanks for the rapid response guys!

UGH! This is clearly NOT what anyone wants to be doing just to get a map to show up when there are many other ways to do it and dealing with the API is already a pain.

Jetpack crew, are y’all working on getting this fixed? I simply tried to update the address for a client whose site I’ve inherited and have stepped in this big pile of goo. Now that I’ve spawned the error, I’m stuck in this time sucking process.

That is correct Robert. I’ll set up a user for you and email the creds.

Ideally, want to use your autosave feature but also include the Save button feature of the associated plugin. This is due to the non-tech-savvy nature of the folks using this online application.

It’s a long 12 page form used by municipalities to apply for a program provided by my clients. Often, it requires multiple staff to supply the data requested, so the form is rarely completed in one sitting. Thus the need for persistent data and the need to make sure they don’t lose data input due to typical mistakes, like accidentally leaving the website, closing the browser etc. They are also much more comfortable being able to hit “Save” to be sure they aren’t losing data, thus the piggyback “reloaded-save button.” However, due to the issues I have deactivated the save button since it was not actually saving. So right now, it’s just “reloaded” that is active via Ajax.

I’ve tested with Chrome and Safari only.

A little extra info:

The only way the data will be persistent, it seems, is if one clicks the button to move to the next page of the form.

This is the functionality of the plugin that “reloaded” was meant to replace.

I’ve switched the hook to gform_after_submission in the plugin but there is still no automatic saving going on. Any ideas?

Thanks Edward. I will try that out. Really like the core function of the plugin and your fast reply.

Hey Brandon, sorry for the non-response. I’ll circle back and check Foobox again. Not sure why I didn’t see your first reply. For the project I was working on, I moved on to a different solution to get it wrapped up as it was a quickie pro-bono gig.

JQuery is loaded.

I will test your new version.

rbird, quite helpful and saved me continuing to cobble together code that would accomplish this.

I’d tried this plug in a couple of circumstances and could never figure out from the sparse documentation how to get it to behave. The selections are not very intuitive for folks who don’t know the ins and outs of WordPress menu code.

I second this issue. If one has multiple lists a user could potentially sign up for, it would be nice if it were like Constant Contact’s default form that provided checkboxes for the user to check the lists they want to receive IN ONE FORM rather than trying to make individual forms for each that then require unique emails.

Your review is a waste of time. If you feel this way about the plugin how about you give us some meaningful information regarding the performance of the plugin or the lack thereof.