static content pages
Locked
 
|
Hi,
I have what I believe would be a typical ecommerce site requirement where in a few pages are relatively static in nature such as "find out more" pages, "About us" pages, Policies pages and perhaps a few others. I see some implementation of the same in the demo ecommerce site. However, I would need these to be not 100% static but something that can be updated regularly by product managers i.e more like a CMS site which just a few pages with sections and blocks that can be updated, disabled etc on the fly. My initial approach is to use the ofbiz component to serve pre-saved HTML snippets to get the page. Instead of only 1 home page planning to have a few more for the navigation menus. I would also like to mount this directly as 'root' i.e '/' e.g www.mysite.com should bring up the home page. I understand that in ofbiz-component one can change the mount point. Am I on the right track? Would be interested in any best practices for such a thing. Thanks in advance Paul |
|
|
- static content is as long static as you do not change it :) the static pages (policies, factoides etc.) are database driven and can be changed about the admin interface (content ...). For these, or for new ones, you can define conditiones and places in your screens, ftl files where to show and when to show...i.ex. just to show in a specific category, or show random content from defined contents...
also you can extend the admin interface to make the admins live easier, that they can i.ex. just click that it shall be shown in the choosen categorie etc...but this I think you have to implement (not that much work). in your admin interface you have an interface to translate visual text / grafics etc. into html, that your employees do not have to know about html syntax etc...just a good, but small cms... for specific questions, please go ahead - mount point is changeable kindly robert
|
|
|
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 |
|
|
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
|
|
|
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." <[hidden email]> To: [hidden email] 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. |
|
|
Paul,
For the removing part of 'control' you can have a url rewriter filter which will remove /contorl/ part from all outgoing links and add it from all incoming requests. Use Tuckey for that in tomcat. http://tuckey.org/urlrewrite/ Simple config would be : <urlrewrite> <rule> <from>/(.*)</from> <to>/control/$1</to> </rule> <outbound-rule encodefirst="false"> <from>^/control/(.*)$</from> <to>/control/$1</to> </outbound-rule> </urlrewrite> On Wed, Jul 25, 2012 at 11:18 AM, Ritu Raj Lakhera <[hidden email]>wrote: > 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." <[hidden email]> > To: [hidden email] > 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. > > -- > Thanks, > Deepak Agarwal, > > Paxcel Technologies Pvt Ltd. > Hartron Complex, Sector 18, Gurgaon, India. > E-Mail: [hidden email] > Mobile: +91 9910322604 > > |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |