In this case, it's less a true "generator" as it is merely a template pack that includes six different layout templates - and one that hasn't been updated functionally in a VERY long time.<div><br></div><div>
It doesn't look like anything nefarious; just outdated code with a repository-incompatible license.</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, Oct 28, 2010 at 1:47 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Print.css is definitely a common name, I use it all the time for my<br>
printer-stylesheets.<br>
<br>
To detect things like this, you're better off looking for naming<br>
schemes or unique styles of the code. Generated themes are template<br>
driven, so they tend to have very similar code from theme to theme.<br>
That's more likely to be recognizable. Searching for a byline or<br>
something isn't reliable, because it's the first thing they'll change.<br>
<br>
Simon: I've been updating the theme check stuff today, adding all<br>
sorts of things. Forward me whatever you have and I'll work it in too.<br>
I'd like to get this thing implemented on the uploader.<br>
<font color="#888888"><br>
-Otto<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
On Thu, Oct 28, 2010 at 1:37 PM, Edward Caissie<br>
<<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:<br>
> The only thing I see with a quick look through the SVN is that both style<br>
> sheets (style and print) have this line:<br>
><br>
> License info can be found at <a href="http://www.wpthemerkit.com/license.php" target="_blank">http://www.wpthemerkit.com/license.php</a><br>
><br>
><br>
><br>
><br>
> Maybe, if you can look for file_exist( print.css ); then inside it for that<br>
> line or even the partial link URL ...<br>
><br>
> Although print.css could be a common file, I don't see them wanting to<br>
> remove that line of text; at least not until they catch on.<br>
><br>
> Just a thought.<br>
><br>
> On Thu, Oct 28, 2010 at 2:28 PM, Simon Prosser <<a href="mailto:pross@pross.org.uk">pross@pross.org.uk</a>> wrote:<br>
>><br>
>> On 10/28/2010 07:24 PM, Edward Caissie wrote:<br>
>> > I'm surprised there are not more of these "generators" ... or maybe<br>
>> > there are and we are just seeing the ones that are leaving these<br>
>> > breadcrumbs behind.<br>
>> ><br>
>> > Good catch!<br>
>> is there any function or something we can search for like with the<br>
>> artisteer themes? so i can add a check for it?<br>
>><br>
>> --<br>
>> My Blog : <a href="http://www.pross.org.uk/" target="_blank">http://www.pross.org.uk/</a><br>
>> Plugins : <a href="http://www.pross.org.uk/plugins/" target="_blank">http://www.pross.org.uk/plugins/</a><br>
>> Themes : <a href="http://wordpress.org/extend/themes/profile/pross" target="_blank">http://wordpress.org/extend/themes/profile/pross</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>
><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>
><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>