Closed (won't fix)
Project:
Filter Default
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
25 Aug 2007 at 20:21 UTC
Updated:
3 Feb 2013 at 17:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
sunFixed a syntax error.
Comment #2
bjaspan commentedI just ported this to D5 and created a D5 development release. I've updated the code style to my current standards for contrib modules. Please re-submit any additional problems as a new issue. Thanks!
Comment #3
sunHow comes that I do not see a DRUPAL-5 branch?
Attached is a new patch against HEAD. Already thoroughly tested on two productive sites.
Comment #4
john bickar commentedThis patch does not apply cleanly for me on patching filter_default.info. I get the following filter_default.info.rej file:
It does apply cleanly on filter_default.module. I applied filter_default_3.patch directly to the 5.x-1.x-dev version; should I have applied the other patches in succession first?
Comment #5
sunAttached patch cleans the coding-style of filter_default adhering to Drupal Coding Standards, and fixes some minor bugs in current HEAD.
Btw: There is still no DRUPAL-5 branch visible in CVS. I have no clue, how you managed to release a development snapshot for 5.x, but for an official release, we need to branch filter_default to DRUPAL-5 and create a DRUPAL-5--1-0 tag afterwards.
These are the included fixes:
admin/settings/filters/defaultshould display a proper page title.!list_linkwould be the proper placeholder for HTML markup like hyperlinks, however, the stringlist tabwould not be translatable, and thus, only the URL is passed tot()as replacement now.filter_default_admin_defaults_form_validate()for better readability. This time, I additionally included some inline comments for better understanding of the rather complex logic (thoroughly tested)._filter_default_form_alter_filters()needs to additionally check if there are any children to iterate over. I already added this check in my last patch, since I encountered an error message somewhere (unfortunately I do not remember anymore, where)._filter_default_is_new().Comment #6
idflorin commented#5 applied , it's huge, thanks.
Comment #7
sunBarry?
Comment #8
chellman commentedBarry has passed the torch. I've been working on issues, and just rolled a 1.0 release of this module to get the ball rolling, but I'll look at these next.
Comment #9
pomliane commentedThis version of Filter Default is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.