Darren ... the first one switched to using a different theme because they could not resolve this. However, his WordPress installation was in a subdirectory (see the errors below **with the user's domain and subdirectory edited**) I do know the first user's site was hosted by surpasshosting dot com and per their security settings they would not enable allow_url_fopen ... other than that I am unaware of their php.ini settings<br>
<br><br>Warning:<br>fopen(<a href="http://primarydomain.com/sub-directory/wp-content/themes/wordsmith-anvil/style.css">http://primarydomain.com/sub-directory/wp-content/themes/wordsmith-anvil/style.css</a>)<br>[function.fopen]: failed to open stream: no suitable wrapper could be<br>
found in<br>/home/primaryd/public_html/sub-directory/wp-includes/functions.php on line<br>4284<br><br>Warning: fread(): supplied argument is not a valid stream resource in<br>/home/primaryd/public_html/sub-directory/wp-includes/functions.php on line<br>
4287<br><br>Warning: fclose(): supplied argument is not a valid stream resource in<br>/home/primaryd/public_html/sub-directory/wp-includes/functions.php on line<br>4290"<br><br>One thing I had read somewhere is that using absolute paths (direct links) as opposed to relative paths could cause these errors to appear. In the Wordsmith Anvil theme the only direct links are:<br>
<br><ul><li>Developer and WordPress.org credit links (common with most all themes)</li><li>Link to FAQ and Theme Home page in Admin Theme Options Page (fairly common)</li><li>Various license links (common with all themes)</li>
<li>Direct links assigned to Social Media variables for Twitter, FB, Flickr, YouTube ...[eg $flickrurl = '<a href="http://www.flickr.com/photos/'">http://www.flickr.com/photos/'</a>;] (common to themes with these options)</li>
</ul><br>The second user's site is hosted with <a href="http://secureserver.net">secureserver.net</a> (there apparently have been some errors with that host server and WordPress in the past see: <a href="http://wordpress.org/support/topic/defaultsecureservernet">http://wordpress.org/support/topic/defaultsecureservernet</a>)<br>
<br>The errors on the second user's site were the same. The user has currently deactivated the theme and has an under construction page displayed. I have emailed her to ask that she re-activate to get addtional feedback. I imagine it will be re-activated at some point today. For reference, the url to that site is: <a href="http://homesweethomerescue.org/">http://homesweethomerescue.org/</a><br>
<br>As I discover additional details I will provide them.<br><br clear="all"><b style="color: rgb(0, 102, 0);"><span style="font-family: trebuchet ms,sans-serif;">Best Regards</span><br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">Tom Matteson</span></b><br style="font-family: trebuchet ms,sans-serif;"><span style="font-family: trebuchet ms,sans-serif;"></span><span style="font-family: trebuchet ms,sans-serif;">---------------------------------------------------------------------------------------</span><br>
<br><br><div class="gmail_quote">On Sat, Jul 16, 2011 at 12:37 PM, Darren Slatten <span dir="ltr"><<a href="mailto:darrenslatten@gmail.com">darrenslatten@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
This would be a lot easier to diagnose if you could provide information like:<br><ul><li>hosting environment</li><li>php.ini settings<br></li><li>full text of error messages</li><li>what types of pages/requests generate the errors<br>
</li></ul>If the errors are only showing in 2:10,000 installations, then there's a good chance that those 2 users have an unusual server configuration or file/URL structure. Could be caused by something like trying to open/include a file or image that isn't in the typical location, relative to your theme.<br>
<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Sat, Jul 16, 2011 at 3:47 AM, Tom Matteson <span dir="ltr"><<a href="mailto:perspectivevision@gmail.com" target="_blank">perspectivevision@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">
Greetings All Concerned ...<br><br>I have a theme on the Repository--Wordsmith Anvil--which does not use fopen, fgets or freads functions. It has been downloaded close to 10,000 times and I have just received a comment from the second user who is receiving errors referencing "failed to open stream: no suitable wrapper could be found in ...", or "supplied argument is not a valid stream resource in ..." with this theme. The errors all point to various lines of wp-includes/functions.php, except one file reference to the theme default css file, style.css. The first user told me they disabled all plugins. Also, they performed a fresh WordPress install and did not see the errors using TwentyTen and a number of other themes. The second user who contacted me yesterday told me they do not have any plugins installed and when they activated the Wordsmith Anvil theme, these errors display at the top of the page. <br>
<br>Knowing that these functions are not used in this theme; yet the errors seem to be theme specific, and each user experiencing these errors have WordPress installations hosted on entirely different servers I am more uncertain as to why these errors are being displayed. I was hoping someone on this list may have experienced this with another theme and could shed some light on why these errors would occur when the theme does not use those functions. In fact, if these functions had been used in my theme, I am fairly certain it would not have been approved anyway. <br>
<br>Otto, Nathan, Chip, Justin, Emil, Cais, etc ... any thoughts or feedback on this. I would like to address this so that users in the future do not see these errors.<br><br clear="all"><b style="color: rgb(0, 102, 0);"><span style="font-family: trebuchet ms,sans-serif;">Best Regards</span><br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">Tom Matteson</span></b><br style="font-family: trebuchet ms,sans-serif;"><span style="font-family: trebuchet ms,sans-serif;"></span><span style="font-family: trebuchet ms,sans-serif;"></span><span style="font-family: trebuchet ms,sans-serif;"><br>
</span><br>
<br></div></div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><font color="#888888">Darren Slatten<br><br>
</font><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br>