Re: YAMS: Yet Another Multilingual Solution

Hmm. I’ve got a feeling that isn’t the problem and that it might be some minor change made to the final version of Evolution. I have only seen the tabified fields working on a release candidate of Evo before I think... Please can you:
1) Edit a document associated with a multilingual template.
2) Click on the background near the document form, select this frame > view source, then do a search for tvpagetitle in the source and tell me if the id is followed by a %5F or an underscore?

Thanks.

I think I found the problem, template variables now get a value like "tv1", where 1 is the id of the tv in the database. So the problem is that the ManagerManager snippet tries to move id’s that don’t exist because they have got another name.

Thanks for posting that Ronald, was just about to make the comment. This is a change which solves a whole host of other issues and is actually quick to update. The TV IDs are in parenthesis next to the Template Variable name.

Quote from: rthrash at Aug 11, 2009, 08:52 AM

Thanks for posting that Ronald, was just about to make the comment. This is a change which solves a whole host of other issues and is actually quick to update. The TV IDs are in parenthesis next to the Template Variable name.

There should be a function that can get the id from the database when you give the name of a TV to it. So that the automatic creation of the mm_rules for YAMS can still do his work

There should be a function that can get the id from the database when you give the name of a TV to it.

Yes. Does such a method exist as part of the MODx API now or should I write my own function? Also, what is the correct way for testing for versions of MODx Evolution 1.0 and above so that I can update the rules to make them backwards compatible?

Thanks.

Hello,

I wonder if anyone has found an answer on mgbowman problem with the language tabs in the manager.
I get a similar problem with similar config (except YAMS 1.0.4a-rc4).
Here it seems that the tabs are not connected with the content and I have all the french & english TV on all tabs.

If someone went through this some kind of walkthrough would be greatly appreciated.

Quote from: PMS at Aug 06, 2009, 05:57 AM

Quote from: mgbowman at Aug 06, 2009, 05:44 AM

Quote from: PMS at Aug 06, 2009, 05:04 AM

You’re right, you shouldn’t see both sets of fields on both tabs. I have never seen that before. Are you using the latest version of ManagerManager and do you have any custom rules specified in addition to the YAMS ones?

I’m running MODx v1.0.0 + ManagerManager v0.3.2 + YAMS 1.0.4a-rc3 and set it up exactly as described in the docs with no additional MM rules (other than the default ones shipped with MM).

assets/plugins/managermanager/mm_rules.inc.php

Please try putting the YAMS rules at the end, or commenting out the default manager manager rules. (There’s no point manipulating document variable fields that you are subsequently going to hide anyway.)

Thanks for your great job & commitment PMS

st1pixel

It’s a bug in YAMS that affects people running MODx Evolution 1.0.0. I’ll see if I can release a patch for it tonight.

Quote from: PMS at Aug 11, 2009, 11:34 AM

st1pixel
It’s a bug in YAMS that affects people running MODx Evolution 1.0.0. I’ll see if I can release a patch for it tonight.

Thanks, it’s a very nice piece of software you are building, a must have for the whole Modx community.
I’ll definetly post the YAMS websites I currently work on.

Okay. I think I have fixed it. At the same time, I have made it so that any template variables ending in _{langId} where {langId} is a language group id are tabbed - not just the standard tvs managed by YAMS as was previously the case.

I have checked that this works for a Pre-Evolution install, but I am looking for a volunteer to test it on Evolution. Just rename the file to remove the .txt extension, and replace your current assets/modules/yams/yams.mm_rules.inc.php file with it. Then reload a multilingual document to see if it works.

Thanks.

Quote from: PMS at Aug 11, 2009, 02:03 PM

Okay. I think I have fixed it. At the same time, I have made it so that any template variables ending in _{langId} where {langId} is a language group id are tabbed - not just the standard tvs managed by YAMS as was previously the case.

I have checked that this works for a Pre-Evolution install, but I am looking for a volunteer to test it on Evolution. Just rename the file to remove the .txt extension, and replace your current assets/modules/yams/yams.mm_rules.inc.php file with it. Then reload a multilingual document to see if it works.

Thanks.

So I’ve checked with modx 1.0 Evolution and it’s working!

Great!