Results 1 to 4 of 4
  1. #1
    Registered User
    Join Date
    May 2016
    Location
    Ahmedabad
    Posts
    2

    How to solve php module related issue

    If there is any php module related issue with the existing php website, first of all check the phpinfo page or php.ini file. Locate the php.ini file and if the module is not loaded in phpinfo page, need to allow that module in php.ini file.

    --------------------------------
    How to create a phpinfo.php File :
    --------------------------------
    → In the public_html folder of the website, create a file named phpinfo.php.
    → Write the following code to show all the information about PHP.
    <?php
    phpinfo();
    ?>
    → Browse this webpage (example: http://64.27.50.50:108/phpinfo.php).

    --------------------------------
    How to find php.ini file :
    --------------------------------
    → Browse phpinfo.php file and search for "Loaded Configuration File". This will show you an actual path of php.ini file on the disk.

    --------------------------------
    How to add module/extension in php.ini file :
    --------------------------------
    → Add following line in php.ini file :
    extension=FILE_NAME.dll

    Here FILE_NAME is the extension file name.
    Best regards,
    Pratik Jajal
    Eminentworks.com

  2. #2
    Senior Member
    Join Date
    Sep 2015
    Posts
    343
    n a perfect world, you'd be able to install a program like Apache, configure it, and walk away. Unfortunately, it doesn't always work that way. Scott Lowe gives some tips about how to troubleshoot problems with Apache 2.2 when they occur.
    f you're having trouble with Apache, or seeming to have trouble with one of its modules, your first stop should be in looking over Apache's detailed error log. Depending on how your system and Apache are configured, the error log may live in different locations. The default location for this file is a file named error_log located in the logs directory inside your Apache root installation. If you can't find your error log, open the httpd.conf configuration file and look for the ErrorLog directive, which defines the location.

    Apache is initially configured to the "warn" log level, meaning that any problem more serious than a warning (critical, emergency, error, alert, and warn) is logged. You can adjust the logging level in httpd.conf my manipulating the LogLevel directive.

    From the Apache documentation, Table A outlines the eight available warning levels and provides an example of what would be logged at that level.

    If you can't figure out why your Apache server is having a problem, try adjusting the log level to a higher threshold to capture more information. After you change the level, stop and restart your server.

    There are actually two log files in Apache: error_log, which I described in this section, and access_log. The error_log file, as you might expect, is the log of most interest for troubleshooting purposes. However, also make use of the access_log when looking for problems. This file lists all of the items pulled down by clients along with the HTTP error or success code.
    Tip #2: Don't let an AllowOverride ruin your day

    Depending on how you want to run your web site, you can selectively alter the behavior of your Apache server by making use of .htaccess files. Simply put, an .htaccess file is a file in a directory that lets you make configuration changes that affect just that folder. For example, if you've disabled the "Indexes" in httpd.conf for all directories, none f your visitors will be able to access a directory listing. You may have a single folder for which this access should be allowed. In this case, you would have an .htaccess file with the "Options Indexes" directive.

    You can probably begin to see some reasons that .htaccess files can be problematic. First of all, for very large sites, keeping track of these files could be a very difficult task. Now, when you have a functionality problem, you can't just look to one source for possible configuration problems. You now need to traverse your directory structure and look for .htaccess files.

    Second, by allowing the use of these files, you may be allowing users the lack your Apache security prowess to make potentially insecure changes to your web site.

  3. #3
    Senior Member
    Join Date
    Sep 2015
    Posts
    343
    OpenCart 2.0 is out and there are a couple of things that need a little help to work as intended. For instance If you get an error below saying "Could not connect as ......" while uploading your zipped extensions via the Extension Installer, you probably have the FTP support disabled from your hosting. We will offer two ways to solve this - one for tech-savvy people who are comfortable with editing files on their FTP and one for store owners who can run it via the OC Installer.

  4. #4
    Registered User
    Join Date
    Apr 2014
    Location
    india
    Posts
    407
    Thanks to all of you for sharing this problem in detail, it will surely help me to understand the php module.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

  Find Web Hosting      
  Shared Web Hosting UNIX & Linux Web Hosting Windows Web Hosting Adult Web Hosting
  ASP ASP.NET Web Hosting Reseller Web Hosting VPS Web Hosting Managed Web Hosting
  Cloud Web Hosting Dedicated Server E-commerce Web Hosting Cheap Web Hosting


Premium Partners:


Visit forums.thewebhostbiz.com: to discuss the web hosting business, buy and sell websites and domain names, and discuss current web hosting tools and software.