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 when activating feedwordpress #11

Closed
JJ opened this Issue May 4, 2013 · 11 comments

Comments

Projects
None yet
5 participants
@JJ

JJ commented May 4, 2013

I get this error when installing the feed on 3.5.1, latest version 2013.0502

Warning: require_once(/path/to/install/wp-content/plugins/feedwordpress/externals/myphp/myphp.class.php) [function.require-once]: failed to open stream: No such file or directory in /path/to/install/wp-content/plugins/feedwordpress/feedwordpress.php on line 105

It obviously does not activate after that.

@sabas

This comment has been minimized.

Show comment
Hide comment
@sabas

sabas May 4, 2013

Create the directory externals/myphp/ and copy this file https://raw.github.com/radgeek/feedwordpress/e5e9e366dcc1c5bfbd49f046222b5c12c01c477f/myphp.class.php
I solved the error (at least loads the website)

sabas commented May 4, 2013

Create the directory externals/myphp/ and copy this file https://raw.github.com/radgeek/feedwordpress/e5e9e366dcc1c5bfbd49f046222b5c12c01c477f/myphp.class.php
I solved the error (at least loads the website)

@ghelleks

This comment has been minimized.

Show comment
Hide comment
@ghelleks

ghelleks May 4, 2013

Adding either the myphp.class.php file above or just adding an empty file at that location will get you past the require_once() failure, but you'll get stuck again with this:

2013/05/04 17:05:11 [error] 21696#0: *1743925 FastCGI sent in stderr: "PHP message: 
PHP Fatal error:  Call to a member function subscription() on a non-object in /usr/share/nginx/whatever/wp-
content/plugins/feedwordpress/feedwordpresslocalpost.class.php on line 94"

ghelleks commented May 4, 2013

Adding either the myphp.class.php file above or just adding an empty file at that location will get you past the require_once() failure, but you'll get stuck again with this:

2013/05/04 17:05:11 [error] 21696#0: *1743925 FastCGI sent in stderr: "PHP message: 
PHP Fatal error:  Call to a member function subscription() on a non-object in /usr/share/nginx/whatever/wp-
content/plugins/feedwordpress/feedwordpresslocalpost.class.php on line 94"
@radgeek

This comment has been minimized.

Show comment
Hide comment
@radgeek

radgeek May 4, 2013

Owner

@JJ and @sabas
I'm sorry that you ran into this problem. Briefly, the issue is that I tried out git submodules, in order to handle a code module that I re-use across several projects. Unfortunately, git clone (or any installation method closely based on git clone) does not automatically copy the contents of submodules into the cloned directory -- you have to also execute a git submodule init, and then a git submodule update, in order to get all the files your project requires. But git makes no effort to tell you that you need to do these things. In short, it results in problems like the ones you're encountering, without explaining what needs to be done to fix them.

Anyway, I've removed the submodule and rolled all of the code into the main supermodule. If you pull the most recent version of FeedWordPress from github, the fatal error message that you are seeing should go away.

@ghelleks : Thanks for the bug report. I will look into that problem, which looks like a separate issue.

Owner

radgeek commented May 4, 2013

@JJ and @sabas
I'm sorry that you ran into this problem. Briefly, the issue is that I tried out git submodules, in order to handle a code module that I re-use across several projects. Unfortunately, git clone (or any installation method closely based on git clone) does not automatically copy the contents of submodules into the cloned directory -- you have to also execute a git submodule init, and then a git submodule update, in order to get all the files your project requires. But git makes no effort to tell you that you need to do these things. In short, it results in problems like the ones you're encountering, without explaining what needs to be done to fix them.

Anyway, I've removed the submodule and rolled all of the code into the main supermodule. If you pull the most recent version of FeedWordPress from github, the fatal error message that you are seeing should go away.

@ghelleks : Thanks for the bug report. I will look into that problem, which looks like a separate issue.

@JJ

This comment has been minimized.

Show comment
Hide comment
@JJ

JJ May 4, 2013

No problem. Git is great, but it's hell sometimes when documentation is not clear enough. Will try this, thanks for the support.

JJ commented May 4, 2013

