Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • k3davis: Thanks for looking into this! Here’s what I’ve found, after testing a little more:

    On my “daily” computer ((an Intel Mac) where I frequently log into Google (mostly analytics)):

    • Google Chrome: shows fine, not difference if logged in to Google or not
    • Safari: Same as above.
    • Firefox: Shows google log-in if I’m not logged into Google. If I am logged-into Google it shows fine

    On my WinXP mini laptop

    • IE8: works fine
    • Safari: works fine
    • Firefox: works fine
    • Chrome: Shows google log-in if I’m not logged into Google. If I am logged-into Google it shows fine

    Whadda ya make of that?

    I’ll be happy to share the URL, but the site is in development so I don’t want to go all public. Is there no way to send PMs in wordpress’s forum? (I can’t see it?).
    Can I contact you either by

    Thanks again!

    NB: my pdf is self-stored, no access limitations

    @k3davis: have you tried to go to google and log yourself out before going to a site to view a pdf? (make sure to only have one open browser / browser window)

    At least on my installation that reproduced the problem. I.e. if I’m logged into Google I view pdf’s just fine, but if I’m not logged into Google, I get the sign-in screen too.

    Hope this helps solve the problem – like lots of others, I’d also very much like to use your otherwise fine plug-in…

    Hi sageleader
    I need my users to be able to create usernames of numbers only.

    Just to be sure; did you go FROM THIS:

    function sanitize_user( $username, $strict = false ) {
    $raw_username = $username;
    $username = wp_strip_all_tags($username);
    // Kill octets
    $username = preg_replace(‘|%([a-fA-F0-9][a-fA-F0-9])|’, ”, $username);
    $username = preg_replace(‘/&.+?;/’, ”, $username); // Kill entities

    // If strict, reduce to ASCII for max portability.
    if ( $strict )
    $username = preg_replace(‘|[^a-z0-9 _.\-@]|i’, ”, $username);

    // Consolidate contiguous whitespace
    $username = preg_replace(‘|\s+|’, ‘ ‘, $username);

    return apply_filters(‘sanitize_user’, $username, $raw_username, $strict);
    }

    TO THIS:

    function sanitize_user( $username, $strict = false ) {
    $raw_username = $username;
    /** $username = wp_strip_all_tags($username);
    * // Kill octets
    * $username = preg_replace(‘|%([a-fA-F0-9][a-fA-F0-9])|’, ”, $username);
    * $username = preg_replace(‘/&.+?;/’, ”, $username); // Kill entities
    *
    * // If strict, reduce to ASCII for max portability.
    * if ( $strict )
    * $username = preg_replace(‘|[^a-z0-9 _.\-@]|i’, ”, $username);
    *
    * // Consolidate contiguous whitespace
    * $username = preg_replace(‘|\s+|’, ‘ ‘, $username);
    */
    return apply_filters(‘sanitize_user’, $username, $raw_username, $strict);
    }

    I think it’s related to the recent update! At least it has worked fine for me for months, but after an update to Contact Form 2.0.7 (and WP 2.8.6) it stopped working.

    Internet Explorer / Safari / FF all give error with reference to the javascript in line 100 position 43, i.e. the “eval” in this line:

    jQuery.each(data.onSentOk, function(i, n) { eval(n) });

    Anyone has an idea? Help much appreciated (as I’ve really been defending on ContactForm for download of my free e-book)

    Thanks, Peter / fotoblogger.dk

Viewing 5 replies - 1 through 5 (of 5 total)