Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • Thread Starter Sircon Norge AS

    (@sircon)

    Det ser ut som at du er på sporet av noe der, endret til “fri frakt” klassen, men fikk samme feil ved refresh.
    Tømte handlekurv og prøvde å legge inn samme produkt på nytt og gikk til checkout på nytt og da får jeg ikke lengre feil her hos meg.

    Tusen takk for kjapp og god service.

    Thread Starter Sircon Norge AS

    (@sircon)

    Customer tried to buy:
    https://forlagetmarvin.no/produkt/tronderske-turrenn/

    With product shipment settings:

    Thread Starter Sircon Norge AS

    (@sircon)

    2026-01-06T11:48:27+00:00 DEBUG Initiating Checkout session for wooforlaget1977
    2026-01-06T11:49:10+00:00 DEBUG Fant ingen fraktmetoder for Vipps Hurtigkasse - ordren 1977 vil bli mislykket
    2026-01-06T11:49:10+00:00 DEBUG Adressen oppgitt for 1977 var Ole Nordgaards veg 58 TRONDHEIM 7049 NO
    2026-01-06T11:50:15+00:00 DEBUG Fant ingen fraktmetoder for Vipps Hurtigkasse - ordren 1977 vil bli mislykket
    2026-01-06T11:50:15+00:00 DEBUG Adressen oppgitt for 1977 var Ole Nordgaards veg 58 TRONDHEIM 7049 NO
    2026-01-06T12:03:09+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:06:49+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:24:35+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:24:58+00:00 DEBUG Initiating Checkout session for wooforlaget1978
    2026-01-06T12:25:07+00:00 DEBUG Fant ingen fraktmetoder for Vipps Hurtigkasse - ordren 1978 vil bli mislykket
    2026-01-06T12:25:07+00:00 DEBUG Adressen oppgitt for 1978 var KONGENS GATE 110 TRONDHEIM 7012 NO
    2026-01-06T12:26:55+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:31:29+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:35:52+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps pending
    2026-01-06T12:35:52+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:41:04+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps pending
    2026-01-06T12:41:04+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:43:08+00:00 DEBUG Initiating Checkout session for wooforlaget1980
    2026-01-06T12:45:51+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps pending
    2026-01-06T12:45:51+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps pending
    2026-01-06T12:49:23+00:00 DEBUG Initiating Checkout session for wooforlaget1981
    2026-01-06T12:49:55+00:00 DEBUG Initiating Checkout session for wooforlaget1982
    2026-01-06T12:50:50+00:00 DEBUG Vipps MobilePay poll: Handling order: 1981
    2026-01-06T12:50:51+00:00 INFO Cannot expire checkout session for order 1981: 409 Array
    (
    [title] => Cannot expire session that is not in state SessionStarted
    [status] => 409
    [instance] => urn:uuid:e195bc73-6e19-4b80-a99a-e6c597b533db
    [errorCode] => Session-00105
    )
    urn:uuid:e195bc73-6e19-4b80-a99a-e6c597b533db
    Session-00105
    2026-01-06T12:50:51+00:00 INFO Callback received
    2026-01-06T12:50:51+00:00 DEBUG Received webhook callback for order wooforlaget1981 but this is no longer pending.
    2026-01-06T12:50:51+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps pending
    2026-01-06T12:50:52+00:00 DEBUG Vipps MobilePay poll: Handling order: 1977
    2026-01-06T12:50:52+00:00 DEBUG For ordre 1977 er ordrestatus hos Vipps cancelled
    2026-01-06T12:50:56+00:00 INFO Callback received
    2026-01-06T12:55:53+00:00 DEBUG For ordre 1980 er ordrestatus hos Vipps pending
    2026-01-06T12:55:53+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps pending
    2026-01-06T13:12:26+00:00 DEBUG For ordre 1982 er ordrestatus hos Vipps pending
    2026-01-06T13:12:26+00:00 DEBUG For ordre 1980 er ordrestatus hos Vipps pending
    2026-01-06T13:12:26+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps pending
    2026-01-06T13:24:55+00:00 DEBUG For ordre 1982 er ordrestatus hos Vipps pending
    2026-01-06T13:24:55+00:00 DEBUG For ordre 1980 er ordrestatus hos Vipps pending
    2026-01-06T13:24:55+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps pending
    2026-01-06T13:28:48+00:00 DEBUG For ordre 1982 er ordrestatus hos Vipps pending
    2026-01-06T13:28:48+00:00 DEBUG For ordre 1980 er ordrestatus hos Vipps pending
    2026-01-06T13:28:48+00:00 DEBUG Vipps MobilePay poll: Handling order: 1978
    2026-01-06T13:28:49+00:00 DEBUG For ordre 1978 er ordrestatus hos Vipps cancelled
    2026-01-06T13:31:33+00:00 DEBUG For ordre 1982 er ordrestatus hos Vipps pending
    2026-01-06T13:31:33+00:00 DEBUG For ordre 1980 er ordrestatus hos Vipps pending
    2026-01-06T13:35:52+00:00 DEBUG For ordre 1982 er ordrestatus hos Vipps pending
    2026-01-06T13:35:53+00:00 DEBUG For ordre 1980 er ordrestatus hos Vipps pending
    2026-01-06T22:40:59+00:00 DEBUG Initiating Checkout session for wooforlaget1983
    2026-01-06T22:43:44+00:00 INFO Callback received
    2026-01-06T22:43:44+00:00 DEBUG Mottok webhook-callback for checkout-ordre 1983 - ignorerer fordi en fullstending callback skal komme
    2026-01-06T22:43:44+00:00 DEBUG Vipps MobilePay poll: Handling order: 1983
    2026-01-06T22:43:49+00:00 INFO Callback received

    There are no fatal errors, and no warnings/notices that seem relevant.

    Thread Starter Sircon Norge AS

    (@sircon)

    Like any of these ?

    Thread Starter Sircon Norge AS

    (@sircon)

    More verbose information about error:

    “Levering til oppgitt adresse er ikke støttet.
    Vennligst prøv en annen adresse. (Feilkode: Logistics-00101)”

    Translated to english:
    “Delivery to given address is not supported.
    Please try another address. (Errorcode: Logistics-00101)”

    Thread Starter Sircon Norge AS

    (@sircon)

    Everything looks to be in perfect order now 🙂

    Thanks.

    Thread Starter Sircon Norge AS

    (@sircon)

    Opened a support ticket about this, and this is fixed in upcoming version.

    Punxsutawney Phils error report is not very informative, so forgive me if this is not related.

    The plugin does indeed seem to be broken in some fashion, with the following versions:
    – WordPress 4.1
    – Cf7 4.1.1
    – CF7 modules: Hidden Fields v 1.4.2

    The problem becomes apparent inside the control panel:
    1 Try to reach “/wp-admin/admin.php?page=wpcf7”
    2 Loads for a very long time. (45 seconds in my case)
    3 Try to edit a form
    4 Loads for a very long time, again. (45 seconds again)
    5 Add custom hidden field and save form
    6 Loads for a very long time, again. (strangely – 45 seconds)
    7 Form seems to be rendered correctly, with the hidden fields.

    Disabling the “CF7 modules: Hidden Fields” makes editing forms reachable again.

    Hello,

    We are experiencing a serverwide slowdown because of one website using this plugin on a shared hosting server.
    This one website is requiring more resources than the rest of the websites combined.

    Update on this source-code-“fix”:
    – “Add media” button popup shows nothing
    – Media library shows something, only the first x images, and keeps querying with ajax for more images. This constantly repeating ajax request keeps failing
    – Media library search works really bad, if at all
    – Adding in the fix mentioned above seems to work where the media library shows no or just some images.
    – The fix mentioned above does not break anything else (so far..!)

    So there you have it, no reponse from the dev, no updates, which is a shame, because I am one webdev that enjoys this plugin for what it does.

    I’m having a problem now in
    – WP v4.0
    – Simple custom post order v2.2

    Media library shows NOTHING. Warnings in the ajax response, loads of them:
    “Illegal string offset ‘width'” etc..

    :: Possible fix, seems to work for my case ::
    Find the file “wp-content/plugins/simple-custom-post-order/simple-custom-post-order.php”
    Ca line 290 you will see the following:

    } else {
    
    $active = false;

    Change it so it looks like this:

    } else {
    /* Sircon attempts to fix media library */
    if(defined( 'DOING_AJAX' )){
     return $wp_query;
    }
    /* Attempted fix complete*/
    
    $active = false;

    I just saw this on a WordPress with Nextgen Gallery v 2.0.14.
    I also found the source of the problem for this particular case, which came from WordPress settings-> general settings.

    These settings made the error occur:
    WordPress Address (URL) http://websiteaddress.com
    Site Address (URL) http://www.websiteaddress.com

    After changing them, the error was gone and images uploaded perfectly. The correct settings for this case was to add www to WordPress address as well:
    WordPress Address (URL) http://www.websiteaddress.com
    Site Address (URL) http://www.websiteaddress.com

    Keep up the great work with NextGen, you are still much loved!

    Another problem:
    – Widget, black studio tinyMCE, is now stuck in html-view. Error in chrome console when editing a tinymce widget: “Uncaught ReferenceError: tinyMCE is not defined”.

    Disabling ckeditor plugin makes this widget work again.

    The settings were set to Kama, which was broken as described.
    Moono, on the other hand, looks very much functional! 🙂 Very good, and thank you!

    Testing the ckeditor-for-wordpress.4.0.zip given on page 1, I find that the editor is now visible and text is editable again.
    I haven’t tested every button and function yet, but all of the editor buttons now have no image or the wrong image.
    Example: “Bold” button has title “Bold” and the image for “Remove formatting”. The “italic” button has the image for “Insert new column”. They still work for setting text to bold and italic though.

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