pesianstranger 2009-04-26 22:27:08 priority major -> minor
pesianstranger 2009-04-26 22:27:08 owner malanciault -> pesianstranger
pesianstranger 2009-04-26 22:27:08 type defect -> enhancement
pesianstranger 2009-04-26 22:27:08 comment 1 -> as we have profile module, it's not a major improvement... all we have to do is add it to profile installer script.
icmsunderdog 2009-05-01 08:10:25 component Misc -> Core Modules
icmsunderdog 2009-05-01 08:10:25 summary fields for jabber, gtalk + skype -> fields in improfile for jabber, gtalk + skype
nekro 2009-05-14 02:42:48 cc -> dev@community.impresscms.org
nekro 2009-05-14 02:42:48 comment 1 -> Not agree at all... we cant create as many configuration as all the users of the community wants... teach them how to create them.

Is more... I propose all the inverse... start removing fields... as aim , yim, msnm, ... those are not vital... most of them are deprecated... is a little stupid adding fields that in a few time should be removed... when ICQ started anyone imagine the sad ending of this messenger?

Opinions?
m0nty 2009-05-14 07:26:17 comment 1 -> imo we should have default, the fields available in 1.1.2 etc.

improfile allows you to create your own fields, so personally, i can't see the point in applying this ticket to the core.
nachenko2 2009-05-14 07:46:57 comment 1 -> I think Everything that goes beyond user + password + email should be optional.
nekro 2009-05-31 03:52:59 comment 1 -> So? ... what we do... votation?
Please... just post an email with the letter of the option you chose.

A - Include this fields.
B - Teach the users how to include them.
underdog 2009-05-31 05:17:47 milestone ImpressCMS 1.2 -> ImpressCMS 1.3
ep98 2009-05-31 05:56:14 comment 1 -> I agree with nachenko2, all fields must be optional
AIM is dead already, US home users still uses MSN bcz is default in windows, but they're rarely uses community sites, ICQ is no more bcz of several things.

Just give a user examples how to add them. Some prefer XFire, some GTalk, some Jabber, some other forks, if ICMS gonna maintain them all, the user profile fields will be overloaded and will not look compact, one ugly profile with many open not filed fields.
m0nty 2009-05-31 10:07:40 comment 1 -> on fresh installs, i agree, username, displayname, password email are needed, all others can be created by the webmaster, it needs to be made clear/documented how to properly do this step by step with improfile.

on upgrades, as long as those fields that the user has filled in are migrated, then i see no problems. they contain info, i'm sure the user would like to keep that info. afterall, some developers change the text label of existing fields so that they can use that field for some other info. so as long as existing fields are preserved migrated, i see no choice other than B.
m0nty 2009-05-31 10:19:00 comment 1 -> maybe we could build a couple of templates that webmasters could quickly use..

by this I mean when they install improfile, they can goto a setup/config page which at the click of a button can create and configure necessary field names, visibility etc.. like a pre defined list which just updates the DB with a predefined list

so the webmaster could create a simple default icms 1.1.2 user profile page with the same fields.

or another template to use, would say have different fields, like company name, company address, Blog, gtalk, skype.

then at click of a button a default config is created with those fields.

just to get the webmaster started quickly. even new config templates could be added to the module if the config data is stored in an xml file or ini file of somesort. in fact, that would then enable developers who manage clients sites to easily setup the profiles. all a developer would do is create the necessary xml file for that site and upload it. click a button in improfile admin, and voila, all those user fields and permissions are instantly created.

in fact, we could pretty much do that with most of the config system.. call it 'config override' or whatever.
skenow 2009-06-14 14:22:33 version trunk -> 1.2
skenow 2009-12-04 03:23:39 comment -> moving tickets out of the 1.3 release that are not cleanup or optimization
malanciault 2009-12-23 12:19:25 milestone -> To be assigned

