I have an application that creates a custom commerce package, extending \IPS\nexus\Invoice\Item\Charge. Up until the latest update it worked fine, but since the latest update the ItemsIterator expects all extensions to be in the 'nexus' application, and therefore cannot load the class of my package object. 

How it works now, I don't think its possible any more to create custom chargable items, but I desperately need this functionality.

Edited December 1, 20231 yr by Callum MacGregor

I don't recall anything being changed in that class recently. 🤔

The best option is to ask the developer who made it for assistance. Since you're posting here I assume they're no longer available?

Edited December 1, 20231 yr by teraßyte

Its my own application. For a bit more information, in the admincp the extension does show up as expected:

 

However, I logged what ItemsIterator collects from \IPS\Application::allExtensions call, and my extension is no longer listed there:

Is your extension listed in your /applications/<app>/data/extensions.json file?

If not, adding a dummy extension and deleting it will recreate that file with the correct extensions.

32 minutes ago, teraßyte said:

I don't recall anything being changed in that class recently. 🤔

The best option is to ask the developer who made it for assistance. Since you're posting here I assume they're no longer available?

4.7.12: 

 

You will have to add an extension, anyone, just to the system create the extension.json for you.

9 minutes ago, Stuart Silvester said:

Is your extension listed in your /applications/<app>/data/extensions.json file?

If not, adding a dummy extension and deleting it will recreate that file with the correct extensions.

I don't have an extensions.json file, its an old application. I'll try and create it myself.

Attach the app folder downloaded via FTP on a private message. I’ll make it within a couple of minutes for you, if that’s the only problem.

I got it working now. Thanks @Adriano Faria for offering to help.

I had to create a dummy extension in admincp, then the extensions.json was created correctly.

This is exactly why I am so reluctant to upgrade Invision to newer versions.