Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

May i know that register link did shared before from your site? Because if the register link shared before from your site, system will stored this link data into database. When you share again this link on your site, system will check whether this link share before or not, if yes, it will load the data from the database, mean it will not re-crawl the register link again to get the latest data from the link.

Perhaps you can update your Joomla backend, FTP and database access so we can better have a check?

By the way, may i know the correct result is won't show any image from this register link right?

Hi Arlex.... I guess it may well have been shared before - It's one of the main pages of my site. I can't say 100% for sure though!

That image would only have existed on the page in a module position as it was a promo campaign running a while back. It's not really anything to do with the page though!

Maybe that 'don't re-crawl' coding needs a re-think to avoid situations like this?

I think all my FTP, Backend and Database info are current. Anything not working?

..and finally yes you're right, at this point in time, anyone sharing that link there shouldn't be any image as there aren't any images on that page.

Thanks for looking at this!
Happy Holidays!

Hello Andy,

When you share a link, EasySocial automatically caches the contents of the link to prevent it from scraping the urls again. This is to avoid the delay when sharing links.

I have purged the cache by running the following SQL query on the site, so that it will try to scrape the page again.

truncate table #__social_links;

OK thanks Mark. I do think this will be an issue for many people and could cause some embarrasing results - if images from old time-expired modules are being cached and then re-presented when users share the page links... takes the control away from the website managers.

Thanks for your input Andy, I will discuss with our developer regarding this and see whether we can do something about it in the future release version.