CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Feature #31617

remove profile image field and use the one from core

Added by Simon Schaufelberger over 1 year ago. Updated 11 months ago.

Status:New Start date:2011-11-06
Priority:Should have Due date:
Assignee:- % Done:

0%

Category:-
Target version:First TER version
Votes: 3 (View)

Description

instead of using an own profile image field, use the one that comes with the core.

History

Updated by Simon Schaufelberger over 1 year ago

  • Target version set to First TER version

Updated by Jörg Velletti about 1 year ago

as i am using my own existing Plugin to edit the Users Profile, i just changed the Typoscript Setup :

config.tx_extbase {
persistence.classes {
Tx_Community_Domain_Model_User {
mapping {
tableName = fe_users
userGroup.foreignClass = Tx_Extbase_Domain_Model_FrontendUserGroup
columns {
// profile_image.mapOnProperty = image // actuall default
image.mapOnProperty = image // my setting, useful to work together with mm_forum
}

this Setting should be default ..

Updated by Tymoteusz Motylewski about 1 year ago

AFAIK community uses different field for image because the default one may have multiple values (multiple images).

Updated by Simon Schaufelberger about 1 year ago

the question here is if we want to have multiple fields in the database for the same thing or not. if there are multiple images, we could also just use the first one (use explode for ',' and use the first array index) if the array is longer than 1 item something like:

$explodedValue = explode(',' $dbfield);
if (count($explodedValue) > 1) {
    $image = $explodedValue[0];
} else {
    $image = $dbfield;
}

what do you think about that?

Updated by Alexander Weiß about 1 year ago

I like this solution, so we have the same profile image on the whole page. At the moment i have to set the image twice, in community and for example in mm_forum.

Updated by Tymoteusz Motylewski about 1 year ago

Of course, I would like to be as much compatible with other extensions as possible. If any of you can provide a patch I will be more than happy :)
Please keep in mind that the solution have to work with community galleries.

Also available in: Atom PDF