|
Thiago Campos Viana
|
Friday 10 September 2010 12:14:32 pm
I was thinking, the step that could cause a php max execution time error, in most cases, is when eZ publish starts to download the packages that the user choosed. So I suggest to distribute eZ publish with all packages needed to make an eZ Flow / eZ Web Interface with content installation, this could be a flawless distribution that could include zeta components ( ez components ) too. So, the installation could be quicker. I think it could also minimize ez.no bandwich, because doing so, it will not be necessary to download all packages from ez.no every installation, we could just unzip and voilà! We have all we need to make the basic installation.
eZ Publish Certified Developer: http://auth.ez.no/certification/verify/376924
Twitter: http://twitter.com/tcv_br
|
|
SEBBANE Alexandre
|
Saturday 18 September 2010 8:38:48 pm
Hello, i was thinking exactly like you when i found the example which make me change my mind : the first is that you can also make your import as in the exrowecommerce project :
[RepositorySettings]
RemotePackagesIndexURL=http://packages.xrow.com/xrowecommerce/latest
RemotePackagesIndexURLBase= and the second reason is that if you know how many packages are docnload you know as well how many installation is made so it is important for ezsystems i think Bye Alex
Paris, France
|
