Forums / Developer / why is ezp_extension.php under var/autoload in 4.1?
zurgutt -
Friday 15 May 2009 11:19:56 am
Could someone explain this? Seems counterintuitive.
Certified eZ developer looking for projects. zurgutt at gg.ee
Łukasz Serwatka
Saturday 16 May 2009 2:03:52 am
Because it is a file which change when you are activating an extension or installing an extension. So it is quite logical to keep it in var/ as data is updated more often then for example autoload/ezp_kernel.php which should not be change as long as you don't add new stuff to kernel. Are you experiencing any problems with it?
Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Damien Pobel
Saturday 16 May 2009 6:02:30 am
Hi,
there were some discussions on sdk-public mailing list in February 2008 on this subject :http://lists.ez.no/pipermail/sdk-public/2008-February/thread.html#2731
Cheers
Damien Planet eZ Publish.fr : http://www.planet-ezpublish.fr Certification : http://auth.ez.no/certification/verify/372448 Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish
Gaetano Giunta
Monday 18 May 2009 12:11:53 am
Not only it is updated more often, but it "can" be updated by ezp itself. All files that can be modified by the system are in the var folder.All the other folders you can chmod 644 for added security...
Now, the real question is rather why ezp_kernel was not out in /share but in a new dir...
Principal Consultant International Business Member of the Community Project Board
Tuesday 19 May 2009 11:53:30 am
I had permission-related problem with it that is covered in http://issues.ez.no/IssueView.php?Id=14923&activeItem=12 and just was wondering. But i see your point. And yes, if that was removed from /autoload then kernel file should be too, why keep directory around for one file?