WPIntell

Source evidence

__DIR__ throws errors

Post Type Icons · support · 2014-01-22T19:44:00+00:00

Post Type Icons plugin evidence original source source API
mixedsentiment
highseverity
0.88relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

4 / 32 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
PaulMighty resolved
Activated the plugin and navigated to Tools > Post Type Icons and found the following errors that prevented the page from loading: Notice: Use of undefined constant __DIR__ – assumed ‘__DIR__’ in [my website]/wp-content/plugins/post-type-icons/post-type-icons.php on line 66 Warning: require_once(__DIR__/font-awesome/class-pti-font-awesome.php) [function.require-once]: failed to open stream: No such file or directory in [my website]/wp-content/plugins/post-type-icons/post-type-icons.php on line 66 Fatal error: require_once() [function.require]: Failed opening required ‘__DIR__/font-awesome/class-pti-font-awesome.php’ (include_path=’.:/Applications/MAMP/bin/php/php5.2.17/lib/php’) in [my website]/wp-content/plugins/post-type-icons/post-type-icons.php on line 66 -PaulMighty http://wordpress.org/plugins/post-type-icons/ Resolved by replacing two instances of __DIR__ with dirname(__FILE__), as suggested here: http://stackoverflow.com/questions/14653947/php-5-2-notice-use-of-undefined-constant-dir-assumed-dir -PaulMighty This is also resolved in the latest version of the plugin.

Comments

2 shown
PaulMighty 2014-01-22T19:46:00+00:00

Resolved by replacing two instances of __DIR__ with dirname(__FILE__), as suggested here: http://stackoverflow.com/questions/14653947/php-5-2-notice-use-of-undefined-constant-dir-assumed-dir -PaulMighty

Matthew Boynes 2014-04-20T07:46:00+00:00

This is also resolved in the latest version of the plugin.