Posted by Bojhan on August 18, 2009 at 5:22pm
Issue Summary
With Drupal 7 we embarked on a rewrite of most of Drupal's part, now that we are introducing the CCK UI. We need to make sure that in conforms with the new standards we set in [#501452]. One of the major issues is all the technical implications that come with creating and editing a CCK field which should be made more clear, mostly by removing and rewording the existing descriptions.
Comments
#1
Moving to field_ui component now that CCK UI is in core.
#2
Will have a look today.
#3
Is this related to #560330: Field UI description is too technical ?
#4
There are several updates in this patch that tidy, clarify and correct some of the UI text in here. Screenshots are attached for all changes apart from the first two which are simply capitalizing the word 'Add'.
dman: Thanks for checking. There's no overlap with #560330. This patch is for the UI text.
I just noticed the field settings page could use some love so will make a separate issue for that.
#5
+++ modules/node/node.module 2009-10-25 16:46:36 +0000@@ -90,7 +90,7 @@
+ return '<p>' . t('Individual content types can have different fields, behaviors, and permissions assigned to it. Save the new content type, then edit it to add mew fields.') . '</p>';
Mew fields! I think your cat wrote this patch. ;)
I didn't install and run this patch. Let's see the test-bot try it out.
I think you might have better luck submitting individual patches for each section? I'm not sure. I tried something like this before and it sort of languished.
This review is powered by Dreditor.
#6
Spotted a typo (mew should not appear!) so use this patch instead (which matches the screenshot), thanks.
#7
Ah, you got me :) I can do indiv. patches if that'll help --- will they need to be in separate issues though?
#8
I don't know, I do know webchick told me about "killing kittens" when you have a patch that affects many different components.
And I know how much you love your cat, and I do too. So... not sure if this is a kills kittens thing. I do know there may be existing issues out there which could be duplicated in this uber-patch.
#202533: Improve help texts in "add content type" is related maybe? is it a duplicate?
{edit: Bojhan confirms, this is too much to review at once, so best to break up into component issues, then link to each from here for posterity}
#9
Cool, I have broken this down into smaller issues/patches:
#614316: improvements to body field label and submission guidelines
#614324: Node UI text improvements to author display settings
#614358: UI text improvements to 'Delete' content type confirmation message
#614396: Clarify UI text on page for adding new content types
#10
None of the changes here are related to Field UI.
Also, note that the 'Body label' field will be gone from the 'edit content type' screen when we're done with #553306: Make nodes have no body field by default. Remove deprecated APIs for body field.
#11
#12
This can probably be made inactive now (see comment 9) unless there's further work to be done around this issue.
#13
The last submitted patch failed testing.
#14
Pushing this to Drupal 8, we might need to rewrite parts given on how the UI will evolve then and any testing we do on Drupal 7 but given the text-freeze it doesn't seem this meta issue should stay for 7.