kalastaja:
That was sort of understood - I just wondered where I should place the module in the structure so that ZenCart finds it!?
And might the module do some uploading!?
What about the bugs - can I do something?
The general structure/placement of payment modules is two fold, one directory for the operation (includes/modules/payment) and one directory for language (sorry, but I usually have to go find the specific language directory path for any of the language related aspects, but a similar path in the includes/languages directory.)
It is not so much a "new" module discovery, but everytime you open modules->payment section, all of the files ending in .php are loaded from those two directories... When a module file is found, an equivalent language file is expected, if not found then usually. An error message is logged and the partial blank screen or warning is posted...
In a sense there are levels to the code. Dr. Bytesuggested how to remove the database information about the module, this causes the module to sort of perform the first level as I have chosen to call it here.. Identify if the plugin is installed, if not installed then continue processing the other payment modules for display/payment.. That is if the module follows the expected general rules for development which based on the above discussion it at least is written properly from that perspective. Otherwise the suggestion would have included file removal.
As any user, you could work to rewrite/remove the bugs that Dr. Byte identified, though that may be a duplication of effort, or maybe not. Communication certainly is important in that regards, but I might suggest being ready to make a donation to the ZC team for the rewrite that may be coming from them/someone involved with them.
Btw, a lot of the questions about how/where things come from/get done etc, would be answered by starting to look at the code itself and researching what is not yet understood... In this case, a good place to start looking I think is in admin/modules.php. Then follow the bouncing ball and the notes in the file(s). Also helps to cross reference the output source code (choosing to view source code when the web-page is open in the browser.)
I still go with some of the previous, great to dig in sometimes, but also need to know when to put on the brakes and move on or accept that not fully knowing or understanding something is okay especially based on the source. Errors may happen, but they tend to still happen securely. :) point being, use your time wisely/appropriately. You're running a business, be sure that what you do supports that.
