Security Groups subpanel is not showing in main modules such as Accounts, the relationship and the subpanel are both appearing in studio, but not in the detail view of the account. When I checked my log I found this:
Bad subpanel definition, it has incorrect value for get_subpanel_data
property securitygroups.
I am using SuiteCRM Version 7.7.8 ( based on Sugar CE Version 6.5.24).
I find a solution :
In "modules/Accounts/vardefs.php" for unknown reason it missed "security_groups" declaration in this line of code :
VardefManager::createVardef('Accounts','Account', array('default', 'assignable','security_groups',
'company',
));
Related
TYPO3 9.5.15
When I edit an existing category and than click the "+new" button inside the edit form, i will get the error:
#1534710048 TYPO3\CMS\Core\Exception\SiteNotFoundException
No pseudo-site found in root line of page 17
Page 17 in this case is absolute incorrect - this is the uid of the sys_category from which editing form I came from. the categories were saved on pid:6
I can do the same task from other category edit-forms, but not from all. I cannot figure out what is the difference of the categories where it doesnt work.
The basic site-configuration is configured and working, there is only one language, no workspaces.
Has anyone ever had a similar problem?
Side note: It still "works" for records which have the same uid as a pages record. It also "works" for L>0 records because they still fall back to 0.
However, this is not a core bug but a misuse of the internal DisplayCond by 3rd party extensions.
E.g. in the latest tt_address this is already fixed, see: https://github.com/FriendsOfTYPO3/tt_address/commit/4501d1f30f3381a235e447567018e6d5646ec069
So changing the TCA DisplayCond of the sys_category slug in my own extension did the trick in my setting
'displayCond' => 'VERSION:IS:false',
I looked at this Similar Question on here but I didn't understand half of what everyone is saying there as I'm not very familiar with TypoScript...
Let me start from my point of view: I got a backend tree in TYPO3 6.2 that looks like this:
Data is of type "Folder" where I want to store my records.
Userroles, Admins and Lawyer are of Type "Standard" while the last two contain the Plugin "Website Users".
Now I want to add a new fe_usergroup to page Userroles:
I get following error:
It's the same when I try inserting a new fe_user in Admins:
So in the other answers from mentioned question they're talking about Page-TS-Config - I looked at my Userroles Page and saw this:
and I went to the Template Analyzer and searched for allowedNewTables and deniedNewTables but no results. And to the comment: section ctrl which value has rootLevel - but those TCAs are from Extbase right? So why would they be wrong...
I must have done something wrong but I have no idea what it could be.
It worked before I think...although I don't know about the usergroups, didn't try to add a new one recently.
I placed
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_myext_download');
into the ext_tables.php of myext to allow this kind of records.
Maybe that helps.
Add in Your ext_tables.php in Your Extension following code:
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_your_extension_table_name');
In TYPO3, you have to define, which tables are allowed on standard pages. There is a method in the ExtensionManagementUtility, that does extacly that:
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_yourtable');
If you have a look at the source, you'll see, that this method ist just one line of code that concatenates table names into the global configuration array, specifically at
$GLOBALS['PAGES_TYPES']['default']['allowedTables']
Its possible that something in your TYPO3 installation messes with this line.
Check the value of this configuration value in either the Install Tool or the Confuguration tab in the backend. If this line contains anything other than comma seperated table names, something is wrong. TYPO3 base table names like pages,tt_content,fe_users,fe_groups and so on should also be listed there by default.
Is the page that you are trying to add usergroups to of type "page" or "directory" (see "General"-tab). Probably it must be of kind "directory" or "folder"
I have created a form in orbeon form builder which has three 30 questions which are belongs to 3 categories. Now I don't want to show all the 30 questions to every one also I don't want to create different forms for each category because all these categories belongs to one module.
While adding the form I have a drop down question like "Select Category". If user select the first category then I need to display only first category related questions and hide the second and third category related questions.
Is there any way to achieve my task in Form Runner?
UPDATE:
#ebruchez, I have followed your suggestion, I tried testing this feature on default "contacts" form. I have created a new text field in the contact form named "Account Related Field" as a label and "control-10" as Control Name. Below is the screen shot for the same.
Then After that I clicked on control setting of the "Account Related Field" and under the "Formulas" tab I have added the following XPath expression in "Visibility" section. $topic='Account' following is the screenshot.
After adding the path expression I saved the contact form and published. Then I tried opening the form in form runner. But I am not able to view the "Account Related Field" field on UI after selecting the "topic" value is "Account" in the form runner. This is the screenshot of form runner after publishing form in form builder.
Did I miss something. Please help to resolve the issue. I need to view "Account Related Field" field only if "topic" field value is "Account"
Thanks in advance.
Yes you can, by using a "Visibility" formula under the section settings. For example if your dropdown is named foo and has two entries, category1 and category2, then you can write:
$foo = 'category1'
to make the section visible only if the dropdown selected category1, and:
$foo = 'category2'
to make the section visible only if the dropdown selected category2.
This doc might help.
I'm trying to setup a form where some fields needs to be hidden depending on the user role. I'm doing this in my own module using hook_form_FORM_ID_alter. No problem with common text, email or link fields (e.g. $form['field_companyname']['und'][0]['value']['#type']='hidden'). But for an image field or a multiple value file field the usual way won't work.
Anybody can give me a clue?
I think your going about this the wrong way. Since your limitation is based on roles you can just use the permissions system. Check out field permissions module.
I recommend you to use #access for the element instead of just hiding the field.
For field company name it will go like this:
$form['field_companyname']['#access'] = FALSE;
In our Jira (v4.4) we are using Greenhopper (v5.7.4), as such Greenhopper makes use of the Flagged custom field to mark Impediments, it is of type "Multi-Checkboxes".
Whilst transitioning from one state to another we are using a pre-installed Post Function to try a set the Flagged custom field. Specifically we are trying the 'Set field value from User Property value' post function.
To support this 'post function' we have tried adding a transition property called flagged with value Impediment and referencing it in the 'post function'.
This doesn't work.
Essentially 2 questions arise.
Is this 'post function' the best way to set a Multi-Checkbox.
If so, how do we specify the Impediment to be true?
For a better explanation of the default flagging behaviour see Flagging Issues in Greenhopper, this is what we want to automate in our transition's 'post function'.
Resolved the Issue - for those that may be looking for a similar solution - here is what I discovered, hope it helps.
Contacting Atlassian the following was suggested:
To set the multi checkbox custom field via post-function is possible.
First of all, you need to install JIRA suites utility plugin:
https://plugins.atlassian.com/plugin/details/5048 After that, in the
workflow transition, add a "Update Issue Custom Field" post function
with your custom field and put the flagged option (e.g. Impediment)
written in the "Custom Field Value" field.
So using the suggested "Update Issue Custom Field" post function I chose the Flagged custom field and used the value 'Impediment' on its own. This worked.
For another transition that unmarked the impediment I used the "Clear Field Value Function" and simple chose the "Flagged" field. This also worked at clearing the Impediment.