-
☆ A M B ☆
- 24,524 Posts
What's the best way to update? Just download the new package and install it from local?
yes.
And don't forget to go to the MIGX-CMP package-manager
put in package name: 'migxmultilang' and click the button 'add Fields' under the tab 'add Fields'
This does add any new fields in the db-schema to the table (and the map-files)
-
☆ A M B ☆
- 24,524 Posts
Oh pooh! That'll teach me to pay more attention. My carefully crafted template in the mml_resourceTemplate got overwritten! I knew I should have configured a custom chunk for that!
-
☆ A M B ☆
- 24,524 Posts
Question. Is there any reason not to use [[*id]]? Or is there a reason to always use the placeholders [[+id]]?
[[[[*id:is=`1`:then=`$homeblocks`]]]]
There isn't.
As long, as they are untranslated fields, you can allways use the normal Resourcefield/TV - tags.
But.
If you have translated fields inside
they may not be translated, because
may be parsed outside of mmlCache
And, if you have translated stuff inside chunks, they need to be called uncached
-
☆ A M B ☆
- 24,524 Posts
I'm just taking baby steps right now, but that's what I wanted to know. So as far as the template (chunk) itself goes, when checking which resource it is in the output modifier, [[*id]] will work as well as [[+id]]. I kind of like the thought of keeping these things separated, using the placeholders where the translated fields are used, but using regular field tags when it's something like id, createdon, createdby, etc. where translation isn't done.
-
☆ A M B ☆
- 24,524 Posts
huhu?
-
☆ A M B ☆
- 24,524 Posts
That was definitely startling, for a few minutes I was trying to figure out how somebody could have hacked my localhost web server! I hadn't noticed it at first - my eyes are getting worse all the time.