There should be no widget definition for screens other than a decorator when using the CMS - that's kinda the point.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595


On Jun 22, 2008, at 4:34 PM, Bruno Busco wrote:

Many thanks,
it seems the "content" and "sub-content" widgets must be used to put a
content from the CMS on a screen.
-Bruno

2008/6/22 Jacques Le Roux <[EMAIL PROTECTED]>:

Bruno,

Maybe the screen policies in
applications/ecommerce/widget/CommonScreens.xml is what you are looking for
?

There are not much examples, you may also look for content-id in
*screens.xml
Jacques

From: "Tim Ruppert" <[EMAIL PROTECTED]>

Yeah - the CMS rendering on the backend is not working as far as I know -
so I stopped using that a while back. I've got a site based on it though, but it's not exactly simple to describe how it's setup. I believe that
there is an example in the demo stuff which is how mine  got built.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595


On Jun 22, 2008, at 10:26 AM, Bruno Busco wrote:

Tim,
many thanks for your help.
The way you indicate is exactly how I am doing it right now. But, I
guess,
this is not the CMS way of doing it.
I mean, what I was looking for, is the steps to have an HTML page loaded
in
the DB from the content application UI and served at the url
/ecommerce/control/cms/xxxxx

Many thanks anyway
-Bruno

2008/6/22 Tim Ruppert <[EMAIL PROTECTED]>:

I just:

1. Make a screen using the ecomm decorator with a name like "aboutus" 2. Then I have a small piece of HTML in an FTL file that gets rendered
like
this:

<screen name="aboutus">
    <section>
        <actions>
            <set field="leftbarScreenName" value="leftbar"/>
            <set field="MainColumnStyle" value="center"/>
            <set field="title-property" value="PageTitleMain"/>
            <set field="headerItem" value="aboutus"/>
        </actions>
        <widgets>
            <decorator-screen name="main-decorator"
location="${parameters.mainDecoratorLocation}">
                <decorator-section name="body">
                    <platform-specific>
                        <html><html-template
location="component://project/webapp/project/snippets/ aboutus.ftl"/
</html>
                    </platform-specific>
                </decorator-section>
            </decorator-screen>
        </widgets>
    </section>
</screen>

Pretty simple. This will do something static - but mostly I drive them
from the db.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595



On Jun 22, 2008, at 9:14 AM, Bruno Busco wrote:

Since I only needed few pages I would have been more than happy to use
the

OFBiz embedded CMS.

But I cannot make a single page appear anywhere...:-(
...and no help, not a single how-to...
...has anybody ever used the OFBiz CMS out there?

Does anybody have a list of steps to have a simple static HTML
rendered
with
the same ecommerce style?

Many thanks for any help,
-Bruno


2008/6/16 Adrian Crum <[EMAIL PROTECTED]>:

Using Drupal or some other CMS with OFBiz is common.


We use Drupal for our public facing site, but it is not connected to
OFBiz.

-Adrian


Bruno Busco wrote:

Another option that I am considering is to use Drupal as CMS and link
it

to
the OFBIz ecommerce. I have already used Drupal and OFBiz is already
running
behind Apache with PHP and MySQL.
So it should be quite simple to go on this solution but I would
prefer
to
use all functionality offered by OFBiz.









Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to