Topic
  • 9 replies
  • Latest Post - ‏2015-07-15T14:10:30Z by PappyBoyington
SystemAdmin
SystemAdmin
7615 Posts

Pinned topic Coach is not viewed properly if accessed through url

‏2013-02-28T12:48:05Z |
Hi,

I try to start a human service , including some nested services , through url in an email. I manage to start the service and view the coach through the url but view of the coach is different than it is in process portal.

Any idea to solve it?

Thanx
Updated on 2013-03-06T03:21:20Z at 2013-03-06T03:21:20Z by SystemAdmin
  • kolban
    kolban
    3322 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-02-28T14:07:46Z  
    In what way is the coach visual different? Perhaps a screen shot of the two would be useful?

    Neil
  • SystemAdmin
    SystemAdmin
    7615 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-03-01T07:51:07Z  
    this is how it is viewed in portal.
  • SystemAdmin
    SystemAdmin
    7615 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-03-01T07:53:13Z  
    and this is how it is viewed when accessed through url posted in the mail.

    thanks for help
  • barsa4ever
    barsa4ever
    100 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-03-01T07:58:00Z  
    and this is how it is viewed when accessed through url posted in the mail.

    thanks for help
    And what about addresses in address bar in your browser?
    We faced pretty the same problem when tried to browse coaches through ip address instead of url.
    AFAIK it's about css files. For some reason it hust won't load.
  • SystemAdmin
    SystemAdmin
    7615 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-03-01T08:07:18Z  
    this is url i use
    "http://localhost:9080/teamworks/process.lsw?zWorkflowState=1&zTaskId=" +taskIdCut
    this is what is on browser

    http://localhost:9080/teamworks/fauxRedirect.lsw?applicationInstanceId=undefined&zWorkflowState=2&zTaskId=t2960&applicationId=1&zComponentName=Coach&zComponentId=3003.1c13e0b1-069e-4f94-baa8-d011f098827a&zDbg=0
  • barsa4ever
    barsa4ever
    100 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-03-01T08:17:38Z  
    And what about addresses in address bar in your browser?
    We faced pretty the same problem when tried to browse coaches through ip address instead of url.
    AFAIK it's about css files. For some reason it hust won't load.
    And is there any error messages in developer console in browser?
  • SystemAdmin
    SystemAdmin
    7615 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-03-01T09:16:02Z  
    SEC7113: CSS was ignored due to mime type mismatch

    login.jsp

    if the user is not authenticated and logs in then it is viewed properly.
  • SystemAdmin
    SystemAdmin
    7615 Posts

    Re: Coach is not viewed properly if accessed through url

    ‏2013-03-06T03:21:20Z  
    SEC7113: CSS was ignored due to mime type mismatch

    login.jsp

    if the user is not authenticated and logs in then it is viewed properly.
    I can't tell if you have fixed your issue or not. The UI you posted is what you get if the URLs in your TeamworksConfigurationRunning.xml file cannot be resolved by the client. I've ususally seen this when the server is installed with a short name that the client cannot resolve, or, in the case of a local install, installed against an IP assigned by a DHCP server that then changed later.

    Andrew Paier | Director of Special Operations | BP3 Global, Inc. www.bp-3.com
  • PappyBoyington
    PappyBoyington
    1 Post

    Re: Coach is not viewed properly if accessed through url

    ‏2015-07-15T14:10:30Z  

    This is happening more frequently, either due to new browser versions (especially IE10 and IE11) or Notes 9.x.  There are several fixes out there for other platforms.  In Domino, this can occur with older legacy applications that use text to include CSS or JS files in the "HTML Head Content" section of the classic Notes form.  I was able to fix this by eliminating this old text, and using Insert Resource to place CSS files in the HTML Head section, and JavaScript libraries in JS Header section instead.  Hope this helps.