Pages: 12Next
Current Page: 1 of 2
Installation problems with 2.0
Posted by: gashaw ()
Date: January 23, 2008 03:04AM

Hi all,

First of all, thanks for writing such a nice program. It would work perfectly for our flying club here in Maryland, USA.

I installed 1.3 earlier today without any problems but 2.0 wasn't that simple. I have installed and verified all the pear modules using the pear installer and I am having problems with 2.0 installation. Here is the error message I get:

[mdb2_error: message="MDB2 Error: unknown error" code=-1 mode=callback callback=displayPearError prefix="" info="connect: [Error message: Access denied for user 'apache'@'localhost' (using password: NO)] [Native code: 1045] [Native message: Access denied for user 'apache'@'localhost' (using password: NO)] "]
Merci de la signaler à l'équipe de développement ici : http://bts.openflyers.org
OpenFlyers.org Aide en ligne Signaler un bug A propos...

I then edited conf/connect.php by hand and added the database name, username and password, but I still get the above error. Anyone has seen this before?

Thanks in advance...

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: January 23, 2008 01:24PM

Hi,

OF 2.0 is still in beta. It's reason why we do not produce a package. We still add/remove/rename database fields and tables. So, if we'd producted a 2.0 release, we should take care about modifications between this 2.0 producted and our current 2.0... Too many works!

I've no answer about your trouble. It's seems a simple database access trouble.

The better to do:
- install OF 1.3
- upgrade to OF 2.0 (you keep the database, you erase all files except connect.php).
(this method is validated)

Of course, you still need to get pear packages.

To upgrade, you go to http://something.org/openflyers/install/

The script should guess that you want to upgrade by reading the connect.php file.

Otherwise, if you want to try the 2.0 release without loosing time with install process (and many updates (we change the svn release 10 times per day)) do not hesitate to contact us for a private free test access!

See you,

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: gashaw ()
Date: January 23, 2008 10:08PM

Christophe,

I would really love to try it out. I want to show it to the club members and to the club board as well. So if you can give me private access, that would be great. Please contact me at

gashaw(at)marylandpilots.org

Thank you.



Edited 1 time(s). Last edit at 01/23/2008 10:09PM by gashaw.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: gashaw ()
Date: January 24, 2008 04:23AM

Chris,

The upgrade install method works and I am up. I don't have much functionality though.. I can't create users or aircraft or instructors.. The demo I see on your website looks much nicer.. I only get Bookings, Data, and Logout.. even logged in with the admin user.

So I guess I get the hint. Let me know when you have an account set up for me and I will get the club board members to test it.

Thanks.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: January 24, 2008 09:44AM

I send you a mail.

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: trystan ()
Date: March 16, 2008 08:02PM

I also have problems installing 2.0

I installed the 1.3 version, uploaded all the 2.0 files (apart from connect.php), but all I get is a white screen.

Trystan

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: March 16, 2008 08:51PM

Hi,

Have you done the update?

(install/)

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: trystan ()
Date: March 16, 2008 09:29PM

Hi Christophe,

Yes - install/ is just a white screen.

Trystan

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: March 16, 2008 09:34PM

Argh...

What about the php.log file? What does it say? (any error report?)

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: trystan ()
Date: March 16, 2008 09:52PM

I've re-installed the old version again, so it's difficult to know what error actually went into the logs, but here we go.

(In /etc/httpd/logs/error_log):

[client xx.xx.xx.xx] PHP Parse error: parse error, unexpected ')', expecting '(' in /home/xxxxx/htdocs/xxxx/includes/init.php on line 94
[client xx.xx.xx.xx] PHP Fatal error: Call to undefined function: _tr() in /home/xxxxx/htdocs/xxxx/install/connect.php on line 38
[client xx.xx.xx.xx] PHP Fatal error: Call to a member function on a non-object in /home/xxxxx/htdocs/xxxx/install/update_db.php on line 828
[client xx.xx.xx.xx] PHP Parse error: parse error, unexpected ')', expecting '(' in /home/xxxxx/htdocs/xxxx/includes/init.php on line 94
[client xx.xx.xx.xx] PHP Parse error: parse error, unexpected ')', expecting '(' in /home/xxxxx/htdocs/xxxx/index.php on line 55

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: March 17, 2008 12:46PM

Strange.

It seems like you do not have a complete 2.0 release.

You should try to get back the svn release and erase ALL files from OF 1.3 before copying OF 2.0.

Then put back connect.php (from OF 1.3) and rename config_sample.php (remove _sample)

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Bernie ()
Date: June 04, 2008 12:08PM

Hi everyone,

with the release I checked out today, 2.0beta doesn't seem to work at all.
Regardless whether I install the package from scratch or use the update procedure described above, I get these error messages:

Parse error: parse error, expecting `'('' in /srv/www/htdocs/trunk/includes/init.php on line 94

Fatal error: Call to undefined function: _tr() in /srv/www/htdocs/trunk/install/install.php on line 104

Very strange, indeed: I'm not really a PHP-crack, but line 94 seems to be ok, syntactically.
Line 104 tastes like a path-misconfiguration, as _tr() is definitely defined... somewhere...

Any suggestions how to get 2.0b running?
Thanks a lot,
Bernie

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 07, 2008 10:33PM

Bernie & Christophe, sorry I can't help specifically but I thought I'd mention that I've been following this thread with interest...

I tried to install v2 here, both separately & as an upgrade to a working 1.3 version but was unable to get it to operate. I'm aware it's work in progress & was happy to deal with that via cvs/svn so I could perhaps contribute with some doc writing but so far to no avail. My recollection is that eventually I could get through far enough to give a mdb2 error which I looked for on these pages - as far as I could tell someone else had the problem also but babelfish's translation left quite a bit to be desired so I'm still at a standstill despite quite a few hours of trying.

I'm sorry I'm unable to provide anything more than a report of my experience, there are definately times I wish I was a competent programmer!

So Bernie I'm with you, if someone finds a repeatable & foolproof means of installing V2 I'd be pleased to know, I'm sure that would help Christophe & team a lot too :-)

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 07, 2008 10:54PM

Update: I had another go with the latest svn release, this is the error I got:

[mdb2_error: message="MDB2 Error: not found" code=-4 mode=callback callback=displayPearError prefix="" info="unable to find package 'MDB2_Driver_mysql' file 'MDB2\Driver\mysql.php'"]

Previously I installed what I thought would be required but after re-reading things I discovered I hadn't indeed properly installed the MySQL optional feature :-|

That done I now find I have the same problem as Bernie - blank white screen but with the four redirect URL options at top left (to openflyers site, wiki, bug report & about). Not sure if that's helped but this was exactly as you suggest Christophe - complete new directory but with the connect.php copied from 1.3 & config.php renamed and the pear directory location updated.

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 07, 2008 11:11PM

Hmmm, I tried to edit my last post after re-reading Bernie's post & checking the log files but that [edit] didn't work, sorry for the repeats but here's a bit more info that may be of use:

Update: I had another go with the latest svn release, this is the error I got:

[mdb2_error: message="MDB2 Error: not found" code=-4 mode=callback callback=displayPearError prefix="" info="unable to find package 'MDB2_Driver_mysql' file 'MDB2\Driver\mysql.php'"]

Previously I installed what I thought would be required but after re-reading things I discovered I hadn't indeed properly installed the MySQL optional feature :-|

That done I now find I have the same problem as Bernie - blank white screen but with the four redirect URL options at top left (to openflyers site, wiki, bug report & about). However I get no php error that I can see in the logs. Not sure if that's helped but this was exactly as you suggest Christophe - complete new directory but with the connect.php copied from 1.3 & config.php renamed and the pear directory location updated.

FWIW this is the access log:

127.0.0.1 - - [08/Jun/2008:10:52:51 +1200] "GET /svn/ HTTP/1.1" 200 722
127.0.0.1 - - [08/Jun/2008:10:53:07 +1200] "GET /svn/about.php HTTP/1.1" 200 722
127.0.0.1 - - [08/Jun/2008:10:58:32 +1200] "GET /pagead/show_ads.js HTTP/1.1" 404 216
127.0.0.1 - - [08/Jun/2008:10:58:32 +1200] "GET /pagead/show_ads.js HTTP/1.1" 404 216
127.0.0.1 - - [08/Jun/2008:11:00:58 +1200] "GET /svn/about.php HTTP/1.1" 200 722
127.0.0.1 - - [08/Jun/2008:11:01:08 +1200] "GET /svn/about.php HTTP/1.1" 200 722
127.0.0.1 - - [08/Jun/2008:11:01:13 +1200] "GET /svn/ HTTP/1.1" 200 722
127.0.0.1 - - [08/Jun/2008:11:02:15 +1200] "GET /svn/install/install HTTP/1.1" 404 217
127.0.0.1 - - [08/Jun/2008:11:02:30 +1200] "GET /svn/install/install.php HTTP/1.1" 302 -
127.0.0.1 - - [08/Jun/2008:11:02:30 +1200] "GET /svn/install/askinfo.php HTTP/1.1" 200 1129
127.0.0.1 - - [08/Jun/2008:11:02:43 +1200] "POST /svn/install/install_db.php HTTP/1.1" 200 5927
127.0.0.1 - - [08/Jun/2008:11:03:40 +1200] "GET /svn HTTP/1.1" 301 229
127.0.0.1 - - [08/Jun/2008:11:03:40 +1200] "GET /svn/ HTTP/1.1" 200 722
127.0.0.1 - - [08/Jun/2008:11:04:17 +1200] "GET /pagead/show_ads.js HTTP/1.1" 404 216
127.0.0.1 - - [08/Jun/2008:11:04:18 +1200] "GET /pagead/show_ads.js HTTP/1.1" 404 216

Regards, Luke.

Postscript: Incidentally the /install/install.php seemed to work fine with no errors that I could see (as per the access log above), I'll post the output here just in case it helps:

Looks like the tables have already been created
Updating the table structure...
Conversion de la table ICAO
Mise à jour du champ NAME de la table icao
Mise à jour du champ ICAO de la table icao
Mise à jour du champ LAT de la table icao
Mise à jour du champ LON de la table icao
Mise à jour du champ ALT de la table icao
Ajout/Remplacement de clé primaire sur la table icao
Suppression de la clé primaire de la table icao
Suppression de l'index icao de la table icao
Création de la table balance_date si nécessaire
Mise à jour du champ id de la table balance_date
Ajout d'un champ balance_date à la table balance_date
Création de la table balance si nécessaire
Mise à jour du champ account_id de la table balance
Ajout d'un champ balance_date_id à la table balance
Ajout d'un champ debit à la table balance
Ajout d'un champ credit à la table balance
Ajout/Remplacement de clé primaire sur la table balance
Création de la table psp_transaction si nécessaire
Ajout d'un champ credit_account_id à la table psp_transaction
Ajout d'un champ debit_account_id à la table psp_transaction
Ajout d'un champ transaction_date à la table psp_transaction
Ajout d'un champ amount à la table psp_transaction
Ajout d'un champ description à la table psp_transaction
Ajout d'un champ payment_type_id à la table psp_transaction
Ajout d'un champ state à la table psp_transaction
Ajout d'un champ bank_answer à la table psp_transaction
Ajout d'un champ bank_misc à la table psp_transaction
Création de la table flight_tank_qty si nécessaire
Ajout d'un champ flight_id à la table flight_tank_qty
Ajout d'un champ tank_id à la table flight_tank_qty
Ajout d'un champ quantity à la table flight_tank_qty
Ajout d'un champ after_flight à la table flight_tank_qty
Ajout d'un champ account_id à la table flight_tank_qty
Ajout d'un champ pay_type à la table flight_tank_qty
Création de la table tank si nécessaire
Ajout d'un champ aircraft_type_id à la table tank
Ajout d'un champ tank_type_id à la table tank
Ajout d'un champ unit_id à la table tank
Ajout d'un champ label à la table tank
Création de la table criteria si nécessaire
Ajout d'un champ label à la table criteria
Ajout d'un champ predicate à la table criteria
Création de la table nationality si nécessaire
Ajout d'un champ label à la table nationality
Création de la table journal si nécessaire
Ajout d'un champ login à la table journal
Ajout d'un champ date_log à la table journal
Ajout d'un champ rights à la table journal
Ajout d'un champ rights2 à la table journal
Ajout d'un champ is_member à la table journal
Ajout d'un champ is_instructor à la table journal
Ajout d'un champ action à la table journal
Création de la table log si nécessaire
Ajout d'un champ action à la table log
Ajout d'un champ table_name à la table log
Ajout d'un champ field_name à la table log
Ajout d'un champ field_value à la table log
Création de la table account si nécessaire
Ajout d'un champ creation_date à la table account
Ajout d'un champ name à la table account
Ajout d'un champ export_account à la table account
Ajout d'un champ activated à la table account
Suppression du champs journal de la table account
Création de la table account_aircraft si nécessaire
Ajout d'un champ account_id à la table account_aircraft
Ajout d'un champ account_type à la table account_aircraft
Création de la table account_club si nécessaire
Ajout d'un champ payment_allowed à la table account_club
Ajout d'un champ order_num à la table account_club
Création de la table account_entry si nécessaire
Ajout d'un champ double_entry_id à la table account_entry
Ajout d'un champ account_date à la table account_entry
Ajout d'un champ account_id à la table account_entry
Ajout d'un champ credit à la table account_entry
Ajout d'un champ debit à la table account_entry
Ajout d'un champ payment_type à la table account_entry
Ajout d'un champ payment_description à la table account_entry
Ajout d'un champ person_delivery_id à la table account_entry
Ajout d'un champ comments à la table account_entry
Ajout d'un champ validated à la table account_entry
Ajout d'un champ exported à la table account_entry
Création de la table account_member si nécessaire
Ajout d'un champ account_id à la table account_member
Ajout d'un champ account_type à la table account_member
Création de la table account_member_type si nécessaire
Ajout d'un champ name à la table account_member_type
Ajout d'un champ order_num à la table account_member_type
Ajout d'un champ activated à la table account_member_type
Création de la table aircraft_type si nécessaire
Ajout d'un champ admin_desc à la table aircraft_type
Ajout d'un champ name à la table aircraft_type
Ajout d'un champ seats_available à la table aircraft_type
Ajout d'un champ comments à la table aircraft_type
Ajout d'un champ order_num à la table aircraft_type
Ajout d'un champ flight_time_formula à la table aircraft_type
Ajout d'un champ counter_state à la table aircraft_type
Ajout d'un champ tolerance à la table aircraft_type
Ajout d'un champ autonomy à la table aircraft_type
Création de la table aircraft_type_qualif si nécessaire
Ajout d'un champ check_num à la table aircraft_type_qualif

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 07, 2008 11:35PM

Ok, I'll make this the last message for a while!

I had a look at the source pages I was getting in 1.3 & 2, and fiddled a bit with the index.php & init.php files. It seems that there's quite a bit of authentication stuff in the v1.3 index.php that isn't present at all in v2's. Possibly irrelevant insofar as I guess it's done a different way but I can't see how (I said I wasn't a programmer!), anyway I thought I'd mention it.

The page source I get when trying to log into v2 is:

<div id="footer">
<div id="footerInfo">
<div>
<div id="footerLog">
</div>
<div id="footerlinks">
<a id="ofButton" href="http://openflyers.org">&nbsp;OpenFlyers.org&nbsp;</a>
<a id="helpButton" href="http://wiki.openflyers.org/index.php/UserDoc2.0">&nbsp;Online help&nbsp;</a>

<a id="bugButton" href="http://bts.openflyers.org/">&nbsp;Report a bug&nbsp;</a>
<a id="aboutButton" href="about.php">&nbsp;About...&nbsp;</a>
</div>
</div>
</div>
</div> </body>
</html>


Which is quite different from my working 1.3 (I won't bother posting that here).

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: utopie ()
Date: June 08, 2008 08:07AM

Hi
Openflyers 2.0 need special configuration, you can find what the server need pear packages, perhaps ut's your problem.
See here the needed pear packages :
http://wiki.openflyers.org/index.php/PEAR#OF_release_2.0

Stephane
OF team

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 08, 2008 11:09AM

Stephane, bonjour & thank you - I discovered that in fact there were some missing pear packages according to the list!

However after downloading and installing them unfortunately it has made no difference, most odd I get no error messages (before or after installing the additional packages).

Incidentaly I discovered the package name http://pear.php.net/package/HTML_Templace_IT on the openflyers website should actually read http://pear.php.net/package/HTML_Template_IT

I guess it's still possible I could have a faulty pear installation but I'm inclined to think it's ok, or that I should get some sort of error message if it were a pear problem? Perhaps it would be useful to have a working pear pool for v2 as you do for 1.2?

Any other suggestions gratefully received :-)

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: June 09, 2008 02:15AM

Hello,

I updated the PEAR package list. Thank you for your report.

To install OF 2, you have to install first OF 1.3 to get a database.

After, you delete all OF 1.3 files, then you install OF 2, and you make an upgrade of your OF 1.3 database (via the install process).

Take care of the config.php et connect.php files.

some have succeeded ;-)

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 09, 2008 09:44AM

Christophe, thanks for the reply...

I did have a working 1.3 when I ran the v2 installation script - I'm assuming the list I posted says that worked ok?!

Now what I have done is install 2.0 in a separate directory under the Apache root so as to maintain the existing - working - 1.3. I then copy the v1.3 connect.php file to the 2.0 directory, and modify the config.php to show the correct pear directory. I would have thought this would have achieved the same result as completely deleting the 1.3 files but perhaps there's something else I need to do?

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: June 09, 2008 10:06AM

There is nothing else at the end of your list? (only: "Ajout d'un champ check_num à la table aircraft_type_qualif"winking smiley

It sounds bad...

No error displayed?

What about our php error log file?

The error should be somewhere around the line 250 of the update_db.php file.

I've translated sentences in english. (your corrections are welcome)

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 10, 2008 10:01AM

Christophe, no there was nothing else, I will run the installation again just to check - I assume it won't make anything worse! :-) This is the first piece of info:

Following tables used by OpenFlyers have been found in the database:
account, account_aircraft, account_club, account_entry, account_member, account_member_type, aircraft, aircraft_qualif, aircraft_type, aircraft_type_qualif, authentication, booking, club, exceptionnal_inst_date, icao, instructor, ip_stopped, journal, log, login_stopped, member, member_qualif, parameter, qualification, regular_presence_inst_date... followed by a warning etc - looks like it has found the database ok.

Then it takes a while & I get:

Looks like the tables have already been created
Updating the table structure...
Création de la table balance_date si nécessaire
Mise à jour du champ id de la table balance_date
Mise à jour du champ balance_date de la table balance_date
Création de la table balance si nécessaire
Mise à jour du champ account_id de la table balance
Mise à jour du champ balance_date_id de la table balance
Mise à jour du champ debit de la table balance
Mise à jour du champ credit de la table balance
Ajout/Remplacement de clé primaire sur la table balance
Création de la table psp_transaction si nécessaire
Mise à jour du champ credit_account_id de la table psp_transaction
Mise à jour du champ debit_account_id de la table psp_transaction
Mise à jour du champ transaction_date de la table psp_transaction
Mise à jour du champ amount de la table psp_transaction
Mise à jour du champ description de la table psp_transaction
Mise à jour du champ payment_type_id de la table psp_transaction
Mise à jour du champ state de la table psp_transaction
Mise à jour du champ bank_answer de la table psp_transaction
Mise à jour du champ bank_misc de la table psp_transaction
Création de la table flight_tank_qty si nécessaire
Mise à jour du champ flight_id de la table flight_tank_qty
Mise à jour du champ tank_id de la table flight_tank_qty
Mise à jour du champ quantity de la table flight_tank_qty
Mise à jour du champ after_flight de la table flight_tank_qty
Mise à jour du champ account_id de la table flight_tank_qty
Mise à jour du champ pay_type de la table flight_tank_qty
Création de la table tank si nécessaire
Mise à jour du champ aircraft_type_id de la table tank
Mise à jour du champ tank_type_id de la table tank
Mise à jour du champ unit_id de la table tank
Mise à jour du champ label de la table tank
Création de la table criteria si nécessaire
Mise à jour du champ label de la table criteria
Mise à jour du champ predicate de la table criteria
Création de la table nationality si nécessaire
Mise à jour du champ label de la table nationality
Création de la table journal si nécessaire
Mise à jour du champ login de la table journal
Mise à jour du champ date_log de la table journal
Mise à jour du champ rights de la table journal
Mise à jour du champ rights2 de la table journal
Mise à jour du champ is_member de la table journal
Mise à jour du champ is_instructor de la table journal
Mise à jour du champ action de la table journal
Création de la table log si nécessaire
Mise à jour du champ action de la table log
Mise à jour du champ table_name de la table log
Mise à jour du champ field_name de la table log
Mise à jour du champ field_value de la table log
Création de la table account si nécessaire
Mise à jour du champ creation_date de la table account
Mise à jour du champ name de la table account
Mise à jour du champ export_account de la table account
Mise à jour du champ activated de la table account
Suppression du champs journal de la table account
Création de la table account_aircraft si nécessaire
Mise à jour du champ account_id de la table account_aircraft
Mise à jour du champ account_type de la table account_aircraft
Création de la table account_club si nécessaire
Mise à jour du champ payment_allowed de la table account_club
Mise à jour du champ order_num de la table account_club
Création de la table account_entry si nécessaire
Mise à jour du champ double_entry_id de la table account_entry
Mise à jour du champ account_date de la table account_entry
Mise à jour du champ account_id de la table account_entry
Mise à jour du champ credit de la table account_entry
Mise à jour du champ debit de la table account_entry
Mise à jour du champ payment_type de la table account_entry
Mise à jour du champ payment_description de la table account_entry
Mise à jour du champ person_delivery_id de la table account_entry
Mise à jour du champ comments de la table account_entry
Mise à jour du champ validated de la table account_entry
Mise à jour du champ exported de la table account_entry
Création de la table account_member si nécessaire
Mise à jour du champ account_id de la table account_member
Mise à jour du champ account_type de la table account_member
Création de la table account_member_type si nécessaire
Mise à jour du champ name de la table account_member_type
Mise à jour du champ order_num de la table account_member_type
Mise à jour du champ activated de la table account_member_type
Création de la table aircraft_type si nécessaire
Mise à jour du champ admin_desc de la table aircraft_type
Mise à jour du champ name de la table aircraft_type
Mise à jour du champ seats_available de la table aircraft_type
Mise à jour du champ comments de la table aircraft_type
Mise à jour du champ order_num de la table aircraft_type
Mise à jour du champ flight_time_formula de la table aircraft_type
Mise à jour du champ counter_state de la table aircraft_type
Mise à jour du champ tolerance de la table aircraft_type

There is no error showing in the php_error.log file for the server - nor was there the last time I ran it. There's no error that shows up on the screen when accessing OF2.0 either, I've just tried again, after the last 'install' and still the same white screen with the four url's at the top of the screen and no php errors.

Now I'm not sure if the update_db.php file should function by itself but I did try running it separately to see what would happen & I get "[10-Jun-2008 21:22:41] PHP Fatal error: Call to a member function query() on a non-object in C:\wamp\www\svn\install\update_db.php on line 830" but I guess that could be normal if it's not called properly from the askinfo script?

*Update*

I tried running it again several times and now I get a bit more:

Looks like the tables have already been created
Updating the table structure...
Création de la table balance_date si nécessaire
Mise à jour du champ id de la table balance_date
Mise à jour du champ balance_date de la table balance_date
Création de la table balance si nécessaire
Mise à jour du champ account_id de la table balance
Mise à jour du champ balance_date_id de la table balance
Mise à jour du champ debit de la table balance
Mise à jour du champ credit de la table balance
Ajout/Remplacement de clé primaire sur la table balance
Création de la table psp_transaction si nécessaire
Mise à jour du champ credit_account_id de la table psp_transaction
Mise à jour du champ debit_account_id de la table psp_transaction
Mise à jour du champ transaction_date de la table psp_transaction
Mise à jour du champ amount de la table psp_transaction
Mise à jour du champ description de la table psp_transaction
Mise à jour du champ payment_type_id de la table psp_transaction
Mise à jour du champ state de la table psp_transaction
Mise à jour du champ bank_answer de la table psp_transaction
Mise à jour du champ bank_misc de la table psp_transaction
Création de la table flight_tank_qty si nécessaire
Mise à jour du champ flight_id de la table flight_tank_qty
Mise à jour du champ tank_id de la table flight_tank_qty
Mise à jour du champ quantity de la table flight_tank_qty
Mise à jour du champ after_flight de la table flight_tank_qty
Mise à jour du champ account_id de la table flight_tank_qty
Mise à jour du champ pay_type de la table flight_tank_qty
Création de la table tank si nécessaire
Mise à jour du champ aircraft_type_id de la table tank
Mise à jour du champ tank_type_id de la table tank
Mise à jour du champ unit_id de la table tank
Mise à jour du champ label de la table tank
Création de la table criteria si nécessaire
Mise à jour du champ label de la table criteria
Mise à jour du champ predicate de la table criteria
Création de la table nationality si nécessaire
Mise à jour du champ label de la table nationality
Création de la table journal si nécessaire
Mise à jour du champ login de la table journal
Mise à jour du champ date_log de la table journal
Mise à jour du champ rights de la table journal
Mise à jour du champ rights2 de la table journal
Mise à jour du champ is_member de la table journal
Mise à jour du champ is_instructor de la table journal
Mise à jour du champ action de la table journal
Création de la table log si nécessaire
Mise à jour du champ action de la table log
Mise à jour du champ table_name de la table log
Mise à jour du champ field_name de la table log
Mise à jour du champ field_value de la table log
Création de la table account si nécessaire
Mise à jour du champ creation_date de la table account
Mise à jour du champ name de la table account
Mise à jour du champ export_account de la table account
Mise à jour du champ activated de la table account
Suppression du champs journal de la table account
Création de la table account_aircraft si nécessaire
Mise à jour du champ account_id de la table account_aircraft
Mise à jour du champ account_type de la table account_aircraft
Création de la table account_club si nécessaire
Mise à jour du champ payment_allowed de la table account_club
Mise à jour du champ order_num de la table account_club
Création de la table account_entry si nécessaire
Mise à jour du champ double_entry_id de la table account_entry
Mise à jour du champ account_date de la table account_entry
Mise à jour du champ account_id de la table account_entry
Mise à jour du champ credit de la table account_entry
Mise à jour du champ debit de la table account_entry
Mise à jour du champ payment_type de la table account_entry
Mise à jour du champ payment_description de la table account_entry
Mise à jour du champ person_delivery_id de la table account_entry
Mise à jour du champ comments de la table account_entry
Mise à jour du champ validated de la table account_entry
Mise à jour du champ exported de la table account_entry
Création de la table account_member si nécessaire
Mise à jour du champ account_id de la table account_member
Mise à jour du champ account_type de la table account_member
Création de la table account_member_type si nécessaire
Mise à jour du champ name de la table account_member_type
Mise à jour du champ order_num de la table account_member_type
Mise à jour du champ activated de la table account_member_type
Création de la table aircraft_type si nécessaire
Mise à jour du champ admin_desc de la table aircraft_type
Mise à jour du champ name de la table aircraft_type
Mise à jour du champ seats_available de la table aircraft_type
Mise à jour du champ comments de la table aircraft_type
Mise à jour du champ order_num de la table aircraft_type
Mise à jour du champ flight_time_formula de la table aircraft_type
Mise à jour du champ counter_state de la table aircraft_type
Mise à jour du champ tolerance de la table aircraft_type
Mise à jour du champ autonomy de la table aircraft_type
Création de la table aircraft_type_qualif si nécessaire
Mise à jour du champ check_num de la table aircraft_type_qualif
Mise à jour du champ qualification_id de la table aircraft_type_qualif
Mise à jour du champ CALLSIGN de la table aircraft
Mise à jour du champ TYPE de la table aircraft
Mise à jour du champ COMMENTS de la table aircraft
Mise à jour du champ ORDER_NUM de la table aircraft
Suppression de l'index ORDER_NUM de la table aircraft
Suppression du champs CLUB_NUM de la table aircraft
Suppression du champs SEATS_AVAILABLE de la table aircraft
Suppression du champs FLIGHT_HOUR_COSTS de la table aircraft
Mise à jour du champ non_bookable de la table aircraft
Ajout d'un champ ref_date à la table aircraft
Ajout d'un champ ref_hours à la table aircraft
Ajout d'un champ inspection_date à la table aircraft
Ajout d'un champ inspection_time à la table aircraft
Ajout d'un champ interval_visit à la table aircraft
Ajout d'un champ time_alert1 à la table aircraft
Ajout d'un champ time_alert2 à la table aircraft
Ajout d'un champ time_alert3 à la table aircraft
Ajout d'un champ day_alert1 à la table aircraft
Ajout d'un champ day_alert2 à la table aircraft
Ajout d'un champ day_alert3 à la table aircraft
Ajout d'un champ tolerance_time à la table aircraft
Ajout d'un champ last_counter à la table aircraft
Ajout d'un champ activated à la table aircraft
Ajout d'un champ non_flightable à la table aircraft
Destruction de la table aircraft_qualif
Création de la table aircraft_type_allowed_function si nécessaire
Ajout d'un champ place_num à la table aircraft_type_allowed_function
Ajout d'un champ function_id à la table aircraft_type_allowed_function
Création de la table aircraft_type_mandatory_flight_type si nécessaire
Ajout d'un champ flight_type_id à la table aircraft_type_mandatory_flight_type
Création de la table aircraft_type_uncomp_flight_type si nécessaire
Ajout d'un champ flight_type_id à la table aircraft_type_uncomp_flight_type
Mise à jour du champ NAME de la table authentication
Mise à jour du champ PASSWORD de la table authentication
Mise à jour du champ NUM de la table authentication
Mise à jour du champ FIRST_NAME de la table authentication
Mise à jour du champ LAST_NAME de la table authentication
Mise à jour du champ PROFILE de la table authentication
Mise à jour du champ VIEW_TYPE de la table authentication
Mise à jour du champ VIEW_WIDTH de la table authentication
Mise à jour du champ VIEW_HEIGHT de la table authentication
Mise à jour du champ AIRCRAFTS_VIEWED de la table authentication
Mise à jour du champ INST_VIEWED de la table authentication

I wonder if there's a timer somewhere that's expiring because it's taking too long to convert or something? It's an older laptop I'm doing this on so it's not the fastest machine around but it worked fine with 1.3. I've now tried the install several times and it appears to stop at different stages each time, presently the last line is "Mise à jour du champ HOME_PHONE de la table authentication".

Also I'm sorry Christophe but perhaps I've missed your translated sentences somewhere?

I'm not sure if any of that is useful but if there's anything else you'd like me to try please ask :-)

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: June 10, 2008 11:31AM

Yes! There is a timer: check your php.ini file
max_execution_time (At home, it's 300 ;-)

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 11, 2008 10:24AM

Hmmm, mine was set to 30 (seconds), I changed it, and a few other timer settings by a factor of ten (eg. so max_execution_time now = 300) but to no avail, it still does the same thing. In case it was a MySQL problem (I assume it's doing something with the database at this point) I had a brief look there but couldn't see any settings that would affect that - unless you're aware of any Christophe?

If there's no other likely settings to change I'm unsure what to do from here. I could perhaps try it on a different machine although this one is a 1.6Ghz Toshi with 380mb of RAM so I wouldn't have expected a problem. I think you said somewhere you were using XP, which I am, so doubt it's anything to do with that but I guess the other option is to try it on a Linux machine...

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: June 11, 2008 12:06PM

Hi,

I got XP, celeron 3Ghz and 1,18Go RAM... and no problem.

I also use PHP 5.2, MySQL 5, Apache 2.

Update your OF 2.0 from the SVN. (now sentences are in english)

Restart all (from a OF 1.3 database).

So you should be able to find the line mistaking in the install/update_db.php file.

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 27, 2008 05:22AM

Christophe, my apologies for taking a while to reply but I've had to find another machine and go through the installation process again...

.. the good news is that I've been able to achieve a (more or less) working version of 2.0beta :-)!

It's worth mentioning that, using WAMP, I had to specifically enable PHP_XSL in the php.ini file to get things working. Also I needed to do the OF2 installation twice (ie. run the installation script twice) before it would operate properly.

That said I'm now having trouble adding instructors and aircraft! I can add users, I can add aircraft type, but that's it. Could you tell me the process to go about doing that? It could be that I don't have it visible on my system for some reason, or it could be that I'm missing something myself but at this stage I'm a bit unsure...

Thanks, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: June 27, 2008 05:46AM

Hi,

The best is to open a test area here: https://www.openflyers.org/clientManager/subscription.php?step=subscription

If it's work on the test area, so your installation is not ok, if you don't achieve to create aircraft or instructors, so I will write down the process ;-)

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 28, 2008 09:58AM

Hi Christophe, I tried setting up a test account but am still waiting for the confirmation email - perhaps you do that manually or did I do something wrong?

Regards, Luke.

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: claratte ()
Date: June 28, 2008 10:56AM

No, it's automatic. I saw your subscription (and that you didn't confirm it).

I just send an automatic subscription reminder.

And I send you the same email manually.

So, you should receive id twice time.

If you receive it only one time or not at all, it's that there is a trouble somewhere... (maybe your anti-spam?)

See you,

Christophe

Christophe LARATTE
OpenFlyers manager

Options: ReplyQuote
Re: Installation problems with 2.0
Posted by: Luke ()
Date: June 28, 2008 11:58AM

Ok, thanks Christophe, I got it that time and confirmed it :-)

From a brief check it seems my local version is working ok so it must be something I'm not doing right! I'll do some study & see if I can work it out first before I ask...

Regards, Luke.

Options: ReplyQuote
Pages: 12Next
Current Page: 1 of 2


Sorry, only registered users may post in this forum.
This forum powered by Phorum.