Frog CMS

actually i was thinking the custom fields or 'parts' in frog could make it like other sites like drupal but no. the custom fields will not allow you to grab a listing of that content type. you are still limited to the page.

that means if you do a custom field or 'parts' that create a ontent type called restuarnts for example. you can' t pull out a list of restaurants, list them alphabetically and so on. you still only have pages. each restaurant will have one page and that's all you get.

so no actually wordpress and frog cannot handle this requirement. am i correct in saying so?

I can't think of how Frog could do this, but I haven't given it much though, either. :)

The best tool I know of for doing this kind of thing is Symphony, in fact it excels at it. It uses XML/XSLT/XPath, and makes pulling all such "bits" quite straightforward.

I love using Frog -- but it possibly isn't the right tool for every job!

Hmmm, David, you've almost convert me to Symphony ...

@ricks - I'm not entirely sure what it is you want/need, but it sounds as though writing a plugin for this kind of thing wouldn't be too difficult. Especially since I've gotten some practice on Frog programming lately. :-)

Could you perhaps give a more extended example of what you want?

@aozuas - Your request seems to be different from ricks, but I'll try to answer...

Assuming you want the same content in your "position" tab, check out David's remarks at this post: http://forum.madebyfrog.com/forum/topic/407#post2253 Also see Philippe's reply at http://forum.madebyfrog.com/forum/topic/57

If you want the contents of the "position" tab to be different, but you just want the tab to be pre-created... that's currently not possible I think.

@mvdkleijn : "If you want the contents of the "position" tab to be different, but you just want the tab to be pre-created... that's currently not possible I think." I just did some experimenting. It seems to be the case that if you create a child page, it has the same page-parts as the last created/saved page for that parent.

It seemed to happen consistently. It would be interesting to know what happens for others here.

@aozuas - sorry you didn't get your question answered! I don't think you want the same thing as Ricks, at least not what you describe in posts ##1 and 10! :) Try this:

• create your "child" page, create the "position" tab/page-part, and save it.
• try to create another child page for the same "parent" -- and the new page you get should have both the "Body" tab and the "Position" tab already to go.

Let us know how it goes!

It was surprising to see the siblings inherit the parts, but I think it makes sense. Thanks for the heads up on the parts inheritance. That will make it easier then, yes.

I guess the way it is now you can do quasi-content types. Then the only thing you need to do is write a plugin that will do the SQL query to search for the quasi-content type within the pages table, which you can identify by the unique combination of parts. A join table would be nicer, but I guess this would work.

Once you can look up all the restaurants, for example. you can then list them all one one page by name and location or whatever you want.

Restaurant listings are one example. Events are another example or staff members. I'm sure you can think of others. Generally it's nice to be able to do listings of a content type and then each of those listings goes to their own page. So a staff member woudl be listed on the general staff page, but when you click on his name it goes to his page that shows is biography or whatever. That's the basic idea behind having different content types. This way at the point of capturing the data, you can just fill out a form (or if we can't have a form, using tabs/parts), and don't worry about the rest of the page, because it all comes from a template. This behaves more like a database-driven website.

In Drupal. everything is a node, but they allow different content types, which then get their own join table, pointing back to the record in the node table. Maybe it's possible to treat the pages table in Frogs sort of like nodes in Drupal?

@Philippe - I think what ricks wants is this: if all sibling (brother/sister) pages have the same part, called for example "Name", then having a way to pull all the "Name" parts only out of all their pages, to be displayed on one single (different) page. A bit like "tags", but using page-parts instead.

Does that make sense? And have I got that right?!