[TYPO3-english] Templavoila does not work again

[Erik Svendsen]

Ries van Twisk skrev:
> 
> On Jun 6, 2009, at 3:17 PM, Erik Svendsen wrote:
> 
>> Ries van Twisk skrev:
>>
>>>
>>> I don't think that Vahan is unreasonable here.
>>
>> Read some of the treads, and maybe you understand Dmitry better.
>>
>> They indicate that he is working on a really large and in some instance
>> complex website. When you are moving to that leauge, paid support are
>> the natural way.
> 
> Not really, some people can manage complex websites perfectly.
> 

That's correct, but they also has the necessary knowlegde. Another 
reason is that good consultancies often has experience from other large 
implementation which makes use of paid support cheaper than using days 
trying to solve the problem yourself.

>>
>>>
>>>>
>>>> A short check on your website shows a lot of bad coding style and no
>>>> optimaliation.
>>>
>>> So what does that say???
>>
>> Larger possibilites for errors? Lack of knowlegde of TYPO3?
> 
> 
> You did remove the part where even TYPO3 websites has mistakes and my 
> portion
> about parsing templates, TV doesn't care if there is border="0" in the 
> wrong tag (w3c does).
> 

I understood your point, and I used question mark. And the total 
impression the source code (not only W3C validation) is giving you, 
often indicates the knowlegde - also of TYPO3. Or lack of time.

And typo3.org/typo3.com sucks in that way.

> 
> 
> Fully agree, but don't blame somebody using a extension
> that does xclassing, I have seen core developers creating extensions
> that does do xclassing.
> 

I don't blame them, but I advice them to look closely at them and try to 
  find alternatives.

> 
>>
>> In which order the extensions are loaded could also be the problem.
> 
> Correct, unfortunately TYPO3 doesn't help a whole let there and
> often extension developers don't put there dependencies correctly
> in there created extensions.
> 

I think we have to live with that problem as long as we have nearly 4 
000 extensions, and no extensions developer has time and opportunity to 
test every possible combination.

>>>>
>>>> And there are a problem with comments like this in TER. Very much of 
>>>> the
>>>> comments will probably be wrong.
>>>
>>> Why would that be?? People can comment on them, right?
>>>
>>
>> People will probably make comments without doing a proper investigation
>> of the problem.
> 
> yes, but they's why people can comment on the comments. Much like what 
> happens on forums and
> mailinglist.
> The comment system is by no means a way of bug tracking, it's just a 
> comment...
> I think it's a good idea....

My experience tells me it's not a good idea. Because the people that 
should make comments on "wrong" comments seldom has time to do it and 
people tends to rush to write commenents long before they even has 
checked the manual or done a search about the problem.

But if the comments could be done in a proper way, with a good 
description it could work. But to have this to work, some moderation is 
needed, and who is going to do it.

>>
>> If something like this is going to work, the comments has to be
>> moderated and commented by the author. Personally I want them to fix 
>> bugs.
> 
> I also want bugs to be fixed,
> but we cannot possible enter all comments in a bugtrack,
> and a way to comment on extensions is a good way of keeping track of 
> things.

Agree that we can't have all comments in the bugtracker, but I think we 
have to look for another solutions at this point than commenting in TER.

> Ries
> 
> PS: You need to set your reply to correctly, I got this:
> 
> <Erik at lists.netfielders.de>: host lists.netfielders.de[213.203.207.41] 
> said:
>    550 5.1.1 <Erik at lists.netfielders.de>: Recipient address rejected: User
>    unknown in local recipient table (in reply to RCPT TO command)
> 
> <Svendsen at lists.netfielders.de>: host lists.netfielders.de[213.203.207.41]
>    said: 550 5.1.1 <Svendsen at lists.netfielders.de>: Recipient address
>    rejected: User unknown in local recipient table (in reply to RCPT TO
>    command)
> 
>  is that a bug or feature :) ???
> 

A bug!! Change from one newsreader to another filled some field with 
wrong values. Bad import tool.

Erik