Jump to content

Jim M

Invision Community Team
  • Posts

    9,606
  • Joined

  • Days Won

    46

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Jim M

  1. Please submit a contact request to our accounts department for assistance with cancelling your license: https://invisioncommunity.com/contact-us As you’re self hosted, you would just take a backup of the files and database and that will be what you restore should you wish to resume your community. Once you get the backup, you can decommission your hosting.
  2. The IP address listed there is returning a 1 from the Spam Defense so that means they are OK to register. You do have Spam Analysis turned on, which we have some improvements for in a future release, however, this could be marking something that they are posting as spam. You may wish to disable this temporarily to see by going to ACP -> System -> Smarty Community -> Spam Analysis.
  3. I have performed the upgrade for you at this time.
  4. I would suggest contacting your hosting provider or server administrator to ensure you're looking at the right path. That would indicate that the files were uploaded to an incorrect path or not all were uploaded (namely the index.php) If the correct path is being used to the URL mentioned, you would want to check permissions and ownership. If all the above checks out, there would be a server configuration issue.
  5. This would be the app on your device.
  6. Correct. The server cannot write to the needed folders, such as applications, datastore, plugins, and uploads
  7. You would just create the database, not the tables.
  8. Indicate the server cannot write to the file storage. Check permissions and ownership.
  9. You would want to verify this in Redis itself.
  10. Would disagree with this. Communities I've been a part of, especially when we were back in the old day of IP.Chat available and today with shoutboxes, members would ask worthwhile questions in chat, and they become lost forever. So much so, on my own communities, I had to post warnings on the page telling them to create a topic for any questions on their cars (being a car site). Then completely disabled IP.Chat entirely due to members not understanding the differences. Even for a brief period here, we had chat enable and people went in to ask questions about their community for support. The more avenues you offer for discussion, the more you are downgrading the long-term content options which take thought in putting forth and people will gravitate towards the "easy" non-thought provoking one. Kind of a separate use case for these players as they are more private focused and not entirely based on marketing their clients' content but communication between colleagues. Unlike, a community, where you're not selling content, but it is pretty much your product to offer and market to get more members. We understand the usefulness of chat, as we use Slack as a company but still use an internal community for a knowledgebase, product discussion, and project management. Think in the terms of community, as Matt mentioned, chat is weak and potentially pulling content away from the community's usefulness.
  11. Sounds like your Redis server isn't running if the system can't connect. You would want to verify that first and ensure the methods you setup to connect over are valid.
  12. Do you have an example URL with the time it is taking to execute? Seems we're missing that information in the slow query log. I just clicked a topic on your community which has over 1000 pages, and it didn't take a long time to execute than I would expect.
  13. Please be advised I have moved this to a ticket so we can further investigate. Please watch your email for further correspondence.
  14. Would recommend using our Cloud and not worrying about making configuration changes if making changes makes you that nervous 🙂 . Self-hosted is really self-managed when it comes to things like this. Making file edits and renaming a folder isn't specific to our software so we assume, if you are self-hosting, you understand these basic changes and how to revert them should something go wrong. A Feedback topic also really isn't the best place for in-depth information, we recommend referring to the guide for any in-depth information and then opening a support topic for any follow up questions regarding the software: If you have suggestions or feedback on the help guides, we recommend you opening up a new topic to do so. Keep in mind that especially guides that interact with hosting elements, we're not here to guide on the hosting-side but rather just the software.
  15. Please make sure you’re on the latest release.
  16. Means you have an error in the template (syntax or otherwise) or you have mod_security or something on your server blocking the save action.
  17. While I get the response ID is not really human legible, it is an always valid identification of the response. The "action" you are suggesting the change to, could change over time and seeing a response in the log that could be varying could get confusing and could hinder troubleshooting. Afterall too, we use it in the configuration screen as well, so it makes sense to relate it back that way. I wouldn't be opposed to the response ID and action taken being shown here. As that way the evergreen ID is shown, and the historical action is logged.
  18. Yeah, as Terabyte mentioned, the only way would be to surgically add all the table rows and references back in, ensuring none are missing (if any are missing, you will get errors). Note: we do not support this kind of custom restore and any issues which result from it would be outside of scope as well. The easiest and cost-effective way to do this would be just to restore a full backup.
  19. I see that there is a hook interfering there. You'll want to disable all third party applications/plugins and then test again.
  20. Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
  21. I have answered your support ticket and resolved this for you. In the future, you can run the upgrade at /admin/upgrade
  22. Glad to hear it's working fine. It may still be worthwhile contacting your hosting provider to ensure permissions are correct and that you know how to check in the future.
  23. That is understood. We are attempting to assist you here. If the software is having issues writing to your server, this is the first troubleshooting step to take.
  24. You would need to contact your hosting provider if you are unsure how to check folder/file permissions and ownership. It is different per server and based on your configuration.
  25. While that may be, doesn't mean something could be off and caching was simply hiding that.
×
×
  • Create New...