Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.7.25, 4.7.27
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
-
Verified?:No
Description
When I attempted to upload the CiviCRM plugin using WordPress’s built-in zip-file uploader, the unpacking process always fails when it encounters a file named ..png (there are four image named ..png within the CiviCRM files). This happens both on my local windows based development server and live server, so I presume it may be a minor glitch with WordPress’s unpacking program.
I unzipped the CiviCRM plugin, deleted the four ..png files and then re-zipped the result, which uploaded and installed perfectly (after which I manually uploaded the four ..png files).
I don’t know if there is a good reason for using files named ..png, but I posted this because I probably would have thought CiviCRM was too buggy to use if I had not already installed and learned to configure it on my local development server. It seems likely that this issue might dissuade some organizations from using CiviCRM for WordPress (i.e., if it throws basic installation errors).
I only have experience with versions 4.25 and 4.27, but I suspect this is happens for all WordPress versions of CiviCRM
The four ..png files are at:
civicrm\civicrm\packages\kcfinder\themes\dark\img\files\big
civicrm\civicrm\packages\kcfinder\themes\dark\img\files\small
civicrm\civicrm\packages\kcfinder\themes\default\img\files\big
civicrm\civicrm\packages\kcfinder\themes\default\img\files\small
Update (Nov9, 2017): WordPress developers have apparently fixed this issue as of late Setpember 2017, though the current release of WordPress still throws the error.