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

upgrade to 4.4.2 led to a fatal error #170

Closed
joejenett opened this issue Dec 25, 2022 · 2 comments
Closed

upgrade to 4.4.2 led to a fatal error #170

joejenett opened this issue Dec 25, 2022 · 2 comments

Comments

@joejenett
Copy link

After updating to 4.4.2, I received emails from each of my 2 wordpress installations regarding a fatal error. Following is a copy of the error details and the actions I took to get everything back in order, including upgrading the plugin again.

---copy---
Error Details

An error of type E_COMPILE_ERROR was caused in line 7 of the file /home/joejen5/public_html/dwtp/wp-content/plugins/syndication-links/includes/trait-bridgy-config.php. Error message: Cannot declare trait Bridgy_Config, because the name is already in use
---end copy---

I first restored the plugin to the previous version (from a backup) which enabled my logging in to wp-admin again. Then I deactivated and deleted the Bridgy plugin, and then upgraded Syndication Links to 4.4.2 and everything is working normally again.

Previous upgrades of your plugin never led to any problems.

Hope this helps...

Thanks

@dshanske
Copy link
Owner

Well, there's your answer. You still had the Bridgy plugin installed. It was removed and retired from the repo at least 3 years ago(don't remember the exact date). I moved the syndication code into this plugin. The only other thing it had was a direct registration link to sign up, which I may add here.

Since the other plugin isn't used anymore, I don't think I have a fix for this one.

@dshanske dshanske closed this as not planned Won't fix, can't repro, duplicate, stale Dec 25, 2022
@joejenett
Copy link
Author

joejenett commented Dec 25, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants