jmviade

Stephen,

New version 9.0.3 already corrects the versioning schema issue; from 0.0.X.Y.Z to X.Y.Z.

I hope you read this message.

Best,

Joan Miquel

Barbara,

I’m just sending a new version, the 9.0.3, that corrects this issue.

Google has modified the message errors and it has added a new one for duplicated test that didn’t exists because of it was produced fake falses.

In a few hours, I hope the plugins repository will show the new version.

Best regards,

Joan Miquel

Hello Barbara,

I’m already working on it through your first two good clues; Not logged + “Sorry it seems that…” that moves me instantly to the start investigation point.

However, I’ll be very thankfull if you send me more additional information about your WP installation: WP version, PHP version, other installed plugins, the name of your wp theme and above all, the content of the javascript console if it contains any error or notice message; or anything message that appears in the screen if you turn on the debug mode…

Thanks in advance.

Joan Miquel

Thank you for your response, Jeesus.
I’m happy that it’s just a false alarm.
Best regards,

Joan Miquel

Waw!!!! Jeesus,
That’s an amazing issue… It looks like a ghost efect and I do want to solved it so, please, send me more information about your WP installation: WP version, PHP version, other installed plugins, the name of your wp theme and above all, the content of the javascript console if it contains any error or notice message.

Before to advice you any technical strategy or to make some correction I have to find out where the issue would come from.

Thank’s in advance.

Joan Miquel

• This reply was modified 7 years, 10 months ago by jmviade.

It’s not so easy, I’m sorry. because the position of the javascripts files is rellevant however, if you want to test it, I supposse that you could change the wp_enqueue_script() / wp_register_script() functions and to change the parameter “in footer” to false notwithstanding, and sincererly, as wp-footer() is a standard and necessary action, not just for my plugin, else tant most of them use it, I suggest, instead of to modify my plugin, to add this simple line

wp_footer();

in footer.php file or, in general, at the end of the HTML output execution.

In any case, I’ll study this question for futures releases.

Best regards,

Joan Miquel Viadé
PD. With your permision, and if there is not more additions in the next 24 hours, I’ll close the topic. ??

Hello, Orixes,

I’ve been reviewing the HTML code of your site and it looks like if there were not any call to wp_footer() or wp_footer action because there is not any script at the end of the page and all scripts of this plugin are added at the end of the HTML pages.

Please, check if, efectively, the call to get_footer(), wp_footer() or wp_footer action is correctly done, habitualy inside the footer.php file or if in general, the script output at the end of page works properly.

Checking your HTML code, I have seen that

* The output of ‘styles’ of the plugin works properly,
* the id’s configuration is standard,
* There is not any javascript notice or warning in the console

therefore the plugin begins to work but I coudn’t see any script at the end of page.. so I think that the problem is that the call to the wp_footer() is suppressed in your theme.

The last lines of any standard WP footer.php file should be like this…

/*———————————— */

….
….
<?php wp_footer(); ?>
</body>
</html>

/*———————————— */

Please, check these points, check if any other plugin interrupts the front-end execution of wp_footer action and say to me something about it.

Best regards,

Joan Miquel Viadé

Thanks again, Florian.

I’ll begin the tests and I supposse that in a few days, I’ll say you something about it meanwhile, with your permission and if there is not anything else that you want to comment, tomorrow, I’ll close this topic.

??

Best regards,

Joan Miquel Viadé

• This reply was modified 8 years, 1 month ago by jmviade.

Hi, Florian,

Thanks a lot for this report.

The plugin has its own instance of the google javascript calls but… It seems that contact form wants all the control… ??

I’ll really apreciate if you send me some details about the version of the WP and the contact form plugin and any other part of code that you consider relevant in termns of javascript.

In any case, I’ll study this question before launching the next version and I’ll contact with you to explain the results.

For second time, thanks and best regards,

Joan Miquel Viadé

Thank’s Stephen,

Happy new year.

Joan Miquel

Thank’s, Chuckwes.

Best regards,

Joan Miquel

Ok. I see.

I’ve already received your email so, I’m going to close this thread.

In a few days I’ll say you something via e-mail.

Best,

Joan Miquel

Hi Chuckwes,

Good blog, yours. I like it.

I’m sorry but I see the recaptcha field perfectly in your example page…

Think that when you are in a normal website page you just see the recaptcha field if you are non logged, as a common visitor.

The plugin detects the logged users (an admin, per example) and then, it doesn’t show the recaptcha field.

Try again but as a “non logged” visitor and please, tell me something about it.

Best,

Joan Miquel

Thanks Lyngar,

Now, I think that I understand you. I’m working on it.

Please excuse my previous over-cautiousness about the verification function but you will understand that I really needed to know exactly what the settings were, how the environment was working and the purpose of the modification. It’s the verification process!!!!

On the other hand, I did not know the exact configuration of your .htpasswd so I could hardly check all the options properly so, before anything else, I thank you for your patience in responding and showing me the details.

Please contact with me via my website form (www.joanmiquelviade.com) and so, after publishing a new version of the plugin I’ll send you via email a new beta version and if it works (nobody is in a better position to test the beta version than you) I’ll introduce this new option in plugins’s settings panel.

I look forward to your e-mail and, with your permission and if there is not more information that you want to say me in, a couple of days I’ll mark this thread as resolved.

Thank’s in advance.

Joan Miquel

Hello Lyngvar,

Inside the file “recaptcha.js”, the unique point where the plugin uses ‘/wp-admin/admin-ajax.php’ is when it’s verifying the recaptcha field. Exactly, function ‘griwpcVerifyCallback’ (lines 90-109). And a website user never access this rutine.

This rutine is used by a background call after the user fills the recaptcha request. And the background call is always executed in admin mode.

In any case, I tested the plugin in a new and fresh WP installation and when I’ve accessed to the comments form as a disconnected user, the plugin works perfectly.

I’m sorry but I coudn’t find any malfunction in the plugin: “non logged users” can perfectly access to the comments form, uses the recaptcha field and send comments…

Perhaps… I didn’t understand your explanation, if this is the case, please, send me a detailed information about “What do you exactly want to do” with the plugin, what do you exactly need…

Best regards.

Joan Miquel