Hello all, I had previously used Flexinode content on a Poetry Magazine website using Drupal 4.7.x Now, in Drupal 5.x it appears that Content Creation Kit replaces flexinode from previous versions, correct? Is the idea the same? I had a menu link to Create Content >> Poems. I also had it setup so that what is submitted appears in the queue, whether it comes from a user role of Contributor, authenticated user, or anonymous. If I give access for all these roles to Create Content, how can I be sure that it goes into the queue for approval first, instead of any user being able to publish directly? Thanks, Bruce

Bruce, We're running into a similar issue with our installation. We have a couple of content types based on flexinode with about 500 nodes based on those types. Rather than convert those to CCK we're exploring using BOTH (gasp!). I have a test site loaded with the flexinodes where I've also installed CCK. They seem to be able to co-exist and I can even reference flexinode types from CCK. The one "catch" I've seen is that I have to enable/disable the flexinode_admin module in order to create/modify flexinode types or CCK types. This doesn't effect node creation, just the management of these custom types. I noticed you mentioned the use of a queue; are you using Drupal's moderation queue? You may want to investigate how this works in 5.1 as I think the moderation queue went away in 5.0. All the best, Scott

I think it was discussed earlier here that you can't give different roles different *default* settings for each content type, but you can give users access by role to view and publish content. The Mercer book has a pretty good overview of user permissions. I'm sure there is more info in the Drupal.org Handbook. You need to go into User Management and first create the roles you want. When I am setting up sites for other people, I typically have a role for webmaster (me), another for site owner, and so on. For my scout troop site there is webmaster, scout leader, and scout member. Then you can go into the User Management/Access Control screen and check off the permissions for each role. You may want to go to User Settings and make it so new registrations need admin approval. On 5/30/07, Bruce Whealton <brucewhealton@yahoo.com> wrote:

Hello all, I want to make sure that most users on my site, including visitors and all others besides those I specify, to have all of their content go into a queue and not be published without approval from administrators. If I go to the Default Options under Workflow and uncheck Published will that put their stories, and etc. into the queue? And those users cannot publish themselves, correct? Only those who can view the queue can publish content submitted to the site, correct? That is what I want. If I want to let a user group/role (what is the correct term?) called "Contributors" actually be able to review content from the queue and publish it, or to be able to select whether or not their content is published, how do I do that? How do I give a user that option of being able to select Published for their content? Thanks, Bruce

-- [ Drupal support list | http://lists.drupal.org/ ]

-- Jean Gazis www.jeangazis.com www.boxofrain.us "Believe those who are seeking the truth; doubt those who find it." - André Gide

I've achieved similar functionality using the workflow module. It requires actions module. I set these up and only gave admin/moderator roles the permission to change workflow status, an then set the default node workflow under admin/content/types to not be published. Then use a form_alter to remove the publishing options from the node creation form, and user that have permissions will be allowed to see the workflow status and use that. Pair this with views to give you a view of all content that has a workflow status of 'In moderation' and you'll have your queue for the administrators. -mike On May 30, 2007, at 5:22 PM, Bruce Whealton wrote:

Well, I want even visitors (anonymous users) to be able to submit content but I don't want them to be able to publish. I want administrators to have to publish content from the queue. I know this can be done. I did this back when I used Drupal 4.7 and then I got away from Drupal for a while. Thanks, Bruce

Jean Gazis <jgazis@gmail.com> wrote: I think it was discussed earlier here that you can't give different roles different *default* settings for each content type, but you can give users access by role to view and publish content. The Mercer book has a pretty good overview of user permissions. I'm sure there is more info in the Drupal.org Handbook.

You need to go into User Management and first create the roles you want. When I am setting up sites for other people, I typically have a role for webmaster (me), another for site owner, and so on. For my scout troop site there is webmaster, scout leader, and scout member. Then you can go into the User Management/Access Control screen and check off the permissions for each role.

You may want to go to User Settings and make it so new registrations need admin approval.

On 5/30/07, Bruce Whealton < brucewhealton@yahoo.com> wrote: Hello all, I want to make sure that most users on my site, including visitors and all others besides those I specify, to have all of their content go into a queue and not be published without approval from administrators. If I go to the Default Options under Workflow and uncheck Published will that put their stories, and etc. into the queue? And those users cannot publish themselves, correct? Only those who can view the queue can publish content submitted to the site, correct? That is what I want. If I want to let a user group/role (what is the correct term?) called "Contributors" actually be able to review content from the queue and publish it, or to be able to select whether or not their content is published, how do I do that? How do I give a user that option of being able to select Published for their content? Thanks, Bruce

-- [ Drupal support list | http://lists.drupal.org/ ]

-- Jean Gazis www.jeangazis.com www.boxofrain.us

"Believe those who are seeking the truth; doubt those who find it." - André Gide -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]

__________________ Michael Prasuhn mike@mikeyp.net http://mikeyp.net 714.356.0168

On Wednesday 30 May 2007 17:22:12 Bruce Whealton wrote:

Well, I want even visitors (anonymous users) to be able to submit content but I don't want them to be able to publish. I want administrators to have to publish content from the queue. I know this can be done. I did this back when I used Drupal 4.7 and then I got away from Drupal for a while.

Oops! I didn't finish my thought in my previous e-mail before I hit send, which was to use the workflow and actions modules as Michael suggested to achieve similar results. -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 14; Cramer, 12; Travis, 10; Angela; Harry, 7; and William, 12:04 am, 12-29-2005) Linux User: http://www.xubuntu.org/ Drupal Fanatic: http://drupal.org/

This is a bit complicated and confusing as I read about it. The CCK module seems to have many functions and applications in addition to what I want. The description in the Install that came with the module mentions wrappers, taxonomy, categories and etc. I thought I was further along in learing Drupal again, but I'm lost reading this. What I want is a unique content type that I will call Poems. I want to control the workflow for that content type and maybe customize the fields that a visitor/user sees. Is that going to be easy enough? The CCK added a number of items to the Module list, some of which are not even selectable (why that is I don't know). I added Category Module also and that seems to add a number of items under Category. I thought I needed that module or should I say those Modules. Can a module be removed? I mean the tables that were created will still be there. If I just remove the module from the site directory, is that going to be ok to do? There's no uninstall module is there? I guess I could just uncheck the enable tabs for the Category module and try to learn one thing at a time. Thanks in advance all for feedback on this, Bruce Larry Garfield <larry@garfieldtech.com> wrote: Yes, CCK has the same "place in the ecosystem" as flexinode, but is a much more robust and extensible architecture. At this point it seems a foregone conclusion that CCK is/will be Drupal's node management system. Unfortunately, there is no good migration from flexinode to CCK that I'm aware of. There's a module that does a conversion in 4.7, but I have not used it and the description, when last I looked, described it as somewhat shaky. In Drupal 5, on Content > Content types you can configure any node type in the system. Simply edit your poem node type and set its default publishing settings to not published. You can then create a View using the Views module to list all poem nodes that have their published flag set to false, and only let admin users see it. Cheers. --Larry Garfield On Mon, 28 May 2007 20:55:21 -0700 (PDT), Bruce Whealton wrote:

Hello all, I had previously used Flexinode content on a Poetry Magazine website using Drupal 4.7.x Now, in Drupal 5.x it appears that Content Creation Kit replaces flexinode from previous versions, correct? Is the idea the same? I had a menu link to Create Content >> Poems. I also had it setup so that what is submitted appears in the queue, whether it comes from a user role of Contributor, authenticated user, or anonymous. If I give access for all these roles to Create Content, how can I be sure that it goes into the queue for approval first, instead of any user being able to publish directly? Thanks, Bruce

David, or if someone else can/will help me, I am now seeing some major things wrong with my site. I'll create a user account if you or someone can help me. You'll see how frustrating this site is now getting to me, and I'm stuck and confused. First, indeed, I thought I could create a new content types without even adding CCK or any module. I do need to add fields to a node, because I want to require that they add their name (or pseudonym) and an email. We must have those two bits of information or we can't publish them. So, I made those required. Getting back to the **serious problems** with the site... This is where I need help. Ok, I created a new menu, to go above the Navigation menu. I called this Word Salad Poetry Magazine. I think I had to create this as a custom block. On most of my themes, the ones I added, that menu doesn't even show up at all!! Second problem... I tried to have a menu item of About Us... and to put a submenu where I list each Staff member as it were, with a link to their bio, which is setup with the Profile module. I just added a Biography paragraph form entry to each user's profile. Most of the time, even when I select About Us to be "Expanded," it doesn't even show the submenu at all! It's not expanded and you can't get to the submenu at all. I want some way to list information about the staff of the publication. Even if the way I'm doing it is not optimal or best, it's not working at all! I also find that when I logout, many menu items, when selected tell the Visitor (anonymous user) that they don't have permission to access the page. They can't access the Submit poem page (form), because they don't have permission it says! Why would it do that? I did give permission for users/visitors to create content. The menus also display and opperate differently for Visitors as compared to when I log in to the site. Sometimes that submenu, that won't display for me, when I'm logged on to the site, will display expanded for an anonymous visitor! Talk about wierd! So, I'll create an account called Assistant for anyone that could take a few minutes to look at this, to help me and I'll pass on the password. David, and/or anyone else, please let me know if you can check this out on my site and see what is going on... hopefully it won't take too long for someone experienced. I really haven't done much at all to the site. So, hopefully I didn't mess things up too much yet. Thanks, Bruce "Metzler, David" <metzlerd@evergreen.edu> wrote: Bruce, If your poem only has a body, as I think it did when I helped you mock this site up some time ago, then you don't need CKK. CKK is for adding fields to a node type beyond title and body, not for creating a new node types. It used to be that you needed flexinode to create a new content type, called Poem, but now you can do this with stock drupal. You can still add categories (taxonmy terms) to new content types as before. You can create the Poem content type without using other modules, provided that you don't need any additional fields. CKK Let's you add fields to custom defined content types. With regard to views, it is used to provide different slices of the data. Want to provide a custom page showing all the poems submitted by a user, or the currently logged in user, Views is good for that. Want to provide a block containing all poems of a specified category? Views is good for that as well. Views and CKK are considered a couple of the basic must haves in Drupal, and well worth the time to just get them downloaded and installed in your Drupal 5 site. Hope this finds you well. P.S. I left up my mockup of your Poem site (drupal 4.7) on www2.evergreen.edu/dave, and was surprised to find that people are periodically finding this site and submitting Poems. :) It's been entertaining, so I've left it up.....

On Wednesday 30 May 2007 17:27:32 Bruce Whealton wrote:

You mention the views module, is that a core module? Bruce

No it's not, and it is listed on the Drupal website in the modules area. It even has it's own category. -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 14; Cramer, 12; Travis, 10; Angela; Harry, 7; and William, 12:04 am, 12-29-2005) Linux User: http://www.xubuntu.org/ Drupal Fanatic: http://drupal.org/

In order to moderate the publication of newly created content, a first step would be to do the following: 1. Assuming your content types (poem, etc.), has already been created, go to Administer » Content Management » Content types, and edit Poem. 2. Look for the Workflow section at the bottom of the form. 3. Make sure "Published" is unchecked. Click on "Save content type". Now, all new Poems will "be in the moderation queue", in the sense that they will not appear as published content. To manage the "moderation queue", make use of Drupal's powerful batch content processing administration interface: 1. Go to Administer » Content Management » Content 2. If necessary apply a filter (status is "not published", type is "Poem", etc.). 3. Read the material posted by your budding bards (I would right click and read in a different tab or window to maintain the administration window), and check all the pieces you feel are up to par and should be published. Then, making sure "Update options" is set to "Publish", click on the Update button. Hope this helps. saludos, Victor Kane http://awebfactory.com.ar On 5/29/07, Bruce Whealton <brucewhealton@yahoo.com> wrote:

Hello all, I had previously used Flexinode content on a Poetry Magazine website using Drupal 4.7.x Now, in Drupal 5.x it appears that Content Creation Kit replaces flexinode from previous versions, correct? Is the idea the same? I had a menu link to Create Content >> Poems. I also had it setup so that what is submitted appears in the queue, whether it comes from a user role of Contributor, authenticated user, or anonymous. If I give access for all these roles to Create Content, how can I be sure that it goes into the queue for approval first, instead of any user being able to publish directly? Thanks, Bruce

-- [ Drupal support list | http://lists.drupal.org/ ]

Fabio Varesano / 2007/05/29 / 08:16 AM wrote:

did you install the video_image module?

Under admin > modules, Video Image is enabled, so I think the answer is yes? -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com>

...

You could ask your hosting company to fix this problem for you.

Yes, I should. Altho I am more interested in how and when this happened, and how to prevent from this to happen in the future.

When you installed the video module and the video_upload plugin drupal automatically created a folder to store the videos (a 'video' folder under the folder you configured for uploads). The newly created folder has been created by Drupal which is PHP code executed by the Apache server which run under an different Unix user. Then the new folder has been assigned to the user which run apache. Fabio