[TYPO3-english] TYPO3 pages inaccessible by Facebook - unable to like/share

[Scotty C]

Christopher,

You make a good point, and my team has tested for that. The peculiar part is 
that this issue is happening with *every* TYPO3 web site we host (over 30, 
spread across 3 different servers, all running 4.4.2). Additionally and in the 
case of the most urgent site, www.centreofthearts.ca/?75&EventID=37 the code is 
an exact copy of the code from a straight-HTML (no CMS) site, where it did work.

Any further advice you (or anybody!) may have is greatly appreciated,
-Scott.





----- Original Message ----
From: Christopher Torgalson <bedlamhotel at gmail.com>
To: TYPO3 English <typo3-english at lists.typo3.org>
Sent: Sun, February 27, 2011 2:12:34 PM
Subject: Re: [TYPO3-english] TYPO3 pages inaccessible by Facebook - unable to 
like/share

Hi there,

On Sun, Feb 27, 2011 at 2:55 AM, Scotty C <superscotty19 at yahoo.com> wrote:
> Hi Heath,
>
> I appreciate your efforts! Perhaps I should clarify ... while the function of
> sharing does work, the problem is that the full description is not showing. As
> you noted, you see the comment box, then the URL below it. However, you should
> see the comment box, then full info below: title, description, and image. I've
> reported to facebook as Ries suggested but I really think this is a TYPO3 
issue
> because if I hand-code an HTML page it works and gives me all the info.


TYPO3 _could_ be involved, but it's not really a factor in determining
the source of a problem like you describe. TYPO3 pages are the same a
any other HTML documents--it's really irrelevant how a page was
generated.

If you have a document where the desired function works correctly, and
another document where it doesn't, then a) find the differences
between those two documents--there MUST be differences--and b) find
out which of those differences is responsible for the problem (usually
by altering one of the documents to be more and more similar to the
other and testing to see if each change causes/fixes the problem).

Once you've discovered the precise cause of the problem in the HTML
document or its associated files, _then_ you take care of whatever it
is in TYPO3/whatever CMS that might be involved in producing the
differences in the HTML/js/css that caused the problem.

-- 
Christopher Torgalson
http://www.typo3apprentice.com/
_______________________________________________
TYPO3-english mailing list
TYPO3-english at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english