Bug #157

Some extensions do not get reported, even when selected for reporting

Added by tshif over 2 years ago. Updated about 1 year ago.

Status:Feedback Start:06/24/2009
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:-
Target version:Customer Service Reporting Module - Future Versions

Description

Some extensions do not get reported, even when selected for reporting.
Example, A user has both extension 105 and 205, both are selected for reporting. Only 105 is reported.

History

Updated by tshif over 2 years ago

  • Assigned to set to jacobsj

Updated by tshif over 2 years ago

Jeremy - do you have any comment on this ?

Updated by TheShniz over 1 year ago

As best as I can tell:

1.) It will NOT report on extensions that make no calls (meaning you won't get a blank report)
2.) It will NOT report to the supervisor UNLESS the user ALSO has an email listed on the extension
3.) It will ONLY report on extensions with a vmcontext of 'default' (this is very unfortunate)

You can set debug to 'true' on line 18 of cron/every_week.php AND then run the report in shell login with 'php /var/www/html/admin/modules/csreporting/cron/every_week.php' ... this will show you the extension directory as the script sees it.

Updated by TheShniz over 1 year ago

Regarding # 3, an ugly workaround:

You can duplicate lines 81-368 of cron/every_week.php to line 369 (immediately following the block of code), and change the first line from default to whatever vmcontext you wanted. Like I said, this is the quick & ugly way... the correct way would be to create a loop taking into account more than one vmcontext.

Such that...
foreach($vmconf['whatever'] as $val)

Updated by tshif about 1 year ago

  • Status changed from New to Feedback
  • Assigned to deleted (jacobsj)

I wonder if there is a way to determine what current vmcontexts are in use, and then iterate through them all.

Maybe this would be a BAD plan - and what we need to do is allow the admin to input a list of the valid contexts?

Also available in: Atom PDF