[TYPO3-core] More strict convention for typoscript naming

[Marcus Schwemer]

Hi all,

I can understand most / all concerns. There are many valid points.

Furthermore I thought about the upgrade wizard. It is not as "simple" as 
it might look like in the first step because of the many places we may 
find TypoScript:

* sys_template: No problem

* fileadmin: included TS in text files; no problem in most cases

* typo3conf/ext/xyz: I know some installations that have all the 
configuration in an extension that is versioned by svn / git. So an 
upgrade could / will break versioning.

* typo3/ext/xyz: I can image installation that have agency specific 
configuration in globally available in an extension. These folders might 
be even not writable by the webserver (which would be a precondition for 
an working wizard).

If the upgrade wizard detects some TS that cannot be autmatically 
updates, there should be a warning in the logging (and maybe a 
downloadable logfile). For these situation we could provide a command 
line script that does the magic.

As the upgrade wizard has to be run in the install tool, this will be 
the right place for it.

With 6.0 we break many, many things. There will be probably no 
installation where a "point and click" upgrade and everything runs as 
before, is possible.

The main reason is not the conversion from "cropHTML" to "cropHtml", but 
the inconsistencies from "minifyCSS" and "compressCss" ... or was it the 
other way round.

But you are probably right that it's not worth the effort.

Ciao
Marcus


Am 14.07.12 00:41, schrieb Jigal van Hemert:
> Hi,
>
> On 13-7-2012 23:46, Philipp Gampe wrote:
>>> - the old syntax is still supported, so no sites get updated and
>>> existing snippets still work
>> I already suggested to use an upgrade wizard (or any other migration
>> tool)
>> for this task. This are simple string replacements, because all keys
>> are (or
>> at least should be) unique.
>> Only extension TS might get corrupted, but I think we can handle that as
>> well.
>
> ... and TSconfig which is added in numerous places, and locations where
> we haven't thought of.
>
> Anyway, "old syntax is still supported" doesn't mean that it is
> converted by some wizard. It means that you can use both the old and the
> new syntax in 6.0 and later.
>
>>> - snippets using the new syntax don't work in older versions of TYPO3;
>>> inexperienced users get confused
>> That might be an issue, but only 4.5 is supported for more than a year
>> once
>> TYPO3 6.0 is out.
>
> And once 4.5 is not supported anymore all existing books, websites,
> blogs and other collections will automatically use the new syntax? There
> are really old snippets of TS around which still work today.
>
>>> All in all confusion increases and consistency actually decreases.
>> IMHO only for a short time.
> I guess we have a different opinion here.
>
> Customers, integrators and especially newcomers need stability.
> Especially those who just start using TYPO3 tend to look up tutorials on
> the web or in books and get demotivated when things don't work.
> Is it really worth it to cause so much confusion just because "cropHtml"
> is better than "cropHTML"?
>
> Simply put: it's not worth it.
>