MKSnMKS

Hi megamenu,

Thank you for checking that.
It sounds like there is nothing in maxmegamenu that would cause its script to be placed in a blocking location, of its own accord.

I will swap templates and see how the tests go then.

Thanks

Hi Caleb,

Thanks for the info.
I will check speed.

1) Thank you for moving this topic to a place that you consider is more appropriate, at “Everything”.

Q) Please can you let me know what the link is that I should use to get there?

I have supplied a footnote at the bottom, for some background information.
Please accept my apologies for placing this in the incorrect location.
Also I am very grateful that you transferred the topic, rather than dumped purely because it was in the wrong forum – a previous method of handling, which is happy to see has been improved upon. appreciably – Thank you.

I have a few questions below, but this is the most important question here, as I have a few more ideas for improvement to contribute.

2) Also, I am sorry, but I am not sure what you mean by

“don’t routinely @ users”

Is “@” a verb, or a terminology?
The only use of “@” that I have been doing, is when I reply to a replier on a topic, and copy and paste their full name in to my greeting.
There’s no hyperlink anywhere in the name I have used to suggest there is an action that is followed. (the respondents names usually are presented with a hyper link on their name, and no hyperlink on the “@name”, and I have no hyperlinks)
I thought I was just being polite.

Q) By “@”, are you referring to my use of the “@” sign that the replier reports their name to be?

3) Spamming
I have had no intention of spamming.
And if using the “@” in greeting the respondent in a topic, is not permitted, then why was I not told about this much much earlier.
It has been my almost universal method of greeting the respondent.
So now, only now, do I find that I have been regarded as a spammer, when my intention was to be welcoming and polite.
So;
in order to try to not offend anybody,

Q) is it okay to greet respondents with their name – leaving out “(@name)” ?

4) Re Bumping.
As far as I can remember, I have not bumped (now that I know what the term means, and why it is important not to) for the last few weeks ; I may have made one or two mistakes, but I doubt it, because I now know that if I add a reply to my first comment, then that is bumping.

But you use the term “bumping” in a manner that suggests that I have been prolific in this action recently. This suggests that you may be referring to something else which also fits (your/WP’s) definition of bumping, which I have not been told about.

Q) If there is more to be known about the definition of “bump”-ing, then can you please let me know, so I will understand the additional meaning of the word, and be able to adjust to the additional constraints.

Thank you for your assistance

=====================
Footnote – re where to place topics related to the Website for the WordPress Forum.

I have made previous enquiries as to where the correct location to make suggestions for the WordPress forum website. And was supplied the link for this forum, which I used for posting this topic (which has now been moved).

As you will see, the correctness of the location has been established at length, to a point of certitude that it was considered that extensive enough enquiry had been made. At the time this may have been thought by some to have been tedious. One of the reasons why I checked, double checked, and triple checked, was because of having been on previous topics that they were made at the incorrect forum.

But, asking the same question repeatedly will not result in a different response, so please stop doing that.

You are in the right place, your feedback has been heard.

see
https://www.ads-software.com/support/topic/is-this-the-correct-forum-for-feedback-to-webmaster-team-of-wordpress-org/

• This reply was modified 6 years, 8 months ago by MKSnMKS. Reason: corrected a typo

Hi pavloborysenko (@pavloborysenko),

Thanks for helping.
Can you please tell me here, what the settings are, I should make at that location of the menu?

Thanks

Hi

The online test site was ;
https://gtmetrix.com/

It reports ;

[These] “JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.”

Thanks

On the description for the “free” plugin on the WP website, it states;

“8. Enable/Disable cache option for mobile devices”

I am using the free versions, and this feature ;

“Mobile Theme – Create cache for mobile theme”

, is shown but is not able to be used (in the free version).
(This is one of the reasons why I initially installed this plugin.)
Qa) Is this correct information for the free version?
or
Qb) Is it true information for the paid version?
or
Qc) There is an option for ;

“Mobile – Don’t show the cached version for desktop to mobile devices”

Does (8) refer to this option but leave out the reference to “desktop”, which creates a certain ambiguity?

Thank you

• This reply was modified 6 years, 8 months ago by MKSnMKS. Reason: fix formatting mistakes
• This reply was modified 6 years, 8 months ago by MKSnMKS. Reason: Clean up formatting again
• This reply was modified 6 years, 8 months ago by MKSnMKS. Reason: improved clarity

