Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
results of the $theme->css() and $theme->script() calls. This handles
the case where combining scripts/css returns HTML instead of putting
it in the queue for combination. Fixes #1611.
|
|
uses to add a captcha to the end of the first group in the form. If
there are no groups, it adds the captcha at the end of the form.
Updated user_profile and comment forms to use it.
|
|
|
|
|
|
|
|
user in messages or pages.
Partial fix for ticket #889 and a fix for #931.
|
|
event. For the first attempt replace the comment_add_form and item_add_form events."
This reverts commit 809e738536b6639bb42ecae8eb1e183543fed93c.
|
|
|
|
the bottom of the user registration form in the register module.
|
|
|
|
so the recaptcha doesn't looking... interesting.
|
|
the first attempt replace the comment_add_form and item_add_form events.
|
|
group that the recaptch element should be attached to instead of the whole form. This allows the recaptch event to have no knowledge of the containing form."
Revert "Generalize the adding of the recaptcha form by changing the name of the event to recaptch_add. This prevents us from having to keep modifying the recaptch module anytime we add a form that requires recaptcha."
This reverts commits e45ea9359d6cb603be0bc28376d92883aa8d7c7e and bfafef95e8090b66f3322f73e532056b10ca116a.
|
|
the recaptch element should be attached to instead of the whole form. This allows the recaptch event to have no knowledge of the containing form.
|
|
event to recaptch_add. This prevents us from having to keep modifying the recaptch module anytime we add a form that requires recaptcha.
|
|
shared images from wind to lib. Deleted unused images in the admin_wind. This will likely break a few ajax features.
|
|
install() function if all you're going to do is to set the version of
the module from module.info into the database. This means that for some
simple modules, you don't need an install.php file at all.
|
|
|
|
views.
|
|
Adding SafeString::of_safe_html() calls where urls are passed as parameters to t() and t2().
|
|
This is the first step towards having a simple, lightweight and
unified API for module interaction.
|
|
|
|
Add xxx_installer::upgrade($version) method so that upgrade stanzas
are separate from install stanzas. In the old code, to do an upgrade
meant that you had to re-evolve everything from the initial install
because we'd step through each version's changes. But what we really
want is for the initial install to start off in the perfect initial
state, and the upgrades to do the work behind the scenes. So now the
install() function gets things set up properly the first time, and the
upgrade() function does any work to catch you up to the latest code.
See gallery_installer.php for a good example.
|
|
|
|
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.
|