Once a problem is found, BAE can directly use the $ _ FILES variable. Therefore, the project that moves the value to the BAE actually only needs to change the database configuration. Under normal circumstances, because there is no way to use install. php (mainly because most of the installation files do not allow you to input constants in the form, but only one string ). OK
Once a problem is found, BAE can directly use the $ _ FILES variable. Therefore, the project that moves the value to the BAE actually only needs to change the database configuration. Under normal circumstances, because there is no way to use install. php (mainly because most of the installation files do not allow you to input constants in the form, but only one string ). OK
Once a problem is found, BAE can directly use the $ _ FILES variable. Therefore, the project that moves the value to the BAE actually only needs to change the database configuration. Under normal circumstances, because there is no way to use install. php (mainly because most of the installation files do not allow you to input constants in the form, but only one string ).
OK. Download the original typecho and install it locally. Modify the database configuration in config. inc. php. Change to online Configuration
At the same time, export your mysql and execute it in phpmyadmin.
The whole world is much quieter.
If you think that I am too simple, or do not want to install it locally, you can refer to this ..... Otherwise, you will find that you cannot log on.
---
Another serious problem with BAE is that the $ _ files I mentioned earlier can be directly used, and FILES can be directly uploaded to the project directory, however, this part of the code is not controlled. Very troublesome.
Typecho can also modify template files online, that is, these modified files are not in the scope of code control...
--- Sometimes I don't know what BAE is, is it just a virtual space? Maybe I can't feel it ..
Original article address: Port typecho to bae. Thank you for sharing it.