Content Fusion Pane Silently Fails to Connect

Having trouble accessing the Oxygen Content Fusion platform or installing the server solution? Got a bug to report? Post it all here.
jmorales
Posts: 93
Joined: Tue Oct 30, 2018 9:47 pm

Content Fusion Pane Silently Fails to Connect

Post by jmorales »

Hi,
We're running Oxygen Author XML 24.0 with Content Fusion 3.0. The Content Fusion Tasks Manager pane does nothing when I click Connect. There is no error message. Further, nothing happens if I click the profile icon in the Content Fusion Tasks Manager pane. On the other hand, if I go to Options > Preferences > Plugins > Oxygen Content Fusion Connector and click Test Connection, it says "Found an Oxygen Content Fusion server (version 3.0) running at: <our http address>". Also, in a web browser I can go to Content Fusion and log on successfully. The problem is new, but I haven't changed any software levels or configuration on my laptop recently.
To try to fix the problem, I uninstalled and reinstalled the Content Fusion Connector; rebooted my laptop; then uninstalled and reinstalled Oxygen Author XML 24.0. None of this helped.
The Content Fusion details are Version 22.1, Build ID 2020062223/2020063002.
Other writers on my team are not experiencing this problem.
Thanks in advance for any suggestions.
cristi_talau
Posts: 496
Joined: Thu Sep 04, 2014 4:22 pm

Re: Content Fusion Pane Silently Fails to Connect

Post by cristi_talau »

Hello,

You can try to enable verbose logging in Oxygen XML Editor [1] to see if there is any error in the logs.
Otherwise, you can try to use the "Help" > "Report Problem..." action to send us information about your platform (e.g. OS, java version, etc.).

Best,
Cristian

[1] https://www.oxygenxml.com/doc/versions/ ... -form.html
mihaela
Posts: 490
Joined: Wed May 20, 2009 2:40 pm

Re: Content Fusion Pane Silently Fails to Connect

Post by mihaela »

Hello,

There was a problem when Oxygen Content Fusion Connector version 4.3.0 was used in Oxygen XML Editor version 24.0 related to the logging mechanism. The problem reported here was fixed after we relesed a new add-on (version 4.3.1) that solved the logging problem.

Best Regards,
Mihaela
Mihaela Calotescu
http://www.oxygenxml.com
Post Reply