Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
mflorell wrote:cd /usr/src/astguiclient/trunk
svn update
perl install.pl
read the UPGRADE doc to see what has changed since your current version
And make sure you run the upgrade on the database!
Then kill all of the screen sessions(don't do this while you are in production of course)
Start Asterisk back up with the start_asterisk_boot.pl script
Then you should be good to go.
If someone paid for it ... it would be there. The Vicidial Group is the ONLY company capable of guaranteeing that such development will end up IN the code for the next release. And when someone pays them to be sure it's there ... it is.dspaan wrote:Do you mean that if you select 'Lists: ALL' you cannot guarantee the fields will be the same?
If yes, then why isn't it possible to export the custom headers if i select a specific list when exporting the calls.
Downloading the list would be an option for me if it contained 'length_in_sec' but it doesn't
williamconley wrote:and you're saying this same field will display and allow editing if you do it the other way? (but if you change to display it breaks?)
williamconley wrote:so dig into the php and find it
and / or post it in the issue tracker as a bug. (with specific detail on how to cause it)
i'd probably recommend testing it with a few more fields first (this is a built-in field ... does the same thing happen with a custom field? what about a date field? do some work and others not? or ALL display functions are down?)
240c240,241
< $field_HTML .= "$A_field_default[$o]\n";
---
> if (strlen($A_field_value[$o]) < 1) {$A_field_value[$o] = $A_field_default[$o];}
> $field_HTML .= "$A_field_value[$o]\n";
Users browsing this forum: No registered users and 37 guests