Closed (works as designed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
user interface text
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
16 Sep 2010 at 20:51 UTC
Updated:
29 Jul 2014 at 19:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
webchickThanks for the patch!
I think it would either be "Cron run successful" or "Cron ran successfully" (the current string). Both "Cron run" and the shortened "Cron" are nouns.
"Cron run successful" would have better parity with the error equivalent -- "Cron run failed" -- but I don't think we can justify breaking strings for this, since it's not really a bug, per se. Moving to 8.x for consideration.
Comment #2
sebyoga commentedHello,
Thank you for your return, indeed, it is not one really a bug. I suppose that il will also be corrected for Drupal 7 ?
I am going to continue to correct certain bug.
Thank you !
Sebastien
Comment #3
devin carlson commentedUpdated per webchick's recommendation (which I agree with) but I believe that it should be "Cron run was successful." in order to be proper English and to match the past tense of "Cron failed".
Comment #4
droplet commentedComment #5
derjochenmeyer commentedI guess a native english speaker should review this. "Cron run succeeded." sounds weird, but may be correct.
Comment #6
bhosmer commentedThe cron run was successful or Cron ran successfully for the affirmative and The cron run failed or The cron run was unsuccessful would be proper English.
Or to simplify: "Cron failed" and "Cron succeeded without errors" maybe?
Comment #7
Anonymous (not verified) commented"Cron run was successful" or "Cron ran successfully" would be good and more common English.
"Cron run succeeded." is Ok but sounds weird.
Comment #8
derjochenmeyer commentedSo I'd vote for closing "closed (works as designed)" this issue, since the current message is correct english:
Comment #9
derjochenmeyer commentedComment #10
yoroy commentedYep, this was a small misunderstanding by sebyoga that didn't stop sebyoga from actually understanding the message, so nothing to fix here :)