When I save a new or existing node, the node save page keeps spinning until my server responds timeout.
Nevertheless, when I open any other page during this spinning, I get the save confirmation message on top of the new page.

Tried without succes
- update to 2.4.3
- clear cache
- updb
- rebuild permissions
- disabling recently installed custom modules (node_resave, track_field_changes)

Comments

katrien_w’s picture

katrien_w CreditAttribution: katrien_w commented

In addition:
custom content types are saved in the background while the save page keeps spinning, but oa wiki pages refuse to save at all and just give WSOD. My error log shows an error I haven't seen before:

PHP Fatal error: Cannot redeclare _mimemail_replace_files() (previously declared in /var/www/vhosts/k00012.local/htdocs/sites/all/modules/messaging/messaging_htmlmail/messaging_htmlmail.inc:422) in /var/www/vhosts/k00012.local/htdocs/profiles/openatrium/modules/contrib/mimemail/mimemail.inc on line 139

Is this thread and latest patch relevant and worth trying?

thanks

leo_g’s picture

leo_g CreditAttribution: leo_g commented

Hi Katrien
The php error occurs because _mimemail_replace_files() is declared twice. Please remove the messaging module and check if your site is working again. You won't need the messaging module, Open Atrium uses message and message_notify for sending notifications. Also the messaging module doesn't have a stable release for drupal 7 and development stopped about 3 years ago. You should be (very) careful with modules like this at all!
Greetings,
Leo

katrien_w’s picture

katrien_w CreditAttribution: katrien_w commented

Thanks for your suggestion. I disabled messaging but that didn't solve the problem that the node save button doesn't redirect to the updated node view. Any other ideas what could cause this?

Argus’s picture

Argus CreditAttribution: Argus as a volunteer commented
Category: Bug report » Support request

@katrien_w Perhaps you should you try to reproduce the problem on a clean installation of Open Atrium. This always helps me differentiate between errors I introduced myself and a "real" Open Atrium bug.

Changing this to Support request meanwhile.

mpotter’s picture

mpotter CreditAttribution: mpotter commented
Status: Active » Postponed (maintainer needs more info)
JKingsnorth’s picture

JKingsnorth CreditAttribution: JKingsnorth commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Things can get declared twice if you didn't do a 'clean' update. Ie: Didn't delete all the old files, and re-upload the new ones. Otherwise the same module can end up twice in the installation.

There's been no response for a while, but if this is still an issue for you then please do reopen and we'll see how we can support you.