Fata Error After updating JM Twitter

Hi, kinda things I hate, very sorry about this, could you try this https://github.com/TweetPressFr/jm-twitter-cards and tell me if that solve your issue ?

EDIT: seems an edge case but I guess your theme is using the same framework, author (Rilwis) reported some bugs with his loading class. I’ll check it

I updated to latest version and it crashed the site twice with 500 Server Errors.

Anyway I can rollback the version?

FYI – the version on github did not fix the issue.

Here are the error codes:

Warning: require_once(/wp-content/plugins/jm-twitter-cards/vendor/autoload.php) [function.require-once]: failed to open stream: No such file or directory in /wp-content/plugins/jm-twitter-cards/jm-twitter-cards.php on line 40

Fatal error: require_once() [function.require]: Failed opening required ‘/wp-content/plugins/jm-twitter-cards/vendor/autoload.php’ (include_path=’.:/php/includes:/usr/share/php’) in /wp-content/plugins/jm-twitter-cards/jm-twitter-cards.php on line 40

@cukeving I’ve done the whole process 6.2 to 7.0.1 by clicking the update button no problem at all.

It did work before the last update. Unfortunate.

It worked fabulously before last update. Hope I can find a fix or rollback.

It doesn’t work and throw me an error after the upgrade:

Fatal error: Cannot redeclare class RW_Meta_Box in /home/efhcmx/public_html/wp/wp-content/themes/ifeature/core/metabox/meta-box-class.php on line 108

I had to erase it from plugins folder.

Please, solve the problem, it was an excellent plugin till now.

Thanks in advance.

Encountering problems since the plugin’s last update. Whenever I save a post the screen returns blank. I think the issue might be related to the new Twitter card preview on the post page.

Very sorry to hear there are such incompatibilities, i’ve worked hard to improve the plugin and it works fine in mot cases but I guess the framework I use is also used by themes and plugins and their implementation might be insecure.

In fact plugins are loaded before themes, if the theme use the class Metabox without checking if it has been loaded before i.e a plugin has already loaded the file then it can trigger errors.

Regarding other errors I’ll check it ASAP.

For now I consider the code is fine but :

FOR THOSE WHO WANT TO ROLLBACK : here is the link download jm-twitter-cards-6.2.1

First I’d like to thank JM for his work on the plugin. I’d also like to add more information about the issues I’m encountering hoping that it might help in finding out the issues.

When the latest version is active, whenever I click the “filter” button to filter posts by category I get a blank screen in return. But if I click a category link under the “Categories” heading I get the page with the posts filtered back.

Whenever I edit a post and click the “Update” button I get a blank page in return. The data is being saved tot he database since if I go back to the page and reload it the submitted info is shown.

It seems that any action that involves a form submission will return a blank page whenever the latest version of the plugin is active. This same issue happens in multisite and single-blog installs as well.

When I downgrade to 6.2.1 all issues are gone.

Once again, thank you JM for the hard work you’ve put into the plugin.

^ I concur and have rolled back to 6.2.1 for now.

Thanks for the efforts with the plugin nonetheless.

I got a 500 error on one of my sites too, turns out it was running an older version of PHP, so make sure you guys check your PHP versions as well before rolling back.

We were getting the require error as well:

Fatal error: require_once() [function.require]: Failed opening required ‘/wp-content/plugins/jm-twitter-cards/vendor/autoload.php’ (include_path=’.:/php/includes:/usr/share/php’) in /wp-content/plugins/jm-twitter-cards/jm-twitter-cards.php on line 40

Issue for us was caused by the vendor/ dir being ignored in the plugin’s .gitignore file.

############
## Composer
############
vendor/
composer.phar

We pull from a git repo as part of our build/deploy process. This was causing the entire vendor directory to get ignored when we pushed the recent plugin update to our own repo.

I removed the line from the ignore file and everything works fine, but I am worried about what will happen the next time the plugin is updated.

@zjustinw while I can understand you may need to read this : Should I commit the dependencies in my vendor directory?