Member Avatar for inzcpa

I have a website called ClippingPathAsia.com. There are 33 errors is showing. I have tried but its tough for me. If you have any tutorial or solution please help me.

  • 2 Contributors
  • 4 Replies
  • 181 Views
  • 1 Hour Discussion Span
  • Latest Post Latest Post by Member #120589

Dani AI

Generated

reported about 33 errors (mostly parse/value errors). That pattern usually means the browser is silently skipping broken declarations rather than loudly failing — the page can still look “mostly right” while chunks of CSS never apply. The quickest first move is to validate the original, unminified stylesheet(s) (not the bundled/minified output) so the validator points to an actual file and line where the parser failed. (developer.mozilla.org)

Practical checklist to narrow the problem:

  • Gather every CSS source: theme style.css, child theme files, plugin CSS, inline styles, and any PHP-generated stylesheets.
  • Turn off concatenation/minification and clear caches; minifiers can hide the true location of the error.
  • Validate each unminified file individually with a standards validator.
  • Run a linter (Stylelint or CSSLint) during development to catch malformed rules and bad values before deployment.
  • Use browser DevTools (Sources/Network/Console) to find which file and line produce ignored or crossed-out rules. (jigsaw.w3.org)

WordPress specifics: styles should be enqueued in functions.php rather than hard-coded. Example (child-theme friendly):

function cpa_enqueue_styles() {
  wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' );
  wp_enqueue_style( 'child-style',  get_stylesheet_uri(), array('parent-style'), '1.0' );
}
add_action( 'wp_enqueue_scripts', 'cpa_enqueue_styles' );

If a stylesheet is produced by PHP, check for stray whitespace or BOM characters before <?php and ensure no accidental PHP output is injected into CSS. (developer.wordpress.org)

Common culprits to inspect: missing semicolons, unmatched braces, unterminated comments, invalid values or units, misplaced @ rules (order matters), and hidden control/BOM characters from copy/paste. For large files, use a binary-search approach (comment out half the file) to isolate the failing block, fix it, then re-run the validator/linter and verify in multiple browsers. (developer.mozilla.org)

Recommended Answers

All 4 Replies

Member Avatar for Member #120589

Are you going to share some of those errors, or do you expect us to visit your site? Is this a ruse to get visitors? :)

Member Avatar for inzcpa

No no no. Please. Most of them are parse error and Value error.

Member Avatar for inzcpa

Have one more issue. HTML5 Conformance Checker.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.