xoops forums

jph000

Just popping in
Posted on: 2010/9/30 18:41
jph000
jph000 (Show more)
Just popping in
Posts: 60
Since: 2004/8/2 2
#1

Template Set Manager Download - bad tar.gz file

Whenever I try to download the XOOPS Default Template Set (or a clone of it) using the Template Set Manager Download link, the downloaded tar.gz file is bad, that is, on Linux the Archive Manager says it is an invalid tar format and generates an error, and on a Mac the Archive Utility likewise generates an error.

The only thing I've found to examine the file is on a Mac using TextWrangler 3.1, which show a sequence of text blocks, starting with:

default/templates/system/system_bannerdisplay.html and a long string of "gremlin" characters and a long string of numbers and more gremlins and then "ustar" and then more gremlins and then an html block

for example.

Any ideas?

XOOPS Version XOOPS 2.4.5
PHP Version 5.3.2-1ubuntu4.5
mySQL Version 5.1.41-3ubuntu12.6

Burning

Theme Designer
Posted on: 2010/9/30 20:53
Burning
Burning (Show more)
Theme Designer
Posts: 1163
Since: 2006/8/22
#2

Re: Template Set Manager Download - bad tar.gz file

hi'

It is not an anwser but ... why do you need Template set manager ?
I believed it was deprecated since Xoops 2.0.14 and his templates oveload feature

I may be wrong...
Still learning CSS and... english

ghia

Community Support Member
Posted on: 2010/10/1 8:16
ghia
ghia (Show more)
Community Support Member
Posts: 4954
Since: 2008/7/3 1
#3

Re: Template Set Manager Download - bad tar.gz file

Probably your server is missing some libraries for making the archive (zip compression: PHP function gzencode).

Probably the file is despite its name a regular .tar file. Try to rename it to .tar and open it like that.

jph000

Just popping in
Posted on: 2010/10/1 19:08
jph000
jph000 (Show more)
Just popping in
Posts: 60
Since: 2004/8/2 2
#4

Re: Template Set Manager Download - bad tar.gz file

ghia, the problem is with the tar file itself that's generated.

The default.tar.gz that's downloaded unpacks okay to default.tar, which generates an error when trying to unpack.

I've spent some time checking code (e.g., /class/class.tar.php) and PHP settings. I've got two xoops sites running on the same ISP's production server. The first uses xoops 2.3.3 and the default.tar.gz file unpacks okay, all the way to the default folder containing the templates folder and tplset.xml file.

The second site uses xoops 2.4.5 beta and the default.tar file extracted from the downloaded tar.gz file is bad. (On my test Ubuntu system noted in a prior post, running xoops 2.4.5, the same thing happens, namely, a bad tar file.)

I've opened the two default.tar files in TextWrangler to compare them as to format, but see no obvious problem. Binary information, of course, is not viewable.

So, this problem remains unresolved.

ghia

Community Support Member
Posted on: 2010/10/2 8:41
ghia
ghia (Show more)
Community Support Member
Posts: 4954
Since: 2008/7/3 1
#5

Re: Template Set Manager Download - bad tar.gz file

There is no difference between 2.3.3 and 2.4.5 in the programs involved (/class/downloader.php, /class/tardownloader.php, /class/class.tar.php, /modules/system'admin'tplsets/main.php) apart from some cosmetic things.

Altough when testing it here on xoops.org 2.4.5, I got also some errors with Winzip:
- Trailing garbage in GZIP file, decompression ended. (Could be from Winzip, as I have this with other tar.gz files too and not with eg 7zip)
- Invalid archive directory
From another older XOOPS, I got also the trailing garbage message, but the tar file opens.
Opening both with Notepad++, it seems there are no file names encoded in the failing tar archive (It should start with the (full) filename of the first template).

I don't know why this fails.

Igor1509

Friend of XOOPS
Posted on: 2010/12/27 11:14
Igor1509
Igor1509 (Show more)
Friend of XOOPS
Posts: 1
Since: 2009/7/12
#6

Re: Template Set Manager Download - bad tar.gz file

Hi there, it's possible to open this bad tar.gz file with muCommander . I had problems to open this file before with any of my archive-programms, so last try was to open it with this alternative file-explorer and it worked.