Filename extensions changed ??
-
I’m not about to sort through 5032 files, and remove all the confidential ones.
As I said, …. it will take a while.
-
Have sent you a test archive. :)
-
Installed version 10.20.17 , and unfortunately, this problem is now worse. :confused:
Instead of just a few files that had the filename extension changed. there are now over 80 files (same archive used for testing), and the ‘filename’ (including the extension) has now been truncated. I checked 5 files, and they are all truncated at 145 bytes (includes full pathname and extension).
What is strange, is that when I shortened the length of the path used to extract, exactly the same problem occurred, that is, the same number of filenames are corrupt.
I would have thought decreasing the size of the (full) pathname, would have resulted in less errors found in the filename.
When I increased the size of the (full) pathname, and did the extract again, the filenames are now truncating at 151 bytes (145 + 6).
There don’t appear to be any filename extensions changed this time, just the truncation problem, but the problem is not consistant with the pathname length, and the same filename results, irregardless of the pathname length.
Here is an example, showing the correct filename, total size is 146 bytes …
F:\temp\powerachiver.…\class\smarty\internals\core.assemble_plugin_filepath.php
======
When the full pathname is increased in size by 8 bytes, the filename is truncated at 145 bytes …F:\temp\powerachiver.…\class\smarty\internals\core.assemble_plugin_fil
When the full pathname is increased in size by 6 bytes, the filename is truncated at 151 bytes …
F:\temp\powerachiver.…\class\smarty\internals\core.assemble_plugin_fil
When the full pathname is decreased in size by 22 bytes, the filename is truncated at 129 bytes …
F:\temp\powerachiver\….\class\smarty\internals\core.assemble_plugin_fil
In all cases, the same filename results, a truncated name, and in all extracts, exactly the same number of errors have occurred (approx. 80 files with filenames truncated).
‘spwolf’ has the same test archive, and will be able to see what the extract is doing.
When the archive is being viewed, the filenames appear to be okay, it is just some weird problem with the extract. :confused:
-
Please try with .21 from our website and see what happens.
thanks
-
Installed .21 , and ran the extract again, … same problems unfortunately.
Just extract the test archive I sent, and you will see where filenames have been truncated. :(
-
Has there been any progress on fixing this bug please ??
-
Try 10.21 RC 1 from our site and see if it works.
-
Try 10.21 RC 1 from our site and see if it works.
Can you supply a link please.
Also, this bug was reported over 6 months ago. I’d really expect it to be fixed by now, and not have to rely on “user testing” of new releases, especially when I went to the trouble of creating a website with various files, then created a website archive, and sent it to PA tech personnel, so they can test it.
-
did you use RC1? (10.21.xx) or 10.20.21?
:-)
Check RC1 from download page please.
-
Have downloaded and installed the RC1, thanks.
I have only checked a few files, especially the ones that were noted in the earlier post, and they are now okay.
Will create a larger archive and extract that, and then advise.
Thanks. :D
-
:-)
-
Well, the filename extensions seem okay, plus the filenames (and paths) look okay, but the modified time of the files don’t seem to reflect what the timestamps should be (I will have to look more into that).
Also, for some reason, PA displayed a “ghost” folder, one that isn’t on the website, called “the.same.host.name;”, see screen dump.
-
Two other minor annoyances with the interface, is that when using the “2-pane” view, the folders are not sorted, makes it a real pain for navigation (see screen dump).
Also, there needs to be a horizontal scroll bar added to the left hand pane/window, as often the 'folder depth" is more than the width of the left hand window, and therefore, folder/path names cannot be seen (see screen dump).
-
Yes, timestamps of the extracted archive are definitely a problem. Will have to look into it further, and then advise. :(
-
Two apologies. :o
Also, for some reason, PA displayed a “ghost” folder, one that isn’t on the website, called “the.same.host.name;”, see screen dump.
PA displayed that folder correctly, I ran the archive through “tar”, and the folder was there, fortunately on a PA extract, it just ignored the folder name.
Yes, timestamps of the extracted archive are definitely a problem. Will have to look into it further, and then advise. :(
I was baffled by the timestamps, because in some cases, the date (day) was different to the file date on the server.
Took me a while to realise it was adjusting the timestamps of files, to reflect the timezone, even had to extract the archive on a *nix box and run “tar” to make sure it wasn’t a Windooze thing.
There is a 15 hour difference in timezones, between here and the web server, and in many cases, the file date was the next day, … hence the confusion. :confused:
So, timestamps of the extracted archive are definitely NOT a problem.
Please accept my apologies.
-
we added scroll bar to the archive folders bar, so it should work fine now. Please check with RC2 from our download page.
thanks!!!
-
Okay thanks, I’ll try it out.
