Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. Odd digital signage integration issue

Odd digital signage integration issue

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 36 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    S
    solutionssquad
    wrote on last edited by
    #1

    Hello all,

    I am trying to get FOP2 to run on a program called Xibo (http://xibo.org.uk/).
    It is a .net based application which can display webpages, pictures, etc.
    When I run FOP2 from inside Xibo, I get "Connecting to server, attempt number :X" and of course it never ends.

    I have added the FOP2 URL to IE as a trusted site and basically set security to none.
    I have ran Xibo as an admin.
    I have ran Xibo in XP mode.
    I have even changed flash security.

    Nothing seems to work.
    Just as an FYI, FOP runs fine outside of Xibo.

    Any hints on what I can try?

    Thanks!

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      Hi,

      Not sure if I can help you out, as i am not familiar with xibo, its client nor .net.

      FOP2 uses just one feature from flash, and it is not graphical at all, it is named "xmlsockets". That feature lets the flash component connect to a specialized server daemon to get a direct and connected path of communications between the client and the server. For that connection to happen, flash requests a policy file from the server that basically tells where it can connect to (to avoid cross site vulnerabilities). My guess is that this cross site checks are failing when embedding IE via .net. But it is just a wild guess. I am not sure if that is the case, and I am not sure how to fix it either.

      1 Reply Last reply
      0
      • S
        S
        solutionssquad
        wrote on last edited by
        #3

        Is the cross site coming from the server side or the client side?

        1 Reply Last reply
        0
        • N
          N
          nicolas
          wrote on last edited by
          #4

          Checks are done on the client side. The policy file is fed by the server via the same xmlsocket connection, and basically allows anything (unless you set restrict_host in fop2.cfg).

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups