Hi,
Anyone can share your favorite PHP open source CMS to work with and
what's the reason? I'm looking for something that easily extensible.
I've googled and found severals but I'm still confused, some from the
lists:
- Drupal
- Tomato CMS
- modx
- xoops
- Symphony
Thanks
# Hendry
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--00504502bc64d300f9047da4d978
Content-Type: text/plain; charset=ISO-8859-1
I've not had much experience with CMS's, however Drupal seems pretty
featured, with the steep-learning curve; it's not very user friendly.
I'm working on my own CMS which is more generic, so that it can be used with
any kind of website (basically). I suggest you do the same; have a page
class with methods that allow you to create new pages. I have not yet
fleshed out this class, but I eventually plan to get it so that when I
"create a new page", my class will generate a PHP file with a unique page ID
number. Then it will log the link to this page into a links table and save
content I enter in different areas, eg. Scripts (here I write any PHP I will
need) and content (the body of the document, which can also make use of
PHP).
The Scripts and Body are saved to include files with the same name as the
ID, and the page loads the items associated with that ID. For example:
Allen McCabe wrote:
> I've not had much experience with CMS's, however Drupal seems pretty
> featured, with the steep-learning curve; it's not very user friendly.
Not to disregard your own experience, but I've found Drupal surprisingly
easy to get running with. In fact it's pretty much my first choice when
installing a CMS for a client and I demsontrate how simple it is for
them to add content. This is especially true in Canada where many
websites are multilingual and Drupal offers one of the best interfaces
for providing multilingual content. Additionally, the ability to create
custom content types while possibly difficult for clients to grasp, is
really simple for them to use if I do the legwork of creating the
content types and associated views.
Cheers,
Rob.
--
http://www.interjinn.com
Application and Templating Framework for PHP
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--000e0cd154ae9daa99047da4f5be
Content-Type: text/plain; charset=ISO-8859-1
For a work in progress, view http://www.mwclans.com/new_index.php
The login fields are a 'component' I include in the header.
The links are generated from the 'links' table; the primary_navigation links
are a class by the same name, and the 'footer_navigation' are also a
different category. All links on this page are generated from the Links
table, and each row has 90% of the properties the HTML 'a' tag can have (eg.
fields: id, link_text, href, target, onmouseover, onmouseout, onclick, name,
class, etc.). The class is the same as the category.
The content is pulled from an include file with the same ID number as this
page ("home" page), which is "1", and the scripts.
There are additional features, like a theme class which pulls a theme ID
from the DB (a `site_settings` table).
Here is an example of the source code for the above link:
$thispage = 1;
// define root directory
if (!defined('ROOT'))
{
// Locate config.inc.php and set the basedir path
$folder_level = ''; $i = 0;
while (!file_exists($folder_level . 'config.inc.php'))
{
$folder_level .= '../';
$i++;
if ($i == 5){ die('Config file not found.'); }
}
// ROOT = base_directory/
DEFINE('ROOT', $folder_level);
}
// include configuration file
include(ROOT . 'config.inc.php');
// include headers
include(ROOT . 'common/global.inc.php');
?>
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The CSS used for this layout is 100% valid and hack free.
To overcome Internet Explorer's broken box model, no horizontal padding or
margins are used. Instead, this design uses pixel widths and clever relative
positioning.
The holy grail 3 column liquid Layout has been tested on
the following browsers:
--00504502acad79dc24047da50a78
Content-Type: text/plain; charset=ISO-8859-1
I suppose I am opposed to 'custom systems' with PHP. I feel that you
shouldn't have to learn "new-stuff" that is specific to a certain system if
it is so extensive. I know, I'm lazy, but I've been trying to learn PHP (as
well as needing to learn JavaScript, SQL, and CSS 2.0 lately) and not stuff
that will only work in a closed system.
That said; Drupal is VERY powerful, and VERY convenient given the
multi-lingual aspects you (Rob) mentioned. From my angle, achieving what
wanted through Drupal was proving to be almost impossible, when I had a good
idea of how to accomplish it on my own, and figuring out how to integrate
Drupal with my own custom scripts was proving to be a headache for me, so I
ditched Drupal.
Again, Drupal is amazing. I guess what I was trying to say was "it depends".
Drupal is great for non-programmers who want to do very simple things, or
for professional PHP programmers who want to do pretty much anything.
Cheers :)
Allen
On Wed, Jan 20, 2010 at 8:14 PM, Robert Cummings
> Allen McCabe wrote:
>
>> I've not had much experience with CMS's, however Drupal seems pretty
>> featured, with the steep-learning curve; it's not very user friendly.
>>
>
> Not to disregard your own experience, but I've found Drupal surprisingly
> easy to get running with. In fact it's pretty much my first choice when
> installing a CMS for a client and I demsontrate how simple it is for them to
> add content. This is especially true in Canada where many websites are
> multilingual and Drupal offers one of the best interfaces for providing
> multilingual content. Additionally, the ability to create custom content
> types while possibly difficult for clients to grasp, is really simple for
> them to use if I do the legwork of creating the content types and associated
> views.
>
> Cheers,
> Rob.
> --
> http://www.interjinn.com
> Application and Templating Framework for PHP
>
--00504502acad79dc24047da50a78--
Hi,
Thanks for both Robert and Allen for sharing, I agree, Drupal is very
easy to start with, and it is also very powerful, but somehow, I find
it very hard to extend which is might be due to my lack of experience.
# Hendry
On Thu, Jan 21, 2010 at 12:21 PM, Allen McCabe
> I suppose I am opposed to 'custom systems' with PHP. I feel that you
> shouldn't have to learn "new-stuff" that is specific to a certain system if
> it is so extensive. I know, I'm lazy, but I've been trying to learn PHP (as
> well as needing to learn JavaScript, SQL, and CSS 2.0 lately) and not stuff
> that will only work in a closed system.
>
> That said; Drupal is VERY powerful, and VERY convenient given the
> multi-lingual aspects you (Rob) mentioned. From my angle, achieving what
> wanted through Drupal was proving to be almost impossible, when I had a good
> idea of how to accomplish it on my own, and figuring out how to integrate
> Drupal with my own custom scripts was proving to be a headache for me, so I
> ditched Drupal.
>
> Again, Drupal is amazing. I guess what I was trying to say was "it depends".
> Drupal is great for non-programmers who want to do very simple things, or
> for professional PHP programmers who want to do pretty much anything.
>
> Cheers :)
>
> Allen
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, Jan 21, 2010 at 11:29:54AM +0800, Hendry wrote:
> Hi,
>
> Anyone can share your favorite PHP open source CMS to work with and
> what's the reason? I'm looking for something that easily extensible.
> I've googled and found severals but I'm still confused, some from the
> lists:
> - Drupal
> - Tomato CMS
> - modx
> - xoops
> - Symphony
Add CodeIgniter to your list. Relatively easy to understand and extend.
Though I'm not sure I'd classify it as a "content management system".
(Same for Symfony.)
Paul
--
Paul M. Foster
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, Jan 20, 2010 at 08:15:55PM -0800, Allen McCabe wrote:
> For a work in progress, view http://www.mwclans.com/new_index.php
>
> The login fields are a 'component' I include in the header.
> The links are generated from the 'links' table; the primary_navigation links
> are a class by the same name, and the 'footer_navigation' are also a
> different category. All links on this page are generated from the Links
> table, and each row has 90% of the properties the HTML 'a' tag can have (eg.
> fields: id, link_text, href, target, onmouseover, onmouseout, onclick, name,
> class, etc.). The class is the same as the category.
>
> The content is pulled from an include file with the same ID number as this
> page ("home" page), which is "1", and the scripts.
>
> There are additional features, like a theme class which pulls a theme ID
> from the DB (a `site_settings` table).
>
> Here is an example of the source code for the above link:
>
You're free to do this as you like, and I've done it in the past just as
you did. But I think the general concensus is that you want to
intersperse as little complicated PHP inside your HTML as possible. For
example, you're doing a database call inside your HTML and then
displaying the results. The more acceptable practice is to make these
calls before you start outputting HTML, shove the values into variables
or an array, and then just loop through the *values* inside your HTML.
There are a couple of reasons for doing it this way. First, anyone
looking at the HTML later who isn't a programmer will have an easier
time of it if there aren't lines and lines of PHP code inside the HTML.
Second, it makes your code more "modular". That is, it puts your main
body of PHP code all together. That aids in debugging, testing and the
like later. This approach means your code is dispersed among several
files instead of just one. But it aids in debugging. I find it painful
to have to scan through HTML for PHP code, so I can fix a problem.
You'll also find that if you have a variety of pages which are all laid
out the same way, it's better to put that HTML in a separate "template"
file. Insert some code in it to display values as needed. Then when you
want to paint a page, simply define the values you want to display, and
include('template.php');
This way, if you make a change to the design or look of the site, you
can make that change to one (template) file and it will echo all over
the site. This is particularly important if you're working with
"designers" who don't know HTML but do the work of designing pages.
This is just simple advice based on my experience. Feel free to ignore
it completely if you work better a different way.
Paul
--
Paul M. Foster
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Hendry wrote:
> Hi,
>
> Anyone can share your favorite PHP open source CMS to work with and
> what's the reason? I'm looking for something that easily extensible.
> I've googled and found severals but I'm still confused, some from the
Bitweaver is nice and modular, load what you want to use, wiki, articles, forum,
blog, galleries etc. OR take a package and tailor it for your own needs ....
bitweaver.org
If you must - it will work with MySQL, but it handles all the good databases as
well :)
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Hendry wrote:
> Hi,
>=20
> Anyone can share your favorite PHP open source CMS to work with and
> what's the reason? I'm looking for something that easily extensible.
I have just installed websitebaker for a client. I've also got redaxo
installed for another client.
/Per
--=20
Per Jessen, Zürich (4.3°C)
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Hendry wrote:
> Hi,
>
> Anyone can share your favorite PHP open source CMS to work with and
> what's the reason? I'm looking for something that easily extensible.
> I've googled and found severals but I'm still confused, some from the
> lists:
> - Drupal
> - Tomato CMS
> - modx
> - xoops
> - Symphony
>
> Thanks
>
> # Hendry
most are good in different ways; many are carbon copies with different
coding styles; pick any of them and work with it till you start fighting
it, then review your choice.
there's no way anybody can really help you pick, you know what you want
to do and what you don't; if you just want to install something load a
plugin and skin it then pick drupal or something like it "a cms". If you
want to code custom things quicker, then pick a framework like zend,
kohana, codeigniter and fuse different classes / modules to develop your
apps quickly.
just to make up a phrase cos I'm in that kind of mood.. "only a foolish
workman carries one tool in his toolbox" - you need different tools for
different jobs, just like we need more than php we need more than one
framework/class/cms.
also worth considering what you want to do, if you don't wanna roll out
carbon copy sites with different templates every day of life then don't
take on that kinda work & forget about picking a cms; or if you just
want to work agency style with clients in and out the door as quick as
possible with little maintenance use what everybody knows, drupal them
all safe in the knowledge that anybody with drupal skills can do the
ongoing maintenance and developers / designers with the needed skills
are plentiful.
ps:
1 - have a quick scan of the source code of each & see if it looks easy
for you to work with and is coded in a similar style to your own code.
2 - look for the most modular, lightest and mature which fits the
results of 1.
regards!
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
At 11:29 AM +0800 1/21/10, Hendry wrote:
>Hi,
>
>Anyone can share your favorite PHP open source CMS to work with and
>what's the reason? I'm looking for something that easily extensible.
>I've googled and found severals but I'm still confused, some from the
>lists:
>- Drupal
>- Tomato CMS
>- modx
>- xoops
>- Symphony
>
>Thanks
>
># Hendry
The best that I've seen is SilverStripe, try this:
http://www.silverstripe.com/
Cheers,
tedd
--
-------
http://sperling.com http://ancientstones.com http://earthstones.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
tedd wrote:
> At 11:29 AM +0800 1/21/10, Hendry wrote:
>> Hi,
>>
>> Anyone can share your favorite PHP open source CMS to work with and
>> what's the reason? I'm looking for something that easily extensible.
>> I've googled and found severals but I'm still confused, some from the
>> lists:
>> - Drupal
>> - Tomato CMS
>> - modx
>> - xoops
>> - Symphony
>>
>> Thanks
>>
>> # Hendry
>
> The best that I've seen is SilverStripe, try this:
>
> http://www.silverstripe.com/
Me no likey... it's seems caught between traditional page style and ajax
style. Some navigational elements do an ajax update, some do a normal
request. The problem is, a normal request causes you to lose your left
navigation context. Also, the multilingual / translation stuff seems
obtuse. The interface makes me think of some Typo3/Joomla hybrid.
Cheers,
Rob.
--
http://www.interjinn.com
Application and Templating Framework for PHP
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 1/21/2010 7:58 AM, Paul M Foster wrote:
> On Thu, Jan 21, 2010 at 11:29:54AM +0800, Hendry wrote:
>
>> Hi,
>>
>> Anyone can share your favorite PHP open source CMS to work with and
>> what's the reason? I'm looking for something that easily extensible.
>> I've googled and found severals but I'm still confused, some from the
>> lists:
>> - Drupal
>> - Tomato CMS
>> - modx
>> - xoops
>> - Symphony
>
> Add CodeIgniter to your list. Relatively easy to understand and extend.
> Though I'm not sure I'd classify it as a "content management system".
> (Same for Symfony.)
>
> Paul
>
I think is talking about Symphony CMS (XSLT-powered open source content
management system) and not Symfony framework.
/i
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Wednesday 20 January 2010 10:29:38 pm Hendry wrote:
> Hi,
>
> Thanks for both Robert and Allen for sharing, I agree, Drupal is very
> easy to start with, and it is also very powerful, but somehow, I find
> it very hard to extend which is might be due to my lack of experience.
>
> # Hendry
The way you extend Drupal is rather different than most other systems due to
its architecture. However, once you wrap your head around doing so it is
extremely extensible. The online docs on drupal.org are a pretty good place
to start, but I can also recommend this book:
http://www.packtpub.com/drupal-6-module-development/book
Disclaimer: The author used to work with me, and I'm a Drupal core developer
so I am admittedly biased. :-)
--Larry Garfield
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php