Active Agenda Community

[robbie-w]

Hello,
Just to let you know on a fresh install of the latest SVN the file s2a/install/empty.sql is missing

Im in trouble somebody lost the database here when he upgraded the server to 2008 lol. I guess I have some data input to do this weekend

Robbie

[robbie-w]

This is when running the DB install by the way

I cant remember if I was supposed to install the 0.8.2 before I went the SVN root so ill probably find out shortly

Robbie

[robbie-w]

Just another observation the s2a-install-db.php only installs to a local MySQL server. There is no option for it to install to a remote server

It would be good if it could pick up the DBHost from the config file

Robbie

[robbie-w]

Ignore the missing file. I've not done this for so long I was a little rusty on the procedure

Are you going to release a 0.8.3.zip to make things easier for new installations?

Robbie

[robbie-w]

Think im going to need some help heres what i've tried

1) in my parent folder I have extracted the 0.8.2.zip to s2a_release and made sure obviously that the folder structure is correct

Now these are the variants of what ive tried next

2) created a folder called s2a, using tortoisesvn done svn checkout. Repository https://activeagenda.svn.sourceforge.net/svnroot/activeagenda/trunk
Checkout folder is s2a

This downloads the latest SVN version however doesnt merge in anything from s2a_release

Other option

2) The other thing I tried was extracting the 0.8.2 install as well to an empty s2a folder and running an svn_checkout on this. This downloaded the latest SVN but did not overwrite any files which already existed?

Where am I going wrong? Can I write you alternative installation instructions for your wiki? I seem to remember getting stuck at this stage last time

Thanks

Robbie

[robbie-w]

Think I should read things twice nxt time . I forget the SVN version isnt an installable one.

By using a subversion client, it is easy to follow the development of new features in Active Agenda. This should be done for testing/learning/evaluation purposes only, not "production".

The following "recipe" assumes that you have installed the SVN client of your choice, as well as the general requirements.

1. Download the latest release from http://www.sourceforge.net/projects/activeagenda

2. Extract the files with the parent folder being s2a. Follow the general general installation procedure: Edit the config.php and gen-config.php files. Install the database. Configure the web server and test that all is working. You must complete this and step 3 before attempting to update to the latest SVN

3. Re-name the s2a folder to s2a_release.

4. Use your Subversion client to check out the latest source from https://activeagenda.svn.sourceforge.net/svnroot/activeagenda/trunk into a new s2a folder in the same parent folder as your s2a_release folder.

Using the svn client, it would be done like this:

$ cd /path/to/s2a-parent
$ svn checkout https://activeagenda.svn.sourceforge.net/svnroot/activeagenda/trunk s2a
In TortoiseSVN, you would right-click in the correct folder (parent of s2a_release) and find the TortoiseSVN->Checkout... menu item. In the dialog box, enter the URL https://activeagenda.svn.sourceforge.net/svnroot/activeagenda/trunk and make sure it places the checked out contents in a new s2a folder: C:\path\to\s2a-parent\s2a.

5. Now we need to copy some files and folders from the s2a_release folder to the same location in the new s2a folder tree:

active_agenda/config.php
active_agenda/gen-config.php
active_agenda/uploads
6. Generate all modules with the s2a.php script (see the Generating a Module article).

cd /path/to/s2a
php s2a.php
Depending on the changes that have occurred since the latest release, you may be prompted to allow database table modifications. There is also a possibility that dependencies with not-yet-generated modules cause a module to fail with an error message: after the other module has been generated, you can simply re-try the failed module again (the script will prompt you once).

7. You should now have the latest code running on your server.

Check that file permissions allow error messages to be saved in active_agenda/s2alog/errors.log (web server must have write permissions to this file), as well as active_agenda/uploads

[mattias]

[mattias]