• Generally like this plugin, but skinning it has been an absolute b1tch!

    The CSS is too specific for my liking with overly deep CSS selectors. Makes life very hard and should be taken as a lesson in poor CSS specificity.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    Which ones do you feel are do deep? Generally, its required to ‘go deep’ in order to work with the default WordPress themes and prevent them from overriding styles.

    By all means suggest alternatives if you find ways to work across the default themes though: https://github.com/mikejolley/WP-Job-Manager/issues

    OR

    Remove the default styles entirely via your theme functions.php file:

    add_action( 'wp_enqueue_scripts', 'remove_job_manager_styles', 11 );
    
    function remove_job_manager_styles() {
      wp_dequeue_style( 'wp-job-manager-frontend' );
    }

    Then you can just use your own CSS for everything.

    Hope you reconsider your review with the above info. Thanks

    I agree, if he didn’t go that route you would probably end up having overlapping styles which then means things may not format correctly.

    There’s a reason multiple themes have been made that fully support WPJM, and that’s because it’s easily theme-able. Don’t think this specific issue is worthy of only 2 stars

    Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    I don’t think you ever followed up on this. Would be great to get your feedback via github – if we can improve things and make it easier for users in the future thats a win for everyone.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘It's fine… unless you want to reskin it’ is closed to new replies.