Site Blog

Jun ’14
Here's a brief summary of the Skype conversation "e107 Meeting Saturday May 31, 2014 (1pm PST = 2pm PDT = 9pm GMT)".

* Issues of milestone 2 are being worked on intensively
* requests for new features have been moved to milestone 3
* TinyMCE plugin (WYSIWYG editor) is the major concern for the new alpha version
* retrieving plugins/themes will not be fully functional as intended yet in alpha release; but free plugins will work properly
* the new naming convention for v2 will be: e107 Bootstrap CMS
* discussion about users vs members naming conventions; Cameron will go through the language files
* concluded that we need an emphasis on 'English only'; we don't support foreign language packs yet!
* a GitHub page will be created were community can add their experiences with 3rd party plugins
* Cameron will find time somewhere in the next 24 hours to implement things in TinyMCE (amongst others: focusing on video and glyphs)
* some core plugins are candidate for core removal/obsolete, because they are based on coding that goes back to e107 0.6; that will not be compatible any more with e107 Bootstrap CMS; alpha 1&2 does not contain PDF plugin or calendar plugin - but can be downloaded from Github by those who need them.

Next meeting: June 7, 2014 (1pm PST = 2pm PDT = 9pm GMT)
May ’14
On Saturday May 17th 2014 we had another Skype developers meeting. Jimako, Kim, Smiley-uki, Tgtje, Moc, Miro, Cameron and myself were present. Just as the previous meeting this was an audio meeting, so I am posting a summary instead of a transcript.

The meeting was from 1pm PST till 3pm PST. It was a lively discussion and both Miro and Cameron have explained a lot of their ideas.

The outcomes:
  • There will be a attention to v2 alpha documentation in the immediate future (soon).
  • We have a roadmap: we consider the Github milestones as our official roadmap (and we will focus along the way on improving this while we go).
  • Developers will focus on prioritizing and categorizing issues on Github better.
  • There are a lot of cache related issued reported for v2 beta on Github; Miro will remove the cache for the v2 alpha version.
  • More important than cache; there are security concerns in new developments in v2 alpha. These will be improved before v2 alpha2 release.
  • We want to make more use of PHP5's built-in security related features.
  • PHP 5.3 will be the absolute minimum requirement for e107 v2 alpha.
  • e107 v2 alpha2 will not support multi-language websites.
  • e107 v2 alpha2 still contains base principles inherited from v1; which was developed organically. To get the things out that the majority of the developers want, we need to set-up things from scratch, those developments will be saved to future versions.
  • Semantic Versioning 2.0.0 might be applied to e107 v2 alpha versioning.
  • The SEO handling of plugins in the core has been noted for improvement.
  • Moc offered his help to go through the Github 'no milestone' issues. We happily invite everybody to support us and help us out!
  • Testing and reporting through Github is of vital importance to keep the development going.
  • There are still a lot of redundant language terms. We need community help pointing things out to us! Help us via Github!
  • There are still a lot of untranslated language terms hardcoded in the coding! We need even more community help pointing things out to us! Help us via Github; raise an issue or better: post a pull request.
  • For language files, only use [x] for language substitution (versus the usage of --x--).
  • Automatic translation of terms dates, numbers etc. can maybe be implemented.
  • There is a new Google+ e107 community.
  • Since the launch of the Google plus e107 community this triggered an increase in issue revivals on Github.
  • There will be a future change in approach in community communications.
  • Github, github, GITHUB and Github!

We are excited that e107 v2 hopefully will get even more attention at Github!

