News 
 0.7.24 rc2 now available
 0.7.24 rc2 is now available. ( Click here to download ) This is a bug-fix release. We recommend that anyone using 0.7.23 or translating language files upgrade to 0.7.24 rc2 immediately. As always, please post any bugs/issues you may find in the bugtracker. Those of you who are using 0.7.22 may wish to wait for the official release of 0.7.24 before upgrading. Enjoy! posted by CaMer0n on Monday 06 September 2010 - 17:12:27 comments turned off for this item
More Acess Denied detailsI would like to give you some more details and hopefully speed up the 'next stable release' process. After the release of 0.7.24 rc1 I'm overloaded with false positives due to a missed point of the upgrade instructions (see previous news). This slows down the process of discovering of not covered yet (if any) issues related with the latest e-token security protection. The case is simple, we are able to stop those false positives with one line of code. However, this will solve our (core developer and support team) problems only. I'll give you some extra info which should help you identify us as 'good guys'  During e-token test, I found very bad issue - it was there forever. In few simple words, if you use default e107.htaccess (renamed to .htaccess) your site will do something like 10 to 20 extra sql queries (depending on your site configuration) plus of course additional php parsing processor job of your server per missing image/css/javascript file reference. A simple calculation says: if your average site sql requests count is 20, you have 4 missing images, you end up with 100 sql queries per page (instead 20). You should understand now the issue is really bad. Most of "Access denied" issues were side effect of the above. It's really easy for me to 'mask' the problem as solved, but I hope you understand now why I don't want to do this. We didn't invented upgrade instructions to 'keep you' busy, so please follow them, give us maximum information so that we'll be able to reproduce your problems, fix them and go forth. A whole 0.8 branch is waiting for us for the final work. I wish to use the moment and add big THANKS to all community members who helped us fighting the latest issues. posted by SecretR on Saturday 28 August 2010 - 06:47:22 comments: 10
Release CandidatesWell, despite what we thought was some good testing of our 'stable' 0.7.23 prior to release, some users' installations became 'unstable' after upgrading. We believe most of these issues have now been corrected, but rather than simply making another official release, we will be introducing beta 'release candidates' into our release process. In retrospect, this is what we should have done with 0.7.23 - so we've learned our lesson. From now on, the stable 0.7 will remain as such, and release candidates will be made available prior to any official release. This will allow us (and yourselves) to test the code more thoroughly and will also give official translators more time to update and validate their language-packs so they are ready in time for the next official release. We recommend that only experienced users upgrade to rc1, while less-experienced users may wish to stick with 0.7.22 or 0.7.23 (if it's running smoothly for you) So, here's 0.7.24 release candidate 1. (rc1) To upgrade from 0.7.x: 1. extract and overwrite your existing files 2. clear your site cache (admin->cache) and your browser's cache. 3. update/merge your .htaccess file (if you are using one) with the changes made in e107.htaccess 4. be sure you don't use footer_something.php override but the default footer_default.php in e107_themes/templates 5. post your bugs in the bugtracker when you find them. Its also worth reiterating that if you use the browser's 'back' button, a subsequent 'posting' of data will generate the 'Access Denied' error - this is a security feature. We'd particularly like to thank Allow and cyrus, who gave SecretR access to their sites to diagnose the problems (which weren't very obvious!) - without this constructive assistance things wouldn't have got fixed. Cheers posted by CaMer0n on Thursday 26 August 2010 - 11:47:11 comments: 38
0.7.23 Releasede107 v.0.7.23 is now available. This release is primarily aimed at reducing vulnerabilities and increasing e107's protection against exploits. (a special thank you to Justin Klein Keane ("MadIrish") for alerting us to the vulnerabilities, and commenting on the fixes.) One of the changes will also affect users who include youtube videos or other embedded media within their site; please see the included readme for more information. This release also includes some minor feature enhancements: Download Flood Protection (simultaneous downloads) Found in admin under downloads->options. Option to prevent a user from downloading multiple files within a short time-period. YouTube bbcode ([youtube][/youtube]) Allows you to easily add youtube videos to pages of your website. A conversion script is provided for those who have utilized html-code from Youtube already and wish to convert to the bbcode equivalent. (see included README.txt for details). By default, 'dangerous' HTML (such as the 'embed' code used with many media) is neutralised when it is displayed. This traps malicious code that may have entered the database before the latest updates were put in place. This filter can be disabled through the preference 'Filter HTML content'. Language-pack CreatorFound in admin under languages->tools. For those who are translating e107 into other languages, this tool will zip up your core language files into the standard language-pack format so that they can be shared easily with the e107 community. Important information on using this tool can be found here. Support for security include scripts. e107 now supports 3rd-Party security includes such as ZB Block without having to manually modify core scripts. Just install them in your root directory as you would normally. To include ZB Block, you would add the following to e107_config.php: $CLASS2_INCLUDE = 'zbblock/zbblock.php'; . e107 would then automatically include it in every page of your site. The full changelog can be found hereWe recommend that everyone upgrades to this new release as soon as possible. Click here now to download e107 v0.7.23, either as an upgrade or full-install.If you happen to find any bugs, please let us know. Cheers posted by CaMer0n on Friday 20 August 2010 - 14:00:11 comments: 67
So where to from here?There has been a lot of speculation about the future direction of e107 recently, and its time to put that to rest and move forward.
The dev team has spent quite a long time (weeks, if not months) discussing all aspects of e107 - the code, the community, the organisation, to try and establish a coherent plan for the future. Some of the results have been around for a while - the establishment of jira as an issue tracking system, some draft coding standards and guidance that we're refining before making public, better code documentation and so on. Overall the objective is to have a much more professionally run project.
We recognise that some things have been far from perfect in the past - sometimes simply due to lack of time; sometimes for other reasons. We're trying to get it right now.
It is also sad to lose McFly's input - hopefully not entirely, since he's still going to be around. As a long-term contributor to e107, its hardly surprising that he needs to concentrate on other things for a while.
Moving on, there are a number of things planned:
1. For 0.7, as well as continuing to maintain the code, we will be adding a few enhancements. These are mostly ones which the dev team already have available, or can release with minimal work, since we don't want to deflect too much effort from getting 0.8 on the way. Various members of the community are also working on enhancements which we will consider.
2. For 0.8, the intention is to move to a release as soon as possible. Part of the delay was due to a realisation that some of the structure was wrong, and is having to be redesigned. This is nearly done, and you should start seeing code changes in SVN soon.
We have a good idea of the final structure we need, and 0.8 is going to be the 'bridge' between old and new in order to maintain a reasonable degree of backward compatibility and provide an upgrade path.
3. On the organisational side, Cameron is going to be the overall project leader (much as jalist was in the early days), backed up by SecretR and myself as the 'old hands'. We already have a capable support team under the leadership of 2dopey, which will continue. The dev team is to be strengthened - as well as existing devs Bugrain and nlStart we have some other community members to be approached. One area where we'd particularly like some input is on the security side. We've also had a tremendous number of offers of talented assistance from all round the world. Not just on the coding side, but also in areas such as marketing and public relations.
So over the next few weeks, we're going to review all these offers, and put together a team to take e107 forward.
More to come - so watch this space.
posted by steved on Thursday 05 August 2010 - 18:11:05 comments: 67
I'll be in my bunkThis has been something I have been considering for quite some time and I feel the time is finally here. As of today, I am no longer developing for e107. The main reason for the decision is due to priorities changing. Other things in my life (work, family, fire department, etc) just seem to be taking up most of my free time and I can't devote the time to e107. It also seems that the fire has gone out for me, I just don't seem to have the desire to open up the code like I used to. For all the people that I have promised code for and for all of the work I have done that is incomplete, I am sorry. I had intended to tie up some loose ends before leaving, but it just didn't happen. I do not know what the future hold for e107, but I wish it the best. I will still be hanging out #e107 during the day, so I'll still be seeing some of you. I want to thank all of the people I have worked with on e107...especially jalist. He graciously accepted code from a complete php newbie and allowed me to get involved with the project. I have totally enjoyed my experience with e107. Now for some fun, for those of you that understand the reference of the news title...discuss Top three Firefly episodes: 1) Out of Gas 2) Objects in Space 3) Jaynestown Top 3 Firefly characters (not part of the crew): 1) Jubal Early 2) Stitch Hessian 3) Adelei Niska posted by McFly on Monday 02 August 2010 - 09:17:29 comments: 35
| 
