لا يمكن تخصيص بعض نصوص الموقع

[pangbo]

I’m attempting to modify certain strings on the user preferences page. I navigated to Admin → Site Texts and searched for the relevant keys. However, I was unable to customize the specific text I was looking for as it told me there were no texts found.

I am reasonably certain that the key is valid, as it is defined here:

config/locales/client.zh_CN.yml

I then switched the target language to English but still yielded no results for user.username.short_instructions. Furthermore, I attempted to search for other strings such as user.username.title, user.preferences.title, and filters.latest.title, and no results either.

[awesomerobot (Kris)]

Very strange, I’m able to pull up the key

@pangbo

Furthermore, I attempted to search for other strings such as user.username.title, user.preferences.title, and filters.latest.title, and no results either.

If you right click and open the browser inspector, are there any errors in the console tab?

[pangbo]

It looks like there are no related errors, and based on the request results, it may be a backend issue.

Although I don’t believe the plugins I’ve installed have modified this particular area, I will attempt to remove all unofficial plugins later to see if that resolves the problem.

[awesomerobot (Kris)]

@pangbo

I will attempt to remove all unofficial plugins later to see if that resolves the problem.

You can temporarily disable customizations by using safe mode and see if that works

[pangbo]

I have some updates regarding this matter. I can now definitively confirm that the issue lies with the backend. While examining the code, I noticed a particular line:

app/controllers/admin/site_texts_controller.rb

To my surprise, executing I18n.exists?("js.user.username.short_instructions", :en) on my instance returns false.

I manually removed this line of code, and I am now able to search for user.username.short_instructions

I am uncertain as to why I18n.exists?("js.user.username.short_instructions", :en) is returning false. I may investigate further to determine whether the problem is specific to my instance or a more general issue with Discourse.