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

"Fatal Error" occurred when adding the Social extension #301

Closed
zane-ng opened this issue Mar 3, 2015 · 4 comments
Closed

"Fatal Error" occurred when adding the Social extension #301

zane-ng opened this issue Mar 3, 2015 · 4 comments
Assignees

Comments

@zane-ng
Copy link

zane-ng commented Mar 3, 2015

I was trying to add the Social extension in Unyson, and suddenly the WP website went down by showing the following line:

"Fatal error: Cannot redeclare class OAuthSignatureMethod_HMAC_SHA1 in /home/content/p3pnexwpnas05_data03/81/2365281/html/wp-content/plugins/unyson/framework/extensions/social/extensions/social-twitter/includes/OAuth.php on line 125"

My site is hosted by Godaddy and now I'm not able to manage it (say, entering the dashboard page) with the above error. I don't know if it is because the extension conflicts with some other plugins.

It seems the only way to "solve" the problem is removing the old one and build a new one. However I don't have a backup so if anyone knows other way please tell me.

@ghost
Copy link

ghost commented Mar 3, 2015

@zaneyu Delete /home/content/p3pnexwpnas05_data03/81/2365281/html/wp-content/plugins/unyson/framework/extensions/social directory.


@valeriuzdrobau I think in social/extensions/social-twitter/includes/OAuth.php you should check if class already exists (maybe it was included by other plugin)

if (!class_exists('OAuthSignatureMethod_HMAC_SHA1')):

class OAuthSignatureMethod_HMAC_SHA1 {
    ...
}

endif;

@ghost ghost assigned valeriuzdrobau Mar 3, 2015
@zane-ng
Copy link
Author

zane-ng commented Mar 4, 2015

@moldcraft Thanks a lot! :)

valeriuzdrobau added a commit to ThemeFuse/Unyson-Social-Extension that referenced this issue Mar 5, 2015
@valeriuzdrobau
Copy link
Contributor

I corrected here, the problem will disappear in the next version.

@valeriuzdrobau
Copy link
Contributor

Fixed in v1.0.4

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