natsshop

Thank you for the quick help. So: I have set the filter via shortcode in the product categories: [woof sid=”flat_grey woof_auto_4_columns” autohide=1_price_filter=3] or [woof sid=”flat_grey woof_auto_3_columns” autohide=1_price_filter=3]. Then I set the shortcode for the price in a widget via the sidebar, for desktop: [woof sid=”flat_grey woof_auto_1_columns” autohide=1_price_filter=3] The filter over the widget is visible. I set the price filter for mobile directly in the shop page via shortcode, which is also visible. Then I assigned the filters for the categories via WOOF by Category. At the moment, I see that only the filters from size 992px are not visible. It’s been a long time, since I set the filters. At the moment I don’t know why the shortcode is in the categories and in Woof by Category. But before the update everything worked. Thank you for help.
Okay, now I know. I have to put the shortcode in the categories in order for the filter to be shown at all.
If I don’t put the shortcode in the categories, the filter is not shown despite Woof by Category.
But the filters are only shown mobile. The filters are gone from a size of 992px. The filters are there up to a size of 991px.

• This reply was modified 4 years ago by natsshop.
• This reply was modified 4 years ago by natsshop.

Hello,
thank you for your help. Yes, I saw that. Then I wrote to the developer of Woozone. He told me, that the plug-in had no main box container. This is always a big problem for us users, when the developer has no idea about his plug-ins. But thank you very much for looking into it anyway. But still, I have to say that it’s confusing, that the error is gone, when woocommerce is disabled. If it’s just up to Woozone, then the bug should still be there.

• This reply was modified 4 years, 2 months ago by natsshop.

Hello,
Thank you very much, I didn’t find where to write. All the best.

Hello,
Thank you for the fast answer. Unfortunately, that’s not the cache. Here, https://klon.nats-shop.com, on my staging page is the same problem. On my staging side I have no cache and no image optimization. I also thought at first, it was a problem of Woozone. So I wrote to the support. The support says, however, that Woozone does not have a main box container. Another plug-in must cause the error. So I turned off all plug-ins. When I deactivated Woocommerce, this notice was gone. Do you have another idea? Thank you.

On my site is all fine again. Thank you so much.

Thank you. I tried the update first on my staging site, so i have not problems yet on the live site. Iam waiting.

Hello,
thank you for wanting to take care of it. I don’t use a shortcode in the categories. I use the plug-in in the categories to assign the filters. In the widget, in the sidebar, I use [woof sid = “flat_grey woof_auto_1_columns” autohide = 1_price_filter = 3]
many thanks.

Hello,
I need help again with this. I was able to pinpoint the problem. I always get this error when I empty the cache. I have the assumption that by clearing the cache, the minimized files no longer have the correct connection to the database. Unfortunately, I can’t explain it better. Do I always have to reset the cache and the minimized files at the same time? I tried to reset only the minimized files, then there is also a timeout, or there is an error message that the database cannot be reached.
Best wishes Gisela

Hello,
Thank you very much, it works perfectly.
Greetings Gisela

Hi,
thank you for your answer.
Yes, deactivating fixes the error. My provider has now reduced the memory_limit to 640M. We suspected, that 1280M would be too much. I also have a staging site. At first, it went well when I disabled the cache on my staging page. But today the error came back when I activated minify. Then i cleared the cache of WPO before activating the minify function. It seems, that was the problem. I have also activated the preload function. Somehow it gives the impression, if the cache is full, the minify function does not find the associated files and then the problem is caused. I can be wrong. But if I clear the cache first, it seems to work. Can this have something to do with the preload function?
Best wishes Gisela

Thank you for the many and quick answers, you don’t feel alone with the problem. But I found the solution: The folder Assets with script-loader-packages.php was no longer there. I am still new on the current server and it is quite possible that I accidentally deleted it. There is no other explanation. I also accidentally deleted my theme recently because the checked files are not so well recognizable. Many thanks to everyone.

• This reply was modified 4 years, 10 months ago by natsshop.

Thank you for the many and quick answers, you don’t feel alone with the problem. But I found the solution: The Folder Assets with script-loader-packages.php was no longer there. I am still new on the current server and it is quite possible that I accidentally deleted it. There is no other explanation. I also accidentally deleted my theme recently because the checked files are not so well recognizable. Many thanks to everyone.

• This reply was modified 4 years, 10 months ago by natsshop.

Hi,
I have now set the debug mode in the wp-config and I get these warnings. I didn’t immediately come up with this idea because they said to me that these were not mistakes and that this was only important for developers.
I downloaded wordpress and the script-loader.php file both look the same. the one with me on the server and the one in the downloaded version. Can anyone do anything with the warnings here? What does “error when opening …” for recording mean … is there something wrong with the .php version of my host? The warning remains even if I switch to the wordpress backend.

Warning: include(/var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/assets/script-loader-packages.php): failed to open stream: No such file or directory in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 238

Warning: include(/var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/assets/script-loader-packages.php): failed to open stream: No such file or directory in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 238

Warning: include(): Failed opening ‘/var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/assets/script-loader-packages.php’ for inclusion (include_path=’.:/opt/plesk/php/7.2/share/pear’) in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 238

Warning: Invalid argument supplied for foreach() in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 240

Hi,
I have now set the debug mode in the wp-config and I get these warnings. I didn’t immediately come up with this idea because they said to me that these were not mistakes and that this was only important for developers.
I downloaded wordpress and the script-loader.php file both look the same. the one with me on the server and the one in the downloaded version. Can anyone do anything with the warnings here? What does “error when opening …” for recording mean … is there something wrong with the .php version of my host? The warning remains even if I switch to the wordpress backend.

Warning: include(/var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/assets/script-loader-packages.php): failed to open stream: No such file or directory in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 238

Warning: include(/var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/assets/script-loader-packages.php): failed to open stream: No such file or directory in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 238

Warning: include(): Failed opening ‘/var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/assets/script-loader-packages.php’ for inclusion (include_path=’.:/opt/plesk/php/7.2/share/pear’) in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 238

Warning: Invalid argument supplied for foreach() in /var/www/vhosts/nats-shop.com/klon.nats-shop.com/wp-includes/script-loader.php on line 240

• This reply was modified 4 years, 10 months ago by natsshop.

I have now followed your link source, but unfortunately that doesn’t tell me anything at all. I am a normal WordPress user and not a programmer.