zdravejte
imam sledniqt problem :
kato imam nqkawa sintakti4na gre6ka v PHP skripta, Ne mi izwejda gre6ka ot sorta "parse error" na edi si koj red.
Nqmakoj znae li ot kakwo e towa i kak da naprawq taka 4e da mi dawa towa suob6tenie za gre6ka i na koj red e tq
10x

php.ini - error reporting

kude po to4no v php.ini se pishe towa
pastne mi fragment ot php.ini kudeto se oprawq

display_errors = On
error_reporting = 2039

Съдържаниет е скрито
Влезте за да го видите

nqma nikakyv rezultata ot towa
pak e su6toto ne vadissuob6tenie za gre6ka , a takawa prawq izkustweno vyv skripta (izpuskam" ; ") i rezultata e bql ekran :(
i e mnogo gadno taka da ne se znae na koj red e gre6kata i kakwa e

Белите страници са много неприятна ситуация, обикновено в този случай така или иначе няма да изкараш каква е грешката.
На мен ми се е случвало няколко пъти това и досега се оказва, че е при опит за проверка за наличие на стойност в необявена променлива. Което е тъпо, защото в PHP това се прави постоянно.
Опитах се да намеря по-точни обяснения и по форуми и по сайтове, но засега никой не е казал нещо по-подробно.
Аз подхождам малко елеметарно към проблема, като почвам да слагам echo "dsads"; на различни места в скрипта, докато това "dsads" не спре да се показва. Малко първобитен дебъг, но засега помага.

i az taka prawq po princip , no spored mene e ne6to ot nastrojkite na php , tyj katosu6tiqt skript kato go puskam na drugo apache s php modul nqma problem izkarwa si gre6kata a pri mene ne iska da stane na moeto apache s php pod linux.
kato go probwam na windows-koto mi apache nqma problem izkarwa mi gre6kata.
kofti rabota no kakwo da se prawi.

Methodut s echo "dasd"; raboti samo ako greshkata ti e logicheska. Ako e parse error nyama da stane, zashtoto greshkata e na drugo nivo. Zatova v php.ini mojesh da nastroish

error_reporting = E_ALL & ~E_NOTICE

ili v nachaloto na vseki script da izvikvash:

error_reporting (E_ALL ^ E_NOTICE); koeto mojesh da go ostavish tyaka dokato go testvash i debugvash, a kogato go kachish na production server da e error_reporting (0), t.e. da ne se pokazvat greshkite, za po-golyama sigurnost i da si proveryavash error log faila, kade se zapisva greshkata.

Uspeh!

sprawih se s problema s beliqt ekran kojto izlizashe i ne dawashe suob6tenie za ger6ki - w php.ini ima paragraf za gre6kite
zamenih go celiq sys eto tozi i nqma problem ve4e:
-----------

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; 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_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:
; error_reporting = E_ALL & ~E_NOTICE ; show all errors, except for notices
; error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR ; show only errors
error_reporting = E_ALL & ~E_NOTICE ; Show all errors except for notices
display_errors = On ; 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_startup_errors = Off ; 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.
log_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.
track_errors = Off ; Store the last error/warning message in $php_errormsg (boolean)
;error_prepend_string = "<font color=ff0000>" ; string to output before an error message
;error_append_string = "</font>" ; string to output after an error message
;error_log = filename ; log errors to specified file
;error_log = syslog ; log errors to syslog (Event Log on NT, not valid in Windows 95)
warn_plus_overloading = Off ; warn if the + operator is used with strings

-----------------

towa s error_reporting (0); go probwah ama ne dejstwa ne6to pri mene kato go sloja v na4aloto na skript, kato ima gre6ka tq pak se izwejda