Jump to content

Jim M

Invision Community Team
  • Posts

    9,611
  • 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. It's worth noting that around 100,000 rows is not a lot. We have clients in the millions for these tables and they function perfectly fine with with our same table configuration that you have. You may wish to move all tables from MyISAM to InnoDB. However, if the table keeps crashing, this is something the hosting provider will need to analyze with their MySQL server configuration on why that is.
  2. Agreed. Allowing a user to delete a post or a topic they made by accident or something in that sort of realm is what the current deletion function is for. Once you get into a more mass deletion realm, you (as an administrator) would ideally want to talk with your member before they do that. They could be temporarily angry and delete all their posts then regret it (or you regret it).
  3. That is correct. They can only delete one off content.
  4. Their member group would need to have permission to delete their own posts in ACP -> Members -> Groups -> edit group -> Can delete own content? That will enable them to delete their content one by one. To delete all their posts, this would require intervention by an administrator, either by way of an account deletion request in Account Settings or via a contact request which the administrator acts on.
  5. Your hosting provider will need to review why the table keeps crashing if they keep repairing it and it keeps crashing. A duplicate entry error would not cause the table to crash.
  6. You can place this in the header of your theme (ACP -> Customization -> Themes) or in the Google Analytics integration (ACP -> System -> Integrations) as that implements in the header as well.
  7. All I can think is back to your CDN or server caching. Would turn that completely off.
  8. Would not go by what PMA is reporting there as that info can often be behind based on refresh timing, garbage collection, etc.. I ran the task manually with a manually queried SELECT * from that table and after running the task manually, I have new entries. Therefore, the table is slowly being built as intended so it does not bring down your community.
  9. Unfortunately, I logged in as a user who has not made any comments/reviews, etc... who belongs to the member group and I am seeing the Downloads button now.
  10. There should not be orphaned images. The software will delete attachments once content has been deleted. The only way would be to create a new folder and then change the file storage configuration to move to that new folder, thus it will only move items it is aware of.
  11. Please note, I'm not stating you're wrong that the option shouldn't be there. I'm just stating it is currently working as intended. I have moved this for you to Feedback so it can be evaluated for a new feature addition.
  12. Feel like this may be better utilized as a suggestion, rather than a bug. Technically, this is functioning by design. Just you're also not wanting it to show up in the sitemap file as well and not be indexed. As there are other items which utilize a sitemap file as well, not just search index spiders.
  13. You'll want to make sure that your database connection is actually the right database as I get the below when going to your upgrade area: Table 'ipbcore_sys_conf_settings' doesn't exist
  14. Hard to say without an example tied to a current content item. Could be a failed deletion from when you previously allowed something large, from a third party app which did not follow our guidelines, something like Gallery where the original file was kept, etc... Too many cases for us to narrow down.
  15. I'm a little confused on how you're seeing this then if you do not have a topic or other example content where they are?
  16. Sorry, please make sure you have checked the above
  17. Would double check it against the requirements checker and ensure that your MySQL connection details are correct in conf_global.php:
  18. We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.
  19. Please ensure that you're on PHP 8.1 or PHP 8.0.
  20. I'm afraid, this is not a service we currently offer. Generally, this would be the responsibility of your hosting provider assist with these kind of service.
  21. Depends on the bot, depends on what they're trying to do, etc... There's good and bad bots and grey area bots. If you find them to be malicious or otherwise not wanted, you can contact your hosting provider to block them at the network/server level.
  22. Keep in mind it’s content you started, not replied to. IE you created a topic.
  23. Have you limited your search index in ACP -> System -> Search to specific time period which is excluding content now?
  24. I have removed sensitive information from your post. You're welcome to create any Feedback topic with suggestions for future release. If you have information that you believe this to be a compromise, rather than just an individual obtaining already compromised credentials from another attack, please create a message to our accounts team here: https://invisioncommunity.com/contact-us
  25. That is the copyright line in ACP -> System -> General Configuration.
×
×
  • Create New...