I know how to install a component together with a plugin. It's all about manipulating the xml like, let's say, the Artof User component.
What I want to know is if this is also applicable to module. Like I can install a component together with a module.
Starting from J1.6, you can create a Package. See http://docs.joomla.org/Package
Related
I would like to override a non-core module of PHPFox,so basically, it is an installed 3rd party application developed by PHPFox themeselves. Here is the file I would like to override.
PF.Site/Apps/core-comments/views/block/comment.html.php
Anyway, I was able to override core modules in my theme following the naming convention from their documentation like the Feeds Module.
Did you mean you'd like to override above file with the file in your module?
In the library, at step render template file, there is a hook. You can use this hook in your module and change above the to the file you want.
I have create one field in stock.quant.package model.
tracking_ref=fields.Char("Tracking Ref")
This field is used in two separate modules and I am not able to give module dependency because both are separate modules.
It may be possible that both modules are installed in same database or it may
be possible that in some database only one module is installed.
Due to that reason i have create same field & view in both modules.
But now issue is that if both modules are installed then field is
available two times in the form view.
Is there any possibility that if we install both modules then field will visible only one time in form view.
I am not sure it is the best solution. Just try:
Create a new Module, say module_common
Put all common fields and functions in new module module_common
Make this module dependent of another two modules.
Ex: module_a depends module_common and module_common depends module_common.
Hope it will resolve your problem.
I'm new to phpfox, I'm developing a payment module. Can anyone help me with the payment module? I have a zaakpay payment integration kit and i have all the necessary inputs. How should i need to integrate? Should need to do like paypal and 2checkout(they have written all the source code in library files) or should need to develop a new module ? Thanks in advance
When developing for PhpFox it is best to follow their conventions. When we have a library that needs to be added we add it to the library section:
/include/library/
So for your project it would be something like this:
/include/library/zaakpay
Than you will want to use the admincp to create a product first and then a module for your product.
http://example.com/admincp/product/add/
http://example.com/admincp/module/add/
All your code for your module will live in the module directory, I use payment as an example.
/module/payment
When you are developing your module you will need to refer to the other modules for examples of class names and file structure. It is a very strict convention.
PhpFox module settings are stored in the database, so it is very important to setup the modules correctly using the admincp. This will allow you to export your product, and have all the settings exported as well. You export your product from the admincp.
http://example.com/admincp/product/
The settings for your module will be in an xml file here:
/include/xml
The xml file only exists in the exported package, and it provides you the ability to install your product on another site. For example if you develop the code locally and want to move it to the production site.
When I installed the module that I developed and in the module manager screen of the backend I can see the title like this.
Module Manager: Module mod_examplemodule
So I want to change it into something like this. Module Manager: Module Example Module
I have developed few Joomla modules but so far I didn't realize how to do this.
Your help on this would really appreciated.
Thank you.
Im using Joomla 2.5.8. I have just added the screen shot. Perhaps it would be more helpful.
In my modules I use:
<name>Module Title</name>
<description>MOD_MODULE_TITLE_XML_DESCRIPTION</description>
I then add an entry in the language file for the description. This normally covers my needs
I have solved this:
You can change name tag in mod_examplemodule.xml file and install again
OR
If you have database access then in [prefix]_modules table find the record of this module and change the name field as per your requirement
I'm using Joomla 2.5.3.
I have this module that incorporates with authentication. For some reasons I want this module to be duplicated, so I save it as another copy.
Now, as its Module Type is same as the original one,say Auth, how do I customize the files of the copied module?
There is no folder for the copied module inside modules. Only the original one is there.
Thanks.
It depends on what you want to modify and how the module was created.
If the module was created using the MVC design pattern you want to modify ONLY the view (layout, html, css, js), then you'll need to check if the module supports multiple views/layouts or override the layout and create a view for each module depending on its Id. http://www.minitek.gr/tutorials/joomla-16-tutorials/item/21-how-to-create-a-new-custom-module-in-joomla-16.html
If the module wasn't created using the MVC design pattern, you could duplicate the module folder with another name and modify the name of the module in the xml, however it also depends on what the module does (does it write anything to the db?).
Maybe the easiest (probably not the best), would be modifying the current module depending on the module id. Check this out: http://docs.joomla.org/JModuleHelper/getModule
Think of a module as being similar to a class. You have one instance of the module created already. When you either clone the current instance or create a new instance there is still only one underlying set of files.
Each instance of the module contains its own individual settings so they should not clash with each other.
I can't think of any reason why you would need to customise the underlying files. If you do find a need then your best bet is to copy all of the files from the original module and use them as a base to build your own - entirely new - module, with a new name, new class names, etc.