Drupal 7.x

I am creating new fields for my users registration form and am having difficulty figuring out how to use the "parent" option. I'm assuming that it allows fields to be organized by listing them as sub-fields in defined sections, but I have no idea how to add an option to my "parent" drop down selection list; all I have available is .

Resolved my own issue

I've been using different CMSes for several years now but am new to Drupal. I've read through most of the documentation and even picked up a book on Drupal 7. However, I'm having trouble understanding the menu and page structure and think it may be a conflict of what I know about other CMSes.

I would like to add an "Image Style" that resizes an image by percentage instead of a fixed pixel. In Drupal 6, Image Cache allowed you to do this (http://drupal.org/node/163561).

I know Image Cache is now in the core... so would I have to alter the core? That's something I really want to avoid. Write a module? I have PHP experience but have never written a module and don't really know where to start. It seems like this wouldn't be too big of a fix but I'm not really sure where to go...

Hello,

I'm currently involved in building a Drupal 7 website integrated with SalesLogix. We've evaluated several CMS options and think Drupal offers by far the most potential, but the integration with SalesLogix is critical. I know it supports several other CRMs, so I'm thinking there has to be a straightforward way to handle this.

We are currently investigating switching our CMS to Drupal (preferably 7). I have been playing around with it a bit and found several, half baked ways of achieving what I want, but it strikes me a more knowledgeable person might know the "right" way to do it.

We have a large content base in the region of 10-12,000 pages across our two main site, plus around 20 additional sites with smaller number of pages in the range of 5 - 100. We have a large author base of around 120 authors who have very specific areas within the site that they can edit, and these edits are then processed through a workflow to a group of 7 web managers to approve. Within the context of thsi requirement we need a way of driving one over-arching, large, quite deep, hierarchical structure, but keeping the experience as simple as possible for the authors so that its not possible for them to end up publishing items to the wrong places in sites.

The closest I can find to achieving this is to have several content types defined, one for each type of author and allow these content types to only publish to specific menus, and then somehow combine this large number of menus into one large menu system to drive the navigation.