ClubDesign

Huh?

Does it generate a new token when you add the second card?

Greets

function stripeResponseHandler ( status, response ) {

        $( '.stripe_token, .payment-errors' ).remove();

        if ( response.error ) {
            $stripeform.before( '<span class="payment-errors required">' + response.error.message + '</span>' );
            $('#place_order').prop('disabled', false);
        } else {
            $form.append( '<input type="hidden" class="stripe_token" name="stripe_token" value="' + response.id + '"/>' );
            $('#stripe-card-number').val('');
            $('#stripe-card-expiry').val('');
            $('#stripe-card-cvc').val('');
            $form.submit();

        }
    }

    function validateCardForm ( stripedata ) {
       var errors = validateCardDetails( stripedata ); 

        $( '.stripe_token, .payment-errors' ).remove();

        if ( errors.length ) {

            if(errors.length > 0){
                for(var i = 0, l = errors.length; i < l; i++){
                    $stripeform.before('<label class="payment-errors required">' + errors[i] + '</label><br class="payment-errors">') ;
                }
            }
           // $form.append( '<input type="hidden" class="form_errors" name="form_errors" value="1">' );
            return false;
        }
        else
        {
            $form.find( '.woocommerce-error' ).remove();
            return true;
        }
    }

i moved $( ‘.stripe_token, .payment-errors’ ).remove(); up out og the if statement in validateCardForm!
But you could do it in both i think.

ad multilingual error messages, just add a filter before you create the notice with wc_add_notice, the filter should get the error code and error message, then anybody can rewrite the error messages!

Do you have a github repo? i could add PRs if you want.

PS: I didn`t even know that there is a pro version! ??

Greets

Hi,

ok i tried it right now (couldn`t wait) and it works smoothly with the development version! Great News!

Greets Marcus

Hi,

ok i`ll try it when i am at the office and tell you the results!

Greets

Hey, thanks for the five stars! But did you know, that the plugin DOES copy the chosen background into your media library and does NOT load it from anywhere else? So the efficiency is not blocked in any way!
When a not logged in user visits your site, the plugin doesn`t even load anything.

Just for Info!
Greets!

I don`t know exaclty what you mean…?

Ok, basically you cannpt connect to Gihub to fetch the patterns. As an explanation: I am using the built-in wp_remote_get function of WordPress (https://codex.www.ads-software.com/Function_API/wp_remote_get) to fetch the patterns. That function tries some different methods to connect to Github and send the request. In your case it seems that this function returns an WP Error and because i don`t check for errors in this part of the script you get this output.

I will implement an error checker in the next version, but basically that doesnt change anything for you, as your server simply cant connect to Github.

Maybe recheck your php settings?

Greets

Thx for the feedback, but i don`t really get the sense of your request?! Who wants a different background on every page?

And, you guessed it correctly, that won`t work because the files have to be imported first..

Greets

Seems no general problem as it`s working on all my sites. Tell what the console says.

Kind of weird behavior. No Error Message?

What does the console say? Any JS errors?

Greets

I didn`t test the plugin in multisites. Basically on saving the plugin checks if the user has the capability edit_themes. If not, then you are rejected. Maybe there is some difference in handling that in a multi site network. If someone comes up with a solution, please post it here, as i a mnot usign Multisites…

Greets

Invalid Request means that your logged in user is not allowed to edit themes, so the script doesn`t save the background.

Greetz

Good to hear srumery…

Time to give it a 5 star vote…;)

Thx for the fixes kraterdesign, will be added in upcoming version…

My guess were the PHP short tags on srumery`s problem.

Fixed in 1.2!