updating extensions notification problem

[peteruoi]

Steps to reproduce the issue

check joomla backend dashboard.
"All extensions are up to date"

Extension->Extension Manager->update->Find updates

Expected result

mod roksprocket new version 2.1.3

Actual result

There are no updates available at the moment. Please check again later.

System information (as much as possible)

Additional comments

I have 4 3.3.6 joomla sites in a unmanaged vps with ispconfig. So server settings (php-mysql) is the same for all of them. In one of them however the joomla updater found the new version of roksprocket. The other three sites dont fint it no matter how many times i press find updates. It's really odd so if someone has any idea what to do to find the bug is more than welcome:)

[mbabker]

Since you're still on 3.3.6, I'd suggest checking the #__update_sites database table to make sure all update sites are enabled (in 3.4, you can do this directly in the Extension Manager).

[brianteeman]

This is almost certainly an issue with an update server being disabled
inside that one site. This has been resolved in Joomla 3.4 with a new
option to check this.

Please upgrade to 3.4 and check

On 3 March 2015 at 15:22, peteruoi notifications@github.com wrote:

Steps to reproduce the issue

check joomla backend dashboard.
"All extensions are up to date"

Extension->Extension Manager->update->Find updates
Expected result

mod roksprocket new version 2.1.3
Actual result

There are no updates available at the moment. Please check again later.
System information (as much as possible) Additional comments

I have 4 3.3.6 joomla sites in a unmanaged vps with ispconfig. So server
settings (php-mysql) is the same for all of them. In one of them however
the joomla updater found the new version of roksprocket. The other three
sites dont fint it no matter how many times i press find updates. It's
really odd so if someone has any idea what to do to find the bug is more
than welcome:)

—
Reply to this email directly or view it on GitHub
#6279.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

[brianteeman]

I am marking this information based ont he advice from @mbabker above and the recommendation to upgrade to 3.4

If this does or does not work please report back

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6279.}

[peteruoi]

updating to joomla 3.4 and going to updates sites. Then enabling the disabled sites solved the issue :) You can close this :)
Thanks!

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6279.}

[joomla-cms-bot]

Set to "closed" on behalf of @zero-24 by The JTracker Application at issues.joomla.org/joomla-cms/6279

[zero-24]

Closing thanks for the update here!

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6279.}