Thanks, I believe that needs to be updated in the options code. You should use the same syntax there that you do for the other date formating, namely that from the PHP date function. http://php.net/date
I had spotted that Friday night, but didn’t get a chance to update a fix over the weekend.
Hmm…I simply changed the date format in the link manager options, and now the floating window doesn’t show up at all. 🙂
The dates show up for me, but they are all “12/31/1969 07:00” unless they have updated..
The 1969 thing is fixed in the CVS. Cena, can you check your options and see if the updated title is enabled, and check the code to see if it’s there? Or maybe you’re running a CVS version and it just hasn’t picked up any changes yet. Is there anything in your weblogs.com.cache file?
I am running a CVS version and there’s nothing in the cache file.
which file in the CVS needs to be downloaded?
I’ve committed changes to CVS for wp-links/links.php, wp-admin/wp-install.php and wp-admin/upgrade-071-to-072.php for this.
If you have the latest CVS version of links.php, then make sure that in “Options/Link Manager Settings”, you’ve removed the ‘%’ characters from links_updated_date_format. Also, in your template, you have to uncomment this line:
require_once($abspath.’wp-links/links.weblogs.com.php’);
Uncommenting that line causes the following:
Warning: php_hostconnect: connect failed in /wordpress/wp-links/links.weblogs.com.php on line 93
Warning: file(“http://www.weblogs.com/changes.xml”) – Bad file descriptor in /wordpress/wp-links/links.weblogs.com.php on line 93
Warning: Bad arguments to implode() in /wordpress/wp-links/links.weblogs.com.php on line 93
That means that it couldn’t open the changes file on the weblogs.com server. This could be for a couple of reasons. On some systems opening remote files through PHP is turned off in a misguided attempt at security. The other possibility is that weblogs.com just wasn’t accessibile (for whatever reason) when it tried to connect. So I would try again, and if it still doesn’t work then contact your host.
Now, I tried to fix it and I’m getting:
Warning: fopen(weblogs.com.changes.cache): failed to open stream: Permission denied in /home/monosyll/public_html/log/wp-links/links.weblogs.com.php on line 99
Warning: fwrite(): supplied argument is not a valid stream resource in /home/monosyll/public_html/log/wp-links/links.weblogs.com.php on line 100
Warning: fclose(): supplied argument is not a valid stream resource in /home/monosyll/public_html/log/wp-links/links.weblogs.com.php on line 101
Did you chmod 666 your weblogs.com cache file per the instructions?
Okay, now it’s showing the notes correctly in the tooltip, but still no go on the date/time of last update.
Hi Cena,
The updated date and time only gets stored in the database when a link matches one in the file pulled from weblogs.com. So if the link wasn’t listed on weblogs.com at the time the cache file was updated then it won’t have a date at all (or it will have an old one).
This is a compromise because the amount of time taken to retrieve and process the xml file from weblogs.com can be considerable. So a cached copy of the file is kept, but only processed once.
Does that make sense?
Mike
It sure does. Now I can get on with fussing over other fiddly details. 🙂
