Thread Details
  • State Verified Answer
  • Replies 12 replies
  • Subscribers 319 subscribers
  • Views 2621 views
  • Users 0 members are here
Forum Actions
Related

7.7 Custom entrypoint randomly redirects to index instead of actual entrypoint

ted moriello

I have a custom entrypoint that I installed via the instructions from the 7.7 developer guide.  The entrypoint is a popup window tied to a custom action button in the accounts module.  Below is my JS function that pops up the custom entrypoint.  It will work for a few hours, then it starts popping open the window but redirects to dashboards instead.  At this point it will intermittently work.  Sometimes the correct window opens, most of the time it wont.  A quick repair and rebuild temporarily fixes the issue but then it comes right back an hour or so later.  

order_history_popup: function() {
var account_id = this.model.get('id');
window.open('index.php?entryPoint=orderhistorypopup&account_id='+ account_id, 'Order History', 'width=900,height=680,scrollbars=yes,fullscreen=yes');

}

  • 0 in reply to Chad Hutchins

    I guess this depends on what you mean when you say "act like entry points currently do".  I have 2 types of entrypoints.  I have some popover windows that display data as web pages and I also have some arbitrary code which does not display any results.  

    If you look at the documentation 7.8 Endpoints it explains some of what endpoints can do.  There is an authentication setting called ('noLoginRequired' => false).  I have never tested this but if it accepts a value of false, it must accept a value of true.  I cant comment on what kind of security implications that would have though.  You'd have to test it and play around. 

  • 0 in reply to ted moriello

    Thanks ted moriello and André Lopes. 

    Some integrations require a non-authenticated endpoint to utilize webhooks. Webhooks are the best way for a 3rd party service to easily push data to Sugar. That's why an authenticated endpoint would be needed.

    I'll have to give Ted's solution a look. If the noLoginRequired parameter works like it says in the docs, that should be exactly what we need. 

    Thanks again!