Matthew Orr
Curator Engineer
December 28, 2021
Some History and a Prediction
Take a journey with me back in time. In the beginning of what would eventually become Curator, we thought it was a good idea to bury our recommended PHP settings in hard-to-find documentation that may or may not have been published on the web. For anyone who purchased Curator, it turned out to be this unintended but thrilling (not in a good way) game of waiting until something caused problems, guessing at a solution then contacting Curator support when the problem didn’t go away. Believe it or not, this was also an unenjoyable experience for the InterWorks Curator team to troubleshoot and fix.
One day, we got bored and wondered what would happen if we turned a lose-lose game into a win-win. As logic-defying as that may have been, we decided to give it a shot anyway, so we added alerts and warnings to Curator’s backend to show when things weren’t set up optimally. It included things like when PHP’s memory or upload limits were set too low.
That brings us to today. My prediction is that you saw one of those warnings, so let’s dive in to how to fix it, so those warnings stop nagging you.
There are only a few different places where PHP puts its configuration file. Instead of listing those places and making you search through each one, there’s a definitive way to determine which one applies to your Curator instance:
Curator has added the feature to be able to send mark commenting data to a webhook. With the widespread use of API integration platforms, this really opens the doorway to virtually unlimited use cases.
If you’ve got users reporting access issues, your first stop on the road to resolution should be the User Menu Access button. This feature gives you a snapshot view of any given user’s current menu structure, as well as their permissions status for all the content within that menu.
In the rapidly evolving landscape of Analytics, it’s become paramount to give your users maximum flexibility while also delivering reliable and sophisticated insights. Today, this means spending a huge amount of effort to create complex dashboards that consider all the variety of ways someone might want to see your data – all in the pursuit of empowering people to make well-informed data-driven decisions.