| Age | Commit message (Collapse) | Author |
|
|
|
Install: <module>_installer::install() is called, any necessary tables
are created.
Activate: <module>_installer::activate() is called. Module
controllers are routable, helpers are accessible, etc. The module is
in use.
Deactivate: <module>_installer::deactivate() is called. Module code
is not accessible or routable. Module is *not* in use, but its tables
are still around.
Uninstall: <module>_installer::uninstall() is called. Module is
completely removed from the database.
Admin > Modules will install and activate modules, but will only
deactivate (will NOT uninstall modules).
|
|
|
|
anything (and was causing an error).
|
|
|
|
recaptcha private key properly anymore, but it's more intuitive to
configure in the admin UI.
|
|
opposed to a direct call.
|
|
Form_Recaptcha class derived from Form_Input that can be added to any class that requires Recaptcha verfication.
|
|
screen just has the public and private keys and if the public key is
provided a recaptcha box shows up which is used to validate the public
private key pair.
|
|
adminstrator. The forms are presented as a checklist, I would have
preferred a selection list, but Forge doesn't have one. The generated
html to contain the recaptcha challenge is defined as <ul> as that was
the only way to force itto line up.
|
|
than the originating module to provide additional functionality to the form.
|
|
how to integrate it with the other module forms.
|