Recommend this pageIf this page was useful to you, please recommend it to fellow websurfers:
Home > Scripts > Content Management (CMS)
You may rate this script by simply clicking on the appropriate star (5 stars is the best rating).
To run jCore your host just needs a couple of things
That’s really it. I recommend Apache as the most robust and featureful server for running jCore, but any server that supports PHP and MySQL will do. That said, I can’t test every possible environment but they should work just fine with jCore if the requirements are met.
Not required, but recommended:
SEO friendly links it is a recommended feature, to use it allow Apache’s mod_rewrite and the usage of .htaccess file. To active the mod_rewrite please make sure you have “LoadModule rewrite_module modules/mod_rewrite.so” in your httpd.conf file also you have “AllowOverride All” for being able to use the .htaccess file.
Multisites feature will not work if you have open_basedir enabled as it won’t allow your script to include files outside of it’s own home directory so it is recommended to have this disabled or use only jCore servers for your websites.
jCore is designed to be easy to install and set up even if you’re not an advanced user. Since it’s so easy to use, as a Web designer or developer, you can quickly build sites for your clients. Then, with a minimal amount of instruction, you can empower your clients to easily manage their own sites themselves.
If your clients need specialized functionality, jCore is highly extensible. You can pick from the available modules or you can easily implement your own and besides this you have full access to the source using Partial Classes from where you can extend/limit the core system too.
The whole system is built up in two parts. There is jCore server and jCore client. jCore server is like a library that you build on, while jCore client is the website that you build for your client.
The advantage of this approach is that each client of yours can have his own home directory with it’s own ftp access and without being able to access the other client’s directories but still use the same core system which is placed in a global place. Also each client can have his own library modifications, modules, or even jQuery plugins, as the core system uses Partial Classes so you can rewrite only a part of the core system by simply extending the core class by placing the same php class file in the lib/ directory and that’s it. This also works for modules and jQuery plugins, just place your own module in lib/modules or jQuery plugin in lib/jquery and you are ready to use them locally just by the defined client.
The current jCore has the following features included and implemented:
This label indicates that I could install the script without major problems and I could run the script without the need for major modifications to the original code (except for the usual configuration, of course). The label does, on the other hand, not indicate that scripts without this label would not work properly. The missing of the „tested & working“-label just indicates that I did not yet test these scripts.
This label indicates that the owner of this website uses this script / application for his own projects with success and satisfaction. This does, however, not indicate that these projects could not have been realized using other scripts / applications as well or that other scripts would not fit the demands of other projects as well or even better.