Next meeting topics: mysqlI, utf8mb4, development tools, frameworks etc.
Next meeting: Saturday 31-May-2014, 1pm PST = 2pm PDT = 9pm GMT
Click here for a countdown to the next meeting.
May ’14
Here at the e107 development center (we're actually individuals scattered all over the world) have this request: we need some development help to boost e107 v2 alpha.
It is fairly simple; we consider e107 v2 alpha as pretty stable already. In fact, it is already in use on a couple of websites out there.

That's why at first I thought of this way to help us out: the so-called 'FIXME hunt'. Here is a simple way to get started: look at Github for all the FIXME lines.
However, Cameron pointed out to me this might be disappointing because a lot of FIXME comments might be outdated.

Please bear in mind that with v2 we want to bring down the number of language terms, to make the job for the e107 Translation Team easier. So please re-use as much language terms as you can, and avoid introducing new language terms.

Instead of a FIXME hunt, our main community target should be the closing Github 'alpha2' milestone issues.
For those who don't code: what might be helpful is if you try to reproduce the issue, and then comment accordingly. This could benefit and help us prioritize what remains.
And for those that do code; a pull-request will be welcome.

Thanks in advance for your help, happy closing the ALPHA2 milestone issues and we are looking forward to see your contributions (commentary/pull requests/etc) on GitHub!
May ’14
On Friday May 9th 2014 there has been a Skype meeting. A few e107 members, Moc, myself and Cameron were present. Fairly quickly we changed to an audio meeting, so I am not able to post a transcript as I promised to do in the original meeting invitation.

The meeting was from 1pm PST till 4pm PST. Mainly it was me asking things and Cameron explaining or responding to it.

The outcomes:
  • all e107 programmers do this as a hobby, we don't earn money with the e107 project
  • all e107 programmers actually do have a life and need to support themselves, their real life companies and/or their real life families; so sometimes that influences priorities on how much time and effort to spend on e107. No further need to explain that in these past harsh economic times, our priorities were other than e107.
  • we speak of the wish that other developers will join us through Github
  • we will therefore focus more on Github
  • even the lesser experienced programmers are welcome to chip in through Github, and learn as you go, just as we did
  • e107 v2 can be considered already fairly stable; it is actually running successfully on a couple of private projects
  • there is a few things to fix in v2 before we can deliver it as stable ALPHA version
  • we want to focus on delivering a stable v2 ALPHA version as soon as possible
  • we will place more effort and attention into communication with the developers group, but also with the community; preferably directly through Github
  • we will pay more attention and facilitate in proper v2 ALPHA documentation, to make an introduction or transition to v2 more smooth
  • we very much need the support of language pack developers, and we try to focus on cutting down on the enormous amount of language terms. We try to have less duplication and therefore smaller language packs. While we're doing so, no official language packs can really be created by the Translation Team; also a lot of new v2 ALPHA software contains language-pack related issues.
  • we still continue to support e107 v1; we will support security fixes when and if they apply
  • the Object-Oriented way of programming might scare some coders; but that's all for 'under the hood'; you don't look under the hood when you're driving a car either. Attention has been spent in v2 to backward compatibility (database calls in a plugin in 'the old way' will still work). Basically the only new element a plugin needs to have for v2 is an accompanying plugin xml file. There is even a plugin builder in v2 that is able to create a plugin based on a SQL database file.
  • Github, github, GITHUB and Github!

Summing it all up, I had the feeling that all attendants were re-inspired, and we are all looking forward to kicking some life back into e107 v2 and seeing it bring some action at Github!
Mar ’12
Since the release of v1.0 of the e107 website content management system I have been appointed as the dedicated Translation Team Leader. We have done very well, and I would like to say 'Thank you!'.

We have established an amazing growth from 12 language packs in the 0.7.x era to 23 language packs in v1.0.0. My personal motivation is: the more translations we have, the bigger possible audience for e107 we might attract! And so far it has been very rewarding for e107.

Also I try to reach as close to 100% perfection as possible for all language packs, in order to assure the quality is also good for users working in foreign languages. That means there is close and intensive communication necessary with the official e107 translators. We discuss missing language items, language interpretations, features, bugs etc. Currently I'm still awaiting final contributions of Latvian and Norwegian, I hope we can also add these to the list on short notice. Of course we want to grow further, so we have set our goals to also have Korean and Japanese as supported languages. We are still looking for official e107 translators for these languages. These and more jobs can be found at the jobs section.

You can read the latest published news article about our language growth here:

In short, the list of e107 translation packages has doubled and is still growing. We would like to express our gratitude to our loyal members making this all possible, and a special thanks for all the efforts made by our expanding translation team. It's an excellent example of the potential of the community at the e107 website content management system.

EDIT: Norwegian language pack has been posted March 19, 2012.
Jun ’10

Development of PHP scripts without a preconceived plan to manage them is asking for a headache. The goal of a framework is to make the process of writing web-based applications simpler. Due to e107 popularity, things got a bit out of hand during the development. It is time to iron some things out that slipped in during these past years. Currently the e107 devs just 'make things work' and 'make things a bit more secure', but old legacy code is still there and it's procrastinating security and performance improvements. The e107 devs see a need to get rid of old procedural code and provide permanent solutions for the e107 system.

An application designed around MVC is easier to manage because it is split into tiers, which allow for independent development. This promotes code re-usability by building models, which are reusable throughout the application. That is why we would like to embrace MVC and single entry point (Front Controller) in the e107 0.8 version.

What is MVC?

Model-View-Controller (MVC) is a software architecture, currently considered an architectural pattern used in software engineering. The pattern isolates "domain logic" (the application logic for the user) from input and presentation (GUI), permitting independent development, testing and maintenance of each.

MVC is often seen in web applications where the view is the HTML or XHTML generated by the app. The history of e107 was working with classes, but not really in an MVC efficient way. Working with MVC will bring better OOP (object oriented programming) standards closer.

What's in it for you?

Applying MVC will bring you more security enhancement (possible 'sandbox-ed' environment, possibilities to implement security mechanisms on different application layers/request stages, etc).
Please note that the code producing will not take so much time. The time consuming process is the design and analysis - the code preparation phase to implement all this.

To summarize all benefits for you: a better, safer and much more flexible CMS platform, that will provide plugin writers to integrate even better in e107, with an architecture ready for future developments. The catch? Well, it might take a while; but that's an old story.

Relevant links