Module development and code questions

Hi, for the last few months I have been looking for a CMS for a new website I want to make, its for a flower export company.

Now I have installed and tried about 7 differant ones so far but running into Drupal seems I have found what I need :)

Let me explain what I need this website to do for me, it has to be pretty simple, but needs away to let customers place there order for flowers online, they get invoiced so no need for a payment thingy.

I have made a modification to the LDAP_integration Module that for users to login using "Friendly Names", nicknames and such. The reasoning behind this is that the CN of a user in an LDAP database can sometimes be fairly cumbersome as most of us know, I for example would be Jeremy G. Devoid on the server I am connecting to. To make sign-ins easier I have created a "Friendly Name Lookup" additon to the LDAP module, it is optional and the admin can turn it on or off. The look up is based on key fields, on the LDAP server, that he admin desires, such as the cn and nickname fields.

Hallo Drupal Communtiy.

Im write a book module with extra fields and on site of the book have 1 or more nodes.
I need help to view more then 1 nodes on a page.
Not a blocklist im need a nodelist with the Body and the Buttons to edit and del,
with the same function range on view.

I hope it understand me!

Sorry for my English, thanks.

DOCI

We're releasing our modifications to the Letter to the Editor tool originally created by Downhill Battle Labs. Changes to the module include several functions which make management easier for the admin of the Letter to the Editor, as well as making the module compatible w/ Drupal's db abstraction layer. Using the Letter to the Editor tool as an additional module to Drupal, the admin can easily assign talking points to appear along-side the letter form, is given the ability to change text to explain the mission of the campaign, the addition of a graphical and numeric display of the number of letters sent, the addition of counting to which individual papers letters have been sent, and finally the ability to use a slightly modified version of the contact directory module to edit records in the paper database via the website interface.

A lot of work remains. First, the module is not very Drupal or CivicSpace-ish. Development standards are not met – these need to be met to make continued development easier. There are definite design limitations – we designed this version to work on a page within Drupal that does not use any blocks (no sidebars) to take advantage of horizontal space. Additionally, an external php mailer is used where Drupal’s built in capacity to send emails should probably be harnessed. Lastly, the tool only lets you run one campaign. The need to run muliple campaigns with a full feature tool set exists, but it needs to be spec-ed and coded. Anyone interested?

I have posted a question few day ago but i have no answer and a tried again

I have installed tinymce and select advanced theme but i cannot see the plugin button.
The file example3.htm include full advanced theme and this is thr code:
....................................................
tinyMCE.init({
mode : "textareas",
theme : "advanced",
plugins : "table,save,advhr,advimage,advlink,emotions,iespell,insertdatetime,preview,zoom,flash,searchreplace,print,contextmenu",
theme_advanced_buttons1_add_before : "save,separator",
theme_advanced_buttons1_add : "fontselect,fontsizeselect",
theme_advanced_buttons2_add : "separator,insertdate,inserttime,preview,zoom,separator,forecolor,backcolor",
theme_advanced_buttons2_add_before: "cut,copy,paste,separator,search,replace,separator",
theme_advanced_buttons3_add_before : "tablecontrols,separator",
theme_advanced_buttons3_add : "emotions,iespell,flash,advhr,separator,print",
theme_advanced_toolbar_location : "top",
theme_advanced_toolbar_align : "left",
theme_advanced_path_location : "bottom",
plugin_insertdate_dateFormat : "%Y-%m-%d",
plugin_insertdate_timeFormat : "%H:%M:%S",
extended_valid_elements : "a[name|href|target|title|onclick],img[class|src|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name],hr[class|width|size|noshade],font[face|size|color|style],span[class|align|style]",
external_link_list_url : "example_data/example_link_list.js",

... That took a while to find!

OK, some lessons include:

Avoid and declare Globals

Occasionally some of the libraries set global variables, some of with are then used by other libraries. This is of course to be avoided, doubly so now we are in a Drupal context where there's lots of overhead going on.
ALL GLOBALS MUST BE DECLARED EXPLICITLY at the top of the file (as sometimes we are running inside an eval() and file scope variables may not be global scope.

ALL GLOBALS SHOULD USE A NAMESPACE to avoid possible conflict with the environment.
global $param;
should be
global $MYMODULE_param;
... everywhere.

Beware of reserved parameters

You should not declare form parameters called:

• q
• destination
• edit

unless you are intentionally messing with the Drupal functioning.
There may be more on this list - even modules may add some - can someone publish them?