[TYPO3-english] Templavoila does not work again

Ries van Twisk typo3 at rvt.dds.nl
Sat Jun 6 20:31:21 CEST 2009

On Jun 6, 2009, at 12:17 PM, Erik Svendsen wrote:

> Vahan Amirbekyan skrev:
>> My team and I area always looking for other alternatives.
>> you are right this is not the first time TV does not work for me.
>> Your comment though does not make any good neither to you nor to T3.
> I can understand Dmitry, most of us make our money from TYPO3 and
> haven't much time to answer questions on this or other lists. And you
> have started 24 threads in 3 months, most of them regarding realUrl  
> and
> TV. When you need support on this level, also more complicated stuff  
> you
> should consider paying for help.

Guys, come-on, this is not fair...

The number of threads a user starts has nothing to do if a user needs  
to pay
for support or not.
They guy had lot's of problems with TV and this was in the end due to  
a conflict with a other extension,
and he even posts his solution on the list for that. Also he made a  
good suggestion that for TER
it would be nice to have some form of feedback (page comments can help  

I don't think that Vahan is unreasonable here.

> A short check on your website shows a lot of bad coding style and no
> optimaliation.

So what does that say???

http://typo3.org has validation errors :
http://typo3.com/ has validation errors :

I can find some other sites that also has validation errors (incliding  
my site)

But this doesn't say a whole lot...

Yes the template should be free of errors, but it highly depends for
TV what sort of errors there are in teh document and lot's of errors
TV don't care, validating a template against w3c and TV doesn't compare.

>> When TV did not work this time it was "simulatebe" ext. Why this two
>> exts conflict you are the one to answer. In my opinion it should  
>> not. I
>> understand that simulatebe is not very popular ext and that is why  
>> you
>> probably never looked into this before. But once you find it out it  
>> is a
>> good idea to add it to the list of conflicting exts.
> It doesn't make any conflict with TV on one of my test installations.
> Personally have I used TV for 5 years and never had conflicts  
> between TV
> and other extensions (besides the conficts listed in TV).
> And yes there are such conflicts, but mainly because of use of  
> xclasses
> in other extensions. Use of xclasses are "bad" coding behavior. TV  
> is as
> far as I can read the code, one of the cleaner extensions in TER and
> don't use xclasses.

Classes are bad, but they are part of TYPO3... right? Does that make  
TYPO3 bad?
Apparently XCLASS is part of TYPO3 standard, if we like it or not...
Don't blame extensions for using using xlassing when TYPO3 has support  
for it.

> My problems with TV is mostly regarded to XML parsing problems and
> conflicts regarding not using utf-8 on the whole website and/or  
> specific
> Norwegian characters. Then it happends that the saved mappings get  
> lost.
>  To be correct, they are there, but they are impossible to render.

hint: make your template in english....

> And there is nothing in the code of simulatebe which indicates  
> conflict
> as far as I see.
>> My suggestion to T3 team is to make comments possible in T3 exts
>> repository. So that for instance I could go to TV ext download page  
>> now
>> and comment with this so that other folks know about this conflict.
>> Another suggestion is that TV did not throw any warning at all. See  
>> if
>> it is possible for this case.
> First question. Is it simulatebe who conflicts or TV. TV is a much  
> newer
> extensions than simulatebe. When two extensions conflicts, the older  
> one
> are the problem in my opinion (most cases).

simulatebe needs to be added to the list of conflicting extensions...
I hope dmitry has a spare 5 minutes to do that one of these days....

> 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?

> Best
> Erik S
> __________

More information about the TYPO3-english mailing list