Dion Hulse (dd32)
wordpress at dd32.id.au
Sun Oct 9 02:08:26 UTC 2011
It doesn't do any user tracking, nor does it care about where you're
Try changing the version string on one of those sites to a older version,
and reloading the themes page, see if it picks it up then?
The other thing that comes to mind, is if all the servers you're testing on
are on a slower network, the update checks might be timing out, so it's only
the once-ever-24hrs check that waits longer for a response that's working,
and so not picking up the updates..
Assuming everything else is working, there's not much else that can be
impacting upon it (except maybe a plugin..). If you've got a test install
you don't mind letting me run a few debug items on, I can give you an exact
reason why the alert isn't showing for you. (contact me off-list)
FYI, I'm getting this warning on 3.3:
( ! ) Notice: wp_enqueue_script was called incorrectly. Scripts and styles
should not be registered or enqueued until the wp_enqueue_scripts,
admin_enqueue_scripts, or init hooks. (This message was added in version
3.3.) in .... ..\anvil-options.php Lines 37 and 38
On 9 October 2011 12:57, Tom Matteson <perspectivevision at gmail.com> wrote:
> Caroline & Dion ...
> Thanks for the quick feedback. However, I thought of this. Actually, to
> test this before posting on the list, I tried installing older versions of
> the theme on a couple different sites; including a site that is not
> registered to me. The update message still didnt appear. I wonder if
> WordPress recognizes my IP address, or the email associated or domain
> associated with my user login; and that is why it does not appear for me.
> Any other thoughts on this. Dion, thx also for testing this. Glad it is
> working on your computer, anyway.
> *Best Regards
> Tom Matteson*
> On Sat, Oct 8, 2011 at 6:23 PM, Dion Hulse (dd32) <wordpress at dd32.id.au>wrote:
>> Hi Tom,
>> 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
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers