This forum is for less technical discussions about the Drupal project, not for support questions.

Restrict editable fields for existing node?

Ok, I am still a babe in the woods with Drupal but doing my best to get my head around it. I have a requirement that goes something like this:

  1. User creates a node (using Flexinode for the time being but may have to go with a custom module based on story.module) and saves it.
  2. User is no longer allowed to edit the node (I know what you are thinking but wait...the problem is coming) except for one field called "status".
  3. User can only change the status field for a node they created.

I have looked at node.module, common.inc, and flexinode.module. I hate to do it but this requirement is immediate so I think I am gonna have to ask one of my developers to start hacking but before I do, I am hoping for some feedback. I looked into node.module and could add in the code below to the node_link such that the link runs a script which updates the status in the db for the current node:

    if ($user->uid == $node->uid) {
      $links[] = l(t('Change Status to Complete'), "changestatus.php?nid=" . $node->id, array('title' => t('Mark this file as complete.')));
    }

I am sure there are many drawbacks to the idea above and I want to keep the hacks to an absolute minium. Any suggestions on how to approach this particular requirements?



Cheers,
Andy

Multiple Vocabularies vs. Deep Hierarchy?

I've created a new node type for maintaining a list of projects for a portfolio site. I'd like to categorize each project by various criteria, so I'm creating various vocabularies specifically for that node type. For example:

Timeline
-- > 1 month
-- 1 month
-- 2 months
...

Budget
-- Pro Bono
-- < $1,000
-- $1,000 - $10,000
...

Languages
-- C
-- C++
-- Java

Relational Databases
-- Oracle 8i
-- DB2
...

Backwards/Forwards compatibility

I’m looking for a PHP/MySQL based CMS to replace my existing site.
The existing site is a magazine site built using framesets : each article is a separate HTML or PDF file, with its own metadat exposed to search robots.
The articles are not ephemeral. The aim of the site is both to provide lively and regularly updated news items, and a searchable archive which will grow over the years. There is no plan to purge articles.
I have several problems which I would like to address in different posts, here is the first:

SQL syntax error

SELECT meta_description, meta_keywords, meta_title FROM
template_front_options tfo JOIN storefronts_to_templates stt ON
tfo.template_front_id = stt.template_id WHERE storefront_id =

You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near " at line 1

I get this error message when I type my domain name in without the www. , can anyone help?

'Search' Index Empty

Hi to everyone.

I made some try with the 'search' function, but i'm not able to find enithing from my nodes.
When I look in the db, I find the search_index empty. Maybe this one is the reason? how can I solve it?

I'm currently running drupal 4.3 with an Italian translation

thanks!

Need Suggestions for File Format for Deploying Content to Web

Has anyone tackled the issue of the best (or better) file format to use to deploy content on a web site? Much of the content at my firm is done using the Microsoft Office suite. This is great for the content creators who have MS-Word or MS-Visio on their desktops. However, I do not want to require clients to have MS-Word or MS-Visio in order to be able to successfully view the content on line.

Pages

Subscribe with RSS Subscribe to RSS - General discussion