Compile and Install Errors #757
-
|
I have been noticing some performance issues when Compiling. The result is always 'Successfully Compiled!', however sometimes the package appears incomplete and fails on installation. By incomplete, I mean that the 'Total Folders Created', 'Total Files Created', etc. are less than expected. For my current component, 'complete' is as shown with about 30153 lines of code and as shown. To 'resolve', I keep compiling until I see a package that is about the size I expect it to be. My first suspicion is that since this is on shared hosting I bump up on time limits, but I cannot confirm that - it just feels right. And before I move to a dedicated host, I wanted to see if there are others things to check. Has anyone run into this? I don't see anything on the Wiki or Discussions. Thanks! Running JCB version 2.12.9
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
There has been multiple issues opened about this in the past, which a quick search in the issues area would show. Most of them the problem was Chrome. Please only use Firefox for development, and then you should have a consistent experience. Should the issue continue, then check your environment that the folders and file permissions are correct. We have spend much time to make sure that we use best practice on this front. So 99% of the time this is not a JCB issue, either browser related (I know that sounds crazy -- but that is Chrome for you ;) or environment issue. |
Beta Was this translation helpful? Give feedback.
There has been multiple issues opened about this in the past, which a quick search in the issues area would show. Most of them the problem was Chrome. Please only use Firefox for development, and then you should have a consistent experience.
Should the issue continue, then check your environment that the folders and file permissions are correct.
We have spend much time to make sure that we use best practice on this front. So 99% of the time this is not a JCB issue, either browser related (I know that sounds crazy -- but that is Chrome for you ;) or environment issue.