7939 Posts in 1472 Topics by 944 members
|Go to End||Next >|
13 August 2009 at 11:20pm
I am using the ManyManyDataobjectManager- going well except one small bug. The TreeDropdownField doesn't work in the popup, if I switch to ManyManyComplexTableField then it works. I had a look and they have just added some new js requirements into those form fields /sapphire/forms/TreeDropdownField.php and /sapphire/forms/TreeSelectorField.php
They have added:
to both so I imagine it's now conflicting with something of yours.
14 August 2009 at 12:27am
TreeDropdownField AFAIK, has never worked in any popups. That's what SimpleTreeDropdownField is for.
14 August 2009 at 8:29am
Oh right - random that it did work in the other popup then. No worries, the simple one does the job Thanks
16 August 2009 at 2:20am
To limit the amount of scrolling in the DOM-Popups and make the layout a bit more clear, I'm using tabs on them (never thought it would be possible, but it was ).
However, these tabs make all HTMLEditorFields (SimpleHTMLEditorField, SimpleWysiwygField and SimpleTinyMCEField) break, so I have to fall back to the good old textareafield (which isn't userfriendly at all).
In case of SimpleHTMLEditorField (the one I like most), the field disappears completely.
In case of SimpleTinyMCEField (the one I like second) and SimpleWysiwygField, the field has the appearance of a plain ol' TextareaField.
19 August 2009 at 5:33am
WMK, can you confirm that Translatable patch for DOM will fix this bug?
If so, you are a hero to many users!
19 August 2009 at 7:01pm
Hi Uncle Cheese,
well, this patch fixes at least the "I can't handle sub-URLs of a CMSMain object." problem when having translatable enabled.
Haven't used Gallery stuff yet...
At my current project i have set cms translatable, but the dataobject is not. (well, it has a seperate locale column which is filtered when generating the DOM)
I ended with something like
$landingPageBlocksTable = new ManyManyDataObjectManager(
'PageBlock', // DO-Klasse
array('Thumbnail' => 'Bild', 'Title' => 'Titel','DateStart' => 'Start','DateEnd'=>'Ende', 'isDefault'=>'Standard'), // Felder fÃ¼r Ãœbersicht
null, // Felder fÃ¼r Popup
"Loc = '" . Translatable::get_current_locale() ."'"//Filter
but removing the "Loc = ..." Filter makes me see all dataobjects in every language and i can work with them without errors.
Maybe ATM translating an image gallery is better with adding seperate title / description fields to the image gallery dataobject than using translatable on the dataobject. Or you need a "copy all images to current language" function, cause you have to add every image to every language... just my 2c
20 August 2009 at 1:17am
Would you mind chiming in on the thread I posted? That user is having a very hard time getting things to work, and I just don't understand how Translatable works or what it's supposed to do at this point because I never have to use it as an ignorant English speaker.
I'm wondering if you might be able to look at the issues he's having and at least shed some light?
|Go to Top||Next >|