Closed (won't fix)
Project:
Coder
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
31 Aug 2008 at 09:30 UTC
Updated:
30 Dec 2014 at 18:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
stella commentedComment #2
stella commentedTry out the attached patch.
Cheers,
Stella
Comment #3
pp commentedI used the patch. It works good. I saw a new group(Select specific profiles) The group contains all installed profil. (I was install all 6.x profil, and my install profile)
I saw correct code review. ("Coder found 1 projects, 2 files, 114 normal warnings" Pasqualle said me, my coding style is dirty... I see now, and I will correct it! ;))
Thanks!
pp
(short: It works, Thanks)
Comment #4
pp commentedduplicate file, see the picture... (I saw it after I corrected all errors)
Comment #5
stella commentedHmmm I can't reproduce this on my test site.
Comment #6
pp commentedsorry, sorry, sorry I'm stupid... I made some changes in coder.module on codesprint. I used this wrong version.
The patch is good.
Comment #7
pasquallet(' (core)')should be:
' ('. t('core') .')'string inside t() should not start or end with space, it is hard to translate correctly..
but this should be fixed with a different issue, as coder already uses this incorrectly
even created a new request for code style check: #304150: check string in t()
based on pp test, and my quick visual code review, this patch is ready to go
Comment #8
stella commentedRe-rolled the patch with the t() change suggested by Pasqualle.
Cheers,
Stella
Comment #9
douggreen commentedThe patch was malformed, so I re-rolled it.
I'm wondering, where do custom and contrib install profiles live? This patch looks from them in /profiles. Can they live in other places?
I'm also wondering if the munging the {system} table names with the profile names might cause problems. Can we have an install profile with the same name as a module.
Comment #10
stella commentedWell the installation instructions for the install profiles I downloaded (e.g. Drupalbin) said to put them in the profiles/ directory, alongside profiles/default/. I also checked where install.php looks for the installation profiles. The function
install_find_profiles()just looks in the top level profiles/ directory :Cheers,
Stella
Comment #11
stella commentedYeah, I suppose there could be potential for name clashes between profiles and modules/themes. Maybe we could prepend the index name with 'coder_profile' or some such. Can take another look at it.
Comment #12
gregglesThe patch still mostly applies and still mostly works.
I think it's impossible to have a module/theme/profile of the same name or at least it's not generally supported by Drupal.
Comment #13
klausiCoder for Drupal 6 is now frozen and only security fixes will be applied. Feel free to update this issue and reopen against 7.x-2.x or 8.x-2.x.