visualcohol

"Out of sight is out of mind" - You never ever hide or runtime-modify the menu unless it is absolutely necessary (mobile etc). In case of the web: design is not only aesthetics! Absolute UX nightmare - its the time of design when everything can and should be measured and researched - do some testing on the issue

Thanks guys. I solved the problem, by implementing a front-end authentication class, so the site users are separated from the CMS, but its great fun to have a such quick and robust back end. As you mentioned, it depends on the time someone has on a work, as this is a community project tinkering with PHP was ok. I think PW would benefit from a better user management - (authentication, quick management, active/not and fields), as this can be a cornerstone of some sites. I tried to play around PW users trough API, and I did not find it very efficient - nor extensible (some 3rd party softwares do not handle well this kind of fragmentation of user data) Anyway thank you

Hi. I'm new to this CMS, but truly love some of its solutions. I'm about to build a community website, with a wiki a forum and some other stuff we can come up on the way, i was using pyrocms lest time, but i wasn't very happy about how Codeigniter made the development difficult. Now, in the last days I made a quick user registration front-end for PW, but iv got concerns about its capabilities. I plan to use PW mainly as a user management and sorting platform for other systems (no blog in sight yet), and since this system absolutely doesn't emphasize these features (no sorting, fields, management of users, no registration etc.), I might be wrong choosing it. I'm not concerned about missing features since I love to solve problems, my concern: Can this system handle thousands of users/related pages/numbers of posts etc, can it be scaled up without problems, registration, activation, or am I on the wrong path? Anyone has any experience? maybe its not built for such tasks Thanks