New Website Display Problems

Error message

  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in drupal_environment_initialize() (line 682 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in drupal_environment_initialize() (line 683 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in drupal_environment_initialize() (line 684 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in drupal_environment_initialize() (line 687 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in drupal_environment_initialize() (line 689 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in include_once() (line 300 of /home/smartkb/public_html/sites/default/settings.php).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in include_once() (line 301 of /home/smartkb/public_html/sites/default/settings.php).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in include_once() (line 309 of /home/smartkb/public_html/sites/default/settings.php).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in include_once() (line 316 of /home/smartkb/public_html/sites/default/settings.php).
  • Warning: ini_set(): Headers already sent. You cannot change the session module's ini settings at this time in drupal_settings_initialize() (line 776 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: session_name(): Cannot change session name when headers already sent in drupal_settings_initialize() (line 788 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: session_set_save_handler(): Cannot change save handler when headers already sent in drupal_session_initialize() (line 242 of /home/smartkb/public_html/includes/session.inc).
  • Warning: session_id(): Cannot change session id when headers already sent in drupal_session_initialize() (line 266 of /home/smartkb/public_html/includes/session.inc).
  • Warning: Cannot modify header information - headers already sent by (output started at /home/smartkb/public_html/index.php:3) in drupal_send_headers() (line 1221 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: Cannot modify header information - headers already sent by (output started at /home/smartkb/public_html/index.php:3) in drupal_send_headers() (line 1221 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: Cannot modify header information - headers already sent by (output started at /home/smartkb/public_html/index.php:3) in drupal_send_headers() (line 1221 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: Cannot modify header information - headers already sent by (output started at /home/smartkb/public_html/index.php:3) in drupal_send_headers() (line 1221 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: Cannot modify header information - headers already sent by (output started at /home/smartkb/public_html/index.php:3) in drupal_send_headers() (line 1221 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Warning: Cannot modify header information - headers already sent by (output started at /home/smartkb/public_html/index.php:3) in drupal_send_headers() (line 1221 of /home/smartkb/public_html/includes/bootstrap.inc).
  • Deprecated function: The each() function is deprecated. This message will be suppressed on further calls in menu_set_active_trail() (line 2394 of /home/smartkb/public_html/includes/menu.inc).

After uploading your Website's files, any changes to your Website should take place immediately.

Problems Affecting Website Display Results:

  • Website Display Issues
  • Wrong Website Page Displays
  • Error Page Redirects

On occasions, after uploading and publishing your New Website pages, you may experience an Index Page (your Website's "Home" or "Welcome" front page) and other website display issues that can result in no display, previous page content displays or as an automatic redirect to a "404 File Not Found Error" page.

The following instructions may resolve your New Website page display issues and content display problems.

Common problems affecting Website Page display:

  • Hosting Service Provider's Default Web Page Still Displays
  • Incorrect Index File Name
  • Website Files Uploaded to an Incorrect Folder (or Directory)
  • Browser or Proxy History Cache
  • Wrong URL (Website Address) in Your Browser

Your Index Page File
Your "Index Page" (your "Home" or "Welcome" page) is the page that loads after having entered your Domain Name (i.e. yourdomain.com) in your browser's address field.

By default, your browser calls your Website's hosting server which then searches your Website's files to locate your Index Page.

Your Index Page file can have a file name such as "index.htm" or "index.html" or "index.php" or "index.shtml" or "index.asp" and so on. A website visitor's browser calls this index file so your hosting server can load this page as your front page (your "Home" or "Welcome" page) content.

Hosting Service Provider's Default Web Page Still Displays
Some web host services providers upload a default web page (usually "index.htm" or "index.html") for you after your web hosting sign-up and your account has been activated.

This default index file is provided so when using your browser to access your Domain Name prior to your uploading your Website's files, this default web page content appears rather than having a domain name load that results as a blank index page (no content displayed) or a "File Not Found" error page.

After your Website's file upload is complete, this web host provider's default web page is often overwritten by your newly transferred Index Page file. Occasionally however, when your using an index page file extension that differs from the web host provider's default index page file extension, your browser may not display the correct front page (your "Home" or "Welcome") content.

To resolve this issue, access your cPanel and search for the web host provider's default index file (usually "index.htm" or "index.html"). You can locate this default index web page most easily by viewing the date field area. Your web host provider's default index file usually has a date that is the same date (or nearly the same date) as your web host account activation date.

Simply remove this default index web page by deleting your web host's default index page and retry your browser with your Domain Name. Your browser should now display your Website's uploaded index file and your correct front page (your "Home" or "Welcome") content should display.

Incorrect Index File Name
The front page content (your "Home" or "Welcome" page) or your Index Page is required to have a certain "naming convention". This specific naming convention is used to define this Index Page file. For your host server to access the correct front page content (your Index Page), you must name your Index Page file using an acceptable naming convention.

Your hosting server is configured to recognize certain files (your front page content) as special files. Your index file (Index Page) is specially recognized as your front page content file.

In order for your front page content to be recognized by your hosting server, your Index Page must be named using certain naming conventions followed by a correct file extension. Many hosting servers allow the front page content file to be named as "index.htm" or "index.html" or "index.php" or "index.shtml" or "index.asp" and other Index Page file name variations.

Additionally, front page naming conventions allow for file names such as "default.htm" or "default.html" to be used for your hosting server locating your Index Page or front page content.

Regardless of Index Page file name variations, the naming convention must match your host server configuration. In most cases, this Index Page file is expressed in lowercase characters (with no spaces) followed by an acceptable file extension.

For absolute certainty, contact your web hosting service for their naming conventions and server configuration. If you are having problems with your front page content displaying correctly or if you are unsure as to your Index Page naming conventions and you need some support, submit a Support Ticket from your Client Account Management area.

Website Files Uploaded to an Incorrect Folder (or Directory)
Your Website's pages should be uploaded to the "www" or "public_html" folder in your cPanel account. This is the most common set-up, however different hosting services may have different system set-up configurations.

Hosting servers are designed to serve website pages that are placed in specific folders. A common error when uploading your Website's files to your hosting server can occur because those files have been uploaded to an incorrect file folder or directory rather than the correct "www" or "public_html" folder.

To resolve this issue, access your cPanel and locate the "www" or "public_html" folder in your cPanel account. Confirm that your Website's uploaded files are contained in the the "www" or "public_html" folder (directory). If your Website's uploaded files are not present in the "www" or "public_html" folder, you have most likely uploaded your website's files to an incorrect folder (directory) location.

To correct an upload mistake to an incorrect folder, delete the Website's files that have been misplaced. Then upload your Website's file's to the correct "www" or "public_html" folder (directory). If you are unsure as to how to resolve this issue or you need some support with your Website's files uploads, submit a Support Ticket from your Client Account Management area.

Browser or Proxy History Cache
If you have reviewed your Website for issues concerning "Hosting Service Provider's Default Web Page Still Displays" and "Incorrect Index File Name" and "Website Files Uploaded to an Incorrect Folder (or Directory)" issues and you are still experiencing problems with your Website's browser display, there is a possibility that your web browser has cached an old copy of your web pages.

Browser cache is used to speed a website visitor's browsing experience and saves your hosting server's bandwidth.

To improve a website visitor's web browsing experience and save server bandwidth, most web browsers keep a copy (cache) of visited web pages. Your browser may contain this web browsing history in its internal cache.

Because of this browser cache, when you request the same web address (to your newly uploaded Website's files), instead of going to the Internet to get a fresh copy of the requested web page, the browser simply displays its old cached copy.

To resolve this issue, try refreshing the requested web page. If you still are receiving an old cached web page, clear your browser cache. This will force the browser to retrieve a new copy of the page when you enter the requested URL in the browser's address bar.

There are 2 general ways to refresh or reload a web page in your browser. The first method uses on a PC, pressing the "Control" and "R" keys (holding down the "Ctrl" key while simultaneously pressing the "R" key) or on an Apple, pressing the "Command" and "R" keys (holding down the "Command" key while simultaneously pressing the "R" key).

The second method of refreshing or reloading a web page in your browser is by pressing the F5 key.

Click here for more information on clearing your browser cache for Firefox.

Click here for more information on clearing your browser cache for Chrome.

Click here for more information on clearing your browser cache for Safari.

Click here for more information on clearing your browser cache for Opera.

For other browser cache clearing processes, consult your specific browser's website support page.

When clearing browser cache, saved login usernames, passwords and other saved information data used by your browser to increase website accessibility functions may be removed.

When using a proxy to access the Internet, it's also possible that your proxy server has cached old versions of visited web pages. Proxies are sometimes used (without the IP user being aware) by Internet Providers (IPs). It may be that your IP is using a proxy without your knowing.

Clearing a proxy cache can most times be accomplished using the "refresh" key commands listed above. If clearing a proxy cache fails using the "refresh" key commands, try using a different browser and again using the "refresh" key commands.

Wrong URL (Website Address) in Your Browser
As a last problem (very unlikely), checking to determine if the website address entered in your browsers address field is correct can sometimes be a careless error that can be easily solved by using the correct Domain Name URL.