I hope I have chosen the right issue tag.
I have tried two ways to enable oa_moderation, one through apps, one by applying the patch myself and enabling it from the module page but both times I am getting the following error:
[16-Feb-2015 02:42:20 America/New_York] PHP Fatal error: Class 'WorkbenchModerationProfileController' not found in /home/dater/public_html/atrium/includes/common.inc on line 7914
I would appreciate it if you can tell me why?
I don't know if I have missed something or is something else. I have read the module pages both for oa_workbench and workbench_moderation_profile and applied the patch. Although the one patch that is indicated on workbench_moderation_profile page does not apply at all.

Comments

mpotter’s picture

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

I'm not sure what you mean by "the patch". What patch are you referring to. If you look in the oa_moderation make file, there are FOUR patches needed to workbench_moderation plus the specific dev version of workbench_moderation_profiles.

You really need to install this via Apps. That is the only method we currently support. The app is working fine for us here on a fresh OA 2.30 install.

sophiejones’s picture

sophiejones CreditAttribution: sophiejones commented

Hello
I did try to install it through apps. But I got the error that I posted. This is why I read documentation and tried to do it manually on yet another fresh install of openatrium. The patch I was referring was the one posted on oa_workbench page (and now I see it is indicated in this make file as well.)
It doesn't matter which way I try to enable it, I still get the same error as I posted above.
I tried once more with fresh installation and apps. the result is the same, i do get the error and I read the make-file and the versions are correct. You mentioned specific dev version of workbench_moderation_profiles and the app installs 1.0-alpha1
Since 2.30 works there for you, then it must be something wrong with my installations of same version of openatrium but there is nothing in log messages, nothing while i was installing it. I successfully installed the other apps I needed.
Just to report unusual behavior when using apps (In case has significance). There is one thing you need to know; when I installed mailhandler through apps, it installed a higher version without enabling it, and then in status report showed some token for user to be changed which I did, and then I was able to go back to apps and enable it. I did not install this higher version manually, it was done through apps which left mailhandler disabled but installed. After I fixed the token for user, I was able to go back to apps and enable it.

mpotter’s picture

mpotter CreditAttribution: mpotter commented

What's important to understand is that Apps are not modules. What we have done with the External Apps is bundle together a set of modules and patches into a tar.gz download that is hosted on drupal.org via a URL given by the app server.

The "version" of an App can be different than the version of any specific module in it. For example, the Open Atrium Workflow App contains "oa_workbench", "workbench_moderation", "workbench_moderation_profiles", and patches. So the Version of the App isn't the same as any specific module.

When an App is re-packaged to include a new patch, the version of the App is incremented so that it is available on the Apps page as an upgrade. That's what happened with MailHandler. The App version changed.

If any module within an App has external dependencies or config, like the token you mentioned, Drupal won't allow it to be enabled until the issue is resolved. Also, you might have multiple modules that need to be enabled if that happens with something like the Workflow.

If you have other questions or problems with Apps, please post them to the Apps issue queue.

sophiejones’s picture

sophiejones CreditAttribution: sophiejones commented

Thank you
I don't think the issue is app problem anyway. But I just have to wait for the new version I heard will be coming this week.
I just cannot enable the oa_workbench because of this controller issue in common.inc as it stands. There is a developer who is doing some work for me, Maybe he can help me out to figure out why I am getting this error.
I appreciate your quick respond.

mpotter’s picture

mpotter CreditAttribution: mpotter commented

Did you be sure to delete any previous version of the code before re-downloading the app? If you look at the manifest from the App server here: http://appserver.openatrium.com/app/query/openatrium-development you can see the exact files that are downloaded for Open Atrium Workflow that have the patches pre-applied. Maybe that will help get the correct code.

sophiejones’s picture

sophiejones CreditAttribution: sophiejones commented

Hello
I had opened an issue in workbench_moderation_profile to see if they can shed some light for me on this controller. they said that the module requires workbench_moderation 1.4 version
Apparently workbench_moderation_portfolio 1.0-alpha1 requires workbench_moderation 1.4 version
But apps downloads workbench_moderation 1.3+10-dev version.
Would it be okay not to use apps for this particular module and instead I manually add this 1.4 version, apply the patch that is mentioned and then enable it?

mpotter’s picture

mpotter CreditAttribution: mpotter commented

