In Accueil - Administration - Store settings - Advanced store settings - Paramètres de paiement

The label is displayed (in french) :

Etape de paiement 'Service d'expédition'

instead of :

Etape de paiement 'Service d'expédition'

(correct value of msgid "Shipping service" in commerce_kickstart-7.x.2.0-beta2.fr.po)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

openskymap’s picture

Title: Localized label is not correctly displayed (&#039 insted of ') » Localized label is not correctly displayed (&#039 instead of ')
bojanz’s picture

Assigned: Unassigned » vasike

Maybe there's an extra check_plain somewhere where it shouldn't be.

vasike’s picture

indeed we have an extra check_plain in "commerce_checkout_pane_settings_title" because of using "@pane" placeholder.
Issue opened on Drupal Commerce : #1777592: Translation issue for Checkout pane settings title

vasike’s picture

Status: Active » Needs work
vasike’s picture

Status: Needs work » Needs review

and there's a commit which includes this patch https://code.drupalcommerce.org/#/c/416/

bojanz’s picture

Status: Needs review » Fixed

Merged.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

RowboTony’s picture

Version: 7.x-2.0-beta2 » 7.x-2.0-rc1
Status: Closed (fixed) » Active
FileSize
32.08 KB
20.56 KB

Hi, this is the closest related issue I could find, I hope it was appropriate to reopen it rather than create a new issue.

I am experiencing this with line items. Other fields such as product_title, and product_display_title are fine and show the apostrophe, but line items are displaying that character as '

title = Cookies 'N Cream Caramels
line item = Cookies 'N Cream Fudge

I'm using Commerce Kickstart rc1, is there anything I can do to fix this in configuration?

vasike’s picture

Status: Active » Closed (fixed)

i'm not sure it's the right place. mayb a new issue will be best.

So it's about Shopping cart block (in Kickstart this block is not enabled).

I enabled and gave a try. but i couldn't reproduce it (tested with RC1 and last dev).

So please open a new issue and provide more details how this could be reproduced?
thank you

RowboTony’s picture

OK, thanks for the quick feedback. I am on 2.x-rc1, but I migrated/upgraded from 1.x, so who knows what sort of cruft may be laying around. I will check this ' issue with my products on a fresh rc1 install to see if I can reproduce it or not, if so then I'll open a new ticket with further details. Thank you, --Tony

RowboTony’s picture

Issue summary: View changes

correction of the way the issue is displayed