Hey Gerald,

I tried to access the site that you have provided us with the access and it seems to be showing up the correct versions as you can see here, http://take.ms/ssPgt . Am I missing anything here?

Both in Joomla Update as well as in 'MyJoomla' the site is showing an update needed for easyblog. It appears to be a site caching issue, though I have done all the maintenance I can think of and this remains.

Perhaps you can try download the latest launcher installer from https://stackideas.com/dashboard then upload through your Joomla backend installer page and proceed that installation again and see how it goes.

Keep us update If that update notice still appear for Easyblog.

that dids not work

Can i have the permission to help you update again latest version of Easyblog on your site?

I will check on this issue.

updated user info so you should be able to access the site. I checked PHPMyAdmin, but cannot find any version info.
Something in the site is reporting version 5.0.22. You can see this in the Joomla Extensions:Update manager

addendum; I did a recursive search on the version number with wildcard brackets (%5.0.22%) and found four references. I am not sure what the 'bf' prefix tables are, whether they are leftover, or something created by admin-tools, but they may be involved, however, there are two other core Joomla tables with the same reference. I am attaching a screenshot of the search results for reference.

Hey Gerald,

There's something strange on the site as there should only be 1 record of com_easyblog in the table #__extensions but there are 2 records now.

Was this a migrated Joomla site? By the way, is it possible for you to provide us with the phpmyadmin access so that I can update the records?

I deleted the bf records, deleted the redirect, and deleted the extension record, went through the process of discovery, and installation. That seems to have fixed the issue. Not sure why this ended up this way. It WAS migrated across several servers. It is our oldest hosted site. But it seems fixed, thank you

Thanks for updating Gerald, glad that the issue is sorted out once and for all I guess the problem was due to the migration earlier and it somehow caused that additional record to be added.