pesianstranger 2009-04-26 22:27:08 priority major -> minor
pesianstranger 2009-04-26 22:27:08 owner malanciault -> pesianstranger
pesianstranger 2009-04-26 22:27:08 type defect -> enhancement
pesianstranger 2009-04-26 22:27:08 comment 1 -> as we have profile module, it's not a major improvement... all we have to do is add it to profile installer script.
icmsunderdog 2009-05-01 08:10:25 component Misc -> Core Modules
icmsunderdog 2009-05-01 08:10:25 summary fields for jabber, gtalk + skype -> fields in improfile for jabber, gtalk + skype
nekro 2009-05-14 02:42:48 cc -> dev@community.impresscms.org
nekro 2009-05-14 02:42:48 comment 1 -> Not agree at all... we cant create as many configuration as all the users of the community wants... teach them how to create them.

Is more... I propose all the inverse... start removing fields... as aim , yim, msnm, ... those are not vital... most of them are deprecated... is a little stupid adding fields that in a few time should be removed... when ICQ started anyone imagine the sad ending of this messenger?

Opinions?
m0nty 2009-05-14 07:26:17 comment 1 -> imo we should have default, the fields available in 1.1.2 etc.

improfile allows you to create your own fields, so personally, i can't see the point in applying this ticket to the core.
nachenko2 2009-05-14 07:46:57 comment 1 -> I think Everything that goes beyond user + password + email should be optional.
nekro 2009-05-31 03:52:59 comment 1 -> So? ... what we do... votation?
Please... just post an email with the letter of the option you chose.

A - Include this fields.
B - Teach the users how to include them.
underdog 2009-05-31 05:17:47 milestone ImpressCMS 1.2 -> ImpressCMS 1.3
ep98 2009-05-31 05:56:14 comment 1 -> I agree with nachenko2, all fields must be optional
AIM is dead already, US home users still uses MSN bcz is default in windows, but they're rarely uses community sites, ICQ is no more bcz of several things.

Just give a user examples how to add them. Some prefer XFire, some GTalk, some Jabber, some other forks, if ICMS gonna maintain them all, the user profile fields will be overloaded and will not look compact, one ugly profile with many open not filed fields.
m0nty 2009-05-31 10:07:40 comment 1 -> on fresh installs, i agree, username, displayname, password email are needed, all others can be created by the webmaster, it needs to be made clear/documented how to properly do this step by step with improfile.

on upgrades, as long as those fields that the user has filled in are migrated, then i see no problems. they contain info, i'm sure the user would like to keep that info. afterall, some developers change the text label of existing fields so that they can use that field for some other info. so as long as existing fields are preserved migrated, i see no choice other than B.
m0nty 2009-05-31 10:19:00 comment 1 -> maybe we could build a couple of templates that webmasters could quickly use..

by this I mean when they install improfile, they can goto a setup/config page which at the click of a button can create and configure necessary field names, visibility etc.. like a pre defined list which just updates the DB with a predefined list

so the webmaster could create a simple default icms 1.1.2 user profile page with the same fields.

or another template to use, would say have different fields, like company name, company address, Blog, gtalk, skype.

then at click of a button a default config is created with those fields.

just to get the webmaster started quickly. even new config templates could be added to the module if the config data is stored in an xml file or ini file of somesort. in fact, that would then enable developers who manage clients sites to easily setup the profiles. all a developer would do is create the necessary xml file for that site and upload it. click a button in improfile admin, and voila, all those user fields and permissions are instantly created.

in fact, we could pretty much do that with most of the config system.. call it 'config override' or whatever.
skenow 2009-06-14 14:22:33 version trunk -> 1.2
skenow 2009-12-04 03:23:39 comment -> moving tickets out of the 1.3 release that are not cleanup or optimization
malanciault 2009-12-23 12:19:25 milestone -> To be assigned

pesianstranger 2009-04-26 22:27:08 priority major -> minor
pesianstranger 2009-04-26 22:27:08 owner malanciault -> pesianstranger
pesianstranger 2009-04-26 22:27:08 type defect -> enhancement
pesianstranger 2009-04-26 22:27:08 comment 1 -> as we have profile module, it's not a major improvement... all we have to do is add it to profile installer script.
icmsunderdog 2009-05-01 08:10:25 component Misc -> Core Modules
icmsunderdog 2009-05-01 08:10:25 summary fields for jabber, gtalk + skype -> fields in improfile for jabber, gtalk + skype
nekro 2009-05-14 02:42:48 cc -> dev@community.impresscms.org
nekro 2009-05-14 02:42:48 comment 1 -> Not agree at all... we cant create as many configuration as all the users of the community wants... teach them how to create them.

