Applications within Concrete5
Permalink
So I have an application that needs a CMS to act as a front end. This would allow the customer to control the website, and have the application appear as a function of the website.
As the application is moderately sized, and currently has multiple zend modules, I cannot figure out where it would fit into Concrete5. It certainly is more than a block and a page, so can someone point me to some documentation about how to integrate my application into Concrete5?
Thanks
Joe
As the application is moderately sized, and currently has multiple zend modules, I cannot figure out where it would fit into Concrete5. It certainly is more than a block and a page, so can someone point me to some documentation about how to integrate my application into Concrete5?
Thanks
Joe
you would have to modify your app a bit to follow how c5 does things, but most apps start with single_pages, singlepages can make most things happen, then there are tools, they do everything that doesn't fit anywhere else
Yeah, I am comfortable with the idea of changing the app to work within the structure of Concrete5.
Thanks for the hint on single pages, I think that those are a good place for me to start. I can try to map my modules to single pages and see how that works out.
1) Could / should bundle them together as a package?
2) Currently the app has 24 tables, is db.xml still the preferred method for database connectivity? and does db.xml have the option for defining a table prefix?
3) Can .htaccess files be configured to exclude a directory from concrete5? For example, i have a websitehttp://www.example.com Concrete5 is installed in the root. Can I exclude /application from concrete5 handling so whatever code is in /application runs as normal?
Thanks
Joe
Thanks for the hint on single pages, I think that those are a good place for me to start. I can try to map my modules to single pages and see how that works out.
1) Could / should bundle them together as a package?
2) Currently the app has 24 tables, is db.xml still the preferred method for database connectivity? and does db.xml have the option for defining a table prefix?
3) Can .htaccess files be configured to exclude a directory from concrete5? For example, i have a websitehttp://www.example.com Concrete5 is installed in the root. Can I exclude /application from concrete5 handling so whatever code is in /application runs as normal?
Thanks
Joe
1. Yes
2. Yes, 2.5. Yes
3. Yes
if there is a file there or a directory, i believe c5 leaves it alone,
the db.xml will only make the tables and set the column properties, you can't make it insert values, you should have it put in the rows in the install controller.
2. Yes, 2.5. Yes
3. Yes
if there is a file there or a directory, i believe c5 leaves it alone,
the db.xml will only make the tables and set the column properties, you can't make it insert values, you should have it put in the rows in the install controller.
Awesome!
Thanks Mnkras for the quick replies. I am trying to wrap my mind around this today so I can actually start recoding tomorrow. Your responses have been a great help.
Thanks Mnkras for the quick replies. I am trying to wrap my mind around this today so I can actually start recoding tomorrow. Your responses have been a great help.
I'd export the relevant tables, then import them into an existing concrete5 install's db.
Then go over to dashboard/settings and debug i think, you can then get the sample xml you can use for your site_db.xml file which needs to sit in config.
Mike is right, all the really custom stuff IMO is a bunch of single pages w/ controllers or page_types with controllers..each have their benefits. Pipe everything to tools, put your ajax stuff(defined vars to tools paths) in a javascript file served from tools..yada yada.
The current app I am doing has 12 tables, several dashboard "pages" and maybe a node of public stuff, that's last.
Good luck. Be sure to check out the adodb activerecord stuff instead of writing all your models manually.
Then go over to dashboard/settings and debug i think, you can then get the sample xml you can use for your site_db.xml file which needs to sit in config.
Mike is right, all the really custom stuff IMO is a bunch of single pages w/ controllers or page_types with controllers..each have their benefits. Pipe everything to tools, put your ajax stuff(defined vars to tools paths) in a javascript file served from tools..yada yada.
The current app I am doing has 12 tables, several dashboard "pages" and maybe a node of public stuff, that's last.
Good luck. Be sure to check out the adodb activerecord stuff instead of writing all your models manually.
also you might want to register an autoloader, a good place to do that is under site_post.php in config so you don't have to do Loader:: statements all over the place.
-Scott
-Scott
