Just a quick FYI:
We have now opened up branch development (http://svn1.cvsdude.com/rethrash/tattoo/tattoo/branches) of MODx in SVN to the public (read-only access, of course). This is the first in a series of efforts to further streamline MODx development and contribution processes, by making them more transparent.
Currently, only the 0.9.6 branch is available, but once 0.9.6 is released, a new public branch for 0.9.7 will be made available for tracking progress on the next-generation MODx. Until then, you can access the latest 0.9.6 branch at:
http://svn1.cvsdude.com/rethrash/tattoo/tattoo/branches/0.9.6
OR
https://svn1.cvsdude.com/rethrash/tattoo/tattoo/branches/0.9.6
Have fun, but remember, branches are not stable pieces of code; so use this cutting-edge access to test our bug fixes as we commit them, or to prepare to make your own contributions to the project.
Jason, is this still your intention to open up a public branch for 0.9.7 so progress may be tracked? My understanding from this post was to make development even in the earlier stages more transparent. However, it appears like this might now be reserved for people subscribed to one of your commercial support offerings, based on
http://modxcms.com/forums/index.php/topic,16100.msg110950.html#msg110950? I guess I am trying to understand the layers of transparency you are trying to establish.
Jesse R.
Consider trying something new and extraordinary.
Illinois Wine
Have you considered donating to MODx lately?
Donate now. Every contribution helps.
-
MODX Staff
- 10,725 Posts
First, I’m in the process of finalizing some major infrastructure changes (moving SVN to a private server fully integrated with Trac and Fisheye/Crucible) that will be part of the process of increasing transparency on the 0.9.7 code base.
But more importantly, the state of the 0.9.7 branch (and lack of accompanying documentation) is unfortunately still such that I do not feel comfortable opening it up to the public. Once I am confident with the state of the code for public consumption, it will be opened up. Until then, if you want to participate in the ongoing 0.9.7 development, you can request membership on the team to collaborate on development, request read-only access to observe as a potential 3rd-party add-on/extension developer, or show some other intention to contribute (i.e. commercial support subscription). I know many of you feel this is a catch-22 (I don’t know that I want to contribute until I see the code), but this is a temporary limitation I feel is necessary to prevent premature experiences (potentially negative) by non-developer users who might expect stability and usablity similar to the current MODx releases (or even the latest 0.9.6 SVN snapshot).
My apologies for my over-excitement in past posts indicating it would be public many moons ago, but we made some decisions over the past few months that created some challenges I did not originally plan to deal with in this release, and I certainly don’t want the entire spectrum of MODx users to deal with them. However, the end-result will be IMHO well worth the delays to public access.
If you do not want to request a place on the team, observer access, purchase a commercial support subscription, or wait for public availability, you could alternatively spend some time with the latest xPDO code, which is fully available via public SVN. This is the core of the new MODx 0.9.7 code base, and becoming familiar with it should keep you occupied and better prepare you for the code shock you will inevitably feel when you see the new core.
How’s this full implementation coming along? And for the immediate who do we ask to request read-only access to the 0.9.7 SVN?
Hmm. I might need a pointer on the best way to make automatic SVN updates work.
I’m using a shared server on 1&1.
-
MODX Staff
- 12,272 Posts
Does SVN run on the server and do you have shell access?
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 10,725 Posts
Hey folks. Stop! As has been said time and time again, this is still alpha software. You can get banned for running alpha software on shared servers (at least you should, and would if i was running the server). So don’t do it. This is not ready for it, period. In fact, there will be specific releases for shared server users.
I’ve been running 0.9.7 (on localhost) for a while but it blew up on me today.
I turned the global cache off in Tools | Config and turned CAPTHA on. When I try to access the manager, I get this:
[2007-12-20 12:05:32] (ERROR @ /mysite/manager/index.php) Could not load context: mgr
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at C:\Program Files\xampp\htdocs\mysite\core\xpdo\xpdo.class.php:1205) in C:\Program Files\xampp\htdocs\mysite\core\model\modx\modx.class.php on line 2368
Warning: Cannot modify header information - headers already sent by (output started at C:\Program Files\xampp\htdocs\mysite\core\xpdo\xpdo.class.php:1205) in C:\Program Files\xampp\htdocs\mysite\core\model\modx\modx.class.php on line 2377
Fatal error: Call to undefined method modRequest::initialize() in C:\Program Files\xampp\htdocs\mysite\manager\index.php on line 93
Going to the site, not the manager, I get this error but the home page still displays as usual but with the error at the top.
[
2007-12-20 12:06:34] (ERROR @ /mysite/index.php) Could not load context: web [2007-12-20 12:06:34] (ERROR @ C:\Program Files\xampp\htdocs\mysite\core\model\modx\modx.class.php : 653) PHP warning: array_search() [function.array-search]: Wrong datatype for second argument
Can I get a tip on where in the database I can turn the cache back on? I’m hoping that will let me back in.
Bob
-
MODX Staff
- 10,725 Posts
BobRay, that captcha mechanism is going to likely be removed, or hopefully replaced, before we go beta with this.
Also, re: the global cache, I have not tested with all caching turned off lately, so that is likely broken from recent merges/changes.
