... And by the way, using the text-align property could sometimes lead to unwanted alignments within the imgtext-table. Any hints, tips or corrections to my problem are very welcome! Cheers, Torsten From schrade at lineara.de Thu May 26 11:51:32 2005 From: schrade at lineara.de (Torsten Schrade) Date: Thu, 26 May 2005 11:51:32 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers In-Reply-To: References: Message-ID: > 1. First we need to wrap the complete IMGTEXT-Object with a > position-specific class. This can be done with > > tt_content.image.20.stdWrap.dataWrap =

class="imageorient-{field:imageorient}">|

> > 2. Now we are able to address them seperately in our CSS: > I forgot to mention that of course I'd first tried out to select them with div[style="text-align:center;"] table[class="imgtext-table"] {} but somehow a css-attribute selector using the style attribute of a tag is not accepted by Gecko/Opera...maybe because of the ";"? greets, Torsten From lars at houmark.com Fri May 27 00:39:14 2005 From: lars at houmark.com (Lars Houmark) Date: Fri, 27 May 2005 00:39:14 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers References: Message-ID: Hi Torsten, > Problem: When I upgraded to 3.8.0 and looked at my site with Firefox, > most of my images were not aligned properly anymore but just on the > left side. With IE however, they were allright. I can confirm this, and I think it should be considered a bug in TYPO3, as the core/csc is producing html/css output, which is not working cross-browser. Therefor this should be fixed in css_styled_content if it is possible, so that people can upgrade this extension to "save" their layout. Have you filed it on the bugtracker? If not, will you please do this, with your observations and your ideas for a fix? This way, it should be possible to make a patch/update of csc which could save the mailinglist massives of questions in the near future. Regards, Lars Houmark From schrade at lineara.de Fri May 27 08:00:09 2005 From: schrade at lineara.de (Torsten Schrade) Date: Fri, 27 May 2005 08:00:09 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers In-Reply-To: References:

Message-ID: Hi Mark, > > Have you filed it on the bugtracker? If not, will you please do this, with > your observations and your ideas for a fix? This way, it should be possible > to make a patch/update of csc which could save the mailinglist massives of > questions in the near future. > I'll do it this afternoon when I'm back from work. When I tried to report it now i always got a *field error* in the bugtracker? cheers, Torsten From rupi at gmx.li Fri May 27 08:51:59 2005 From: rupi at gmx.li (Rupert Germann) Date: Fri, 27 May 2005 08:51:59 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers References:

Message-ID: Torsten Schrade wrote: > I'll do it this afternoon when I'm back from work. When I tried to > report it now i always got a *field error* in the bugtracker? I got the same error 2 days ago: seems that the field "TYPO3 Version" is required now. Workaround: choose a TYPO3 version (3.8.0rc1 f.e.) in this field ;-) This can easily be changed later but for now it's IMO more important that this bug don't get lost. greets rupi From alexander at schories.com Fri May 27 09:19:51 2005 From: alexander at schories.com (Alexander Schories) Date: Fri, 27 May 2005 09:19:51 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers Message-ID: Hello Torsten, Hello Lars and Hello Rupert, first of all: Honestly thank you very much, Torsten, for not only describing the bug *but even* giving us a valueable solution! I can confirm as well, that all my sites show this behaviour under Gecko & Opera since the update to TYPO3 3.8.0 two days ago. For now i will try to implement the solution in my sites Torsten gave us. However, i totally agree with Lars and Rupert, that this should be an official bug along with an official fix. :) I love my firefox browser. And, even more i loved TYPO3 for rendering websites in the same pretty way on all browsers. I still would like to do so in the future. :D Kind Regards Alexander Schories Tuebingen, Germany If privacy or security of communication is on your mind, feel free to establish a secure transmission using the PGP public key obtainable from http://www.schories.com/alexander/pubkey/alexander_schories.asc From schrade at lineara.de Fri May 27 19:23:49 2005 From: schrade at lineara.de (Torsten Schrade) Date: Fri, 27 May 2005 19:23:49 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers In-Reply-To: References:

