And how about multiple {content} and {image} on the page? Isn't really that hard that it seems?
And where is {image} block anyway?
And how about multiple {content} and {image} on the page?
-
Gomes
And how about multiple {content} and {image} on the page?
Happy New Year!
And how about multiple {content} and {image} on the page? Isn't really that hard that it seems?
And where is {image} block anyway?
And how about multiple {content} and {image} on the page? Isn't really that hard that it seems?
And where is {image} block anyway?
-
uptoeleven
- Forum Members
- Posts: 96
- Joined: Sat Dec 04, 2004 10:30 pm
possible solutions
I don't think they want to have support for multiple content objects as part of the main page per se.
It might be possible to create content blobs or something like that but CMS Made Simple is supposed to be a simple CMS to work with and a vast array of bits of page that can have content would be complicated. There may be a simple and well thought out way of achieving this but it would have to be very well designed so that it's dead easy to work with.
It might be possible to create content blobs or something like that but CMS Made Simple is supposed to be a simple CMS to work with and a vast array of bits of page that can have content would be complicated. There may be a simple and well thought out way of achieving this but it would have to be very well designed so that it's dead easy to work with.
And how about multiple {content} and {image} on the page?
Multiple {content} blocks is definatly on the short term list. I think it's absolutely necessary for people that want to support many users with a complex site layout. This way, users can just defined the content in individual places of a template (read: specific s), and the admin doesn't have to worry about them styling it properly.
The content rewrite that happened in 0.8 was mostly for this purpose. It would have been next on my list of development issues if I didn't feel the module API rewrite was more important to do now before we gained much more popularity.
The content rewrite that happened in 0.8 was mostly for this purpose. It would have been next on my list of development issues if I didn't feel the module API rewrite was more important to do now before we gained much more popularity.
