|
lefty 3/9/2017 |
|
I have two PHPR applications that have been corrupted, I assume by an attack. The apps essentially do the same thing for two different clients. The app is supposed to store client documents like board of directors meeting agendas and minutes, etc. The problem happens when I try to create a new record and upload the file. The "Save" function never completes and a message displays saying that no file was attached. Additionally, the app is essentially locked after that and I have to restart. However, I have noticed if I run PHPR, build the app and then execute from "View in Browser" I can upload and save documents without a problem. My question is what is the difference in the executing environment between "View in Browser" and the live production environment. I have tried uploading the app brand new, even deleting the existing app files before uploading. I have also used the admin fuction to view the SQL data base but do not find anything wrong. I have to believe that a sever based environment file has been corrupted that is not used when the app is executed from "View in Browser". Any ideas would be greatly appreciated.
|
|
|
|
lefty 3/9/2017 |
|
give read/write permissions to files folder/directory where uploads are stored. either outside root or inside ../files . If you delete the output on the server and then re-build then you have to assign permissions each time. If just updateing same output , settings should be okay. |
|
|
HJB 3/9/2017 |
|
I understand that the two apps had been working fine until a sudden day both did not work any longer. Further I understand you are first developing the apps under LOCALHOST to then upload the final version to the live server then. In the course of constant of live server upgrades and configuration changes, it could happen that what you run locally and what is live elsewhere are differing. So, I personally do NOT develop apps under LOCALHOST at all since years now, but am using the PHPR connection script to base on the live server configuration right from the beginning. This way ensures that once PHPR has a remote connect to the live server, the generated code would definitely run fine on the live server as well. At no time (over years) I needed to run permissions on file folders at all, even not when using the DOMPDF issue. Say, I connect via PHP connection script and upload the generated code then, that's all. It runs and runs and runs (like famous VW's beetle) right from the beginning without ANY further manual intervention at all. I use a "test subdirectory" on the live server to get things to final stage then, using Filezilla to then copy the final app to the wished directory. It seems to me you should give the connection script method a try as third party driven live server operators are changing configurations at will, hence the problem at your end, looking like an attack, but it's not. It seems to me it's more likely a sudden configuration change on the live server. |
|