#35343 closed defect (bug) (invalid)
DesktopServer reports a PHP parsing error in wp-admin/install.php with WP v4.4.1
Reported by: | yogaman5020 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.4 |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
In wp-admin/install.php
, line 171, there's a right-hand curly brace inside a set of PHP tags that the PHP compiler can't parse [<?php } ?>
]. This line of code appears in both WP v. 4.4 and 4.4.1. By comparison, the code is not present in v. 4.3.1. [I think it was added when strong passwords were enforced with v. 4.4.] In my local dev environment, DesktopServer keeps throwing a parsing error when spinning up a site with v. 4.4 or 4.4.1. Wanted to bring to your attention. My solution at this point is to spin up and install a local site with WP v. 4.3.1., then upgrade to v. 4.4.1 once the site is up and running.
Attachments (1)
Change History (4)
#1
@
8 years ago
Just wanted to add that the local PHP parsing error stops the installation process dead in its tracks. That's why I'm reverting back to v. 4.3.1 to install locally, then upgrade once WP is installed.
#2
follow-up:
↓ 3
@
8 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
That looks like a corrupted file, There's multiple lines missing at line 169.
If that's how the file comes included with DesktopServer,either they're doing something really bad or they've got a corrupted package. You should report that to them.
#3
in reply to:
↑ 2
@
8 years ago
Replying to dd32:
You're absolutely right about the missing code at line 169. I put some fresh installs of WP 4.4. and 4.4.1 in my DTS app, and got the same result (failure to install). I'll let the folks at ServerPress know.
That looks like a corrupted file, There's multiple lines missing at line 169.
If that's how the file comes included with DesktopServer,either they're doing something really bad or they've got a corrupted package. You should report that to them.
line 171, wp-admin/install.php; possible error in code?