150d

Yes, I had already noticed the link. But thanks for the hint anyways.

This will bring you to the main menu – but if you haven’t completed those startup questions, you still can’t select what you want: It wouldn’t allow me to select the few options I needed without applying a full set of defaults – which I absolutly didn’t want to do. I rather deleted the plugin and moved on. 🙁

• This reply was modified 4 years, 3 months ago by 150d.
• This reply was modified 4 years, 3 months ago by 150d.

Hi again,

Sorry, but I have to come back on this once more:

My provider told me that the error I’ve been getting from my wget-test referred to missing parameters on the URL and/or unspecified methods (get/post). This makes sense, because a normal request will surely transmit at least the Google API-key in some way, probably as part of the URL. In any case, I get a similar error if I try the wget at home – indicating that this isn’t the problem on my server after all.

Additionally, as I just noticed the behaviour on my WordPress-site has changed: Before, the “send” button simply did nothing. Now, the message “Please solve the recaptcha to continue.” appears. This is after the reCAPTCHA has already been marked with a green check mark, indicating a successful answer.

Can I get some sort of debug log from the plugin?

Regards

PS: To make matters worse – I just tried a different contact form plugin, and it worked there. So it actually seems to be a problem with CaSCF after all.

Hi,

indeed: It’s hard for me to debug this (shared hosting with limited features), but I can get this result on a console:

[code]
> wget https://www.google.com/recaptcha/api/siteverify
--2015-09-07 12:00:02-- https://www.google.com/recaptcha/api/siteverify
Resolving http://www.google.com... 173.194.116.180, 173.194.116.179, 173.194.116.176, ...
Connecting to http://www.google.com|173.194.116.180|:443... connected.
ERROR: cannot verify http://www.google.com's certificate, issued by /C=US/O=Google Inc/CN=Google Internet Authority G2:
Unable to locally verify the issuer's authority.
To connect to http://www.google.com insecurely, use --no-check-certificate.
[/code]

So it seems clear, the server can’t verify Google’s SSL certificate.

Can you venture a guess as to why? Is this Google’s fault or my provider’s?

Regards

Ok, I did both, without anything changing for the better. (For the plugin install, I simply switched the old for the new directory – there are no old files to keep, right?)

I just looked into the database. In table wp_ngg_gallery I found this:

The galleries that show the error have the field “author = x”.
The galleries that do not show the error have “author = y”.
(Not wanting to give away any secrets here, so let’s keep it at “x” and “y”… 🙂

This gave me an idea: The “bad” galleries are all old ones. For quite some time I’m using iThemes Security. One of its functions is to change user IDs for admin users. Could it be that “x” is the user ID before the change, and “y” is the ID after the change? NextGen wouldn’t be able to locate any user “x”, that’s why it shows an error.

Can I just modify the said records in the database “x”->”y” without side effects?

Regards