Add translation policies, versions and direct language edit

«

Previous topic

|

|

Next topic

»

Author	Message
Tony Wood	Tuesday 08 February 2005 8:53:27 am This is a suggestion for multi-lingual sites. 1. Can you add a policy for each language. i.e. content\|edit\|english or content\|edit\|french etc. Basically we need a method of locking down security per translation. Currently this is not possible. 2. Can you add a direct language edit feature. This will prevent people from having to edit the english version first. A direct edit is needed to speed up this process. 3.Can you please split the version history per language. Currently if a user selects a previous language version it affect all languages. This really needs to be locked down to a single language otherwise chaos ensues. These would really help in multi-lingual site development. Tony Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future
Tomek Klaudel	Tuesday 08 February 2005 10:40:08 pm +1 vote for this
Gabriel Ambuehl	Wednesday 09 February 2005 4:15:29 am And while we're at it: replacing EUR with USD without any currency conversion of the amount isn't exactly what localization is all about. A factor should be used for conversion between different currencies. The list with the factors could then be updated via whatever means one can conceive (webservices would help). Visit http://triligon.org
Tony Wood	Tuesday 22 February 2005 4:24:15 am As an addition can you please make Drafts language specific. You can get into a real mess if they are not. Tony Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future

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 31 2025 01:28:12
Script start
Timing:	Jan 31 2025 01:28:12
Module start 'layout'
Timing:	Jan 31 2025 01:28:12
Module start 'content'
Timing:	Jan 31 2025 01:28:12
Module end 'content'
Timing:	Jan 31 2025 01:28:12
Script end

Main resources:

Total runtime	0.0212 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0047	588.3906	151.2422
Module start 'layout'	0.0047	0.0035	739.6328	220.7500
Module start 'content'	0.0082	0.0112	960.3828	1,001.7734
Module end 'content'	0.0194	0.0017	1,962.1563	33.9922
Script end	0.0212		1,996.1484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	11.8293	14	0.0002
Check MTime	0.0011	5.0996	14	0.0001
Mysql Total
Database connection	0.0007	3.3952	1	0.0007
Mysqli_queries	0.0018	8.4082	3	0.0006
Looping result	0.0000	0.0416	1	0.0000
Template Total	0.0013	6.2	1	0.0013
Template load	0.0010	4.7623	1	0.0010
Template processing	0.0003	1.3716	1	0.0003
Override
Cache load	0.0007	3.3480	1	0.0007
General
dbfile	0.0005	2.5464	8	0.0001
String conversion	0.0000	0.0326	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs