Hello,

It's have problem with Extra fields on Downloads app when i upgrading to Version 4.7.20. It's doesnt display when i add a file on Downloads app

Does anyone meet this case on me?

Regards

It has permission now:

Downloads

• Implemented support for permissions on Custom Fields.

• Added custom fields to the Downloads API responses.

I didn’t use it yet but it is probably the reason why it isn’t showing up.

I cant see any issues my end. Please check both the following

1 - for the field in question, the permissions are set on that field correctly

2 - the field is question is selected as an extra field to be used in the downloads category

@Marc I just upgraded a test site to 4.7.20 and this is what's happening:

1. Existing custom fields are visible/usable to all, but the new 4.7.20 version adds a permission check.

2. The upgrade code does NOT add permission rows for the existing fields to enable the add/edit permission for all groups.

3. You have to edit the field in ACP to update the permissions.

4. With the permissions updated the fields show again in the add/edit form.

There is no upgrade code to insert the permissions for the existing fields anywhere. The upgrade should add permissions rows for everyone to add/edit the fields to keep it compatible with the pre-upgrade setup. Post upgrade only the view permission is enabled for all groups. 👀

26 minutes ago, teraßyte said:

@Marc I just upgraded a test site to 4.7.20 and this is what's happening:

1. Existing custom fields are visible/usable to all, but the new 4.7.20 version adds a permission check.

2. The upgrade code does NOT add permission rows for the existing fields to enable the add/edit permission for all groups.

3. You have to edit the field in ACP to update the permissions.

4. With the permissions updated the fields show again in the add/edit form.

There is no upgrade code to insert the permissions for the existing fields anywhere. The upgrade should add permissions rows for everyone to add/edit the fields to keep it compatible with the pre-upgrade setup. Post upgrade only the view permission is enabled for all groups. 👀

Excellent, thank you for that

2 hours ago, teraßyte said:

@Marc I just upgraded a test site to 4.7.20 and this is what's happening:

1. Existing custom fields are visible/usable to all, but the new 4.7.20 version adds a permission check.

2. The upgrade code does NOT add permission rows for the existing fields to enable the add/edit permission for all groups.

3. You have to edit the field in ACP to update the permissions.

4. With the permissions updated the fields show again in the add/edit form.

There is no upgrade code to insert the permissions for the existing fields anywhere. The upgrade should add permissions rows for everyone to add/edit the fields to keep it compatible with the pre-upgrade setup. Post upgrade only the view permission is enabled for all groups. 👀

I'll do some tests next week, but there is one in applications/downloads/setup/upg_107795/upgrade.php

I can confirm that all fields have no add/edit permissions.

12 minutes ago, Daniel F said:

I'll do some tests next week, but there is one in applications/downloads/setup/upg_107795/upgrade.php

Ops, I see the problem. I was looking at the 5.0.0 files which don't have that folder yet. 🤦‍♂️

The code is indeed there, but the permissions are missing as visible in the opentype's screenshot above. I had the same situation right after the upgrade when I edited a field permissions.

Yes, the code is faulty. I have fixed this and we'll probably patch this on Monday, but the fix isn't retroactive, so anybody who upgrades in the meanwhile will need to set the permissions manually.