Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
Hi,
We have updated ProjeQtor following the procedure and technical recommendations:
- Version 8.1.8 to version 9.5.5
- Version 9.5.5 to version 10.0.6
On versions 9.5.5 and 10.0.6, we encounter a problem when calculating schedules when checking "All projects".
In the logs, we have the following error:
2022-09-14 08:00:11.659 ** ERROR ** [V10.0.6] ERROR **
2022-09-14 08:00:11.659 ** ERROR ** [V10.0.6] on file '/var/www/html/model/PlannedWork.php' at line (1947)
2022-09-14 08:00:11.659 ** ERROR ***** [V10.0.6] cause = Undefined property: GlobalPlanningElement::$_profile
We encounter this error with all the profiles authorized to calculate schedules.
If we select one or more projects and sub-projects, we don't get any error.
Thanks for your help
Hi,
By checking the calculation project by project, I finally found out why we had this error.
When milestones are closed but not the items they were attached to as predecessors blocked the calculation.
I reopened the closed milestones and we no longer have the error.
We'll have a look at the issue.
Thanks for pointing out the workaround, it will help us reproduce the issue.
Hi,
On ProjeQtor DEMO, I reproduced the problem with the project "12547-error-planning" (gestionnaire profile).
We have a recurring task (Task A) with an assignment and 2 predecessor milestones:
- Milestone "Jalon A": end-to-end / closed state
- Milestone "Jalon B": end-start
At the planning claculus, we have an error :
In order not to block the DEMO, milestone "Jalon A" has been reopened.
Thnals for the additional information.
Added as note on the ticket.
Same kind of error here when calculating :
ERROR : Undefined offset: 1
in projeqtor.php
at line 4714
--
Bena
Same kind of error here when calculating :
ERROR : Undefined offset: 1
in projeqtor.php
at line 4714
This is absolutely not same isse.
Your issue is just a case we did not take into account : you entered the Memory limit in php.ini as bytes.
Most configurations use K or M or G units.