Will have to check my Git repository on the site, and make sure it points to the correct remote repo. It includes the new server environment changes. It appears that the site is back up and running on Local. I was able to successfully clone the broken site and rename it. Select the ‘Admin’ button in the Local UI, and the code for the /wp-admin/index.php file displays in the browser.
When I select the ‘View Site’ button in the Local UI, the code for the site index.php file appears in the browser.
The DB connection to the site files broke. There’s an important project that I was blocked from working on today after updating the site server environment from v1.2 to 1.3.1. As I was preparing to pursue that option, I found the ‘Clone’ site option on the right-click of my touchpad (I use a MacBook Air). Saw good reviews in the forum for packaging a *.sql dump and the /wp-content/ directory into an archive package, and then importing to LBF.
SQL UNAVAILABLE LOCAL BY FLYWHEEL HOW TO
Right now, I don’t know how to troubleshoot this issue any further.Ībout my computer: MacOs 10.13.6 (High I was unpleasantly surprised, and later frustrated about the breaking change introduced to LBF with the version 2.4.0. I would gladly provide you with a LBP log file if could tell me where to generate it from.Ĭan you suggest how to check and reestablish DB connections between my site files and DB? That tells me that the connection to the DB is broken while the site files remain intact and operative. Front to the WordPress Application Admin page, or the login page). When I select either ‘View Site’ or ‘Admin’ from the LBP UI, the actual WordPress PHP file renders in the browser (e.g. I was just prompted, and updated the dev dependencies on a local environment to version 1.3.1. I can login to the Admin page from the front-end. Sites running a local environment version 1.2 (configured to run Apache server, PHP v7.2.0, and MySQL 5.6.34) will launch and render perfectly fine in the browser. Here are some observations that may assist you in troubleshooting the problem. None too happy about it as it’s disrupted my workflow today. The update to v2.4.0 broke my installation of LBF.
0 kommentar(er)
