Error reporting 22519 - Исправление ошибок и поиск оптимальных решений проблем

Что такое 22527 в error_reporting 22527 из phpinfo

В моем локальном dev env я использую PHP Version 5.3.3-1ubuntu9.2.

Теперь, когда я вижу error_reporting, значение равно 22527.

Что такое 22527?

Я проверил http://www.php.net/manual/en/errorfunc.constants.php , но я не смог найти номер.

Может ли кто-нибудь сказать мне, что это?

Мне нужно изменить его на E_ALL | E_STRICT?

Related of «Что такое 22527 в error_reporting 22527 из phpinfo»

Это значение является фактически растровой маской , суммой констант.

В вашем случае это E_ALL &

E_DEPRECATED , он отображает каждую ошибку, кроме E_DEPRECATED и E_STRICT (поскольку E_STRICT не включен в E_ALL )

Когда вы OR или две или более константы определены здесь , вы получаете значение 22527 . Вот как вы его декодируете (если вам интересно):

НИКОГДА не используйте числовое значение, чтобы установить отчет об ошибках, поскольку значение этого значения может измениться, но значение констант (например, E_ALL, E_STRICT и т. Д.), Вероятно, не будет:

Новый уровень error_reporting. Он принимает либо битмаску, либо именованные константы. Использование именованных констант настоятельно рекомендуется для обеспечения совместимости для будущих версий. По мере добавления уровней ошибок диапазон целых чисел увеличивается, поэтому старые уровни ошибок на основе целого числа не всегда будут вести себя так, как ожидалось .

(и обратите внимание, что с PHP 5.4 E_ALL теперь включает E_STRICT)

Если вы хотите, чтобы строжайшая отчетность вечно и вечно, вы можете установить error_reporting на очень большое число, чтобы гарантировать (?), Что вы будете сообщать о всех ошибках навсегда :

Источник

The Joomla! Forum™

Administrator login page error Topic is solved

Administrator login page error

Post by stubby_finger48 » Fri May 28, 2021 3:24 am

Re: Administrator login page error

Post by toivo » Fri May 28, 2021 6:09 am

The 500 error may originate from a third party plugin that is out of date or simply not compatible with PHP 7.4.

If you already enabled error reporting in the file configuration.php, enable also the Debug option before trying to access the back end:

Re: Administrator login page error

Post by stubby_finger48 » Fri May 28, 2021 6:18 am

Database Configuration :: Version: 5.7.28-log (Client:mysqlnd 7.4.15) | Database Size: 22.27 MiB | #of Tables with config prefix: 118 | #of other Tables: 0 | User Privileges : GRANT SELECT User Privileges : INSERT User Privileges : UPDATE User Privileges : DELETE User Privileges : CREATE User Privileges : DROP User Privileges : REFERENCES User Privileges : INDEX User Privileges : ALTER User Privileges : CREATE TEMPORARY TABLES User Privileges : LOCK TABLES User Privileges : EXECUTE User Privileges : CREATE VIEW User Privileges : SHOW VIEW User Privileges : CREATE ROUTINE User Privileges : ALTER ROUTINE User Privileges : TRIGGER

Switch User Environment :: PHP CGI: Yes | Server SU: Yes | PHP SU: Yes | Potential Ownership Issues: No

Источник

Это значение является фактически растровой маской , суммой констант.

Итак, 22527

  16384 E_USER_DEPRECATED + 4096 E_RECOVERABLE_ERROR + etc...

В вашем случае это E_ALL & ~E_DEPRECATED , он отображает каждую ошибку, кроме E_DEPRECATED и E_STRICT (поскольку E_STRICT не включен в E_ALL )

Когда вы OR или две или более константы определены здесь , вы получаете значение 22527 . Вот как вы его декодируете (если вам интересно):

 <?php $error_number = 22527; $error_description = array( ); $error_codes = array( E_ERROR => "E_ERROR", E_WARNING => "E_WARNING", E_PARSE => "E_PARSE", E_NOTICE => "E_NOTICE", E_CORE_ERROR => "E_CORE_ERROR", E_CORE_WARNING => "E_CORE_WARNING", E_COMPILE_ERROR => "E_COMPILE_ERROR", E_COMPILE_WARNING => "E_COMPILE_WARNING", E_USER_ERROR => "E_USER_ERROR", E_USER_WARNING => "E_USER_WARNING", E_USER_NOTICE => "E_USER_NOTICE", E_STRICT => "E_STRICT", E_RECOVERABLE_ERROR => "E_RECOVERABLE_ERROR", E_DEPRECATED => "E_DEPRECATED", E_USER_DEPRECATED => "E_USER_DEPRECATED", E_ALL => "E_ALL" ); foreach( $error_codes as $number => $description ) { if ( ( $number & $error_number ) == $number ) { $error_description[ ] = $description; } } echo sprintf( "error number %d corresponds to:n%s", $error_number, implode( " | ", $error_description ) ); ?>

Вывод:

 error number 22527 corresponds to: E_ERROR | E_WARNING | E_PARSE | E_NOTICE | E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_COMPILE_WARNING | E_USER_ERROR | E_USER_WARNING | E_USER_NOTICE | E_RECOVERABLE_ERROR | E_USER_DEPRECATED

Новый уровень error_reporting. Он принимает либо битмаску, либо именованные константы. Использование именованных констант настоятельно рекомендуется для обеспечения совместимости для будущих версий. По мере добавления уровней ошибок диапазон целых чисел увеличивается, поэтому старые уровни ошибок на основе целого числа не всегда будут вести себя так, как ожидалось .

(и обратите внимание, что с PHP 5.4 E_ALL теперь включает E_STRICT)

Использование PHP-констант вне PHP, как и в httpd.conf, не имеет никакого полезного значения, поэтому в таких случаях требуются целые значения. И поскольку уровни ошибок будут добавляться с течением времени, максимальное значение (для E_ALL), скорее всего, изменится. Таким образом, вместо E_ALL рассмотрим использование большего значения для покрытия всех битовых полей отныне и в будущем, числовое значение, например 2147483647 (включает все ошибки, а не только E_ALL).

Проверьте свой php.ini на значение error_reporting в формате чтения PHP-констант. Кажется, что функция phpinfo () всегда показывает числовое значение, а не показывает константы.

Но, лично, я оставляю php.ini со значениями по умолчанию для сообщений об ошибках. Вместо этого я просто помещал функцию сообщения об ошибках в начало любого скрипта php, над которым я работаю, чтобы переопределить значения по умолчанию. например:

 error_reporting(E_ALL | E_STRICT);

Источник

We have by far the largest RPM repository with NGINX module packages and VMODs for Varnish. If you want to install NGINX, Varnish, and lots of useful performance/security software with smooth yum upgrades for production use, this is the repository for you.

Active subscription is required.

The arrival of amazing malware

In one of the servers which I’ve been securing against malware, an amazing backdoor PHP script was found:

<?php error_reporting(0); ${"x47Lx4fBx41x4cx53"}["x72x6dx63vfy"]="bx6fx74x5fx75x73ers";${"x47x4cx4fBx41x4cx53"}["x67x74lx76x68x75x6e"]="x62x6ft_ix70s";${"x47x4cx4fBx41x4cx53"}... lots of obfuscated code follows..

Why was it undetected by malware scanners? And how can we detect this kind of malware ourselves?

I won’t go into much details what the actual code does. In short, it allows hackers to run any commands on the compromised servers.
The code is highly obfuscated and there were dozens of similar scripts implanted in multiple directories of the website in question.

Take note at the opening code: error_reporting(0). It tries to turn off any errors from being written to PHP error log or displayed to browsers. And it succeeds.

php_admin_flag and error_reporting(0)

Supposedly, you did the right thing in configuring your PHP-FPM pool, e.g.:

php_admin_value[error_reporting] = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED

You’d expect that error_reporting(0) function calls will have no effect on the configured secure value of logging level. You’re wrong. At least as of PHP 7.0, there’s a long-standing bug which makes php_admin_value[error_reporting] useless.

With 7.0 <= PHP <= 7.?, any script can call error_reporting(0) and bypass whatever secure log level you have chosen.

You can see whether your specific PHP version is affected by running a simple test script. Provided you have placed the sample php_admin_value[error_reporting] directive in your PHP-FPM pool, create a script:

<?php
var_dump(error_reporting());
error_reporting(0);
var_dump(error_reporting());

Affected PHP versions will emit int(22519) int(0), meaning that error_reporting(0) is allowed to override master PHP configuration value.

PHP Version	Affected?	Behaviour
5.4.45	NO	`error_reporting(0)` does not override master value.
5.6.36	NO	`error_reporting(0)` does not override master value.
7.0.30	YES	`error_reporting(0)` overrides master value.
7.2.6	YES	`error_reporting(0)` overrides master value.

Surely enough, if hackers want to use your server as a tool, they want to keep their profile low. This is especially true for cryptojackers who want to leverage the power of your server to mine Monero. They want to do it as long as possible and stay undetected for as long as possible.

And the error_reporting PHP function is just there for their benefit. No matter what secure configuration PHP 7 has on the server level, the error_reporting(0) can override it and completely silence errors in affected scripts.

I can’t think of a good use for error_reporting function at all!. Apart from the mentioned malicious intent, error_reporting(0) is also a darling of bad coders trying to silence their code from emitting errors and warnings. This just makes things hard to troubleshoot on live servers.

If you know how to configure servers properly and have already specified the necessary logging level via error_reporting php.ini configuration directive, then you don’t need error_reporting(...) function at all.

Disable error_reporting(…)

Unfortunately, with the aforementioned PHP 7 bug, any script can override the configured error level, by just calling error_reporting(0). The only way to stop this is to disable the function altogether.

Make sure that your php.ini is configured with:

disable_functions=error_reporting

This will emit a security warning for scripts that use the function (they won’t fail). There, one change got us 2 things:

The malware can’t hide so easily as we have raised the chances of it exposing itself via PHP error log
We know who’s only trying to appear as a good coder by having PHP run with mouth shut about their unfixed bugs

But WordPress…

WordPress is trying to outsmart us and their developers think that we don’t know how to configure our servers. Even with default configuration (with WP_DEBUG off), you’d notice:

error_reporting() has been disabled for security reasons in wp-load.php on line 24
error_reporting() has been disabled for security reasons in load.php on line 333

You can’t do much about this: ignore the warnings or comment out those lines with ‘//’ to keep your logs clean (and also make things a little faster by running 2 fewer lines of PHP. Micro optimization maniac detectado 🙂

Oh wait, you can actually use an automated patch plugin. Installable via CLI:

wp plugin install https://github.com/GetPageSpeed/wp-error-reporting-patch/archive/master.zip --activate

If you go “ignore the warnings” route (keep WordPress files intact), you may want to filter WordPress cron errors.

@ Not so fast @

PHP has one built-in error handling operator which is @. If you prepend anything to a code with this sign, the error will be silenced.

There are basically 2 solutions to unsilence all pieces of code that make use of it.

First, is PHP based. In your bootstrap PHP file, set a custom PHP error handler ( via set_error_handler() ).

Second, is to install and configure a PHP extension which will stop the scream operator from working.

For PHP < 7.0, this scream PHP extension. To install it, run yum install php-pecl-scream. After the extension is installed, configure it in php.ini:

scream.enabled = On

For PHP >= 7.0, you can use XDebug extension. Once installed, configure it in php.ini with:

xdebug.scream=1

Note that the value of 1 disables scream operator, so the setting value is counter-intuitive. From XDebug documentation:

If this setting is 1, then Xdebug will disable the @ (shut-up) operator so that notices, warnings, and errors are no longer hidden.

On another note about XDebug – you can use to prevent error reporting calls from hiding errors as well. Place this in your php.ini:

xdebug.force_display_errors = 1;
xdebug.force_error_reporting = -1;

Return of the malware

Fast forward to May 14, 2018. And I’m dealing with another malware that uses error_reporting to hide itself. This time it has made some evolution: there are markers with an ID of the “hack”. The files have the same signature at the beginning. Some of the files showed signs of double penetration 😀 :

    <?php /*564794552*/ error_reporting(0); @ini_set('error_log',NULL); @ini_set('log_errors',0); @ini_set('display_errors','Off'); @eval( base64_decode('blah 
    blah lots of encoded stuff')); @ini_restore('error_log'); @ini_restore('display_errors'); /*564794552*/ ?><?php /*8793453*/ error_reporting(0); ... /*8793453*/ ?>

Amazing. This could have to effect been hacked by 2 different people using the same malware. On that particular server, they had an old PHP and Apache. Still, there was no error anywhere as they haven’t setup secure php_admin_value for error log level. Their site failed with a 500 error.

However, in some files, the malware manifested itself with:

Namespace declaration statement has to be the very first statement in the script in …

The number of affected PHP files count was topping 10K. That is, the malware put itself into every single PHP file out there. How do you find and weed out all these malware strings from your files?

Find infected file with:

grep -R --include=*.php "error_reporting(0)"

And further you can count them with:

grep -R --include=*.php "error_reporting(0)"  | wc -l

To clean then up, use the sed command line program. The following will replace all the marked PHP code blocks like <?php /*8793453*/ ... /*8793453*/ ?> while keeping a copy of “hacked” files with .virus extension:

find . -iname "*.php" -exec sed -i.virus --regexp-extended 's@<?php /*[0-9]+*/.*/*[0-9]+*/ ?>@@g' {} ;

Needless to say, you have to take some measures on having the hack not happen again:

Upgrade server software
More importantly, secure your open source apps, like WordPress (update core and plugins)

Conclusions for admin:

1. Disable the silencing operator:

Install the PHP extensions to control it:

sudo yum install php-pecl-scream

Edit your php.ini and put:

scream.enabled = Off

2. Disable error_reporting

Edit your php.ini and put:

disable_functions=error_reporting

3. Ensure non-overridable log settings

As you might have noted, the malware in question tried to override some settings via ini_set. You can disable this function as well, but many apps use ini_set for their function.
So you might want to simply enforce the important security-related settings in your web server configuration. Use of php_admin_flag or php_admin_value directives is highly recommended while configuring log settings for your websites.

Conclusion for hackers:

Use @ silencing operator for every function call In the latest example they were using it, but for some reasons error_reporting call itself was not subjected to @. Other from that things were advanced enough to keep current log level and make sure that non-hacked related code keeps its current logging level. In a way, this allowed the malware to shamelessly infect every PHP file on the server.
Try not to break the code in a way that you will manifest yourself

Источник

closed

Error Reporting always set with E_WARNING

Description

There is something in the core that sets the error reporting to 22519 (E_ALL ^ E_NOTICE ^ E_DEPRECATED), even with the following localconf.php configuration:

$TYPO3_CONF_VARS['SYS']['displayErrors'] = 0;
$TYPO3_CONF_VARS['SYS']['errorHandlerErrors']     = 22517; // E_ALL ^ E_DEPRECATED ^ E_NOTICE ^ E_WARNING (everything except deprecated-msgs and notices and warnings) 
$TYPO3_CONF_VARS['SYS']['syslogErrorReporting']   = 22517; // E_ALL ^ E_DEPRECATED ^ E_NOTICE ^ E_WARNING (everything except deprecated-msgs and notices and warnings) 
$TYPO3_CONF_VARS['SYS']['belogErrorReporting']    = 22517; // E_ALL ^ E_DEPRECATED ^ E_NOTICE ^ E_WARNING (everything except deprecated-msgs and notices and warnings)

This can be reproduced on all systems using TYPO3 4.5.X with PHP 5.3 on Windows and Linux.

Even when set directly in the php.ini, the value get’s set to 22519 again.

To check I used extdeveval’s phpinfo.

This wouldn’t be as much as a problem, if the PHP errors weren’t logged to PHP’s error log (which can only be avoided by either setting the correct error_reporting bitmask or disabling error reporting completly which should not be seen as an option).

I made absolutely sure that none of the installed extensions in the system actually sets this value by:
— grep’ing the whole thing for 22519, E_WARNING, ini_set and error_reporting
— deinstalling all non-core extensions
— tracing the execution of the extdeveval module

All this showed that there is nothing that actually modifies the error reporting, but still, the error_reporting get’s flawnd (see attached screenshot from extdeval).

Files

History
Notes

Status changed from New to Needs Feedback
Target version deleted (4.5.30)

Is it possible that your PHP configuration enforces this value?

I don’t think so, the master Value in the phpinfo shows 22517, but the running value is still 22519.

Is Regression set to No

Hi,

I do not have this issue in our installations nor do I find a part in the source which sets this mask value.
Can you recheck you .htaccess files, server config and so on?

Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Also available in: Atom
PDF

Источник

Administrator login page error

Topic is solved

Moderator: General Support Moderators

stubby_finger48: Joomla! Apprentice; Posts: 5; Joined: Fri May 28, 2021 3:06 am

Administrator login page error

We have a Joomla site that has been up for 4 or 5 months now hosted at dreamhost.com. The site itself is working perfectly fine. But today we found that when we try to go to the /administrator page to login it doesn’t load at all. It will just sit there for a minute or two and then display a 500 Internal Server Error page. It does not load anything else, you never get the login screen at all. After searching for answers I found the recommendation to enable php error reporting in the configuration.php file which I have but I’m still not seeing any error messages. Looking for any recommendations on how to go about troubleshooting this, I’m an IT guy but not much or a web guy. I’m not sure the exact version of Joomla the site is on, we used whatever was the current version of 3.9 when we set it up and I believe it is up to date and it’s on PHP 7.4 FastCGI. Thanks for any ideas.

toivo: Joomla! Master; Posts: 15503; Joined: Thu Feb 15, 2007 5:48 am; Location: Sydney, Australia

Re: Administrator login page error

Post

by toivo » Fri May 28, 2021 6:09 am

The 500 error may originate from a third party plugin that is out of date or simply not compatible with PHP 7.4.

If you already enabled error reporting in the file configuration.php, enable also the Debug option before trying to access the back end:

Code: Select all

	public $debug = '1';
	public $error_reporting = 'maximum';

Please post the results from the Forum Post Assistant (FPA) by following the instructions at https://forumpostassistant.github.io/docs so that our volunteer experts can review the configuration.

Toivo Talikka, Global Moderator

stubby_finger48: Joomla! Apprentice; Posts: 5; Joined: Fri May 28, 2021 3:06 am

Re: Administrator login page error

Post

by stubby_finger48 » Fri May 28, 2021 6:18 am

Still trying to figure this out, Joomla version is 3.9.26. I read about fpa so decided to give it a go. I got an A+ 100% generated post is below,

Forum Post Assistant (v1.6.2) : 27-May-2021 wrote:

Basic Environment :: wrote:Joomla! Instance :: Joomla! 3.9.26-Stable (Amani) 13-April-2021
Joomla! Platform :: Joomla Platform 13.1.0-Stable (Curiosity) 24-Apr-2013
Joomla! Configured :: Yes | Writable (644) |
Configuration Options :: Offline: false | SEF: true | SEF Suffix: false | SEF ReWrite: false | .htaccess/web.config: No | GZip: false | Cache: false | CacheTime: 15 | CacheHandler: file | CachePlatformPrefix: false | FTP Layer: false | Proxy: false | LiveSite: | Session lifetime: 15 | Session handler: database | Shared sessions: false | SSL: 0 | Error Reporting: maximum | Site Debug: true | Language Debug: false | Default Access: 1 | Unicode Slugs: false | dbConnection Type: mysqli | PHP Supports J! 3.9.26: Yes | Database Supports J! 3.9.26: Yes | Database Credentials Present: Yes |

Host Configuration :: OS: Linux | OS Version: 4.14.117-grsec-grsec+ | Technology: x86_64 | Web Server: Apache | Encoding: gzip, deflate, br | System TMP Writable: Yes | Free Disk Space : 491.70 GiB |

PHP Configuration :: Version: 7.4.15 | PHP API: cgi-fcgi | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 22519 | Log Errors To: | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 512M | Max. POST Size: 512M | Max. Input Time: -1 | Max. Execution Time: 120 | Memory Limit: 256M

Database Configuration :: Version: 5.7.28-log (Client:mysqlnd 7.4.15) | Database Size: 22.27 MiB | #of Tables with config prefix: 118 | #of other Tables: 0 | User Privileges : GRANT SELECTUser Privileges : INSERTUser Privileges : UPDATEUser Privileges : DELETEUser Privileges : CREATEUser Privileges : DROPUser Privileges : REFERENCESUser Privileges : INDEXUser Privileges : ALTERUser Privileges : CREATE TEMPORARY TABLESUser Privileges : LOCK TABLESUser Privileges : EXECUTEUser Privileges : CREATE VIEWUser Privileges : SHOW VIEWUser Privileges : CREATE ROUTINEUser Privileges : ALTER ROUTINEUser Privileges : TRIGGER

Detailed Environment :: wrote:PHP Extensions :: Core (7.4.15) | date (7.4.15) | libxml (7.4.15) | pcre (7.4.15) | sqlite3 (7.4.15) | filter (7.4.15) | hash (7.4.15) | intl (7.4.15) | json (7.4.15) | mbstring (7.4.15) | SPL (7.4.15) | PDO (7.4.15) | Reflection (7.4.15) | session (7.4.15) | pdo_sqlite (7.4.15) | standard (7.4.15) | mysqlnd (mysqlnd 7.4.15) | cgi-fcgi (7.4.15) | bcmath (7.4.15) | bz2 (7.4.15) | calendar (7.4.15) | ctype (7.4.15) | curl (7.4.15) | dom (20031129) | exif (7.4.15) | fileinfo (7.4.15) | ftp (7.4.15) | gd (7.4.15) | gettext (7.4.15) | iconv (7.4.15) | imap (7.4.15) | mysqli (7.4.15) | openssl (7.4.15) | pcntl (7.4.15) | pdo_mysql (7.4.15) | zlib (7.4.15) | posix (7.4.15) | pspell (7.4.15) | sodium (7.4.15) | SimpleXML (7.4.15) | soap (7.4.15) | sockets (7.4.15) | tokenizer (7.4.15) | xml (7.4.15) | xmlreader (7.4.15) | xmlrpc (7.4.15) | xmlwriter (7.4.15) | xsl (7.4.15) | zip (1.15.6) | Phar (7.4.15) | imagick (3.4.4) | Zend OPcache (7.4.15) | Zend Engine (3.4.0) |
Potential Missing Extensions ::

Switch User Environment :: PHP CGI: Yes | Server SU: Yes | PHP SU: Yes | Potential Ownership Issues: No

Folder Permissions :: wrote:Core Folders :: images/ (755) | components/ (755) | modules/ (755) | plugins/ (755) | language/ (755) | templates/ (755) | cache/ (755) | logs/ (755) | tmp/ (755) | administrator/components/ (755) | administrator/modules/ (755) | administrator/language/ (755) | administrator/templates/ (755) | administrator/logs/ (755) |

Elevated Permissions (First 10) ::

Database Information :: wrote:Database statistics :: Uptime: 39488114 | Threads: 17 | Questions: 7309898534 | Slow queries: 216474648 | Opens: 446448235 | Flush tables: 167 | Open tables: 2048 | Queries per second avg: 185.116 |

Extensions Discovered :: wrote:Components :: Site ::
Core :: com_mailto (3.0.0) 1 | com_wrapper (3.0.0) 1 |
3rd Party:: WF_AGGREGATOR_AUDIO_TITLE (2.9.7) ? | WF_AGGREGATOR_DAILYMOTION_TITLE (2.9.7) ? | WF_AGGREGATOR_VIDEO_TITLE (2.9.7) ? | WF_AGGREGATOR_VIMEO_TITLE (2.9.7) ? | WF_AGGREGATOR_[youtube]_TITLE (2.9.7) ? | WF_FILESYSTEM_JOOMLA_TITLE (2.9.7) ? | WF_LINKS_JOOMLALINKS_TITLE (2.9.7) ? | WF_POPUPS_JCEMEDIABOX_TITLE (2.9.7) ? | WF_LINK_SEARCH_TITLE (2.9.7) ? | WF_ANCHOR_TITLE (2.9.7) ? | WF_ARTICLE_TITLE (2.9.7) ? | WF_ATTRIBUTES_TITLE (2.9.7) ? | WF_AUTOSAVE_TITLE (2.9.7) ? | WF_BROWSER_TITLE (2.9.7) ? | WF_CHARMAP_TITLE (2.9.7) ? | WF_CLEANUP_TITLE (2.9.7) ? | WF_CLIPBOARD_TITLE (2.9.7) ? | WF_CONTEXTMENU_TITLE (2.9.7) ? | WF_DIRECTIONALITY_TITLE (2.9.7) ? | WF_EMOTIONS_TITLE (2.9.7) ? | WF_FONTCOLOR_TITLE (2.9.7) ? | WF_FONTSELECT_TITLE (2.9.7) ? | WF_FONTSIZESELECT_TITLE (2.9.7) ? | WF_FORMATSELECT_TITLE (2.9.7) ? | WF_FULLSCREEN_TITLE (2.9.7) ? | WF_HELP_TITLE (2.9.7) ? | WF_HR_TITLE (2.9.7) ? | WF_IMGMANAGER_TITLE (2.9.7) ? | WF_KITCHENSINK_TITLE (2.9.7) ? | WF_LINK_TITLE (2.9.7) ? | WF_LISTS_TITLE (2.9.7) ? | WF_MEDIA_TITLE (2.9.7) ? | WF_NONBREAKING_TITLE (2.9.7) ? | JCE — Noneditable (1.0.0) ? | WF_PREVIEW_TITLE (2.9.7) ? | WF_PRINT_TITLE (2.9.7) ? | WF_REFERENCE_TITLE (2.9.7) ? | WF_SEARCHREPLACE_TITLE (2.9.7) ? | WF_SOURCE_TITLE (2.9.7) ? | WF_SPELLCHECKER_TITLE (2.9.7) ? | WF_STYLE_TITLE (2.9.7) ? | WF_STYLESELECT_TITLE (2.9.7) ? | WF_TABLE_TITLE (2.9.7) ? | WF_TEXTCASE_TITLE (2.9.7) ? | WF_VISUALBLOCKS_TITLE (2.9.7) ? | WF_VISUALCHARS_TITLE (2.9.7) ? | WF_WORDCOUNT_TITLE (2.9.7) ? | WF_XHTMLXTRAS_TITLE (2.9.7) ? |

Components :: Admin ::
Core :: com_actionlogs (3.9.0) 1 | com_admin (3.0.0) 1 | com_ajax (3.2.0) 1 | com_associations (3.7.0) 1 | com_banners (3.0.0) 1 | com_cache (3.0.0) 1 | com_categories (3.0.0) 1 | com_checkin (3.0.0) 1 | com_config (3.0.0) 1 | com_content (3.0.0) 1 | com_contenthistory (3.2.0) 1 | com_cpanel (3.0.0) 1 | com_fields (3.7.0) 1 | com_finder (3.0.0) 1 | com_installer (3.0.0) 1 | com_joomlaupdate (3.6.2) 1 | com_languages (3.0.0) 1 | com_login (3.0.0) 1 | com_media (3.0.0) 1 | com_menus (3.0.0) 1 | com_messages (3.0.0) 1 | com_modules (3.0.0) 1 | com_newsfeeds (3.0.0) 1 | com_plugins (3.0.0) 1 | com_postinstall (3.2.0) 1 | com_privacy (3.9.0) 1 | com_redirect (3.0.0) 1 | com_search (3.0.0) 1 | com_tags (3.1.0) 1 | com_templates (3.0.0) 1 | com_users (3.0.0) 1 |
3rd Party:: ImageShow (5.0.15) 1 | ImageShow (5.0.15) 1 | PageBuilder (1.4.6) 1 | UniForm (4.1.29) 1 | JSN EasySlider (2.1.15) 1 | Akeeba (8.0.4) 1 | COM_JCE (2.9.7) 1 |

Modules :: Site ::
Core :: mod_articles_archive (3.0.0) 1 | mod_articles_categories (3.0.0) 1 | mod_articles_category (3.0.0) 1 | mod_articles_latest (3.0.0) 1 | mod_articles_news (3.0.0) 1 | mod_articles_popular (3.0.0) 1 | mod_banners (3.0.0) 1 | mod_breadcrumbs (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_finder (3.0.0) 1 | mod_footer (3.0.0) 1 | mod_languages (3.5.0) 1 | mod_login (3.0.0) 1 | mod_menu (3.0.0) 1 | mod_random_image (3.0.0) 1 | mod_related_items (3.0.0) 1 | mod_search (3.0.0) 1 | mod_stats (3.0.0) 1 | mod_syndicate (3.0.0) 1 | mod_tags_popular (3.1.0) 1 | mod_tags_similar (3.1.0) 1 | mod_users_latest (3.0.0) 1 | mod_whosonline (3.0.0) 1 | mod_wrapper (3.0.0) 1 |
3rd Party:: JSN ImageShow (5.0.15) 1 | JSN UniForm (4.1.29) 1 | JSN EasySlider (2.1.15) 1 | Easy Facebook Embedded Posts (1.0) 1 | GTranslate (3.7.6) 1 |

Modules :: Admin ::
Core :: mod_custom (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_latest (3.0.0) 1 | mod_latestactions (3.9.0) 1 | mod_logged (3.0.0) 1 | mod_login (3.0.0) 1 | mod_menu (3.0.0) 1 | mod_multilangstatus (3.0.0) 1 | mod_popular (3.0.0) 1 | mod_privacy_dashboard (3.9.0) 1 | mod_quickicon (3.0.0) 1 | mod_sampledata (3.8.0) 1 | mod_stats_admin (3.0.0) 1 | mod_status (3.0.0) 1 | mod_submenu (3.0.0) 1 | mod_title (3.0.0) 1 | mod_toolbar (3.0.0) 1 | mod_version (3.0.0) 1 |
3rd Party:: JSN ImageShow Quick Icons (5.0.15) 1 |

Libraries ::
Core ::
3rd Party:: file_fof40 (4.0.3) ? |

Plugins ::
Core :: PLG_ACTIONLOG_JOOMLA (3.9.0) 1 | plg_authentication_cookie (3.0.0) 1 | plg_authentication_gmail (3.0.0) 0 | plg_authentication_joomla (3.0.0) 1 | plg_authentication_ldap (3.0.0) 0 | plg_captcha_recaptcha (3.4.0) 0 | plg_captcha_recaptcha_invisible (3.8) 0 | plg_content_confirmconsent (3.9.0) 0 | plg_content_emailcloak (3.0.0) 0 | plg_content_fields (3.7.0) 1 | plg_content_finder (3.0.0) 1 | plg_content_joomla (3.0.0) 1 | plg_content_loadmodule (3.0.0) 1 | plg_content_pagebreak (3.0.0) 1 | plg_content_pagenavigation (3.0.0) 1 | plg_content_vote (3.0.0) 0 | plg_editors-xtd_article (3.0.0) 1 | plg_editors-xtd_fields (3.7.0) 1 | plg_editors-xtd_image (3.0.0) 1 | plg_editors-xtd_menu (3.7.0) 1 | plg_editors-xtd_module (3.5.0) 1 | plg_editors-xtd_pagebreak (3.0.0) 1 | plg_editors-xtd_readmore (3.0.0) 1 | plg_extension_joomla (3.0.0) 1 | plg_fields_calendar (3.7.0) 1 | plg_fields_checkboxes (3.7.0) 1 | plg_fields_color (3.7.0) 1 | plg_fields_editor (3.7.0) 1 | plg_fields_imagelist (3.7.0) 1 | plg_fields_integer (3.7.0) 1 | plg_fields_list (3.7.0) 1 | plg_fields_media (3.7.0) 1 | plg_fields_radio (3.7.0) 1 | plg_fields_repeatable (3.9.0) 1 | plg_fields_sql (3.7.0) 1 | plg_fields_text (3.7.0) 1 | plg_fields_textarea (3.7.0) 1 | plg_fields_url (3.7.0) 1 | plg_fields_user (3.7.0) 1 | plg_fields_usergrouplist (3.7.0) 1 | plg_finder_categories (3.0.0) 1 | plg_finder_contacts (3.0.0) 1 | plg_finder_content (3.0.0) 1 | plg_finder_newsfeeds (3.0.0) 1 | plg_finder_tags (3.0.0) 1 | PLG_INSTALLER_FOLDERINSTALLER (3.6.0) 1 | plg_installer_packageinstaller (3.6.0) 1 | PLG_INSTALLER_URLINSTALLER (3.6.0) 1 | plg_privacy_actionlogs (3.9.0) 1 | plg_privacy_consents (3.9.0) 1 | plg_privacy_content (3.9.0) 1 | plg_privacy_message (3.9.0) 1 | plg_privacy_user (3.9.0) 1 | plg_quickicon_extensionupdate (3.0.0) 1 | plg_quickicon_joomlaupdate (3.0.0) 1 | plg_quickicon_phpversioncheck (3.7.0) 1 | plg_quickicon_privacycheck (3.9.0) 1 | plg_search_categories (3.0.0) 1 | plg_search_contacts (3.0.0) 1 | plg_search_content (3.0.0) 0 | plg_search_newsfeeds (3.0.0) 1 | plg_search_tags (3.0.0) 1 | PLG_SYSTEM_ACTIONLOGS (3.9.0) 1 | plg_system_cache (3.0.0) 0 | plg_system_debug (3.0.0) 1 | plg_system_fields (3.7.0) 1 | plg_system_highlight (3.0.0) 1 | plg_system_languagecode (3.0.0) 0 | plg_system_languagefilter (3.0.0) 0 | plg_system_log (3.0.0) 1 | plg_system_logout (3.0.0) 1 | plg_system_logrotation (3.9.0) 1 | plg_system_p3p (3.0.0) 0 | plg_system_privacyconsent (3.9.0) 0 | plg_system_redirect (3.0.0) 0 | plg_system_remember (3.0.0) 1 | plg_system_sef (3.0.0) 1 | plg_system_sessiongc (3.8.6) 1 | plg_system_stats (3.5.0) 1 | plg_system_updatenotification (3.5.0) 1 | plg_twofactorauth_totp (3.2.0) 0 | plg_twofactorauth_yubikey (3.2.0) 0 | plg_user_contactcreator (3.0.0) 0 | plg_user_joomla (3.0.0) 1 | plg_user_profile (3.0.0) 0 | plg_user_terms (3.9.0) 0 |
3rd Party:: PLG_ACTIONLOG_AKEEBABACKUP (8.0.4) 0 | Content — JSN ImageShow (5.0.15) 1 | JSN PageBuilder Plugin Content (1.4.6) 1 | JSN_UNIFORM_PLUGIN_CONTENT_TITLE (4.1.29) 1 | JSN_EASYSLIDER_PLUGIN_CONTENT_TITLE (2.1.15) 1 | plg_content_jce (2.9.7) 1 | plg_editors_codemirror (5.60.0) 1 | plg_editors_tinymce (4.5.12) 1 | plg_editors_jce (2.9.7) 1 | Button — ImageShow (5.0.15) 1 | Button — JSN PageBuilder (1.4.6) 1 | JSN_UNIFORM_PLUGIN_BUTTON_TITLE (4.1.29) 1 | JSN_EASYSLIDER_PLUGIN_BUTTON_TITLE (2.1.15) 1 | plg_extension_jsnframework (2.1.10) 1 | plg_extension_jce (2.9.7) 1 | plg_fields_mediajce (2.9.7) 1 | plg_installer_jce (2.9.7) 1 | plg_quickicon_jce (2.9.7) 1 | plg_quickicon_akeebabackup (8.0.4) 1 | JSN PageBuilder extended — Content (1.4.6) ? | JSN PageBuilder extended — K2 Searc (1.4.6) ? | plg_system_sunfw (2.2.30) 1 | System — JSN ImageShow (5.0.15) 1 | plg_extension_jsnframework (2.1.10) 1 | plg_system_jsnframework (2.1.10) 1 | System — JSN PageBuilder (1.4.6) 1 | System — JSN Uniform (4.1.29) 1 | PLG_SYSTEM_EASYSLIDER (2.1.15) 1 | plg_system_jce (2.9.7) 1 | plg_system_jsntplframework (3.2.9) 1 | PLG_SYSTEM_BACKUPONUPDATE (8.0.4) 0 | Source Picasa (1.1.8) 1 | Theme Classic (1.4.3) 1 | Theme Carousel (1.1.5) 1 | Theme Slider (1.2.9) 1 | JSN PageBuilder — Alert Element (@version) ? | JSN PageBuilder extended — Default (1.4.6) ? | plg-uniform — Mailchimp (4.1.29) 1 | PLG_UNIFORM_PAYMENT_PAYPAL (4.1.29) 1 |

Templates Discovered :: wrote:Templates :: Site :: beez3 (3.1.0) 1 | protostar (1.0) 1 | jsn_epic2_pro (2.0.7) 1 | jsn_epic_pro (6.2.3) 1 |
Templates :: Admin :: hathor (3.0.0) 1 | isis (1.0) 1 |

toivo: Joomla! Master; Posts: 15503; Joined: Thu Feb 15, 2007 5:48 am; Location: Sydney, Australia

Re: Administrator login page error

Post

by toivo » Fri May 28, 2021 6:42 am

The PageBuilder, presumably JSN PageBuilder 3, version 1.4.6 is out of date. The current version is 1.5.8, updated in October 2020.

You could edit the extensions table in the database and disable the PageBuilder plugins one by one and test the back end.

Error Reporting: 22519

The value 22519 indicates that PHP notices, strict and deprecated messages are filtered. Use the value ‘maximum’ in the file configuration.php and the numeric value of Error Reporting changes into 32767 and all the errors (E_ALL in PHP) will be displayed.

If you have a current backup of the database and the file system using Akeeba Backup, install Wampserver on your workstation, then restore the backup into a virtual host by using the Kickstart utility and you can then modify a copy of the website in a test environment to get to the bottom of the issue.

Toivo Talikka, Global Moderator

stubby_finger48: Joomla! Apprentice; Posts: 5; Joined: Fri May 28, 2021 3:06 am

Re: Administrator login page error

Post

by stubby_finger48 » Fri May 28, 2021 7:21 am

Thank you for the suggestions Toivo, I tried editing the extensions table and disabling the PageBuilder extensions one by one but was never able to get the /administrator page to load. I did manage to break some stuff on the main page somehow though. When I enabled debug it only came up on the main website, it didn’t show anything when I tried to load the admin page. I think I will call it a night, it’s almost 2:30am. Maybe I will see what I’m doing wrong after some sleep. Thanks again.

stubby_finger48: Joomla! Apprentice; Posts: 5; Joined: Fri May 28, 2021 3:06 am

Re: Administrator login page error

Post

by stubby_finger48 » Fri May 28, 2021 4:32 pm

Well, this morning I tried wiping out the home directory restoring the site with a backup from about month ago using akeeba kickstarter. The site restored without any issues and the main site is working but I still have the exact same problem with the /administrator page where it never starts to load at all, no login screen, nothing just sits there for a couple minutes and then the Internal server error screen shows up. Would this indicate that it is a PHP problem? would trying a different PHP version have any effect? There is an option to select different versions from the dreamhost control panel.

leolam: Joomla! Master; Posts: 20521; Joined: Mon Aug 29, 2005 10:17 am; Location: Netherlands/ Germany/ S’pore/Bogor/ North America; Contact:

Re: Administrator login page error

Post

by leolam » Fri May 28, 2021 5:47 pm

You have no other option than to disable all non-core admin extensions and successively enable them 1 by 1 to see which one is the culprit. One of them is not compatible with PHP 7.4 which is causing the issue

Makes no sense to set back to PhP 7,3 since that is dead already and won’t be supported shortly now any longer so you need to find the culprit in the ADMIN-extensions and replace it. It is not any of the site extensions

Leo

Webdongle: Joomla! Master; Posts: 42388; Joined: Sat Apr 05, 2008 9:58 pm

Re: Administrator login page error

Post

by Webdongle » Sat May 29, 2021 6:45 am

Use phpMyAdmin to set Protostar as the default front end Template.

If the problem occurred after upgrading to php 7.4 then change it to 7.3

leolam: Joomla! Master; Posts: 20521; Joined: Mon Aug 29, 2005 10:17 am; Location: Netherlands/ Germany/ S’pore/Bogor/ North America; Contact:

Re: Administrator login page error

Post

by leolam » Sat May 29, 2021 7:52 am

@Webdongle and then being stuck on PHP7.3 with Joomla 4 around the corner? Is that good advice? What should the user do after he is well running on PHP7.3 in your opinion?

Leo

Webdongle: Joomla! Master; Posts: 42388; Joined: Sat Apr 05, 2008 9:58 pm

Re: Administrator login page error

Post

by Webdongle » Sat May 29, 2021 9:14 am

@leo
Now you are just being silly or deliberately argumentative. Nobody is suggesting staying on php 7.3.

Just that if the op can get into the backend then it will be easier for them to change the default template and disable the 3rd party extensions.

They can then switch back to php 7.4 to enable the 3rd party extensions one by one.

stubby_finger48: Joomla! Apprentice; Posts: 5; Joined: Fri May 28, 2021 3:06 am

Re: Administrator login page error

Post

by stubby_finger48 » Sat May 29, 2021 10:13 pm

Thanks for all the help, looks like disabling plg_system_jsntplframework and jsn_epic_pro allowed the admin page to load again. Not sure why it suddenly had an issue, but at least we can work with it now.

leolam: Joomla! Master; Posts: 20521; Joined: Mon Aug 29, 2005 10:17 am; Location: Netherlands/ Germany/ S’pore/Bogor/ North America; Contact:

Re: Administrator login page error

Post

by leolam » Sun May 30, 2021 6:31 am

And so are many out-of-date

SP Page Builder v3.7.10 Brings PHP 8 and MySQL 8 Support

, Uniform, Template, tons of modules and plugins.

% month new site with fully outdated extensions installed. I strongly advise the owners to manage their site properly. This is bad Webmastering regretfully and you are lucky that you have not been hacked and whacked yet

Leo

Return to “Administration Joomla! 3.x”

Jump to

Joomla! Announcements
↳ Announcements
↳ Announcements Discussions
Joomla! 4.x — Ask Support Questions Here
↳ General Questions/New to Joomla! 4.x
↳ Installation Joomla! 4.x
↳ Administration Joomla! 4.x
↳ Migrating and Upgrading to Joomla! 4.x
↳ Extensions for Joomla! 4.x
↳ Security in Joomla! 4.x
↳ Templates for Joomla! 4.x
↳ Search Engine Optimization (Joomla! SEO) in Joomla! 4.x
↳ Language — Joomla! 4.x
↳ Performance — Joomla! 4.x
↳ Joomla! 4.x Coding
Joomla! 3.x — Ask Support Questions Here
↳ General Questions/New to Joomla! 3.x
↳ Installation Joomla! 3.x
↳ Joomla! 3.x on IIS webserver
↳ Administration Joomla! 3.x
↳ Access Control List (ACL) in Joomla! 3.x
↳ Migrating and Upgrading to Joomla! 3.x
↳ Security in Joomla! 3.x
↳ Extensions for Joomla! 3.x
↳ Templates for Joomla! 3.x
↳ Search Engine Optimization (Joomla! SEO) in Joomla! 3.x
↳ Language — Joomla! 3.x
↳ Performance — Joomla! 3.x
↳ Joomla! 3.x Coding
Joomla! Versions which are End of Life
↳ Joomla! 2.5 — End of Life 31 Dec 2014
↳ General Questions/New to Joomla! 2.5
↳ Installation Joomla! 2.5
↳ Joomla! 2.5 on IIS webserver
↳ Administration Joomla! 2.5
↳ Access Control List (ACL) in Joomla! 2.5
↳ Migrating and Upgrading to Joomla! 2.5
↳ Security in Joomla! 2.5
↳ Extensions for Joomla! 2.5
↳ Templates for Joomla! 2.5
↳ Search Engine Optimization (Joomla! SEO) in Joomla! 2.5
↳ Language — Joomla! 2.5
↳ Performance — Joomla! 2.5
↳ Joomla! 1.5 — End of Life Sep 2012
↳ General Questions/New to Joomla! 1.5
↳ Installation 1.5
↳ Joomla! 1.5 on IIS webserver
↳ Administration 1.5
↳ Migrating and Upgrading to Joomla! 1.5
↳ Security in Joomla! 1.5
↳ Extensions for Joomla! 1.5
↳ Templates for Joomla! 1.5
↳ Search Engine Optimization (Joomla! SEO) in Joomla! 1.5
↳ Language — Joomla! 1.5
↳ Performance — Joomla! 1.5
↳ Joomla! 1.0 — End of Life 22 July 2009
↳ Installation — 1.0.x
↳ Upgrading — 1.0.x
↳ Security — 1.0.x
↳ 3rd Party/Non Joomla! Security Issues
↳ Administration — 1.0.x
↳ Extensions — 1.0.x
↳ Components
↳ Modules
↳ Plugins/Mambots
↳ WYSIWYG Editors — 1.0.x
↳ Integration & Bridges — 1.0.x
↳ phpbb — Joomla! Integration
↳ Templates & CSS — 1.0.x
↳ Language — 1.0.x
↳ Joom!Fish and Multilingual Sites
↳ Performance — 1.0.x
↳ General Questions — 1.0.x
Joomla! International Language Support
↳ International Zone
↳ Arabic Forum
↳ تنبيهات هامة
↳ الدروس
↳ 4.x جوملا!
↳ جوملا! 1.6/1.7
↳ الأسئلة الشائعة
↳ التثبيت و الترقية
↳ الحماية — و تحسين السرعة والأداء
↳ لوحة التحكم
↳ الإضافات البرمجية
↳ تعريب جوملا! و الإضافات البرمجية
↳ القوالب و التصميم
↳ صداقة محركات البحث
↳ القسم العام
↳ 1.5 !جوملا
↳ الأسئلة الشائعة
↳ التثبيت و الترقية
↳ الحماية — و تحسين السرعة والأداء
↳ لوحة التحكم
↳ الإضافات البرمجية
↳ تعريب جوملا! و الإضافات البرمجية
↳ القوالب و التصميم
↳ صداقة محركات البحث
↳ القسم العام
↳ جوملا! 1.0
↳ الأسئلة الشائـعة
↳ التثبيت
↳ لوحة التحكم
↳ الإضافات البرمجية
↳ الإضافات المعرّبة
↳ القوالب و التصميم
↳ الحماية — تحسين السرعة والأداء — صداقة محركات البحث
↳ القسم العام
↳ القسم العام
↳ !عرض موقعك بجوملا
↳ الأرشيف
↳ Bengali Forum
↳ Bosnian Forum
↳ Joomla! 1.5
↳ Instalacija i prvi koraci
↳ Ekstenzije
↳ Templejti
↳ Moduli
↳ Prevodi i dokumentacija
↳ Joomla! 1.7 / Joomla! 1.6
↳ Catalan Forum
↳ Notícies
↳ Temes sobre l’administració
↳ Temes sobre la traducció
↳ Components, mòduls i joombots
↳ Temes de disseny
↳ Webs realitzades amb Joomla!
↳ Offtopics
↳ Chinese Forum
↳ Croatian Forum
↳ Danish Forum
↳ Meddelelser
↳ Joomla! 4.x
↳ Joomla! 3.x (Anbefalet til nye installationer. Nyeste funktionalitet)
↳ Installation, backup, opdatering og flytning — Godt igang
↳ Administration — Generel brug
↳ Komponenter, Moduler og Plugins
↳ Template, CSS og Design
↳ Nethandel, betaling m.m.
↳ Ældre versioner (disse vedligeholdes ikke længere fra officiel side)
↳ Joomla! 2.5 (Supporteres indtil 31. dec. 2014)
↳ Installation, backup, opdatering og flytning — Godt igang
↳ Administration — Generel brug
↳ Komponenter, Moduler og Plugins
↳ Template, CSS og Design
↳ Nethandel, betaling m.m.
↳ Joomla 1.5 (Tidligere langtidssupporteret version indtil sep. 2012)
↳ Installation, backup, opdatering og flytning — Godt igang
↳ Administration — Generel brug
↳ Komponenter, Moduler og Plugins
↳ Template, CSS og Design
↳ Nethandel, betaling m.m.
↳ Joomla 1.0 (Udgået version, der blev afløst af 1.5 i 2008)
↳ Installation, backup, opdatering og flytning — Godt igang
↳ Administration — Generel brug
↳ Komponenter, Moduler og Mambots
↳ Template, CSS og Design
↳ Nethandel, betaling m.m.
↳ Oversættelser (lokalisering)
↳ Joomla brugergrupper i Danmark
↳ JUG Kolding
↳ JUG København
↳ JUG Odense
↳ JUG Århus
↳ JUG Sorø
↳ Kommerciel (betalt) hjælp ønskes
↳ SEO
↳ FAQ — Dokumentation og vejledninger
↳ Vis dit websted
↳ Afviste ‘Vis dit websted’ indlæg
↳ Diverse (Off topic)
↳ Dutch Forum
↳ Aankondigingen
↳ Algemene vragen
↳ Joomla! 4.x
↳ Joomla! 3.x
↳ Installatie 3.x
↳ Extensies 3.x
↳ Templates 3.x
↳ Joomla! 2.5
↳ Installatie 2.5
↳ Componenten 2.5
↳ Modules 2.5
↳ Plugins 2.5
↳ Templates 2.5
↳ Joomla! 1.5
↳ Installatie
↳ Componenten
↳ Modules
↳ Plugins
↳ Templates
↳ Joomla! 1.0
↳ Installatie 1.0.x
↳ Componenten 1.0.x
↳ Modules 1.0.x
↳ Mambots 1.0.x
↳ Templates 1.0.x
↳ Vertalingen
↳ Offtopic
↳ Show jouw website
↳ Filipino Forum
↳ International Support Center
↳ Pinoy General Discussion & Archives
↳ Site Showcase
↳ Events
↳ Design Tips and Tricks
↳ Tsismis Zone
↳ Pinoy Translation Zone
↳ Pinoy Forum Archives
↳ Joomla! Philippines Local Forum www.joomla.org.ph
↳ Finnish Forum
↳ French Forum
↳ Les annonces!
↳ Le bistrot!
↳ L’expo!
↳ J! 4.x — L’atelier!
↳ J! 3.x — L’atelier!
↳ 3.x — Questions générales, nouvel utilisateur
↳ 3.x — Installation, migration et mise à jour
↳ 3.x — Sécurité et performances
↳ 3.x — Extensions tierce partie
↳ 3.x — Templates et design
↳ 3.x — Développement
↳ 3.x — Ressources
↳ J! 2.5.x — L’atelier!
↳ 2.5 — Questions générales
↳ 2.5 — Installation, migration et mise à jour
↳ 2.5 — Sécurité et performances
↳ 2.5 — Extensions tierce partie
↳ 2.5 — Templates et design
↳ 2.5 — Développement
↳ 2.5 — Ressources
↳ J! 1.5.x — L’atelier!
↳ 1.5 — Questions générales
↳ 1.5 — Installation, migration et mise à jour
↳ 1.5 — Sécurité et performances
↳ 1.5 — Extensions tierce partie
↳ 1.5 — Templates et design
↳ 1.5 — Développement
↳ 1.5 — Ressources
↳ J! 1.0.x — L’atelier!
↳ 1.0 — Questions générales
↳ 1.0 — Installation et mise à jour
↳ 1.0 — Sécurité
↳ 1.0 — Extensions tierce partie
↳ 1.0 — Templates et design
↳ 1.0 — Développement
↳ 1.0 — Ressources
↳ Besoin d’un professionel ?
↳ Extensions Open Source pour Joomla!
↳ German Forum
↳ Ankündigungen
↳ Joomla! 4.x
↳ Joomla! 3.x
↳ Allgemeine Fragen
↳ Installation und erste Schritte
↳ Komponenten, Module, Plugins
↳ Template, CSS und Designfragen
↳ Entwicklerforum
↳ Zeige Deine Webseite
↳ Joomla! 2.5
↳ Allgemeine Fragen
↳ Installation und erste Schritte
↳ Komponenten, Module, Plugins
↳ Template, CSS und Designfragen
↳ Entwicklerforum
↳ Zeige Deine Webseite
↳ Joomla! 1.5
↳ Allgemeine Fragen
↳ Installation und erste Schritte
↳ Komponenten, Module, Plugins
↳ Template, CSS und Designfragen
↳ Entwicklerforum
↳ Zeige Deine Webseite
↳ Professioneller Service
↳ Sonstiges (Offtopic)
↳ Archiv
↳ Joomla! 1.0
↳ Allgemeine Fragen 1.0.x
↳ Installation und erste Schritte 1.0.x
↳ Komponenten, Module, Mambots 1.0.x
↳ Template, CSS und Designfragen 1.0.x
↳ Entwicklerforum 1.0.x
↳ Zeige Deine Webseite 1.0.x
↳ Greek Forum
↳ Joomla! 4.x
↳ Joomla! 3.x
↳ Joomla! 2.5.x
↳ Joomla! 1.5.x
↳ Joomla! 1.0.x
↳ Hebrew Forum
↳ Indic Languages Forum
↳ Indonesian Forum
↳ FAQ
↳ Bantuan
↳ Komponen
↳ Modul
↳ Template
↳ Diskusi
↳ Italian Forum
↳ Guide
↳ Traduzioni
↳ Componenti — Moduli — Plugins
↳ Template — Grafica
↳ Notizie
↳ Prodotti Open Source per Joomla!
↳ Richieste professionali
↳ Joomla! 4.x
↳ Joomla! 3.x
↳ Joomla! 2.5.x
↳ Joomla! 1.x
↳ Latvian Forum
↳ Lithuanian Forum
↳ Joomla! 4.x
↳ Joomla! 1.5
↳ Joomla! 1.7 / Joomla! 1.6
↳ Joomla! 1.0
↳ Vertimai ir Kalba
↳ Malaysian Forum
↳ Solved
↳ Norwegian Forum
↳ Informasjon
↳ Arkiverte annonseringer
↳ FAQ — Ofte spurte spørsmål
↳ Arkiv
↳ Joomla! 4.x
↳ Joomla! 3.x
↳ Administrasjon/installasjon
↳ Migrering/Oppdatering
↳ Template, CSS og design
↳ Komponenter/moduler/programutvidelser
↳ Sikkerhet
↳ Generelt
↳ Netthandel, betaling m.m.
↳ VirtueMart
↳ Andre nettbutikkløsninger
↳ Generelt
↳ Oversettelser
↳ Fremvisning av sider (Show off)
↳ Avviste fremvisninger
↳ Diverse (off topic)
↳ Kommersiell hjelp ønskes
↳ Eldre versjoner av Joomla!
↳ Joomla! 1.0
↳ Administrasjon/installasjon
↳ Template, CSS og design
↳ Komponenter/moduler/mambots
↳ Sikkerhet
↳ Generelt
↳ Joomla! 1.5
↳ Administrasjon/installasjon
↳ Migrering/Oppdatering
↳ Template, CSS og design
↳ Komponenter/moduler/programutvidelser
↳ Sikkerhet
↳ Generelt
↳ Joomla! 2.5
↳ Administrasjon/installasjon
↳ Migrering/Oppdatering
↳ Template, CSS og design
↳ Komponenter/moduler/programutvidelser
↳ Sikkerhet
↳ Generelt
↳ Persian Forum
↳ قالب ها
↳ مدیریت
↳ سوالهای عمومی
↳ نصب
↳ مامبوت ها
↳ ماژولها
↳ کامپوننت ها
↳ Polish Forum
↳ Instalacja i aktualizacja
↳ Administracja
↳ Komponenty, moduły, wtyczki
↳ Szablony
↳ Paczta i Podziwiajta
↳ Modyfikacje i własne rozwiązania
↳ Tłumaczenia
↳ FAQ
↳ Tips&Tricks
↳ Dokumentacja
↳ Profesjonalne usługi
↳ Portuguese Forum
↳ Componentes, módulos e mambots
↳ Programação e desenvolvimento
↳ Segurança
↳ Sites dos usuários
↳ Off-topic
↳ Tradução
↳ Templates
↳ Romanian Forum
↳ Traduceri
↳ Russian Forum
↳ Объявления по Joomla!
↳ Безопасность Joomla!
↳ Joomla 4.x — Задайте здесь свой вопрос по поддержке
↳ Joomla 3.x — Задайте здесь свой вопрос по поддержке
↳ Общие вопросы/Новичок в Joomla! 3.x
↳ Установка Joomla! 3.x
↳ Миграция и переход на Joomla! 3.x
↳ Расширения для Joomla! 3.x
↳ Многоязычные веб-сайты на Joomla 3.x
↳ Joomla 2.5 — Задайте здесь свой вопрос по поддержке
↳ Общие вопросы/Новичок в Joomla! 2.5
↳ Установка Joomla! 2.5
↳ Расширения для Joomla! 2.5
↳ Русский язык Joomla! 2.5
↳ Serbian/Montenegrin Forum
↳ Tehnička pitanja
↳ Instalacija i početnička pitanja
↳ Šabloni
↳ Prevod i dokumentacija
↳ Ćaskanje
↳ Bezbednost
↳ Joomla! dodaci
↳ Pravna pitanja
↳ Arhiva
↳ Joomla! Događaji i Zajednica
↳ Izlog (spisak) sajtova radjenih u Joomla! CMS-u
↳ Profesionalne usluge
↳ Slovak Forum
↳ Spanish Forum
↳ Joomla! 4.x
↳ Joomla! 3.x
↳ Migración y actualización a Joomla 3.x
↳ Versiones de Joomla! obsoletas
↳ Joomla! 2.5
↳ Joomla! 1.5
↳ Extensiones
↳ Plantillas (templates) y diseño
↳ Idioma y traducciones
↳ SEO para Joomla!
↳ Seguridad y rendimiento
↳ Productos de Código Abierto para Joomla!
↳ Servicios profesionales
↳ Salón de la comunidad Ñ
↳ Swedish Forum
↳ Meddelanden
↳ Forum Joomla! 4.x
↳ Forum Joomla! 3.x
↳ Allmänna frågor
↳ Användning och administration
↳ Installation, backup och säkerhet
↳ Komponenter, moduler och plugin
↳ Mallar (templates) och design
↳ Äldre versioner
↳ Forum Joomla! 1.0
↳ Allmänna frågor
↳ Användning och administration
↳ Installation, backup och säkerhet
↳ Komponenter, moduler och Mambots
↳ Mallar (templates) och design
↳ Forum Joomla! 1.7 / Joomla! 1.6
↳ Allmänna frågor
↳ Användning och administration
↳ Installation, backup och säkerhet
↳ Komponenter, moduler och plugin
↳ Mallar (templates) och design
↳ Forum Joomla! 1.5
↳ Allmänna frågor
↳ Användning och administration
↳ Installation, backup och säkerhet
↳ Komponenter, moduler och plugin
↳ Mallar (templates) och design
↳ Forum Joomla! 2.5
↳ Allmänna frågor
↳ Användning och administration
↳ Installation, backup och säkerhet
↳ Komponenter, moduler och plugin
↳ Mallar (templates) och design
↳ Översättning
↳ Webbplatser gjorda i Joomla
↳ Webbplatser J! 3.x
↳ Webbplatser J! 2.5
↳ Webbplatser Joomla! 1.7 / Joomla! 1.6
↳ Webbplatser J! 1.5
↳ Webbplatser J! 1.0
↳ Kommersiell hjälp önskas
↳ Diverse (off topic)
↳ Tamil Forum
↳ Thai Forum
↳ โชว์เว็บไซต์ของคุณที่สร้างด้วยจูมล่า
↳ เคล็ดลับการใช้งานส่วนต่างๆ เกี่ยวกับจ&#
↳ คอมโพเน้นท์ โมดูล ปลักอิน ต่างๆ ที่ติดตั
↳ อับเดดข่าวสารเกี่ยวกับจูมล่าลายไทย
↳ Turkish Forum
↳ Duyurular
↳ Dersler
↳ Genel Sorular
↳ Bileşen, Modül, Bot
↳ Eklenti Haberleri
↳ Temalar
↳ Vietnamese Forum
↳ Gặp gỡ và giao lưu
↳ Joomla Tiếng Việt
↳ Cài đặt — Cấu hình
↳ Thành phần mở rộng cho Joomla!
↳ Hỏi đáp Joomla! 3.x
↳ Hỏi đáp Joomla! 2.5
↳ Hỗ trợ kỹ thuật
↳ Bài viết cũ
↳ Thiết kế Template
↳ Joomla! 1.5
↳ Hỏi đáp Joomla! 4.x
↳ Welsh Forum
Other Forums
↳ Open Source Products for Joomla!
↳ The Lounge
↳ Forum Post Assistant (FPA)
Joomla! Development Forums
Joomla! Official Sites & Infrastructure
↳ docs.joomla.org — Feedback/Information
↳ extensions.joomla.org — Feedback/Information
↳ joomla.com — Feedback/Information
↳ Sites & Infrastructure — Feedback/Information
↳ Archived Boards — All boards closed
↳ Design and Accessibility — Archived
↳ Quality and Testing — Locked and Archived
↳ Joomla! 1.0.x_Q&T
↳ Q&T 1.0.x Resolved
↳ Known Issues
↳ Superseded Issues
↳ Archive
↳ Q&T 1.0.x Resolved — Archived
↳ Known Issues — Archive
↳ Superseded Issues — Archive
↳ Joomla! 3.x Bug Reporting
↳ Third Party Testing for Joomla! 1.5
↳ Q&T 1.5.x Resolved
↳ Joomla! 1.5 BETA
↳ Joomla! 1.5 BETA 2
↳ Reaction to the ‘Letter to the community’
↳ Reaction to New Project Name
↳ Logo Competition
↳ Humor, Fun and Games
↳ Libraries
↳ patTemplate
↳ com_connector — Multi Joomla Bridge
↳ CiviCRM Support
↳ CiviCRM Installation Issues
↳ FAQ Archive
↳ FAQ Discussion Board
↳ 3rd Party Extensions FAQ
↳ FAQs not moved
↳ 3rd Party/Non Joomla! Security FAQ
↳ Joomla! Coding 101
↳ Joombie Tools of the Trade
↳ Joombie Coding Q/A
↳ Joombie Think Tank
↳ Joombie Developer Lab
↳ Joomla Forge — Archived
↳ Non-Profit Organizations and Joomla!
↳ Schools and Universities
↳ Bangsamoro Forum
↳ Joomla! 1.5 Template Contest
↳ SMF — Simplemachines.org Forum
↳ GPL Discussion
↳ Security Announcements — Old
↳ Tips & Tricks — Moving
↳ Submit Your Suggested Tips & Tricks to Docs.joomla.org now please.
↳ Google Summer of Code and GHOP
↳ Google Summer of Code 2008
↳ Proposed projects
↳ Student area
↳ Past Google Summer of Code Editions
↳ Google’s Highly Open Participation Contest
↳ Documentation
↳ Suggestions, Modifications, and Corrections
↳ Archive
↳ 1.5 Archive
↳ Suggestions, Modifications & Corrections
↳ Submit
↳ Feedback and Suggestions
↳ Applications for participation in the Development Workgroup
↳ Development
↳ 1.5 Site Showcase — Archived
↳ 1.0 x Site Showcase — Archived.
↳ Feature Requests — White Papers — Archived
↳ Under Review — Archived
↳ Accepted — Archived
↳ Not Accepted — Archived
↳ Wishlists and Feature Requests — Archive
↳ Wishlist Archives — Archived
↳ Spanish Forum — Archive
↳ Papelera
↳ Tutoriales
↳ General
↳ Salón de la Joomlaesfera hispanohablante
↳ Danish Forum — Archive
↳ Diskussion af Meddelelser + Sikkerhedsmeddelelser + FAQ
↳ Shop.Joomla.org
↳ Joomla! 1.6 RC Support [closed]
↳ Joomla! 1.0 Coding
↳ Core Hacks and Patches
↳ Joomla! 2.5 Beta Support
↳ People.joomla.org — Feedback/Information
↳ Joomla! 1.5 Bug Reporting
↳ Joomla! 1.5 Coding
↳ Joomla! 3 Beta Support
↳ Trending Topics
↳ Help wanted in the community
↳ templates.joomla.org — Feedback/Information
↳ Certification
↳ Albanian Forum
↳ Azeri Forum
↳ Urdu Forum
↳ Basque Forum
↳ Itzulpenaren inguruan
↳ Laguntza teknikoa
↳ Belarusian Forum
↳ Maltese Forum
↳ Hungarian Forum
↳ Slovenian Forum
↳ Japanese Forum
↳ Khmer Forum
↳ ពិពណ៌ស្ថានបណ្ដាញជុំឡា
↳ ជុំឡាខ្មែរមូលដ្ឋានីយកម្ម
↳ Community Blog Discussions
↳ JoomlaCode.org
↳ Joomla! Marketing and PR Team
↳ resources.joomla.org — Feedback/Information
↳ Training.Joomla.org
↳ OpenSourceMatters.org
↳ magazine.joomla.org — Feedback/Information
↳ Site Showcase
↳ Joomla! 4 Related
↳ Joomla! Events
↳ Joomla! Ideas Forum
↳ Registered Joomla! User Groups
↳ Joomla! 2.5 Coding
↳ Joomla! 2.5 Bug Reporting
↳ User eXperience (UX)
↳ Joomla! Working Groups
↳ Translations

Источник

TITLE:

mod_php showing outputting warnings in HTML while display_errors Off

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk Onyx 17.5, x64, Ubuntu 14.04 Trusty / CloudLinux 6.8

PROBLEM DESCRIPTION:

Hi,

after upgrading both servers from Plesk 12.5 to Plesk 17.5
We were contacted by our customers that their sites started showing PHP Warnings in the web browser.

When looking into this, it seems that Apache configs have been changed to now include
«php_admin_value error_reporting xxxxx»

<IfModule sapi_apache2.c>
php_admin_flag engine on

# General settings
php_admin_flag safe_mode off
php_admin_value open_basedir none
php_admin_value error_reporting 22519
# Performance settings
# Additional directives

</IfModule>

<IfModule mod_php5.c>
php_admin_flag engine on

# General settings
php_admin_flag safe_mode off
php_admin_value open_basedir none
php_admin_value error_reporting 22519
# Performance settings
# Additional directives

</IfModule>

<IfModule mod_php7.c>
php_admin_flag engine on

# General settings
php_admin_flag safe_mode off
php_admin_value open_basedir none
php_admin_value error_reporting 22519
# Performance settings
# Additional directives

</IfModule>

STEPS TO REPRODUCE:

Create a basic PHP site

and place following file into it:

error.php

<?php
trigger_error(«test», E_USER_WARNING);
?>

Set PHP settings to Apache mod_php and set display_errors to Off (or 0).

This warning should not be displayed via HTML.
And yet it is.

ACTUAL RESULT:

PHP Errors and Warnings are displayed through HTML.

EXPECTED RESULT:

PHP Errors and Warnings should only be logged to error_log when display_errors is set to Off (or 0).

ANY ADDITIONAL INFORMATION:

Fixes:

sed -i.bak ‘/php_admin_value error_reporting/d’ /var/www/vhosts/system/domain.tld/conf/httpd.conf && service httpd restart || service apache2 restart #remove these php_admin_value settings

Possible other fix (stops Errors and Warnings from displaying in HTML as well):

php_admin_value error_reporting «E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED»

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug

IgorG

From developer:

Was not able to reproduce. Here is what I did:

1. Created a webpage with the aforementioned content:

<?php
trigger_error(«test», E_USER_WARNING);
echo ini_get(‘display_errors’);
?>

2. Enabled mod_php5, set the corresponding handler for the domain, set display_errors to «off».

When the webpage is accessed via browser, following directives is created in the Apache configuration:

php_admin_value open_basedir «/var/www/vhosts/qwe.tld/:/tmp/»
php_admin_value error_reporting 32767

However, «display_errors» is still managed by php.ini, and no output presented in the browser.
———-
When «display_errors» turned on via Plesk, the following output is displayed when the webpage accessed:

Warning: test in /var/www/vhosts/qwe.tld/httpdocs/index.php on line 2
1

Disabling «display_errors» via Plesk removes PHP warning from the page again.

Hi,

the issue was traced back to ExpressionEngine using an ExceptionHandler and outputting the captured errors/warnings/notices/etc into the HTML itself.
This functionality was created to be able to log to alternative mechanism then php error log, eg. for when the customer has no access to these, they can log to httpdocs/error.log aswell.
They do this based on the error_reporting() set.

The logic to show errors or not, is defined as:

if (($severity & error_reporting()) == $severity)
{
$_error->show_php_error($severity, $message, $filepath, $line);
}

Where $severity is one of the predifined constants listed here: PHP: Predefined Constants — Manual
2 == E_WARNING

The & operator in PHP is a Bitwise «And» Operator PHP: Bitwise Operators — Manual
And will output the matching bits between $severity and error_reporting() .

The new setting in vhost httpd.conf:

Code:

php_admin_value error_reporting 22519

efectively disables the CMS from setting error_reporting via their internal debugging function:

PHP:

/*
 * --------------------------------------------------------------------
 *  Set the error reporting level
 * --------------------------------------------------------------------
 */
        if (DEBUG == 1)
        {
                error_reporting(E_ALL);
                @ini_set('display_errors', 1);
        }
        else
        {
                error_reporting(0);
        }

If ExpressionEngine is unable to set error_reporting() to 0 it will always be the default 22519
2 & 22519 will output 2

and thus (($severity & error_reporting()) == $severity) will equate to true and errors/warnings.notces/etc will always be shown in HTML!

So why is the httpd conf in Plesk 17.5 now using:

Code:

php_admin_value error_reporting 22519

This makes no sense and cripples the CMS from overriding this in any way..
Please give more info on why this value was «locked» by using the php_admin_value directive or otherwise consider removing this from Plesk again as it was not present in Plesk 12.5 and cripplies all Expression Engine sites running on mod_php!

FastCGI does not have this value «locked» in any way and allows PHP code to set the error_reporting() values:

test.php

PHP:

<?php
echo "Running PHP as: " . php_sapi_name() . "</br>" . PHP_EOL;
echo "Regular error_reporting return function: " . error_reporting() . "</br>" . PHP_EOL;
echo "Suppressed error_reporting return function: " . @error_reporting() . "</br>" . PHP_EOL;
echo "Setting error_reporting to 0 via error_reporting(0)" . "</br>" . PHP_EOL;
error_reporting(0);
echo "error_reporting value is: " . error_reporting() . "</br>" . PHP_EOL;
echo "Setting error_reporting to 0 via @error_reporting(0)" . "</br>" . PHP_EOL;
@error_reporting(0);
echo "error_reporting value is: " . error_reporting() . "</br>" . PHP_EOL;
?>

The Good:

Code:

Running PHP as: cgi-fcgi
Regular error_reporting return function: 22519
Suppressed error_reporting return function: 0
Setting error_reporting to 0 via error_reporting(0)
error_reporting value is: 0
Setting error_reporting to 0 via @error_reporting(0)
error_reporting value is: 0

The Desired (mod_php without php_admin_value error_reporting):

Code:

Running PHP as: apache2handler
Regular error_reporting return function: 22527
Suppressed error_reporting return function: 0
Setting error_reporting to 0 via error_reporting(0)
error_reporting value is: 0
Setting error_reporting to 0 via @error_reporting(0)
error_reporting value is: 0

The Ugly (mod_php with php_admin_value error_reporting 22519):

Code:

Running PHP as: apache2handler
Regular error_reporting return function: 22519
Suppressed error_reporting return function: 0
Setting error_reporting to 0 via error_reporting(0)
error_reporting value is: 22519
Setting error_reporting to 0 via @error_reporting(0)
error_reporting value is: 22519

Источник