Print

[lamama]

this is a question very close to "support", so just ignore if its not ok to ask.


The DevTeam has decided to drop the feature of setting alternative file prefixes.

Usually I use custom prefixes and would like to keep it that way.
I prefer 3-letter prefixes like "thn_" and "pre_" (for "preview") instead of "thumb_" and "normal_".

Is 1.5.x (internally) still supporting alternative prefixes?
Or are there problems waiting for me after upgrading to 1.5.x?

[Paver]

Yes, 1.5.x still uses the config options internally.  From the docs:

This feature is deprecated in cpg1.5.x or better and can no longer be configured, since it only lead to end user confusion. If you performed a fresh install or if you have never changed this prefix, the option won't show through. Only for those who have actually changed this option and have a config setting that differs from the default prefix, the text field will show at all. If this is the case for you: you're strongly encouraged to change this back to the default value to avoid possible issues in future versions.

It's a one-way option.  If you upgrade and you have a non-default value, you'll see the config options on the admin page.  If you set them to default, the options disappear.  But the config options are used internally, so you could modify the database to change to non-default values and everything will use whatever you set in the config options.

The warning about future versions applies, but I don't think anyone has any plans yet to make this option non-operational in future versions.

[Joachim Müller]

Moving from  "cpg1.5 Testing/Bugs" to support board.

[lamama]

Ah, thanks a lot. Haven't actually tested it yet, will do in a few days I guess.

Classic case of RTFM.