Drastic no ... but a lot of files were updated, some just a couple of lines, others more extensive. Since most custom themes tend to mainly hit MessageIndex.template.php, BoardIndex.template.php and Display.template.php and then fallback to the default templates for everything else, you would just have to post those changes back to your files.
14/27/25 are the number of lines affected for the above mentioned files.
This loads the strings and shows the variable name / current text. Change the text to what you want and hit save. This saves the change in the database and change is loaded/merged with the language file when its called for. This is faster and more portable.
I think this answers that for you. Looks like it saves what you change to the database, not the file.
Last post by Hj Ahmad Rasyid Hj Ismail -
Isn't the problem with default language files are that they will be overwritten when updating to newer version? If it is not update proof, there is no point of editing it. What I think may be best is, if such editor is being used, the string(s) that have been edited shall be put into a custom.language.php and also remember that it had done that in the future, when it is opened again.
Correct me if I'm wrong, but am I not the one that found most of the bugs that's been exterminated since B1 came out? LOL
I never used the admin editors. I usually just edit files and be sure. However, this sounds decent. I'll have to use this when re-add my own strings in B2.
EDIT: Just took a look, and I think I'd prefer actual file edits. Especially to add own strings. This, would be more geared to just changing, which will help in some parts for me. Thank you for that!
Last post by Hj Ahmad Rasyid Hj Ismail -
The idea of custom.css is an override to all default css, so I think the customized language should do the same, i.e. in one file something like custom.language.php? Addon already doing this, I think, so elkarte as a whole can have something like thing too?
Last post by Spuds -
Your wish has been somewhat granted. In 2.0 goto:
Configuration -> Languages -> Edit Languages
Select the Language you want to edit (listing is based on what languages you have installed)
Select the area such as Post, Errors, Admin, etc.
This loads the strings and shows the variable name / current text. Change the text to what you want and hit save. This saves the change in the database and change is loaded/merged with the language file when its called for. This is faster and more portable.
The custom css file idea is great, and I thought of another idea that would be just as useful. A custom language file, for people to add own strings to, or change default strings without editing set language files. On my site, I changed a few lines and added a bunch of my own. This would be so easy having in just one custom file that overrules the regular files if there's a like call.
Quote from: Spuds – With a B1 installed, B2 will pretty much be a overwrite the existing install, keeping of course your Settings.php file. Were your edits (other than the bug fixes posted) just in the themes directory and did you modify the existing or create a new theme?
Made theme. Modified some SP files and Gallery files. And menu/language file edits. Bug fixes in sources and other forum areas. I'm guessing no drastic theme file changes?
no ... but a lot of files were updated, some just a couple of lines, others more extensive. Since most custom themes tend to mainly hit MessageIndex.template.php, BoardIndex.template.php and Display.template.php and then fallback to the default templates for everything else, you would just have to post those changes back to your files.