Message-ID: Rupert Germann wrote: > I got the same error 2 days ago: seems that the field "TYPO3 Version" is > required now. > Workaround: choose a TYPO3 version (3.8.0rc1 f.e.) in this field ;-) > Thanks Rupert, that's done it! Issue filed as bug 0001115. cheers, Torsten From sachav at gmx.net Fri May 27 19:44:37 2005 From: sachav at gmx.net (Sacha Vorbeck) Date: Fri, 27 May 2005 19:44:37 +0200 Subject: [TYPO3-content-rendering] xhtml cleaning messes up spam protected email addresses? Message-ID: Hi, I`d like to know if you also made the experience that spam-protected email addresses won`t work if you enable xhtml cleaning in your setup. If so, did you find a solution for for this problem? I also tried the new spamProtectEmailAddresses = ascii option. TYPO 3.7.0 or 3.8.0 with css-styled-content and htmlArea RTE. With or without TemplaVoila!. -- thanks, Sacha From robert.markula at gmx.net Fri May 27 20:07:33 2005 From: robert.markula at gmx.net (Robert Markula) Date: Fri, 27 May 2005 20:07:33 +0200 Subject: [TYPO3-content-rendering] xhtml cleaning messes up spam protected email addresses? In-Reply-To: References: Message-ID: Sacha Vorbeck wrote: > Hi, > > I`d like to know if you also made the experience that spam-protected > email addresses won`t work if you enable xhtml cleaning in your setup. > If so, did you find a solution for for this problem? > > I also tried the new spamProtectEmailAddresses = ascii option. > > TYPO 3.7.0 or 3.8.0 with css-styled-content and htmlArea RTE. With or > without TemplaVoila!. Hi Sacha, Do you use qcom_htmlcleaner? In the current version there is a bug which doesn't render spamProtectEmailAddresses in the right way (getting a 404 "Page not found" error). According to the author it will be fixed in the next version. The workaround for now is to deactivate the 'clean links' [clean_links] option in the extension properties of qcom_htmlcleaner. Regards, Ro From michael at typo3.org Sun May 29 20:20:53 2005 From: michael at typo3.org (Michael Stucki) Date: Sun, 29 May 2005 20:20:53 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers References: Message-ID: Hi Torsten, > Problem: When I upgraded to 3.8.0 and looked at my site with Firefox, > most of my images were not aligned properly anymore but just on the left > side. With IE however, they were allright. > > Observation: There seems to be a difference regarding the rendering of > "classical" IMGTEXT-Objects in the new 3.8.0 (with "classical" I mean > the normal tt_content.image.20 rendering that comes from > css_styled_content). After a first look this was me who made that change after a suggestion on the dev list: http://lists.netfielders.de/pipermail/typo3-dev/2004-December/007370.html According to it this is required by XHTML 1.1. There are two options to fix the problem: a) Reverse the change b) Enable it only optionally considering the config.doctype setting (which is what I'm going to do I think) Generally I want to remark that I'm somewhat amazed that this bug was not found in any of our three pre-releases of 3.8.0. Our bugtracker got approximately twice as many bug reports since Monday (when 3.8.0 was released) than those we collected in the time since 3.8.0beta1. Therefore, don't wonder if the stable releases are not as "stable" as you could expect. It took me hours to release these pre-releases, but if nobody uses them after all, I will spend that time to go for some roller skating and we'll have the bugs fixed out some weeks after the "final" release has been done. Think about that! :-) Kind regards - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From alexander at schories.com Sun May 29 21:53:11 2005 From: alexander at schories.com (Alexander Schories) Date: Sun, 29 May 2005 21:53:11 +0200 Subject: AW: [TYPO3-content-rendering] TYPO 3.8 and image alignment problemsin Gecko-Opera Browsers In-Reply-To: Message-ID: Hi Michael, > Therefore, don't wonder if the stable releases are not as > "stable" as you > could expect. The release of TYPO3 3.8.0 IS stable and *great*!! At least for me, this small image issue has no impact on TYPO3`s great stability at all! Thanks to Torsten Schrade we even got a working solution. And even more: Once i now know, that this issue (as far as i got it) is actually an understandable (!) problem of the Gecko-Engine, that seems to be shocked with sudden "XHTML 1.1" code in an "HTML 4.01 Transitional" declarated page - i see absolutely no reason for questioning this final release! No release (of any software) will be 100% perfect and bullit proof! Never ever.. :) > It took me hours to release these pre-releases, > but if nobody > uses them after all, I will spend that time to go for some > roller skating > and we'll have the bugs fixed out some weeks after the > "final" release has > been done. > > Think about that! :-) Well, i am sorry. Honestly. :| Because you hit the point: At least I was one of those guys who were just to lazy and even somewhat egocentric to check out the pre-releases, while "knowing that others will probably do that.." :-( I feel ashamed having somewhat ignored the efforts of all the people involved in these pre-releases.. I promise to install, thourougly test and mail my results of the next pre-releases!! >b) Enable it only optionally considering the config.doctype setting (which > is what I'm going to do I think) If i may leave my feedback here: This way seems to be fine! Thank you! Kind Regards Alexander Schories Tuebingen, Germany If privacy or security of communication is on your mind, feel free to establish a secure transmission using the PGP public key obtainable from http://www.schories.com/alexander/pubkey/alexander_schories.asc From info at cybercraft.de Mon May 30 00:17:13 2005 From: info at cybercraft.de (JoH) Date: Mon, 30 May 2005 00:17:13 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers References:

Message-ID: >> Problem: When I upgraded to 3.8.0 and looked at my site with Firefox, >> most of my images were not aligned properly anymore but just on the >> left side. With IE however, they were allright. >> >> Observation: There seems to be a difference regarding the rendering >> of "classical" IMGTEXT-Objects in the new 3.8.0 (with "classical" I >> mean the normal tt_content.image.20 rendering that comes from >> css_styled_content). > > After a first look this was me who made that change after a > suggestion on the dev list: > http://lists.netfielders.de/pipermail/typo3-dev/2004-December/007370.html > > According to it this is required by XHTML 1.1. > There are two options to fix the problem: > a) Reverse the change > b) Enable it only optionally considering the config.doctype setting > (which is what I'm going to do I think) > > Generally I want to remark that I'm somewhat amazed that this bug was > not found in any of our three pre-releases of 3.8.0. Well - I would have found it, and I could have told you that an "inline style" would not work here - apart from the fact that a class will always be preferrable ;-) But - I never noticed that thread you mentioned and for testing reasons I only upgraded my personal testsites, where I am not working with IMGTEXT at all since we are creating a TS based solution there using IMAGE and TEXT inside one surrounding COA. So I was not able to even see the bug. Sorry. Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your knob sometimes!) Dieter Nuhr, German comedian openBC: http://www.openbc.com/go/invuid/Jo_Hasenau From sachav at gmx.net Mon May 30 02:04:16 2005 From: sachav at gmx.net (Sacha Vorbeck) Date: Mon, 30 May 2005 02:04:16 +0200 Subject: [TYPO3-content-rendering] xhtml cleaning messes up spam protected email addresses? In-Reply-To: References:

Message-ID: Hi, > The workaround for now is to deactivate the 'clean links' [clean_links] > option in the extension properties of qcom_htmlcleaner. thanks for your feedback. In 3.8.0 it was the qcom_htmlcleaner ext that caused the problem just like you said. But in 3.7.0 it also happens without the extension. I will update to 3.7.1 and see if the problem is fixed there. -- Ciao, Sacha From schrade at lineara.de Mon May 30 07:22:37 2005 From: schrade at lineara.de (Torsten Schrade) Date: Mon, 30 May 2005 07:22:37 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers In-Reply-To: References:

