I tried to delete InsideView from sugarcrm, but I do not know where to find the templete which includes them, It seems that InsideView was created by javascript.
could any one tell me how to delete InsideView from sugarcrm?
You can disable the InsideView connector from the Admin area which will hide it. Go to Admin->Connectors->Enable Connectors. Then select the InsideView tab and drag over all modules from Enabled to Disabled.
Related
How is it possible in version 7.6 of TYPO3 to add a second workspace? I was able to successfully activate the extension workspace management and there appears a menu entry workspaces in the menu bar but I could not find a possibility to add a second workspace. Furthermore there isn't a menu entry in the top menu bar how it used to be (atleast in version 6.1.5).
Is there a configuration step I overlooked? Was the workspace management concept revised in version 7.6? Is there documentation to this?
Regards,
Thomas
After you created the workspace and if it doesn't appear in the top menu bar you only need to log out and then log in again. After this it should appear next to the help menu entry. I tested it with TYPO3 CMS 8.1.2 and 7.6.9 and 6.2.25.
You have to create a new workspace in the list view on your very root page (Pid 0). Just click add record scroll down to workspace and create as many workspaces as you need.
As for the top menu. There is a menu entry. After installing workspace extension, try reloading you backend once. It should appear next to the help menu entry.
I have recently created a custom tool in Perforce P4V that I can use by right clicking a changelist and executing the tool. However, I would like to assign a shortcut to that tool and it does not appear is the "Shortcuts" section. Is it possible to do that?
This is possible now (eg. Verion 2017.3), You can assign a shortcut in the 'Manage Custom Tools' dialog. Just make sure that the dialog is big enough, otherwise you can't see the Shortcut column next to the Name column, or simply scroll to the left.
In admin , main menu is not displaying from menu manager but other menus like footer menu and header menu are displaying / working.
Has it been created? Was it accidentally deleted?
You may be able to recreate it - or go into the module manager and make sure that there's the appropriate module for it!
I have a system that I've built that makes heavy use of custom menus in FileMaker. When I log in as full access, and install the menu set with these custom menus, they appear fine. However, when a non-full access user logs in, they're disabled. This includes most of the custom menus, but not all.
For example, I have left the File>Change Password option in and the user I'm logging in as has the permission to change their password, but the Change Password menu item is disabled.
Other disabled menus include those I've placed in the View menu to navigate to different sections of the system, such as Home, People, Companies, etc. The functionality of these items is duplicated in buttons, and they work, but the menu is disabled. The buttons are calling the exact same script with the exact same parameter.
Alternatively, the File>Close command is left in and is enabled. So both Close and Change Password are based on existing commands but one's enabled and the other isn't. I can't seem to find anything in common with the menus that are enabled vs. those that are disabled.
So, under what conditions will a custom menu item be disabled?
Thanks,
Chuck
The online documentation says the following about when menus are dimmed:
Standard FileMaker menu items are dimmed if users don’t have privileges to perform the menu command. Menus are not dimmed if you attach a script to the menu item.
That being said, I wonder if you aren't encountering dimming because of the menus being based on an existing command which they don't have access to. I would try the following:
Turn off your custom menu for a moment and log in as the user who doesn't have access to the Change Password option. Is it still dimmed using the default menu set? If so, it sounds like you have a permissions issue and should explore that further.
In the permissions 'Edit Permission Set' window take a look at the 'Available Menu Commands' option and see how that is set up. If it's not set at 'All' try changing it to 'All'
For the View menu, look at the custom menu items and see if you have 'Based on existing command:' selected. If the menu item is performing a script, try unchecking 'Based on existing command:' and see if that changes the dimming behavior.
Make certain that the user has permission to run any script which the menu calls.
Good luck!
I accidentally clicked on "Validate" for all of my projects (instead of going to Team > synchronize...) and I have several validation errors and tons of warnings.
I can't figure out how to clear these so it goes back to just having the standard errors.
(One way is to go to "Configure Contents" of the "Problems" view and deselect the validation errors, but I know they're still there, just hidden... it bugs me that they're not actually removed)
I've tried restarting eclipse, tried cleaning all projects but that doesn't clear these validation errors.
You should be able to select all the offending markers in the Problems View, right-click and choose Delete from the context menu. Clean-building causes all builders to remove only the markers that they produced, but these markers weren't produced by a builder (you created them through an explicit invocation of the "validate" command.)
I'm not aware of a built-in way to clear them all. You might try deleting the markers file in
[workspace dir]/.metadata/.plugins/org.eclipse.core.resources/.projects/[project name]
Go to Window -> Show View -> Problems and delete error marker(s) on right mouse-click
You probably want to exclude some third party libraries (such as jquery-1.x.min.js) from being validated by your project.
In this answer I've documented how to disable it for specific sources -> How do I remove javascript validation from my eclipse project?
I'll just repeat the steps here:
Right click your project
Select Properties -> JavaScript -> Include
Path Select Source tab. ( It looks identical to Java Build Path Source tab )
Expand JavaScript source folder
Highlight Excluded pattern
Click Edit button
Click Add button next to Exclusion patterns box.
You may either type Ant-style wildcard pattern, or click Browse button to mention the JavaScript source by name.
BTW, I think you should never disable validation for sources that you are in control of (i.e. coded by yourself or your team).
In case you select and delete more than 100 problems and eclipse only deletes up to 100 problems, check the "Configuration Contents..." menu. This menu is the top-right of the problems tab. There is a small triangle drop down menu containing the configuration. In that menu, there is a "Use limits" checkbox which you should uncheck to be able to dleete all problems at once.
I was facing same problem but i am able to remove these errors.
Go to project properties -> validations and click on override validation preferences.
Click on disable all and Apply changes and click on okay. Let the project built.
Again go to project properties and change the validation settings as of original.
In Indogo
GO to
Property -> Builder - > Uncheck Validator
To disable validators in your project or workspace, complete the following steps:
Click Window--> Preferences and select Validation in the left pane. The Validation page of the Preferences window lists the validators available in your project and their settings.
To disable individual validators, clear the check boxes next to each validator that you want to disable. Each validator has a check box to specify whether it is enabled for manual validation or on a build.
Optional: You can also change the following check box options on this page:
Allow projects to override these preference settings--->Select to
set individual validation settings for one or more of your
projects.
Suspend all validators-->Select to prevent validation
at the global level. If you select this check box, you can still
enable validation at the project level.
Then Click OK.
If you want to set individual validation settings for one or more of your projects, see Overriding global validation preferences