mithu_sree Posted December 2, 2006 Share Posted December 2, 2006 My problem is that when tried to get http://localhost/sqlitemanager/ on my machineI am getting a blank pageAt the same time bothhttp://localhost/http://localhost/phpmyadmin/are working currectly. I had a initially correctly working system for all loacal addressesAccidently i mordified somewhere so that i lost my sqlitemanager home pageCan anyone explain how to retain it? Link to comment https://forums.phpfreaks.com/topic/29210-sqlitemanager/ Share on other sites More sharing options...
wildteen88 Posted December 2, 2006 Share Posted December 2, 2006 If you are getting a blank page then there may be an error which is occurring when you go to http://localhost/sqlitemanager/To see if there is any error occurring open up you php.ini and find the following:[code]; server, your database schema or other information.display_errors = Off[/code]Change Off to On after display_errors = Now save the php.ini and restart your server. Now go back to http://localhost/sqlitemanager/ do you get any errors? Link to comment https://forums.phpfreaks.com/topic/29210-sqlitemanager/#findComment-133928 Share on other sites More sharing options...
mithu_sree Posted December 4, 2006 Author Share Posted December 4, 2006 Here is that part of my php.ini;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; Error handling and logging ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; error_reporting is a bit-field. Or each number up to get desired error; reporting level; E_ALL - All errors and warnings; E_ERROR - fatal run-time errors; E_WARNING - run-time warnings (non-fatal errors); E_PARSE - compile-time parse errors; E_NOTICE - run-time notices (these are warnings which often result; from a bug in your code, but it's possible that it was; intentional (e.g., using an uninitialized variable and; relying on the fact it's automatically initialized to an; empty string); E_STRICT - run-time notices, enable to have PHP suggest changes; to your code which will ensure the best interoperability; and forward compatability of your code; E_CORE_ERROR - fatal errors that occur during PHP's initial startup; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's; initial startup; E_COMPILE_ERROR - fatal compile-time errors; E_COMPILE_WARNING - compile-time warnings (non-fatal errors); E_USER_ERROR - user-generated error message; E_USER_WARNING - user-generated warning message; E_USER_NOTICE - user-generated notice message;; Examples:;; - Show all errors, except for notices;;error_reporting = E_ALL & ~E_NOTICE;; - Show only errors;;error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR;; - Show all errors except for notices and coding standards warnings;error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT; Print out errors (as a part of the output). For production web sites,; you're strongly encouraged to turn this feature off, and use error logging; instead (see below). Keeping display_errors enabled on a production web site; may reveal security information to end users, such as file paths on your Web; server, your database schema or other information.display_errors = On; Even when display_errors is on, errors that occur during PHP's startup; sequence are not displayed. It's strongly recommended to keep; display_startup_errors off, except for when debugging.display_startup_errors = Off; Log errors into a log file (server-specific log, stderr, or error_log (below)); As stated above, you're strongly advised to use error logging in place of; error displaying on production web sites.log_errors = On; Set maximum length of log_errors. In error_log information about the source is; added. The default is 1024 and 0 allows to not apply any maximum length at all.log_errors_max_len = 1024; Do not log repeated messages. Repeated errors must occur in same file on same; line until ignore_repeated_source is set true.ignore_repeated_errors = Off; Ignore source of message when ignoring repeated messages. When this setting; is On you will not log errors with repeated messages from different files or; sourcelines.ignore_repeated_source = Off; If this parameter is set to Off, then memory leaks will not be shown (on; stdout or in the log). This has only effect in a debug compile, and if; error reporting includes E_WARNING in the allowed listreport_memleaks = On; Store the last error/warning message in $php_errormsg (boolean).track_errors = Off; Disable the inclusion of HTML tags in error messages.; Note: Never use this feature for production boxes.;html_errors = Off; If html_errors is set On PHP produces clickable error messages that direct; to a page describing the error or function causing the error in detail.; You can download a copy of the PHP manual from http://www.php.net/docs.php; and change docref_root to the base URL of your local copy including the; leading '/'. You must also specify the file extension being used including; the dot.; Note: Never use this feature for production boxes.;docref_root = "/phpmanual/";docref_ext = .html; String to output before an error message.;error_prepend_string = "<font color=ff0000>"; String to output after an error message.;error_append_string = "</font>"; Log errors to specified file.error_log = ../logs/php_error.log; Log errors to syslog (Event Log on NT, not valid in Windows 95).;error_log = syslog Link to comment https://forums.phpfreaks.com/topic/29210-sqlitemanager/#findComment-134732 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.