I need to keep some custom created configuration keys to be disabled (unchecked) by default. However, its behaviour can be changed by user after that.
By default, it shows those conf keys checked or enabled. I want them to be disabled by default. Please let me know how to do so
you can uncheck the custom key and then do database sync
Related
I have a mediawiki installation. When I double-click on text, mediawiki goes into edit mode. I don't like this, because I want to use double-click for selecting text. (I actually use triple-click for selecting a paragraph because I have a Mac and it just works.)
How do I disable double-click to edit?
I'm happy to disable it individual users, or disable it system-wide. I'm the only user.
It's unclear from your question if you want to disable this for you as a user, or change the default setting.
In the latter case, as an administrator, add this line to your LocalSettings.php:
$wgDefaultUserOptions['editondblclick'] = 0;
Though the default setting in a fresh MediaWiki install is '0', or 'false' (at least in the latest stable version, MediaWiki 1.34)
If you want to disable it for you as a logged-in user:
Go to the page Special:Preferences, click on 'Editing' and deselect 'Edit pages on double click'. Be sure to save.
If the default setting was '1' and you want to disable it for all existing users, you can use the script: UserOptions.php
Documentation on this setting can be found at: https://www.mediawiki.org/wiki/Manual:$wgDefaultUserOptions#Default_values
I am awkward because I am trying a translation tool, but please forgive me
As a problem su command is no longer available
I think that the same account was used as the cause and that access was done simultaneously from different terminals
Please tell me how to resolve
I had the same problem today. You need to enable oslogin by adding the necessary meta data to your Instance (likely your project as well).
Instructions below. Solved it for me. Hope it helps
https://cloud.google.com/compute/docs/instances/managing-instance-access#enable_oslogin
To set enable-oslogin in project-wide metadata so that it applies to all of the instances in your project:
Go to the Metadata page.
Click Edit.
Add a metadata entry where the key is enable-oslogin and the value is TRUE. Alternatively, set the value to FALSE to disable the feature.
Click Save to apply the changes.
To Set enable-oslogin in metadata of an existing instance:
Go to the VM instances page.
Click the name of the instance on which you want to set the metadata value.
At the top of the instance details page, click Edit to edit the instance settings.
Under Custom metadata, add a metadata entry where the key is enable-oslogin and the value is TRUE. Alternatively, set the value to FALSE to exclude the instance from the feature.
At the bottom of the instance details page, click Save to apply your changes to the instance.
To Set enable-oslogin in instance metadata when you create an instance:
In the GCP Console, go to the VM Instances page.
Click Create instance.
On the Create a new instance page, fill in the desired properties for your instance.
In the Metadata section, add a metadata entry where the key is enable-oslogin and the value is TRUE. Alternatively, set the value to FALSE to exclude the instance from the feature.
Click Create to create the instance.
How to enable code completion in PhpStorm only with Tab key, and other keys (e.g. Enter) should be disabled? Can't find this option in settings.
The problem is in the conflict between code completion and live templates. They both use the same shortcuts('tab' and 'enter'). I don't know why. How to separate them?
Completing code items can be configured via "Choose Lookup Item" actions in Settings\Preferences | Keymap:
Change or remove the assigned shortcut as #LazyOne suggested.
You can also change the key to expand live templates with:
So you can eventually configure this in any way you want.
I wanted to set $cfg['RowActionLinksWithoutUnique'] to TRUE so that I can edit the datas in phpMyAdmin without any Primary Keys present, but after checking over config.inc.php and both layout.inc.php in phpmyadmin/themes/
I can't find the mentioned configuration.
Does anyone know how where can I modify $cfg['RowActionLinksWithoutUnique'] ?
Currently using phpMyAdmin via XAMPP Control Panel v3.2.2.
There are default directives, and you only need to put something in config.inc.php if you are changing from the default. In fact, the official phpMyAdmin distribution doesn't come with a config.inc.php at all; if you need to change some value you have to create the file yourself. Since you're trying to change a setting that doesn't already exist in your configuration, you simply have to add it to config.inc.php. Just find a good section, anywhere will do really (I like to keep it near the top so it's visually separated from the server-specific settings), and add the complete line like $cfg['RowActionLinksWithoutUnique'] = true;
Save the file, logout and log back in so the changes are loaded, and you should be all set.
You can see more information in the phpMyAdmin manual.
Just open XAMPP and click on "Config" in the Apache module. Then select "phpMyAdmin (config.inc.php)".
Don't forget to set the semicolon ';' at the end of the variable.
$cfg['RowActionLinksWithoutUnique'] = true;
Is there any way to add extra column to Permission tab in Configuration setting of Portlet? I have a portlet which allows adding and editing of some documents. So i need to set some configuration such as Allow Add / Edit to user based on their roles.
I read about "Implementing Configurable Portlet Preferences" in the documentation section of Liferay. It adds an extra setup tab where we can specify some settings. However if i need to add some extra columns/parameters in existing tab, i am not sure how to do it. If you have any ideas, please let me know.
Thank you
What I understand is you are looking for additional permissions in the permissions tab. In order to achieve the same check out - https://www.liferay.com/documentation/liferay-portal/6.0/development/-/ai/security-and-permissions
Let me know in case of any doubts.