I have the following set in trac.ini:
[components]
acct_mgr.admin.accountmanageradminpanel = enabled
[inherit]
plugins_dir = ../../plugins
and in a global plugins folder I have TracAccountManager-0.5.dev0-py2.7.egg.
However, I don't see the account manager admin panel still. Putting it in the project specific plugins folder seems to resolve the issue. I'd rather have it be globally inherited. Any ideas?
EDIT:
Forgot to add the following details:
This is on Windows 7, and trac version is 1.2.2.
Let me know if any other details are needed.
EDIT:
It seems to be picking up the plugin b.c. if I go to the admin tab and then manage plugins, the plugin shows up as tracaccountmanager 0.5.dev0. After seeing this, I've confirmed that I do not have a copy of it in the project specific plugins folder.
I've also characterized the inherited plugins dir to be relative to the project env specific plugins dir.
Non-absolute paths are relative to the Environment conf directory. You probably need to modify your relative path. I will update the Trac documentation to specify this detail.
After messing around with the [components] configuration it seems that the documentation for https://trac-hacks.org/wiki/AccountManagerPlugin/Modules#AccountManagerAdminPanel is not working for me. Instead of using
[components]
acct_mgr.admin.AccountManagerAdminPanel = enabled
as the documentation suggests, I'm finding better success using
[components]
acct_mgr.admin.configurationadminpanel = enabled
acct_mgr.admin.useradminpanel = enabled
acct_mgr.api.accountmanager = enabled
acct_mgr.notification.accountchangenotificationadminpanel = enabled
I concluded this from going to the admin plugins section and expanding the tracaccountmanager 0.5.dev0 section, clicking enable all, then started disabling components in batches or individually. In fact, I don't think acct_mgr.admin.AccountManagerAdminPanel does anything from what I've observed.
Related
Despite a successful build, no modules will load. The Browse menu is empty (except for Assets) and custom modules in the Configuration menu are missing.
After downloading the most recent build from our repository, I followed all steps in the "Source Code Getting Started" page. It has been a few months since looking at the VC documentation, and it looks like it has been updated. I recall an extra step after creating the Assets virtual folder in IIS that isn't there now. Is there perhaps a step here that is missing since the docs update?
Fwiw, the build deployed in our QA environment is fine. This is the same code, but I am trying to run locally and am having no luck with modules.
Virtual folder for Modules is optional in IIS and this step was skipped in the updated docs. But adjusting permissions in needed: "Open properties for vc-platform\VirtoCommerce.Platform.Web\Modules (create this folder if not exsist) folder and give permission Modify to IIS_IUSRS user group as shown above."
I created a project using Amber Smalltalk and hosted it on a remote server so multiple people can access it. The network connection is slow and it triggers timeout and just figured that the setting 'waitSeconds' solves the problem.
But, we can't figure out where to set it.The config.js file is generated, and can't be changed manually. Only managed to change it in the default settings in the requirejs source. But that should not be the right place. Please tell me how to solve this problem.
config.js is generated using https://lolg.it/herby/amd-config-builder
from the readme:
The local.amd.json files describe the require.config part for the module at the directory where they are present.
to add WaitSeconds to config.js add it to local.amd.json at the root level of your project.
I've been searching for a solution but I can't find one.
I have a global configuration directory in my IntelliJ workspace. I also have several dozen modules. I would like each module to automatically include the global config directory in its path when I run or test a class.
Is there anyway to do this within IntelliJ? I don't think I should need to edit the configuration for each "Run/Debug" config to include the directory.
You'll want to set it in the Defaults for the type of Run or Debug Configuration that you are using.
For example, if I always want a Java Application to have the VM Option -XPutYourThingyHere, then I could go to Edit Configurations, Defaults, Application, and put -XPutYourThingyHere in the VM Options box. Then all new Applications that I run will have that option.
I would like all developers on my team to use the same default code style settings. We all use IntelliJ 11+ as our IDE and we use git as our source control system.
What is the easiest way to make sure they're all using the same settings? I thought there would be a way to check in the style settings into the project and have their editors discover them automatically, but that doesn't seem to be the case.
PS. I don't mind if developers consciously override some of the default settings with their own preferences, but I do want to make sure that we all at least start from a common set of default settings.
Code Style can be copied to project and saved in .idea/codeStyles to be shared via version control:
Copy to Project Click this button to create a copy of the current global scheme to the project level. After creating the copy, IntelliJ
IDEA suggests to switch to this new scheme at the project level.
The Settings Repository feature was introduced at IntelliJ IDEA 2016.
This option helps us to share IDE settings between different computers, including sharing settings between developers.
The settings are stored at Git repository, for example on GitHub or Bitbucket.
To setup Git repository we should set URL via Settings Repository menu option.
The developer can load remote settings, overwrite remote settings or merge local settings with remote ones.
The structure of Git repository with settings:
I used personal access token for GitHub authentication.
More information:
Settings Repository
Creating a personal access token for the command line
I came across this long after the fact, but thought I'd share if anyone ran into this. Add the following to your .gitignore
# IDE - IntelliJ
/.idea/*
# Keep the code styles.
!/.idea/codeStyles
/.idea/codeStyles/*
!/.idea/codeStyles/Project.xml
!/.idea/codeStyles/codeStyleConfig.xml
# Keep the inspection levels
!/.idea/inspectionProfiles
/.idea/inspectionProfiles/*
!/.idea/inspectionProfiles/Project_Default.xml
And of course, make sure your .gitignore also has a ! in front of it so these changes get picked up.
Basically, gitignore's recursive looking is a little wonky, so the below ignores a directory's contents, except for a subdirectory, then ignores that subdirectory's contents, except for the files we want.
codeStyleConfig lets you use per project settings, the project file itself is your actual code styles, and I included the Project_Default as it holds the warning levels, which you likely want if you're doing the code style work anyways.
You can create .editorconfig file in Your project (and it can be managed on directory level). More info on https://www.jetbrains.com/help/idea/configuring-code-style.html#editorconfig and https://editorconfig.org/
With this approach You can keep all Your code style settings in one file and it's not limited to IJ only.
I'm trying setup the Versioning bundle in RavenDB: http://ravendb.net/bundles/versioning
The installation instructions are pretty straight forward:
Simply place the Raven.Bundles.Versioning.dll in the Plugins
directory.
I've tried this do this by creating a "Plugins" directory under the Server directory (the Server directory contains the Raven.Server.exe), and dropping Raven.Client.Versioning.dll into that Plugins directory.
However, when I run RavenDB after that (either from the command line or as a service), it doesn't give me any indication that it has recognized the plugin, and when I save/edit new documents no versioning is being applied.
I've tried running with the default plugin directory settings (which supposedly automatically looks in the Plugins directory), and I've tried manually adding the PluginsDirectory setting to Raven.Server.exe.config, to no avail.
Has anyone been able to get plugins working, specifically the versioning bundle? Do you hae to do anything special?
Mike,
It is supposed to just work. Take a look at the statistics, you should see the versioning trigger registered there.
It is important to ensure that:
You are using the same version of the dlls
You restarts RavenDB after copying the directory
You don't reference another Raven/PluginsDirectory in the configuration
It is probably better to follow this up in the mailing list.
For Raven v2, you'll also add the bundle name to the the Raven/ActiveBundles property on a database document. The names should be semicolon-delimited.
For example, I have a database called MidwestAnimalRescue. To enable the Periodic Backup bundle and the Versioning bundle, my document will look like this: