• Using traditional JS libraries as modules
• Traditional scripts
• Third-party assets

Thanks a lot Nikolai,

I am trying to use Traditional scripts but how to load external js. I used to load "links" in head this way.

elgg_register_plugin_hook_handler('head', 'page', 'favicon_head');

function favicon_head(\Elgg\Hook $hook) {

$data = $hook->getValue();

$data['links']['apple-touch-icon'] = [

'rel' => 'apple-touch-icon',

'href' => elgg_get_simplecache_url('favicon_override/favicon-128.png'),

];

return $data;

}

How to load non AMD javascript using elgg_register_plugin_hook_handler('head', 'page', $callback);

Regards,

Is this something related with? 

• https://webmasters.stackexchange.com/a/128680
• https://www.chromium.org/updates/same-site/faq

You are saying your session is 'destroyed'. I think you should investigate if this is truly the case. You need to confirm if your session cookie is still available. If so, could there be a reason that the session is 'removed'? Sessions (and also the session cookie) have a limited lifetime. 

There might also be another reason that the session is 'reset'. You can check that by looking at the identifier in the session cookie. If that changes, something reset the session. This normally only happens when a user logs in/out.

Be aware that session data is not copied from a logged out user to a logged in user. So if you have done something in your session as a logged out user and that user logs in, he/she loses the session data (as a new session is generated on login). If you need logged out user session data transferred to the logged in user, you need to copy this somewhere in your code.

Hi Jeroen,

This is not a login / logout issue. This is exactly how it happens

1. User logs in to elgg website (normal user login)
2. Logged in user clicking on the "Proceed to payment" button (within elgg site)
3. This will submit the form to the payment gateway website, with a hidden callback url parameter (which is a url in elgg website)
4. Once payment is processed / cancelled, payment gateway sends the userback to the callback url (in the same browser); but randomly the users cookie is getting changed and user is now logged out of the system.

This is the exact problem they mentioned in the stackexchange webmaster link. Is this related with the same-site issue?