Jump to content

Nabeel

Administrators
  • Posts

    8147
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by Nabeel

  1. I will be offering VA hosting shortly, along with nav-data updates with the upcoming 2.1 release. Pricing hasn't been decided yet, but the web-hosting will be completely certified to run with phpVMS, including support for the new phpVMS maintenance cron files, FTP support, and any other pieces which are required for phpVMS to work - including command line access, and access to tools such as mysql and git on the command line. It will include scripts to install phpVMS directly from the command line, using git (which the move to was just completed). I don't have a timeline yet, but it will be sometime soon, I'm in the process of setting things up. Navdata updates will also be provided for 2.1 - at a monthly, or yearly rate. These will contain the latest AIRAC updates, which are compatible with whatever route software you're using.
  2. Yeah, it's just the header.tpl/footer.tpl squashed into one file.
  3. I've implemented an additional layout format for 2.1, called 'layout.tpl'. When this file is in a skin's folder, it will use that, instead of the header.tpl and footer.tpl files. It'll look like this: <html> <head> <title><?php echo $page_title ?></title> <?php echo $page_htmlhead; ?> </head> <body> <?php $page_htmlreq; ?> <div id="container"> <div id="content"> <?php echo $page_content; ?> </div> </div> </body> </html> As you can see, this is the entire HTML page, with: <?php echo $page_content;?> Placed where the content will show up, and the normal additions to the template. The default skin has been changed to this. But it might help some people with skinning, since it's a bit easier to visualize how it comes together. The old method (header.tpl/footer.tpl) will still work, but if it sees the 'layout.tpl' file, it will use that. Any other ideas?
  4. Hi Imran, Good to see you guys are considering phpvms. I joined a while ago, but never got the time to fly much. But, I would go with what Tom said, doesn't seem like everything uploaded properly
  5. Can you pastebin: /core/classes/CodonWebService.class.php I wonder why it tagged that as different. Maybe I forgot the generate hash, weird. Git a bit more flexible than SVN. I just don't like how it does hashs, etc. I might still switch to bitbucket, which is then another switch.. lol. But we'll see. I want to move away from SVN, my local repository is getting huge and slow
  6. Nabeel

    Help

    It's in admin/templates/, I think email_pilotaccepted. It's going to be moved in the next release.
  7. Well, CLI is different. You have to make sure it's configured correctly to host on localhost or wherever your server is supposed to be setup. But in short, MySQL isn't setup correctly
  8. codonwebservice fix, returned data on post View more details, download from here
  9. There's on SITE_ROOT, that's figured out automatically. The error you posted above - seems as though it can't connect to the database. Make sure those settings are correct
  10. vacentral related front-end fix View more details, download from here This doesn't affect any vaCentral functionality, but fixes a bug where the response was coming as "API server didn't respond". Your stuff is still sent, though
  11. Try an export now. I just pushed a new update to the API server. Thanks joeri for letting me borrow your server. Next commit will have a few fixes to. Also, before you export, clear the phpvms_updates table. It could still be a problem with the betas which then I have to dig a bit deeper, which I think I'll do anyway tomorrow. Seems like any VAs on release are working. BTW Joeri, all your PIREPs were in the database, so it was all updates. But I'll poke around a bit more. I think there's something funky going on somewhere, which all the shuffling around that's been going on
  12. Make sure the paths are correct in local.config.php
  13. fixed #213, changed to layout.tpl format View more details, download from here Notes New format for skins: http://forum.phpvms.....html?record=20 Scroll down to bottom ('layout.ctp'). The old method still works, but if there is a layout.ctp present, it will use that format.
  14. fixed mysqli issues View more details, download from here
  15. moved versions into file, out of db View more details, download from here
  16. Moved versioning outside of DB View more details, download from here
  17. Moved versioning outside of DB View more details, download from here
  18. Moved versioning outside of DB View more details, download from here
  19. Click the docs link in my sig, go all the way to the bottom
  20. push test View more details, download from here
  21. Push test View more details, download from here
  22. SVN push test View more details, download from here
×
×
  • Create New...