I'm currently trying to install a module (service level agreement module) on Odoo 8. I downloaded the zip, copied it over to the addon directory specified in the configuration file, and then restarted the server. To ensure it restarted I killed the old process, check that it was dead, and then started it up again.
I attempted to search for the module (searched for Service), and it was not found.
Am I missing something?
Thanks.
They appear after you update Module List but you need the "Technical Features" permission. You even have to set it for your admin user like this.
To activate the technical features, you have to add access rights to your user. You must edit your current user from the menu Settings > Users. Edit your user (probably admin) and, in the Access Rights tab, check the option Technical Features.
Did you update your list of modules ? (Settings / Modules / Update Module List).
You need the 'Technical Features' rights to do that.
Related
I'm an experienced (ASP.NET|Java|PHP|web) developer, new to DotNetNuke.
Currently I'm following a blog tutorial to try to get an Angular module up-and-running in my local installation of DNN 7 (http://www.bitboxx.net/Blog/Post/505/DNN-module-development-with-AngularJS-Part-1#)
My environment: Windows 2012 Server R2, SQL Server 2016 Express, Visual Studio 2015 and DNN 7 on IIS 8.
DNN nuke runs fine.
I installed the downloaded module from the blog to my DNN. I'm having problems to run the HelloWorld example (at the bottom of the 2nd part of the course).
Through some trial-and-error I found out this has to do with the [SupportedModules] attribute on the controller.
Without this attribute it runs fine, but with the attribute it won't.
How does DNN determine the name of the module? The "installation" process was no more then unzipping the modules contents to the DesktopModules directory within my DNN directory (in inetput\wwwroot).
Do I need to install/configure the modules in Settings > Extensions?
Or am I missing some other point with regards to the DNN 7's security?
Thanks in advance for any help/thoughts!
Yes, you need to install the module through the Extensions mechanism in DNN. This will register the module so DNN is aware of the module as well as make sure the files get copied to the right places, in accordance with the installation manifest (the .dnn file you should find inside that .zip file)
However, looking at the blog article you referenced, I don't see an actual installation zip file anywhere. The only download I found was for the project as a whole. You would need to package your compiled solution into an installable zip file (with a .dnn manifest file) or you need to manually register your extension from the Extensions page.
On that page you should click the "Create New Extension" button which will walk you through supplying details for the module. Choose Module as the Extension Type
Only a few of the items are required. The "Name" you use for the module will be the name you use in SupportedModules. It will also default your folder name (the folder in /DesktopModules) to the module name. Friendly Name, incidentally, is what will be displayed in menus and such.
Once you've created the module it should be registered with DNN. You will probably need to restart your AppPool and website for the change to take effect.
FYI, SupportedModules isn't strictly required. If you're building this for a client and not building this for distribution.
Hope this helps.
The modules a Webmin user can see in the menu can be configured via the GUI under Webmin/Webmin Users/Available Webmin modules. Where are these settings stored? I need to restore them programmatically on a fresh Webmin installation - without accessing the GUI.
The Available Webmin Modules that are displayed in the menu are reflected in file /etc/webmin.acl. It contains a space seperated list where modules are added when changing the settings via GUI.
In this case the configuration was made for the root user. The list therefore has the format
root: moduleX, moduleY.
It is likely that configurations for other users would be added in the same format, e.g.:
userXYZ: moduleX, moduleY
Restoring webmin.acl did the trick.
I am about to create a MSI package.
During the installation (launched e.g. via double-click on the MSI) some files contained in the MSI are deposited deeper under c:\ProgramData (resp. the CommonAppDataFolder), e.g. c:\ProgramData\myCompany\myApplication.
Later when the installed application is run by the user the application may need to modify these file.
The problem is that neither the running application nor the user e.g. via Windows Explorer has the right to modify any files under c:\ProgramData\myCompany\myApplication created during installation.
The files do not have a readonly attribute set.
The strange thing for me now is: If I install the MSI via msiexec /q /i then I have write permissions on these files.
My MSI is created with WiX, my os is Win 7, the user is member of the administrator group.
Can anyone tell me why that is so, and how I can gain write permissions to these files w/o having to use /q /i?
Thanks
Jan
EDIT 2014-03-24: Damned. I missed to specify the InstallPrivileges attribute on my element, I just didn't know about it.
Setting it to "limited" does not show up a UAC prompt when installing to ProgramData! And now the user / my application is allowed to overwrite files in the destination folder :)
I don't know why that behavior would be different regarding access to that folder unless you have a custom action that does something that is only in the UI sequence. That's the only functional difference I can think of - the UI sequence is suppressed in a silent install.
However the common app data folder is not normally writeable to limited users. I'm not sure how much you know about UAC, but it doesn't matter if the user running the program is an admin or not because by default admins run with limited privileges. If the app needs admin privilege to run then it needs building with an elevation manifest so it asks for elevation to admin privilege. Either that or run it as administrator from a shortcut.
Windows access control is extremely complicated to deal with. In every version of Windows there is something new and changed to deal with, and it looks like the default write access in ProgramData now includes some sort of special ACL / DACL. If this is indeed the problem you can apply new permissions there and open up for regular users to write. Please note that I am not quite aware of exactly what newer versions of Windows apply as default. The tool I generally use to set permissioning is subinacl.exe. A real handful of a tool with a command line that can scare the most experienced system administrators. Some command line samples are here. You can also use the LockPermissions table in MSI, but somehow there are some issues with how these permissions are applied to the file system object. subinacl.exe is more complex, and more capable.
More on file and folder permissioning:
http://technet.microsoft.com/en-us/library/bb727008.aspx
http://support.microsoft.com/kb/308419
With regards to where you should put different types of files on the system, please check this thread.
Hi I am using openerp 7 on my XP . I have created a custom openerp module . It was shown in openerp and I installed it successfully but now I dont know where it has been installed. I also cannot view other installed openerp modules . I wanted to see the installed modules . How to view them?
Hopes for suggestion
When you said you installed the module, what all you have done? Here are some steps to follow.
Create the module (detail on how to create a module is out of scope)
copy the module folder in to the addons folder
Login in as admin
you probably want to see technical details as admin. So, go to "Settings / Users / Users". Open the admin record and edit it. And on access rights tab enable "Technical features". Save the form and reload the page.
If the DB is created before the modules folder was copied in to addons, go to "Settings / Modules / Update module list" and Update the module list.
Go to "Settings / Modules / Installed module" remove the "installed" filter from search box and search for your module name.
Once found the module, click the install button.
from "Settings / Modules / Installed module" find and open the module in form view. Under the "Technical Data" tab, you will see the views added by the module. Under "Features tab" you will all the menus and report created by the module.
I created a new module by following the testimonials example in the SDK. But, it won't install. There are no error messages to help direct me in a certain direction.
I've fired up the project in debug mode setting a break point on the install method, but it never gits hit.
Anyone know why that would be?
Thanks,
Jacques
If it's not installing it might not be properly registered in the system. What version of Sitefinity is this? If one of the more recent ones there is a section under Administration > Modules where you can install the module. Otherwise you need to do it in the Administration > Settings > Advanced > System > Application Modules and create a new entry there manually
Either way, make sure that the full name of your module is correct (including the namespace) as the Type, and that the startupType is set to "OnApplicationStart" so it initializes when the website starts.
Then force your website to restart (easiest way is to just save the web.config file) and it should fire up.
I hope this is helpful!
If you have done all this and it's still not firing, can you tell me if the module is listed in the systemConfig.Config file under app_data folder?