Posten Bring AS
Forum Replies Created
-
Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issuev 1.1.52 is now available. Thanks again for reporting the issue
Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueAh yes – understood your remark now. We will include a tiny change that will make the prefix population only trigger if one of our shipping options are selected. New version will most likely be available tomorrow.
Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueThe validation will only trigger if the user has selected a shipping option produced by our plugin, since these requirements only apply when shipments are made via Posten Bring Checkout. If another shipping option (possibly from a different plugin) is selected, the special validation will not be triggered. This is to not interfere with different requirements other shipping plugins/providers might have.
What is the reason you want this to be validated even if another shipping option from a different plugin is selected?- This reply was modified 1 week ago by Posten Bring AS.
Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueAnd btw – we have reported the lack of a proper country code selector as part of the phone number form field several years ago.
https://github.com/woocommerce/woocommerce/issues/48525Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueThanks again for the feedback.
We have identified a couple of UX issues related to how validation errors are presented in some checkout flows, and those will be improved in a future update.
Regarding the international phone number requirement itself, this is an intentional part of the plugin design. The plugin supports multiple Nordic countries with overlapping numbering formats, and shipment notifications / locker-related flows rely on unambiguous phone numbers in international format.
This is particularly important for cross-border Nordic shipments. For example, Danish and Norwegian mobile numbers can share the same local number format, which means an incorrectly interpreted number could result in shipment notifications being sent to the wrong recipient. From both a delivery and privacy perspective, we therefore consider it important to collect the number in an explicit international format during checkout.
Providing the correct phone number at checkout is also important because there is often no reliable way to collect or correct it after the order has been placed and shipment processing has started.
WooCommerce block checkout is also heavily JS-driven by design, so frontend validation logic in that environment is expected and supported.
At the moment we have not been able to reproduce a scenario where orders can consistently be completed with invalid phone numbers in a clean installation, but we will continue monitoring feedback and compatibility reports.
Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueRight – we do observe that the field is not marked correctly in red (which it should), and that the “inline” error message is only displayed with the field when more than one validation error is present in the form. We will fix those, so thanks for pointing that out.
There is validation in js, but that only applies to block based checkouts which already relies heavily on React.js, so this should not cause any issues with caching/optimisation.
Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueInteresting – we are not able to reproduce it in our test environment. Validation works as expected in both shortcode and block based checkouts. It should not be possible to proceed without getting a validation error when order button is clicked unless a valid phone number with country code prefix is provided.
Would it be possible to link to your site so we can examine it?Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueand are you using shortcode or block based checkout?
Forum: Plugins
In reply to: [Posten Bring Checkout] Phone number issueHi Rune and thanks for your feedback.
We know there was problems with the phone number validation similar to what you described in versions up until 1.1.45 where the validation was improved. Could you elaborate on what version you are experiencing this problem with?
Regards
Posten Bring Checkout dev-teamForum: Plugins
In reply to: [Posten Bring Checkout] Max 35 Characters for NameThanks for providing more context. In our experience, based on feedback and interviews with shops having our plugins installed, editing name/address details provided by the customer after the order has been placed is a quite common task. Typically a customer contacts the shop and requests changes to the address or shipping option used, or the data provided by the customer is not valid (non-existing postal codes or similar). Delivering simplicity is great, but having the possibility to edit the customer provided details should maybe be considered a basic feature?
There are many options to explore in Woo to limit or hide editing options, but without knowing more details about your platform it’s hard to provide concrete suggestions. Let us know if you would like us to add hook support for manipulating the recipient name/address used during shipment booking.Forum: Plugins
In reply to: [Posten Bring Checkout] Max 35 Characters for NameWhat platform is this? Is it not using the standard shop manager role?
There are currently no hooks available for altering the recipient name used while booking shipment. It is fetched directly from the details stored with the order shipping address. If this is a show stopper we can of course consider adding a filter hook for this purpose.Forum: Plugins
In reply to: [Posten Bring Checkout] Max 35 Characters for NameHi @pckbtm!
Yes when booking shipping there is a max length requirement for customer names of 35 characters. This is a limitation in the Bring backend systems, and also applies to any shipment booked via mybring.com.
The solution is to have a look at the name provided by the customer. In our experience this is often caused by scenarios where auto-fill has added more than just the name. In such cases you edit the customer name by removing any excess data and try again. If the name length is actually more than 35 characters, one solution could be to use an abbreviation for the first name, e.g. “Petter -> P.”
Regards,Posten Bring Checkout team
Hei,
Statisk frakt fungerer dårlig i kombinasjon med Posten Bring Checkout så lenge du tilbyr Pakke til hentested som fraktalternativ. Statisk frakt innebærer at butikkens adresse vil benyttes når tilgjengelige hentesteder hentes. En kunde som ønsker varen tilsendt til et annet postnummer enn der den sendes fra vil dermed få opp feil hentesteder. Anbefaler dermed at statisk frakt deaktiveres så lenge Posten Bring Checkout er i bruk.
Når det gjelder problemene du nevner med manglende alternativ til postkasse, skyldes dette historisk sett ofte feilkonfigurert vekt/vektenhet på produkter. Dersom en vekt over 5kg kommer inn vil ikke dette alternativet dukke opp. Er det et bestemt produkt dette ofte skjer med? Utfra beskrivelsen over kan det høres ut som det er tilfeldig og kan skje med alle produkter?
Dersom du vet ca når på onsdag dere klaret gjenskape det og hvilket produkt det gjaldt kan vi sjekke om det kan ha sammenheng med vekten.Forum: Plugins
In reply to: [Posten Bring Checkout] Path issues with custom WP_CONTENT_DIR@kimbertelsen A fix has been released with version 1.1.33
Regards,
Posten Bring Checkout teamForum: Plugins
In reply to: [Posten Bring Checkout] Path issues with custom WP_CONTENT_DIRHi @kimbertelsen and thanks for your feedback!
We will look into and come up with a solution shortly. Will keep you posted
Regards
Posten Bring Checkout team