I’ve successfully deployed on a windows server under IIS, but now going to a hosted unix server on hostgator. I created an add-on domain (xxx) I have the actual domain name pointing to the unix server. I tossed a phpinfo in the folder xxx.com and I can access that perfectly from xxx.com/phpinfo.php. I uploaded all the required project files in xxx.com folder but when I try to run xxx.com/_lib/prod it sits there and looks at me. No error…just…nothing. I took the _lib and the prod and everything in them to 777 permission. Obviously I’m missing something. Help?
When looking at the PHPinfo() what version of PHP do you see?
I assume you upload the ZIP file and extract it on the server.
Wrong.
You have to extract the ZIP file locally and then upload all the files via ftp.
Then your server will set the correct permissions on the files.
Of course, this is then a very time consuming process.
I don’t know why this is happening, but there have been problems with this for years and years.
However, I can’t figure out if it’s related to hosting or just creating a ZIP file in Scriptcase.
I upload the ZIP file and the extract all the time to my server and works every time.
Pointing the browser to to https://xxx.com should automatically direct to _lib/prod to enable the setup and configuration for the database if the configuration has not been done yet.
Nico: 7.4 which is the same as on my development machine and the same as is running on my personal server. I am totally mystified. I’ve redeployed twice, removed and recreated the folder. Not sure what else to do.
Rik: I’ve never done that on the windows server. I load everything to a folder and then extract into the correct location. Can set the 777 permissions on _lib and prod manually. What else does your method change?
Edited to add: Let me ask one more question please. On WINDOWS I install under inetpub and all is good. Here, I have a top level folder of /home3/cmj. Under that is cmj.com along with public_ftp, public_html, etc. When I created the addon domain, it created a folder on the same level as public_html of xxxx.com. I assumed, possibly mistakenly, that the project should unzip into xxx.com. Am I incorrect in thinking this?
Well I finally got it. Apparently there was a weebly site attached to this domain (who knows why) and it completely rewrote the .htaccess file creating havoc. After recreating the entire file structure, it let me connect. Thanks for all your help.
1 Like