Map Demo CLASSES Language

Author Message

Marco Zinn

Thursday 21 October 2010 12:11:19 pm

Hi there,

I'd like to set up a mono-lingual german site. Whenever i choose to import the demo content, i can map the demo objects' content to "German" and get nice, german content object (with english content, fine).

I'm not really interessted in the demo content, but i want the ezwebin/ezflow classes.

But, the content classes are create as ENGLISH classes. They only have the english translation. That means, that ez asks me about the content language, whenever i create content in the admin interface.

I guess, i can limit the content languages in admin, very much as they are limited in the user siteaccess (ez does not ask me for the language there). But: How do i get rid of the english (content) language completly? I cannot delete the language in the admin interface, because there are 32 classes, that are defined in english.

I've demanded multi-langual demo content (and classes) since some years ago, but it's unheard...

Marco
http://www.hyperroad-design.com

Greg McAvoy-Jensen

Thursday 21 October 2010 12:59:38 pm

Marco,

You'll need to create German translations of each of those classes, set the German translation as main, and delete the English translations. Once that's done for all 32, the system will let you delete the language.

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

Marco Zinn

Tuesday 26 October 2010 9:58:30 am

Thanks, Greg.

I knew (well: expected) this. Now, can you image how awesome it is to do this at every new installation? :(

@eZ: Can't we have multi-langual demo classes (and demo content), so we can only keep the required language at mono-lingual sites?

Marco
http://www.hyperroad-design.com

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 15 2025 09:05:22
Script start
Timing: Jan 15 2025 09:05:22
Module start 'layout'
Timing: Jan 15 2025 09:05:22
Module start 'content'
Timing: Jan 15 2025 09:05:22
Module end 'content'
Timing: Jan 15 2025 09:05:22
Script end

Main resources:

Total runtime0.0198 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0060 686.1328183.6875
Module start 'layout' 0.00600.0031 869.820352.5703
Module start 'content' 0.00910.0065 922.3906177.5625
Module end 'content' 0.01560.0041 1,099.9531751.7578
Script end 0.0198  1,851.7109 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.004623.4331140.0003
Check MTime0.00115.4125140.0001
Mysql Total
Database connection0.00083.882910.0008
Mysqli_queries0.002713.824030.0009
Looping result0.00000.060110.0000
Template Total0.003718.810.0037
Template load0.002914.430010.0029
Template processing0.00094.297710.0009
Override
Cache load0.002512.518010.0025
General
dbfile0.00125.829780.0001
String conversion0.00000.044540.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0005 secs