File bean_twitter_pull/plugins/bean/TwitterPullBean.class.php is missing, I am not sure what else is. Please check the files uploaded. Thanks

CommentFileSizeAuthor
#4 1397534.4-bean_twitter_pull-class-location.patch485 bytesmrfelton

Comments

bkoether’s picture

bkoether commented
Status: Active » Postponed (maintainer needs more info)

Hi Trent,

not sure what you are referring to. All files needed are in the package. The class TwitterPullBean is defined in plugins/bean/bean_twitter_pull.inc.
I don't get any errors.

bmx269’s picture

bmx269 commented

Plugin twitter_pull of plugin type bean:types points to nonexistent file sites/example.com/modules/bean_twitter_pull/plugins/bean/TwitterPullBean.class.php for class handler handler.

bkoether’s picture

bkoether commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

I think this is an issue with the Bean module, not this one.
Have a look at http://drupal.org/node/1376902

mrfelton’s picture

mrfelton commented
Status: Closed (duplicate) » Needs review
StatusFileSize
new 1397534.4-bean_twitter_pull-class-location.patch485 bytes

This is still an issue. I see these errors repeated on site install using drush site-install. We eed to fix this in the same way that bean did in #1376902: Plugin container of plugin type bean:types points to nonexistent file.

valderama’s picture

valderama commented
Status: Needs review » Reviewed & tested by the community

I can confirm, this issue happens using drush site install.

The patch in #4 helps - as the installation runs smoothly. I'll put it RTBC ...

pcambra’s picture

pcambra
he/him
Primary language Spanish
commented

Just confirming the RTBC and pointing to the source of this problem (documentation in bean) #1973696: Fix bean.api.php to set path and file in the class level

To be strict, the class should bre renamed to BeanTwitterPull.class.php according ctools naming convections.

saltednut’s picture

saltednut
she/her
Primary language English
Location Chicago
commented

Yes, this was a sweeping change made to avoid these problems with beans during site install. All plugins should be updated accordingly.

John Carbone’s picture

John Carbone commented

Had some nasty problems seeming to revolve around this issue as I was getting this in my watchdog logs. Anyway turned out that I had a bad combination of dependencies apparently. Even after updating them I still had issues. Uninstalling/re-installing didn't help either In the end I actually had to revert to an earlier database and re-run my steps with the following module versions, (the patch in #4 wasn't even needed although it could be applied).
Bean 7.x-1.2
Entity 7.x-1.1 (was running 7.x-1.0-rc3)
CTools 7.x-1.3 (was running 7.x-1.3)

Anyway, I'm just sharing in case someone else runs into this same problem and lands on this thread.

mmlabelle’s picture

mmlabelle commented

John, could you share the error you were seeing. The bean just died on my site after an update and I'm trying to troubleshoot.