June 2018 - Developers - lists.phpmyadmin.net

Outdated version of PHP
by Julie Lopez 11 Jun '18

11 Jun '18

Hello, We just launched our new website and our developers sent us the following: One item of note — once we launched the new website, we noticed that the version of PHP that your hosting provider is running is outdated. When you log into the Dashboard in WordPress you’ll see a warning message about it. It’s pretty important to run an up-to-date version of PHP from a site performance and security standpoint. We recommend contacting your hosting provider and requesting an update to the newest version of PHP for your server. Can someone look in to this and let me know if it is possible? Thanks, Julie ________________________________________________ Julie Lopez Senior Marketing Manager Trilliant Surgical Direct: 713-388-6061 | Main: 800-495-2919, Ext. 1009 727 North Shepherd Drive, Suite 100 | Houston, TX 77007 jlopez(a)trilliantsurgical.com <mailto:jlopez@trilliantsurgical.com> | www.trilliantsurgical.com <http://www.trilliantsurgical.com/> PRIVILEGED/CONFIDENTIAL INFORMATION may be contained in this message. If you are not the addressee indicated in this message or the employee or agent responsible for delivering to addressee, you are hereby on notice that you are in possession of confidential information. Any dissemination, distribution, or copying of this e-mail is strictly prohibited. In such case, you should destroy message and kindly notify sender by reply e-mail.

1 0

Build failed in Jenkins: documentation #763
by Jenkins Daemon 10 Jun '18

10 Jun '18

1 1

Introduction of Modern Javascript GSoC 18 Project
by Piyush Vijay 08 Jun '18

08 Jun '18

Hi Community, I was working on revamping the javascript code base to make it modular as GSoC 18 project. While revamping the code base, I introduced webpack as the bundler to create a production bundle but the combined bundle coming out to be was large which was not good in terms of performance. So I have decided to use code splitting which will create small bundles and they can be used for different pages. But there are two options for ode splitting. The first one is to create multiple entry points which will generate file specific bundles having independent scope of modules imported in those specific files and the other one is dynamic imports which will split the code at dynamic import points. So I have decided to go with dynamic imports for code splitting because in this method, the bundles will have a common scope and the bundles can be downloaded at the time of need. We don't need to take care of which scripts have been downloaded. Webpack uses a JSONP function for loading the chunks asynchronously and these downloaded chunks will remain in the head of the document until the page reloads. This will ensure that chunks which are loaded once will not be loaded again. Some Important Links: https://webpack.js.org/guides/code-splitting/ https://medium.com/@piyush3079/week3-gsoc-with-phpmyadmin-41a1b7f1dd70 https://github.com/phpmyadmin/phpmyadmin/issues/14355

1 0

Build failed in Jenkins: documentation #754
by Jenkins Daemon 02 Jun '18

02 Jun '18

1 2