More info for you:
When I re-installed v5.1.3-3 (KF6–I believe that is what was previously installed) from the ‘administrative’ archive to /boot/system/packages–kMyMoney works no issues and I see the plugins.
When I install v5.1.3-3 (KF5) to /boot/home/config/packages–that when the issues appears.
When I install v5.1.3-3 (KF5) to /boot/system/packages–kMyMoney works no issues and I see the plugins.
Hope this additional info helps
My guess would be that the plugins are not loaded when installed there (not visible in $PATH?), will check this localy, thanks on the feedback! 
EDIT: the plugins are installed in -DKDE_INSTALL_PLUGINDIR=$addOnsDir/Qt5 during build, I guess the binary won’t find them if they are “installed” in ~/config/non-packaged/add-ons, so best to install them in /system/packages (KF5 version probably won’t be updated so you should be clear on using it there).
Thank you for doing this…have a great week!
Probably only a display thing but I noticed that there are 2 slashes in folders between kmymoney and html.
There is still something wrong when installing this in ~/config/packages, KMyMoney is installed in $appsDir, when doing this above you’ll find the binary in ~/config/apps.
You can’t launch it directly from Terminal though, when installed in system it launches just fine in Terminal by typing it’s name …
Even if there would be something wrong in packaging, I think this should be included in default paths?
Not working from Terminal without full path given:
This location was added to $PATH about 5 months ago, but it’s only in the nightly builds. Beta 5 doesn’t include this change.
I am running B5 on both of my Haiku systems…no nightlies.
@ Begasus
Howdy!
I upgraded to H1B6 three weeks ago. I waited till now to see what else I should report after I checked out all the software that I use daily. My only gripe is with kMyMoney (v 5.1.3 [KF5])…it is missing a plugin to read the financial file.
It still opens fine in H1B5 (laptop), whereas, compared to the PC with the H1B6, it does not with the following message:
Refer to the next pic for the software installed that is now presenting the issue:
I remember we fixed last time–but I do not recall what we actually did to rectify the issue. I reviewed all the messages from our previous discourse–no clue how we fixed last time. So, I believe it was something you fixed code-wise.
Let me know if you require additional information.
Thank you beforehand!!
