Jump to content

Marc

Invision Community Team
  • Posts

    14,983
  • Joined

  • Last visited

  • Days Won

    263

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Forums

Events

Store

Gallery

Everything posted by Marc

  1. Generally you would bypass word filters for some groups in this scenario. It would not be for one specific word though, but rather for all. You can do this within groups. I would say however, if one group is not doing so, why would you need to bypass it?
  2. No problem 🙂 It happens
  3. The correct way would be to restore, however you could try creating with this if CREATE TABLE IF NOT EXISTS `core_sys_cp_sessions` ( `session_id` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `session_ip_address` varchar(46) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `session_member_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `session_member_id` bigint UNSIGNED NOT NULL DEFAULT '0', `session_location` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `session_log_in_time` int NOT NULL DEFAULT '0', `session_running_time` int NOT NULL DEFAULT '0', `session_url` text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, `session_app_data` mediumblob, PRIMARY KEY (`session_id`), KEY `session_running_time` (`session_running_time`), KEY `session_member_id` (`session_member_id`) )
  4. Ive not seen this happen on my end, or seen other reports of it. If you test this in a different browser, do you get the same result?
  5. I have created a ticket on this, so we can take a look for you
  6. You need to check your database to see if that table has crashed and rectify from there. You may need to recover that table from a database backup if its not present
  7. Glad to hear you now resolved the issue. If you have the same problem on the next update however, please let us know
  8. 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.
  9. Are you visiting on the same device?
  10. On taking a look at this, please could you disable all 3rd party applications and plugins and have them test this. You have a few things there that interact with that process
  11. Yes, the bug was fixed in 4.7.1. It may well be the resource was removed before that point
  12. That is mysql configuration. You would need to contact your hosting company on this
  13. Have you first of all looked at the block manager to ensure the database is actually on the page? The most likely scenario is that someone has unintentionally removed the block
  14. Please disable 3rd party items and test this again first of all. I see there are 2 loaded at the point those errors occurred
  15. Im not sure what we can really add here unfortunately. We are getting 403 when sending requests to your server, so it will not work. You mention logging in, but this also needs to be able to connect back and forth from that location.
  16. You would need to contact your hosting company to ask that question. Usually you can just repair these with tools like phpmyadmin, but I would contact your host if you are unsure
  17. Sorry, I should say recommendation. However these are still hosting related items, not software
  18. This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues
  19. This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues
  20. This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues
  21. This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues
  22. This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues
  23. This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues
  24. This issue has been resolved in the latest 4.7.11.1 release. Please upgrade your site to resolve this, and let us know if you have any further issues
×
×
  • Create New...