)
and comments/rating per artwork.
☆ A M B ☆
☆ A M B ☆
I’m actually in the process of making one now... I’m using several snippets together to create a completely editable page by a member but I’m having some issues with completing the project. I’m waiting on some help through the forums just now.
So far what I have... A new member signs up and is allocated a page of their own that only they can edit. I have created a few fields so far but choices are endless. Name, age, interests, an area to use html elements like images and flash. What I need to do is get an upload feature that allows a user to upload images etc to their own folder so no one else has access to it and I need to sort out the tinyMCE editor a little as well. So far, it’s looking pretty good but still hoping to get some more help with it. Once I manage to get it sorted, I’m going to create a tutorial with all the details on how to create your own.
MODX Staff
I always weigh the options of trying to use a simple set of TV’s to store data like this versus creating my own data model. But I generally tend towards the build a custom data model, and if I need to expose or manage some of that data via a TV, I can do that via plugins most of the time (i.e. updating custom table records or updating TVs from custom table records).
Rossco, I’m looking forward to hearing more about your project. I have a few projects that I plan to incorporate social networking aspects, and I’m new to modx. I like what I’ve seen so far, and I’m "practicing" by rebuilding my own site. When you say that you’ve created "few fields," you mean that you are just creating TVs for member usage, correct? One thing that I’m trying to wrap my head around is the use of a relational database for something like this. A good example might be something like an author community, where each individual can post multiple books. From the DB perspective, how would that look? If it were just one book per person, I could just create a TV called "book." If I were programming from scratch, I’d have an authors table and a books table, along with a join table. What’s the most appropriate way to create this in modx?
Sorry for such a newbie question, but I’m hopeful that with a couple of answers to questions I haven’t quite figured out, I’ll be on my way to building some decent stuff.
I always weigh the options of trying to use a simple set of TV’s to store data like this versus creating my own data model. But I generally tend towards the build a custom data model, and if I need to expose or manage some of that data via a TV, I can do that via plugins most of the time (i.e. updating custom table records or updating TVs from custom table records).
Creating a solid model for your application helps it stand on it’s own while providing easy ways to integrate it with MODx. And BTW, I wrote xPDO to make this even easier, providing O/R mapping with ACID/CRUD scaffolding as well as separate domain classes (much better IMHO than the all-to-common ActiveRecord-only approach popularized by RoR) for any MySQL data structure you need to work with (will soon support PostgreSQL and SQLite, and others are possible since it is built on top of PHP’s PDO layer). Design your tables, create a quick reverse-engineering script to create an xPDO schema of your tables, then forward-engineer the Domain and ActiveRecord classes plus the xPDO O/R maps you need to start working with your data easily in a matter of seconds.
I always weigh the options of trying to use a simple set of TV’s to store data like this versus creating my own data model. But I generally tend towards the build a custom data model, and if I need to expose or manage some of that data via a TV, I can do that via plugins most of the time (i.e. updating custom table records or updating TVs from custom table records).