Message-ID: Good morning everybody, > But - I never noticed that thread you mentioned and for testing reasons I > only upgraded my personal testsites, where I am not working with IMGTEXT Same here. Additionally, it's a browser specific issue and not obvious for everybody at first sight. But anyway, it's a shame and it's very understandable that you are quite annoyed Michael. Sorry from me as well! Let's discuss some thoughts about a solution to this: First, considering the validity of align: according to my O'Reilly reference the align-attribute for divs is deprecated *only* for HTML 4.01 Strict and XHTML 1.1 Strict. But looking into the Specs from the W3C (http://www.w3.org/TR/html401/index/attributes.html) gives the impression that it is deprecated in general...? If anybody has clarifications on this please post it. Be that as it may, the impact on the two mentioned solutions is the same: 1) Reverse the change - is out of the question, as there clearly are doctypes where this attribute is not valid. 2) combine it with the config.doctype setting - better, but this only makes sense if the attribute really is deprecated just for the Strict doctypes. And there are some additional drawbacks: a) the text-align will have to stay in there even in the strict doctypes for backwards compatibility with IE 5+ - for them, margins don't work. As Joey said: an inline style is problematic - text align is inherited and this influences everything within the table, e.g. the caption. At the moment, this is solved by wrapping the caption in an additional div with another text align...ahem. This method rules out the possibility that we users can define some general alignment rules for imagecaptions: what if I want all my images at different positions but my captions always left-aligned -> I will have to set it for each single image... a general rule in my CSS will not work as the inline style always wins out... b) if the core begins to output browser specific CSS (for Gecko/Opera in this case) - well, where will that end? I think the aim for the core should always be to produce one single HTML/CSS concept that is valid for all browsers. Which leaves me with the conclusion that a) let's not just use the method of my *workaround* for solving that problem in the core > it's only a *workaround* and nothing the core would ideally produce. Unless this problem is fixed I'm glad though that it seems to be working for other people as well :-) b) let's have a look at the IMGTEXT function in class.tslib_content. Though my php is not the best I'll at least try to email you some structural suggestions Michael. And everybody else who is interested please do so as well. c) my posts are clearly to long! So before you get the impression that i want to write books in this list, have a nice day and cheers, Torsten From alexander at schories.com Mon May 30 08:33:07 2005 From: alexander at schories.com (Alexander Schories) Date: Mon, 30 May 2005 08:33:07 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problemsin Gecko-Opera Browsers In-Reply-To: Message-ID: Good morning list, :) > b) if the core begins to output browser specific CSS (for > Gecko/Opera in > this case) - well, where will that end? I think the aim for the core > should always be to produce one single HTML/CSS concept that is valid > for all browsers. Agreed! I believe it is important, that TYPO3 continues to produce good, general output and will not have "x" render cores for "x" browsers or even browser versions, that would all have to be maintained separatly.. Thank you all for your efforts! Kind Regards Alexander Schories Tuebingen, Germany If privacy or security of communication is on your mind, feel free to establish a secure transmission using the PGP public key obtainable from http://www.schories.com/alexander/pubkey/alexander_schories.asc From schrade at lineara.de Mon May 30 11:37:52 2005 From: schrade at lineara.de (Torsten Schrade) Date: Mon, 30 May 2005 11:37:52 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers In-Reply-To: References:

Message-ID: > b) let's have a look at the IMGTEXT function in class.tslib_content. > Though my php is not the best I'll at least try to email you some > structural suggestions Michael. And everybody else who is interested > please do so as well. ok, I've come up with some concepts that maybe point into the right direction: http://www.staff.uni-mainz.de/schradt/imgtext.html I've had a look at things in class.tslib_content.php and thought to become clear first what html/css-concepts we want to achieve at the end. Targets: 1. Completely skip the align attribute. 2. Don't use any additional divs, especially clearing ones. 3. Have it compatible for IE5+ as well. If you have a look at the code on my page you can see that I've done it by using inline styles, even if Joey and myself have problematized this. But the point is a) if we skip the html-attribute and solely rely on css - that has to go somewhere and well, why not inline as this seems to be the easiest way for a patch b) after all the user decides to position an image and so has to live with the consequences ;-); after all, there are three other imgtext extensions that handle things differently. So, linking this concept to the class we would need the following changes in function IMGTEXT: - the text-align inline style has to stay in there, but only for imageorient-0 and imagorient-8. Otherwise the tables aren't centered in IE<6 - not one $tablecode but three variants of this variable, each one either floating the imgtext-table or setting auto-margins with inline styles - the enclosing div should always get a general and one position specific class - the enclosing div has to have a calculated height set by an inline style that roughly equals the height of the whole imgtext-table. This is for the floated types and I realize that this might be very difficult to achieve. As usual, any hints, corrections and suggestions very welcome, yours, Torsten From ben at netcreators.nl Mon May 30 15:21:26 2005 From: ben at netcreators.nl (ben van 't ende [netcreators]) Date: Mon, 30 May 2005 15:21:26 +0200 Subject: [TYPO3-content-rendering] TYPO3 3.8.0 XHTML strict mailform Message-ID: Hi List, I have been testing a bit with the latest mailform in TYPO3 3.8.0. I can't really get enthousiastic about it. On this page (http://ben.vantende.net/t3/mail/) you can find a mailform with almost all options with this setup: tt_content.mailform.20 { accessibility = 1 REQ = 1 layout = ###LABEL### ###FIELD###
COMMENT.layout = ###LABEL### RADIO.layout = ###LABEL###

###FIELD###

