Hi Paul, 1. Static page can be handle by content and we can make active and inactive the content, you need to simply create a controller entry which will render the content. Header and footer can be render from content so you can simply add the static pages link under header and footer. BigFish accommodate all this type of content requirement (http://bigfish.salmonllc.com/bfDemo.html).
2. I think creating the different component for populating the catalog is not a right way. You can handle this requirement using the SEO friendly url functionality which all already implemented in BigFish. Rendering static pages as friendly url is in development queue. BigFish is free to use.I think that will help you. Regards Ritu Raj Lakhera ----- Original Message ----- From: "Robert G." <[email protected]> To: [email protected] Sent: Wednesday, July 25, 2012 10:12:00 AM Subject: Re: static content pages Hey Paul, 1. the content thing, check the boxes like "factoids", then you understand well, how it works...quite easy at the end 2. URL: Sorry Im still in development and had not focused on that, so I cannot really help. I just read this question here often and read the answer, that you can change the mount point. To choose different catalogs in ecommerce system is allready implemented (check http://demo-stable.ofbiz.apache.org/ecommerce/control/main at the top-left...) changing the url to catalog is maybe possible with multiple shops, which you can fill with products of your warehouse...than you get this pattern. But you can also do it maybe easier, that you do kind of url redirect...but Im not into it... to remove the "control" pattern, I think this is also possible, but than you have to hold in mind, that all requests to your TLD: http://www.xxx.com/**** have to be redirected to the controller.xml, so you have to handle each request with that. If you have other applications on the server which are called with i.ex. http://www.xxx.com/otherapplication/andsoon than you have the problem, that even this is runinng over your controller.xml... kindly Paul wrote > > Hey! Robert, Thanks a bunch. Concur on the dig on static pages ;-) > > Well, I think I can set up 4-5 required pages easily with a combination of > content and ftl. At least for now looks reasonable. Will know more when I > actually try it. > > Meanwhile notice that the URL takes the typical > application/control/request pattern. For example the polices page URL > becomes ecommerce/control/policies > > Since I am planning to mount ecommerce as root e.g. > http://<myecomsite.com>, is there a way to keep the URL for policies page > as http://<myecomsite.com>/policies i.e. without the control/ part. > > In fact rethinking as I am writing this down. > http://<myecomsite.com> Regular Landing page of ecommerce (main without > the /ecommerce/control/main) > http://<myecomsite.com>/policies > http://<myecomsite.com>/aboutus > http://<myecomsite.com>/contact > > Since I am planning multiple catalog and plan to have them as menus on the > home page, so once the user clicks on a particular catalog that becomes > the selection and the navigation changes to > http://<myecomsite.com>/<catalog-name> > I am considering creating ecommerce clone for each of the catalogs with a > catalog-name as the mount point. > > This is a whole lot of questions, and thinking aloud here. However, will > this work? I am still unclear how to handle the root mount point with a > few cms style pages right under root without the trailing control/ URL. > Perhaps I should create a new component with a different controller (like > in products in ecommerce) and not touch ecommerce. The new component can > then be mounted a root and act as the cms. > > > Thanks a bunch in advance > Paul > -- View this message in context: http://ofbiz.135035.n4.nabble.com/static-content-pages-tp4635197p4635208.html Sent from the OFBiz - User mailing list archive at Nabble.com.
