Gabriel Torres

Fantastic! 🙂 

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Yes, it is:
+------------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+--------------------+---------+ | Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment | +------------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+--------------------+---------+ | core_profanity_filters | InnoDB | 10 | Dynamic | 2095 | 62 | 131072 | 0 | 49152 | 0 | 9604 | 2022-08-19 13:21:53 | NULL | NULL | utf8mb4_unicode_ci | NULL | row_format=DYNAMIC | | +------------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+--------------------+---------+  

Yeah, looks like that plugin is quite old. The $anonymous parameter was added back in 4.6 if I remember right.

@Gabriel Torres that sounds like a similar issue I am getting. Upgraded from 7.4.3 to v 8 and getting 500 errors. but this is for the whole site including the admin panel. No idea if its possible to disable the customisations without the admin panel is there?

Sounds great. Please loop back your findings as someone else may run into this as well 🙂 .

No problem. 🙂 

Hi guys,
As usual, we face limitations when translating certain strings since in English there is no male/male words like in Portuguese, Spanish etc.
In addition, some words in English don't change regardless of singular/plural.
Right now, the following strings that are giving us trouble.
notification__unapproved_content_bulk_title
notification__unapproved_content_title
These two strings default to: ⚠️ New %s awaiting approval
There are two problems here:
1. We don't know deforehand whether "%s" will be a male or a female word. "New", in English, doesn't have gender, but in Portuguese/Spanish/etc the adjective changes depending on the noun: Nova (female) / Novo (male). And we have a mix here! Some examples:
Male: post, tópico (topic)
Female: avaliação (review), respostas (reply)
2. We don't know beforehand wether "%s" will be a singular or plural word. In English, "New" doesn't change with singular/plural, but in Portuguese/Spanish/etc it does. So, if we translate "New" as "Novo", when %s is plural, the grammar is incorrect (ex: "Novo posts" instead of "Novos posts").
I tried to use the {!#[1:novo][?:novos]} trick, but it didn't work here. But this would fail the male/female problem anyway.
I got a little creative here and solved this by translating this string as:
⚠️ Há %s aguardando aprovação
Instead of using the adjective "New", I changed it to the verb "Há" (There is/There are). So we have "There is/there are %s awaiting approval". The meaning is slightly different from the original string, but it does the trick.
Even though I have found a solution, I thought it would be interesting to tell you this, so you understand the challenges we face when running non-English communities.
However, the major issue now is with the following string:
notification__unapproved_content_grouped
Which defaults to:
There are {count} new %s requiring approval %s
Here, since we have the {count}, we can correctly apply the singular/plural trick, so I translated it to:
Há {count} {!#[1:novo][?:novos]} %s aguardando aprovação %s
The problem now is, we don't know whether the first "%s" will be a male or a female word. So we have a gender mismatch whenever it is a female noun.
Now, another issue we have is when it is a review in Pages that is pending approval. It is pulling the string "avaliação" (review), in the singular form, even when more than one is present. See the screenshot below. This may be a bug, maybe the system is pulling __defart_content_record_reviews_title instead of __defart_content_record_reviews_title_plural, and I kindly ask you to take a look into this. In other words, which string is being used in the first %s when the this notification is about reviews in Pages.
I hope I was clear enough for you to undertand what I mean, and let me know if you need any additional information.
Best regards,
Gabriel Torres

I have marked this for a devs attention so we can comment on this in more detail. Someone will respond once we have gone through this 🙂 

Not seeing this problem myself.  Have tested with groups as well as with single member notifications.  
The only bug related to alerts that I'm aware of are alerts that have an end date specified may not show at all.  

I'm also not able to recreate this on my end unfortunately. It does seem its something local to your own environment. Do you have an example on your site I can take a look at?

Hi guys,
As usual, we face limitations when translating certain strings since in English there is no male/male words like in Portuguese, Spanish etc.
In addition, some words in English don't change regardless of singular/plural.
Right now, the following strings that are giving us trouble.
notification__unapproved_content_bulk_title
notification__unapproved_content_title
These two strings default to: ⚠️ New %s awaiting approval
There are two problems here:
1. We don't know deforehand whether "%s" will be a male or a female word. "New", in English, doesn't have gender, but in Portuguese/Spanish/etc the adjective changes depending on the noun: Nova (female) / Novo (male). And we have a mix here! Some examples:
Male: post, tópico (topic)
Female: avaliação (review), respostas (reply)
2. We don't know beforehand wether "%s" will be a singular or plural word. In English, "New" doesn't change with singular/plural, but in Portuguese/Spanish/etc it does. So, if we translate "New" as "Novo", when %s is plural, the grammar is incorrect (ex: "Novo posts" instead of "Novos posts").
I tried to use the {!#[1:novo][?:novos]} trick, but it didn't work here. But this would fail the male/female problem anyway.
I got a little creative here and solved this by translating this string as:
⚠️ Há %s aguardando aprovação
Instead of using the adjective "New", I changed it to the verb "Há" (There is/There are). So we have "There is/there are %s awaiting approval". The meaning is slightly different from the original string, but it does the trick.
Even though I have found a solution, I thought it would be interesting to tell you this, so you understand the challenges we face when running non-English communities.
However, the major issue now is with the following string:
notification__unapproved_content_grouped
Which defaults to:
There are {count} new %s requiring approval %s
Here, since we have the {count}, we can correctly apply the singular/plural trick, so I translated it to:
Há {count} {!#[1:novo][?:novos]} %s aguardando aprovação %s
The problem now is, we don't know whether the first "%s" will be a male or a female word. So we have a gender mismatch whenever it is a female noun.
Now, another issue we have is when it is a review in Pages that is pending approval. It is pulling the string "avaliação" (review), in the singular form, even when more than one is present. See the screenshot below. This may be a bug, maybe the system is pulling __defart_content_record_reviews_title instead of __defart_content_record_reviews_title_plural, and I kindly ask you to take a look into this. In other words, which string is being used in the first %s when the this notification is about reviews in Pages.
I hope I was clear enough for you to undertand what I mean, and let me know if you need any additional information.
Best regards,
Gabriel Torres

@andavis Just use the plugin I posted in the link above by @Square Wheels

@andavis Just use the plugin I posted in the link above by @Square Wheels

Please be advised I have marked this to a developer to comment on what is happening here.

Hi,
We have the word "configuracoes" configured in our word filter to replace it with its correct form: "configurações".
Now we are trying to add the word "configuraçoes", however, the system doesn't allow it, saying "there is an existing filter for this word".
So, the system doesn't differentiate "c" from "ç", which are different letters.
Please advise.
Gabe.

No problem. I have created a ticket for you on this so that we can take a look

@Andy928 @Matt We've just upgraded to 4.7.0 and I can confirm that this bug is now gone. Many thanks! 🙂
 

@Andy928 @Matt We've just upgraded to 4.7.0 and I can confirm that this bug is now gone. Many thanks! 🙂
 

@Andy928 @Matt We've just upgraded to 4.7.0 and I can confirm that this bug is now gone. Many thanks! 🙂
 

It's a known bug fixed for the upcoming 4.7 version: https://invisioncommunity.com/release-notes/
 

Nice find and troubleshooting! 👍

Excellent sleuthing @Andy928!
A fix is now in review and may just make it for the June release.

This is the same issue being discussed here: