Installation xml is not created after compilation #822

New Issue

Closed

opened 2021-11-01 17:14:29 +00:00 by nikkolaos · 4 comments

nikkolaos commented

2021-11-01 17:14:29 +00:00

(Migrated from github.com)

Steps to reproduce the issue

Compile a project and then try to install it (please note that I try to install to another joomla instance, not the same as the one containing JCB).

Expected result

After compilation, have a zip file that can be installed to any Joomla instance

Actual result

During installation, I get the message "Error Unable to locate the installation XML"
The zip file that the compilation produces, does not contain the XML file, and the index.html file.
Also, the access.xml, config.xml, controller, .php and index.html files are missing from the admin directory.

System information (as much as possible)

OS Name & Version: debian 9
MySql Version: Mariadb
Apache Version: apache 2
PHP Version: 7.3
Joomla Version: 3.9.28
JCB Version: 2.12.10 (recently upgraded)
Browser: chrome

Additional comments

I noticed this after upgrading to the most recent .10 JCB from .9 version
Also, after the compilation I get some warnings regarding "not being able to write/copy to folders", for example "Failed to copy .../.../public_html/images/Wooden-Folder-5515017801-plus.png to .../...public_html/administrator/components/com_componentbuilder/compiler/com_diaxeirisi_programmaton_v1_0_223__J3/admin/assets/images/icons/program_add.png"
If I copy the missing files manually from an older compilation zip file, the installation seems to work properly. It doesn't seem to have affected other files.

### Steps to reproduce the issue Compile a project and then try to install it (please note that I try to install to another joomla instance, not the same as the one containing JCB). ### Expected result After compilation, have a zip file that can be installed to any Joomla instance ### Actual result During installation, I get the message "Error Unable to locate the installation XML" The zip file that the compilation produces, does not contain the XML file, and the index.html file. Also, the access.xml, config.xml, controller, .php and index.html files are missing from the admin directory. ### System information (as much as possible) - OS Name & Version: debian 9 - MySql Version: Mariadb - Apache Version: apache 2 - PHP Version: 7.3 - Joomla Version: 3.9.28 - JCB Version: 2.12.10 (recently upgraded) - Browser: chrome ### Additional comments - I noticed this after upgrading to the most recent .10 JCB from .9 version - Also, after the compilation I get some warnings regarding "not being able to write/copy to folders", for example "Failed to copy .../.../public_html/images/Wooden-Folder-5515017801-plus.png to .../...public_html/administrator/components/com_componentbuilder/compiler/com_diaxeirisi_programmaton_v1_0_223__J3/admin/assets/images/icons/program_add.png" - If I copy the missing files manually from an older compilation zip file, the installation seems to work properly. It doesn't seem to have affected other files.

Llewellyn commented

2021-11-02 14:18:23 +00:00

Please never use chrome, use Firefox, this will resolve your issue.

nikkolaos commented

2021-11-02 14:32:54 +00:00

(Migrated from github.com)

Please never use chrome, use Firefox, this will resolve your issue.

Thanks for the input.

I also used Opera, which perhaps shares things with Chrome, noticed the same problem there.

I will try Firefox tonight and let you know.

> Please never use chrome, use Firefox, this will resolve your issue. Thanks for the input. I also used Opera, which perhaps shares things with Chrome, noticed the same problem there. I will try Firefox tonight and let you know.

nikkolaos commented

2021-11-03 07:47:43 +00:00

(Migrated from github.com)

For some reason it worked fine, both on Opera and Firefox. Can't explain why.

Llewellyn commented

2021-11-12 17:44:54 +00:00

Anyway building extensions with JCB in Firefox should work... the extensions themselves should be okay in all browsers... it seems like its just JCB itself as it deals much with file system creation, moving and screening far beyond your normal extensions would do.

Yes this is a chrome thing that mess with server side folder caching. Absolute madness if you ask me, since I saw this I never use chrome from anything except google stuff. Seems like massive over reach if you ask me.... Anyway building extensions with JCB in Firefox should work... the extensions themselves should be okay in all browsers... it seems like its just JCB itself as it deals much with file system creation, moving and screening far beyond your normal extensions would do.