The site I'm working on has both English and Spanish translations. Upon installing Workflow and Workflow Access, I get 'importing translation interface' messages, and then a message that I need to rebuild content permissions. On another (English-only, and drupal 6.12) site this worked just fine, but now I am finding that the rebuild always gets stuck at some point and does not complete.

My site is running Drupal 6.10, PHP 5.2.9, Linux, and MySQL 5.0.77.

I have the following modules enabled:
admin_menu
content
filegroup
filefield
imagefield
number
text
comment
content_translation
database_logging
forum
help
locale
menu
php_filter
search
taxonomy
tracker
devel
event
imageapi
imageapi_gd2
imagecache
imagecache_ui
internationalization (i18n)
customerror
google_cse
lightbox2
menu_block
print
nodequeue
views
views_ui

Any advice would be appreciated. Thanks!

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

Are there any error messages displayed? I guess there could be
1) a time out
2) a php memory limit problem.

But this could have happened also for other access modules.

brian_c’s picture

brian_c commented
Version: 6.x-1.1 » 6.x-1.5

I seem to be getting something similar.

When I enable the Workflow Access module, every admin page has a warning that I need to rebuild content permissions. Rebuilding them goes through a lengthy process with a percentage slowly counting up, and message "Remaining 1 of 1". Then it always hangs right at the end, right before it gets to 100% (so it gets to around 96-99% then just stops).

If I reload this page, I will get a message:

"An error has occurred.
Please continue to the error page

An HTTP error 403 occurred. /batch?id=12&op=do"

Clicking on the error page just takes back me to the Post Settings page (ie where you click "Rebuild Permissions"), with an extra error message: "The content access permissions have not been properly rebuilt."

If I disable Workflow Access module, the content permissions are rebuilt properly, this also happens nearly instantly.

brian_c’s picture

brian_c commented

Upgraded to latest version of Drupal core (6.20), and it fixed the problem for me.

Was running 6.16 before.

Bastlynn’s picture

Bastlynn commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

This seems to be related to timeouts in your environment. The more nodes you have, the worse impact a rebuild will have on your system because the system is recalculating the access for each node and saving it one at a time. It's not directly related to Workflow code, but more how Drupal itself works in this situation, which should be rare in the life of your site.

I would suggest updating to the latest versions of your contrib modules and core to take advantage of any efficiencies in that code, and if possible tweak your php.ini and server environment settings to give your website as much memory and time as possible to complete this action. You can usually drop those settings back down after the rebuild is over.

If your site is on a subpar hosting that won't coordinate with you on this, then you may be stuck or may need to lock the site, copy the site to a local machine, run the updates, and reload the DB from that. It's a pain, but it would work.

shabbir’s picture

shabbir commented

hey,

I have migrated to Drupal 7 and facing the same problem. My Drupal core as well as contrib modules are upto date and even when i ran my update.php script it ran successfully.

When i run rebuild it takes me to the progress bar page and then the progress bar just hangs at 59%. I have kept it entire night to see if it takes time but it still doesnt work. Also i have increased the memory limit in my php.ini file but it still doesnt fix the problem. I have tried and tested a lot of methods, but have got dirt on my face, if anyone could help me out over it would be much appreciated.

Regards,
Shabbir