node

I'd like to see someone create a simple, stable, mechanism to change the node-type of an existing node. I foresee something where data fields from the old node type can be mapped to fields in the new node type, or ignored, and any missing fields can be filled in. Then the updated node can be previewed before the change is committed to the database.

Hi,

I have been checking Google Webmaster Tools and i got 32 Duplicate meta descriptions:

All the /node?page=* pages.

How do i add custom titles for those pagination pages?

Thanks.

Hi, I posted this to the forums, but probably this is a better place to place it since it seems to be a problem for the advanced Drupal community...

I have a node type called XXXXX for example. When the node is displayed (by the author) usually there are two default tabs on the top:
View | Edit

Let's say I want to display some information related to the current node and I want to display that on a separate tab on the same level as View and Edit. So the tab line should look like this:
View | Edit | Related Information

I'm going to bring up an old discussion now. I don't think there's been much discussion in forums (but if so, maybe someone can dig up some posts). But there has been much over the past couple of years in IRC.

This has to do with integrating RPG with the Drupal node system. The current RPG module is its own entity, entirely unattached to nodes. This is a reversal of earlier versions of the module. Originally, I'd planned to fully integrate it with CCK and Views, and if you look at the first few dozen commits, you'll see that RPG objects were actually node types, and the attributes were fields.

Eventually, I ran into several problems. Some issues were merely difficult, while others seemed nearly insurmountable. Thus, I rewrote the engine, making RPG objects an entirely separate entity in the database.

Now I'm writing graphical support for RPG, and am finding myself duplicating code, and questioning (yet again) my original decision to detach RPG from nodes. Here are some Pro's and Con's of using node types & fields for RPG objects:

I'd like to be able to submit a post, have members vote on it, and then if the score is high enough, it gets published publicly. Is that possible? Perhaps if I posted a private group post, it could be changed to public with og_audience?. Should I be looking at the action module instead?

We are currently working on adding language support to nodes in a simple and clean way. Meanwhile separate implementation details and issues are now created and discussed in the issue queue of our project. Feel free to comment on our implementation and/or submit patches as we move along.

After reading Hariska2@drupal.org's comment about creating a rudimentary DMS module, I was thinking about wanting just such a thing. (It is part of the reason for establishing this group.)

However, much of the functionality already exists. I want to make sure that if I aid in the creation of a new module for document management that that module doesn't totally overlap existing functionality to much. However, there are some pretty significant improvements that I think could be made. I will commence with suggesting the things that already exist and then consider what is missing.

Hi,

I am interested about your favorite way to post your forum topics/comments.

I'll classify it into 3 categories:
1. The way it done in Drupal/IPB, simple text area maybe with BB Code/Html
2. The way it done in vBulletin. Cool plain text editor, with user friendly BB Code/Smileys buttons and wysiwyg option.
3. Using advanced wysiwyg editors like TinyMCE or FCKEditor

Link to fckeditor demo:
http://www.fckeditor.net/demo/

Link to TinyMCE demo:
http://tinymce.moxiecode.com/example_full.php?example=true

Which of the wysiwyg editors you like more? TinyMCE or FckEditor?

I think my favorite way is like it done in vBulletin, but what's your favorite option? What will fit best the DruBB project?

The most abstract concept in my opinion: "everything is a field" (fully atomic value) instead of "everything is a node". CCK is ardent proof that this idea could work. If that's the case, we can share the same field (as regards value), node is just a set of fields tie together by new relationships system, whereas content type is a predefined set of relationships between fields.

If like me you are not new to PHP, Web development or CMSs but new to Drupal and hoping to build a website with complex user profiles you may be looking for that killer link that documents putting modules like nodeprofile and usernode through their paces.

Does anyone know the URL of that tutorial, or anything even remotely like it?

Thanks in advance :-)

zzJames