Release Plans

Travis has some things unexpected take him out of the pictures for a few days, so here's what I'd propose we do:

Raymond is adding a few files to the base set uploaded earlier including a couple of bugfixes cured by the new sql file uploaded in the forum too. After that, I'd like to have everyone give it a quick test on an upgrade install and a fresh install.

If that passes, hopefully Susan in the interim will make the installer a bit more friendly when making goofs (retry button on relevant pages, and longer pages when appropriate). I'll also collect a few more of the "Web Standards" oriented snippets to the installer, such as ListSiteMap and a few others, and we'll toss it out to the public.

Travis should be done with the code formatting inconsistency cleanups and creating a new manager layout that works cross-platform/cross-browser much better by sometime Monday I'm hoping. We can then test and tweak those options, make any improvements thereto, and fix any bugs users find in the forums.

I'd like to unveil "Tattoo" officially with a new manager layout that will be default and that MUST be superior to the stock Eto layout. We'll also offer the "legacy" layout too, of course. I'd like to do this roughly 2 weeks after the "preview" release this weekend.

What am I forgetting here?

Well, I think I fixed it...made a few small changes to the css file, and changed the javascript in the index.php file to display the "Back" button on the summary screen. I added a sentence to the failure message to the effect that you could re-run the tests by clicking on the "Back" button. I am not sure if there was a good reason for the "Back" button being disabled on that screen; I'll have to try a fresh install to see what happens.

Thanks Susan; I'm sure it won't be too tough to get it sorted out quickly.

Ok, that was a dud...the check is actually done as the as the page is being generated, so using the "back" button, since it only hides/displays what was already generated, of course did nothing. (duh!) So, I removed the ob_ stuff from the Summary function, renamed it, and called it at the bottom of the intro page. Then I created another page 6, that justs says to click the button to install. Works great; now you know immediately if your files and stuff are OK, and only have to hit the reload button on the browser to rerun the checks before you go any further. If the checks fail, there is no "Next" button. Of course, that final page needs to be dressed up, but at least it works.

I'm sure Ajax would have worked here; a "retry" button to call a .php file to re-run the checks and write the new results...but this was easier.

http://www.sottwell.com/private/installfiles.zip

Here's the latest greatest files with a few bug fixes and lots of little installer tweaks. Can everyone try to test these to see if they're working for you, please? Upgrade and new installs should work on pretty much everything:

New files
Documentation

Before releasing this to the public, I'd like a bit more testing and the additino of some additional snippets from the Eto Snippet library, ListSiteMap, comes to mind, as does our Tell-A-Friend snippet/chunk/page combo.

Back button, retry and other contingencies should now be handled much more gracefully in the installer. If someone could come up with code to actually create the config.inc.php file on Unix/Linux that works, that would make it one-step better for those OSes. That's around line 336 of /install/index.php. It works on Windows servers, but not my Linux box.

Thanks!

Installation works fine for OS X.

Except you still forgot the "plugin" field in the site_snippets table.

Installation works fine for OS X.

Except you still forgot the "plugin" field in the site_snippets table.

The plugin field should be gone now, along with all references to it in regards to the site_snippets table.

Installation works fine for OS X.

Except you still forgot the "plugin" field in the site_snippets table.

Are you saying that the table needs to be modified, or is it that there's still some files calling the plugin field?

OK, based on what I can tell, we've got a pretty major problem with Firefox and the buttons. I think it's time that we come up with a definitive strategy to get rid of the cool web fx "stuff". It's just plain aweful.

How big of a process would it be to go through and replace the JS calls to the current buttons with code that looks likethe following code?

Actually, it might be good to create a button class that accepts the button action as the onclick action, and that also disables the button and optionally pops a message when clicked. What do you think?