BGM

Yes, this was before I truly understood the separation between advanced custom fields and the file meta fields, and them not being connected.

Originally I had made them a date field: https://www.screencast.com/t/kF8bKUA98E
Which made it use the date picker and then displays the date in the editor as mm-dd-yyyy. https://www.screencast.com/t/fj5wOp52ahlX
However when it gets displayed on the package it displays as yyyy-mm-dd https://www.screencast.com/t/AOUYkwNNSQU

Since it wasn’t working as I wanted and my efforts to shift the date format based on earlier replies I changed the fields in the editor to text and input them as mm-dd-yyyy as I wanted for temporary purposes until I could get it worked out on the display side to be a date field. I wanted to use a the date field with date picker to reduce input user error as well as eventually I want to build some internal processes off of these fields based on date. I’ve changed the fields back to date type in the editor.

Making this adjustment seems to have had no effect on the Attached File Meta Date Display.

I added the plugin again and enabled it. The problem is still there so I deactivated it again.

I created a test package: https://www.screencast.com/t/CrkWSdMtkws
and then a mockup of the package details page I would like: https://www.screencast.com/t/Rq1KGiD9r0

The custom fields I created are Firm Name, Approval Number, Approval Date, Exp Date
[acf_DocumentFields_firmName]
[acf_DocumentFields_approvalNumber]
[acf_DocumentFields_approvalDate]
[acf_DocumentFields_expDate]

Everything above “Available Files” I’ve created already.
It’s the file section I’m not sure how to do.

Sounds great.
Until then can you point me to where I can make that change locally. I believe the package dates are currently just date(“F j, Y”).

Yes, I tried using either of those template tags, as those are the only attached file related tags I see in the documentation: https://www.wpdownloadmanager.com/doc/templates/template-tags/ I didn’t see any other way to show the attached files on the details page.
The Custom Field Addon makes it seem like you can simply use the field shortcodes. Are these shortcodes not available to the details page templates?

Details Page: https://www.screencast.com/t/CrYQjji56w
I would like that table of attached files (currently created with [file_list]) to look the same as the “Call To Action 3” Link template. Which is to say I’d like the icon, the filename, the file size, and the custom meta fields for each attached document that I have added to the package. Custom Meta Fields: https://www.screencast.com/t/Fk6DnVBltnCa

“Page templates are used to render package details page”
If I can’t customize the way that the “package details page” displays the files in that package why would I ever send anyone to the package details page?

I’ve designed a very nice page to show the details of the package. However currently, no matter what I do it shows “file name” and download button for the files in that package. That’s it. I want it to show the nice custom download link section I created that also contains the 4 custom file attachment meta fields that I have added.

I’m trying to create a library of my packages. There is information in the package and the document that needs to be communicated to my users. The package will contain a variety of files such as a preview, a pdf, .doc, .docx, .jpg and .png version. They’ll download the version that meets their needs from the package.

Now seeing the difference I can see my mistake. Thank you for your help.

So to create a custom meta attached file field using the add ons and version at this time is:
<input placeholder=”<?php _e( “Field Placeholder Text” , “download-manager” ); ?>”
title=”<?php _e( “Field Title Text” , “download-manager” ); ?>” class=”form-control” type=”text”
name=’file[fileinfo][<?php echo $id; ?>][Field Name]’
value=”<?php echo isset($fileinfo[$id][‘Field Name’]) ? esc_html($fileinfo[$id][‘Field Name’]) : ”; ?>” />

with Field Name coming from the Custom Fields add on with the input field needing to be placed in the appropriate bootstrap layout as the rest of the form is.

Okay, I got it.
Here is what it took. https://www.screencast.com/t/zNQOQ7RkJjdz

Yes, I think I may have gotten it to work. I did get the custom field to show up on the document as a form field.
I updated the snippet with the following:
[acf_groupname_fieldname] replaces [version] in the snippet and
‘groupname/firmname’ replaces ‘version’
in his example snippet.

One thing to note, the custom fields you create to use for the document will also show up on the package as form options. Is there any way to prevent this?

I’m also noticing that when I put a value into the form it doesn’t save. 🙁