Forum Replies Created

Viewing 15 replies - 31 through 45 (of 96 total)
  • Plugin Author jmviade

    (@jmviade)

    Perfect. Thanks.

    Plugin Author jmviade

    (@jmviade)

    Hi, Dumples,

    It’s very strange because, both processes, recaptcha and span operation have different functions to control them but, it’s possible… I’ll take a Look.
    On the other hand I’ll also take a look to the google’s API because they change it every day…

    Please, send me more details about your installation. Installed plugins, WP version, over all any javascript console message… And I could be fantastic if you send me the URL of your website.

    Thanks,

    Joan Miquel
    PD. By the way, “forced javascript output” option just affects on how the recaptcha field is inserted in HTML code but not in the spam operations.

    Plugin Author jmviade

    (@jmviade)

    Hello, themightyjmac,

    Thanks for your comments. Interessing point of view, other WP distributions…

    So, I’ll review the “fixed admin url” which will be substituted for a dynamic var -most probably- and also the behaviour of the “statusText”, both in the next minor plugin version… In fact, these last days I’m working on it due to the new WP version.

    Best,

    Joan Miquel

    Plugin Author jmviade

    (@jmviade)

    sutuardready,

    I’ve been trying to add a solution that would be able to be generic but it’s not possible so, I take a note of this issue to solve it in the next version of the plugin (…if I can).

    Thanks for your time.

    Joan Miquel
    PD. I’ve closed this incidence but if you have some more information about it, please, don’t hesitate to send it to me.

    Plugin Author jmviade

    (@jmviade)

    In a paralalel line of investigation, I’ve been making some generic searches about ‘IE11 + google Recaptcha’ and, I’m afraid that, independently of the plugin, this behaviour of the recaptcha field is related directly to a IE11 error.

    I found a lot of board messages about this error and some of them propose alternative solutions. I don’t know if they will work however, in next days I’ll try to test them and I’ll tell you something… meanwhiile, take a lock at, per example,

    https://stackoverflow.com/questions/47669463/google-recaptcha-error-in-ie-11
    https://support.google.com/recaptcha/answer/6223838?hl=en

    So, at the end, I’m afraid that it will be difficult to fix it because it is a browser malfunction not a plugin issue… and I’m so sorry.

    Joan Miquel
    PD. I’ll keep this comment as ‘not resolved’ still some days, while you test the other plugins and I try to implement some ‘inspirated’ board message ideas… 🙂

    • This reply was modified 2 years, 8 months ago by jmviade.
    Plugin Author jmviade

    (@jmviade)

    Ok, stuartready, understood. So then, let’s go to the last point.

    Firstly, check if the javascript console of your IE11 has got all javascript event types checked for displaying (code, network, js, css, registry, etc.).

    On the other hand, tell me, please, what happens when you deactivate the plugins one by one (take your time, your visitors are the most important, of course) and what you find out during this process, because, I have not got any other reports about IE11… so that, I need more clues that allow me to help you.

    Additionally, check if your wp theme has defined any special output strategy for the javascript scripts or its code is drived by browser type… It’s not so common but it’s also possible.

    Thanks in advance,

    Joan Miquel.

    Plugin Author jmviade

    (@jmviade)

    Hello, stuartready,

    Really, I’d not had issues related with IE11. It’s the first time so, I supposse that among more than 7000 plugin installations, some other users use this browser and also the visitors of their websites… so that, I suppose that the issue you describes should be related with another element but not with the browser version…

    Therefore, check this list of elements concerned to your installation to find out the true reason of this plugin behaviour.

    0) Check if the plugin has the switch ACTIVE in the ON position.

    1) Check the Google RECATPCHA api pair of keys.

    2) Check the plugin having CLOSED your WP admin session.

    It’s impossible to see the plugin in action if you are logged so, before test it, first, close you your WP admin session. The plugin just works for the ‘NOT logged’ users.

    And, always in a WP NOT LOGGED browser window.

    3) Using the Inspector tool of your browser, please, check if the HTML code of the recaptcha appears but its element, due to theme CSS, has the property display:none.

    4) Using javascript tool of your browser, check if the javascript queries that the plugin uses for locating the HTML ID and FORM elements are truly correct and works. In case of error, go to plugin settings page and change the parameters of these queries.

    5) Finally, principally because you haven’t got any error messages in the javascript console tool, disconnect one by one, your other installed and active plugins to detect some other hidden interferences.

    And please, tell me something about it….

    Thanks in advance,

    Joan Miquel

    • This reply was modified 2 years, 8 months ago by jmviade.
    Plugin Author jmviade

    (@jmviade)

    Thanks for your comment, Antonio Carlos,

    But I’m sorry to say that, this plugin doesn’t generate nor create a website field.

    I suppose that this issue must be related to another theme, plugin or WP update but recaptcha plugin doesn’t interact with website: name="url" in any way.

    In any case, a possible solution for hidding completely ‘website’ field is to add this code inside the functions.php file of your theme

    function my_custom_comment_fields( $fields ){
      if(isset($fields['url']))
        unset($fields['url']);
      return $fields;
    }
    add_filter( 'comment_form_default_fields', 'my_custom_comment_fields' );

    It’s a global filter that works directly over ‘\wp-includes\comment-template.php’ file (line 2220) and serves to select what fields you want show.

    Finally, of course, if I’m wrong, please, send me some other additional information about your configuration, wp version, installed plugins, etc. and I’ll try to find out what could be happening.

    Best,

    Joan Miquel

    • This reply was modified 2 years, 8 months ago by jmviade.
    • This reply was modified 2 years, 8 months ago by jmviade.
    Plugin Author jmviade

    (@jmviade)

    Yes, robhenley, you articulated perfectly because of in my last messages I said that’s I tested that solution and it worked but 1) that it was better to do not modify the core ‘things’ and 2) that was better to wait for the next proposed solution in 4.9.9.

    Thanks a lot, notwithstanding, for this additional explanation.

    Joan Miquel

    Plugin Author jmviade

    (@jmviade)

    Thanks, erikrobles,

    I’ve tested the solucion that’s explained in,

    https://core.trac.wordpress.org/ticket/44832

    modifying directly the wp-embed.min.js and it works perfectly and the console error dissapears.

    Particulary, in the minified code I change this piece of code

     
         if(d.secret||d.message||d.value)
    

    for this piece of code

    
         if(!d||!(d.secret||d.message||d.value))return;
    

    (be carefull, the first one hasn’t got semicolon and the second one has got semicolon)

    However, I do not recommend changing the WP core code in any way, but wait for the final solution proposed for version 4.9.9 wp, above all, if we take into account the last message of the discussion thread,

    @robhenley: “I agree the check should be there but isn’t the issue the generic “message” event that both wp-embed.min.js and Recaptcha’s recaptcha__en.js are using? So receiveEmbedMessage is being called by Recaptcha without the proper arguments.”

    So, be patient, and wait… 🙂

    Thanks, erikrobles for your contribution and your example of code in github.

    Joan Miquel

    • This reply was modified 2 years, 9 months ago by jmviade.
    • This reply was modified 2 years, 9 months ago by jmviade.
    • This reply was modified 2 years, 9 months ago by jmviade.
    • This reply was modified 2 years, 9 months ago by jmviade.
    Plugin Author jmviade

    (@jmviade)

    Hi, erikrobles,

    Please, tell me something more about your installation (the plugin name, other installed plugins, theme, wp version, etc) because I’ve been doing a lot of tests and the plugin works perfectly despite of the console error however I see that’s not your case so I’m sure that there will be any other significant difference.

    Please, help me, to find out what is happening, with just the console error message it’s very difficult to understand where the issue could come from.

    Thanks in advance.

    Joan Miquel

    • This reply was modified 2 years, 9 months ago by jmviade.
    • This reply was modified 2 years, 9 months ago by jmviade.
    Plugin Author jmviade

    (@jmviade)

    Hi, swarups,

    I’m sorry but It seems that there is a mistake because the action ‘google_invre_render_widget_action’ is not inside my plugin.

    Did you spel it correctly?

    Thanks, again.

    Joan Miquel

    Plugin Author jmviade

    (@jmviade)

    Hi, everybody,

    Today’ve been testing all possible scenarios and, as I said, this error is related to the javascript code of Google and not directly with the plugin, in any case, I hope they will correct this error as soon as possible however and, on the other hand, I’ve been testing the plugin again and again and despite this console error log, the plugin works perfectly and checks correctly the comments form so, knowing that it’s always better do not have got any message in console, for the moment you can trust in the plugin, while, we’ll expecting for a new release of google’s javascript code and, of course, I keep investigating for any alternative solution.

    Thanks for your pacience. If I have got any new information, I’ll start a new messages threat.

    Best,

    Joan Miquel Viadé

    Plugin Author jmviade

    (@jmviade)

    Hi, again,

    I’m sorry but the issue is directly related with the javascript code of google generated when its recaptcha module is included in a page.

    To test this, I’ve disconected completely my plugin and I’ve manually included a ‘google recaptcha field’ directly inside a wp_post and I’ve obtained the same error. 🙁

    In fact, this is one of recent documented errors for most of wp plugins and other add-ons that use this external javascript code of google: this one, Contact form 7, etc…

    I’m sorry, I’ll keep investigating, perhaps there is a solution… And, of course, if you have new information about this error, please, feel free to send it to me.

    Thank’s in advance.

    Best regards,

    Joan Miquel

    Plugin Author jmviade

    (@jmviade)

    Hi, nelgarbuzova and dmullanpanda,

    Thanks for the report.

    Google, constantly, is changing its API so… Well, I will check out this issue and I’ll write (or correct) in a couple of days, I hope so. 🙂

    • This reply was modified 2 years, 9 months ago by jmviade.
Viewing 15 replies - 31 through 45 (of 96 total)