WPIntell

Source evidence

Errors on multisite

Specific Files · support · 2011-05-03T15:36:00+00:00

Specific Files plugin evidence original source source API
complaintsentiment
mediumseverity
0.86relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

3 / 31 rows with source links

9.7% 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
Anony Mouse unresolved
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 resource in /wp-content/plugins/specific-files-for-posts-and-pages/specific-files.php on line 435 This is for both css and js admin panels. Obviously this is not going to look good to the network. Any idea on what the issue might be? Thanks. This would only be a problem if WordPress (PHP) does not have the ability to create directories on the server. I’ve tested the current plugin with WordPress 3.1.2 and both subdomain and subdirectory installations, and found no errors. I would check with your host about the permissions for allowing PHP to create directories. In the next version I’ll have a more friendly error message 😉 Thank you. I’ll check that out. Can you verify that the directory ‘specific-files/’ does not exist in ‘wp-content/’? Also check for the two subdirectories ‘css/’ and ‘js/’ in ‘specific-files/’. If they do not exist, you can create them manually and it should work. Also, I looked over the plugin a little today and you actually should be getting a nice error message if the directories do not exist or are not writable. So, I’m a bit confused as to how this could happen. xP

Comments

3 shown
dwieeb 2011-05-19T10:24:00+00:00

This would only be a problem if WordPress (PHP) does not have the ability to create directories on the server. I’ve tested the current plugin with WordPress 3.1.2 and both subdomain and subdirectory installations, and found no errors. I would check with your host about the permissions for allowing PHP to create directories. In the next version I’ll have a more friendly error message 😉

Anony Mouse 2011-05-19T10:29:00+00:00

Thank you. I’ll check that out.

dwieeb 2011-05-19T20:10:00+00:00

Can you verify that the directory ‘specific-files/’ does not exist in ‘wp-content/’? Also check for the two subdirectories ‘css/’ and ‘js/’ in ‘specific-files/’. If they do not exist, you can create them manually and it should work. Also, I looked over the plugin a little today and you actually should be getting a nice error message if the directories do not exist or are not writable. So, I’m a bit confused as to how this could happen. xP