specific-files-for-posts-and-pages
Specific Files
This plugin allows you to include CSS or JS files in specific posts and pages.
Proof Health
Open evidenceCommercial opportunities need traceable source links before they are treated as build-worthy.
62.3% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Related Opportunities
4 marketsSource Evidence
Open evidence explorer[Plugin: Specific Files for Posts and Pages] Does This Work with Custom Post Types?: users show bugs, missing feature, setup pain that may indicate a product gap.
Buyer: developers, agencies, and technical site owners · Wedge: preflight CSS code changes, compatibility risks, rollback paths, and debug evidenceErrors on multisite: users show bugs, compatibility, setup pain that may indicate a product gap.
Buyer: developers, agencies, and technical site owners · Wedge: preflight CSS code changes, compatibility risks, rollback paths, and debug evidenceheaders already sent and wp_enqueue_script was called incorrectly: users show bugs, support pain that may indicate a product gap.
Buyer: developers, agencies, and technical site owners · Wedge: preflight CSS code changes, compatibility risks, rollback paths, and debug evidence[Plugin: Specific Files] Using Quick Edit deselects all specified files in post: users show bugs pain that may indicate a product gap.
Buyer: developers, agencies, and technical site owners · Wedge: preflight CSS code changes, compatibility risks, rollback paths, and debug evidenceInline edit boxes not saving code: users show bugs pain that may indicate a product gap.
Buyer: developers, agencies, and technical site owners · Wedge: preflight CSS code changes, compatibility risks, rollback paths, and debug evidenceLoad css with @media queries doesn't work.: users show bugs, support pain that may indicate a product gap.
Buyer: developers, agencies, and technical site owners · Wedge: preflight CSS code changes, compatibility risks, rollback paths, and debug evidenceWorks great: users praise easy, reliable, quality, which suggests what competitors already do well.
Buyer: developers, agencies, and technical site owners · Wedge: preflight CSS code changes, compatibility risks, rollback paths, and debug evidenceCompetitor Context
16 shownRepeated Themes
0 shownNo repeated plugin-level themes have been generated yet.
Collected Signals
7 shown from 7 collectedheaders already sent and wp_enqueue_script was called incorrectly: users show bugs, support pain that may indicate a product gap.
Evidence: headers already sent and wp_enqueue_script was called incorrectly hello, i am getting the issues with the latest version of the plugin.Inline edit boxes not saving code: users show bugs pain that may indicate a product gap.
Evidence: Inline edit boxes not saving code When trying to add inline css or js code via the pop-up light boxes, when they are closed, the code is not saved and the inline box becomes unusable.Load css with @media queries doesn't work.: users show bugs, support pain that may indicate a product gap.
Evidence: Thank you in advance if you can help me.Works great: users praise easy, reliable, quality, which suggests what competitors already do well.
Evidence: Works great Very simple and clear way for adding JS script file only in specific pages or posts.Errors on multisite: users show bugs, compatibility, setup pain that may indicate a product gap.
Evidence: Errors on multisite I’m seeing the following errors on a sub directory multisite install: Warning: opendir(/wp-content/specific-files/css) [function.opendir]: failed to open dir: No such file or directory in /wp-content/plugins/specific-files-for-posts-and-pages/specific-files.php on line 427 Warning: closedir(): supplied argument is not a valid Directory re[Plugin: Specific Files] Using Quick Edit deselects all specified files in post: users show bugs pain that may indicate a product gap.
Evidence: [Plugin: Specific Files] Using Quick Edit deselects all specified files in post Hi, I noticed that if you use Quick Edit instead of Edit, all the CSS and JS files you’d selected before become deselected.[Plugin: Specific Files for Posts and Pages] Does This Work with Custom Post Types?: users show bugs, missing feature, setup pain that may indicate a product gap.
Evidence: http://wordpress.org/extend/plugins/specific-files-for-posts-and-pages/ Hi, Right now it does not work with any post type other than page or post.