artyus

I understand all this, and the site has been fully tested for viruses on numerous occasions, but Wordfence finds nothing. Backups are also made regularly.

Perhaps the problem is precisely in the “Custom Post Type UI”: their plugin, despite over 800 thousand active installations, is currently marked as not having confirmation of compatibility with the current version of WordPress. Maybe that’s the reason.

Thanks for the quick response.

Yes, I have not formulated the problem correctly. I used at the same time both your plugin for tag organizer and the “Custom Post Type UI” to create custom tags. Therefore, it is difficult to immediately understand which plugin caused the problem on some of the tag archive pages.

All plugins on the site were installed in the official way from the www.ads-software.com site, also a powerful protection system (Wordfence) was initially installed and configured on the site, so the possibility of external infection is excluded (if Wordfence does not work, then not only my sites are at risk, but also several million other sites using it).

Ok, I’ll try to contact with developers of “Custom Post Type UI”. Then, for now, we will assume that this is their problem.

Have a nice day!

Hello!

This is fact that your plugin is emptying the backend of the site.
A few days ago, I also unexpectedly ran into this.
By the method of exclusion it was found out that the fault is in your plugin.. Moreover, I checked the possible presence of conflicts with other plugins, specifically disabling absolutely all other plugins. Even when other plugins are completely disabled, the contents of the admin page no longer appear immediately after the activation of your plugin.

Agree, this should not be so. If you cannot explain and eliminate the cause of what is happening, then site administrators are not wise to use a plug-in, which may unexpectedly lead to similar problems.
It was easier for me to uninstal the plugin completely, since the site where there were problems with it is at the development stage. I’ll see how it behaves on several of my other sites.

–RU–

Привет!

То, что ваш плагин опустошает бэкенд сайта, факт.
Несколько дней назад тоже неожиданно столкнулся с этим.
Методом исключения было установлено, что вина в вашем плагине. Более того, я проверил возможное наличие конфликтов с другими плагинами, специально отключив абсолютно все остальные плагины. Даже при полностью отключённых других плагинах, содержание страницы администратора перестаёт отображаться сразу же после активации вашего плагина.

Согласитесь, такого уж не должно быть. Если вы не можете пояснить и устранить причину происходящего, то администраторам сайтов не разумно использовать плагин, который неожиданно может привести к подобным проблемам.
Мне проще было снести плагин полностью, благо сайт, где с ним возникли проблемы, находится на этапе разработки. Посмотрю, как он будет вести себя на нескольких других моих сайтах.

С уважением,
Фарид Тазиев.

Thanks for the clarification and for your plugin!

Respectfully,
Farid Taziev.

Hello!

Yes, these two quotation marks corrected everything. Thanks for the promptness, I’m waiting for a full update.

Have a nice day!

Respectfully,
Farid Taziev.

If this can help you, then WooCommerce shows a php-error, which, as I understand it, is also associated with your plugin (Query Monitor detected):

wp-content/plugins/woocommerce/templates/notices/error.php:22
    wc_get_template()
    wp-content/plugins/woocommerce/includes/wc-core-functions.php:270
    wc_get_template_html()
    wp-content/plugins/ultimate-woocommerce-auction/includes/class-uwa-scripts.php:125
    UWA_Scripts->uwa_register_front_scripts()
    wp-includes/class-wp-hook.php:287
    do_action('wp_enqueue_scripts')
    wp-includes/script-loader.php:2294
    wp_enqueue_scripts()
    wp-includes/class-wp-hook.php:287
    do_action('wp_head')
    wp-includes/general-template.php:2884
    wp_head()
    wp-content/themes/weaver-xtreme/header.php:58
    load_template('wp-content/themes/weaver-xtreme/header.php')
    wp-includes/template.php:672
    locate_template()
    wp-includes/general-template.php:41
    get_header('page')
    wp-content/themes/weaver-xtreme/includes/lib-layout.php:431
    weaverx_page_lead()
    wp-content/themes/weaver-xtreme/page.php:11

Hi, did you manage to reproduce the described error?

Resolved

• This reply was modified 4 years, 5 months ago by artyus.

Yes, now everything seems to be fine.

Thank you for quick response and efficiency.

Hi!

Please check: disable this checkbox in the basic settings of the plugin.

If after that everything works fine, then you and I have the same problem.

Hey.

I can confirm that after the last update everything is fine. Thank.

Yours faithfully,
Farid Taziev.

Unfortunately, a lot of work is currently underway and there is no way to allocate time for testing directly on the site. But this is not necessary. As developers of the plugin, I am sure you are constantly testing it on various assemblies.

The problem is present, even if only three plugins are installed on WordPress in their latest versions:

1. WooCommerce (Version 4.2.2 | Author: Automattic)
2. WooRewards (Version 3.15.0 | Author: Long Watch Studio)
3. Ultimate WooCommerce Auction Plugin (Version 2.0.10 | Author: Nitesh Singh)

See screenshot 1: WooRewards is displayed in the menu.
See screenshot 2: After installing your plugin, WooRewards disappears from the menu, its place takes your plugin. But WooRewards is active.

Yours faithfully,
Farid Taziev.

I took another screenshot.

This error occurs on the site when you activate your plugin. I think this is the very reason.

This list does not display the sequence of errors. This is a list of PHP errors and warnings in alphabetical order by source (in the list there are others, I showed only the part of the list that is associated with your plugin).

To make it easier for you, I have disabled sources that cause all other errors and warnings (look at the new screenshot). As you can see, now on the site all PHP-errors are generated exclusively by your plugin.

Alas, mistakes remain. Checked several times, including clearing the cache.