Summary
LightStart 2.6.22 can fail when opening its fresh-install wizard on PHP 7.1 or 7.2. The wizard is expected to load on versions covered by the plugin's published PHP requirement, but the affected environment instead reports Parse error: syntax error, unexpected ')' at wizard line 42. This prevents the reported user from completing initial plugin setup.
Customer context
- Product / area: LightStart fresh-install wizard
- Version: 2.6.22
- Environment: Exact WordPress and PHP versions were not provided; the parser message is consistent with PHP 7.1 or 7.2
- Integration / third party: None identified
- Reported error / symptom:
Parse error: syntax error, unexpected ')' in views/wizard.php line 42
- Impact: Initial setup could not be completed; the plugin was deactivated shortly after activation
Reproduction notes
Reported reproduction: activate LightStart 2.6.22 on a fresh installation and encounter Parse error: syntax error, unexpected ')' in views/wizard.php line 42 during initial setup.
Repository-derived reproduction path, not runtime-executed:
- Use LightStart 2.6.22 with PHP 7.1 or 7.2 and WordPress 5.8 or later.
- Activate it where no prior
wpmm_settings option exists.
- Follow the redirect to, or open, the LightStart settings page.
- The fresh-install branch includes
views/wizard.php; parsing is expected to fail at line 42.
Missing details: exact customer PHP version, exact WordPress version, and an independently reproduced runtime trace.
Diagnosis
Conclusion
Release 2.6.22 advertises PHP 7.1 compatibility, but its fresh-install wizard contains trailing commas in function calls, syntax available only from PHP 7.3. The customer-reported unexpected ')' at line 42 precisely matches the closing parenthesis after one such trailing comma. This is direct repository evidence of a compatibility defect for the inspected PHP 7.1-7.2 path; the customer's exact PHP version remains unknown.
Where this likely occurs
- Fresh-install settings wizard:
views/wizard.php — template-level sprintf() call, lines 35-42. Its final argument has a trailing comma immediately before the reported closing parenthesis.
- Additional wizard expressions have the same compatibility surface:
views/wizard.php — template-level sprintf() and wp_kses() calls, lines 90-99 and 118-127.
- Fresh-install state:
includes/classes/wp-maintenance-mode.php — WP_Maintenance_Mode::__construct() lines 34-42 sets wpmm_fresh_install for a new installation on WordPress 5.8 or later.
- Wizard include:
views/settings.php — settings template branch, lines 38-43 includes wizard.php when wpmm_fresh_install is set.
- Settings routing:
includes/classes/wp-maintenance-mode-admin.php — WP_Maintenance_Mode_Admin::add_plugin_menu() lines 350-364 and display_plugin_settings() lines 390-395 route the non-network settings page to views/settings.php.
- Release contract:
readme.txt — plugin metadata header lines 11-12 identifies stable tag 2.6.22 and Requires PHP: 7.1; includes/classes/wp-maintenance-mode.php — WP_Maintenance_Mode::VERSION line 11 identifies version 2.6.22.
- Git history: commit
60fbdc1c279abfe1a375f54161ffbf02bafe7963 introduced the line-42 expression. The commit is contained in tags v2.6.19 through v2.6.22; tag v2.6.22 resolves to 642a8d830bf5e0e807bd87fdb5075682baba51c7.
Engineering notes
The affected template is included conditionally rather than parsed during the initial plugin bootstrap, explaining why activation can proceed before the settings wizard fails. The inspected flow applies to a fresh non-network settings visit on WordPress 5.8 or later. Network-admin behavior and older WordPress paths were not runtime-tested. The repository is the free plugin only; no companion add-on is implicated by the inspected path.
The exact customer PHP version is absent. The parser text strongly suggests PHP 7.1 or 7.2, but that environmental detail is an inference rather than transcript-confirmed fact. The shipped compatibility mismatch exists independently because 2.6.22 declares PHP 7.1 support.
Test coverage status
tests/generic-test.php — Test_Generic::test_class_loading() lines 31-33 checks only core class loading and does not include the settings wizard. No references to wizard, wpmm_fresh_install, or display_plugin_settings were found in the inspected tests. .github/workflows/test-php.yml — phplint and phpunit jobs lines 11-18 and 39-78 configure PHP 7.2, but the nominal lint job invokes composer run lint/PHPCS and the PHPUnit path does not render the wizard. No relevant wizard compatibility coverage was found during inspection.
What to verify or explore next
- Reproduce
php -l views/wizard.php from tag v2.6.22 under PHP 7.1 and PHP 7.2, then compare the PHP 7.3 boundary.
- Exercise a fresh installation on WordPress 5.8 or later under PHP 7.1/7.2 and open the LightStart settings page.
- Confirm the WordPress.org 2.6.22 package contains the same
views/wizard.php bytes as tag v2.6.22.
- Check whether release-package validation exercised all PHP files under the published minimum version.
Unknowns / follow-up
- The reporting site's exact PHP and WordPress versions were not provided.
- No runtime reproduction was performed during this inspection.
- File corruption or local modification was not independently excluded, although the reported line and parser token match the tagged source.
Confidence
Confidence: 98/100
The reported parser message and line match PHP 7.1/7.2-incompatible syntax shipped in the verified 2.6.22 tag, while that release advertises PHP 7.1 support and routes fresh installations through the affected template.
Generated by bug-report-triage (ID: bug-report-triage_6a5f6173bb9229.85672047)
Summary
LightStart 2.6.22 can fail when opening its fresh-install wizard on PHP 7.1 or 7.2. The wizard is expected to load on versions covered by the plugin's published PHP requirement, but the affected environment instead reports
Parse error: syntax error, unexpected ')'at wizard line 42. This prevents the reported user from completing initial plugin setup.Customer context
Parse error: syntax error, unexpected ')'inviews/wizard.phpline 42Reproduction notes
Reported reproduction: activate LightStart 2.6.22 on a fresh installation and encounter
Parse error: syntax error, unexpected ')'inviews/wizard.phpline 42 during initial setup.Repository-derived reproduction path, not runtime-executed:
wpmm_settingsoption exists.views/wizard.php; parsing is expected to fail at line 42.Missing details: exact customer PHP version, exact WordPress version, and an independently reproduced runtime trace.
Diagnosis
Conclusion
Release 2.6.22 advertises PHP 7.1 compatibility, but its fresh-install wizard contains trailing commas in function calls, syntax available only from PHP 7.3. The customer-reported
unexpected ')'at line 42 precisely matches the closing parenthesis after one such trailing comma. This is direct repository evidence of a compatibility defect for the inspected PHP 7.1-7.2 path; the customer's exact PHP version remains unknown.Where this likely occurs
views/wizard.php— template-levelsprintf()call, lines 35-42. Its final argument has a trailing comma immediately before the reported closing parenthesis.views/wizard.php— template-levelsprintf()andwp_kses()calls, lines 90-99 and 118-127.includes/classes/wp-maintenance-mode.php—WP_Maintenance_Mode::__construct()lines 34-42 setswpmm_fresh_installfor a new installation on WordPress 5.8 or later.views/settings.php— settings template branch, lines 38-43 includeswizard.phpwhenwpmm_fresh_installis set.includes/classes/wp-maintenance-mode-admin.php—WP_Maintenance_Mode_Admin::add_plugin_menu()lines 350-364 anddisplay_plugin_settings()lines 390-395 route the non-network settings page toviews/settings.php.readme.txt— plugin metadata header lines 11-12 identifies stable tag 2.6.22 andRequires PHP: 7.1;includes/classes/wp-maintenance-mode.php—WP_Maintenance_Mode::VERSIONline 11 identifies version 2.6.22.60fbdc1c279abfe1a375f54161ffbf02bafe7963introduced the line-42 expression. The commit is contained in tagsv2.6.19throughv2.6.22; tagv2.6.22resolves to642a8d830bf5e0e807bd87fdb5075682baba51c7.Engineering notes
The affected template is included conditionally rather than parsed during the initial plugin bootstrap, explaining why activation can proceed before the settings wizard fails. The inspected flow applies to a fresh non-network settings visit on WordPress 5.8 or later. Network-admin behavior and older WordPress paths were not runtime-tested. The repository is the free plugin only; no companion add-on is implicated by the inspected path.
The exact customer PHP version is absent. The parser text strongly suggests PHP 7.1 or 7.2, but that environmental detail is an inference rather than transcript-confirmed fact. The shipped compatibility mismatch exists independently because 2.6.22 declares PHP 7.1 support.
Test coverage status
tests/generic-test.php—Test_Generic::test_class_loading()lines 31-33 checks only core class loading and does not include the settings wizard. No references towizard,wpmm_fresh_install, ordisplay_plugin_settingswere found in the inspected tests..github/workflows/test-php.yml—phplintandphpunitjobs lines 11-18 and 39-78 configure PHP 7.2, but the nominal lint job invokescomposer run lint/PHPCS and the PHPUnit path does not render the wizard. No relevant wizard compatibility coverage was found during inspection.What to verify or explore next
php -l views/wizard.phpfrom tagv2.6.22under PHP 7.1 and PHP 7.2, then compare the PHP 7.3 boundary.views/wizard.phpbytes as tagv2.6.22.Unknowns / follow-up
Confidence
Confidence: 98/100
The reported parser message and line match PHP 7.1/7.2-incompatible syntax shipped in the verified 2.6.22 tag, while that release advertises PHP 7.1 support and routes fresh installations through the affected template.
Generated by bug-report-triage (ID: bug-report-triage_6a5f6173bb9229.85672047)