No problem. Git is great, but it's hell sometimes when documentation is not clear enough. Will try this, thanks for the support.

@sabas

This comment has been minimized.

Show comment
Hide comment
@sabas

sabas May 4, 2013

@radgeek thanks ! I saw also some people commenting about the error on the plugin wordpress forum, don't know if you've replied also to them..

sabas commented May 4, 2013

@radgeek thanks ! I saw also some people commenting about the error on the plugin wordpress forum, don't know if you've replied also to them..

@ghelleks

This comment has been minimized.

Show comment
Hide comment
@ghelleks

ghelleks May 4, 2013

@radgeek Good to know, please let me know if you need any diagnostic information.

ghelleks commented May 4, 2013

@radgeek Good to know, please let me know if you need any diagnostic information.

@radgeek

This comment has been minimized.

Show comment
Hide comment
@radgeek

radgeek May 4, 2013

Owner

@ghelleks : It looks like the problem you were encountering was an issue related to PHP 5.4's new behavior with the global variable namespace and the $GLOBALS array. I just pushed some updates to Github (v. 2013.0504) which should, hopefully, systematically go through and fix the compatibility issue that was producing the fatal error message you saw. If you want to take a look, and let me know whether it fixes your issue, I'd be much obliged.

Cheers,
-C

Owner

radgeek commented May 4, 2013

@ghelleks : It looks like the problem you were encountering was an issue related to PHP 5.4's new behavior with the global variable namespace and the $GLOBALS array. I just pushed some updates to Github (v. 2013.0504) which should, hopefully, systematically go through and fix the compatibility issue that was producing the fatal error message you saw. If you want to take a look, and let me know whether it fixes your issue, I'd be much obliged.

Cheers,
-C

@ghelleks

This comment has been minimized.

Show comment
Hide comment
@ghelleks

ghelleks May 4, 2013

@radgeek, would that it did. I'm running 5.3.3, and still receiving the same error after a fresh pull.

ghelleks commented May 4, 2013

@radgeek, would that it did. I'm running 5.3.3, and still receiving the same error after a fresh pull.

@tekaymedia

This comment has been minimized.

Show comment
Hide comment
@tekaymedia

tekaymedia Dec 12, 2016

@radgeek I'm experiencing the same problem. I guess with your latest update. It broke my WP website and I had to manually deactivate the plugin. When I want to activate it again I get the error message on the plugins page.

tekaymedia commented Dec 12, 2016

@radgeek I'm experiencing the same problem. I guess with your latest update. It broke my WP website and I had to manually deactivate the plugin. When I want to activate it again I get the error message on the plugins page.

@radgeek

This comment has been minimized.

Show comment
Hide comment
@radgeek

radgeek Dec 13, 2016

Owner

@tekaymedia Just to be clear, the problem you got is that you got a fatal PHP error after updating the plugin to version 2016.1211 (the version released a couple days ago)?

If you are using FWP with a WordPress version < 4.7, then you should be able to fix the problem by updating to the latest release of FWP, 2016.1213, which I just pushed to Github and to the WordPress plugins repository, which should restore backwards compatibility with versions of WordPress < 4.7. Take a look and let me know if it solves your problem. If so, great; and I'm sorry for the trouble with the last update. If not, let me know in more detail what you're seeing when you try to activate the new version, and I'll do what I can to troubleshoot.

Owner

radgeek commented Dec 13, 2016

@tekaymedia Just to be clear, the problem you got is that you got a fatal PHP error after updating the plugin to version 2016.1211 (the version released a couple days ago)?

If you are using FWP with a WordPress version < 4.7, then you should be able to fix the problem by updating to the latest release of FWP, 2016.1213, which I just pushed to Github and to the WordPress plugins repository, which should restore backwards compatibility with versions of WordPress < 4.7. Take a look and let me know if it solves your problem. If so, great; and I'm sorry for the trouble with the last update. If not, let me know in more detail what you're seeing when you try to activate the new version, and I'll do what I can to troubleshoot.

@tekaymedia

This comment has been minimized.

Show comment
Hide comment
@tekaymedia

tekaymedia Dec 13, 2016

tekaymedia commented Dec 13, 2016

@radgeek radgeek closed this Dec 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment