Hey Roberto, Since it’s intermittent, it’s pretty tough to write detailed replication steps. I’ve been keeping an eye on it to see if I could tie a specific action to triggering the problem.
Today the indexes broke again and I noticed that it didn’t happen until after I moved a document to the trash. As soon as I did this, all of my indexes started showing the server error page. I’m going to continue monitoring and see if any other actions trigger this. Interestingly enough, I’ve been doing a bunch of updates to the metadata today and did not get the error at all. Are index updates done differently when moving documents to the trash vs updating metadata? This really feels like a caching problem to me, but I honestly don’t know enough about Mayan and Django to know if this is a reasonable assumption. Thanks, -- Dave Kimmel [email protected] > On Aug 2, 2017, at 13:22, Roberto Rosario > <[email protected]> wrote: > > Thanks for reporting this and for the debug information. The first step is to > try to make it repeatable to find the cause, things that happen sometimes and > sometimes not are very hard to track down. I'll try to write a test to > replicate this behavior in development. Thank you. -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