LABEL.layout = ###LABEL### ###FIELD###
labelWrap.wrap = | commentWrap.wrap = | radioWrap.wrap = | REQ.labelWrap.wrap = | stdWrap.wrap =

params.radio = class="mf-radio" params.check = class="mf-check" params.submit = class="mf-submit" } I haven't styled it in anyway, but validating (xhtml_strict) returns a number of errors: 1. attribute "name" in form element 2. attribute "wrap" in textarea element [accessibility = 1] 3. id's for radiobuttons are not unique. (don't now how this should actually be) who knows? 4. incredible long hashed id's. there is a bug describing an issue with square brackets here: http://bugs.typo3.org/view.php?id=1075 Martin just told me he wants to patch that for 3.8.1 Does anyone have any thoughts on the first three items? Should they be deleted or changed to something else/ gRTz ben -- netcreators :: creation and innovation www.netcreators.nl - www.typo3.nl From mathias.schreiber at wmdb.de Mon May 30 15:47:16 2005 From: mathias.schreiber at wmdb.de (Mathias Schreiber [wmdb>]) Date: Mon, 30 May 2005 15:47:16 +0200 Subject: [TYPO3-content-rendering] TYPO3 3.8.0 XHTML strict mailform In-Reply-To: References: Message-ID: ben van 't ende [netcreators] wrote: > 1. attribute "name" in form element We did a funny test back at our UG meeting. If you write "" and send the form the server does not recieve and POST or GET parameters called "whatever". Maybe someone can clear things up a bit but right now I think it is not possible to send POST vars while being 100% XHTML strict compatible. -- if ($GLOBALS['TSFE']->fe_user->user['ahnung'] == 0) { $this->fresseHalten = 1; } From mathias.schreiber at wmdb.de Mon May 30 16:00:43 2005 From: mathias.schreiber at wmdb.de (Mathias Schreiber [wmdb>]) Date: Mon, 30 May 2005 16:00:43 +0200 Subject: [TYPO3-content-rendering] TYPO3 3.8.0 XHTML strict mailform In-Reply-To: References:

Message-ID: Mathias Schreiber [wmdb>] wrote: > ben van 't ende [netcreators] wrote: > >> 1. attribute "name" in form element > > > We did a funny test back at our UG meeting. > If you write "" and send the form the > server does not recieve and POST or GET parameters called "whatever". > Maybe someone can clear things up a bit but right now I think it is not > possible to send POST vars while being 100% XHTML strict compatible. ignore - read wrong -- if ($GLOBALS['TSFE']->fe_user->user['ahnung'] == 0) { $this->fresseHalten = 1; } From info at cybercraft.de Mon May 30 16:14:32 2005 From: info at cybercraft.de (JoH) Date: Mon, 30 May 2005 16:14:32 +0200 Subject: [TYPO3-content-rendering] TYPO3 3.8.0 XHTML strict mailform References:

Message-ID: >>> 1. attribute "name" in form element >> >> >> We did a funny test back at our UG meeting. >> If you write "" and send the form >> the server does not recieve and POST or GET parameters called >> "whatever". Maybe someone can clear things up a bit but right now I >> think it is not possible to send POST vars while being 100% XHTML >> strict compatible. > > ignore - read wrong Sorry - initially it was me who read it wrong on the dev list. W3C say "name" is not allowed for form tags - but still allowed (and necessary) for elements inside a form. ;-) Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your knob sometimes!) Dieter Nuhr, German comedian openBC: http://www.openbc.com/go/invuid/Jo_Hasenau From schwarzkopf.no.spam at artplan21.de Mon May 30 22:25:29 2005 From: schwarzkopf.no.spam at artplan21.de (Andreas Schwarzkopf) Date: Mon, 30 May 2005 22:25:29 +0200 Subject: [TYPO3-content-rendering] TYPO3 3.8.0 XHTML strict mailform In-Reply-To: References:

Message-ID: Hi Mathias, Mathias Schreiber [wmdb>] schrieb: > We did a funny test back at our UG meeting. > If you write "" and send the form the > server does not recieve and POST or GET parameters called "whatever". > Maybe someone can clear things up a bit but right now I think it is not > possible to send POST vars while being 100% XHTML strict compatible. this is valid xhtml 1.0 strict: grtx Andreas From info at cybercraft.de Mon May 30 23:01:01 2005 From: info at cybercraft.de (JoH) Date: Mon, 30 May 2005 23:01:01 +0200 Subject: [TYPO3-content-rendering] TYPO3 3.8.0 XHTML strict mailform References:

Message-ID: >> We did a funny test back at our UG meeting. >> If you write "" and send the form >> the server does not recieve and POST or GET parameters called >> "whatever". Maybe someone can clear things up a bit but right now I >> think it is not possible to send POST vars while being 100% XHTML >> strict compatible. > > this is valid xhtml 1.0 strict: > > Fine - but will it be valid XHTML 1.1? Not sure about that since I got a bit confused by different messages on the list, where people wrote that "name" and square brackets will be not allowed anymore. Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your knob sometimes!) Dieter Nuhr, German comedian openBC: http://www.openbc.com/go/invuid/Jo_Hasenau From michael at typo3.org Mon May 30 23:11:23 2005 From: michael at typo3.org (Michael Stucki) Date: Mon, 30 May 2005 23:11:23 +0200 Subject: AW: [TYPO3-content-rendering] TYPO 3.8 and image alignment problemsin Gecko-Opera Browsers References:

Message-ID: Hi Alexander, >> Therefore, don't wonder if the stable releases are not as >> "stable" as you could expect. > > The release of TYPO3 3.8.0 IS stable and *great*!! Thanks, I didn't know that! ;-) Just joking, see above - I meant it's not _as_ stable as you could expect... However it has at least 200 bugs less than 3.7.0 has! > Well, i am sorry. Honestly. :| > > Because you hit the point: At least I was one of those guys who were just > to lazy and even somewhat egocentric to check out the pre-releases, while > "knowing that others will probably do that.." :-( > > I feel ashamed having somewhat ignored the efforts of all the people > involved in these pre-releases.. > > I promise to install, thourougly test and mail my results of the next > pre-releases!! If you keep your word then my mail was worth the time. May others follow your example... Regards, michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From michael at typo3.org Mon May 30 23:17:56 2005 From: michael at typo3.org (Michael Stucki) Date: Mon, 30 May 2005 23:17:56 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignment problems in Gecko-Opera Browsers References:

Message-ID: Hi Torsten, > > b) let's have a look at the IMGTEXT function in class.tslib_content. >> Though my php is not the best I'll at least try to email you some >> structural suggestions Michael. And everybody else who is interested >> please do so as well. > > ok, I've come up with some concepts that maybe point into the right > direction: http://www.staff.uni-mainz.de/schradt/imgtext.html Your comments look fine, thanks so far. Please coordinate with this group and as soon as you have agreed on a solution, file a bug report and send it to me. You are the experts! - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From alexander at schories.com Tue May 31 08:39:34 2005 From: alexander at schories.com (Alexander Schories) Date: Tue, 31 May 2005 08:39:34 +0200 Subject: [TYPO3-content-rendering] TYPO 3.8 and image alignmentproblemsin Gecko-Opera Browsers In-Reply-To: Message-ID: Hello Michael, > Just joking, see above - I meant it's not _as_ stable as you > could expect... I understood that - i just gave you no further details, that for us here it IS as stable as we dared to expect: Well, there are many complex TYPO3 sites running here. All of them were updated to 3.8.0. A school site with teachers, pupils, means many users - nobody found the image-alignment-problem. Even after i discovered it a day later and told them, that i will look out for a fix, people told me once more that they love TYPO3 and it is no big issue for them at all! As an interim solution i patched back the code in class.tslib_content.php to 3.7.0. Everybody seems to be *very* happy here with 3.8.0 - until now nobody has complained a single time..so at least over here it`s all stable and wonderfull. Really. :) So please understand, that i somewhat dislike people always complaining to be "shocked" about a bug in a "final version" of a software. Well folks, "final" will never mean perfect. Even not for TYPO3. :D > However it has at least 200 bugs less than 3.7.0 has! Cool! > If you keep your word then my mail was worth the time. May > others follow > your example... Don`t worry - i keep my word! Btw: As you will know, i am not that far away located from you - so i will always have to fear "Major Stucki" coming to my place and beat me up. :D Thank you once again! Kind Regards Alexander Schories Tuebingen, Germany If privacy or security of communication is on your mind, feel free to establish a secure transmission using the PGP public key obtainable from http://www.schories.com/alexander/pubkey/alexander_schories.asc