Yes, if you absolutely *must* use file operations, then you must use the Filesystem API.<div><br></div><div>Is there any particular reason that your "skins" have to use these sort of files, rather than simply enqueueing CSS files?</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Sun, Mar 18, 2012 at 1:45 AM, Konstantin Obenland <span dir="ltr"><<a href="mailto:obenland@gmx.de">obenland@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Ravi,<br>
<br>
check out Otto's WP_Filesystem Tutorial at <a href="http://ottopress.com/2011/tutorial-using-the-wp_filesystem/" target="_blank">http://ottopress.com/2011/tutorial-using-the-wp_filesystem/</a> and have look at the Codex at <a href="http://codex.wordpress.org/Filesystem_API" target="_blank">http://codex.wordpress.org/Filesystem_API</a>. This should get you going on this :)<br>
<br>
Konstantin<br>
<br>
Sent from my iPhone<br>
<div class="HOEnZb"><div class="h5"><br>
On Mar 18, 2012, at 5:46, // ravi <<a href="mailto:ravi-lists@g8o.net">ravi-lists@g8o.net</a>> wrote:<br>
<br>
><br>
> Hello all,<br>
><br>
> the theme checker that runs on submit returned a fail for my theme due to one WARNING, 3 RECOMMENDATIONS and 6 INFO reports. I had run the plugin myself and assumed that WARNINGs are not grounds for rejections, but it seems that I might have taken the meaning too literally. I am guessing it is the warning for which the theme check failed. The warning is:<br>
><br>
> WARNING: fopen was found in the file functions.php possible file operations.<br>
><br>
> And that’s true. I do read/write files that contain user customisations (which I call “skins”) to my theme. These files are written into the directory WP_CONTENT_DIR/themestore/ahimsa. This choice of directory is based on advise from the wp-hackers list a few years ago (<a href="http://lists.automattic.com/pipermail/wp-hackers/2009-September/027526.html" target="_blank">http://lists.automattic.com/pipermail/wp-hackers/2009-September/027526.html</a>).<br>
><br>
> I am stuck with this setup, and have users out there who are using it to create and use their own “skins”. I cannot, as a result, pull that code out immediately.<br>
><br>
> What’s the way out for me, in this situation?<br>
><br>
> Thank you and regards,<br>
><br>
> —ravi<br>
><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>
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>
</div></div></blockquote></div><br></div>