Issue with “Maximum Upload Size” Display in Frontend Upload Form

Hello,

I believe the value set in Upload Configuration: Max Upload File Size should be reflected in the “Maximum upload size” displayed on the frontend upload form.
However, the current behavior varies depending on the site: sometimes it shows the value from the server’s Default INI Setting, and other times it simply displays “2MB.”

This seems to be a bug.
Could you please check the behavior?

Thanks

P.S. My system information:
- Joomla 5.4
- EDocman 3.1
- PHP 8.2.20
-  MySQL 8.0.42
- Apache

Hi,
The line showing "Maximum Upload file size" is a core feature of Joomla. However, you can handle it as follows:
1. Open the file: root/language/en-GB/en-GB.com_edocman.ini
2. Add this line:
JGLOBAL_MAXIMUM_UPLOAD_SIZE_LIMIT=""
You can enter a custom translation that matches your upload limit, or simply leave it empty to hide this line.
Best regards,
Dam

Thank you for the explanation.

Just to clarify my original point:
The issue I reported is not about the text string itself, but about the inconsistency between the value set in “Max Upload File Size” and the value displayed as “Maximum upload size” on the frontend upload form.

In my understanding, the frontend display should normally reflect the configuration value set in EDocman. However, depending on the site, the displayed value is sometimes taken from the server’s default INI setting or fixed at 2MB.
This inconsistency made me think that there might be an issue in the logic that determines which value is shown.

Could you please check this behavior on your side?

Thank you for looking into this.

Hi,
The file responsible for displaying the upload size is created by Joomla at this location: layouts/joomla/form/field/file.php. Joomla takes the value from the PHP ini settings, which is why you see this inconsistency.
Additionally, Joomla does not allow overriding the layout for this file, so the only solution is to override the text in the language file.
Thanks
Dam

Hi Dam,

Thank you for the explanation.

I understand your point about Joomla’s core file field layout.
However, the issue I reported is not about the Joomla layout itself, but about the inconsistency between EDocman’s own “Max Upload File Size” configuration and the value displayed on the frontend upload form.

Other extensions (for example, Convert Forms) are able to display a custom upload size that matches their configuration, so it seems technically possible to provide a consistent value independent of Joomla’s default layout.

If the displayed value cannot reliably match EDocman’s configuration, then hiding the line may be a better option than showing an incorrect value to users.
However, to enhance the value of EDocman, I believe it would be much more beneficial to display the correct value based on the backend configuration rather than simply hiding the line.

Could you please consider this point?


Thanks

Hi,
We have found a better solution for this issue and will include it in the next release of Edocman. Thank you for your feedback and patience.
Dam

After updating to EDocman 3.3, the display of “Maximum Upload Size” on the frontend has been improved. However, in the backend, the “Maximum Upload Size” display does not reflect the configured value and does not match the frontend value. It appears that the backend is displaying the “default INI setting,” so I would like to report this issue.

Hi,
Thank you for your feedback.

In most cases, displaying the correct maximum upload file size is more important on the frontend, since this information helps users know the limits when uploading documents. In the backend, typically only administrators upload files, so displaying this value is less critical for admins.
Thanks
Dam

Thank you for your explanation.
I understand that the frontend display is more critical for end users. However, my concern is not about priority, but about accuracy and consistency.

In many real-world cases, the person managing uploads in the backend is not the same person who configured the server or component settings. Showing an incorrect value in the backend can therefore cause confusion and lead to incorrect assumptions.
If the backend value cannot reflect the configured limit, it would be better not to display the value at all, rather than displaying a misleading “default INI value.”

This is why I consider this a bug rather than a UX preference issue.
Also, from a UI/UX perspective, displaying an incorrect value is worse than displaying nothing, regardless of whether the user is an administrator or a frontend user.


Thanks

Hi,
Thank you for sharing your concerns and suggestions.
We understand your point about accuracy and consistency in the backend display, and we agree that showing incorrect values can cause confusion. We will review this issue and see what we can do to address it in the next version.
If you have any further feedback or questions, please feel free to let us know.
Thanks
Dam