Error in the page code

Hi @ya4elovek

It’s a weird problem, it relates to the WordPress core or hosting/server.

I’ve just followed this topic
https://www.ads-software.com/support/topic/an-error-occurred-while-processing-this-directive-after-wordpress-4-8-update/

You can go to Settings -> Permalinks -> Select Default -> Save -> then back to selected permatlink -> Save again.

Let me know how it goes.

Thank you, but:
I followed your recommendations: settings – > permalinks – > select “simple” – > (https://infoservice-taxi.ru/?p=123) save -> then go back to the selected permatlink – > save again.
The error message did not disappear: [an error occurred while processing the directive]

Hi @ya4elovek

Could you please switch to the default theme of WordPress (Twenty Twenty) and check the problem again?

Or contact your hosting/server provider to ask for help with this case.

Let me know if there is any information.

Thank you for participating!
Switching to any other topic solves the problem. Checked on three different topics. Therefore, I turned to support a specific topic One Press. Am I correct?

hi (@longnguyen)

I turned to the provider:
Website https://infoservice-taxi.ru created on the basis of WordPress 5.3.2 with the theme onepress. Recently, on all pages except home, an error message appeared in the sidebar [an error occurred while processing the directive].

When you change the subject, the message is not displayed.

The problem appeared after the next update of the theme or CMS (but this is not accurate).

Technical support on the site of the authors of the theme and the WordPress forum recommended to contact the hosting provider to check the rights of folders and files, believing that the problem may be in this.

Help to understand, please

The answer of the hosting provider:

Hello!

Some of the files in the theme you are using have comments in the code that contain the #character. The error appeared because of this. Removed the symbol, please check. Pre-clear the browser cache according to the instructions.

We have replaced #content-content-inside with the following files in the /VAR/VSP/u0865728/data/VSP/Infoservice-taxi directory.<url> / WP-content / topics:

./onepress / template-left sidebar.PHP
./ onepress / home.PHP
./onepress/woocommerce.PHP
./onepress / template-full width.PHP
./onepress / index.PHP
./onepress / search.PHP
./onepress / template-fullwidth-stretched.PHP
./onepress / single.PHP
./onepress / page.PHP
./ onepress/404.PHP
./ onepress / archive.PHP

of our side have already made the changes necessary for normal operation, in particular, replaced “# content-inside” (without quotes) with “content-inside” (without quotes) in the files from the directory in /var/www in/u0865728/data/VSP/Infoservice-taxi.<url> / WP-content / topics :

./onepress / template-left sidebar.PHP
./ onepress / home.PHP
./onepress/woocommerce.PHP
./onepress / template-full width.PHP
./onepress / index.PHP
./onepress / search.PHP
./onepress / template-fullwidth-stretched.PHP
./onepress / single.PHP
./onepress / page.PHP
./ onepress/404.PHP
./ onepress / archive.PHP

You need to check the site now by clearing your browser cache.

No additional actions are required.

And that really fixed the problem

• This reply was modified 5 years, 2 months ago by ya4elovek.