This forum is for module development and code related questions, not general module support. For general support, use the Post installation forum.

Extending functionality of core modules

I'm trying to modify the "weblink" module so that users can add more iinformation about a link that they submit. However, I'm having trouble as to which table to store the additoinal link information: the node table or weblink table?

Anyone know?

RS

HTMLAREA: Added Permission by Role

I added a patch to allow HTMLarea to limit its use by role:
http://drupal.org/node/17819

This poses several questions for me as I looked at the module.

1) It looks like there is another permission_hook in there (before mine) called "upload images" but it does not look like it does anything. Should this be removed?

2) I wanted to make a new input filter called "Rich Text Editor" which when selected HTML area would appear. How do I 1st identify what mode they have selected.. $node->filter does not appear to be working for me; this line looks promising but I cannot get it to do anything:
if ($node->format == 2) { $htmlarea_codeview = true; }

3) When PHP input filter is selected HTMLarea is turned off by default? Where is this code located? Is it in another higher function? I do not see anything out there on it.

4) I wanted to add permissions for each filter, something like enable imagemanager, enable insertfile... I could live with a hard coded solution, but a loop over the installed and active plugins might make more sense.

5) Last thing: When looking at the database it looks like permissions assigned to each role is simple put in a comma separated list by the name of the permission granted. This seems to me that module developers could quickly step on each others toes, if they call a permission the same. Is there a guideline for naming permissions like "HTMLAREA: Upload Images" and "HTMLAREA: Use HTMLarea" thus making them all unique enough from other modules. Any thoughts on this?

Chapter levels screwed up in the printer-friendly output of books module

When I look at the printer friendly version of the Admin Guide, the chapter levels are all screwed up.

Specifically, it looks like all levels of subchapters (eg. h2, h3, etc) get displayed as H1 level chapters. It makes the guide very confusing to read.

From talking to people on the documentation mailing list, it sounds like this is a known bug with the book module.

Integration with Lightbox Photo

I was wondering if it is possible to integrate software called lightbox photo (http://www.lightboxphoto.com) into the drupal system?

It is a great soft for selling photos either by print or by download.

Would be great

Thanks
Steve

Can't branch module to DRUPAL-4-5

Being a newbie at CVS, I'm having trouble with branching/tagging my module (amazon_items). It was released as 4.5.0 code, but I have since made minor bugfixes that I want to be reflected on the Drupal website under the 4.5 modules tab. Do I need to commit my changes to CVS, and then branch or tag the code to be DRUPAL-4-5, or does this somehow happen automagically? I read this post (http://drupal.org/node/11663) which contains the same error message I'm getting, but it doesn't seem like exactly the same issue.

How much "optional" stuff is too much?

Module developers,

How many features never see the light of day because they might be too narrowly focused for general use? How many "smart defaults" do you write into your modules that could be tweaked as an admin setting? I tend to want to put way too much into a module's admin settings, rendering it very difficult to use for regular users to learn. Most of the time, "smart defaults" would work just fine, but I'm prone to be a control freak and want to adjust everything from the admin settings (and thus want everything configurable from there).

Pages

Subscribe with RSS Subscribe to RSS - Module development and code questions