I am having trouble with a custom module where I would like to add a custom dropdown. What I would like is to have a couple of items preset for the dropdown but have it show up in the dropdown editor so the admin can change or add more items to the dropdown. I have played around with it for quite a while and can't get it to work.
Thanks
Sounds like Dependent Dropdowns in Sugar 6.5 are what you are looking for...
http://developers.sugarcrm.com/wordpress/2012/05/03/new-for-sugar-6-5-create-dependent-dropdowns-using-sugar-logic-in-studio/
SugarCRM doesn't seem to allow you to use the data of a module in (multi-)select of another module. Despite having a relationship set between the modules as such.
Related
Is there a way to add a custom column menu tab with my own favourite icon which on click would render my custom react component?
something like
myColDef.menuTabs: ['generalMenuTab', 'filterMenuTab', 'myCustomMenuTab']
FYI I'm using v12.0.2
What you're after can't be done I'm afraid. The grid supports React components in all sorts of ways (renderers, editors, filters etc), but not via the column menu.
I've updated the docs page to remove the gibberish issue - it'll be fixed properly in the next release, thanks for highlighting this.
This would be helpful to have. In particular for us, we'd like to filter based off row properties, and not row values. Creating our own tab to filter by cell colors that we have assigned with our own set of labels would be useful.
I agree that it would be a nice feature to have. Apparently, there's no quick out-of-the-box solution to do it. The only workaround I see is to implement your own custom Header component which would display any buttons your want.
There you can put a button to open your own custom menu, which you can implement as any regular UI component. It also means you'll need to manually implement all standard menu options that Ag-Grid provides out of the box if you need them.
I have created a content app in which I am able to show and hide different fields using radio buttons but how to Show/Hide different fields Based on the dropdown value in Magnolia content app?
For radio button and fields i used below class info.magnolia.ui.form.field.definition.SwitchableFieldDefinition
and for transformer class i used
info.magnolia.ui.form.field.transformer.composite.DelegatingCompositeFieldTransformer
but now i want to use
info.magnolia.ui.form.field.definition.SelectFieldDefinition
instead of SwitchableFieldDefinitionbut I am unable to do so with any of the transformer class.
I also searched and found similar thread here but it has the incomplete answer!
According to https://documentation.magnolia-cms.com/display/DOCS/Switchable+field you can define a property named "selectionType" with the value "select".
I haven't tested that though.
If you have a look in SwitchableFieldDefinition, it looks promising though, because there's really a property with that name and it just defaults to "radio" but can be overwritten.
Are there plugins that achieve the following:
You can add text blocks into a section of a page (left, right, normal,bottom). the text isnt shown ommediately but after clicking the title/header of the text block which slides open the text. I'm in need of such an extension as I want to place much content on a site without throwing the whole text on a viewer. There seem not to ve any available.
By default TYPO3 doesn't force any particular frontend library so probably you won't find such ext (maybe somebody created extension like this but for 99% it will be required to fit it tou your needs)
Instead there are generic extensions like Grid Elements or Dynamic Content Elements (DCE) - you can use it to predefine your custom HTML structures and then reuse them easily (no need for advanced PHP programming of your own plugins).
So finally you can combine them with dedicated JS libs for frontend i.e. Bootstrap and its Accordion Collapse
If you use TYPO3 6.2 or higher have a look at df_contentslide. After install you'll find another section under appearance in CEs. Now you can slide every content element. It is easy to use and with little knowledge also easy to style.
I'm trying to build a form in the Zend Frameword in which there has to be a table like this:
So, it's a radiobutton followed by some descriptions about a subscription of some sorts. I have googled myself senseless, but can't make this happen. I have tried several form-decorators, but it seems that the radiobuttons stick together, and you can only wrap a whole group of radiobuttons in an html-tag...
The form will be rendered by a Smarty template, but I can't get the individual radio-buttons in the template. Maybe somebody has some experience with this.
Does anybody have an idea or a link to get me going with this?
This task is suited for View Script Decorator .
http://framework.zend.com/manual/en/zend.form.standardDecorators.html#zend.form.standardDecorators.viewScript
I developed a Sitecore control I'd like to put into a layout on one page.
In this case it's a registration page, and my control is defined as a sublayout.
What I did is went into the Page Editor interface, and plonked the control into one of the placeholders.
What I want to do now is to create a package only containing the information that this control is on this particular page, without affecting e.g. the content or subitems of this node.
Can you please advise on the best way to create such packag, what exactly to select in the Package Designer?
Thanks
I don't believe the Package Designer gives you granular control to include just specific fields of an item. You need to add the item as whole.
You should configure layouts and renderings in the presentation details of an item OR even better in the __Standard Values of the template.
You can call the presentation details dialog through the content editor. Just select an item in the content tree, click on the Presentation tab in the top ribbon and select Details. You can configure all layouts/renderings for the selected item here.
But ff you want to prevent content changes you really SHOULD configure the presentation in the __Standard Values of the template. This is also the way, which is recommended by Sitecore. If you do this, the layouts are all you have to put into a package.