Dion Hulse (dd32)
wordpress at dd32.id.au
Sun Oct 9 01:23:02 UTC 2011
I've just tested out your theme and the update API seems to be working
correctly for it for me.
(I installed the latest 2.1.1 version, changed the version in the style.css
to 2.1.0 and reloaded the themes page, and got a notice for it)
The main reason I can think of why you're not getting the alerts, would
simply be due to your version number always matching the latest release or
being up to date already? You'll never see the notice if you've already
updated the theme on the site for testing before the theme was
approved/published on WordPress.org.
On 9 October 2011 12:14, Tom Matteson <perspectivevision at gmail.com> wrote:
> Greetings ...
> I have a theme on the Repository that has been updated a half-dozen times
> or so. My understanding is that WordPress.org runs a cron job twice a day
> that checks all the self installed WordPress installations to query which
> themes, plugins etc are installed. From what I have read the
> theme_update_available function in theme.php is supposed to display '*There
> is a new version of %1$s <http://../../_variables/s.html> available'* *with
> an update url*, whenever there is a new version of the theme, if it
> detects a there is a newer version of any of the installed themes that
> reside in the Repository. Unless I am misunderstanding something, this is
> the default behavior, unless the theme has added some code to bypass the
> this function.
> I have not added any functions to bypass the theme_update_available().
> However, even though I see the update message displayed for other themes, I
> have never seen it displayed for my theme, Wordsmith-Anvil. Does anyone know
> what would cause this function not to work for my theme?
> *Best Regards
> Tom Matteson*
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers