First of all, don't want to disappoint you but some of the stuff you plan here seems not that uncomplicated to me =)
Quote from: allan1 at Jan 27, 2013, 10:50 AM
The fishing club would like the members to be able to enter details of;
1. where and when they've caught fish and see their own catch records;
2. record when they've read a club notice;
3. post photographs etc.
Club Officers would need to be able to;
4. post notices;
5. store minutes of meetings;
6. send emails to members;
7. register new members;
8. View summary and specific catch record/member information.
1. I would probably go with a MIGX grid for that, so every user had it's own resource in the manager and there you somehow manage this information
2. You mean like a history with exact date when they clicked the "read" link (or something like that)? Actually don't have a quick solution or idea for this one, maybe over the modx internal message system? anyone?
3. I guess the photographs would be related to the catches right? so maybe it would be the easies to just add an inner MIGX grid (for images and descriptions, gallery like) to the catch MIGX grid, so users could add unlimited pictures to every catch (you can make it easier if you limit the amount of images allowed to 3 or so and then just add 3 image fields to the MIGX grid
4. This would somehow require a central notices management (maybe a custom migxdb setup?) ie. post a notice, viewable for all members and then have a row for each member where you can save read-date or so.
5. You mean something like an event calender/manager? Check out Charles mxCalendar extra
6. Probably also something to integrate into the notice addon, instead of notice you could just have a type "email" or so, then the notice gets sent as an email.
7. Then the "officers" need the permission to create new users, could also be done through the frontend via Login extra
8. Would gather the information needed out of the specific user resources, should this be available in backend or frontend?
Quote from: allan1 at Jan 27, 2013, 10:50 AM
1. I think I need 2 or 3 user groups who are going to be able to accees different features in different ways?
2. I think that means I need 2 or 3 different categories for resources/templates?(Do you create categories first or User Groups?)
3. Is it better to have a separete database for the 'extra' tables that are needed(catch returns, member details etc) or should I just add tables to the database MODx created
4. I'll be able to use 'eform2db' to update database tables?
5. Where one of the club officials wants to upload a document/create a new page and add it to a menu do they need to access the 'manager' screen or is there a way to automate it all?
6. If I wanted to create another MODX site for another domain would I need to plan that first or is it something that could be done after the first site had been built?
1. At least, depending on how you solve it =)...I see Administrator, Offiercs, Members. The members usergroup has then assigned all members (only a few permissions).
2. I think what you mean are resource groups (categories are more for internal organization of snippets, chunks etc.). Here you could create a separate resource group for each member (which somehow sucks in my eyes) or just a "member" one and then add all Member resources to that group. This would probably force you to have another authentification mechanism like a TV with username stored (for each member resource) so you can grant access to a single resource instead of all member resources (because permissions in MODx Revo are not user based, they are resource based) by checking if the logged in user has permission to access the resource (part of member resource group) AND if the userTV matches his username...
3. You can definitely add tables to the modx database
4. Like already posted before, eForm is only for Evolution. in Revolution there is FormIt that has custom hooks to do stuff like that (search for formit2db from bruno17) But the problem I see there is that you want to UPDATE database tables (that's what the manager is usually there for) and not CREATE db entries. I'm not sure if this is possible with formit2db. I think it just does ADD a new db entry for each form submission, and not update existing ones, that would require some custom coding too
5. Automate it seems difficult =), the self managing/creating website is not yet invented. Probably it's the easiest if the officers learn the manager interface, it's not so hard to understand and you can minimize clutter with form customization (ie. hiding all unnecessary fields). If you want to do it from frontend, I would suggest you have a look at the NewsPublisher extra from Bob Ray
6. This can easily be done later, so no need to plan this ahead. If you want a new one you just add a new context for that second site and set the context settings accordingly.
☆ A M B ☆