-
-
Notifications
You must be signed in to change notification settings - Fork 810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the Purge Re: Prefixes option in the dashboard obsolete? #9797
Comments
I just installed a test version with 6.3.8 and then updated to 6.4.0-RC3. You probably forgot to put a colon after Re (Re:) A question on the side: is it possible to download the installation files pkg_kunena_v6.4.0-RC3-DEV_2025-01-21.zip and pkg_kunena_languages_v6.4.0-RC3-DEV_2025-01-21.zip again somewhere for test purposes? I couldn't find anything in the areas I had access to. |
With the function “Aw: remove prefix” in the configuration (frontend tab), no “Aw:” can be removed before the titles. It could only prevent “Aw:” from being set before the title. Existing “Aw:” are not removed before the titles. The “Aw: Remove Prefix” in the Dashboard -> Tools makes more sense if you have very old posts and it works. My suggestion is to remove the entry in the configuration but leave the function in the tools. |
The ‘Disable Re: in subject’ option in the configuration is useful as it removes the Re on the index page, which is still prefixed.
These versions no longer exist. We update our test versions after each merge to test if a bug fix has produced the desired result. These are only temporary versions, which are constantly being adapted. |
Describe the bug
We have the Purge Prefixes option in the Dashboard -> Tools (see image below). But you cannot remove prefixes with this option.
Message: No message subjects starting with 'Re' were found.
I think that was an option for K3, where every title in an answer started with Re. Now we have ‘Replied by’ and username.
We only have Re-prefixes on the index page and you can disable these prefixes in the configuration (Frontend tab).
.
The text was updated successfully, but these errors were encountered: