This topic has 6 replies, 3 voices, and was last updated 1 months, 1 weeks ago ago by Andrew Mitchell
Hi,
I was trying to use this code for No-break space after thousand number for prices
(otherwise it breaks the Shipping fee and other prices after the thousand, like:
1
690 Ft
and it should be 1 690 Ft)
Can you please correct this code or send one that helps resolve this?
Thank you very much! 🙂
.woocommerce-price-amount {
white-space: nowrap !important; /* Megakadályozza, hogy a szöveg megtörjön */
}
Hello, @creativesite,
Thank you for contacting us and for using XStore.
To assist you more effectively, could you please provide a screenshot of the issue along with the URL of the page where the problem is occurring? This information will enable us to better understand and address your concerns.
Thank you for your cooperation.
Best regards,
The 8Theme Team
Actually, on any pages where the prices need to continue in the next line.
I’ve used this ode but it doesn’t work now:
.woocommerce-price-amount {
white-space: nowrap !important;
}
Hello, @creativesite,
Thank you for your prompt response.
To address your request, kindly add the following custom CSS code by navigating to **XStore > Theme Options > Theme Custom CSS > Global CSS**:
.woocommerce-cart td.product-price.mob-hide {
padding-left: 0px !important;
padding-right: 0px !important;
}
.woocommerce-Price-amount.amount {
white-space: nowrap !important;
}
We hope this solution meets your needs. Should you require any further assistance, please do not hesitate to reach out.
Best regards,
The 8Theme Team
Super, Thank you very much!! 🙂
Dear creativesite,
We trust our theme is enhancing your experience. Taking a brief moment to rate it with a glowing 5 stars on ThemeForest would be immensely appreciated. Your feedback holds significant value for us.
Click here to rate now: https://themeforest.net/downloads
Thank you sincerely for your ongoing support!
Best Regards,
The 8Theme Team
The issue related to '‘No-break space after thousand numbers for prices’' has been successfully resolved, and the topic is now closed for further responses