Contact forms have stopped working


(Paul Stokes) #1

Since upgrading to 8.1.3 my contact forms, which were working, no longer send emails. In trying to work around this I’ve found that if I change the ‘send to’ email address the ‘Publish’ button stays greyed out (and the red ‘close’ button does not have a black dot in it). Does this indicate that Rapidweaver isn’t registering that I’ve made a change to the project?


Foundation Contact Form Ceased Working - Help Appreciated
(Paul Stokes) #2

Further to this, ‘HTML Contact Form’ from Doobox does work, so I guess that this would indicate that server setting etc. are fine and that the problem is in Rapidweaver.

BTW using the Doobox stack doesn’t solve the problem because it doesn’t have the upload facility that I need.

Everything worked fine until 8.1.3. Installing 8.1.4 hasn’t cured it.


(Ric) #3

I had exactly the same problem with the Foundation Contact Form. I posted about this yesterday.

I swapped out for the DooBox Contact Form which I have working.

Today I can’t connect to my ftp server with 8.1.3. and 8.1.4. I have never (ever) had a problem connecting to my ftp server. If I run the test on the ftp setup panel it says it’s fine.

Using RW and upgrading is a f… lottery.


(Joe Workman) #4

Republish all files?


(Paul Stokes) #5

Tried that. It makes no difference.


(Paul Stokes) #6

Updating this…

I’ve tried toggling the advanced setting in the Inspector panel. I’ve also tried deleting all files on the FTP and then republishing all files, all to no avail. I’m using 123-reg on a linux server running php 7.2 as a host. I’m using Rapidweaver 8.1.5 and everything worked fine until mid to late January (ie. the introduction of RW 8.1).

There are two thing I’ve noticed that may be relevant.

Any changes made in the inspector panel do not prompt a save or publish action. The ‘Publish’ button stays greyed out unless I add or delete a field in the body of the form.

There are three ‘required’ fields in the form but omitting any of them make no difference to the result. It just reverts to the “Please fill in the form below to send us your DPI files and print titles” header at the top of the page instead of the “Fields marked with * are required.” message. Also clicking on “Submit” doesn’t display the “Thank you” message either.


(Joe Workman) #7

Is there a URL that we can test?


(Paul Stokes) #8

Yes it’s: https://suttonphoto.club/contact-form-2/ ( https://suttonphoto.club/page-9/ is the Doobox form)


(Doobox Software) #9

Are you having the form send to: something @ suttonphoto.club ??
If it worked previously, then your host may have made some changes that only allows the form to be sent from an address tied to your server like this.

Otherwise the form is indeed sending and just getting caught in your spam folder.


(Paul Stokes) #10

We may have our wires crossed.

The Doobox form (https://suttonphoto.club/page-9](https://suttonphoto.club/page-9/) works perfectly. It’s the Rapidweaver template (https://suttonphoto.club/contact-form-2) that fails.

If the Doobox form had an upload/attachment facility I’d use that for both.


(Paul Stokes) #11

Further to this, I’ve contacted the hosting company that I use with about this and had the following reply:

" To test your hosting package, I have now added a file called mailtest.php on your hosting package (for lucentimage.uk) and accessed it with:
http://lucentimage.uk/mailtest.php
I can confirm that an e-mail has been sent and received after the file was accessed.
You can test the script yourself, however, please edit the file and replace enter_email_here with your destination e-mail address.
As there are no issues with the hosting package, I recommend that you contact the developers of the contact form you are using to further assist you."

Which I understand to mean “It aint us, it’s them!”


(Paul Stokes) #12

I found that I still had RW 7 installed (as well as RW 8), so trashed all of my RW application files, downloaded a fresh installer for RW 8.1.6 and then installed and re-started my Mac and…

…it’s made no difference.


(Paul Stokes) #13

Well, it seems that my hosting company was right.

I’ve purchased the Superforms stack from One Little Designer and built a stacks page that looks and functions in a similar way to the Rapidweaver template.

It works perfectly, which suggests that the problem lies within Rapidweaver 8. Slightly galling that I’ve had to buy in a stack to replace what is a standard feature of Rapidweaver.


(Jan Fuellemann) #14

@dan should know about this.


(system) #15

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.