Download Files Not Opening, even when forced

dangdesigns

New Member
I've tried both the normal and kitchen sink files, from multiple browsers & machines, all have the same result. Download as xx.zip, then change to xx.zip.cpgz using the regular unarchive utility (Mac OS 10.10.5)

I attempted to unzip via terminal and see the following errors

Archive: /Volumes/Mac Pro Work Files/Software-and-Installers/joomla/pkg_fabrik_3.8.zip
error [/Volumes/Mac Pro Work Files/Software-and-Installers/joomla/pkg_fabrik_3.8.zip]: missing 221 bytes in zipfile
(attempting to process anyway)
error [/Volumes/Mac Pro Work Files/Software-and-Installers/joomla/pkg_fabrik_3.8.zip]: attempt to seek before beginning of zipfile
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)
(attempting to re-compensate)
file #1: bad zipfile offset (local header sig): 0
(attempting to re-compensate)
error [/Volumes/Mac Pro Work Files/Software-and-Installers/joomla/pkg_fabrik_3.8.zip]: attempt to seek before beginning of zipfile
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)
file #2: bad zipfile offset (local header sig): 851
file #3: bad zipfile offset (local header sig): 890
file #4: bad zipfile offset (local header sig): 4890127
file #5: bad zipfile offset (local header sig): 4899538
file #6: bad zipfile offset (local header sig): 4920817
file #7: bad zipfile offset (local header sig): 4991574
file #8: bad zipfile offset (local header sig): 5025077
file #9: bad zipfile offset (local header sig): 5039568
file #10: bad zipfile offset (local header sig): 5051976
file #11: bad zipfile offset (local header sig): 5078454
file #12: bad zipfile offset (local header sig): 5257557
file #13: bad zipfile offset (local header sig): 5270947
file #14: bad zipfile offset (local header sig): 5374197
file #15: bad zipfile offset (local header sig): 5415488
file #16: bad zipfile offset (local header sig): 5500848
file #17: bad zipfile offset (local header sig): 6128961
file #18: bad zipfile offset (local header sig): 6232903
file #19: bad zipfile offset (local header sig): 6254483
file #20: bad zipfile offset (local header sig): 6260191
file #21: bad zipfile offset (local header sig): 6288344
file #22: bad zipfile offset (local header sig): 6313729
file #23: bad zipfile offset (local header sig): 6366428
file #24: bad zipfile offset (local header sig): 6397602
file #25: bad zipfile offset (local header sig): 6457968
file #26: bad zipfile offset (local header sig): 6480168
file #27: bad zipfile offset (local header sig): 6497032
file #28: bad zipfile offset (local header sig): 6536657
file #29: bad zipfile offset (local header sig): 6548156
file #30: bad zipfile offset (local header sig): 6570200
file #31: bad zipfile offset (local header sig): 6573876
file #32: bad zipfile offset (local header sig): 6584142
file #33: bad zipfile offset (local header sig): 6601940
file #34: bad zipfile offset (local header sig): 6625757
file #35: bad zipfile offset (local header sig): 6651180
file #36: bad zipfile offset (local header sig): 6676640
file #37: bad zipfile offset (local header sig): 6693402
file #38: bad zipfile offset (local header sig): 7343937
file #39: bad zipfile offset (local header sig): 7401913
file #40: bad zipfile offset (local header sig): 7544509
file #41: bad zipfile offset (local header sig): 7880660
file #42: bad zipfile offset (local header sig): 7923053
 
Can you unzip other extensions?

I can't see a problem when unzipping in Windows10 (with WindowsExplorer or 7-zip) or on UNIX.
 
nope, the other extensions all do the same on both of my macs, OS 10.10 & OS 10.11. I'll try my windows machine
 
Windows 10 gives me "package is invalid" message for the 3.8 package and I also tried the "list - Link" download as a test.
 
Issue confirmed.
I did my test with the fabrik package downloaded on 11-Oct, the recent one is not working (can't unzip or install).
 
Hmmm. The ZIPs in my local build folder, the ones that would have gotten ftp'ed up during the last build, are fine. Not sure what's going on there.

Anyway, I've run the build again, and a new set of ZIPs has been uploaded.

(So this build is actually github as of today, so it's really 3.8.1, but I'm not ready to do an actual update yet)

-- hugh
 
Happening to me too - Mac OS 10.12.6, Google Chrome, J!3.8.1. These are the new 3.8 zipfiles downloaded from the website, not the github.
ie:
opening... plg_fabrik_element_youtube_3.8.zip
gives me a new file... plg_fabrik_element_youtube_3.8.zip.cpgz

Will try from the github now.
 
Happening to me too - Mac OS 10.12.6, Google Chrome, J!3.8.1. These are the new 3.8 zipfiles downloaded from the website, not the github.
ie:
opening... plg_fabrik_element_youtube_3.8.zip
gives me a new file... plg_fabrik_element_youtube_3.8.zip.cpgz

Will try from the github now.
Have you tried since I re-uploaded all the zips earlier (just before my last post)?

Sent from my HTC6545LVW using Tapatalk
 
Yes, about 80 mins ago. I also downloaded 3-4 again about 55 mins ago. All elements I tried still had the same error.

UPDATE:
I have just finished cloning from github onto my desktop, zipped one of the plugins and installed it onto the site I'm working on - it installed correctly.
 
Last edited:
Github updated as it should, so it seems specific to the individual zipped files in the download section?
 
I am also confirming the issue. Size mismatch error while downloading on Windows 10. On Linux it says crc error.
As an extreme step,

Unfortunately, the error exists on all earlier version in download section of fabrikar.com

I have tried git zip file and tried to discover from joomla backend -- works till you add one article after that it gives all sort of database errors like #__fabrik_log not found.
 
OK, something is adding a couple of blank lines at the start of the file during the download process (where the upload element code reads the file from disk and outputs it to the browser), I'm working on it.

-- hugh
 
OK, fixed.

A couple of blank lines had somehow crept into the start of a totally unrelated system plugin, before the opening <?php tag, which was causing two blank lines at the start of every page on the front end. Didn't hurt anything else, but also got inserted into the output from the upload element's download script output that sends the ZIP content back to the browser.

-- hugh
 
Just for anyone stumbling across this, to find PHP files with blank lines at the start or end, ssh to your server, create a file (say 'blanklines.sh') with this in it:

Code:
#!/bin/bash

for f in `find . -type f -name '*.php'`; do
  for t in head tail; do
    $t -1 $f  |egrep '^[  ]*$' >/dev/null && echo "blank line at the $t of $f";
  done;
done

And run it ...

# chmod 755 blanklines.sh
# ./blanklines.sh

... and it'll churn out any files it finds which start or end with blank lines. You are looking for ones which have blank lines either before the opening php tag or after a closing tag. Files with no close tag are OK.

-- hugh
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top