I searched the posts for an answer to this and haven’t come up successful. Please point me to the answer if this has already been answered.
I’m "shopping around" for a CMS package that can handle this. I’ve known about MODx for a few years now but never had a client to use it on so please excuse my ignorance.
I am producing a site where there will be roughly 200-250 users that will all need to have their own login/pass.
This will give them access to a section of about 10 pages that only registered users can see from the navigation and the site owner will create and update these 10 pages. I am gonna assume this is as simple as saying: registered=true then show X
The second part is that each user will need to have their own page(s) that will have data that only they can see. Like an account page, but instead of information like Name, Birthday, Favorite Movie, it’ll have financial data. They can’t and shouldn’t be able to change anything. The site owner will be responsible for adding this data to each user’s page(s) so they’ll need a way to easily update this.
The information is financial data so the security is of the utmost importance. If I can use SSL, even better.
Any help will be greatly appreciated.
-Mike
To add to above I have a snippet that reads the latest message out of an
e-mail box with a choosen subject line, so I can easily send news to each one
of my users private pages. The php comes from www.sottwell.com
I think there might be an easier way without webloginpe.
1. Create a Template with all of the fields the logged-in user will see.
- Create one Template Variable as a Dropdown List with an SQL binding that creates a list of every user. (called MemberName)
2. Create a page with this template (let’s call it ’Your Financial Data’
- Add a Ditto call here and filter away all where tvMemberName doesnot equal loggedinMember
- Create a Chunk for the layout of their info
3. In this directory, Create a page for each user and fill in their information
- and assign their member name via the tvMemberName
This would let the site owner use all the goodies of modx without having to deal with external tables and what-not. This probably sounds overwhelming, but the forums here are great and active. And this could be done fairly quickly if you knew modx well- I think 1-2 hours.
This is quite a lot to take in without knowing the terminology so I’ve already installed and began getting my design template going. I think that will help me understand the MODx speak a bit better. But I feel confident that MODx is the way to go with this project.
Using the ideas you guys have been kind enough to leave here, how does this sound as a solution (and if you know any plugins that can make/do what I theorize, please tell me)
1 - Create just one page that sniffs out the user that’s logged in and has fields of data placed on the page.
2 - Pull that data from a table in the system that will be populated by the sys user.
3 - The sys user can fill the table from a backend tool.
It seems that step 1 is easily doable using the MODx calls.
Step 2 would require a new table consisting of the new fields and the Member ID from the user and the system.
Step 3 is the tough one. I have no idea if there is any plugin that allows manipulation of a new table that I could hack to work for my purposes. I even thought that a completely independent third party app that could share database/table space with MODx might work here... but i don’t know of one. Any suggestions?
To add to the complexity, my client said today that he would want historical data available to the end user. By having a separate table, the records could be written as:
MemberID - Date - Info1 - Info2 - InfoN
The template page would be written to find all instances of MemberID = LoggedInMember and then sort on Date.
Plus, I feel more secure knowing that only this page touches this table from the front end and isn’t in the same table as other page data.
Would webloginpe be the "third-party app" in this scenario? Is it capable of what I need it to do? I’ll try to install it into my test site tonight and give it a try.
Again, I defer to the experts on this forum to comment/rip apart my theory and suggest ANYTHING you can think of!! (Can you hear the desperation in my voice!)
Thanks again gang!
-Mike
Since there is only going to be 200-250 members, I think it would be best to make each member a ’document’ instead of as a seperate table.
I say ’best’. I guess I mean easiest and most flexible.
example:
All People (1)
+ Johnny (2)
+ Sharon (3)
+ Bill (4)
Let’s say you need Address 1, Address 2, Address 3, City, and State for the users
You would create a text TV for Address 1, Address 2, Address 3, City and State
TV’s are just extra content blocks. Check the 2 threads in my signature to see more description (it took me a long time to understand them).
