Deprecated - Usability feedback

Hi folks,
I am still trying to create a site using drupal, but find it really hard, seems to me that more documentation should be available.

I am building a providers yellow pages site, I have a table of all the countries(including the ISO names and codes) and a list of providers, each provider has various info such as address, contacts, offered services and so on. Each provider may be present in a number of countries.

As I understand I should use the taxonomy categories system. So I have countries vocabulary that has "countries" as a parent term, and each specific country is a child term ("USA", "Germany", "Argentina").
The second vocabulary is the providers vocabulary where "providers" is the parent, and specific providers are the children "ERT ", "Easynet","Shiny" and so on. Now I need specific pages(nodes) for every country that lists all the present providers under this country, and specific provider pages.

At first I need to create a node for every country, how do I do it? It should be a sort of a script that runs ones and creates a page for every country I have in the countries pages, tried to look at the node.module but this node_add, node_confirm, node_submit are kind of confusing. Later when I or any user add providers to the system a new node/page should be added to the system, with taxonomy tags to attach it to specific countries.

I am kind of lost with this implementation, anyone could help? I really need it done... I can pay some money if someone is willing to develop parts of this system.

I'm looking for feedback on a new taxonomy browsing module I'm working on... this could easily be used as an index of sorts for a site, but we plan to use it in a couple administrative areas of our store. The idea is that you're browsing a vocabulary like it's a file tree. So, there are two select boxes, one populated with the terms of a vocabulary and the other with the child nodes for those terms. You can also search for nodes, but this isn't vocabulary specific at the moment. There are only two actions right now, select (to set the value of another element on the page to the nid of the selected node) and view (to browse to the selected node). The search and action components are configurable, and I'm working on a good solution to allow a developer to create his own callback function for action buttons.

This code relies on jQuery and uses its AJAX methods $.post() and .load() to display the appropriate content in the node select box. I would love to get some ideas for improvement, expected possible uses that I might tailor the module specifically to support, and how to best display the widget. Right now I have defined on the test page a div that gets loaded with the content when you click some buttons... So the presentation is very basic, but it is meant to be worked on. ; ) Also, it doesn't seem to render properly in IE... some weirdness in the table.

Anyways, please check it out and offer some feedback here or there. Thanks!

Hi!
I am building a new site, and have chosen drupal as the cms platform.

I want to use drupal as good as possible, and not just insert my php scripts wherever enable.

My site is a sort of providers yellow pages. I have a list of all countries, when the user choses a country, a list of all available providers is available, with a brief description for each.

When a provider is chosen, a specific provider page is open. With various information available, such as address and contact details, offered services, technology that is in use and so on.

Is there a module or some way of efficiently uploading several stories at a time?
i.e. If I have just written 100 content pieces, do I have to enter each one of them separately?

I am just testing the cvs version of drupal. One thing I noticed that on the module page, we have divided it into two pages.

1. Core - optional
2. Core - required

Core - required cannot be disabled by the user. Why would we then need to display something that just takes up space.
Would it not be better just to remove that from the page, and just list Core - optional?

Warren Brian Noronha

From an end-user perspective, I would like Drupal to remember which page sections I have (not) collapsed, so that the page layout remains the same after I, for example save the settings.

Currently, after having saved a settings page or after having browsed from and to a settings page, all page sections are intracted again. I would like to have them the way the are. Is it possible to store this information in a cookie / session?