WPIntell

Source evidence

How to Edit the frontend CSS

wePOS – Point Of Sale (POS) for WooCommerce & Dokan · support · 2024-03-18T12:12:00+00:00

wePOS – Point Of Sale (POS) for WooCommerce & Dokan plugin evidence original source source API
questionsentiment
highseverity
0.88relevance
2replies
Evidence onlycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 1 rows with source links

100.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

0 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
cleanpagedesign resolved
Hi there. I’m using WePOS on a mobile and the checkout view is a bit odd. I’d like to make some customisations to it. I’m trying to make some changes to the CSS in my child theme’s styles.css file, but it’s not overriding the default CSS in the plugin. Is there a way to create a copy of the folder structure in my child theme (like you do with templates in WooCommerce) to override the default CSS? Hi @cleanpagedesign , If you are trying to just add some CSS to your site, did you consider using the customizer of your site? May I know the reason why you are trying to add CSS by overriding files? Thanks! Thanks for the reply. I hadn’t thought of using the WP customiser Additional CSS panel. I was putting it into my child theme’s custom.css file. Maybe it was a caching issue, or some badly-written CSS on my part! I’ve now got the changes I wanted.

Comments

2 shown
Jahidul Hassan Mojumder 2024-03-22T10:55:00+00:00

Hi @cleanpagedesign , If you are trying to just add some CSS to your site, did you consider using the customizer of your site? May I know the reason why you are trying to add CSS by overriding files? Thanks!

cleanpagedesign 2024-03-22T14:03:00+00:00

Thanks for the reply. I hadn’t thought of using the WP customiser Additional CSS panel. I was putting it into my child theme’s custom.css file. Maybe it was a caching issue, or some badly-written CSS on my part! I’ve now got the changes I wanted.