0.9.6.2-rc1 is available for download

Quote from: MotSmart at May 17, 2008, 12:33 PM

Just a question or consider it as a suggestion, Can we include an RTL manager theme (based on MODxlight manager theme) & another one for the front-end use (based on MODxHost template) as of default theme/template in both back & front-ends?

BTW theme/template is ready to be committed, So what do you say?

MotSmart, I would prefer if that is distributed separately, in the spirit of where MODx is heading with the 0.9.7 release (total separation of core and add-ons/extensions).

I will look into incorporating whatever changes are necessary to support RTL languages in the core, but actual theme/templates need to remain separate.

Jason, Thanks for clearing that out, Now how about this (link)?

Just curious! how is the 0.9.7’s add-ons/extension system?, I mean is it going to be just like the repository section that anyone interested to have something will go and grab the desired thing or there will be a ready-to-use package (Which includes most favored extensions) that will be offered, or there will be some automated system of add-ons/extensions like FF or SMF that have remote install feature?

Quote from: MotSmart at May 17, 2008, 10:19 PM

Jason, Thanks for clearing that out, Now how about this (link)?

I’ll try and review that this afternoon and merge it in.

Quote from: MotSmart at May 17, 2008, 10:19 PM

Just curious! how is the 0.9.7’s add-ons/extension system?, I mean is it going to be just like the repository section that anyone interested to have something will go and grab the desired thing or there will be a ready-to-use package (Which includes most favored extensions) that will be offered, or there will be some automated system of add-ons/extensions like FF or SMF that have remote install feature?

In 0.9.7, Transport Packages are simply a way to collect and distribute data and/or file system assets in a platform-independent bundle. These packages can be used to move just about anything:

• A single add-on or extension, e.g. a snippet package would include the database object representing the snippet and all it’s dependent files
• A set of Resources demonstrating the use of an add-on or extension
• A set of Resources that have been updated in a development deployment and need to be distributed to staging, production or other deployments
• You can even script the installation of these objects and file assets in order to handle upgrade procedures, register plugin events, or just about anything else you can script with the MODx API, or PHP period.

In addition to the packaging technology, there will also be a distribution aspect provided by an add-on package that we will be distributing (hopefully with beta), that will allow anyone to setup a "Web Transport Facility" where users can access available packages and download them manually, or directly to another MODx installation. This facility will consist of various web views into the packages being hosted as well as a set of web services for managing and accessing the packages. MODx will of course host a primary transport facility similar to our current Repository where we will feature "reference" or official add-on and extension packages. Individual add-on/extension authors will have a choice to work with the MODx Team and Community to produce a reference package to be featured from the MODx Web Transport Facility, or can become their own package provider by setting up their own facility.

It might be a bit last minute, but could you include this fix?
http://modxcms.com/bugs/task/1060

Many thanks Jason, MODx future seems to be like a wider highway! that allows faster driving speeds for developers!

Quote from: coroico at May 16, 2008, 02:00 PM

Until now, it was a proposal, first (#MODx87) proposed on crucible. I have added the #MODx141 correction proposed by Shane and ask for some tests.
Ok I will commit these changes and ask for testing. In the same time, This will need to update the language files of the new installer. I will organize that with Motsmart.

@ coroico
Any news on above quote? Oh! after i posted this i reviewed FishEye and found that this is committed to the SVN by rev#3710
So ill go to collect the languages files. Thanks!

I’m about to crash for the evening, but could someone please test the current RC to see if you can change doc restrictions. I’m seeing an 0962 rev from some point but we’ve got 2 custom groups created and you can’t alter the groups w/o using the doc manager ... changing the checkboxes has no effect.

Another long standing bug which now has a code fix attached - would be good to get in 0.9.6.2 too:
http://modxcms.com/bugs/task/1022

Alright, I’m going to merge any additional commits to the 0.9.6 branch, and prepare the build around 6pm CST today (midnight Friday GMT), so finish testing and commit what you want to make it in to RC1 as soon as possible.

Public RC1 or RC2?

Quote from: rthrash at May 22, 2008, 04:59 PM

Public RC1 or RC2?

Official public RC1; the download I put up there originally was premature.