Prateek Rungta
Prateek Rungta
Makes sense!
@engram-design Figured it out — there was no discernible feedback on the front-end due to #313.
Hi @marionnewlevant, curious about your plans for the plugin. Is there a release planned with the #27 PR for the `{% return %}` tag, or will there be no more...
No one would have run that command manually on the server. Could it have been triggered by Craft’s auto garbage collection routine(s)?
> Were the revisions’ nested entries in tact before the update? No, there were missing nested entries in the DB before the update as well. However, I assumed that might...
@brandonkelly We just experienced this issue once again on production. I am trying to isolate the issue down to clearly reproducible steps. What we know so far is that the...
@iwingate-digistorm Yes, we continue to face this issue at our end and it is causing much distress. Thank you for sharing the steps to replicate. I will try and see...
@brandonkelly We were also able to replicate the behaviour after reducing `maxRevisions` to `3`. Please see: https://www.loom.com/share/9fc8d06056014fb485ee8c932d4a2bb1?sid=a6a3920e-6786-4911-9ce1-2971c7ac4dc4 While this has been able to successfully reproduce the bug where nested entries...
@angrybrad The query time has reduced from 5s to around 2-4s after running `./craft db/repair`. Still seems excessive though.
It is definitely MySQL. I had myself re-created this entire server and to move away from MariaDB to MySQL a couple months back. Nevertheless, here is `select version();` and DB...