Can't change a string, internal server error

AI-generated summary

Pad_Pors reports an issue where changing the js.flagging.custom_message.more string in the admin panel results in an “internal server error,” and reverting to default shows [Object object] instead of the expected text. The issue appears related to pluralization — specifically, the placeholder {{n}} is not rendering correctly, and replacing it (e.g., with {{count}}) triggers the error. gerhard suggests this may stem from prior customization before the string was pluralized, and confirms that refreshing the page after resetting to default resolves the [Object object] display issue. Pad_Pors confirms the fix works after refresh. The problem may involve translation handling (e.g., Transifex) or core string formatting, especially for Arabic, where the placeholder should display the number of remaining characters — currently showing “missing {{n}} value” instead. No permanent fix is offered yet, but the workaround (reset + refresh) restores normal behavior. The underlying cause — whether in translation, pluralization logic, or admin UI handling — remains unresolved.

I guess this is a minor Contribute > Bug :

I get the error “internal server error” when I want to change the js.flagging.custom_message.more string from the admin panel. the reason I want to change it is shown in the image:

image

number of remaining character should be written there, instead of “missing {{n}} value”!

  • when I return the string to default, it is written: [Object object] in the field.
  • when I change the {{n}} to {{count}} or anything else I get “internal server error”.

is it something related to the translation written in transifex or is it something else?

I assume this is for Arabic? I’m seeing the following text entries in the admin panel:


That looks fine. Are you on latest?

I think you customized js.flagging.custom_message.more before it was converted into a pluralized string. Reverting the string to its default should work make it disappear even though you see the [Object object]. That “error” should be gone after you refresh the page. Can you give it a try?

yes, it’s gone and things are normal with refresh after pressing “default”.