Nabeel

Try the public release, but have you modified the registration form at all?

Yep it does filter invalid characters, anything that's entered does get filtered for validity And yes, you need an API key for every site

I just registered for your VA:

You don't have any hub's added. Add a hub first, then it should work

what's this: "Google map logout "loop war""

Just a warning - this will produce disconnected PIREPs from the main, and also screw up your financial reports and NOT be accurate. I don't know the full back-end effects of this work around so any problems from it I can't really help you out there!

Put an echo in the function the recentfrontpage like echo "hello";, just to see if it's being called?

Hmm, seems to be working on both my test sites

It should be the code that novamix posted

I'm looking at it now, thanks Wasn't clear if it was a modified template or a code issue

What? It's done automatically when running the installer/updater

You shouldn't change that else { } statement, that'll break. I think you meant that in the first one

Make sure that you indeed to revert back to the original. A captcha was added to that form

It's been fixed in the 693 beta which went up about 20 minutes ago

Rev 693 - Case-sensitive class creation for autoload on GoogleChart.class.php29 April 2009, 3:53 pmRev 693 - nabeel (1 file(s) modified)Case-sensitive class creation for autoload on GoogleChart.class.php~ /trunk/core/common/StatsData.class.phpSource: phpVMSDownload from http://downloads.phpvms.net

The original worked?

copy the CREATE TABLE from the install.sql file, or: CREATE TABLE `phpvms_schedules` ( `id` int(11) NOT NULL auto_increment, `code` char(3) NOT NULL default '', `flightnum` varchar(10) NOT NULL default '0', `leg` smallint(6) NOT NULL default '1', `depicao` varchar(4) NOT NULL default '', `arricao` varchar(4) NOT NULL default '', `route` text NOT NULL, `aircraft` text NOT NULL, `distance` float NOT NULL default '0', `deptime` varchar(15) NOT NULL default '', `arrtime` varchar(15) NOT NULL default '', `flighttime` FLOAT NOT NULL default '0', `daysofweek` VARCHAR( 7 ) NOT NULL DEFAULT '0123456', `maxload` INT(11) NOT NULL, `price` FLOAT NOT NULL, `flighttype` VARCHAR( 1 ) NOT NULL DEFAULT 'P', `timesflown` int(11) NOT NULL default '0', `notes` text NOT NULL, `enabled` int(11) NOT NULL default '1', `bidid` int(11) NOT NULL default '0', PRIMARY KEY (`id`), KEY `depicao` (`depicao`), KEY `flightnum` (`flightnum`), KEY `depicao_arricao` (`depicao`,`arricao`), KEY `code` (`code`) ) ENGINE=InnoDB ; Run that in phpmyadmin. Make sure to change the phpvms_ to your proper table prefix.

Hey, Did you modify that template in any way? Try reverting to the default template

Rev 692 - Updates for central, file-locking when writing pages to prevent potential ...29 April 2009, 7:13 amRev 692 - nabeel (6 file(s) modified)Updates for central, file-locking when writing pages to prevent potential ...~ /trunk/core/classes/SQL.class.php~ /trunk/core/common/CentralData.class.php~ /trunk/core/common/FinanceData.class.php~ /trunk/core/common/PIREPData.class.php~ /trunk/core/common/SiteData.class.php~ /trunk/index.phpSource: phpVMSDownload from http://downloads.phpvms.net

Need some more details than that

I'm shooting for an update this weekend, this won't make it in, we'll try for the next one

Any financial stuff is accounted for if you use it. It's in the pipeline for some time

Basically, it goes like this: mysite.com/index.php/MODULE then MODULE -> Template A module is what's called a "controller", which handles the logic, getting data from a model (the api), and passing that data to a view (template) to output. Usually, most new programmers will plop everything into one file - all their SQL, their PHP and the HTML, all into one big file, which makes it a mess to extend, and a big mess to debug and eventually the next person who has to look at it, will shoot themselves (I come across alot of this code, it's not pretty). But this method is called "MVC" programming, "Model-view-controller", where the controller (a module) is the brain for that peice, and it will talk to the model (api) and then send its final data to the view (a template). This way is very powerful as you can shift things around, etc. In my methodology, I do the main Template::Set() calls in the Controller after getting the data from the model, and then Template::Show(), then in the template, I show the final output. That way, there are no calls to the model within a template, and it's very clear where to look for specific things; if you want to know how variables are set for the template, you check the controller. If you want to see what template is called, you check the controller. If you want to see what data is used, you check the controller, then you check the model since you'll know the exact path it's taking. And you can wrestle around with the template without touching anything in the controller or model. This way it's also really easy to see where bugs really are. Maybe reading this will help: http://en.wikipedia.org/wiki/Model-view-controller http://www.codinghorror.com/blog/archives/001112.html

Can you send the image to me?

Oh, the per-flight ones are rolled into the total number. It's not tabulated out the way the monthlies are... ...I think. If you add up the numbers, it should make sense