extern/egroupware_official
1
0
Fork 0
mirror of https://github.com/EGroupware/egroupware.git synced 2024-12-02 21:07:12 +01:00
Code Issues Packages Projects Releases Wiki Activity
1e3627ad51
egroupware_official/addressbook/templates/default/index.xet

201 lines
9.7 KiB
Plaintext
Raw Normal View History

first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<?xml version="1.0"?>
<!-- $Id$ -->
<overlay>
addressbook can now group contacts by organisations (sql only atm.) and change organisational fields for all organisation members
2006-04-30 11:34:24 +02:00
<template id="addressbook.index.left" template="" lang="" group="0" version="1.3.001">
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<menulist class="bold">
some (crm) features: - filter for business country - sorting by postal code - add can create now already linked entries by specifying app/id pairs in the url (as eg. timesheet) - setting egw_info[flags][currentid] in view to allow to add already linked entries via quick add some bugfixes: - sql can now change the ownership if a user gets deleted, ldap implementation still missing, but gives no more error - photo template was not shown under some circumstances
2006-12-11 08:35:49 +01:00
<menupopup rows="1" cols="1" id="org_view" no_lang="1" statustext="Select a view" onchange="1" options="All contacts"/>
addressbook can now group contacts by organisations (sql only atm.) and change organisational fields for all organisation members
2006-04-30 11:34:24 +02:00
</menulist>
</template>
some fixes and improvments around the distribution lists: - to, cc, bcc is working again in the email-selection-popup - shortcut to directly add the whole list in the email-popup - error message that a list already exist - javascript only get's loaded if not already loaded - fix for bug #588: content of emailpopup to wide - fix for bug #713: wrong redirect creating distrib.list via popup from fmail
2007-05-25 20:20:57 +02:00
<template id="addressbook.index.right_add" template="" lang="" group="0" version="1.3.005">
<hbox>
<buttononly id="search" label="Advanced search" onclick="window.open(egw::link('/index.php','menuaction=addressbook.uicontacts.search'),'_blank','dependent=yes,width=850,height=440,scrollbars=yes,status=yes'); return false;"/>
<buttononly id="add" label="Add" statustext="Add a new contact" onclick="window.open(egw::link('/index.php','menuaction=addressbook.uicontacts.edit'),'_blank','dependent=yes,width=850,height=440,scrollbars=yes,status=yes'); return false;" class="rightPadAdd"/>
ability to insert contacts into documents, one can specify a document dir and a default document in the addressbook prefs. Addressbook then offers actions to insert (at the moment only single) contacts into that document. The default document is also shown as in extra icon for each contact in the list. Documents have to be text document including rtf, which allows to be saved as open office or word documents.
2007-06-17 15:55:43 +02:00
<description id="manual" class="rightPadAdd"/>
some fixes and improvments around the distribution lists: - to, cc, bcc is working again in the email-selection-popup - shortcut to directly add the whole list in the email-popup - error message that a list already exist - javascript only get's loaded if not already loaded - fix for bug #588: content of emailpopup to wide - fix for bug #713: wrong redirect creating distrib.list via popup from fmail
2007-05-25 20:20:57 +02:00
</hbox>
ability to insert contacts into documents, one can specify a document dir and a default document in the addressbook prefs. Addressbook then offers actions to insert (at the moment only single) contacts into that document. The default document is also shown as in extra icon for each contact in the list. Documents have to be text document including rtf, which allows to be saved as open office or word documents.
2007-06-17 15:55:43 +02:00
<styles>.rightPadAdd { width: 30px; }</styles>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</template>
fix for bug #658: Custom Fields - added user in list comes up as ID (number) Unfortunatetly this bugfix requires some corrections in the way the customfield widget is called in the templates of other apps
2007-07-11 17:43:09 +02:00
<template id="addressbook.index.rows" template="" lang="" group="0" version="1.4.002">
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<grid width="100%">
<columns>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<column/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<column/>
<column/>
<column width="60" disabled="@no_photo"/>
<column/>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<column disabled="@no_home"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<column/>
<column/>
<column disabled="@no_customfields"/>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<column/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<column width="90"/>
</columns>
<rows>
<row class="th">
<description/>
<grid spacing="0" padding="0">
<columns>
<column/>
<column/>
</columns>
<rows>
- own sorting of the list/index - preferred phone can be selected in the main-screen (not only the popup) too - polishing of the layout and labels/translations
2006-04-24 13:15:10 +02:00
<row disabled="!@order=n_fileas">
<nextmatch-sortheader span="all" label="own sorting" id="n_fileas"/>
</row>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<row disabled="!@order=n_given">
<nextmatch-sortheader id="n_given" label="Firstname"/>
<nextmatch-sortheader label="Name" id="n_family"/>
</row>
<row disabled="!@order=n_family">
<nextmatch-sortheader label="Name" id="n_family"/>
<nextmatch-sortheader id="n_given" label="Firstname"/>
</row>
<row>
- changed labels from company to organisation - using a country-selection instead of an text-input - disabled "change all members of org" if no org set
2006-07-07 01:01:29 +02:00
<nextmatch-sortheader id="org_name" label="Organisation" span="all"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</row>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<row disabled="!@order=/^(org_name|n_fileas|adr_one_postalcode|contact_modified|contact_created)$/">
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<nextmatch-sortheader id="n_family" label="Name"/>
- own sorting of the list/index - preferred phone can be selected in the main-screen (not only the popup) too - polishing of the layout and labels/translations
2006-04-24 13:15:10 +02:00
<nextmatch-sortheader id="n_given" label="Firstname" class="leftPad5"/>
</row>
<row disabled="@order=n_fileas">
<nextmatch-sortheader span="all" label="own sorting" id="n_fileas"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</row>
</rows>
</grid>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<nextmatch-header label="Category" id="cat_id"/>
<nextmatch-header label="Photo" id="photo"/>
some (crm) features: - filter for business country - sorting by postal code - add can create now already linked entries by specifying app/id pairs in the url (as eg. timesheet) - setting egw_info[flags][currentid] in view to allow to add already linked entries via quick add some bugfixes: - sql can now change the ownership if a user gets deleted, ldap implementation still missing, but gives no more error - photo template was not shown under some circumstances
2006-12-11 08:35:49 +01:00
<vbox options="0,0">
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<nextmatch-header label="Business address" id="business"/>
some (crm) features: - filter for business country - sorting by postal code - add can create now already linked entries by specifying app/id pairs in the url (as eg. timesheet) - setting egw_info[flags][currentid] in view to allow to add already linked entries via quick add some bugfixes: - sql can now change the ownership if a user gets deleted, ldap implementation still missing, but gives no more error - photo template was not shown under some circumstances
2006-12-11 08:35:49 +01:00
<nextmatch-customfilter id="adr_one_countryname" options="select-country,Country,1" class="countrySelect"/>
<nextmatch-sortheader id="adr_one_postalcode" label="zip code"/>
</vbox>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<nextmatch-header label="Home address" id="home"/>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<vbox options="0,0">
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<nextmatch-header id="tel_work" label="Business phone"/>
<nextmatch-header label="Mobile phone" id="tel_cell"/>
<nextmatch-header id="tel_home" label="Home phone"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</vbox>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<vbox options="0,0">
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<nextmatch-header id="url" label="Url"/>
<nextmatch-header label="Business email" id="email"/>
<nextmatch-header id="email_home" label="Home email"/>
</vbox>
<vbox options="0,0">
<nextmatch-header id="customfields" options="Custom fields"/>
<grid spacing="0" padding="0">
<columns>
<column/>
</columns>
<rows>
<row>
<description no_lang="1" id="customfields[$row][label]"/>
</row>
</rows>
</grid>
</vbox>
<vbox options="0,0">
<nextmatch-sortheader id="contact_created" label="Created"/>
<nextmatch-sortheader id="contact_modified" label="Last modified"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</vbox>
<hbox align="center" class="noPrint">
<description value="Actions" align="center"/>
<button image="check" label="Check all" id="check_all" statustext="Check all" onclick="toggle_all(this.form,form::name('checked[]')); return false;" needed="1" align="right"/>
</hbox>
</row>
<row class="row" valign="top">
<image label="$row_cont[type_label]" src="${row}[type]" align="center" no_lang="1"/>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<vbox options="0,0" id="${row}[id]">
- own sorting of the list/index - preferred phone can be selected in the main-screen (not only the popup) too - polishing of the layout and labels/translations
2006-04-24 13:15:10 +02:00
<description id="${row}[line1]" no_lang="1"/>
<description id="${row}[line2]" no_lang="1"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description id="${row}[org_unit]" no_lang="1"/>
<description id="${row}[title]" no_lang="1"/>
<description id="${row}[first_org]" no_lang="1"/>
</vbox>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<menulist>
<menupopup type="select-cat" options="1" id="${row}[cat_id]" readonly="true"/>
</menulist>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<image src="${row}[photo]"/>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<vbox options="0,0">
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description id="${row}[adr_one_countryname]" no_lang="1"/>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<hbox options="0,0" orient="0">
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description no_lang="1" id="${row}[adr_one_locality]"/>
fix for bug #323: Postal Code / City, Country / State fields confusing
2007-05-03 10:18:26 +02:00
<description class="leftPad5" no_lang="1" id="${row}[adr_one_region]"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description id="${row}[adr_one_postalcode]" class="leftPad5" value=" " no_lang="1"/>
</hbox>
<description no_lang="1" id="${row}[adr_one_street]"/>
<description id="${row}[adr_one_street2]" no_lang="1"/>
</vbox>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<vbox options="0,0">
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description id="${row}[adr_two_countryname]" no_lang="1"/>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<hbox options="0,0">
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description no_lang="1" id="${row}[adr_two_locality]"/>
fix for bug #948: space missing in regular addressbook view in home address
2007-06-23 09:14:27 +02:00
<description no_lang="1" id="${row}[adr_two_region]" class="leftPad5"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description id="${row}[adr_two_postalcode]" class="leftPad5" value=" " no_lang="1"/>
</hbox>
<description no_lang="1" id="${row}[adr_two_street]"/>
<description id="${row}[adr_two_street2]" no_lang="1"/>
</vbox>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<vbox options="0,0">
moved contact-data (firstname, lastname and email) from the account-table to the contact table: - all (sql) accounts have now allways a contact associated with them (account_id is added as new column to the contacts table) - contacts queries are simplefied a lot now, as no more join with the accouns-table, union and case when statesments are necessary - lot of the special handling for accounts in the contacts class is no longer needed - new contact-repository mode "sql-ldap" which additional writes all changes to the ldap repository, to allow to use it read-only from eg. thunderbird and still have the full sql speed and features within eGW (not yet fully working!) ==> requites update of API and addressbook to work (setup!)
2006-06-17 20:50:07 +02:00
<description no_lang="1" id="${row}[tel_work]" class="telNumbers" options=",$row_cont[tel_work_link],,,calling,$cont[call_popup]"/>
<description id="${row}[tel_cell]" no_lang="1" class="telNumbers" options=",$row_cont[tel_cell_link],,,calling,$cont[call_popup]"/>
<description id="${row}[tel_home]" no_lang="1" class="telNumbers" options=",$row_cont[tel_home_link],,,calling,$cont[call_popup]"/>
<description id="${row}[tel_prefered]" no_lang="1" options=",$row_cont[tel_prefered_link],,,calling,$cont[call_popup]"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</vbox>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<vbox options="0,0">
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<description options=",,1" class="fixedHeight" no_lang="1" id="${row}[url]"/>
<description options=",@${row}[email_link],,,_blank,$row_cont[email_popup]" class="fixedHeight" id="${row}[email]" no_lang="1"/>
<description options=",@${row}[email_home_link],,,_blank,$row_cont[email_home_popup]" class="fixedHeight" id="${row}[email_home]" no_lang="1"/>
</vbox>
fix for bug #658: Custom Fields - added user in list comes up as ID (number) Unfortunatetly this bugfix requires some corrections in the way the customfield widget is called in the templates of other apps
2007-07-11 17:43:09 +02:00
<customfields-list rows="1" cols="1" id="$row" class="customfields"/>
adaption for the new nextmatch feature plus some nice extra columns
2007-03-07 13:31:48 +01:00
<vbox options="0,0">
<date-time id="${row}[created]" readonly="true" class="noWrap"/>
<menulist>
<menupopup type="select-account" id="${row}[creator]" readonly="true"/>
</menulist>
<date-time id="${row}[modified]" readonly="true" class="noBreak"/>
<menulist>
<menupopup type="select-account" id="${row}[modifier]" readonly="true"/>
</menulist>
</vbox>
fixed not shown customfields in addressbook index, if a not set one is in before
2006-10-26 15:40:47 +02:00
<hbox options="0" class="noPrint" orient="0">
ability to insert contacts into documents, one can specify a document dir and a default document in the addressbook prefs. Addressbook then offers actions to insert (at the moment only single) contacts into that document. The default document is also shown as in extra icon for each contact in the list. Documents have to be text document including rtf, which allows to be saved as open office or word documents.
2007-06-17 15:55:43 +02:00
<button id="document[$row_cont[id]]" image="new" label="Insert in document"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<image options="addressbook.uicontacts.view&amp;contact_id=$row_cont[id]" label="View" src="view"/>
<button image="edit" label="Edit" onclick="window.open(egw::link('/index.php','menuaction=addressbook.uicontacts.edit&amp;contact_id=$row_cont[id]'),'_blank','dependent=yes,width=850,height=440,scrollbars=yes,status=yes'); return false;" id="edit[$row_cont[id]]"/>
<button id="delete[$row_cont[id]]" image="delete" label="Delete" statustext="Delete this contact" onclick="return confirm('Delete this contact');"/>
<checkbox id="checked[]" options="$row_cont[id]" statustext="Select multiple contacts for a further action" align="right"/>
</hbox>
</row>
</rows>
</grid>
</template>
<template id="addressbook.index" template="" lang="" group="0" version="1.3.001">
<grid width="100%">
<columns>
<column/>
<column/>
</columns>
<rows>
<row disabled="!@msg">
<description span="all" class="redItalic" align="center" id="msg" no_lang="1"/>
<description/>
</row>
<row disabled="1">
addressbook can now group contacts by organisations (sql only atm.) and change organisational fields for all organisation members
2006-04-30 11:34:24 +02:00
<template id="addressbook.index.left"/>
some fixes and improvments around the distribution lists: - to, cc, bcc is working again in the email-selection-popup - shortcut to directly add the whole list in the email-popup - error message that a list already exist - javascript only get's loaded if not already loaded - fix for bug #588: content of emailpopup to wide - fix for bug #713: wrong redirect creating distrib.list via popup from fmail
2007-05-25 20:20:57 +02:00
<template align="right" id="addressbook.index.right_add"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</row>
<row>
<nextmatch options="addressbook.index.rows" id="nm" span="all"/>
</row>
<row class="noPrint">
<button id="add" label="Add" statustext="Add a new contact" onclick="window.open(egw::link('/index.php','menuaction=addressbook.uicontacts.edit'),'_blank','dependent=yes,width=850,height=440,scrollbars=yes,status=yes'); return false;"/>
<hbox align="right">
- own sorting of the list/index - preferred phone can be selected in the main-screen (not only the popup) too - polishing of the layout and labels/translations
2006-04-24 13:15:10 +02:00
<checkbox id="use_all" label="whole query" onchange="if (this.checked==true &amp;&amp; !confirm('Apply the action on the whole query, NOT only the shown contacts!!!')) this.checked=false;" statustext="Apply the action on the whole query, NOT only the shown contacts!!!"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
<menulist>
small js change for the selectbox in index
2006-04-26 23:27:22 +02:00
<menupopup onchange="if (this.value != '') { this.form.submit(); this.value=''; }" options="Select an action or addressbook to move to..." no_lang="1" id="action" statustext="Select an action or addressbook to move to"/>
first version / step to the new 1.4 addressbook: - User accounts are an own addressbook now - every user and group (can) have an own addressbook - for groups the accessrights no longer depend on the creator - new acl for adding into an addressbook - all addressbooks can be displayed together (eg. accounts mixed with personal and group AB's) - some useful new fields (photo, private cellphone, ...) and some obscure ones have been removed - db update puts all contacts in the owners personal addressbook (further manual migration tools will follow), thought the UI already allows to mass-move them into a group-addressbook - group addressbooks in SQL are created by making a group-grant for addressbook (like filemanger) - Warning: all import/export/xmlrpc/syncml stuff and other apps accessing the addressbook is broken until the contacts class in the API gets fixed! - it depends on further updates of etemplate, phpgwapi, admin! ==> it's pretty cool (specialy the foto's), but NOT ready for a production server !!!
2006-04-23 16:40:31 +02:00
</menulist>
<button image="arrow_ltr" label="Check all" id="check_all" statustext="Check all" onclick="toggle_all(this.form,form::name('nm[rows][checked][]')); return false;" needed="1" class="checkAllArrow"/>
</hbox>
</row>
</rows>
</grid>
</template>
</overlay>
Reference in New Issue Copy Permalink