Here are some modules, themes, and other tools I've developed in the course of supporting Drupal on several sites.
These are generally not polished (and in particular, not documented) to official Drupal contrib standards. Though I tried to avoid it, it's possible that some also depend on patches not (yet?) in the core.
All are provided as-is, and absolutely no (unpaid) support whatsoever will be provided.
Modules
- copyright
Adds a copyright notice (automatically using the current year) at the bottom of each page.
- extralinks
Optionally adds (a) an "edit" link to teaser displays (like Drupal 4.4), and (b) "next", "previous", and "latest" links to node pages, based on the front page display order.
- ii404
Perform a search when a page is not found. Derived from i404.module by goekker.
- insertions
Provides XML-style tags to insert information (e.g. title, teaser, body, link list, etc.) about nodes and comments. Similar in spirit to the Attached node contrib module.
- linebreak
An extension to the line break filter. Converts line breaks into HTML, but only if the user has not supplied explicit <p>, <div>, or <br> tags.
- minoredit
Allows editors to mark node edits as 'minor', so that the content does not appear to be 'new' in the tracker.
- nlist
An adjunct to insertions.module, this lists the nodes in a taxonomy in <n> form, so that the editor can copy them to easily build custom article lists.
- noteaser
Allows the admin to suppress teasers for particular node types. See http://drupal.org/node/12667.
- replace
A filter that provides two functions: (a) Turn '@' characters into images, to discourage email address harvesting; (b) turn the site's name into a link.
- results
Suppress the author field in search results, for 'editorially' unsigned collaborative sites.
- shuffler
Present a "random" selection of articles in a sidebar block. Nodes are selected and weighted by taxonomy. Reasonably efficient, since the list of links is generated by a cron hook rather than on every page load.
- teaserless
Handle old database nodes with no/empty teaser field.
- tracking
Similar to the core tracker.module, but primarily focussed on providing registered users with personalized lists of unread content.
PHP pages
- fc
Flushes the Drupal cache when loaded. Useful while working on code that uses the cache.
- node
Redirect old node URLs. Better than the standard Apache redirect because it handles links to comments.
- updatecommentcount
Repairs the node_comment_statistics table after an upgrade to 4.5.0. Probably won't be necessary for 4.5.1; see http://drupal.org/node/11366
Theme Preprocessor
This allows one to write themes in a 'template' style, but runs at theme-install time for maximum efficiency (that is, it produces a pure PHP theme, and is not itself present as part of a Drupal installation). It provides inclusions, conditionals, macros, etc.; its main design goal was to allow one to easily share code/design between themes.
It requires a command-line-accessible PHP; it is written in PHP because that language will be familiar to people working on Drupal.
Comments
Why not put them in contributed modules?
Why not put them in contributed module right here on this site?
Apply for a CVS account, and add them.
If you do, then perhaps you want to update existing modules that you based some of those on, to avoid duplication of modules.
You have a lot of good stuff there, and they deserve to be advertised for everyone who visits here.
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
Eventually...
I might do that eventually, but at present I don't have time to convert them to Drupal standards, document them, and so on. A few of them date from 4.2, and I still hadn't gotten around to it -- so I thought just making them available raw would be better than nothing. I wouldn't complain if someone wanted to 'adopt' any of them.
Applause and whistles for KPS
This is the kind of thing I wish there was more of around the Drupal community. As a developer I really appreciate when someone shares their hacked code. Others learn from it and maybe someone else has the time and inclination to turn it into a polished effort.
Thanks!
---------------------------
info for Drupal installation
__________________________
Carl McDade
Information Technology Consult
Team Macromedia
www.hivemindz.com
nice one dude
HEY!
those modules are great. Masssive thanks for sharing.
I have only tried out the tracking.module...have been scratching my head for a few days trying to work outhow to filter recent posts by type...and your module has given me some insight into how I could possibly do it.
Quick bit of feedback re: tracking .module
Your tracking.module worked fine on drupal 4.5 with one exception - it didn't show the author names in the result list. Only a minor thing, but, I thought I would mention it.
Jason
Currently in Switzerland working as an Application Developer with UBS Investment Bank...using Drupal 7 and lots of swiss chocolate
Right
Yeah, I'll add a cautionary note about things like that. That particular module was written for the site these are hosted on, which is collaboratively written using the "editorial we", so the identity of the logged-in user who posted an item is deliberately not displayed. Maybe the next version will make that an option.
contribute, please!
Allthough, indeed you might not "have the time" to contribute, I think you did wrong choosing to distribute them from your own website.
This way efforts cannot be controlled and centralised, people will only learn obout the existence by googling or searching the folders. And we cannot rteack support and bugs whne all is decentralised.
So please, please keep yopur efforts centralised. And if they do not apply to the coding standard then keep them in your CVS sandbox, or do not release them.
I beleive these are very good modules, but I beleive its a very bad thing when you decentralise the efforts! We should never, ever become a *nuke alike community.
[Ber | Drupal Services webschuur.com]
I have to disagree. If
I have to disagree. If somebody already knows that he does't have the time to support/maintain his modules then he is right by not putting them into the contrib cvs. We already have enougn not maintained modules there. Also, a lot of the modules offered seem to be very specific in use and might not appeal to a wider audience.
--
If you have troubles with a particular contrib project, please consider to file a support request. Thanks.
--
Drupal services
My Drupal services
I have to disagree again
Indeed we have a maintainance problem.
And we also have gfar too much specific modules. But not contibuting them is a clear waste of effort. we have near to 11000 articles on Drupal.org about all sorts of stuff. if one of them holds a link to a very usefull module it /will/ get lost. Thats the nature of the web.
So, killes, if you address problems of maintainance and of importance of modules, those are valid issues. And we shoud tackle those problems, rather then "hacking" a way around them by hosting modules elsewhere. For a hack it is.
We need a solution here, on drupal.org, in project.module, to solve the issues of abandoned modules, and of modules that are site specific. The tools are at hand, taxonomy and user hooks, only the good ideas and code lack still.
So I conclude again: Please, please do not scatter drupal. For that will be the beginning of the end of it (it killed the *nukes, for the moment that project scattered is considered the moment the code became unmaintainable and thuis dirty and buggy)
[Ber | Drupal Services webschuur.com]
This is more a developer issue than a user one
The problem with trying to centralize all the modules and code contributions in one place is that there are rules. As long as there is an attempt to make people go by those rules then you go against what developers and coders are striving for which is the implemetation of ideas in code. Not everyone wants to be a part of a concerted effort and they should be allowed to exchange ideas and code without being part of any group effort. This is the point of community development and a basic of open source.
Macromedia has this same problem when it comes to Dreamweaver and Homesite extensions. The solution is to just let go of the hacks and specific code and take items that qualify into the exchange. The other items get posted to sites that cater to them.
Now when it comes to distributing user software then the rules should be applied very strictly. This avoids support and help issues that arise out of incomplete or dropped projects.
So the Drupal add-on section should be just the way it is but there should be no effort to control the hackers and fixers that just want to have fun and profit.
---------------------------
info for Drupal installation
__________________________
Carl McDade
Information Technology Consult
Team Macromedia
www.hivemindz.com
thank you kps...
Thanks for sharing all your work. All your effort is much appreciated.
Thanks again,
larry
--There are no Kangaroos in Austria--
Update for 4.6
The modules and patches have now been updated for Drupal 4.6.0.
New or significantly revised modules:
A captcha plug-in that provides a simple arithmetic question as the challenge. Derived from an early version of the captcha module.
Allows editors to promote an unpublished forum item to a story.
From 4.6, this module allows the administrator to configure, for each node type, what information will be displayed in search results.
An input filter to protect email addresses from automated harvesting. This filter converts email addresses (either in mailto: links or in text) into links to an internal URL. Access to the decoded email address may be restricted by role and/or guarded with a captcha.
This module provides an alternate report of external referrers, parsing search engine referrers and excluding unwanted referrers.
This is a plug-in for the spam module, which notifies users when their content appears to be spam. (The hope is that they will then be less likely to wonder why their content does not appear, and resubmit it repeatedly.)
Really nice
Can I convince you this time to get a CVS account and commit them to the repository?
They will then be available for download and have project pages.
You can state that you will not support them (and that is somewhat acceptable in the contrib area), but at least people looking for modules will find them in the one stop shopping that is Drupal.org.
Please?
--
Consulting: 2bits.com
Personal: Baheyeldin.com
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
Contribbing saves your time, kps
At the long range, you will not only waste time but save time by contributing the modules to the CVS, since other people will help with modules maintenance.
Amnon
-
sakeret.com | hitech-dolphin.com | small-business-web-hosting-strategies.com | levavie.com
Any upgrade to D6
Any upgrade to D6
Dreamweaver extension