Adlago

The file is small. But the whole possible action of this notification is a complicated process and calculation from a browser delayed loading site. IPS needs to find another solution. Here, look at the entire code that a browser needs to process before downloading m3 ... (function($,_,undefined){"use strict";ips.createModule('ips.utils.notification',function(){var supported=("Notification"in window);var sound=null;if(!ips.getSetting('disableNotificationSounds')){sound=new Howl({src:ips.getSetting('baseURL')+'applications/core/interface/sounds/notification.mp3',autoplay:false});} var hasPermission=function(){if(!supported||Notification.permission=='denied'||Notification.permission=='default'){return false;} return true;},needsPermission=function(){if(supported&&Notification.permission=='default'){return true;} return false;},permissionLevel=function(){if(!supported){return null;} return Notification.permission;},requestPermission=function(){if(supported){Notification.requestPermission(function(result){if(result=='granted'){$(document).trigger('permissionGranted.notifications');}else{$(document).trigger('permissionDenied.notifications');}});}},create=function(options){return new notification(options);},playSound=function(){try{if(!ips.getSetting('disableNotificationSounds')){sound.play();}}catch(err){}};function notification(options){this._notification=null;this._options=_.defaults(options,{title:'',body:'',icon:'',timeout:false,tag:'',dir:$('html').attr('dir')||'ltr',lang:$('html').attr('lang')||'',onShow:$.noop,onHide:$.noop,onClick:$.noop,onError:$.noop});this._options.body=_.unescape(this._options.body.replace(/&#039;/g,"'").replace(/<[^>]*>?/g,''));this._options.title=_.unescape(this._options.title.replace(/&#039;/g,"'"));this.show=function(){this._notification=new Notification(this._options.title,this._options);this._notification.addEventListener('show',this._options.onShow,false);this._notification.addEventListener('hide',this._options.onHide,false);this._notification.addEventListener('click',this._options.onClick,false);this._notification.addEventListener('error',this._options.onError,false);if(this._options.timeout!==false){setTimeout(_.bind(this.hide,this),this._options.timeout*1000);}};this.hide=function(){this._notification.close();this._notification.removeEventListener('show',this._options.onShow,false);this._notification.removeEventListener('hide',this._options.onHide,false);this._notification.removeEventListener('click',this._options.onClick,false);this._notification.removeEventListener('error',this._options.onError,false);};};return{supported:supported,hasPermission:hasPermission,needsPermission:needsPermission,permissionLevel:permissionLevel,requestPermission:requestPermission,create:create,playSound:playSound};});}(jQuery,_)); These are 600 milliseconds that delay any site, not just mine.

It should be so - but this mp3 is being loaded by every guest and this is a slow loading site. So I'm looking for a solution.

What I can not understand - please comment. notification.mp3 is initiated by the howler.core.min.js, loading is a task of the framework.js. That's good, but why does the start notification.mp3 download request lag behind by more than 600 milliseconds from the end downloading framework.js? If this process does not speed up, then what is the best way to get this resource "preload"?

PS. I'm not sure if this was any reason for poor performance, but after this change, my performance increased by 7 points - from 84 to 91 on the Lighthouse test report...

Thanks for your opinion. I described this problem to my host company and the boys there looked at this thoroughly. They solved this problem. In your command for Cron, you use this /opt/cpanel/ea-php73/root/usr/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/... They changed the command to /opt/cpanel/ea-php73/root/usr/bin/php -c /home/... and it all works like a Swiss watch ...

I have not tested with a new installation. My test site is currently with 4.4.3 beta 2. There is also this issue. I do not use plugins

A few months ago after upgrading to 4.4.x I had a problem with Memcached. Cron jobs stopped working, and in the system logs began recording in every minute - "BadMethodCallException:...from Memcached". After a lengthy analysis of my ticket, Matt advised me to switch to Redis. This then solved the issue. Before several hours, I switched my site to PHP 7.3.3. Everything worked correctly. When reviewing all the ACP functions, I noticed I should replace the command in a Cron jobs with a new addressing to ea-php73. For several hours with php 7.3.3 everything worked correctly with a command to ea-php72. After changing Cron command, the same thing happened as with Memcached. Cron stopped working and was recording every minute in System logs: "BadMethodCallException:...from Redis" I tried a lot of things, my head hurt, and I tried - I switched to Data storage File system method and Cron iobs worked normal and accurate. PS. Now I have reviewed and my test installation with 4.4.3 beta 2. The same issue exists there. Please review this - there is a constant mistake in using Redis/Memcached and it will exist in your next release.

Ask the driver to include the XSS and the police will not see anything. Still, look around who's sitting in the back seat ...

This is not good - if your pants are removed, your "GmMetrix" if it is not A ++ - which lady will test you?😀

@Mark Google is a search engine and you can not publish it there. Facebook a few days ago collapsed for several hours - I'm not saying that's exactly why. The reason is unnecessary self-confidence of developers. A sentence for everyone is right ... I already wrote it. Thank you for your comprehensive answer.

On this topic, in my ticket after many research, in version 4.4.1, @bfarber said to include a patch in the next version to fix these records errors ... Yes, however, these record log errors continue. 2S119/1 Something went wrong. Please try again. 95.216.197.231 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/14/2019 05:30 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM Adoption of the rule by a guest bot machine that made a session fix from a this bot machine. Next visit from this bot but another machine causes this error - another machine has another session guest but uses an indexed address ... Will the IPS find a solution to this?

Everyone is free to walk in his way even with the pants removed ....

I did not understand what you want in this topic. I have a position and defend it. This topic is not aimed at you, it is a team for development. They can decide whether to take it for analysis or not.

Using this option will turn off X-Frame. Do you like unsecured security?

This is easy to check and is not true. Do your security test and then say