WebERP 4.13.1 unable to list accounts and users

[R2-G]

Hi,

I set up WebERP 4.13.1 on a webhost and am getting the following issues

1. MAIN MENU --> GENERAL LEDGER --> ACCOUNTS fails to display the list of accounts and gives the warning message below:

Warning: Invalid argument supplied for foreach() in H:\root\home\mburumn-001\www\FINALWEBERPAPP2017\GLAccounts.php on line 334

and the screen looks like this:



Same thing happens in MAIN MENU --> SETUP --> USER MAINTENANCE
where the list of existing users fails to display and a warning issues

Warning: Invalid argument supplied for foreach() in H:\root\home\mburumn-001\www\FINALWEBERPAPP2017\WWW_Users.php on line 352



Any assistance greatly appreciated

R2-g

[VortecCPI]

This may help: http://www.weberp.org/forum/showthread.php?tid=3320

[R2-G]

This may help: http://www.weberp.org/forum/showthread.php?tid=3320

Thanks a whole bunch VortecCPI, the solution in the thread solved the issue.


R20g

[TimSchofield]

Would be great if somebody committed this fix to svn.

Tim

[VortecCPI]

This may help: http://www.weberp.org/forum/showthread.php?tid=3320

Thanks a whole bunch VortecCPI, the solution in the thread solved the issue.


R20g

You are very welcome. Happy I was of some help.

---

Would be great if somebody committed this fix to svn.

Tim

Since this is an error in the source code why not an incremental/update patch by the webERP development team? Users may not know anything about SVN and, in my opinion, should not have to deal with such a thing to have a working instance of webERP.

I say this will all due respect but I would never expect my customers to install and learn and fiddle with SVN in order to have a working instance of one of my applications. However, I do realize this is an open-source application and things are different.

[TimSchofield]

Updating the subversion repository is a precursor to it being released.

When I was admin we used to have a stable branch on subversion which contained the previous release plus any bug fixes that had come up since then, but none of the new features that had been added. I have tried to persuade someone to take on managing a stable branch but enthusiasm is low.

Tim

[VortecCPI]

Updating the subversion repository is a precursor to it being released.

When I was admin we used to have a stable branch on subversion which contained the previous release plus any bug fixes that had come up since then, but none of the new features that had been added. I have tried to persuade someone to take on managing a stable branch but enthusiasm is low.

Tim

I agree on that approach. Bug Fixes can be (and should be) addressed apart from Feature additions/deletions/updates.

From what I have seen so far this is a very good product and I think it is a bit of a shame current and potential future users can not easily retrieve a latest "fixed" version. Imagine the initial impression when a tester implements webERP and it immediately fails on something as simple as a list? It will be immediately discarded and that is just a shame.

Unfortunately users don't remember how great 99% of the product is; they remember that 1% that threw them into the ditch and this is a good example.

My applications are not perfect as every Use-Case and every permutation of code path can not be identified therefore can not be tested. However, when an issue does arise it is addressed IMMEDIATELY and a new version is released, often within a few hours.

Again, I must close by adding this is OSS and there is often a small price to be paid since there is no other price being paid (apart from time). We use MANY OSS solutions and have been very happy. I hope webERP ends up in our OSS bucket.