We will need to investigate this. It certainly looks like there was a lot of changes to workbench_moderation recently and we haven't tested the 1.4 version. You can certainly give it a try and report what you learn.

sophiejones’s picture

sophiejones CreditAttribution: sophiejones commented

Hello
No, I tried doing this manually and it didn't work.
The problem is according to maintainer of workbench_moderation_profile the version that is used and installed by apps will not work with the workbench_moderation version that is installed by apps since this workbench_moderation_profile only works with workbench_moderation 1.4
I can only tell you the buck stops at workbench_moderation_profile. I cannot enable this module even if I manually install and enable workbench_moderation v1.4
In workbench_moderation_profile page, there is instruction to apply a specific patch to workbench_moderation. Well, patch didn't apply and when I investigated further, it seems on this new 1.4 version this patch has already been committed and applied.
So for the life of me, I cannot figure out why. It is not like i went straight on enabling oa_workbench. I decided to do this module by module so I can figure out where the problem is.
Workbench and workbench_moderation get enabled without any problem. then I attempted to enable workbench_moderation_profile and I got the same php fatal error.

mpotter’s picture

mpotter CreditAttribution: mpotter commented

As I said, I'll need to look into this. At the time the latest oa_workbench App was built back in Nov/Dec it all worked. Last time I tried installing it it worked. I have it running on a client site. So will need to look into what changed in 1.4 and why even using the app of 1.3 doesn't work. The problem is you've got 2 different module maintainers between workbench_moderation and workbench_moderation_profiles and looks like there is confusion there.

sophiejones’s picture

sophiejones CreditAttribution: sophiejones commented

hello
Thank you for getting back to me and you are right, there seem to be some confusion there. I read you are giving out a new version due to views security update and am hoping this is also resolved on that version.

mpotter’s picture

mpotter CreditAttribution: mpotter commented

The 2.31 version of OA2 due out this week doesn't update oa_workbench. That is a separate external App and isn't part of core OA. oa_workbench will get it's own App update when we've had a chance to look at this. But it's not going to be this week, sorry.

candelas’s picture

candelas CreditAttribution: candelas commented

I am having the same error when trying to enable oa_workbench. My steps
drush dl oa_workbench --yes
drush apps-install oa_workbench --yes

The installation gets this error

Error: Class 'WorkbenchModerationProfileController' not found in
/xxx/includes/common.inc, line 7914
candelas’s picture

candelas CreditAttribution: candelas commented

@mpotter which other info do you need? I really would like to be able to use this feature. Thanks

Wiskane’s picture

Wiskane CreditAttribution: Wiskane commented
Component: Code » Workbench App
Category: Support request » Bug report
Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Active

I met the same error("Error: Class 'WorkbenchModerationProfileController' not found in /xxx/includes/common.inc") when enabled the "Open Atrium Workbench App".

Håvard’s picture

Håvard CreditAttribution: Håvard commented

Same error over here when enabling the OA Workbench app.

Fatal error: Class 'WorkbenchModerationProfileController' not found in /xxx/includes/common.inc on line 7931

serenecloud’s picture

serenecloud CreditAttribution: serenecloud commented

Same issue here with OA2 running on Pantheon:

Fatal error: Class 'WorkbenchModerationProfileController' not found in /srv/bindings/7ca666a1935d411d8a5b7a4e389f5ce6/code/includes/common.inc on line 7931

I had to empty out workbench_moderation_profile.module so I could use drush to disable the module.

elibibbio’s picture

elibibbio CreditAttribution: elibibbio commented

Hi, same issue on a clean installation after installing oa_workbench via apps:

[error] PHP Fatal error: Class 'WorkbenchModerationProfileController' not found in /var/www/openatrium-7.x-2.31/includes/common.inc on line 7914, referer: http://openatrium.mysite.com/?q=batch&op=start&id=19

Need to manually delete module's files on fs to restore.

hefox’s picture

hefox CreditAttribution: hefox commented
Status: Active » Postponed
Related issues: +#2427615: Conflict with core patch OpenAtrium is running, causes fatal error
hefox’s picture

hefox CreditAttribution: hefox commented
Version: 7.x-2.30 » 7.x-2.x-dev
Status: Postponed » Fixed

Patch added

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

mpotter’s picture

mpotter CreditAttribution: mpotter at Phase2 commented

See #2427615: Conflict with core patch OpenAtrium is running, causes fatal error for a better patch to workbench_moderation_profile if you run into this issue.