-
Display Namepranger
-
Member SinceJanuary 21st, 2022
-
Last SeenApril 20th, 2022
pranger does not have any add-ons for sale.
-
Support February 4th, 2022 @ 3:35 am
Ok I found it.
In php.ini, max_input_vars has to be very high. In my case, I have 60 projects with +- 5 project tasks each. Thats 300 lines, multiplied by 7 days, meaning I have more or less 2100 input variables.
I think this should be added to the documentation.
View Comment
-
Support February 4th, 2022 @ 2:51 am
Investigating further, I tried to enter time against every single one of my projects and it works.
So I tried to reduce the number of projects in the timesheet. It works with 31 projects or less, but not with 32 or more. It might also be the number of project tasks : works with 141 or less and not with 142 or more.
In php.ini all settings seemed fine (max execution time, max post size, etc) but I still rose everything with no change.
Now I don't know where to look anymore.
View Comment
-
Support February 4th, 2022 @ 2:10 am
I realize this error is not responsible for the timesheet not beeing saved. I juste copied the first error in the log. Sorry about that.
Still, I can't save my timesheet if "all projects" are displayed. And I can't find a relevant error in the log. I tried a quick repair wit hno luck. Any clue to where I should look?
View Comment
-
February 10th, 2022 @ 1:52 pm
We needed a timesheet for all our office employees to log time against client projects, sales tasks and administrative tasks. This module is very useful since it allows any users to log time against any project tasks, compared to other timesheets where users can only log time against tasks that are assigned to them. Another advantage for us is that all project tasks are displayed when you start a new week. On other timesheets I have tried, you had to select all the objects you want to log time against and start over every week. To reduce the time needed to create every client project, I created project models with their sets of subtasks, and then created workflows to create new projects based on these models, triggered every time an opportunity is won. Here are a few tradeoffs and enhancements I would like to see : -- The documentation does not mention, but you have to increase max_input_vars in php.ini. In my case, I have 60 projects with +- 5 project tasks each. That's 300 lines, multiplied by 7 days, meaning I have more or less 2100 input variables. -- There is no way to remove a single project task from the timesheet, whatever their status and dates. Only when projects are completed will they stop appearing in the timesheet. You could create "completed" projects to move project tasks if you want to remove single tasks from the timesheet. -- You cannot change the default first day of the week, which is Monday, and you cannot change the week numbering. I know, this could be customized by the editor. But for the pricing, most timesheet apps will allow you to change some basic preferences to fit your payroll software. Of course you could try and customize yourself, but it seems that parts of the code has been encoded. And anyways, I think this is a basic feature that should be included in any timesheet. -- There is no build in reports to extract time logged against projects. You need to build your own reports from the SuiteCRM Report module. And in the report module, some labels don't appear and you see the "field" names. And some labels are incorrectly named (Timesheet Entry Name = Project name, Timesheet Entry Description = Project task, etc). I know this can easily customized in the studio but again, this is not a free module : labels should be relevant. --The support seems dead. The pricing page says "Outstanding Support", but it's been 2 days since I asked a basic question and I got no reply. So overall, it's a very usefull module, and some enhancements should be made. View Add-on
pranger has not verified any add-ons.
pranger has not created any Wanted Add-ons.