melebius

@tychesoftwares Sorry for the delay, I am not actively working on the project currently.

Do you mean that you’re not getting custom order numbers without adding prefix?

Yes, exactly.

This is my setup:

WooCommerce Custom Order Numbers: Enable
Order numbers counter: Sequential
Sequential: Reset counter: Disabled
Order number custom prefix: 1 or empty (this makes the difference)
Enable order tracking by custom number: Enable
Hide … for roles (2 fields): empty

I am using the free version, the fields I have not mentioned are disabled.

While testing WordPress 5.9 with my WooCommerce site, I have experienced the numbers aren’t changed in my case, too. However, if I set an “Order number custom prefix” in the plugin settings, it starts to behave as expected. Could it be your case, @bartkal?

With version 1.3.6, I can turn off “Include Variations in Search Suggestions” and it does what I was looking for. Thank you for adding this!

I looked into the code of the plugin and found that the position is simply the order in which WordPress returns the attribute term which simply matches the ID, at least in my case.

However, I also found I can alter the position value (used for sorting) using the filter hpy_fdv_build_attribute_filter. I got the list of the attribute terms for my variation attribute (the attribute with checked “Used for variations”) and set the position accordingly:

add_filter( 'hpy_fdv_build_attribute_filter', set_position_by_variation_attributes' );
/**
 * Replaces the position attribute with the position in the attribute terms list.
 * 
 * Assuming just **one** variation attribute.
 * If multiple attributes needed to be taken into account,
 * you would have to define a custom criterion function
 * instead of just assigning $term_idx to position.
 */
function set_position_by_variation_attributes( array $attributes ) {
  $var_attribs = wc_get_product_variation_attributes( $attributes[ 'id' ] );
  foreach ($var_attribs as $attr_name_full => $current_term) {
    $attr_name = substr( $attr_name_full, strlen( 'attribute_' ) ); // strip 'attribute_' prefix

    // Search for the current variation’s term ($current_term) among available terms.
    // Terms returned by get_terms() are sorted according to the Product Attributes back-end page.
    foreach ( get_terms( $attr_name ) as $term_idx => $term ) {
      if ( $term->slug == $current_term ) {
        $attributes[ 'position' ] = $term_idx;
        break;
      }
    }
  }
  return $attributes;
}

Thank you for making this plugin and making the mentioned filter (among others) available! Feel free to incorporate my code into the plugin if you find it useful.

Hi @imagely,

Thanks for your reply, I appreciate it much. AFAIK the translations should not be updated manually in the plugin, see https://translate.www.ads-software.com/projects/wp-plugins/nextgen-gallery/language-packs/: “Language packs are installed automatically if they are available. Once a locale has reached the threshold for a package build it will be listed here. It also means that you don’t have to include this language in your plugin anymore.”

I tried to copy the file /wp-content/languages/plugins/nextgen-gallery-cs_CZ.mo to /wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/i18n/lang/nggallery-cs_CZ.mo in my WordPress installation and I got the translations of NextGEN updated (i.e. got the behavior I expected when I started this thread). Could the plugin load the translations provided by WordPress automatically? Or at least copy them to its folder when they are updated?

Hi @imagely,

Thanks for your reply. I am using WordPress in Czech already and see most WordPress strings translated. (It seemed so obvious to me that I didn’t even mention it…) When I find an untranslated string in WordPress core, themes, or most plugins, I can use Poedit or go to translate.www.ads-software.com, find the string and add the translation. However, in the case of NextGEN, I see untranslated strings even if they appear translated on translate.www.ads-software.com.

I made two screenshots for you: imgur.com/a/U3BmQsB

The former one shows that I have set Czech (“?e?tina”) as my WordPress language and that WordPress strings are displayed in Czech. The latter one shows one of NextGEN screens. I marked blue the correctly translated Czech strings and red the incorrectly untranslated English strings. And I made sure they are translated on translate.www.ads-software.com.

I sent my Complianz Settings export to the support email and got a useful hint: I had turned on “Do you want to ask for consent for Statistics?” by a mistake. The problem is solved now.

Hi @jarnovos,

I installed the updated version on my website today and went through the wizard again but nothing changed from my perspective – Complianz still shows a Cookie Banner and blocks statistical cookies by default.

Hi @jarnovos,

You are right, I haven’t mentioned that Complianz detected I do not need a Cookie Banner, so it was disabled automatically. That was true with Complianz 5.4.

However, today I upgraded Complianz to 5.5.1. With the same settings, the Cookie Banner started to display. After I accepted statistical cookies, GA started to recognize my visit.

So my initial problem seems to be solved but I’ve got a follow-up question: Is it no more possible with Complianz 5.5 to use Google Analytics (with IP anonymization) without a cookie banner?

“In some countries, like Germany, Austria, Belgium or Spain, consent is required for statistics, even if the data is anonymized.”
I am located in the EU but have selected that I am not targetting mentioned countries in the Complianz wizard.

Hi @aahulsebos,

Thanks for your prompt reply. I do have Complianz enabled all the time on the production site. I have got the script you mentioned at the end of my webpage source code but as I’ve written before, its first line is missing…

Thank you for the hint. I can translate your plugin’s strings in Loco and also by using wp i18n make-pot and Poedit. However, I find this just a workaround as using this way, every single user would have to translate your plugin themselves. Please make it possible to be translated using the accustomed WordPress way.

Update: The configuration of “Reset Label” works, probably my cache plugin affected this.

There is also a text string “Clear” which is shown in front-end and not translatable. The settings field “Reset Label” does not seem to affect this.

Hi @themifyme,

Thanks for your reply! I agree that most strings don’t need to be translated as they can be configured in settings. However, I haven’t found any way to translate the text of the “Load More” button in front-end when used as a pagination option.

(Moreover, if you allowed to translate the back-end texts, you could help to address the WooCommerce administrators who don’t speak English well enough.)

Dear @royho, thank you for the hint!

This SQL query helped me:

UPDATE wp_wc_product_meta_lookup SET
total_sales = '0'
WHERE total_sales > '0';