Hi!
I bumped into very strange error / warning.
After editing the book I got error: "This book has been modified by another user, the changes could not be saved."
Everything is OK, changes are committed, so I don't know why this error is appearing?!?
I have test site on same server, so I copied my production site to test and tried to reproduce error: nope. Error disappeared. WTF?!? ;)
On test site I disable googleanalytics + apachesolr_stats modules, and set variable "apachesolr_read_only" to "1". Test site is @ http protocol, while production is https.
So, I disabled googleanalytics + apachesolr_stats modules, and set variable "apachesolr_read_only" to "1" on my production site, run cron, flush all caches, but no, error is not moving.
I have another books, and after editing them I don't get error, so I really don't know how to reproduce this error.
If you have some ideas, please share them, if not, you can close this issue.
Comment | File | Size | Author |
---|---|---|---|
#8 | cmfspaces.make_.txt | 7.68 KB | gmclelland |
Comments
Comment #1
mariomaric CreditAttribution: mariomaric commentedHeh,
problem solved with disabling (+ uninstalling) Outline Designer, editing problematic book, then enabling OD again - and now everything is OK. Strange.
JFTR. :)
Cheers.
Comment #2
mariomaric CreditAttribution: mariomaric commentedSorry for spamming, but error jumped again. :(
Enabled modules:
Comment #3
btopro CreditAttribution: btopro commentedthis is a common drupal error that I've been able to replicate based on either having multiple users altering the weights (drag/drop) of books at the same time / session duration. OR, sometimes when you have 2 different windows / browsers open and working on different parts of a book outline it'll happen. Drupal will detect that something is being edited and doesn't always break the "lock" immediately (like when you goto an edit page and then close the browser this can happen at times too). Not specifically a problem with this module I don't think, mostly an issue with hitting the DB at similar times.
Comment #4
mariomaric CreditAttribution: mariomaric commentedHi!
Tnx for info - yup, on test site only one user is logged in so there is no error.
If you think it's nothing important and there is no need for escalation, feel free to close issue.
IMHO this message can be confusing to (new) editors if they are not familiar with this issue - it's not user friendly to have fake errors. :)
Comment #5
btopro CreditAttribution: btopro commenteddefinitely can be confusing, unfortunately one of those usability issues in D6
Comment #6
btopro CreditAttribution: btopro commentedhmm... not sure if it's related to some OG integration stuff but getting this error again.
Comment #7
btopro CreditAttribution: btopro commentedso this was evil to track down but #968882: Method cache_clear_all() in memcache.db.inc doesn't clear memcache if $cid is set and $wildcard is TRUE was my issue. I also fixed the book stuff in my menu table (was creating a book incorrectly at a code level) so somewhere between the two issues this is fixed. Unfortunately it seems that memcache won't look into the issue and as it's the backbone of ELMS I can't really run memcache at this time til it gets figured out. I'll have to dig into it someday but for now we'll be running w.o. memcache as a result
Comment #8
gmclelland CreditAttribution: gmclelland commentedLooks like I'm experiencing this as well when I click on "Add content". It's strange as it adds the nodes, but it doesn't display their titles in the OD hierarchy until you refresh the page.
I attached my make file. If you want to try to reproduce.
Note.. I am using Outline Designer 6.x-1.3 and pressflow, spaces, and purl. I am not using Memcache.
Hope that helps,
-Glenn
Comment #9
btopro CreditAttribution: btopro commentedare u using dev or 1.3?
Comment #10
gmclelland CreditAttribution: gmclelland commentedI'm using 1.3
Comment #11
btopro CreditAttribution: btopro commentedhmm... InnoDB or MYSAM DB encoding? I haven't experienced this issue since I switched to inno. also might want to try this patch -- http://drupal.org/node/360377
This sounds related too tho it's marked fixed -- http://drupal.org/node/272900
I'm running the same stack you're talking about at elms.psu.edu and am not experiencing this issue though I'm also not testing for it very heavily at the moment.
Ultimately we might need to override this it would seem -- http://api.drupal.org/api/drupal/modules--book--book.admin.inc/function/...
Comment #12
gmclelland CreditAttribution: gmclelland commentedI was using MYSAM, but then I switched all tables to innodb. Still I have the same problem. I haven't tried the other patches yet.
Comment #13
gmclelland CreditAttribution: gmclelland commentedFYI..
I just applied the patches http://drupal.org/files/issues/364529_menu_tree_all_data_cache_6.x_7.patch (from http://drupal.org/node/364529#comment-2939580) and http://drupal.org/files/issues/reset_book_cache_6.x.patch (from http://drupal.org/node/360377).
Still this didn't work. :(
I also cleared the caches after I applied each patch.
Comment #14
btopro CreditAttribution: btopro commentedhmm, using any other book/menu related projects?
Comment #15
gmclelland CreditAttribution: gmclelland commentedNo, just those modules listed in the make file. I'll keep digging, I believe I have another test site where it is working ok.
Comment #16
gmclelland CreditAttribution: gmclelland commentedOk, I have done some more testing. I tried the same setup with Drupal 6.22 instead of Pressflow. (Same Problem)
I have two different VMs.
1. Standard 1.4 Ubuntu 11.04 - Aegir 1.4 with APC
2. Quickstart 1.0 without APC
Both experience odd behaviors
VM#1. shows - This book has been modified by another user, the changes could not be saved. errors in red. When the pages are duplicated it doesn't fully show the whole tree of pages until you refresh the page.
VM#2. when the pages are duplicated it doesn't fully show the whole tree of pages until you refresh the page. Doesn't show "this book has been ..." message
Should we set this issue back to open? Next up, I'm going to start disabling all the modules and see if that has any effect.
Comment #17
gmclelland CreditAttribution: gmclelland commented@btopro - what version of php do you run? Me - I'm using php 5.3
Comment #18
btopro CreditAttribution: btopro commented5.3 here too. does this happen if you install locally and use a different browser? Might be a caching issue at some level cause I'm running in production without issue (OD 1.3 that is). Switching this issue to 1.3 since you said that's where you've experienced it (the dev for this project is a wasteland).
Comment #19
gmclelland CreditAttribution: gmclelland commentedOk, after a lot of testing. The problem I believe happens when you have a minimum cache lifetime/ page cache maximum age set. This will cause the following problems:
1. When you duplicate the branch, OD will only show the root node of the duplicated branch with arrow next to it. When the arrow is clicked it points down but nothing is displayed under the root node. When you refresh the page, you will see the sub nodes under the root node.
2. Sometimes new nodes that are created with OD don't show their titles when using "Outline child pages", you simply see the icons next to where a title would normally be displayed.
3. After deleting a branch of hierarchical nodes the branch will be removed from OD correctly, but when the page is refreshed or if you go to another page then it will show the error in red "This book has been modified by another user, the changes could not be saved."
To fix the problems above, simply set the minimum cache lifetime/ page cache maximum age to none. Not sure if this is acceptable to other people, but maybe it provides enough information to work on fix? Maybe it is intended to work this way?
Hope that helps,
-Glenn
Comment #20
btopro CreditAttribution: btopro commentedSounds like we might need to do some kind of cache rebuilding on request.. yeah not sure how to do that without insane performance implications. Might be worth using the tool to build the site and make quick changes after the fact with the expectation that there are some issues when modifying live material.
Thanks for tracking this down, haven't had anyone be able to figure it out in the last year :)
Comment #21
btopro CreditAttribution: btopro commentedComment #22
btopro CreditAttribution: btopro commentedSolved in beta1