Nabeel

Can you try now with the latest tar? You'll need to reinstall, sorry. The accept/reject pireps is related to the airport lookup error, I think I've fixed that one but from what I heard last (before this latest round of fixes), there was a problem. Are you installing in a subfolder?

What topics? There is this v7 category here, there's a few forums in it.

That means that the htaccess file isn't being parsed. There isn't a separate install folder. Who's your host?

Hi all, we should be good to go on shared hosting. Just tested it on Dreamhost. Just upload the files like any old software and just go to the site

There's the test site at http://demo.phpvms.net I need help with installation testing and things of that nature. There's a couple of topics in this forum as @shakamonkey88 has pointed out

Did you try this, and did it work? Now with the latest version, I think I have it working so you can just drop it into a folder and it should all work. Give it a shot. The thing is that it might need some work on the .htaccess file for the URL rewrite stuff. I tried to make it so that it'll work with the "proper" way of pointing a server to the public folder, but if you have to, you can either do the symlink or moving the public folder, or just dropping it in. I had to make a few changes, though, so if you've already got an install, rename the .env file to env.php. I had to override some of the methods in Laravels master bootstrap in order to shift some other directories around, but the main thing was the env file. I still have to fix the installer for a few things. So grab the latest master, upload it to a folder and then try going to it in the browser and see what happens.

Let's talk on discord

Are you on Discord? If you're handy with PHP and pathing, try the instructions here... https://github.com/nabeelio/phpvms/wiki/shared-hosts#copying-the-public-folder-contents If you need to make modifications to those instructions, just post the changes here, or create a new issue on github, and I'll update the wiki.

Fix sqlite3 path on windows view the full commit | http://phpvms.net/downloads/nightly.tar.gz

Run database create for sqlite view the full commit | http://phpvms.net/downloads/nightly.tar.gz

Some more cleanup view the full commit | http://phpvms.net/downloads/nightly.tar.gz

More installer fixes, creation and seeding works view the full commit | http://phpvms.net/downloads/nightly.tar.gz

Some fixes to the installer view the full commit | http://phpvms.net/downloads/nightly.tar.gz

So I was using a 3rd party module for the installer, I decided to scrap it and just write it fresh from scratch. If you download the new nightly tarball, you should be able to just extract it, and then go to /install. Right now, it will create the database files, and then load the default "dev" data. Eventually it'll have the final step of creating the first user and stuff, but for now I just want to get the DB install stuff working. If you have issues, zip up the files in the storage/logs folders and add them to a post so I can take a look. I'm working on a solution for /public as well on shared hosts, so if you want to help test that, let me know as well.

Set some defaults for the cache and queue drivers in the installer view the full commit | http://phpvms.net/downloads/nightly.tar.gz

Rewrite installer without 3rd party installer lib. view the full commit | http://phpvms.net/downloads/nightly.tar.gz

packing fixes view the full commit | http://phpvms.net/downloads/nightly.tar.gz

path fix view the full commit | http://phpvms.net/downloads/nightly.tar.gz

fix method call for time to string view the full commit | http://phpvms.net/downloads/nightly.tar.gz

grr path fixing again view the full commit | http://phpvms.net/downloads/nightly.tar.gz

more archiving fixes view the full commit | http://phpvms.net/downloads/nightly.tar.gz

more fixes to packaging view the full commit | http://phpvms.net/downloads/nightly.tar.gz

I'm trying to find my code for that... but I don't know where the code is. Hmm. What you basically do is: #instead of this: return jsonencode({"some" => "structure"}); # you do: return $_GET["callback"] . '(' . jsonencode({"some" => "structure"}) . ')'; So you're essentially wrapping the JSON that's returned. So if the request is: airports?icao=KJFK&callback=somefn (the browser populates "somefn" with some name, it gets returned as: somefn({JSON});

build tarball in /tmp view the full commit | http://phpvms.net/downloads/nightly.tar.gz

deploy script fixed view the full commit | http://phpvms.net/downloads/nightly.tar.gz