PLEASE TEST. Commit in prep for Tech Preview 2 release

FYI:

I have committed all my rich-text editor changes and some miscellaneous bug fixes to the project trunk and it is available for testing in preparation for Tech Preview 2 release. Please SVN UPDATE and get testing so we can get this one out.

There are a few outstanding issues, which I will be posting soon, mostly in relation to the configuration options for the rich text editors in the manager, but otherwise, this should be releasable.

The sooner we get this out, the sooner we can start making our mark on the web....

Cheers

Jason--

Any way you know of to get a diff between your trunk last week and the one today? I need to update the code in my branch, too, but don't want to just rely on the SVN since mine is a little ... different.

Travis

Couple of possible issues:

1) http://vertexworks.com/forums/viewtopic.php?t=274 -- error page title on login pages.

2) The installer crashes every time in Safari 2.0 when changing the database name (while typing)... this is REALLY weird... and 100% repeatable on my machine.

P.S.
Travis, I think the changes are mainly updates to the Tiny/FCK code and... Jason, can you confirm? I've updated a few files here and there, but nothing major.

More minor install issues:

The name variables in setup.info.php override the variables in the index.php file, therefore the Module Name is presented wrong (we're not on RC3, any more... ... I'll fix this and a few other install files, along with a few other files, and commit later today.

I have a gut feeling that the Safari crash is due to the webelm.js file. Can this be consolidated to use the one located in the manager so we're not maintaining separate versions ... don't really need to duplicate files, do we?

Other than the Safari crashing on install (workaround by modifying the dang index.php file), and a few JS errors reported in Firefox, I think they look pretty solid.

Could everyone dowload the latest trunk and test this for any obvious show-stoppers. I've committed the minor installer tweaks, including version numbers now.

One last thing that should probably accompany this release is how to customize the way the editors show the buttons. Resources?

One last thing that should probably accompany this release is how to customize the way the editors show the buttons. Resources?

Ryan, I think we're going to need to allow those to be options before we need this information. For now, both are using fixed configurations, beyond the CSS file and selectors for TinyMCE. I'll find some time tonight to take a look at it.

Looking at FCK Editor, it's overwhelming ... LOTS of stuff everywhere.

We might think about putting in a basic content editor, then, with fewer options whether it's Tiny or FCK, it doesn't matter to me.

Guess I should check out their respective image managers too now

Looking at FCK Editor, it's overwhelming ... LOTS of stuff everywhere.

We might think about putting in a basic content editor, then, with fewer options whether it's Tiny or FCK, it doesn't matter to me.

Guess I should check out their respective image managers too now

Let me add options to select from the available themes on each. I'll do that, test it, and merge it in as soon as possible. Any other basic options for either or both editors that definitely should be included in the tech preview, while I'm at it?

Guess I should check out their respective image managers too now

And I don't have these image managers/file managers working properly either, at least not in my local Apache 2 install on Win XP :roll: Trying to figure out how to properly configure the paths in them.