Translation Tool for MODx Revolution

This tool probably needs an update; sounds like the Language needs to be added to the transport before the topics/entries. We’ll look into it in conjunction with RC-1 release.

Quote from: OpenGeek at Feb 14, 2010, 12:48 PM

This tool probably needs an update; sounds like the Language needs to be added to the transport before the topics/entries.

The files in the package simply return arrays - how can any information possibly be added earlier?

I debugged the whole package installation progress when adding my language pack, and found out that in xPDOObject::fromArray() the language name ($val) is not assigned to the "name" key ($key) because $setPrimaryKeys is set to false. xPDOObject::fromArray() is called by xPDOObject::fromJSON(), which is called by xPDOObjectVehicle::get(). Above the line

the third parameter is defined by


So I changed the line that defines this value in /core/components/languagebuilder/processors/build.php

(line 88) to

and now it works for me. But as I’m quite new to MODx, I’m not totally sure if this can cause any other problems. Could you take a look at my solution and tell me if there are any side effects?

Thanks in advance!

Cheers,
Jan

The updated Language Builder tool was posted yesterday: http://modxcms.com/extras/package/546

Quote from: OpenGeek at Feb 16, 2010, 11:06 AM

The updated Language Builder tool was posted yesterday: http://modxcms.com/extras/package/546

I did use the updated version (languagebuilder-1.0-rc1), but it didn’t work for me. The language name was still set to the empty string.

Cheers,
Jan

Thanks for updating this tool again (RC2) - you guys are really hard-working and quick, which I appreciate very much (I just came here from some other CMS that seems to die an insidious death) -, but now the packaging process won’t finish. I get the "please wait" message, and that’s it.

I guess the fact that you preferred a different solution means that mine does in fact have some side effects?

Cheers,
Jan

Quote from: enigmatic_user at Feb 16, 2010, 08:15 PM

but now the packaging process won’t finish. I get the "please wait" message, and that’s it.

Hm. Are you using Revolution SVN, or beta5?

Quote from: splittingred at Feb 16, 2010, 08:29 PM

Hm. Are you using Revolution SVN, or beta5?

I’m using RC1 rev6368 from SVN. Sorry, but it’s impossible to keep up with the frequency you’re checking in new revisions (although I try to update my local working copy quite frequently).

I could try to update MODx to the most recent version (rev6373) if you’re expecting it to behave differently.

Cheers,
Jan

Quote from: enigmatic_user at Feb 16, 2010, 08:40 PM

I’m using RC1 rev6368 from SVN. Sorry, but it’s impossible to keep up with the frequency you’re checking in new revisions (although I try to update my local working copy quite frequently).
I could try to update MODx to the most recent version (rev6373) if you’re expecting it to behave differently.

Ha! Yes, r6372 actually has the fixes you need. Jason and I worked today specifically on the packaging issues that were causing your error. Upgrading to the latest SVN should (hopefully) fix that.

(This is the downside to using SVN; often we’re shooting at a moving target. Releases are much easier to manage.)

Okay, I now updated my two MODx installations (one for the export, one for the import) and the Language Builder, and now import and export are working as expected. Thank you very much for fixing this! And sorry for not testing the newest build before - I already updated quite frequently, but as I said, it’s impossible to install every new build (there’s some other work to be done ).

Now there’s a little problem with the login (blank page after login, everything works after a reload), but that’s another story, and I’m sure you guys will fix this soon.

Cheers,
Jan

Quote from: enigmatic_user at Feb 16, 2010, 09:20 PM

Now there’s a little problem with the login (blank page after login, everything works after a reload), but that’s another story, and I’m sure you guys will fix this soon.

Yep, already fixed.