fop2 chrome extension

[nicolas]

Just use a basic url for the popup link and see if it opens. Remember to allow popups, perhpas chrome prevents it from opening and you have to allow it.

[saltyfish]

Chrome is already set to allow popups, and version is 22.0.1229.79 m. Do I need to change anything on Elastix to allow popup link to work on FOP2 Chrome Extension?

Shawn

[nicolas]

What url did you use? It works for me, is all I can say. Does the url exists at all? The chrome extension does not check if the url is in elastix, or whatever web server you like, you can fire google searches, vtiger crm lookups, or whatever that has an URL that works in your browser.

[saltyfish]

I used:
http://www.google.com
www.google.com

What version of Chrome do you have? In Chrome setting, I've allowed Notifications and Pop-ups. The Popup link just doesn't work, with Call Popup checked and unchecked. Any other suggestions?

Shawn

[nicolas]

I tried with all versions including 23.0.1271.10 (beta). It just works, there is not much to look for, you can go to extension preferences, open the background page and look at the log. If you save a valid url, the popup should show.

[saltyfish]

Thanks for your responds. I also tried the 24.0.1284.2 beta and two other computers, but still the same. I gave up, it's not working for me.

Shawn

[nicolas]

Are you using FOP 2.26?

/usr/local/fop2/fop2_server -v

You can contact me on the live help and we can do a reverse ssh session or access your fop2 install from my own browser.

Best regards,

[toni]

Hi Nicolas,

I am also having the pop link problem. The rest features are working fine aside from the pop up link.

I already disabled my pop blocker but still it's not working. I am not sure if this helpful but looking at the plugin Inspect views: background page. I am seeing this in red text with an x icon, not sure if this is related.

This is the information on red
"Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' chrome-extension-resource:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution."

Screenshot:
http://i.imgur.com/8MdyQbE.png

Thanks
Toni

[nicolas]

Hi Toni,

What version do you have installed? 1.0.3 or 1.0.4 (released last week) ?

[toni]

Hi Nicolas,

I am using the latest 1.0.4. I tried reinstalling it again but still the same. I am getting same thing.

Thanks
Toni