I have this up and running in a test area and it looks great!
Quick question... is the current 1.02 release of multi-lang going to be upgradeable as cmsms core moves to 1.1 and onwards? I would love to use the multi-lang in production environments, but I'm a little unclear whether this release is going to be supported moving forward, or if it's more of a fork that might be abandoned when multi-lang becomes part of the core... if it becomes part of the core.
Thanks.
One more thing... for News to be in multiple languages, does this require there to be a news release in each language.
Lastly... if there's a help area I'm missing for multi-lang, please direct me to it. When I search the forums I keep ending up here, and the readme in the release looks like the readme from the core release. If I'm missing the documentation, please point me in the right direction.
Technically, I implement multilingual support with upgrades in mind. Once it becomes part of the core after the release of 1.1, you won't have to worry about it at all. Ideally, we'll need to make one more leap from 1.0.2 to 1.1 before this happens. And I will ensure that the sites are upgradable. I'll even do my best to have multilingual support incorporated into one of 1.1 betas.
Regarding the News module, I would recommend using categories as languages. Actually, I'm going to release build 3 with the news module installer adapted for MLE.
Regarding the help for MLE, it just doesn't exist. MLE has very minimal difference to the core. I used to include a readme file before I adapted the installer. Now that's it's all automatic, there's no need for it. If you thing that something needs to be documented, please let me know and I will set something up.
Thanks a lot. That all sounds wonderful. The system works really well and it is much appreciated.
I agree that the system works closely enough to the core that it doesn't really need its own instructions. I just didn't want to be posting questions about the News module, etc., if the information existed elsewhere.
I upgraded to the recently-released 1.02 build 3, and the footer doesn't work right for me. When I look at the global content for footer, it has the two flags, and both can be edited, but they seem to overwrite each other. For example, if i put "this is spanish" in the Spanish footer, and then I edit the English one to say "this is English," the Spanish one goes blank when viewed in a browser.
Couple things: this was not a clean install for me. I uploaded the new build over the old one and ran the upgrade. The upgrade threw a footer error, so I reran the install without creating the tables again, so this might be the problem. I just didn't want to blow away the information already in the tables, since I started adding content.
The real question... lol... Is this build working for everyone else in terms of the footer working correctly in two or more languages? If it is, I'll just blow away the database and reinstall, but if there is a bug, I wanted you to be aware of it.
See how the footer disappears on the Spanish one, and reads Spanish on the English one? This could totally be me screwing up the upgrade, so if this looks like it just needs a clean install, let me know.
am
Last edited by moorezilla on Tue Nov 21, 2006 7:13 pm, edited 1 time in total.
I have a problem with the last realease 1.02 build 3 - after a fresh installation when I try to load the main page it gives me Error 404. I can login in the admin area but I cannot add new pages and also there is a problem with the global contetnt footer in one of the php class files. I see that this was a problem in the previous release, it seems it is not completely solved.
Had the same thing just happen, after clean install main page won't load, no new pages can be added.
This turns out to be a permissions issue, preventing the installer from creating config_lang.php. I temporarily made the document root world writable to get around this.
The way the installer script is written, it will silently fail when unable to create config_lang.php, perhaps some error message would be in order?
$newfiledir = dirname(CONFIG_FILE_LOCATION);
$newfilename = "config_lang.php";
if (is_writable($newfilename) || is_writable($newfiledir)) {
$handle = fopen($newfiledir .DIRECTORY_SEPARATOR. $newfilename, "w");
if ($handle)
{
fwrite($handle, $config_lang);
fclose($handle);
}
}
=> if config_lang not writable, we just sliently skipped writing it causing all sorts of havoc later on
echo "[done]";