vmajor

Hi Kaushik,

no the version 1.02 still only hides categories in the main “shop” page, nowhere else.

I think I have the same problem. I will send you an email. The plugin hides categories only on the master “shop” link, but once you are inside a category all the other categories again appear.

Actually I cannot send you an email. Here are the links. Please look at the sidebar:

Correct: https://developer.venn-cycling.com/shop/
Fail: https://developer.venn-cycling.com/product-category/components/

Cheers,

V.

• This reply was modified 3 years, 10 months ago by vmajor.

Sure: https://www.venn-cycling.com

Apache.

There is now around 60 entries in the log with the same three warnings.

I looked up the originator IPs for the requests that caused these errors and they may in fact be attacks against your plugin which are failing because you changed the code.

PHP 7.2.24

Yes it persisted through several cache purges. This is in this morning’s log along with system time. It only repeated 3 times today:

[Mon Oct 12 08:03:11.940776 2020] [php7:warn] [pid 16305] [client xxx.xxx.xxx.xxx:44920] PHP Warning:  sprintf(): Too few arguments in /var/www/html/wp-content/plugins/w3-total-cache/ObjectCache_WpObjectCache_Regular.php on line 854
[Mon Oct 12 08:03:11.940997 2020] [php7:warn] [pid 16305] [client xxx.xxx.xxx.xxx:44920] PHP Warning:  sprintf(): Too few arguments in /var/www/html/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php on line 1572
[Mon Oct 12 08:03:11.941186 2020] [php7:warn] [pid 16305] [client xxx.xxx.xxx.xxx:44920] PHP Warning:  sprintf(): Too few arguments in /var/www/html/wp-content/plugins/w3-total-cache/DbCache_WpdbInjection_QueryCaching.php on line 731

Mon Oct 12 08:20:06 UTC 2020

• This reply was modified 4 years, 1 month ago by vmajor.

Thank you for the quick reply.

1. Server is a dedicated VPS
2. Both Object Cache and DB Cache are cached with Redis running on localhost

OK I did some more work on this. The problem is that TranslatePress translates the URL entirely, not just the final product name and that means that on dynamic pages from WooCommerce they no longer point anywhere.

Translatepress (in my setup) only works correctly in Japanese as the taxonomy is not translated. All other languages fail with a 404 or with often bizarrely incorrect page showing up

For example;

Original URL:https://www.venn-cycling.com/en/index.php/product/venn-var-37-tcd-filament-wound-tubeless-clincher-disc-brake-custom-wheels

DE translated ‘product’ into ‘produkt’ URL gives 404: https://www.venn-cycling.com/de/index.php/produkt/venn-var-37-tcd-filament-wickel-schlauchlos-clincher-scheibenbrems-scheibenbremsen-sonderrader

Manually edited link (replaced ‘produkt’ with ‘product’) showing DE translated content, intact taxonomy: https://www.venn-cycling.com/de/index.php/product/venn-var-37-tcd-filament-wickel-schlauchlos-clincher-scheibenbrems-scheibenbremsen-sonderrader

I call this a bug, and a significant one. It entirely breaks the intent and functionality of the plugin.

Furthermore I could not find any option to make it stop translating URLs. Unticking “Automatically translate slugs” makes no difference to the appearance or function of the URLs.

• This reply was modified 4 years, 1 month ago by vmajor.
• This reply was modified 4 years, 1 month ago by vmajor.

Thank you for looking Marko, yes I have been working on the site. I use Smushit but the issues is with me reusing images in different locations than originally intended. I will need to resize them to match the page requirements.

OK I will try that. My example above was with the auto option.

No I was not using additional minify solutions (that I am aware of) and I had disabled cloudflare minify and purged caches.

Thank you for the replies and @docbt thank you for mentioning the console. When I select to minify JS I get 400 bad request errors.

When I select to minify CSS no errors are reported but the site layout is broken.

Minify HTML & XML does nothing, I guess it is intended for static pages of which I have none.

Also it is not correct. I have the same error, and the product has a review. I have gone through all the threads on this issue and the responses are incorrect and support is mainly by deflection to something unrelated. Does Woocommerce support team have a solution to this?

I am now running a development server with php 7.1 on dev.venn-cycling.com and the Mailchimp plugin still does not work. When it is enabled and I choose to have a newsletter subscription popup I am unable to scroll the page, any page.

When I disable the popup I cannot see any obvious problems. All three available popup versions cause the scrolling error.

– There are no errors in the server log.
– I am not disabling other plugins. Unless you can fix your plugin I will just use a different plugin for signup
– It is the native plugin. Non native (ibericode) works just fine, as does everything else.

Hi Malachite,

I know how to find the report. I was asking how would you like me to share it. I am not going to copy and paste it in here.

Regarding the requirements, sure. Your plugin is still the only one that does not work out of…let me count… 33 plugins, including WP 4.8.3 that do work. Php logs on the server report no errors. The errors seem to be on the client side front end likely with javascript, or conflicts therewith. I should also add that your plugin crashes Edge, and makes Chrome unresponsive requiring a reboot.

• This reply was modified 7 years ago by vmajor.

Hey! a reply from MC…great. I would really love to get this plugin to work. One thing that you may use as a get out of jail ticket is that I use Ubuntu 14.04 so I am stuck with PHP 5.59.

– how can I provide you with the status report? The main complaint is about the PHP version.

-The errors I saw were in the Apache log – something about hooks being deprecated so nothing indicating that you were calling on functions that did not exist in 5.59.

-The issue resolves as soon as I deactivate your plugin. Yours is the only one that breaks the site.

– I am not switching to another theme, sorry. Other plugins work.

V.

I take this back. After further testing I realized that this plugin was causing the website to fail. It is as useful as a dose of malware. Do not install it or attempt to use it. It not only fails to perform its intended purpose, it also breaks your entire site.

The cause of the problem:

In the “Mail” section “From:” field contained only [name] tag

Solution:

It required the following tags: [name] <[your-email]>