| Age | Commit message (Collapse) | Author |
|---|
|
replace with a type field with one of two values (head and block). We need to
do this to determine what fields go in the rss block so we can ignore the
definitions that are related to the page head when creating the rss block that
goes into the sidebar.
|
|
modules that are supplying the feed. The rss controller becomes a router.
In this change the comment and updates fields are distributed.
|
|
api.
|
|
provide the part of the url (the suffix) that they are interested in and the
rss module will format the rest of the url.
|
|
allow modules to contribute rss feed links to the rss sidebar block.
Ticket #388.
|
|
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).
|
|
|
|
It doesn't fit in with the others and as Jakob points out, the scroll
wheel on the mouse is perfectly sufficient. I'll leave the icon around, though.
|
|
|
|
|
|
|
|
|
|
prefix handling.
|
|
mirror the drupal pattern of using braces {}.
|
|
tag, search, comment and notification modules (Ticket #68)
|
|
message below it.
|
|
|
|
button is clicked. Used jQuery UI Effect to .highlight() to bring attention to newly added comments. Also added a named anchor to our block library to allow direct linking/scrolling to those blocks on the page.
|
|
opposed to a direct call.
|
|
Form_Recaptcha class derived from Form_Input that can be added to any class that requires Recaptcha verfication.
|
|
|
|
than the originating module to provide additional functionality to the form.
|
|
the controller on successful add.
|
|
wide, not just in the dashboard.
|
|
for us to rename the dashboard helper to be a block helper since
sidebar blocks are not just in the dashboard.
|
|
item and comment data. Whew!
It's not pretty yet. And you have to manually update the index
currently in admin/maintenance. But it works.
|
|
Fire off the appropriate item_related_update events as appropriate.
|
|
File_Structure_Test to make sure we don't regress.
According to the PHP docs, the "public" keyword is implied on static
functions, so remove it. Also, require private static functions to
start with an _.
http://php.net/manual/en/language.oop5.visibility.php
|
|
module installers don't have to know the grotty details of how it works.
|
|
* Refactor blocks so that they have a separate id vs css_id. This way
we can have a unique identifier for each visual block.
* Store blocks with a random id as their unique identifier
* Add Admin_Dashboard::remove_block() and modify
themes/admin_default/views/block.html.php to call it when you click the
remove box.
|
|
OLD:
$form->submit("Foo") --> <input type="submit" value="Foo">
New:
$form->submit("foo_button")->("Foo") --> <input type="submit" name="foo_button" value="Foo">
Mostly we don't care what the button is so we leave the name blank.
|
|
both the sidebar and the center content area from a dropdown at the
top of the dashboard sidebar.
|
|
And truncate strings before passing them to MySQL.
|
|
comment. Get rid of comment::update tests since, comment::update is
gone.
Found a bug in comment::create() in the process.. yay unit tests!
|
|
|
|
user modules.
* Don't delete vars when we delete a module. This makes
reinstalling a module a lot easier.
* Add user::lookup() as the preferred way to load a user, so that
other modules don't delve into the user module (that'd be a
problem when we swap out user modules)
* Notify site admins if Akismet is not fully configured
* Bundle all server variables into the comment so that if/when we
re-check the comment, we are not using the server info from the
site admin's request.
* Update Akismet to grab request context data from the comment
* Pre-seed comment fields if we have a logged in user. Update
comment::create() API to clarify it for this.
* Delete comment::update(), that's a controller function.
* Add url to User_Model
* Add author_name() author_email() and author_url() to
Comment_Model. It'll return the appropriate values depending
on whether the comment was left by a logged in user or a guest.
* Use resetForm() instead of clearForm() when we reload the
comment form after ajax submit, this way we preserve the
pre-seeded values.
* In the user profile page, ignore blank passwords.
|
|
- And refactor printf to our string interpolation / pluralization syntax
- Also, a slight change to the translations_incomings table, using binary(16) instead of char(32) as message key.
|
|
1) Akismet now detects when we change a comment's published state and submits
info back to akismet.com as appropriate
2) We now show 4 different queues (all / approved / unapproved / spam) and let you
move messages between the queues
3) We track and display "spam caught" stats.
4) You can delete comments entirely.
|
|
(approved, unapproved, spam).
|
|
fails set the comment
state to unpublished.
|
|
"view comments" link to the comment menu helper.
|
|
Rename menu "General Settings" -> "Settings"
Rename "Comments Moderation" -> "Comments"
Move "Content" -> "Configure Spam Filtering" -> "Settings" -> "Spam Filtering"
|
|
2) Replaced it with a string field (state) which contains the state of the comment. i.e. published, unpublished, spam. Unsure if we want to create constants in comments.php to standardize the valid values... thoughts?
3) synchronized the spamfilter and comment unit tests with the current functionality
|
|
the appropriate form content. Add a callback so if the driver changes in the driver selection dropdown, then the api form fields are updated with the new form fields for that driver
|
|
any spam services. But you can go into the admin screen and choose the driver and set the api key.
|
|
comment model)
|
|
bytes on some systems.
|
|
|
|
the spam_filter module
|
|
two columns to the comment table. The url of the author's web site(default null) and a flag to indicate that the comment is visible (default true).
The comment block has changed to only display comments that are visible.
And there is code added to call the spam_filter helper if the spam_filter module is installed.
|
