Bug202407250835 profile vcard empty

2024-07-25 09:37:47

Hubzilla Support Forum

adminsforum@hubzilla.org

od wrote the following post Thu, 25 Jul 2024 09:38:06 +0200

Bug202407250835 profile vcard empty

The option 'export' for a profile, produces a vcard with no 'connection' content

2024-07-25 10:39:32

Der Pepe (Hubzilla) ⁂

pepecyb@hub.hubzilla.hu

Profiles are like ‘business cards’ that we create for our channels. A profile has no connections, only the channel has connections. This is why the connections are not exported with the profile export. After all, not every ‘business card’ contains all the names of people you know.

In my opinion, it is therefore correct that no connections are exported. RFC6350 does not provide for connections either.

The real question that arises if you have created several profiles for a channel and you export one that is not visible to all contacts would be where this ‘list’ of visibility is exported. I guess this is rather part of the channel export file.

Question for the Hubzilla experts: Are profiles also exported in a channel export file? And also their visibility for other users?

2024-07-25 11:55:31

Der Pepe (Hubzilla) ⁂

pepecyb@hub.hubzilla.hu

Then the profile export (single) is used to add a created profile to another channel via import, right?

2024-07-25 13:29:58

Der Pepe (Hubzilla) ⁂

pepecyb@hub.hubzilla.hu

Ok, I'll give that a try too.

Premiere... 😂 I'll create my first ‘second profile’ for this (I don't actually need it yet).

2024-07-25 15:24:19

Der Pepe (Hubzilla) ⁂

pepecyb@hub.hubzilla.hu

@Harald Eilertsen I can confirm the behaviour. It is possible to select the profile file during import, but there is no ‘button’ to confirm the selection. Clicking on ‘Submit’ in the profile editor cancels the file selection and does not change anything in the new profile.

2024-07-26 09:36:12

od@zotum.net

> In my opinion, it is therefore correct that no connections are exported

Mis-interpretation again (communication needs to improve!)

The 'connection' is this context is the information of the channel that has the 'export', _not_ the list of connections that have been added to a channel/profile.

The expected behaviour is that a channel/profile vcard is available when it becomes a 'connection' somewhere and the person wants to import vcard data into a database such as an address book of connections (e.g. 'ldap'?)

The 'vcard' should store all of the information that the channel/profile has submitted. This information should then become the data as a vcard of that channel/profile when it becomes a 'connection' somewhere else.

The 'vcard' export does not even show the name of the channel/profile!:

"
BEGIN:VCARD
VERSION:4.0
PRODID:-//Sabre//Sabre VObject 4.3.1//EN
UID:sabre-vobject-...
ADR;TYPE=HOME:;;;;;;
FN:
N:;;;;
END:VCARD
"
It should show:

"
BEGIN:VCARD
VERSION:4.0
PRODID:-//Sabre//Sabre VObject 4.3.1//EN
UID:sabre-vobject-...
ADR;TYPE=HOME:;;;;;;
FN: your full name as entered in your hubzilla channel/profile
N:;;;;. your channel name/profile as entered in your channel/profile
your other meta data (e.g. location, country, hometown) that you entered in your channel/profile
END:VCARD
"

Behaviour about import, export, clone of channel/profiles is separate and seems to be another new bug

2024-07-26 12:14:53

Der Pepe (Hubzilla) ⁂

pepecyb@hub.hubzilla.hu

@od

Mis-interpretation again (communication needs to improve!)

Accepted... I misinterpreted that.

It seems that you misunderstand profiles. A profile is the description for channels. You can also use identical profiles for different channels. The profile is linked to a channel, but the channel is not linked to the profile. This is why the channel is not in the VCARD, but the profile is in the channel export file.