Options Advanced mode

The advanced options are only shown when the installer mode is set to "Advanced." This section allows users to change or set advanced options, configure additional database settings and set other configuration options in the wp-config.php file.

Advanced Tab

These are the advanced options for advanced users.
Option Details
Processing
Extraction
Mode
Manual Archive Extraction
Set the Extraction value to "Manual Archive Extraction" when the archive file has already been manually extracted on the server. This can be done through your host's control panel such as cPanel or by your host directly. This setting can be helpful if you have a large archive file or are having issues with the installer extracting the file due to timeout issues.

PHP ZipArchive
This extraction method will use the PHP ZipArchive code to extract the archive zip file.

PHP ZipArchive Chunking
This extraction method will use the PHP ZipArchive code with multiple execution threads to extract the archive zip file.

Shell-Exec Unzip
This extraction method will use the PHP shell_exec to call the system unzip command on the server. This is the default mode that is used if it's available on the server.

DupArchive
This extraction method will use the DupArchive extractor code to extract the daf-based archive file.
Server
Throttling
If the current host is a budget host that monitors CPU usage, then users might want to consider checking this box to help slow down the process and not kick off any high-usage monitors.
Extraction Flow
Archive Action Extract files over current files
The existing site files will be overwritten with the contents of the archive.zip/daf.

Pro Remove WordPress core and content and extract
The existing WordPress core files and WordPress content directory will be removed, and then the archive will be extracted.

Pro Remove all files except add-on sites and extract
All files except an add-on site will be removed, and then the archive will be extracted. An add-on site is a site/domain that is stored in a directory off of your main site that has been "added on" to your main hosting account. For instance, when you purchased a hosting account it could be for a.com. Then after that, you decided to add b.com and c.com to the same hosting account. The structure of this setup is often the following although it can vary some:
  • /public_html - contains files for a.com
  • /public_html/b.com - contains files for b.com
  • /public_html/c.com - contains files for c.com
The directories /public_html/b.com and c.com contain the files for the add-on sites b.com and c.com (so the option above means that b.com and c.com would be preserved and not deleted when you installed to a.com)
Skip Files Extract all files
Extract all files from the package archive. This option is selected by default.

Pro Skip extraction of WordPress core files
Extract all files except WordPress core files. Choose this option to extract only the wp-content folder and other non-core WordPress files and directories.

Pro Skip extraction of WordPress core files and plugins/themes existing on host
Extract all files except WordPress core files and existing plugins/themes on the current host.

Pro Extract only media files and new plugins and themes
Extract all media files, new plugins, and new themes. The installer will not extract plugins and themes that already exist on the destination site.
File Times When the archive is extracted it should show the current date-time or keep the original time it had when it was built. This setting will be applied to all files and directories. Note: Setting the Original time is currently only supported when using the ZipArchive Format.
File
Permissions
Switch on and set permissions in either octal or symbolic values to assign permissions to files. This option is not available on Windows machines.
Directory
Permissions
Switch on and set permissions in either octal or symbolic values to assign permissions to directories. This option is not available on Windows machines.
Configuration Files
WordPress
wp-config
Do nothing
This option simply does nothing. The wp-config file does not get backed up, renamed, or created. This advanced option assumes you already know how it should behave in the new environment. This option is for advanced technical persons.

Modify original
This is the default recommended option which will modify the original wp-config file.

Create new from wp-config sample
This option creates a new wp-config file by modifying the wp-config-sample.php file. The new wp-config.php file will behave as if it was created in a fresh, default WordPress installation.

Apache
.htaccess
Do nothing
This option simply does nothing. The .htaccess is not backed up, renamed, or created. This advanced option assumes you already have your .htaccess file set up and know how it should behave in the new environment. When the package is built it will always create an .htaccess file at this location: /dup-installer/original_files_[HASH]/.htaccess Since the file is already in the archive file it will show up when the archive is extracted.

Retain original from Archive.zip/daf
This option simply copies the /dup-installer/original_files_[HASH]/.htaccess file to the .htaccess file. Please note this option will cause issues with the install process if the .htaccess is not properly set up to handle the new server environment. This is an advanced option and should only be used if you know how to properly configure your .htaccess configuration.

