Hi, we would like to help asap - I talked to the teams about this – they need further information to deal with the problem: @Björn – could you please send us some code examples or (better still) the module that you wrote for the 4.8, showing your use of the "API-Safe PSR Autoloaders" so that we can see, how to adapt that to the 5.2?
Thanx and all the best, Ina Von: <Lange>, Björn <[email protected]<mailto:[email protected]>> Antworten an: <[email protected]<mailto:[email protected]>> Datum: Wed, 22 Oct 2014 07:59:30 +0200 An: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Betreff: Re: [oxid-dev-general] Core OXID eShop classes: must not be extended Good morning, To stop this thread from dying, i will escalate a bit. Sry if i'm to harsh .... Additionally to the "getInstance"-Removing from jkrug ... Am Dienstag, 30. September 2014 schrieb Lange, Björn : Hi Ina, Fixing some modules for oxid 49 ... 2014-08-27 13:07 GMT+02:00 Ina El-Kadhi <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>>: Hi Dave, glad u sort of like the idea :) As to the enforcing - we did not just want to plonk draconian measures onto everyone - spontaneously switching from "u can do everything" to "u must not ever do this thing" I think you just did. Without any further real notice you extended the list of "non extendable classes" and with oxid 4.9, i got an oxid version which disables whole eco systems of modules with a changed oxmodule* API (again) ... but to make it worse, you made the new API "private". I am still searching a way to (re-)enable "API-Safe PSR Autoloaders". I do not understand, why you announce PSR-Structures in the OXID-Core for new versions and disable custom autoloaders, which enabled this for modules since years (!) ... and this in just an "minor release". I think this is a major turndown for me and many other deep-involved-agencies to use OXID >= 4.9. "oxarticle => WBL_SEMFOX_App_Model_Article" is much cleaner in actual PHP Environments than "oxarticle => wbl/semfox/app/model/wbl_semfox_article" or some other variations. Correct me if i am wrong, but PSR is a declared goal of OXID itself, why disable it now - for people, who already use it? Please, make the new private API protected or add PSR-Module Support to the core in the next patch. Thx! Regards, Björn -- ______________________________________________________________ WBL Konzept GmbH Björn Simon Lange Geschäftsführender Gesellschafter Bilker Straße 34 40213 Düsseldorf Telefon: 0211 942 120 30 | Fax: 0211 942 120 32 www.wbl-konzept.de<http://www.wbl-konzept.de/> | www.facebook.com/wbl.konzept<http://www.facebook.com/wbl.konzept> | [email protected]<mailto:[email protected]> ______________________________________________________________ Registereintrag: Registergericht: Amtsgericht Düsseldorf, Registernummer: HRB 68990 Vertreten durch: Herr Daniel Beerden<mailto:[email protected]> und Herr Björn Simon Lange<mailto:[email protected]> _______________________________________________ dev-general mailing list [email protected]<mailto:[email protected]> http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
