Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Thanks! That worked a treat!

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    I’ve now tried this. I had to re-activate my original theme and it’s core plugins, as well as a the social media plugin to avoid not just having the site just load all the code as just text. With just these plugins activated, I was able to make the translation on the button work.

    Re-activating the rest of the plugins did not have an impact. The translation on the initial iteration of the button still works. It could have to do with me recently cleaning up MySQL.

    However, it only works when pressing the button once. When it has loaded more posts, it shows the button once again in English. I tried to click the button in translation mode and then translate, but it already has the translation stored, so it doesn’t seems to be separate buttons or translation every time you hit the button. It must be noted that when you hit the “load more” button the site jumps to the bottom of the page. It still loads the posts, but puts me at the bottom of the page, forcing me to scroll up again to see the posts. I was thinking that maybe these two problems could be related, if there’s something broke with the social media plugin itself.

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Hi, thanks for the help, though I wasn’t able to fix the issue. I did find a tab containing “Load More” in the language-files, but nothing changed. I think it’s the same string TranslatePress finds as well. The plug-in providing the instagram feed is Spotlight. I assume some code broke in the plug-in, maybe?

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Update: I checked the “disable dynamic translation” i advanced settings and seemed to have reverted the button and the plugin as a whole back to normal, with english text. However, is there a way to make the norwegian translation work?

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    I did this. Only using the storefront theme and just the woocommerce plugin. If I activated the PayPal-plugin, Stripe cc-fields go narrow.

    However, it seems to be working now with template and all. Perhaps an update sorted things out?

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Der var du nok inne p? noe. Jeg endret template og da lastet den inn, dog ikke helt optimalt, da. Jeg kan ikke lage en egen side og bruke det som mal, da laster den ikke inn riktig lenger. Jeg kan kun bruke eksisterende sider og det ser ikke helt korrekt ut da heller, men det fungerer.

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Ja, jeg lagde en testside for ? sjekke den opprinnelige problemstillingen. Der fungerte alt som det skulle, pussig nok.

    Jeg endret ordre-prefiksen og n? er vi oppe og nikker igjen, dog med den opprinnelige feilen tilbake, da.

    Alts? at man velger ? avbryte og g? tilbake til siden fra Vipps (der hvor du skriver inn tilf nr og betaler).

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Ah, ok.

    Jeg ser disse dukke opp i loggen:

    2020-09-01T13:54:36+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T13:54:52+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T13:56:18+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T13:57:14+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T13:58:27+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T14:02:42+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T14:06:09+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T14:07:42+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T14:08:37+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    2020-09-01T14:16:49+00:00 ERROR Could not initiate Vipps payment 400 orderId is already used, and must be unique

    Antar hver enkelt er for hver gang jeg har fors?kt ? bruke vipps?

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Ny oppdatering. N? vil ikke Vipps fungere i det hele tatt. For bare beskjed om at Vipps ikke er tilgjengelig og at jeg m? pr?ve en annen betalingsform.

    Unfortunately, the Vipps payment method is currently unavailable. Please choose another method.

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Hi

    All I have done is deactivate the Paypal plug-in called: WooCommerce PayPal Checkout Gateway

    What I don’t know is if Paypal still works as normal without it.

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    WooCommerce PayPal Checkout Gateway

    Once this is activated, Stripe breaks. Does Paypal work as normal without this activated? Seems like it. These plugins came with WooCommerce I never installed these separately, but is it so that they were never meant to work at the same time? I assume that this particular PayPal gateway-plug-in is only necessary for credit card purchase through PayPal, but regular payment is ok?

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Hi again

    I have now had help from Avada support and narrowed down the issue. It is the Woocommerce Paypal-plugin that causes the issue. Once I deactivate it. Stripe works. Anyone knows how I can allow both payment options to work at the same time?

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    I see that this morning I got this error message in woocommerce:

    Error: The WooCommerce Services server returned: Unauthorized Invalid token ( 401 ).

    I reached out to Stripe and they said the following: “Upon checking, this error means that the token was not generated properly from woocommerce, you should reach out to them to check what to do next. When users are seeing this error, the most likely root cause is that there’s a Javascript error blocking the Stripe-related code from running on the client side – and therefore it does not not create a Stripe token – but it is still allowing the form to be submitted, and therefore passing this blank value server-side”

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Hi

    Thanks for the reply. Tested out WP-staging, switched to storefront and deactivated all plug ins, except Woocommerce and the plugins related to checkout and stripe. The last two I’ve deactivated and reactivated. The problem persists.

    Thread Starter thomaskirkeberg

    (@thomaskirkeberg)

    Ok. Newbie question, but how do I roll back and what does it entail?
    I can fiddle a little bit with CSS.

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