content

Hello All,

I had been working for couple of days on a module that would allow me to transfer nodes from a Drupal Website to another drupal site (for now).

which includes a full node save along with terms,files and CCK extra fields.

its really been a headache since i started patching the method "taxonomy_node_save" in "taxonomy services";
i have done the step of save a node (piece of cake) but now into the terms problem hence the NID of the new transferred node needs to be send to the remote server.

ill keep you updated guys on it and might release a contribution soon.

Hi,

I have a question related to the usage of Drupal to create content. I am basically running 10-15 blogs on various topics and I would like to use a single CMS system to manage them. So I chose Drupal. Now I want to know, whether it makes sense to create different content types for each blog-topic, or just publish everything as stories with appropriate taxonomies? My requirements are as below.

1) I want to have different themes for each blog-topic.
2) I want to have separate blocks for each topic, in the frontpage, which will display the latest 5 posts in that topic.

.

.

As some of you know, I've recently taken over maintenance of Inline and Image Assist, and initiated the Wysiwyg project. That was not only caused by personal interest, but also to take the necessary steps to realize the long awaited Inline API. You might ask yourself, what those three modules have in common or to do with each other at all: They deal with user input, allow to embed complex contents into a content, and provide an interactive GUI for that. If you already had the chance to work with them, you already know that there is a rather hidden, non-obvious hard-dependency between them.

Although I'd really like to discuss both topics (Inline and Wysiwyg support) separately, the gained experience on these topics enforces us to discuss them concurrently. The following mockup hopefully explains why: (see attachment to view in full size)

I submitted this within the forums, but I don't think it will get the attention it desires... I think this is an important step in development in Drupals Social Networking... Take a look and see if it is something that will draw the attention and the enthusiasm that it deserves. If it is deemed usable, then I will start working on an API.

The first beta for the 5.x.3 release is out. It is likely buggy and needs tester love.

In good news, I did all the testing against pgSQL, so there should not be any database issues.

5.x.3 adds multiple page support and will also include a number of community-driven features. It will also be the version ported to Drupal 6.

http://drupal.org/node/204753

Greetings fellow Michigan Drupal users. I have a question. Let it be noted that I have only been using Drupal for about 2 months, so please forgive my newbisms & lack of knowledge...believe me, I'm trying, and I'm excited to be doing so.

Content Blocker enables users to block the content they see according to various parameters. Current implementations are for blocking by user and blocking by leech feed. So like on some social networking sites, users can say "I don't want to see any content by User X."

Early version. Please try it out and post issues. AJAX support through Fast Toggle module. Modularly built, quickly extensible through small .inc files to offer different kinds of blocking.

http://drupal.org/project/contentblocker