News
Analyzed over 1 year
ago based on code collected over 1 year ago.
|
Posted
about 5 years
ago
by
Nicolas Steenhout
MOStlyCE Important Update
We are proud to bring you MOStlyCE version 3. This represents the first major release for MOStlyCE in several years. Release Notes: Upgraded to the latest TinyMCE v3.0 core which was a full rewrite for the ... [More] project. This includes tons of bug fixes, better cross browser support (Safari too), cleaner code, etc. Security holes closed and additional security checks added Resolved outstanding compression and spellchecker issues. They should both be working now in most common browsers/environments. Added new pagebreak toolbar option which inserts a more visible indicator Added new dropdown selection lists for images stored under /images/stories and for linking to existing sections, categories, or content MOStlyCE is now distributed as a single .zip file. There are three parts to the package; the mostlyce mambot, the mostlyce admin component, and the mostlyce frontend component (needed for the new dynamic link list features). All three parts are required for proper functionality of this extension. Version 2.x of MOStlyCE is now deprecated and version 3 is now recommended for all Mambo 4.6 users. We encourage you to upgrade to take advantage of the latest developments and increased security (http://secunia.com/advisories/28670/). See the official doc page (http://docs.mambo-foundation.org/en/?View=entry&EntryID=116) for more information and upgrading tips. Also in order to manage releases better and keep things a bit cleaner we have created a stand-alone project on the forge for MOStlyCE. You can find that new project page here (http://mambo-code.org/gf/project/mostlyce/). It is still being distributed with the Mambo core, but releases for MOStlyCE that come outside of normal core releases will be found there. [Less] |
||||||
|
Posted
over 5 years
ago
by
Nicolas Steenhout
The Mambo Team announces the final release of the Mambo 4.5.x series of releases. This marks the end of an era for one of the web's most popular Free Open Source Software (FOSS) Content Management Systems (CMS). The enormous success of Mambo 4.5.x
... [More]
led to many forks, some successful, some less so. Mambo 4.5 has been a great CMS, a good framework, and a great school to many of us , says Ozgur Cem Sen, Core Team Leader of Mambo.
We have been overwhelmed with the positive feedback we've received for the Mambo 4.6.x series, initially released over 16 months ago , continues Mr. Sen. We encourage all Mambo users to upgrade to the latest stable release of Mambo 4.6. During the last several months, the Mambo Team has been working very hard on the upcoming Mambo 4.7, as well as maintaining and doing minor development on Mambo 4.6.x. The Mambo Team also has been discussing Mambo 5. It is time to look forward, and focus our efforts towards growth , says Nicolas Steenhout, Secretary of the Mambo Foundation, Inc. Project Leader, Chad Auld says that this is both a sad and an exciting time for Mambo. It is always sad to see software reaching the end of development, Chad says, Mambo 4.5 has been with us for many years . He adds, Mambo 4.5's time has passed and Mambo is moving forward to an even better future. With 4.7 getting closer to release and planning under way for Mambo 5.0, we have exciting things coming. Team Mambo supports those sentiments and wishes to thank everyone who contributed to Mambo 4.5. This is an exciting step forward for Mambo and one which the Team hopes will be supported by the community. Farewell Mambo 4.5! What's Changed? 1) Hardened security. 2) Updated mod_templatechooser to improve security. 3) Fixed a small issue with the PDF code. 4) Fixed a PHPMailer issue 5) Fixed login and logout redirection issue. Mambo 4.5.6 is code named Sunset . You can download Mambo 4.5.6 from the Mambo Code forge here: http://mambo-code.org/gf/project/mambo/frs/?action=FrsReleaseView release_id=304 (http://mambo-code.org/gf/project/mambo/frs/?action=FrsReleaseView release_id=304) While there, you may like to click on the link to the forge sponsors site. Every project hosted on the forge is offered free hosting for the project on BuyHTTP (http://www.buyhttp.com/mambo_hosting.html) and they have some good deals going for Mambo hosting too. Support for our sponsors directly helps the Mambo project. If you have any reminiscences or thoughts to share about the sunset of the Mambo 4.5 branch you can discuss them here: http://forum.mambo-foundation.org/showthread.php?t=9843 (http://forum.mambo-foundation.org/showthread.php?t=9843) [Less] |
||||||
|
Posted
over 5 years
ago
by
Chad Auld
With the 4.7 release just around the corner the Mambo team thought now would be great time to discuss with the community our plans for post 4.7 releases. The major initiatives laid out on the Roadmap a year ago are still in place, but the release
... [More]
plans have changed slightly based on some decisions we have made. Originally we had planned to release 4.7, then 4.8, and then 5.0. We are now planning to move from the 4.7 release directly into Mambo 5. The 4.8 release was to focus on database portability, content versioning, and the implementation of a PHP template engine. Version 5.0 was to tackle features like enhanced Access Control Lists (ACL), N-Level content organization instead of the current two tier section/category structure, multi-site management, etc. The team has spent a great deal of time thinking about the approaches we will take to implement all those features and how best to leverage the great work being done by others within the PHP community as well. Over the last year the number of PHP frameworks on the market has increased as have the maturity level and feature set provided by each. As the size and complexity of a project like Mambo grows having a solid foundation to build from becomes increasingly more important. We believe that Mambo 4.7 will prove to be the best Mambo release yet. The team has spent a considerable amount of time working on XHTML validation, WCAG 1.0 (Priority 1, 2, and some 3), removal of unnecessary and/or inaccessible JavaScript code, improved usability, plus much more. With a solid release like Mambo 4.7 out we will have a stable, accessible, and standards compliant system for the community to use which will allow the team to fully focus its attention on the future. Of course we will continue to provide maintenance releases of 4.7 as needed while we work on Mambo 5. Mambo 5 offers us a chance to step back and rework things from the ground up. There couldn’t be a better time to leverage the benefits of tried and true enterprise patterns and features offered by a number of great web development frameworks on the market today. After a great deal of research the Mambo team has decided to utilize the CakePHP framework for Mambo 5. CakePHP is a rapidly evolving, mature, and feature rich PHP framework. The project is backed by an official Foundation (http://cakefoundation.org/ (http://cakefoundation.org/)) much like the Mambo project itself. We believe this is an important criterion as it helps assure the project will remain active and community minded. CakePHP also has a growing community, a software forge (http://cakeforge.org/ (http://cakeforge.org/)), and a nice body of documentation. From their site, Cake is a rapid development framework for PHP which uses commonly known design patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. Our primary goal is to provide a structured framework that enables PHP users at all levels to rapidly develop robust web applications, without any loss to flexibility. Here are some of the standard cake features: Hot Features:Model, View, Controller ArchitectureView Helpers for AJAX, Javascript, HTML Forms and moreBuilt-in ValidationApplication ScaffoldingApplication and CRUD code generation via BakeAccess Control ListsData SanitizationSecurity, Session, and Request Handling ComponentsFlexible View CachingAnd More...Active, Friendly Community - Just join our IRC channel to see who's in. We'd love to help you get started.Flexible License - Cake is distributed under the MIT LicenseClean IP - Every line of code was written by the CakePHP development teamExtremely Simple - Just look at the name...It's CakeRapid Development - Build apps faster than ever before (check out the zZine article - http://www.zzine.org/articles/cakephp (http://www.zzine.org/articles/cakephp))Best Practices - Cake is easy to understand and sets the industry standard in security authentication, and session handling, among other features.OO - Whether you are a seasoned object-oriented programmer or a beginner, you'll feel comfortableNo Configuration - Set-up the database and watch the magic begin We realize this decision is not only important for the Mambo core, but also for the 3rd party developer community. I’m sure at this point most of you have at least read about and more than likely have tried at least several different frameworks. In fact you probably already have a favorite. Like anything else, each framework has its own strengths and weaknesses and CakePHP may or may not be your first choice, but we hope you’ll agree that CakePHP is a solid choice and certainly one of the top frameworks available today. Having a framework like CakePHP at your disposal should make developing Mambo add-ons just that much easier and offer new levels of extendability. Developers will find a great starter manual (http://manual.cakephp.org/ (http://manual.cakephp.org/)), a solid API (http://api.cakephp.org/ (http://api.cakephp.org/)), plenty of online tutorials (http://bakery.cakephp.org/ (http://bakery.cakephp.org/)) screencasts (http://cakephp.org/screencasts (http://cakephp.org/screencasts)), an IRC channel, and the projects Google Group (http://groups.google.com/group/cake-php (http://groups.google.com/group/cake-php)) for CakePHP support. Of course Mambo 5 will have its own documentation as well, but we still have a long way to go before then. Also, just so you know its not all theory I thought I would mention that we already have a pre-alpha prototype of the new Mambo 5 installer. I've spent the last month or so reworking some early code I had done on the Mambo installer for 4.8 around database portability. I started the code 1 year ago this week and set it off to the side for a long while waiting for 4.8. With 4.8 going away and the project moving to CakePHP I decided it was time to bring it back to life and do it the CakePHP way. It utilizes ADOdb and AXMLS to create the initial Mambo database and land the database connector. From that point on it relies on the native database portability drivers within CakePHP. Having these native drivers has made life much easier than previous methods. The pre-alpha version was done on CakePHP 1.1.x and has support for SQLite, PostgreSQL, and MySQL. CakePHP 1.2 is now in alpha status and is looking better by the day. Before too long I will rework the installer to utilize the 1.2 branch which will bring even more databases into the mix; oracle, db2, and mssql. By no means is the pre-alpha installer ready for production, but it does show off some nice functionality and proves Mambo and CakePHP can make a nice pair. We will be sharing this with interested 3rd party developers as a sample shortly after 4.7 is released. It's the perfect time to make a shift and look toward the future of this great system of ours. We hope you'll join us on this new adventure. Mambo on! [Less]
|
||||||
|
Posted
over 5 years
ago
by
Nicolas Steenhout
Written by: Ozgur Cem Sen, Team Leader, Quality Assurance Release Team - (read an introduction to Cem here) (/content/view/129/28/) From a software developer’s perspective QA is the most boring and unnecessary part of software development.
... [More]
How dare someone check my state-of-art code and tell me that it is not working? Tsk tsk tsk… I cannot name one software developer, who never said that. I have known many, plus I am still one of them – been there, still doing it. In this article, I will be sharing some of my observations on what’s going on with the QA in the large scale Free Open Source Software projects and what we do here at Mambo about this boring thing called QA. Let’s start with the evolution of a big Open Source project. It’s all the trivial stuff; idea is born, a couple of buddies start developing it, initial release goes out, some need is fulfilled, more people start using it, some patches and the second release comes out, couple of other developers join, the community grows, 3rd party folks start making money off the project, new releases come out with more features, more and more people start using the projects, some corporate money flows in, the original developers are the Gods of the source, power struggles start, project forks, some of the key developers quit and start over etc etc etc… Did I mention QA? Not yet. Indeed, I probably cannot, because it was never a part of all that happened above. The Free Open Source World is a very strange place. Since there is no money involved – in most cases – almost everything is driven by commitment. Therefore the human emotion becomes the dominant driver for the projects. I would rate the cool factor as the top rated emotion. If you are a core development team member, you are cool. Now, the rest of the community, millions of other users of your project must bow in front of you, just because you can commit code. Sweet isn’t it. If you’re writing up documentation, you are not cool. If you are translating, you are not cool. If you are testing it you are not cool. Unless you commit code, you are not cool. This must be the main reason that QA teams of big Open Source projects are like deserted islands. Once the software hits the wires for download, the cool does not mean a thing. Quality does. That's why, the QA Release Team at Mambo is in the process of implementing better testing and release processes on top of manual testing, in order to avoid oops, how did I miss that!!! situations. Our new QA Release process is defined with this catchy-phrase – Mambo 4x4 Testing. Mambo 4x4 Testing is: Selenium Based Ant Driven Maven Controlled Cruise Control Powered This new process will allow us to continuously test our software under different environments and conditions. I have to admit, writing the test scenarios is boring , nevertheless I am self assured that the end result will be thrilling. Mambo Open Source CMS has already hit the widely accepted threshold. We are all very well aware of the fact that being a part of this project is not about being cool anymore. It is about being responsible and being able to release an excellent product to our user base and prospective users. This is our responsibility and pledge. If you are interested in being part of this important function in the development cycle of the Mambo CMS, please make yourself known to the Team on the Mambo forums. QA is vital to Mambo and we would appreciate having more skilled people on board to assist with ensuring our code meets the highest standards. [Less]
|
||||||
|
Posted
over 5 years
ago
by
Nicolas Steenhout
Team Mambo announces the release of Mambo 4.6.3!
Code name Dylan , this minor version release features a number of security improvements and bug fixes. These include: Stability security improvements Performance ... [More] improvements A number of bug fixes Improved compatibility with 3rd party extensions Updates to some core extensions What's New in 4.6.3... Security Fixes: *php mailer security fix. *template chooser security fixes *XSS fixes in administrator backed *sample configuration file renamed to configuration.sample.php Bug Fixes: *fixed banner manager custom-code bugs *fixed mambo admin template install problem *fixed special vs. registered users menu access related problems *fixed login component redirection *fixed line breaks in emails in Mambo *fixed missing links in pathway *fixed problems with module ordering affecting menus *fixed an xml parser problem in the installer *fixed section module problems related to Itemid. *fixed content editing resulting in overriding the article creator *fixed incorrect escaping of weblinks' titles, description Enhancements: *mostlyce upgraded to 2.4 *mostlydbadmin upgraded to 1.5 *geshi upgraded to 1.0.7.20 *enhanced editor initializing *enhanced weblinks component, so the target param is not confusing anymore *updated the sample data so Mambo links will be up-to-date with the recent Mambo sites changes *Some XHTML compliance work *added option to block the blocked users in the mass email *added mosshowhead and some helper classes to select/exclude head tags *added module buffering *added the ability to delete superadmins *added search feature in language manager *added onAfterStart mambot trigger *compressed js and css files for improved performance Mambo 4.6.3, including upgrade files, can be found on the Mambo Code forge here: http://mambo-code.org/gf/project/mambo/frs/ (http://mambo-code.org/gf/project/mambo/frs/) Because Mambo 4.6.3 is a security and maintenance release we advise everyone using Mambo 4.6 - 4.6.2 to upgrade. If you are not running Mambo 4.6.2 then you should patch up to this version prior to applying this new patch. Upgrade instructions are provided in the patch download - please read the instructions! Note about Mambo Security. Each of the security fixes relates to vulnerabilities that have the potential for exploit. There have been no known cases of them actually being exploited and most relate to backend/administrator security weaknesses that would first require someone to be logged into the backend. A Secunia advisory reported a proof of concept regarding two potential security flaws in 4.6.2 (http://secunia.com/advisories/28133/ (http://secunia.com/advisories/28133/)). Only one of the reported flaws had any potential to insert code and even then, the code could not be executed. The result of extensive testing showed that where a user was using an unpatched version of IE6 it was possible to enter raw text into one form in Mambo 4.6.2. While this would not compromise a site because the script could not actually run, the vulnerabilities in IE6 could result in a small amount of unwanted text appearing below a form. While this flaw was really a browser flaw (that has been fixed in recent updates to IE6) we blocked the hole that allowed unauthorised text to be inserted. The Secunia advisory does not relate to Mambo 4.5.5. While the 4.6.2 security vulnerabilities are low level, we prefer everyone to be running sites that have a high level of protection and the bug fixes, feature and performance improvements make this a very worthwhile upgrade. [Less] |
||||||
|
Posted
over 5 years
ago
by
Nicolas Steenhout
Mambo Foundation, Inc President, Lynne Pope, is a finalist in the inaugural New Zealand Open Source Awards. Selected as one of three finalists for the title of New Zealand's Open Source Ambassador from 130 nominations, Lynne Pope has been
... [More]
nominated for her involvement with the content-management system Mambo, and for setting up a website, Katrina Evacuee Help Centre, at www.disastersearch.org (http://disastersearch.org), to assist victims of the 2005 Hurricane Katrina disaster. Disastersearch, which was formerly named the Katrina Evacuee Help Centre, was built on a base of Mambo 4.5.2 and through the efforts of a large number of volunteer programmers from the Mambo and Joomla! communities evolved to become an application that can be used in any emergency involving the evacuation and relocation of people. It is an ongoing project and continues development under the leadership of both Lynne and her fellow director of Disastersearch Ltd, Dr John Long. John and Lynne are also members of the Mambo core development team. The New Zealand Open Source Awards recognise and promote: * the contributions of New Zealanders directly to open source projects or the promotion of open source generally * exemplary use of open source by New Zealand organisations.Sponsored by Google, Red Hat, Novell, Catalyst IT and a number of local New Zealand organisations, the awards will be presented at a gala function in Wellington, NZ on October 17th, 2007. http://www.nzosa.org.nz/news (http://www.nzosa.org.nz/news) [Less]
|
||||||
|
Posted
over 5 years
ago
by
Nicolas Steenhout
Written by: Ozgur Cem Sen, Team Leader, Quality Assurance Release Team - (read an introduction to Cem here) (/content/view/129/28/) From a software developer’s perspective QA is the most boring and unnecessary part of software development.
... [More]
How dare someone check my state-of-art code and tell me that it is not working? Tsk tsk tsk… I cannot name one software developer, who never said that. I have known many, plus I am still one of them – been there, still doing it. In this article, I will be sharing some of my observations on what’s going on with the QA in the large scale Free Open Source Software projects and what we do here at Mambo about this boring thing called QA. Let’s start with the evolution of a big Open Source project. It’s all the trivial stuff; idea is born, a couple of buddies start developing it, initial release goes out, some need is fulfilled, more people start using it, some patches and the second release comes out, couple of other developers join, the community grows, 3rd party folks start making money off the project, new releases come out with more features, more and more people start using the projects, some corporate money flows in, the original developers are the Gods of the source, power struggles start, project forks, some of the key developers quit and start over etc etc etc… Did I mention QA? Not yet. Indeed, I probably cannot, because it was never a part of all that happened above. The Free Open Source World is a very strange place. Since there is no money involved – in most cases – almost everything is driven by commitment. Therefore the human emotion becomes the dominant driver for the projects. I would rate the cool factor as the top rated emotion. If you are a core development team member, you are cool. Now, the rest of the community, millions of other users of your project must bow in front of you, just because you can commit code. Sweet isn’t it. If you’re writing up documentation, you are not cool. If you are translating, you are not cool. If you are testing it you are not cool. Unless you commit code, you are not cool. This must be the main reason that QA teams of big Open Source projects are like deserted islands. Once the software hits the wires for download, the cool does not mean a thing. Quality does. That's why, the QA Release Team at Mambo is in the process of implementing better testing and release processes on top of manual testing, in order to avoid oops, how did I miss that!!! situations. Our new QA Release process is defined with this catchy-phrase – Mambo 4x4 Testing. Mambo 4x4 Testing is: Selenium Based Ant Driven Maven Controlled Cruise Control Powered This new process will allow us to continuously test our software under different environments and conditions. I have to admit, writing the test scenarios is boring , nevertheless I am self assured that the end result will be thrilling. Mambo Open Source CMS has already hit the widely accepted threshold. We are all very well aware of the fact that being a part of this project is not about being cool anymore. It is about being responsible and being able to release an excellent product to our user base and prospective users. This is our responsibility and pledge. If you are interested in being part of this important function in the development cycle of the Mambo CMS, please make yourself known to the Team on the Mambo forums. QA is vital to Mambo and we would appreciate having more skilled people on board to assist with ensuring our code meets the highest standards. [Less]
|
||||||
|
Posted
over 5 years
ago
by
Nicolas Steenhout
MAMBO ADDS MAMBOXCHANGE AND ANNOUNCES NEW COMMUNITY GOVERNANCE Award winning Open Source CMS now in a better state than ever with new leadership and adds MamboXchange to it’s stable of developer resources.One year after becoming an autonomous
... [More]
, community-controlled entity for the first time in its seven year development timeline, Mambo has reached a turning point in the history of one of the world’s most popular Open Source content management systems.“The recent board elections of the Mambo Foundation, Inc. reflects the community’s vote of confidence in our abilities to manage an extremely large and successful open source project without having to depend on corporate participation” said Lynne Pope, newly elected president of the Mambo Foundation, Inc.“The Mambo project is growing strongly and as a result, demand has increased for improved developer services. We will be working overtime to ensure that access to core structures are made accessible and to keep communication free-flowing and transparent” add Ms. Pope.In August 2005, the Mambo Foundation, Inc was established as a non-profit governing body for the Mambo CMS by former Miro International CEO, Peter Lamont. “This caused some controversy amongst the community of users due to a broad spread of misinformation”, Lynne Pope stated. “The truth of the matter is that the Foundation was set up, all IP was transferred to it, and Peter Lamont held the reins as Chairman of the Foundation just long enough for the community to get ready for self-governance”.Heading into its second year as a community-controlled organisation and following the election of a new Board of Directors, the second phase of endowment from the former sponsor of Mambo has been announced.Peter Lamont, who has been running the mamboserver.com websites and the MamboXchange developer forge through his company, Mambo Communities Pty Ltd, has assigned the MamboXchange domain and websites to the Mambo Foundation. “The Xchange rightly belongs with the Foundation who have demonstrated their ability and commitment to responsibly manage and grow the Mambo project and unite a large and growing community of dedicated Mambo users” said Peter Lamont. “I have no doubt that Lynne and the new board will take Mambo from strength to strength under accountable and transparent leadership and governance.”The new Mambo forge can be found at http://mambo-code.org/ (http://mambo-code.org/) [Less]
|
||||||
|
Posted
almost 6 years
ago
by
Ric Shreves
Jem Matzen of The Jem Report interviewed Ric Shreves, president of the Mambo Foundation. The interview touches on open source project governance before diving into topics specific to the Mambo Project. Ric talks about present challenges and long term
... [More]
plans for Mambo. Read it all on The Jem Report. (http://www.thejemreport.com/mambo/content/view/311/) Everybody Mambo! [Less]
|
||||||
|
Posted
almost 6 years
ago
by
Chad Auld
With the 4.7 release just around the corner the Mambo team thought now would be great time to discuss with the community our plans for post 4.7 releases. The major initiatives laid out on the Roadmap a year ago are still in place, but the release
... [More]
plans have changed slightly based on some decisions we have made. Originally we had planned to release 4.7, then 4.8, and then 5.0. We are now planning to move from the 4.7 release directly into Mambo 5. The 4.8 release was to focus on database portability, content versioning, and the implementation of a PHP template engine. Version 5.0 was to tackle features like enhanced Access Control Lists (ACL), N-Level content organization instead of the current two tier section/category structure, multi-site management, etc. The team has spent a great deal of time thinking about the approaches we will take to implement all those features and how best to leverage the great work being done by others within the PHP community as well. Over the last year the number of PHP frameworks on the market has increased as have the maturity level and feature set provided by each. As the size and complexity of a project like Mambo grows having a solid foundation to build from becomes increasingly more important. We believe that Mambo 4.7 will prove to be the best Mambo release yet. The team has spent a considerable amount of time working on XHTML validation, WCAG 1.0 (Priority 1, 2, and some 3), removal of unnecessary and/or inaccessible JavaScript code, improved usability, plus much more. With a solid release like Mambo 4.7 out we will have a stable, accessible, and standards compliant system for the community to use which will allow the team to fully focus its attention on the future. Of course we will continue to provide maintenance releases of 4.7 as needed while we work on Mambo 5. Mambo 5 offers us a chance to step back and rework things from the ground up. There couldn’t be a better time to leverage the benefits of tried and true enterprise patterns and features offered by a number of great web development frameworks on the market today. After a great deal of research the Mambo team has decided to utilize the CakePHP framework for Mambo 5. CakePHP is a rapidly evolving, mature, and feature rich PHP framework. The project is backed by an official Foundation (http://cakefoundation.org/ (http://cakefoundation.org/)) much like the Mambo project itself. We believe this is an important criterion as it helps assure the project will remain active and community minded. CakePHP also has a growing community, a software forge (http://cakeforge.org/ (http://cakeforge.org/)), and a nice body of documentation. From their site, Cake is a rapid development framework for PHP which uses commonly known design patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. Our primary goal is to provide a structured framework that enables PHP users at all levels to rapidly develop robust web applications, without any loss to flexibility. Here are some of the standard cake features: Hot Features:Model, View, Controller ArchitectureView Helpers for AJAX, Javascript, HTML Forms and moreBuilt-in ValidationApplication ScaffoldingApplication and CRUD code generation via BakeAccess Control ListsData SanitizationSecurity, Session, and Request Handling ComponentsFlexible View CachingAnd More...Active, Friendly Community - Just join our IRC channel to see who's in. We'd love to help you get started.Flexible License - Cake is distributed under the MIT LicenseClean IP - Every line of code was written by the CakePHP development teamExtremely Simple - Just look at the name...It's CakeRapid Development - Build apps faster than ever before (check out the zZine article - http://www.zzine.org/articles/cakephp (http://www.zzine.org/articles/cakephp))Best Practices - Cake is easy to understand and sets the industry standard in security authentication, and session handling, among other features.OO - Whether you are a seasoned object-oriented programmer or a beginner, you'll feel comfortableNo Configuration - Set-up the database and watch the magic begin We realize this decision is not only important for the Mambo core, but also for the 3rd party developer community. I’m sure at this point most of you have at least read about and more than likely have tried at least several different frameworks. In fact you probably already have a favorite. Like anything else, each framework has its own strengths and weaknesses and CakePHP may or may not be your first choice, but we hope you’ll agree that CakePHP is a solid choice and certainly one of the top frameworks available today. Having a framework like CakePHP at your disposal should make developing Mambo add-ons just that much easier and offer new levels of extendability. Developers will find a great starter manual (http://manual.cakephp.org/ (http://manual.cakephp.org/)), a solid API (http://api.cakephp.org/ (http://api.cakephp.org/)), plenty of online tutorials (http://bakery.cakephp.org/ (http://bakery.cakephp.org/)) screencasts (http://cakephp.org/screencasts (http://cakephp.org/screencasts)), an IRC channel, and the projects Google Group (http://groups.google.com/group/cake-php (http://groups.google.com/group/cake-php)) for CakePHP support. Of course Mambo 5 will have its own documentation as well, but we still have a long way to go before then. Also, just so you know its not all theory I thought I would mention that we already have a pre-alpha prototype of the new Mambo 5 installer. I've spent the last month or so reworking some early code I had done on the Mambo installer for 4.8 around database portability. I started the code 1 year ago this week and set it off to the side for a long while waiting for 4.8. With 4.8 going away and the project moving to CakePHP I decided it was time to bring it back to life and do it the CakePHP way. It utilizes ADOdb and AXMLS to create the initial Mambo database and land the database connector. From that point on it relies on the native database portability drivers within CakePHP. Having these native drivers has made life much easier than previous methods. The pre-alpha version was done on CakePHP 1.1.x and has support for SQLite, PostgreSQL, and MySQL. CakePHP 1.2 is now in alpha status and is looking better by the day. Before too long I will rework the installer to utilize the 1.2 branch which will bring even more databases into the mix; oracle, db2, and mssql. By no means is the pre-alpha installer ready for production, but it does show off some nice functionality and proves Mambo and CakePHP can make a nice pair. We will be sharing this with interested 3rd party developers as a sample shortly after 4.7 is released. It's the perfect time to make a shift and look toward the future of this great system of ours. We hope you'll join us on this new adventure. Mambo on! [Less]
|
||||||
Code Data
SCM Data
Community Data
Copyright
©
2013
Black Duck Software, Inc.
and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a
Creative Commons Attribution 3.0 Unported License
. Ohloh
®
and the Ohloh logo are trademarks of
Black Duck Software, Inc.
in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.