Strange doubling after update

[aguywithaphone]

Hello,

I recently accidentally updated Queuemetrics when I ran a yum update and things broke. Thankfully there were verbose error messages referencing settings in the configuration.properties file, however after resolving all those and logging in the ICON agent page has two headers and two sets of windows. While it seems operable, it is annoying. Has anyone else experienced, and more importantly resolved this issue?

-dude

[mirkox]

Hi there,

this is the first time I hear about that; could you share a screenshot? Also do you get any errors in the browser's console?

Mirko

[aguywithaphone]

There are no any error messages, initially there were a few about incorrect configurations, but they were verbose messages and I found the lines they referenced in the old config and copy pasted them. Below is a link to a screenshot of what is happening. This happens for all agents, but only on the agent page:

https://imagebin.ca/v/3JVFSBcI9bBN

[mirkox]

Please check into the configuration: how is set the default.crmapp property?

[aguywithaphone]

Thank you for the reply, the property is set:

# Asterisk Unique ID visibility and related callback URL associated to the icon
default.crmapp=http://server/app?agent=[A]&unique=
default.showAstClid=false

I noticed that in the old configuration it was set to:
default.crmapp=http://queuemetrics.com/sample_screen_pop.jsp?agent=[A]&unique=

however replacing the line with the one from the old configuration did not resolve the issue.

[mirkox]

The setting is fine; can you verify using the browser's inspector what page is loading the big iframe in the agent's page?

Also what's the exact version of your QM?

[aguywithaphone]

Thats a great idea to use the inspector, unfortunately I'm not sure I understand the question. I did notice there were two sets of html, head, and body tags:

https://imagebin.ca/v/3Jd1Kdwnu9lV

The version is:
Loway QueueMetrics - 16.10.13
B: 184 - 2017.03.23-08:34

[mirkox]

Hi there,

basicly QM has the possibility to integrate with a CRM and do other stuff by opening a URL in a iframe in the backgrorund of the page.

I see that your iframe is pointing to # so it's loading itself.

The property that could affect this are:

default.crmapp   (the page that opens automatically with each call, you can also pass some parameters of the call in the url; check if maybe it is defined twice)

realtime.agent_web1_url
realtime.agent_web2_url  (two custom urls)

realtime.agent_background_url  (the default background url)


Please check the above properties.


What's your version of QM btw?

[aguywithaphone]

Thank you very much, in my case none of the configuration options mentioned in the previous post were in my config file, but adding the
realtime.agent_background_url=XXX
changed the background to XXX instead of the queuemetrics agent page. Setting the
default.crmapp=YYY
changed the background to YYY when the CRM (Alt-8) option is selected.

Is it possible to disable the iframe alltogether?



Software release:   Loway QueueMetrics - 16.10.13
B: 184 - 2017.03.23-08:34
Firefox client version:   CURRENT - Install now: Firefox - Chrome
URL: 192.168.10.3:8080/qm_agaw_facade_ajax.do

 
Operating System:   O.S.: Linux - Ver: 2.6.32-696.el6.x86_64 - amd64
Java Runtime:   Version: 1.6.0_22
Vendor: Sun Microsystems Inc.
Class Version: 50.0
Java Home: /usr/local/queuemetrics/jdk1.6.0_22/jre
System path:   /usr/local/queuemetrics/tomcat/webapps/queuemetrics/WEB-INF
Storage type:   SQL Storage (Partition: P001)
Loway TPF:   Version: TPF 264p/P B:264p - 2016.11.29-16:11
Language pack:   V:2017-03-16 10:39
System time:   Java Time: 2017-04-20 12:09:45
Java Time Zone: America/New_York
MySQL Time: 2017-04-20 12:09:45.0
MySQL Time is aligned with Java Time

[mirkox]

Honestly that's really weird because I tested the same version here and can't reproduce the problem; you can't disable it but you can use the default value for the background setting:

http://10.10.5.27:8080/queuemetrics/qm/agent_page_gwt_background.jsp

replace the http://10.10.5.27:8080/queuemetrics with the correct url of your QueueMetrics

[aguywithaphone]

Perhaps it was because this instance of QM is almost 4 years old, and I have only updated sporadically (not every at every version). Anyways thanks for you help, is there a way I can mark this as resolved?