Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error after updating to master (f40ed56): syntax error in lib/Configuration.php line 24 #2996

Closed
quickwick opened this issue Sep 4, 2022 · 3 comments
Labels
Bug-Report Confirmed bug report

Comments

@quickwick
Copy link
Contributor

Describe the bug
rss-bridge main page is throwing an error after updating to master

After updating to master f40ed56 just now, my rss-bridge is now generating this error:

Something went wrong

Uncaught Exception ParseError: syntax error, unexpected 'array' (T_ARRAY), expecting function (T_FUNCTION) or const (T_CONST) at lib/Configuration.php line 24

Stacktrace

#0 index.php:7
#1 lib/RssBridge.php:15
#2 lib/RssBridge.php:35
#3 :(no line)
#4 lib/Configuration.php:24

I don't have the energy to chase this down right now (getting a migraine), just reporting it so that hopefully someone can figure this out and fix it. Assuming it's not just something wonky on my end.

@quickwick quickwick added the Bug-Report Confirmed bug report label Sep 4, 2022
@dvikan
Copy link
Contributor

dvikan commented Sep 4, 2022

It's because your machine is running lower than php 7.4 which is the minimum supported version.

You can do git checkout 9503f9ad7fe84a5fca63d9dbb3005d640ddb7a0b to checkout the latest version that supports php 7.3.

#2838

@quickwick
Copy link
Contributor Author

Thank you @dvikan . I've installed php7.4 and rss-bridge is back to working.

Would it be possible to add a php version check and print an error message about having the wrong php version, rather than the current unclear error?

@dvikan
Copy link
Contributor

dvikan commented Sep 4, 2022

We already have that. But due to a bug, the code that checks the php version used a php7.4 feature. Fixed in #2999

@dvikan dvikan closed this as completed Sep 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug-Report Confirmed bug report
Projects
None yet
Development

No branches or pull requests

2 participants