Freelancer
Well-known member
Okay, installed today. Great new features. It does come along well. New permissions and a progress bar as well as user roles. Still a lot of essential things missing, but I am not impatient, let my try to help...
Here are some bugs I found so far:
Here are some bugs I found so far:
- After uninstall and fresh install, old templates were still present. I had to delete (revert) the old templates to get it cleaned out.
- All "CallToAction" buttons (upper right corner right to the breadcrumb bar) do have "primaryButton" classes instead of "CallToAction" classes (mind the "<span>" tag that needs to be included as well). If I remember it right, i reported that in in the v1.0.0 version as well.
- Missing phrase in the Error Modal when you leave away the "Project Description" while generating a project.
- Projects User Page: A User's projects are listed but doubled and tripled.
- The class ".task" is not used, I wonder what that was for.
- Tags
- Alerts
- "Projects" Tab on Member Profile View
- Conditional visibility of "Projects Count" on Member Profile View and Member Cards (No projects = no visibility)
- Complete Meta Controls on Task Comments (approval, report, like, etc)
- "Report" function in general for projects (Report Projects, Report Tasks, Report Comments)
- Project Icons in the sidebar (Latest Projects)
- At some places the correct XF hierarchy of CSS Classes – instead of inline-styling (sorry to say) – for example the sidebar list items.
- Task Icons (in general)
- Task Icons customizable
- Task Icons in the sidebar
- Category description ON HOVER (tooltip) on desktop (category description solid if on mobile)
- Plus my suggestions from above: Projects Manager - ThemesCorp.com [Paid]
- I don't 100% understand the correlation of the "Can view category" in Category Setup in combination of the User Group Permissions. There you have – under Moderator Permissions – "Can view all Categories"... is this redundant? Or is this an override to the Category Setup?
- The User Roles (User, Co-Leader, Leader) are nowhere separated, so I don't really understand the difference in permissions. It looks like it is only a cosmetic name change. For example, "invite users" could be restricted to Leaders and Co-Leaders only, while deleting a project should be allowed to leaders only. I dont see that this is covered as it is now. To my understanding I would need to make separate user Groups in XF Core to have "Leaders, Co Leaders and Users" have different permissions. Which is not very desirable...
- I would propose to have "inline roles" for Project Manager – of what can be allowed – for every project. That is flexible and makes great sense, since every project can be different. Then you just need cover who can access categories.
- How are Threads and Forums be handled if someone has no access to a project/category?
Last edited:
