CMS Made Simple Forums

Just launched my new site - Babel - using CMS 1.2.2.

I made a couple custom modules for it.  One allows FrontEndUsers to submit and edit Lesson Plans.  The other allows FrontEndUsers to create Web Quests (mini webpages for use in the classroom).

I played with the News summary template a bit, so that now the title links straight to a content page.  This way the news articles are simple stubs for new content pages, which seemed more useful than a "Detailed" version of the news article.

Otherwise, haven't modded anything too heavily.  Make use of News, FrontEndUsers, SelfRegistration, CustomContent, and Uploads.

- Walkere

Looking good,

2 small remarks, you can loose the "Print this page"-text next to the print-icon, by restoring the printing template in "Content -> Printing -> Link template" and then "Reset to default" and "Save template".

The other is that the links that have H2 arent quite visible, as you underline both H2 and the link, like on the main-page with "Browse lessons plan".

Ronny

I like it, looks good to me.

Good site!!! Keep it up!

You were able to use article-name.html pretty url with the blog/news?? Have you tried it with 1.2.3?

Nice!  Great example of showing off the power and flexibility of CMSms.

@giggler:

I played with the News summary template a bit, so that now the title links straight to a content page.  This way the news articles are simple stubs for new content pages, which seemed more useful than a "Detailed" version of the news article.

Looks like he just modified a template to get that working like that.  Nice idea, I had something similar going around in my head, but only and idea.  Hadn't looked into how to get it done, thanks for posting.

Oh and it looks like it's running 1.2.3 from the footer.

Nice

I have a question, how did you implement the Webquests?

so it's actually just a regular content page?

Hey all,

Sorry I've been working a lot on a different project.  Didn't notice there was any interest in this... =)

@nivekiam

100% correct.  I write up the standard content page (which has the pretty url).  Then, I modified the news template and write a News article stump for it.  I added a custom field with the page id #, and use that for a cms_selflink tag in the template.  That replaces the normal link that would go to the "Detailed" viewed of the news entry.

@giggler

Yup, just a regular content page.  Check out this post in the Tips and Tricks forum.  It explains how I modified the news template to do that.

@hexdj

I wrote my own module for the Webquests, which depends partially on FrontEndUsers, Uploads, and the MenuManager stylesheet.

The user can log in and fill out a form to create the webquest.  The information gets stored in the DB.  Here's the basic DB structure...

Webquest - quest_id, title, description, and other basic info
Page - page_id, quest_id, title, content, menu_order
Attachment - attach_id, page_id, title, url

So when you first create the webquest, you create an entry in the Webquest table.

Then, as you fill out information for extra pages, new entries are entered into the Page table.  Each one is linked to the same quest_id with a unique page_id and an int that helps order the menu listing.

When you view the webquest, the server fetches the basic info from the Webquest table and then all of the individual pages attached to that webquest.  Based on the pretty-url, it knows which one is the active page.  The module makes a list of the page titles with links which are used to build a menu.  The content info for the active page is displayed, along with any attachments linked to that page_id.

If you're interested, I'd be happy to share the source code.  No guarantees that I can help you understand it tho =)

- Walkere

I'd love to see the source.

Nullig

Alright, I posted the source code for the two modules I wrote.

You can find the source code for the User Generated Articles module here.

You can find the source code for the Web Quests module here.

They're both functional on my site, but I can't make any guarantees that they'll be easily portable or easy to understand.  I started out trying to comment well and make it adaptable... but by the end I may have gotten frustrated and taken a few shortcuts =)

Good luck.  At some point, I intend to turn the two pages (linked to above) into a homepage for the modules with documentation.  But at the moment it's more or less just the source code for your enjoyment.

- Walkere