admin-page-framework icon indicating copy to clipboard operation
admin-page-framework copied to clipboard

Published 20 hours ago • verified publisher icon michaeluno

Compiled file corrupted or invalid

Open SUGO-es opened this issue 9 years ago • 3 comments

Hi,

When building the framework with the utility returns me a corrupt or invalid zip file.

Best regards.

xtend-admin-page-framework.3.8.1.zip

SUGO-es avatar Aug 21 '16 10:08 SUGO-es

Hi,

I cannot reproduce the problem with the given information unfortunately. A couple of suggestions for you to find the cause and the way to reproduce the problem.

  1. When downloading a zip file, the server may be producing a PHP error and causing the file to be corrupt. So check the PHP error log and post relevant log entries if you find some.
  2. Try on a server with a different OS. If you got that corrupt file with a Windows server, try with a Linux server and see if you get the same problem. If this does not make a difference, try running it on a clean installed test site with the default theme and no plugin except Admin Page Framework - Loader and see if the same problem happens.

michaeluno avatar Aug 21 '16 12:08 michaeluno

Hi Michaeluno,

I do not get any error , I have proven in multiple installations and gives me all damaged or corrupted file .

update: Ok, error occurs when have enabled plugin APF with my compiled framework , if I turn off my plugin everything works correctly. There is some inconsistency here when there are several APF working at the same time.

Thank you very much as always for the help Michaeluno.

SUGO-es avatar Aug 22 '16 08:08 SUGO-es

Hi,

Ok, error occurs when have enabled plugin APF with my compiled framework , if I turn off my plugin everything works correctly.

If you see some error messages, can you post them?

Also please try providing the steps to reproduce the error. Unless I see it, the problem won't be fixed.

You said it occurs when your plugin using APF and Admin Page Framework - Loader are both activated. Then you should be able to check which part of code of your plugin causes the conflict. For example, try commenting out the lines that instantiate the classes extending the framework classes. If the problem does not go away, then keep commenting out the lines of your plugin until the problem goes away. Then you should be able to tell which line causes it.

michaeluno avatar Aug 22 '16 13:08 michaeluno