Prior to 2.0p3 the user could choose to show hidden columns.
Is that still possible in 2.0p3? It does not appear to be, but is there an option to enable this? This functionality was nice in the previous versions, so I'm hoping it's not gone permanently.
I'm assuming you're talking about hiding and showing columns in the context of a grid.
When you are adding in your grid configuration, you must add the following config:
gridConfig: {
disableColumnMenus: false,
// more config options go here...
}
That will reenable ExtJS's default of showing the drop down menu on each grid column.
In SDK 2.0p3, we disabled the column drop down header by default due to a combination of inconsistent functionality and minor styling issues. I just filed a defect regarding this issue to make the column chooser more consistent with the rest of the app (such as the Backlog page).
Related
I have a project which is using Umbraco v7.7.9 installed with nuget.
I was wondering if it is possible to change the buttons displayed in the sidebar section when a user selects to preview a content node. Particularly I want to remove the option that allows the user to close the preview.
The reason I want to hide this option is because some of the content the backoffice users will be previewing will not actually be published yet so clicking the close preview button causes an error.
I first asked this question on the Umbraco forums but haven't received a response yet, here is the link to the question: https://our.umbraco.org/forum/extending-umbraco-and-using-the-api/90878-editing-preview-window-sidebar-options
Thank you in advance.
Currently no - it would not be possible without doing hacks in the Core that would be overwritten when you upgrade your site (unless you manually merge your changes in when updating).
If you however don't mind doing that - the file used for the preview function is /umbraco/preview/index.html. You should look for the element with an exitPreview() click handler attached to it.
In later versions (7.10+) this modification will have to be done in /umbraco/Views/Preview/Index.cshtml instead, as these static files will be changed to MVC actions.
We have an existing text field 'Defect Found Version' (DFV) and a new Field I have created 'Defect Found Version Picker'
I have made the Picker mandatory & that works fine, listing all the cersions on the project.
The DFV field is set to 'Optional' on the right hand side of the Configure Field layout page, however next to the name on the left there is the text REQUIRED & I can not see how to disable this.
Even if I remove this field from all screens I get an error when I create a bug saying that DFV is required.
Any thoughts please ?
Look at the Field Configuration Scheme used by the JIRA project. Then look at the field configuration used for that issue type. That's where it is being made required. Unless it's because of the JIRA Behaviour plugin, so check if that is active
Do you have take a look on your Workflow validator ?
Sometimes, it's required on your workflow, and not on your screen.
In Jira (5.1.3), I have created a custom (Multi) checkbox
I have defined only one option (Yes), and set the default value to Yes.
When you edit a jira, the checkbox is not pre-selected, even though the default is the same as the value for that checkbox.
Is this a bug in jira? or is there something I need to do to get the checkbox pre-selected?
I have spoken with Atlassian (Jira) support, and know the answer. The configuration of the issue, whether issues already exist, and the order you do things matters.
When you set the default value, jira detects the change and tells you that you need to reindex the issues. But this does NOT set the default for existing issues though
You have to do re-index, and then select all the issues (using a filter) that should use the default, and manually do a bulk update and set their default value.
New issues after that should use the default automatically.
I am working on a web app that utilizes jquery UI for drag/drop functionality.
There's a strange problem in IE browsers only. When user drops an item inside a container, that item is added to the container but also leaves a remnant of it on the page.
Here's a working DEMO.
Drag items from the left column to yellow field to create container.
Add second item to newly created container.
What's causing it and how can I fix it?
This happens in IE8 and below.
The error is:
SCRIPT5007: Unable to get value of the property 'options': object is
null or undefined jquery-ui.min.js, line 105 character 158
That line is:
var a=d(this).data("draggable").options;
The jQuery UI version they are using is 1.8.11.
I would suggest upgrading to the latest version of jQuery UI and see if that resolves your issue.
If not, you might want to create a test case and submit it to them as a bug.
I'm building a form in the Orbeon Form Builder. The simplest way to recreate this problem is as follows:
Put a control on the form.
Give it any label, it does not matter.
Go to 'control details'.
Change the 'Control Name' to 'test-controlenummer'.
Confirm with the 'apply' button.
See the control itself disappear
Notice that the question mark of the help feature does not disappear, nor do the delete and validation options once you hover over the formerly-visible-component. The grid cell also acts as if it was occupied. The control simply does not show and some of the changes to the name and/or validation options result in XPath expression errors.
I have taken a quick look at the underlying xml code, however at first glance I did not find anything out of the ordinary.
It disappears because of a bug in Orbeon Forms 3.9 when control names contain a dash. Like you said, there is nothing wrong with the markup Form Builder generates, but it then incorrectly just doesn't expect a dash to be present in the control name.
This bug has been fixed in the latest code, so it won't be present in the next release.
If you are using Orbeon Forms PE, I recommend you contact Orbeon to see if you can get a patch for this (either through Basecamp if you already have a support account setup, or by email, info AT orbeon.com).
If you are using Orbeon Forms CE, for now, you can work around this issue by avoiding dashes in the names of your controls.