Data at Your Fingertips: Explore Our New Reporting and Statistical Capabilities By Ryan Ashbrook Tuesday at 01:29 PM
roc13x Posted February 20, 2019 Share Posted February 20, 2019 Hi, I have a question about this 4.4 developer change: Quote Changed how share services, file storage engines, package types, payment gateways, license key generation methods, server types, converters, and widget types are loaded: instead of using a DirectoryIterator to look at what files are on disk, all of these are now defined in a method. To add a new one, you can (and will need to) extend the appropriate method, rather than having users upload a file to a particular location. I assumed this would allow third-party developers to store files for custom share services, payment gateways, license keys, etc. within their own application directory, and not require the user to upload them into specific locations anymore. Which would be a very welcome change 🙂 However, this doesn't actually work. The code still loads all these classes from hard-coded directories. For example, Commerce loads gateways with: $classname = 'IPS\nexus\Gateway\\' . $data['m_gateway']; Meaning that in practice, we still need to upload our custom gateways to /applications/nexus/sources/Gateway/ folder for it to work. I'm just wondering if this was the intended way of it working? Thanks Link to comment Share on other sites More sharing options...
Ilya Hoilik Posted February 20, 2019 Share Posted February 20, 2019 I reported this a week ago and today got notification that this will be fixed in 4.4.1 Link to comment Share on other sites More sharing options...
Daniel F Posted February 20, 2019 Share Posted February 20, 2019 Yea, we have fixed this for 4.4.1 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.