Create New
This is the default recommended option which will create a new .htaccess file. The new .htaccess file is streamlined to help guarantee no conflicts are created during install.

Notes: Inside the archive.zip or archive.daf will be a copy of the original .htaccess (Apache) file that was set up with your packaged site. The .htaccess file is copied to /dup-installer/original_files_[HASH]/source_site_htaccess. When using either "Create New" or "Retain original from Archive.zip/daf" an existing .htaccess file will be backed up to a /wp-content/backups-dup-lite/installer/original_files_[HASH]/source_site_htaccess. This change will not made until the final step is completed, to avoid any issues the .htaccess might cause during the install
General
php.ini, .user.ini,
web.config
OVERVIEW
When the archive is built it will always create an original backup of the php.ini, .user.ini, and web.config files ("Config Files") if they exist. The backups will be in the following location within the archive file without an extension. Original File Backups
archive.zip|daf/dup-installer/original_files_[HASH]/[location]_phpini
archive.zip|daf/dup-installer/original_files_[HASH]/[location]_userini
archive.zip|daf/dup-installer/original_files_[HASH]/[location]_webconfig
If there are "Config Files" on the new server, backups may also optionally be created. Backup [location] is defined by the following:
  • source_site Backup of original file when the archive was created on the source host
  • installer_host Backup of original file before the installer starts on active host

ACTIONS
Do nothing
This option performs no actions and assumes you already have your configuration files set up properly; either on the server or in the archive. If the same "Config Files" exist in both the deploy directory and the archive, then the archive files will overwrite any configuration files that exist at the same location in the archive.


Retain original from Archive.zip/daf
  1. Moves any existing "Config Files" on the new host to the following location: /dup-installer/original_files_[HASH]/installer_host_[CONFIG-TYPE]
    An existing "Config File" resides on the server before the archive is extracted or step 1 is ran.
  2. The installer last step copies all "Config Files" from the archive backups to the correct location on the new host. They are copied from this location:
    /dup-installer/original_files_[HASH]/source_site_[CONFIG-TYPE]

Reset
  1. Moves any existing "Config Files" on the new host to the following location: /dup-installer/original_files_[HASH]/installer_host_[CONFIG-TYPE]
    An existing "Config File" resides on the server before the archive is extracted or step 1 is ran.
  2. If any "Config Files" already exist in the archive they will be deployed "as is" to the location that matches the archive file structure.
General
Logging The level of detail that will be sent to the log file (installer-log.txt). The recommended setting for most installs should be "Light." Note if you use Debug the amount of data written can be very large. Debug is only recommended for support.
Cleanup Pro Remove disabled plugins/themes
Remove all inactive plugins and themes when installing site. Inactive users will also be removed during subsite to standalone migrations.

Pro Remove users without permissions
Removes users that currently do not have any permissions associated with their accounts.
Safe Mode Safe mode is designed to configure the site with specific options at install time to help overcome issues that may happen during the install where the site is having issues. These options should only be used if you run into issues after you have tried to run an install.

Disabled
This is the default. This option will not apply any additional settings at install time.

Enabled
When enabled the safe mode option will disable all the plugins at install time. Note: When this option is set you will need to manually re-enable the plugins that need to be enabled after the install from the WordPress admin plugins page.


Database Tab

These are the advanced options for database configuration.
Option Details
Table Prefix Pro This option allows changing the table prefix to other than the package creation site's table prefix. The table prefix is the value placed in the front of your database tables. It is possible to have multiple installations in one database if you give each WordPress site a unique prefix.
Mode Modes affect the SQL syntax MySQL supports (and others such as MariaDB) . This setting performs various data validation checks. This makes it easier to use MySQL in different environments and to use MySQL together with other database servers. It is very useful when running into conversion issues. The following options are supported:
  • Default: This is the recommended setting to use. It will use the current Database mode setting.
  • Disable: This will prevent the database engine from running in any mode.
  • Custom: This option will allow you to enter a custom set of mode commands. See the documentation link below for options.
For a full overview please see the MySQL mode and MariaDB mode specific to your version. To add a custom setting enable the Custom radio button and enter in the mode(s) that needs to be applied.
Processing Chunking mode
Split the work of inserting data across several requests. If your host throttles requests or you're on a shared server that is being heavily utilized by other sites then you should choose this option. This is the default option.

