No Bug - Hidden Custom Fields are Showing!

As part of my venue management, I need to store venue phone numbers and e-mail addresses, but I do not want the public to see them. I used Venue custom fields 6-10 for "private" information.

In Settings/Global Parameters, I had set Editvenue/Max#CustomFields to 5.

This worked when I initially set it up over a year ago. Now these fields are exposed. I am wondering if this issue was introduced in v2.2.0, which I installed in December.

Example:

Go to themodelrailroadopenhouse.com

Under the Schedule menu, go to Event List.

From the Event List, click on one of the events for "Columbia Historic Preservation Society".

On the Event page, under Venue, it is displaying the following custom fields, which should be hidden:
NMRA Division: SUSQUEHANNA
Sub Division: SOUTHERN PA
E-mail: seg57@embarqmail.com

Hi, I don't know if this is a bug. Perhaps you wanted it otherwise we thought!
The Setting is for giving to the frontend creators only a limited number of Custom Fields.
You know because unused customfields with their complicated names (when the content is not yet defined). This always made troubles for new creators.

Now I don't know (I am not a developer) if this is big work to give customfields special rights.
At the moment all our developers are very engaged in the first life. We still need more peoples engaged in developing! If you find a solution, please share here. Thanks

Hi jbritton,

this is not a bug. Generally all custom fields with data will be shown on event/venue details view.
The setting to limit the amount is for create/edit event/venue view on frontend only, as Jojo described.
If we change this behavior we would make a lot other webadmins unhappy which requested to limit custom fields on frontend but give full writablity on backend.

Personally I would never recommend to realise security/privacy by a simple counter in the settings. Instead these fields should be configurable by access control records as possible for categories, articles etc. - but this is a bigger development task.

Maybe a workaround could be to "mis-use" an open-date event attached to the venue and with proper assess rights, containing the internal infomration you need to store "private".

So the expectation is that all 10 custom venue fields display for everyone...

That only the quantity specified in the config are available for editing in the front end by those with edit privileges and the others would be read-only (are they displayed?)...

and that any editing of the protected custom fields would only be in the back end.

Is this the behavior as designed?

That's correct.
The Edit view will show the quantity specified in settings only. (others will not be shown, also not read-only)
The Details views will show all custom fields if they contain data.

Possible easy solution:

create a template override: copy the file "default.php" from "components/com_jem/views/venue/tmpl/default.php" to "templates/MY_TEMPLATE/html/com_jem/venue/default.php"

in the copyed file search for change it to So only the five first custom fields will show up.