If you encounter unexpected behavior in Siteligent or the Siteligent Connector, submit a support ticket.
Include as much detail as possible, especially:
What you expected to happen
What actually happened
The affected website, if applicable
Steps to reproduce the issue
Exact error messages
Screenshots or relevant logs
Clear reproduction steps are particularly useful because they allow our team to reproduce the same problem and investigate its cause. If the issue is related to a website, make sure you link the affected site to the ticket when creating it.
What Happens After You Report a Bug?
Our engineering team reviews reported issues and investigates confirmed bugs.
If a bug is confirmed, we'll work on an appropriate fix and provide updates when relevant.
Requesting a Feature
Have an idea for something you'd like to see in Siteligent? You can submit a request by creating a support ticket. A useful feature request should explain:
What you'd like to add or change
Why you need it
How it would help your workflow
Who would benefit from the feature
How you would expect it to work
For example, instead of simply requesting: "Add another cache plugin."
A more useful request would explain which caching system you need supported, which sites use it, and what you'd like Siteligent to be able to do with it.
What Happens to Feature Requests?
Feature requests are reviewed by the Siteligent product team as part of our product planning process. Not every request can be added immediately, but your feedback helps us understand what customers need and where the platform should improve.
If a requested feature is selected for development, we'll share updates when appropriate.
Have a Bug or Idea?
We're always interested in hearing what's working, what's not, and what would make Siteligent better. Create a Support Ticket to share your issue, feedback, or idea with our team.