[resolved] Invalid upload filename. Valid filenames contain only alpha-numeric, dot, hyphen and underscor

[mtk]

Hey,

this started after the upgrade to 5.2.13. the server settings where not change and should not be changed (as suggested here: http://forum.whmcs.com/showthread.php?81942-problem-in-attachments-after-upgrading-to-5-2-13)

 

WHMCS does not accept 123.pdf or invoice.pdf, which are valid filenames!

 

Invalid upload filename. Valid filenames contain only alpha-numeric, dot, hyphen and underscore characters.

 

 

if a change was made to the software that requires a change on the server, then this should be publicly known!

[Matt]

Hi,

 

Please check to make sure that you don't have the "escapeshellcmd" function disabled in your PHP configuration. If you do, that is the most likely cause for seeing this error message with seemingly valid filenames. If you can enable it again that should take care of it for you.

 

Matt

[edvan.com.br]

Hey,

this started after the upgrade to 5.2.13. the server settings where not change and should not be changed (as suggested here: http://forum.whmcs.com/showthread.php?81942-problem-in-attachments-after-upgrading-to-5-2-13)

 

WHMCS does not accept 123.pdf or invoice.pdf, which are valid filenames!

 

Invalid upload filename. Valid filenames contain only alpha-numeric, dot, hyphen and underscore characters.

 

 

if a change was made to the software that requires a change on the server, then this should be publicly known!

 

Try to update your PHP to 5.4.

[WHI]

HI,

 

I have same problem. This is the solution:

 

Please ensure that the escapeshellcmd function is not disabled by the disable_functions setting in your server's php.ini configuration file, as it is currently used during the attachment process and disabling it will cause this error. If you are unsure of how to check this, please contact your hosting provider/server administrator.

 

B.r.

Robert

[WHMCS TedX]

The issue with escapeshellcmd() being blocked by certain hosts has been addressed and fixed in WHMCS 5.2.14, via case 3688 (Remove reliance on the escapeshellcmd() function).

 

If you still have this problem after upgrading to 5.2.14, open a new support ticket.