Single step
Perform data insertion in a single request. This is typically a bit faster than chunking, however it is more susceptible to problems when the database is large or the host is constrained.
Create Run all CREATE SQL statements at once. This option should be checked when source database tables have foreign key relationships. When choosing this option there might be a chance of a timeout error. Uncheck this option to split CREATE queries in chunks. This option is checked by default.
Objects Allow or Ignore objects for "Views," "Stored Procedures," "Functions" and "DEFINER" statements. Typically the defaults for these settings should be used. In the event you see an error such as "'Access denied; you need (at least one of) the SUPER privilege(s) for this operation" then changing the value for each operation should be considered.


URLs & Paths Tab Pro

In the tab "URLs & Paths," you can read the current path of all the various path configurations for the WordPress site. These are advanced options that should only be edited if you know the correct path. These options are editable in the Pro version. These paths and URLs are set automatically by the package installer. You can set these paths and URLs manually. If you are changing it, please make sure you are putting the right path or URL.


Benefits of Using a Face Serum in Your Skincare Routine
Home Lifestyle Benefits of Using a Face Serum in Your Skincare Routine

Benefits of Using a Face Serum in Your Skincare Routine

0
169
Benefits of Using a Face Serum in Your Skincare Routine

Introduction

If you’ve ever struggled with dull skin, acne, fine lines, dark spots, or dryness, you’re not alone. These are among the most common skincare concerns people experience regardless of age or skin type. While cleansers and moisturizers form the foundation of a skincare routine, they may not always provide the targeted treatment your skin needs.

That’s where face serums come in. Packed with concentrated active ingredients, face serums are designed to penetrate deeper into the skin and address specific concerns more effectively than traditional creams or lotions. Whether your goal is brighter skin, improved hydration, reduced wrinkles, or fewer breakouts, the right serum can make a noticeable difference.

We will explain what a face serum is, its key benefits, how to choose one based on your skin type, and the best way to apply it for maximum results.

What Is a Face Serum?

A face serum is a lightweight skincare product formulated with a high concentration of active ingredients. Unlike moisturizers, which primarily create a protective barrier to lock in moisture, serums are designed to deliver targeted ingredients deep into the skin.

Their smaller molecular structure allows them to absorb quickly, making them ideal for treating specific skin concerns.

Some of the most common active ingredients found in face serums include:

Vitamin C

  • Brightens dull skin
  • Reduces pigmentation
  • Protects against environmental damage
  • Boosts collagen production

Hyaluronic Acid

  • Provides intense hydration
  • Helps retain moisture
  • Makes skin appear plump and smooth
  • Supports the skin barrier

Niacinamide

  • Controls excess oil
  • Minimizes enlarged pores
  • Reduces redness
  • Improves uneven skin tone

Retinol

  • Reduces fine lines and wrinkles
  • Speeds up skin renewal
  • Improves skin texture
  • Helps prevent acne

Salicylic Acid

  • Unclogs pores
  • Reduces acne
  • Controls oil production
  • Prevents future breakouts

Each ingredient serves a unique purpose, allowing you to customize your skincare routine according to your skin’s needs.

Key Benefits of Using a Face Serum

1. Deep Hydration and Skin Barrier Support

One of the biggest advantages of using a face serum is its ability to deeply hydrate the skin. Hydrating ingredients like Hyaluronic Acid attract water into the skin, leaving it soft, supple, and refreshed.

A well-hydrated skin barrier is essential because it helps protect against pollution, bacteria, and moisture loss. Regular use of a hydrating serum strengthens this barrier, reducing dryness and irritation over time.

2. Targeted Treatment for Specific Skin Concerns

Unlike general moisturizers, serums are formulated to address particular skincare issues.

Depending on the active ingredients, a serum can help with:

  • Acne and blemishes
  • Hyperpigmentation
  • Dark spots
  • Uneven skin tone
  • Fine lines
  • Wrinkles
  • Dehydration
  • Redness

For example, someone dealing with post-acne marks may benefit from Vitamin C or Niacinamide, while those concerned about aging may prefer Retinol-based formulas.

3. Improves Skin Texture and Natural Glow

Consistent use of the right serum can significantly improve your skin’s overall appearance.