Is more... I propose all the inverse... start removing fields... as aim , yim, msnm, ... those are not vital... most of them are deprecated... is a little stupid adding fields that in a few time should be removed... when ICQ started anyone imagine the sad ending of this messenger?

Opinions?
m0nty 2009-05-14 07:26:17 comment 1 -> imo we should have default, the fields available in 1.1.2 etc.

improfile allows you to create your own fields, so personally, i can't see the point in applying this ticket to the core.
nachenko2 2009-05-14 07:46:57 comment 1 -> I think Everything that goes beyond user + password + email should be optional.
nekro 2009-05-31 03:52:59 comment 1 -> So? ... what we do... votation?
Please... just post an email with the letter of the option you chose.

A - Include this fields.
B - Teach the users how to include them.
underdog 2009-05-31 05:17:47 milestone ImpressCMS 1.2 -> ImpressCMS 1.3
ep98 2009-05-31 05:56:14 comment 1 -> I agree with nachenko2, all fields must be optional
AIM is dead already, US home users still uses MSN bcz is default in windows, but they're rarely uses community sites, ICQ is no more bcz of several things.

Just give a user examples how to add them. Some prefer XFire, some GTalk, some Jabber, some other forks, if ICMS gonna maintain them all, the user profile fields will be overloaded and will not look compact, one ugly profile with many open not filed fields.
m0nty 2009-05-31 10:07:40 comment 1 -> on fresh installs, i agree, username, displayname, password email are needed, all others can be created by the webmaster, it needs to be made clear/documented how to properly do this step by step with improfile.

on upgrades, as long as those fields that the user has filled in are migrated, then i see no problems. they contain info, i'm sure the user would like to keep that info. afterall, some developers change the text label of existing fields so that they can use that field for some other info. so as long as existing fields are preserved migrated, i see no choice other than B.
m0nty 2009-05-31 10:19:00 comment 1 -> maybe we could build a couple of templates that webmasters could quickly use..

by this I mean when they install improfile, they can goto a setup/config page which at the click of a button can create and configure necessary field names, visibility etc.. like a pre defined list which just updates the DB with a predefined list

so the webmaster could create a simple default icms 1.1.2 user profile page with the same fields.

or another template to use, would say have different fields, like company name, company address, Blog, gtalk, skype.

then at click of a button a default config is created with those fields.

just to get the webmaster started quickly. even new config templates could be added to the module if the config data is stored in an xml file or ini file of somesort. in fact, that would then enable developers who manage clients sites to easily setup the profiles. all a developer would do is create the necessary xml file for that site and upload it. click a button in improfile admin, and voila, all those user fields and permissions are instantly created.

in fact, we could pretty much do that with most of the config system.. call it 'config override' or whatever.
skenow 2009-06-14 14:22:33 version trunk -> 1.2
skenow 2009-12-04 03:23:39 comment -> moving tickets out of the 1.3 release that are not cleanup or optimization
malanciault 2009-12-23 12:19:25 milestone -> To be assigned

After reading the comments and thinking about it for almost two weeks now I came to the conclusion that everyone can add these fields in case he wants them. The reason why AIM, ICQ, MSNM and YIM are directly added is that these are system fields.

With closing ticket* 334 there are no further problems in creating these fields. Therefore this ticket will be closed without a fix.

Updating tickets (#70, #162, #163, #168, #270, #271, #272, #273, #274, #275, #329, #330, #331, #332, #333, #334, #335, #336, #337, #338, #339, #364, #401, #405, #407, #423, #429, #432, #434, #435, #437, #439, #440, #441, #445, #447, #449, #450, #453, #562, #613)

Updating tickets (#253, #60, #165, #61, #62, #63, #64, #118, #120, #121, #122, #123, #124, #125, #169, #172, #177, #182, #185, #225, #234, #251, #277, #305, #307, #310, #318, #1, #2, #3, #5, #119, #126, #127, #128, #163, #164, #171, #174, #175, #183, #245, #322, #65, #153, #170, #173, #176, #180, #184, #306)