Hi edo888 (@edo888),

I tested it using GT Metrix’s online test.

I see (now) that the script is not locally run, so it is also at risk of slowing down the page load due to any delay at the external website.

Thanks

Hi Instant Search + (@instantsearchplus),

Thanks for fixing that.
And I also see that it is continuing to report compatibility with the later versions of WooCommerce. So it looks like you now have that requirement as part of usual procedure.

You’ve done good, and I thank you.

Thanks.

Does the paid version?

Hi Yoast Team,

You are probably aware that wordPress sites go faster on more recent versions of PHP, and site that go fast have shorter pageload times, and that gets better ratings with Google.

If it is compatible, then please say so.
If it is not compatible, then please say so.
But not saying so, portrays a dis-interest in an important performance factor.

Please keep up the otherwise good work.

Hi Caleb Burks (@icaleb),

Thanks for your help.
WooCommerce have done well by coming up with this method for helping standardise the system. I am not so sure it is “enforce”ing it, but it is definitely encouraging or inducing it.

This system could be used for all plugins that have plugins that depend on them, and possibly even for WordPress itself (if it doesn’t already).

Another extension of this system would be plugins to declare if they have problems or conflict with certain other plugins, so the user can be alerted to potential problems when combinations of plugins arise (ship/deactivate/swap?).

Main thing about this WooCommerce header tag problem is;
Please make sure all the plugin author teams ‘know’ about the issue with the header tags declaration of compatibility.
Not just been slipped an insignificant note somehow, but something that they will definitely read and act on.
What ever method is used to communicate this information could also be used in future vital improvements to the system, and be a model method for other plugins developers.

Hope this helps.
Please can you forward the essence of this to the WooCommerce dev team ?
Thanks

• This reply was modified 6 years, 8 months ago by MKSnMKS. Reason: layout
• This reply was modified 6 years, 8 months ago by MKSnMKS. Reason: made the main point clearer

Hi Caleb Burks (@icaleb),

Thanks for helping.

If you think the screen is cluttered by this addition then okay.
I am interested in usability and intuitiveness, so screen clutter is something I consider.

It looked to me like there is plenty of room in the form used to create a new category, but I am not using a smartphone or tablet to view it.

If the general concensus is such that additional features in this form are cluttering the screen then yes, please leave this out.

I prefer to keep my feedback to this centralised WordPress forum, otherwise I’d end up in all sorts of skattered forums.

But if you wish, please feel welcome to copy and paste this suggestion across to that.

Thanks

Hi Dominik Schilling (ocean90) (@ocean90),

Thank you for doing that.
I updated it earlier today.

I ran a PHP compatibility check in the last few days,
so will have missed the recent update.
I will be scanning again within a month (hopefully),
for PHP 7, and up.

If you can, it might be helpful to know why this problem existed for so long, so would you be able to maybe give a story or a (bullet point) list of contributing factors?
And maybe some thoughts or suggestions on how things might be able to be improved to help assist the development of plugins?

Thank you

The fix for this is provided below, by
kaggdesign (@kaggdesign) author of WOOF by Category,
which had alerted to the same problem,
and they found the fix.
So thanks Kagdesign

Hi,

It is very simple. Open main plugin file /wp-content/plugins/woof-by-category/woof-by-category.php and in the first lines you can see the plugin header

/**
* Plugin Name: WOOF by Category
* Plugin URI: https://www.ads-software.com/plugins/woof-by-category/
* Description: WooCommerce Product Filter (WOOF) extension to display set of filters depending on current product category page.
* Author: KAGG Design
* Version: 1.5
* Author URI: https://kagg.eu/en/
* Requires at least: 4.4
* Tested up to: 5.0
* WC requires at least: 3.0
* WC tested up to: 3.3
*
* Text Domain: woof-by-category
* Domain Path: /languages/
*
* @package WOOF by Category
* @author KAGG Design
*/

Lines

* WC requires at least: 3.0
* WC tested up to: 3.3

are responsible to reflect compatibility with WooCommerce.

Hi kaggdesign (@kaggdesign),

Thank you very much for the info.
I aim to let the remaining plugin authors know, within about three days, possibly earlier.