Benefits include:

  • Smoother skin texture
  • Brighter complexion
  • Reduced rough patches
  • Smaller-looking pores
  • Healthier glow

Many people notice their skin becoming more radiant after incorporating a quality serum into their daily routine.

4. Lightweight Formula with Fast Absorption

Face serums are known for their lightweight texture.

Unlike heavy creams that may leave a greasy finish, serums absorb quickly without clogging pores. This makes them suitable for all skin types, including oily and acne-prone skin.

Their fast absorption also allows active ingredients to work more efficiently beneath the skin’s surface.

How to Choose the Right Serum for Your Skin Type

Choosing the right serum is essential for getting the best results.

For Oily Skin

If your skin produces excess oil or is acne-prone, look for lightweight, non-comedogenic serums containing:

  • Niacinamide
  • Salicylic Acid
  • Zinc
  • Tea Tree Extract

These ingredients help regulate oil production while minimizing breakouts.

For Dry Skin

Dry skin benefits most from hydrating and nourishing ingredients such as:

  • Hyaluronic Acid
  • Ceramides
  • Glycerin
  • Vitamin E
  • Squalane

These ingredients replenish moisture and reduce flakiness.

For Sensitive Skin

Sensitive skin requires gentle formulations.

Choose serums containing:

  • Aloe Vera
  • Centella Asiatica
  • Panthenol
  • Niacinamide (lower concentration)

Avoid products with excessive fragrance or alcohol if your skin reacts easily.

For Combination Skin

Combination skin needs balance.

Ingredients like:

  • Niacinamide
  • Hyaluronic Acid
  • Peptides

provide hydration without making oily areas greasy.

How to Apply Face Serum Correctly

Even the best serum won’t deliver optimal results if applied incorrectly.

Follow these simple steps:

Step 1: Cleanse

Wash your face with a gentle cleanser to remove dirt, oil, and makeup.

Step 2: Apply Toner (Optional)

A toner helps prepare your skin for better absorption.

Step 3: Apply Face Serum

Take 2–3 drops of serum and gently press or pat it into your skin.

Avoid rubbing aggressively.

Step 4: Moisturize

Seal the serum with a moisturizer to lock in hydration.

Step 5: Sunscreen (Morning Only)

If using your serum during the day, always finish with a broad-spectrum sunscreen (SPF 30 or higher).

Morning vs. Night Usage

Morning Routine

Morning serums often contain:

  • Vitamin C
  • Hyaluronic Acid
  • Niacinamide

These ingredients protect the skin from environmental stress while keeping it hydrated throughout the day.

Night Routine

Nighttime is ideal for repair-focused ingredients like:

  • Retinol
  • Peptides
  • Ceramides

These work while your skin naturally regenerates during sleep.

Frequently Asked Questions (FAQs)

Can I use a face serum every day?

Yes. Most face serums are designed for daily use. Hydrating and brightening serums can typically be used once or twice daily. Stronger active ingredients like Retinol may be introduced gradually, starting two to three nights per week before increasing frequency.

Should serum be applied before or after moisturizer?

Face serum should always be applied before moisturizer.

Because serums have a thinner consistency, they absorb quickly into clean skin. Moisturizer is then applied afterward to lock in the active ingredients and hydration.

How long does it take to see results?

Results vary depending on the serum and your skin concerns.

  • Hydration: A few days
  • Brighter and Glowing skin: 2–4 weeks
  • Reduced pigmentation: 6–12 weeks
  • Fine lines and wrinkles: Around 8–12 weeks with consistent use

Consistency is the key to achieving long-term improvements.

Conclusion

A face serum is one of the most effective additions you can make to your skincare routine. Its concentrated ingredients provide targeted solutions for hydration, acne, pigmentation, fine lines, and uneven skin texture while absorbing quickly into the glowing skin.

Whether you have oily, dry, sensitive, or combination skin, there’s a serum specifically formulated to meet your needs. By selecting the right ingredients and applying the serum correctly, you can enjoy healthier, smoother, and more radiant skin over time.

Start with a serum that matches your skin type, use it consistently, and pair it with a good moisturizer and sunscreen. Your skin will thank you with a brighter, healthier complexion that looks and feels its best.