pikamander2

Solution:

This issue is being caused by a bug in the Starter Templates plugin that has now been fixed.

If your site is stuck in maintenance mode, you can fix that by deleting the “.maintenance” file in your main WordPress directory (probably /public_html)

To update to the fixed version of the plugin:

1. Deactivate the Starter Templates plugin (since it’s breaking the updater)
2. Update the Starter Templates plugin to 3.1.26 or higher
3. Reactivate the Starter Templates plugin

Solution:

This issue is being caused by a bug in the Starter Templates plugin that has now been fixed.

If your site is stuck in maintenance mode, you can fix that by deleting the “.maintenance” file in your main WordPress directory (probably /public_html)

To update to the fixed version of the plugin:

1. Deactivate the Starter Templates plugin (since it’s breaking the updater)
2. Update the Starter Templates plugin to 3.1.26 or higher
3. Reactivate the Starter Templates plugin

Solution:

The issue was being caused by a plugin bug that has now been fixed.

If your site is stuck in maintenance mode, you can fix that by deleting the “.maintenance” file in your main WordPress directory (probably /public_html)

To update to the fixed version:

1. Deactivate the Starter Templates plugin (since it’s breaking the updater)
2. Update the Starter Templates plugin to 3.1.26 or higher
3. Reactivate the Starter Templates plugin

Solution:

The issue was being caused by a plugin bug that has now been fixed.

If your site is stuck in maintenance mode, you can fix that by deleting the “.maintenance” file in your main WordPress directory (probably /public_html)

To update to the fixed version:

1. Deactivate the Starter Templates plugin (since it’s breaking the updater)
2. Update the Starter Templates plugin to 3.1.26 or higher
3. Reactivate the Starter Templates plugin

Solution:

The issue was being caused by a plugin bug that has now been fixed.

If your site is stuck in maintenance mode, you can fix that by deleting the “.maintenance” file in your main WordPress directory (probably /public_html)

To update to the fixed version:

1. Deactivate the Starter Templates plugin (since it’s breaking the updater)
2. Update the Starter Templates plugin to 3.1.26 or higher
3. Reactivate the Starter Templates plugin

@bsfherman – We’re experiencing the same issue when updating from 3.1.25 to 3.1.26.

Same here. The latest plugin update is broken and needs to be patched ASAP.

@dakeg –

Just chiming in to say that we noticed the same issue on our site and are looking forward to a fix.

We’re aware that the deprecation warnings aren’t breaking our site, but they are still flooding our error log and could potentially break the site in a future version of PHP like PHP 9.0.

Aside from that, I’m a bit confused by the mention of backwards compatibility. I’m not super experienced in that area, but a quick test on onlinephp.io seems to suggest that the {$var} syntax works fine in both PHP 8.2.1 and PHP 5.6.0. If that’s the case, I would think that you could just bulk replace the syntax in that file to eliminate the deprecation warnings without causing any backwards compatibility issues.

@ramyos – If you’re able to update your site to PHP 7.4 or 8.0 or 8.1, then that should fix the issue.

Otherwise, you can remove the trailing comma from line 110 of /wp-content/plugins/happy-elementor-addons/extensions/scroll-to-top-kit-settings.php and then avoid updating the plugin until the developer removes it from the next version.

• This reply was modified 2 years, 5 months ago by pikamander2.

The error is being caused by the plugin’s use of trailing argument commas, which aren’t supported by older versions of PHP.

If you update your server to PHP 7.4, 8.0, or 8.1, that should fix it. Although, ideally the developer should also remove the comma(s) for now since they aren’t necessary and too many people are (unfortunately) still running older versions of PHP.

@goldgothe is correct. The error is being caused by the extra comma at the end of the argument list, which is supported by newer PHP versions but not older ones.

Here’s the relevant documentation, I think: https://wiki.php.net/rfc/trailing_comma_in_parameter_list

Reinstalling our wp-includes and wp-admin folder via FTP fixed the error. After that, we were able to navigate to wp-admin and successfully update to version 6.0.

• This reply was modified 2 years, 10 months ago by pikamander2.

Do you have access to your PHP/Apache error log?

We’re getting the exact same error after updating to WordPress 6.0, but only on one of our 10 sites.

The error appears to be in the core itself rather than any themes, so it seems like there might be some kind of issue with the updater.

• This reply was modified 2 years, 10 months ago by pikamander2.

@cristianrossi – Looks like that fixed it.

Thanks for the amazing turnaround time.