Module development and code questions

Hiya Guys,

I miss the simplicity of the old inline.module that allowed users to upload and insert images in the blogs/pages simply and easily. the nostalgic words "those were the days" doesn't exactly spring to mind..drupal has never been more stable, but, I was just thinking if it would be a good/bad idea to store inline images in the drupal SQL table rather than as a graphic....for two reasons..

a) to make it easier to back up the site in one simple step..i.e. by backing up your sql, you're also backing up the inline graphics.

I have been trying for weeks to get blogapi.module to post correct HTML and special characters via w.blogger. The problem is that ' becomes '' and then gets converted to its entity equivalent when editing and reposting through the desktop client. HTML does not get posted but shows as raw entity values like &nbsp and >br&lt. From their it gets worse because ampersands an colons get converted with each repost also. I have look at both the blogapi.module and the xmlrpc.inc and cannot find anything wrong in the way they work and no errors are produced.

I'm considering writing a module to track search engine referrals, specifically the keywords used in the search engine query that resulted in the referral. Has anyone written code for Drupal to extract the query strings and maintain counts of the keywords resulting in queries?

Radi

I would like to allow some users to have permission to 'administer users', but would like to make it impossible for them to edit the primary administrator account (uid 1).

I would also like to restrict these users so that they have access to the 'configure' tab, but only to adjust the 'settings' (and not access rules, permissions, profiles, or roles)

I hope this makes sense - any ideas would be appreciated. I have tried to modify the user.module without any success.
:)

Greetings All,

This is Ankur Rishi here at CivicSpace Labs (http://www.civicspacelabs.org). I just wanted to announce that we are in the process of building a module for tying locative information to nodes (address.module). The plan is to implement it on top of an API in an include file also part of this project (address.inc).

For details, you can see an implementation plan: http://www.civicspacelabs.org/book/view/5999

For a while I've been wanting a feature similar to LiveJournal's "Listening to" feature to make Drupal an even better blogging platform for nerds like me. I finally finished a thrown together module that I call the "currently" module, because you can put what you're currently listening, reading, or watching in your blog. It integrates with the Amazon Search module to enable searching and showing cover art.