Last post by Spuds -
And some more progress. I found a couple of minor issues in the upgrade script. It ran fine but the result had a couple of minor db value issues that I wanted to cleanup. That work has been completed, of course there maybe other issues but I have run it on a 100K forum and the conversion worked fine.
While doing that I had to update our buddy repair_settings so it was 2.0 compatible. Actually found some large inefficiency's and fixed those so it runs a LOT faster in certain situations. While working on that I found some problems/inefficiency's in attachment maintenance so fixed those as well.
Lastly since I was stuck in attachment mode, I added support for AVIF and HEIC attachments (not smileys not avatars) .. AVIF is supported in recent GD and Imagick ... HEIC is ONLY supported in new Imagick (don't expect GD support)
AVIF is supported in most modern browsers, the forum support allows (if you allow the extension) resize/rotate per your admin panel settings, the format will remain AVIF. Its not treated much different than a JPG or PNG file.
HEIC is a another Apple I-turd. The software (if you have Imagick support) will allow uploading an HEIC image and then it will always convert it to a JPG. After that t will treat that image like it always was a JPG and shrink/rotate/etc per you admin panel settings. Only some versions of Safari will display a HEIC image, nothing else knows what the heck that is. You can allow the extension w/o server support but it will show as a dead bird on 95% of browsers.
I think I can do the initial 2.0B1 packages this weekend so they can be tested, and if they don't fail in spectacular fashion, I'll tag them as official.
Quote from: ahrasis – Downloaded it (the Malay package) but not sure how to test it since 2.0 is not yet released. Also the content is English, not translated at all.
Last post by ahrasis -
Downloaded it (the Malay package) but not sure how to test it since 2.0 is not yet released. Also the content is English, not translated at all.
Last post by Spuds -
And I've created the package build automation and updated translations site so they can be downloaded. Next to test to make sure the package build did its thing correctly.
Last post by Spuds -
This ended up being a bit of a chore. The upload is of-course easy, its standard push/pull commands. The chore was that we changed the way lanaguage files are named and where they are storred in 2.0
In 1.1 it was /themes/languages/admin.lang1.php ... admin.langx.php In 2.0 it is /sources/ElkArte/Languages/Admin/lang1.php ... langx.php
Renaming is not a big deal, but we had new strings, new area/files, changed strings, removed strings. So I wrote a little best guess program that compared each area, like Admin 2.0 to 1.1.
If the string key existed in both and the values were they the same use it,
If the string was missing drop it
If the string was only different by capitalization/punctuation, use as is,
If it they were close based on a levenshtein_ratio use as is, otherwise drop it as untranslated.
If the translated string is just English strings, drop them.
So what is now in Transifex under ElkArte-2.0 is cleaner than what we have had before and the % translated is more accurate.
Also for fun, I wrote a small program that pulls untranslated strings from Transifex, runs them through an OpenAI model and stuffs them back into Transifex. You specify the area, like Admin, the language like German/de and the program does the rest. Of course those models are not free to run so I did it as an experiment ... and it works!
Still have to write the program that pulls the language files from Transifex and creates the packages.
Last post by Spuds -
Made some good progress over the last few days.
I do have install working correctly, the only tweaks were getting the base settings to something more appropriate.
The upgrade was a different story, but I have it working to the point I can finally check on some refinements. The delay was really in updating the update.php script so it worked with 2.0, plus there was so much old cruft in that file. Anyway it now will upgrade a 1.1 db to a 2.0 version.
If upgrading there is still manual work that needs to be done, copying attachments and avatars over but the script is not going to do that for you, the overall directory structure is just too different. I'll jot down the easy path to upgrade but that will not be the only way, nor will the upgrade to anything other than update the db.
Last post by Spuds -
Got sidetracked updating SimplePortal so it was 2.0 compatible Thought I was all done but found a couple ofthat needed fixing. I'm sure there are more but that is always the case. I did add a new goodie feature to the portal
that needed fixing. I'm sure there are more but that is always the case. I did add a new goodie feature to the portal
