Is there any difference between modules & app in odoo - odoo

I have installed odoo ver8.0 in my local machine.
I just want to know:
Is there any difference between modules & apps in odoo. If yes what is it?
Also i want to know the difference between the links 'Local modules' & 'Apps' in the left menu of odoo

Difference between the links 'Local modules' & 'Apps' in the left menu:
The "Apps" are online (it doesn't work to me because I use the OCA version) and the "Local modules" you can install them offline. What I do is install the disable_openerp_online module, in order to hide the "Apps" menu, because you can install your own local "Apps" from the "Local modules" menu as well.
The main difference between "Application" and "Module":
It’s common to hear about Odoo modules and applications. But what
exactly is the difference between them? Modules are building blocks of
Odoo applications. A module can add or modify Odoo features. It is
supported by a directory containing a manifest or descriptor file
(named __openerp__.py) and the remaining files that implement its
features. Sometimes, modules can also be referred to as “add-ons.”
Applications are not different from regular modules, but functionally,
they provide a central feature, around which other modules add
features or options. They provide the core elements for a functional
area, such as accounting or HR, around which other modules add
features. Because of this, they are highlighted in the Odoo Apps menu.

Modules are individual pieces/directories of code that extend introduce functionality. An app is a collection of modules, usually with a configuration option, that represent the same purpose (for example: Sale or Purchase).
https://www.odoo.com/forum/help-1/question/what-is-the-difference-between-an-app-an-addon-and-a-module-56285

Related

Module Selection tab is missing in Prestashop 1.7.4

I've just installed two instances of Prestashop on my local server from the same downloaded zip. However on one install, the module "selection" tab is missing, preventing me from installing modules placed into the module folder.
I've tried clearing the cache folder to no avail.
Would appreciate any insight into the matter.
Kind Regards
Musaffar
That's a bug!
Waiting for the team to fix it.
But here is a work around:
Access the installed modules tab.
Above in the url, change manage with catalog as follow:
And finally, if you want to search a module you are building, or any other module, directly search it using the search bar (the category menu, can suffer problems, it doesn't show well, you can use the developer inspector, and change the css (set the z-index to a big number, something like 5000)), so it can be shown if you want! but it's faster to directly search for what you want.
And here you can see your module, you are building. If that's what you're searching, you can install it too.

I want virtocommerce in my own local repository.(include storefront, platform and modules). How to setup all of these in my solutions?

I want virtocommerce in my own local repository.
storefront is a solution that will configure it according to the following link:
Storefront Source Code Getting Started
And it works.
But I want to have a solution For platforms and modules,
Like the link below:
vc-integrations
But I need the platform and modules to be connected to the github for the latest changes.
I've studied the link below:
Source Code Getting Started
but I do not understand how should I configure for my goals (one solution for platfrom and modules and fork, clone ,upstream for all for get latest versions of them)
We've used to have a single repository and single solution for Virto Commerce Manager and modules (vc-integrations). It was difficult to maintain and release often. That's why the single repository was split into many "1 module per repository" pieces.
We consider that in most cases having only Virto Commerce Manager configured should be sufficient. What's your scenario? Check "Manual module installation from source code" section in Source Code Getting Started to get started.

Build a (custom) module in Odoo OpenERP

I have downloaded the source code of Odoo (previously OpenERP) and installed OpenERP. I wanted to know how can I create new module, build it and install it (on Windows) when I don't have the Update Module List.
Take a look at this doc. This is in new api version 8.0
Odoo documentation
To build an Odoo module please Have a look here Which is the Basic Odoo Documentation to builds a new addon. To update Apps list after building the addon after restarting the server you have to follow below methods according to the versions so that you can customize it.
Odoo V8
Go to settings -> Users -> Check the Technical Features.
Update Apps list and Install custom add-on.
Odoo V9
click on About, will open wizard
Use active developer mode and then Update Apps list and Install custom add-on.
Odoo V10
Goto Settings -> Activate developer mode and then Update Apps list and Install custom add-on.
After Updating the module list you can see the custom add-on.
First of all place your module into addon folder of your odoo installation
Log in as Administrator
got to settings - users - Administrator
click on Edit
Check Technical properties
Save and refresh your browser
Go to Settings - Modules - Refresh module list
Click on Refresh
If everything went well you will see your own module within the list
Ensure you have technical features enabled for your user in the access rights section.
Once you have enabled it, logout and login again and you should see Update Module List menu item
As a matter of first importance put your module into addon envelope of your odoo establishment
When you have empowered it, logout and login again and you ought to see Update Module List menu thing. An other way to odoo erp customization
Sign in as Administrator
got to settings - clients - Administrator
tap on Edit
Check Technical properties
Spare and invigorate your program
Go to Settings - Modules - Refresh module list

How to install Modules in Orchard CMS

I'm trying to use the FeaturedItemSlider Module in Orchard CMS, which has already been installed and enabled. How do I use this module after all this is done? I don't see it on the left hand navigation pane in the admin dashboard and, to be honest, I don't actually see any of my installed modules there. How do I use modules once they are installed?
If you see no menu items for modules that you know should have items (and you should see one for that module called "Featured Items") then I would start by checking the log. There are a few scenarios that I have seen in the past where the module crashes out during enabling, but the module still says that it activated successfully.
Did you enable via command line or the Admin interface. If admin interface, did you get the screen after pressing enable offering to activate the feature?
I would start by checking the log for when you activate the module. It may provide you access to an error message that the orchard UI is hiding.

Distributing Eclipse plugin with dependencies

I recently wrote an Eclipse plugin, and I'm trying to get some coworkers to install it for testing.
As far as I can tell, dropping the .jar into the dropins folder in Eclipse is supposed to install it, but it seems to not be working on any installation of Eclipse but the one I developed on. This seems to be a problem with the dependencies not being installed.
I thought that the dropins folder was supposed to automatically calculate and install dependencies, but perhaps I'm wrong. If so, how can I distribute it without having everybody install each dependency separately?
I'd recommend against using the dropins folder. It is unreliable as you have seen. Instead, I'd recommend that you export your plugin as an update site.
So:
Create a feature for your plugin. This is a lot simpler than it sounds. See Lars Vogel's tutorial: http://www.vogella.de/articles/EclipseFeatureProject/article.html
File -> Export... -> Deployable Features.
In the options, section, select "Package as individual jar files..." (see screenshot)
Tweak other things as required
Finish
Now, you have an update site that you can zip up, or put on a web server somewhere. Your colleagues can add that update site just like any other. To install, make sure that they also have all of the dependencies available from other update sites and that they have "Contact all update sites..." checked.
The nice thing about this is that if you place your plugins on a web server somewhere, and you replace it with a new versions, people will be able to update transparently.