simpilot

You have copied the necessary code into your post <?php echo 'Pilot average landing rate '.TouchdownStatsData::pilot_average('pilot#'); ?> Replace the 'pilot#' with the variable that contains the raw pilot id from the database for the page that you are on, it varies from page to page and is unavailable on some.

Are you filling the variables with the data needed for the form?

There is a section deep in the PilotData.class.php file function that builds the signature that should look something like this depending on the version; # Add the country flag, line it up with the first line, which is the # pilot code/name $country = strtolower($pilot->location); if(file_exists(SITE_ROOT.'/lib/images/countries/'.$country.'.png')) { $flagimg = imagecreatefrompng(SITE_ROOT.'/lib/images/countries/'.$country.'.png'); if(Config::Get('SIGNATURE_USE_CUSTOM_FONT') == false) { $ret = imagecopy($img, $flagimg, strlen($output[0])*$fontwidth, ($yoffset+($stepsize/2)-5.5), 0, 0, 16, 11); } else { # figure out where it would go $ret = imagecopy($img, $flagimg, $flag_bb[4]+5, $flag_bb[5]+2, 0, 0, 16, 11); } } It should calculate the placement automatically but if you have altered the class to change the size it is probably not seeing that and you will have to adjust it manually which may be a little tough with names of different lengths. The section - $flag_bb[4]+5, $flag_bb[5]+2, 0, 0, 16, 11 - is what sets the image location on the background. The settings are explained here -> http://www.php.net/manual/en/function.imagecopy.php

Link?

Delete the local.config.php file. Video (although I am told it is not needed) and other comments - http://forum.phpvms..../page__hl__line

Looks like you have the wrong version of the plugin manager for the phpVMS version you are using. Try using the one under the releases tab taht uses the .tpl extension.

http://forum.phpvms.net/topic/18860-i-have-a-xxxxxxtpl-file-not-found-error/

As Jeff pointed out -> "You must install the module" http://www.victorvirtual.org/index.php/kacars_free shows that the module does not exist.

http://forum.phpvms.net/topic/18860-i-have-a-xxxxxxtpl-file-not-found-error/

The module does not really keep data week by week, it only uses the data available from the PIREPS table. You could alter the sql code in the module to just look for rates within a certain time frame and use the date function to set the current week.

There were a couple of small items added from Oxymoron for addressing and data validation.

php 5.3 will be supported at least through 7/2014 with security releases but many hosts are opting to switch now. It is unfortunate if they are upgrading without any notice to their hosted clients. That leaves two choices then at this point. 1 - Switch to a host that is using php 5.3.x (5.3.27 is the current release form 7/2013) 2 - Work your way throught the system to change the items that are causing havoc with the 5.4 migration, or supress the errors in the php.ini file as some have done, which I can not say is 100% as I have not tried it that way any more than installing a clean install with it. A third choice is to try the version I have for 5.4 on my Github account, I have cleaned up the errors I have come across so far, not to say there is not more. Also, do not take my version as any type of offical release of phpVMS, I do however have a couple of client sites running onit right now.

It looks like you are probably on a server running php 5.4.x - It has been an open issue for phpVMS and sites migrating from php 5.3 to 5.4. You can search for 5.4 errors and strict standards errors in the forums and find a lot of fifferent approaches to a fix. You can also find a 5.4 version I have been working on my github account under the 5.4 dev branch. It addresses a lot of the issues with using php 5.4. It in no way should be considered any type of an offical version.

If you have this error in your phpVMS system it is one of two things. #1 - The file is simply not where it belongs. Follow the path in the error and make sure the file is in that path. If it is not in the correct folder it will not be found. #2 - If you are downloading any of my modules from GitHub most likely you are downloading the newest version which has template files using the .php extension instead of the .tpl extension. I have changed this so the modules will work with the latest development versions of phpVMS which uses the .php extension as well as some other items to try and help secure the system. If you are running an older version that is still using the .tpl extension then look under the releases link in the github panel for the last release for .tpl file versions and download that one. Example -> main Github page for AirMail -> https://github.com/D.../phpVMS-AirMail The version you download from this page uses the .php extensions. -> if you click on the releases link right under the title you will get the releases page -> https://github.com/D...irMail/releases - You should see a version that is notated with something to the effect of - Final version using .tpl template format for <= phpVMS version 2.935 - ALSO: The plugin manager would make all this automated for you and it automatically knows which version of the module to install. I think it is probably one of the better items as far as addons for phpVMS. If you already have modules installed and try to install them again with the PlugIn Manager you will probably lose any data that you had prior. This will not happen if the module was installed with the Plugin Manager.

His posts do not have to be approved, he has more than 5 so they are automatically approved.

AirMail 4 is for the latest development version of phpVMS and uses .php as the template extensions and it look slike you have an earlier version as it is looking for .tpl extensions for template files. Go under releases on the github account and us ethe last 3.x version of AirMail. https://github.com/D...irMail/releases http://forum.phpvms.net/topic/18860-i-have-a-xxxxxxtpl-file-not-found-error/

The pull resuest can be found here -> https://github.com/nshahzad/phpVMS/pull/115 You can find the fix in the development version here around line 62 -> https://github.com/DavidJClark/phpVMS/blob/6802f722a26e8d7822f66f3b35b15b0407e9cd46/admin/templates/settings_mainform.php <- you will have to find the same code inthe production version and change it to make the drop down work.

You will have to find help from someone else until the powered by phpVMS is returned to your site. BTW, this question has been asked and answered many times already....

No, as stated the "releases" link...... https://github.com/D...ooking/releases

It is the same one you downloaded the module from and is in my signature......

It is in my Github account under the releases link

You have downloaded the latest version. download the older version under the releases option that uses the older .tpl extension for template files.

Sorry you feel that way, it just seems that after a dozen or so threads of the same issue and many claiming that the fix does not work there needed to be a "proof of life" message to show that it does indeed fix the issue. I am leaving it in place as hopefully it will help someone else.

If I remember I think it is an issue with ASP tags on the server the site is on.

I have an extended version on Github. There are a coupe of things you need to know about it though. 1 - It uses the newer .php template file extensions versus the old .tpl extensions. Nothing inside the templates has really changed and you can most often just change the extension on any older custom templates you are using. There is a line at the start of all the new templates to help secure them that you should, but do not have to, add to all of your existing templates if you are going to convert them. 2 - The Simpilotgroup Plug-In Manager is already installed in the download, I think it is probably one of the better items to be done as far as addons for phpVMS. If you already have modules installed and try to install them again with the PlugIn Manager you will probably lose any data that you had prior. This will not happen if the module was installed with the Plugin Manager. 3 - This is not an official release in any way. I will say that I am using it on all new sites I am building and it has been in the "wild" for a few months in some cases without any real issues. Some of the changes can be found here -> https://github.com/DavidJClark/phpVMS/commits/extended You can find it here -> https://github.com/DavidJClark/phpVMS/tree/extended