joomla/Component-Builder
joomla/Component-Builder
38
20
Fork 10
Code Issues 55 Pull Requests Projects 3 Releases Wiki Activity

During compilation I get Errors #703

New Issue
Closed
opened 2021-03-20 11:50:09 +00:00 by Schrijvers123 · 9 comments
Schrijvers123 commented 2021-03-20 11:50:09 +00:00 (Migrated from github.com)
Copy Link

I just installed Compnent builder on a fresh Joomla installation. Used the demo component to install.

I get the error:
JFolder: :delete: Could not delete folder. Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/libraries/phpspreadsheet/vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Writer/Pdf
Failed deleting Parser.php
Failed deleting Workbook.php
Failed deleting Worksheet.php
Failed deleting Xf.php
JFolder: :delete: Could not delete folder. Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/libraries/phpspreadsheet/vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Writer/Xls
Failed deleting Xlsx.php
Failed deleting Chart.php
Failed deleting Comments.php
Failed deleting ContentTypes.php
Failed deleting DocProps.php
Failed deleting Rels.php
Failed deleting RelsRibbon.php
JFolder: :delete: Could not delete folder. Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3
Joomla\CMS\Filesystem\Folder::create: Could not create folder.Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/admin
Copy failed: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/joomla_3/index.html to /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/admin/index.html

Als I get some notice messages.

image

What could the issue? Before I never had issues with JCB.

Best regards,

Arjen Schrijvers

I just installed Compnent builder on a fresh Joomla installation. Used the demo component to install. I get the error: JFolder: :delete: Could not delete folder. Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/libraries/phpspreadsheet/vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Writer/Pdf Failed deleting Parser.php Failed deleting Workbook.php Failed deleting Worksheet.php Failed deleting Xf.php JFolder: :delete: Could not delete folder. Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/libraries/phpspreadsheet/vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Writer/Xls Failed deleting Xlsx.php Failed deleting Chart.php Failed deleting Comments.php Failed deleting ContentTypes.php Failed deleting DocProps.php Failed deleting Rels.php Failed deleting RelsRibbon.php JFolder: :delete: Could not delete folder. Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3 Joomla\CMS\Filesystem\Folder::create: Could not create folder.Path: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/admin Copy failed: /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/joomla_3/index.html to /var/www/vhosts/acceptatie-server.nl/httpdocs/administrator/components/com_componentbuilder/compiler/com_demo_v2_0_3__J3/admin/index.html Als I get some notice messages. ![image](https://user-images.githubusercontent.com/3889668/111874958-9357bd80-8997-11eb-9a39-06d55d00dee0.png) What could the issue? Before I never had issues with JCB. Best regards, Arjen Schrijvers
Llewellyn commented 2021-03-22 01:06:31 +00:00
Copy Link

Joomla seems to have made changes to the File class, well that is as much as makes sense to me.

  • Please check the folder paths in the global options under the tab->folder paths
  • The check that Apache (user) has access to the folder JCB needs to write in and from

We had this issue here https://github.com/vdm-io/Joomla-Component-Builder/issues/682 and it was resolved... please check over the conversation.

Then I saw you send me a pro-member request... I would like to know did you get the last Pro-Member Newsletter that we now send out from sendinblue?

Joomla seems to have made changes to the File class, well that is as much as makes sense to me. - Please check the folder paths in the global options under the tab->folder paths - The check that Apache (user) has access to the folder JCB needs to write in and from We had this issue here https://github.com/vdm-io/Joomla-Component-Builder/issues/682 and it was resolved... please check over the conversation. Then I saw you send me a pro-member request... I would like to know did you get the last Pro-Member Newsletter that we now send out from sendinblue?
Schrijvers123 commented 2021-03-22 16:34:13 +00:00 (Migrated from github.com)
Copy Link

Thanks I will check later today.

"Then I saw you send me a pro-member request... I would like to know did you get the last Pro-Member Newsletter that we now send out from sendinblue?" Nope, I didn't received it. When was it send?

Thanks I will check later today. "Then I saw you send me a pro-member request... I would like to know did you get the last Pro-Member Newsletter that we now send out from sendinblue?" Nope, I didn't received it. When was it send?
Schrijvers123 commented 2021-03-22 21:51:39 +00:00 (Migrated from github.com)
Copy Link

Hi Llewellynvdm,

Issues solved.

The issue was that I was using Microsoft Edge Versie 89.0.774.57 (Officiële build) (64-bits)

After testig it in Firefox 86.0.1 (64-bits) it was working.

So I did some test with some browsers on Windows:

Firefox 86.0.1 (64 bits) working
Chrome version 89.0.4389.90 (Officiële build) (64-bits) Not working
Microsoft Edge Versie 89.0.774.57 (Officiële build) (64-bits) Not working
Opera 68 Not working
Brave Versie 1.21.77 Chromium: 89.0.4389.90 (Officiële build) (64-bits) Not working

My conclusies the only browser that is working on windows is Friefox. All Chromium based brwosers will cause errors.

Any idea why?

Best regards,

Arjen

Hi Llewellynvdm, Issues solved. The issue was that I was using Microsoft Edge Versie 89.0.774.57 (Officiële build) (64-bits) After testig it in Firefox 86.0.1 (64-bits) it was working. So I did some test with some browsers on Windows: Firefox 86.0.1 (64 bits) **working** Chrome version 89.0.4389.90 (Officiële build) (64-bits) **Not working** Microsoft Edge Versie 89.0.774.57 (Officiële build) (64-bits) **Not working** Opera 68 **Not working** Brave Versie 1.21.77 Chromium: 89.0.4389.90 (Officiële build) (64-bits) **Not working** My conclusies the only browser that is working on windows is Friefox. All Chromium based brwosers will cause errors. Any idea why? Best regards, Arjen
dformdotdk commented 2021-03-23 08:01:51 +00:00 (Migrated from github.com)
Copy Link

I've had similar issues on a localhost installation (Mamp Pro) on MacOS / Safari. The weird part is, I could try to compile 10 times and every time, the installation of the compiled component would fail, and then without doing anything, it would install. I will try on another browser, and also install a backup on my production server, and se if the issue remains there as well.

I've had similar issues on a localhost installation (Mamp Pro) on MacOS / Safari. The weird part is, I could try to compile 10 times and every time, the installation of the compiled component would fail, and then without doing anything, it would install. I will try on another browser, and also install a backup on my production server, and se if the issue remains there as well.
Schrijvers123 commented 2021-03-23 11:22:17 +00:00 (Migrated from github.com)
Copy Link

Let us know. Could be that some settings om Mamp Pro are not correct. Normal Safari has no issues.
Please check the folder paths in the global options under the tab->folder paths and check that Apache (user) has access to the folder JCB needs to write in and from

Let us know. Could be that some settings om Mamp Pro are not correct. Normal Safari has no issues. Please check the folder paths in the global options under the tab->folder paths and check that Apache (user) has access to the folder JCB needs to write in and from
dformdotdk commented 2021-03-23 15:02:51 +00:00 (Migrated from github.com)
Copy Link

I've tried using Firefox for a while now, and so far no errors. So at least in my end, the errors during compile/installation seems browser related, so perhaps a JS issue?

I've tried using Firefox for a while now, and so far no errors. So at least in my end, the errors during compile/installation seems browser related, so perhaps a JS issue?
Llewellyn commented 2021-03-23 22:06:29 +00:00
Copy Link

The fact that JCB works in Firefox and not in Chromium based browsers is yet unknown to me. This is an old issue actually and the outcome was that we all just USE Firefox in compilation of the of components.

Yet the fact that Chromium based browsers effect on server-side outcome is unacceptable, and concerning to say the least. This means as a localhost system Chromium is effecting the PHP classes. Since none of the files being build, or the data being generated is ever done with JS... ever. The button in the compiler area post to the controller on the server and from there it is all PHP, until the page reloads and shows the build outcome. So if any of you can show me where a browser gets the right to effect the permissions on the server we may have discovered a major bug/loophole in the Chromium based browsers.

The fact that JCB works in Firefox and not in Chromium based browsers is yet unknown to me. This is an old issue actually and the outcome was that we all just USE Firefox in compilation of the of components. Yet the fact that Chromium based browsers effect on server-side outcome is unacceptable, and concerning to say the least. This means as a localhost system Chromium is effecting the PHP classes. Since none of the files being build, or the data being generated is ever done with JS... ever. The [button](https://github.com/vdm-io/Joomla-Component-Builder/blob/staging/admin/views/compiler/tmpl/default.php#L153) in the compiler area [post](https://github.com/vdm-io/Joomla-Component-Builder/blob/staging/admin/views/compiler/tmpl/default.php#L55) to the [controller on the server](https://github.com/vdm-io/Joomla-Component-Builder/blob/staging/admin/controllers/compiler.php#L75) and from there it is [all PHP](https://github.com/vdm-io/Joomla-Component-Builder/blob/staging/admin/controllers/compiler.php#L96), until the page reloads and shows the build outcome. So if any of you can show me where a browser gets the right to effect the permissions on the server we may have discovered a major bug/loophole in the Chromium based browsers.
Llewellyn commented 2021-03-23 22:08:09 +00:00
Copy Link

I am closing this... but the conversation is welcome to continue...

I am closing this... but the conversation is welcome to continue...
Llewellyn commented 2021-03-23 22:09:35 +00:00
Copy Link

@Schrijvers123 please check your spam, since we did send out mails to the PRO members just last week.

@Schrijvers123 please check your spam, since we did send out mails to the PRO members just last week.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Beta

Issues related to the a beta release

  
Bug

   
Documentation

   
enhancement

   
help wanted

   
invalid

   
joomla

Joomla related changes

  
question

   
URGENT

   
wontfix
No Label
Beta
Bug
Documentation
enhancement
help wanted
invalid
joomla
question
URGENT
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: joomla/Component-Builder#703
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?