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

Enabling Plug-ins - The addon could not be enabled because it generated a fatal error: #1561

Closed
bbsforum opened this issue Apr 4, 2013 · 22 comments

Comments

Projects
None yet
10 participants
@bbsforum
Copy link

commented Apr 4, 2013

This just started since upgrading today to 2.1b1. Now the strange thing is after this error happens. If I still go back and click Enable a second time the plug-in will be enabled and work just fine. But no matter what plug-in I try this with (old, new, whatever) I am getting this error. I've literally gone down the line of plug-ins and it happens every time.

It shows a distorted look of the site (including messing up the sidebar of vanilla, screenshots attached) and scrolling down the page it says:

Page Not Found

The page you were looking for could not be found.

Here are the screenshots. This is what I have to scroll past to get to the list of plug-ins and then when I enable that second time, it works.

bbsforum-plugin1

bbsforum-plugin2

@bbsforum

This comment has been minimized.

Copy link
Author

commented Apr 4, 2013

Things I've tried so far:

Config file, rewrites to FALSE: Made no difference
Cleared .ini files from cache: Made no difference
Config file permissions: Tried them all, made no difference.

I'll keep updating as I try more things to figure it out, any help or ideas always appreciated.

@tburry

This comment has been minimized.

Copy link
Member

commented Apr 4, 2013

Can you try disabling your theme and then try enabling a plugin?

@bbsforum

This comment has been minimized.

Copy link
Author

commented Apr 4, 2013

Funny. I get the error while going to change from Bittersweet to Baseline!

So I applied the theme twice, went to plug-ins. Same thing.

@tburry

This comment has been minimized.

Copy link
Member

commented Apr 4, 2013

Okay. I'm going to say that I know that the plugin enabling code is very old-school and needs to be made more bullet-proof. I think basically if you have one piece of extraneous text somewhere then any plugin screws up.

You've given me the motivation to go through this for beta 2 fwiw!

@bbsforum

This comment has been minimized.

Copy link
Author

commented Apr 4, 2013

At least it still works! :)

I'm going to keep digging here, and if something comes up I'll be sure to post..

@tburry

This comment has been minimized.

Copy link
Member

commented Apr 4, 2013

If you have the firebug or chrome developer tools it would help if you can
grab the network information. See if there are any non http 200 responses.

On Thu, Apr 4, 2013 at 11:18 AM, bbsforum notifications@github.com wrote:

At least it still works! :)

I'm going to keep digging here, and if something comes up I'll be sure to
post..


Reply to this email directly or view it on GitHubhttps://github.com//issues/1561#issuecomment-15903583
.

@bbsforum

This comment has been minimized.

Copy link
Author

commented Apr 4, 2013

Mac guy here so it's all Safari for me. But let me grab a PC laptop I have tonight and jump on it and get the info for ya.

@hgtonight

This comment has been minimized.

Copy link
Contributor

commented Apr 4, 2013

You should be able to use the webkit inspector tools on safari.

@pixelnated

This comment has been minimized.

Copy link

commented Apr 4, 2013

I am experiencing the same issue here but not on my localhost (wamp) install but on the server (linux host vps)
now here is an interesting catch.
On the server where it fails
I can disable a plugin but I can't enable it. The plugin appears to be updating the config file but not fully.
For example
The Stop Forum Spam plugin will add the line to the Plugins section just fine:
- $Configuration['Plugins']['StopForumSpam']['UserID'] = 'xxxxx';

But it does not or can't add the line to the enabledplugins section. I can manually add this and the plugin works just fine:
$Configuration['EnabledPlugins']['StopForumSpam'] = TRUE;

Hope that helps you trace where the issue is. I have manually enabled a couple that failed in the settings page so I think it has something to do with not being able to find the right spot in the config.php

A core plugin that worked the same way for me is VanillaInThisDiscussion

Still can't figure out why it worked locally though.

@pixelnated

This comment has been minimized.

Copy link

commented Apr 5, 2013

tested again and still can't explain why but this is still working just fine on my local test environment (WAMP) but can't add the enabledplugins section and fails on my LAMP setup. It seems that is the only section in the config file that it can't update and only in the LAMP install. so strange.
If I add those lines to the enabled plugins section manually (the other sections where needed get added) the plugins work just fine.

@hgtonight

This comment has been minimized.

Copy link
Contributor

commented Apr 9, 2013

I was able to reproduce your issue. I was also able to get rid of the error by commenting out line 895 in class.settings.controller

//header(self::GetStatusMessage(200), TRUE, 200);

@bbsforum

This comment has been minimized.

Copy link
Author

commented Apr 10, 2013

@hgtonight that worked for me. works flawless now.

Jeremiah, it was in applications/dashboard/controllers

@hgtonight

This comment has been minimized.

Copy link
Contributor

commented Apr 10, 2013

@tburry I forgot to mention that I was getting a 404 error on /dashboard/settings/testaddon/Plugin/embedvanilla/8AAOQ40DQTXV?DeliveryType=JSON

@pixelnated

This comment has been minimized.

Copy link

commented Apr 10, 2013

Thanks @hgtonight & @bbsforum Worked for me too!

@tburry

This comment has been minimized.

Copy link
Member

commented Apr 15, 2013

I kind of don't want to comment out that line. There are other errors that can occur. @pixelnated can you send me a zip of your plugins and themes folders for me to do some testing? todd@vanillaforums.com

@jasonlor

This comment has been minimized.

Copy link

commented Jun 1, 2013

Works for me too after commenting that line out.

@aery

This comment has been minimized.

Copy link

commented Jun 6, 2013

Did you guys used Vanilla Porter to migrate from 2.0 to 2.1B or using LAMP?

Because I am getting same error on exporting-importing through Vanilla Ported on LAMP but things work fine with fresh local WAMP install.

@cardassian-tailor

This comment has been minimized.

Copy link

commented Jun 19, 2013

I am also experiencing this same issue

@cardassian-tailor

This comment has been minimized.

Copy link

commented Jun 19, 2013

should i comment out the line?

@elwizard

This comment has been minimized.

Copy link

commented Jun 20, 2013

That worked for me too! Thanks.

@bleistivt

This comment has been minimized.

Copy link
Contributor

commented Feb 21, 2015

The commit log suggests, that this was fixed in master, too (and still is)

@linc

This comment has been minimized.

Copy link
Member

commented Feb 21, 2015

Thanks!

@linc linc closed this Feb 21, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.