-
Notifications
You must be signed in to change notification settings - Fork 2
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: Cannot redeclare scb_init() #80
Comments
@Vernal in the case of wp-pagenavi, it appears that activating Replyable before PageNavi is a workaround in that particular case. |
Thanks boss.
…On Jan 11, 2017, 4:48 PM -0500, Dylan Kuhn ***@***.***>, wrote:
@Vernal in the case of wp-pagenavi, it appears that activating Replyable before PageNavi is a workaround in that particular case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I'm experiencing the same issue using a plugin that makes use of the posts-to-posts plugin. I noted that in the ticket reported here: scribu/wp-scb-framework#50 My error is:
|
@misfist did you try deactivating both plugins, then activating replyable before posts-to-posts? |
@misfist As an experiment I forked wp-scb-framework and tried having Composer use the standard loader. Give the following build a try if you like: |
@cyberhobo - Thanks for this! I'll check it out and report back. |
@cyberhobo that zip file shared works, the fatal error prevent activation. Thanks! |
Thanks @danaskallman - I actually forgot to close this issue, the "loading voodoo" should be included in the current releases also, please let me know if they do not. |
@cyberhobo I just tried version 2.2.1 and I am getting the fatal error. posts-to-posts in installed as it's own plugin in the instance I would use this alongside it. |
Thanks for letting me know - I'll reopen this and target our next release. Meanwhile it should be okay to use the zip that works. |
Sounds good, I'll follow updates. Thanks! |
just to add, other plugins such as BadgeOS also affected by this issue. |
Observed when running with wp-pagenavi:
The text was updated successfully, but these errors were encountered: