PLEASE TEST. Commit in prep for Tech Preview 2 release

IMO, to really clean up everything, both the manager and the site itself should have their own set of $base_path, $base_url, and $site_url variables. And these should be accessible as configuration settings that can be set to something specific if need be (e.g. supporting IIS or other non-Apache servers).

Not sure that I follow, but that could be because I've been up over 72 hours now. Explain further, please?

IMO, to really clean up everything, both the manager and the site itself should have their own set of $base_path, $base_url, and $site_url variables. And these should be accessible as configuration settings that can be set to something specific if need be (e.g. supporting IIS or other non-Apache servers).

Not sure that I follow, but that could be because I've been up over 72 hours now. Explain further, please?

Well, the manager path is going to be constant, while each site's url would be unique, so how did you address that? I was thinking the manager would store the configuration for each site in the database, so at runtime, the paths would be correct for the specific site, while the manager would have it's constant manager base path/url. And then either provide API functions to access the site specific ones, and keep the manager ones global. Or...I'm just thinking out loud...

As for having a configuration override capability, I think that goes without saying. Auto-determine it for them, but allow them to override the value if they want to, just like the image plugin path and URL.

Bypassed above issue by just removing the & from the arguments, and logged in OK, opened the System Configuration, and several of the items are displayed badly (narrow column under the label, or way off on the right side, clear off the page), and the "cleanup" page reloading problem is still alive and well. This is with the new Safari.

Outside of purely aesthetic issues, are there any changes we should make to get it working better in Safari... if anyone can figure out a solution for the infinite clean-up loop for new installs, that would be great; it's not isolated to Macs, either, FYI (see the bug report forum).

Jason, how's the FCK and/or Xinha progress coming? Nice work on getting Tiny MCE up and running. Could you commit the stuff to date in case someone wants to peek at the code in order to lend a hand. I'd like to get this out pronto!

Jason, how's the FCK and/or Xinha progress coming? Nice work on getting Tiny MCE up and running. Could you commit the stuff to date in case someone wants to peek at the code in order to lend a hand. I'd like to get this out pronto!

Ok, got FCK's latest File and Image Manager plugins to work somewhat -- though it is not working with relative paths still (e.g. if you use a path relative to the site root and the site is not in the document root, images don't show up in the wysiwyg; plus it inserts full paths when selecting images/files from a directory). I'm thinking if we can integrate the standalone HTMLArea ImageManager into TinyMCE, FCK, and Xihna, that might be the best next step. I included the standalone version in my branch (under /manager/media/imagemanager) for anyone to experiment with.

Xihna looks great, but I haven't gotten the plugins working yet, especially the ImageManager; it's using some new backend.php stuff instead of different URLs for each action and these requests aren't working currently. I've removed the ability to select Xihna for now.

Working on checking in my branch...should be in within the hour.