Module development and code questions

Billing users to publish nodes

Howdy,
after puzzling with different possible solutions to get different levels of publishing for node listings (a la Silver, Gold, Platinum) - see eventually pay 2 publish post here (note: i posted this thread also there for more visibility) - i am working on a new module that aims at providing a solution.

Scope
(well, actually work-in-progress!) the idea is to let users publish basic version of nodes for free, and later be able to pay to "upgrade" it and show more information (more fields outputted to the final node) and add more visibility (views plays here).
This should incentivate new users to go for a free publication at first, letting them explore the ground first, and helping new sites collecting content.

Taxonomy_actions:
I asked a coder to develop a module that aims at what i tryed to explain above, based on E-commerce obviously, on Taxonomy (Category) and Actions. The module will be called Taxonomy_actions, and the idea behind it is:

• set up different "Levels" with different costs and properties (Silver, Gold, Platinum style). Each level will have it's corresponding taxonomy (category) term.
• to upgrade a node, the user will have to buy the desired "Level" and assign it to one of his published nodes. The corresponding taxonomy term will be assigned to the desired node.
• user will also be able to choose a duration in months. The final price will be a combination of Level x Number of months.

Once done that:

• a conditional can be used in the template of the content-type to show more or less text-fields or whatever fields (show additional information) depending on the level they bought.
• Views will play the role of showing higher-level listings in specific pages and blocks views in the site (more visibility).

Possible questions:

Q: Why not use role memberships to define different roles for publishers?
A: Tryed this in the early day, but this way is not possible to differentiate levels on a per-node level. All nodes published by a user asssume the properties of the role he buys. No good.

Q: Why not just add a price to publish a node type?
A: This way users have to pay a fixed price for each node they wish to publish. This is very straightforward and effective, but also can be a stop for some users who would like to get familiar with the site before actually paying for publishing.

Q: And why not have a node-type per level instead of taxonomy levels?
A: True, different per-level content-types each with additional information fields could be setted up, but in this case issues would arise when a user decides to upgrade/downgrade a node listing (he should copy the information into the new node and delete old one).

Hallo

I am new to drupal. I like to make an integration between Drupal and phpBB. So I took a look at this site http://kepp.net/drupal/ and http://drupal.org/project/phpbb

I can see that this module requires mod_rewrite support on the server. But mod_rewrite is disable by my webhost (b-one). And they don't want to enable it :(

Hi ,
Can anyone please develop or upgrade the exising news page module for drupal 4.7 please as the existing maintainers dont seem to be doing any development and are not replying to any issues as well.

Manuj

I was wondering if there's a way to set the _REQUEST['destintion'] variable to include a query string?

Here's my situation in a nutshell:

I've got a form that logged in users can use to submit links to the site. This interaction is initiated via a bookmarklet (essentially a "Digg this" type thing). If they're not logged in, they get sent to the login page. I'm using the login_destination module to send them back to the proper form upon login. But when I try to pass the query string, I'm getting errors.

here's how my function is looking: (assume destination at this point is 'node/add/storylink')

  if ($_REQUEST['destination']) {
    $path = $_REQUEST['destination'];
    $query = '';
    // do a test to see if we're also passing url submission info
    if ($_REQUEST['edit']['url']) {
      $query .= '?edit[url]=' . $_REQUEST['edit']['url'];
    }
    return url($_GET['q'], "destination=$path". urlencode($query));
  }

problem is, that will return a destination string of:

node/add/storylink%3Fedit%5Burl%5D%3Dhttp%3A//www.google.com

if I don't urlencode the querystring, I get redirected to whatever site is in edit[url].

Has anyone else had a problem like this? is there some kind of destination_query_string function that exists?

Thanks!

I use form API create a form page. But if I click the submit button many times in a very short time, the form values will be submitted not only once. In the database there are also not only one data record.

why?

I'd prefer to have space between the list of contacts, and maybe more explanation of who they are, and also for it not to say 'Who would you like to contact?' Anyone know how to change it?