<div>Alright.. Figured it out.. even if it took me a good 45minutes flipping back and forth between your site, the API code, and scratching my head!<br></div><div><br></div><div>The root cause of it is: You've got multiple Themes called 'WordSmith Anvil' on the installs in question.</div>
<div><br></div><div>Longer answer: WordPress includes a "Trump Card" system, whereby, if a theme attempts to use a name which has already been used by another theme on the site, the theme name gets suffixed with the theme directory. As a result, the theme update API is receiving a request looking for a theme called 'WordSmith Anvil/wordsmith-anvil' with a slug of 'wordsmith-anvil'.. Now, the Themes API doesn't know about that title.. and since it requires an exact match on both the Title and the Slug, it'll never respond with an update for that particular theme.</div>
<div><br></div><div>Take the other copy of the theme though, the one which WordPress read first and which took the "WordSmith Anvil" title, Well, it has a slug of "wordsmith-anvil-theme-1.2.1" and once again, which the update API doesn't know about (since it needs both the Title and Slug to match) will not receive an update either!</div>
<div><br></div><div>Finally.. You might now question why you don't see the "WordSmith Anvil/wordsmith-anvil" title shown anywhere in the Admin.. Well, WordPress knows that that title isn't meaningful to you, so uses the raw Title instead of the "Name" (WordPress internally refers to themes by the unique "Name" rather than the directory slug for historical reasons).</div>
<div><br></div><div>I'm not sure what can be done about this for the update API, It's entirely possible to work around it, but introduces issues on the client side (the wrong copy of the theme might be upgraded) and isn't a situation that 99% of users would ever come across.</div>
<div><br></div><div><br></div><div><strong>tl;dr:</strong> If you have multiple themes with the same name on a WordPress blog, There is a high chance that the updates will not be notified about, due to the internal name not matching the theme title (that the update API uses).</div>
<div><br></div><div>D</div><div><br></div><div class="gmail_quote">On 9 October 2011 21:44, Tom Matteson <span dir="ltr"><<a href="mailto:perspectivevision@gmail.com">perspectivevision@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Otto ...<br><br>Thx for pointing that out. Now that you mention it, that is what I recall having read. In fact, I think it was probably a post of yours I had read. Clearly, it makes more sense that each install will call home; rather than WP calling out to millions of installs. That, of course, would not be practical. <br>
<br>That being said, I am still trying to figure out why on my installs, the theme_update_available function seems to be getting bypassed or timing out only for my theme. At least it was reassuring to hear, per Dion, the update message appears to be displaying for this theme on other installs. I have addressed a couple other issues that were brought to my attention in this thread. However, I am not sure if any of those changes will have any impact the the function and the display of the update message. However, it has been less than 12 hours since I made these changes. <br>
<br>Thx to everyone that has responded.<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"><font color="#888888"><span style="font-family:trebuchet ms,sans-serif">Tom Matteson</span></font></b><div>
<div class="h5"><br style="font-family:trebuchet ms,sans-serif">
<span style="font-family:trebuchet ms,sans-serif"><br></span><br>
<br><br><div class="gmail_quote">On Sat, Oct 8, 2011 at 9:41 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.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">
On Sat, Oct 8, 2011 at 8:14 PM, Tom Matteson<br>
<<a href="mailto:perspectivevision@gmail.com" target="_blank">perspectivevision@gmail.com</a>> wrote:<br>
> My understanding is that WordPress.org runs a cron job twice a day that...<br>
<br>
No. Your own WP install runs its check, then stores the results in a<br>
transient with a 12 hour expiration time.<br>
<br>
So, if you just checked, and then change things around, it won't check<br>
again for another 12 hours. This is controlled by your system, not<br>
ours.<br>
<font color="#888888"><br>
-Otto<br>
</font><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>
</div></div></blockquote></div><br>
</div></div><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>