cPanel New Features

We have all being there.

You are editing something and messed your file.

Or you clicked the wrong button and deleted a very important file.

And since Linux doesn't have "undo" button, your file disappears into File's heavens where mortals are unable to access.

Enter cPanel File Restoration.

With this much-anticipated feature now available in cPanel, you can restore items from local backup files. This interface displays all of the files and directories in a backup file.

To access your backups, log in to cPanel and navigate to Home >> Files >> File Restoration.

Step 1

Once you open that interface you are presented with the list of files in your backup.

For example, if you wanted to restore a file from your public_html folder, you would click public_html.

Step 2

Then select the file that you want to restore (index.html in our case) and you are then presented with the list of dates that you can restore that file from.

Step 3

Once you choose one version to restore, you are asked to confirm before continuing.

Step 4

Note: If the file that you want to restore already exists on your account, you must select the Overwrite existing file? checkbox in order to continue the restoration. Otherwise, click Cancel.

Overwrite Verification

You also get a confirmation message once the restore is complete!

Restore cPanel File

Here is a video showing the process:


If you don’t see that option in cPanel, ask our technical support team or contact your server administrator if you are using one of our Resellers to ensure that the “Backup Manager” feature has been added to your account.


PHP New Feature

Added zlib.output_compression setting to MultiPHP INI Editor

gzip is a method of compressing files (making them smaller) for faster network transfers.

Compression allows your web server to provide smaller file sizes which load faster for your website users.

Enabling gzip compression is a standard practice since compression of your HTML and CSS files with gzip typically saves around fifty to seventy percent of the file size. This means that it takes less time to load your pages, and less bandwidth is used overall.

Previously you have to add something like this manually to your .htaccess file after wrapping it with mod_gzip module "If" statement.

mod_gzip_on Yes
mod_gzip_dechunk Yes
mod_gzip_item_include file .(html?|txt|css|js|php|pl)$
mod_gzip_item_include handler ^cgi-script$
mod_gzip_item_include mime ^text/.*
mod_gzip_item_include mime ^application/x-javascript.*
mod_gzip_item_exclude mime ^image/.*
mod_gzip_item_exclude rspheader ^Content-Encoding:.*gzip.*

Our new version of cPanel added the zlib.output_compression setting to cPanel's MultiPHP INI Editor interface (cPanel >> Home >> Software >> MultiPHP INI Editor).

This setting if enabled allows your cPanel server to transparently compress pages if the browser sends an Accept-Encoding: gzip or deflate header.

All modern browsers understand and accept compressed files and if you are not using it for some reason, your web pages are likely slower than your competitors.

cPanel's MultiPHP INI Editor

cPanel's MultiPHP INI Editor interface (cPanel >> Home >> Software >> MultiPHP INI Editor) now only shows directives that you can change. Though for security purposes, we strongly recommend that you use the provided default values, post_max_size PHP directive has been added to the interface.

To use this feature,
  • Login to cPanel
  • Navigate to cPanel >> Home >> Software >> MultiPHP INI Editor
  • Select either the Basic or Editor mode.
  • Select the location that you wish to configure from the menu. You can edit either the account's home directory or the domain's document root. The PHP directives will appear. Warnings:
    • You must exercise extreme caution when you make changes in this interface. Errors could result in non-functional PHP scripts. Only advanced users should use this interface.
    • Directives also cannot contain any the following special characters: ?{}|&~![()^"

The Editor Mode section of this interface loads the contents of the php.ini file for your selected domain if it exists. If the php.ini file does not exist, the interface loads a blank editor so that you can create your own file. Make your changes to the desired directives and click Save.

The system saves changes to both the php.ini file in the Path section of the interface and the .user.ini file. The system also saves these changes to your .htaccess file.

For example, the location of your file may be the /home/allthethings/public_html/php.ini file. The interface attempts a rudimentary validation of directive names. This does not guarantee that your PHP configuration will function. To reset your PHP settings to default values, delete the domain's or home directory's php.ini file.

We hope that these new features will give you more great options as you seek to build your dream online.

Thursday, November 9, 2017

« Back