I am administrating a company FB channel and currently I am trying to upload images of the brand's history. However, the upload feature freezes when I add an image or posting prior to 1970-1-1. I guess that's an issue with the database and related to the UNIX timestamp. Does anyone have a hint for me?
They are possibly using epoch timestamps which can not contain dates prior to 1/1/1970. In anycase... This is a bug and should be reported to Facebook at their Bug System
For what it's worth, text posts and milestones can still be backdated before the Unix epoch, just not photos or videos.
I've had the same problem too for almost on two months. (Three bug reports didn't change anything!)
I can confirm that milestones can be placed before 1970. Thanks. I have sent numerous bug reports to FB about the problem with photos with no results. I guess no one over 42 works at Facebook.
It appears that Facebook is only using epoch timestamps to determine IF they want to save the date now.
Before I could set the date to before the UNIX timestamp, and they still appear correctly. However, if you want to change the date you can only choose a date of 1 January 1970 or later.
It amazes me that this bug still hasn't been fixed.
Yes, thank you! posting milestones do work prior to 1/1/1970 including with photos. I added a milestone and tried both adding a photo (from the existing photo gallery) at the same time as posting the milestone and editing the milestone after it was posted to add the photo. Not tried video yet (as I don't have any moving images prior to 1970!). See FB for Swords Aviation. You do need to set the start date of your timeline prior to the date you want to post of course.
Related
Seems like FB has an issue fetching or displaying properly set og:image on our links suddenly - this affects share dialogs etc.
Everything has been working fine so far. I noticed this issue today.
Debugger https://developers.facebook.com/tools/debug/og/object/ shows the image after refetching (try: http://cakesdecor.com/cakes/194565-3d-vintage-clock-cake) but the image doesn't appear in the share dialog at all.
Is it a temporary bug or are there some new FB policies re images?
Approx. 2 hours ago, this bug was confirmed by FB!
see: https://developers.facebook.com/bugs/978421888869140/
I confirm this issue also occurs on multiple sites I own. It began some time in the past 14 hours. The debugger is returning a valid output (but the post preview at the bottom is lacking the image).
My guess is that it is somehow related to the face that today (30/apr) they've forced all fb apps to migrate to sdk2.0.
I sure hope they're already working on a fix... but go figure :-/
I'm using Nutch 1.7 and everything seems to be working just fine. However, there is one big issue I don't know how to overcome.
How can I crawl ONLY urls newly added in the last 24 hours. Of course we could use adaptive fetching but we hope there would be another better way that we are not aware until now.
We only need the urls that are added in the last 24 hours as we visit our source-websites every each day.
Please let me know if nutch can be configured and setup to do that or if there is a written plugin for crawling only urls added in the last 24 hours.
Kind regards,
Christian
you gain your new urls by parsing HTML!
there is no way that you could specify an anchor's lifetime by parsing an
<a>
tag!
you have to have a list for old urls in your DB so you can skip them!
Dates on a website I maintain display fine, until I log in (as an admin). Then they are off by minus one day.
I figured this is because the timestamps are then displayed in UTC while they should be displayed in UTC+1. And since UTC is one hour off, days display one day off.
I could hunt down every piece of code displaying dates and hard code them to always display as UTC+1 (which is what I want), but I have a feeling there might be an easier, global way to fix this.
Check your timezone settings. Drupal must be using it for displaying dates.
Our website was recently redesigned and since then I have been unable to get the correct image to appear when I choose link.
For instance:
If I post this link:
http://www.horrormovienews.net/article1184.html
It does not show the image of Ethan Hawke as one of the choices for me to post along with this story. I have asked a few other people (co-workers) and some friends who live around the USA, PA, NC, etc. and they can not get that pic as a choice either. One person who lives in MA can see it when he posts a link.
(This happens to every news story in our network of sites since the theme was changed on the sites)
Another bizarre thing is it WILL show the image for this story:
http://www.horrormovienews.net/article1160.html
but not the one at the top of this post.
I have even used the Facebook lint tool about a week ago to try to refresh the cache.
I have tried to many different things to try to fix thing. I changed the image path, the size of the images, etc. Nothing seems to work.
Does anyone have any idea what could be causing it? Any help would be much appreciated.
You need to specify og:image tag. See your results here: http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.horrormovienews.net%2Farticle1184.html
Fix up those warnings and then you should be able to share the link much more consistent.
I am storing dates in a core data data file whenever the user uses my app and then displaying them back to the user. For some reason, just every now and again, i get an entry with the the right day and year but the month has dropped back to the fires. Has anyone heard of this happening in the past and know how to fix it?
Everything seems unaffected (ie time, days and years) except month. It only ever changes to january (IE it either works right eg 23/5/2011 or it defaults to january eg 23/1/2011)
Thanks to anyone who can shed some light on this or can even point me in the right direction as to finding the problem as so far it looks random
thanks
Found my issue. It wasn't random, it only happens when I quit the app then go back in. I wasn't handling the date correctly when I feed it back into the app.