L
L
Lucker Spirit2021-11-11 17:27:53
PHP
Lucker Spirit, 2021-11-11 17:27:53

Bitrix, why is the page not displayed?

The site started loading incorrectly. The page displays php-code, css-styles flew off.

618d27ad0617b064133460.png

nginx logs:

m_settings.conf:3
2021/11/11 20:02:36 [info] 2937#0: pagespeed: rollback gzip, explicit configuration in /etc/nginx/nginx.conf:66
2021/11/11 20:09:22 [info] 3444#0: [ngx_pagespeed 1.13.35.2-0] No threading detected. Own threads: 1 Rewrite, 1 Expensive Rewrite.
2021/11/11 20:09:22 [info] 3444#0: Using 262144KiB of shared memory for push stream module on zone: push_stream_module in /etc/nginx/bx/settings/im_settings.conf:3


Apache logs:
[Thu Nov 11 20:09:21.999570 2021] [mpm_prefork:notice] [pid 2950] AH00170: caught SIGWINCH, shutting down gracefully
[Thu Nov 11 20:09:23.103287 2021] [suexec:notice] [pid 3457] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 173.125.161.122. Set the 'ServerName' directive globally to suppress this message
[Thu Nov 11 20:09:23.198946 2021] [mpm_prefork:notice] [pid 3457] AH00163: Apache/2.4.6 (CentOS) PHP/7.2.34 configured -- resuming normal operations
[Thu Nov 11 20:09:23.198996 2021] [core:notice] [pid 3457] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

Answer the question

In order to leave comments, you need to log in

2 answer(s)
A
Adamos, 2021-11-11
@Adamos

Give a hand to the one who edited it crookedly in the built-in editor, open it in a normal editor, restore<?php

T
tgarl, 2021-11-12
@tgarl

There’s no way to explain normally, so hire a specialist right away ...
In general, if you read the comments, the general problem was nevertheless indicated. The problem is that the content of the page was not saved correctly. Through the editor or not - this is not a fact, the author did not say at what point the error appeared.
To correct it, you need to open the page in php mode (via the site admin panel - file structure) or via ftp (which is more correct) and go through the code, closing the tags where necessary and correcting the errors.
In general, such an error often occurs when html and php are mixed on the page and edits are made through the vizeditor - in this case, when editing through the vizeditor, the code is not correctly parsed and saved. So usually everything is formatted either into components and placed on the page or using include areas (in this case, if you break only a small piece in the include area, and not the entire page).

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question