Jump to content

Jim M

Invision Community Team
  • Posts

    9,253
  • Joined

  • Days Won

    45

 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 Jim M

  1. x-proxy-cache header is still present on your community. This may be coming from your server. You would need to engage your hosting provider if you are unsure.
  2. You would then need to contact your language pack author for assistance as this is an issue with the language pack.
  3. As my colleague mentioned, that is from the plethora of third party addons which you have installed. You would need to disable those to have your community online again.
  4. Please upgrade to the latest release. This seems to have been resolved.
  5. Please ensure they have the moderator permission “can manage sidebar?”
  6. As mentioned, this has been moved for a ticket so we can investigate this more. Unfortunately, I can’t provide an ETA of when it will be resolved but our team works on offline issues as fast as they can.
  7. Was anything changed? While I am seeing this error again now and have moved this to a ticket, something seems to be putting into memory large amounts of data here which shouldn't be happening natively. Please watch your email for further correspondence.
  8. You had some very odd session configurations in your php.ini that was in your installation directory. As a courtesy I removed those as they likely were causing some session issues here and elsewhere. I will message you these so that you have them for review with your hosting provider. Once I disabled all third party applications and plugins via the recovery tool and cleared cache. Your registration page is working fine. Thus, this is one of your third party add-ons creating this error for you. You will want to review each one of the many third party applications/plugins which you have installed and enable them one-by-one to check for which one is causing the memory issue here.
  9. I am receiving a 500 Internal Server Error when accessing your community now. Please provide that server error log entry for us now.
  10. You would need to disable all third party applications/plugins to see if that resolves the issue then. Something is exceeding it and the normal application should not do this.
  11. You would need to increase your PHP memory limit. Something being loaded there is exceeding it.
  12. Sorry, server access logs will not help here.
  13. I'm afraid, there is a disconnect. Please let me rephrase what I said. Currently, we do not have an error log entry to describe the error you're encountering so I cannot give you information on how to solve this. A white page is your server suppressing any action on that page due to an error, thus, we cannot use any information we have available to us to determine that error. Therefore, you would need to contact your hosting provider to obtain the error. We then can help you resolve the error once we know what the error is. If you want to disable your third party applications/plugins to see if this makes any difference while waiting on a reply from your hosting provider, that is something else to do as this is often the issue when a third party add-on is not compatible with the most recent release.
  14. Yes, if you are unable to obtain the correct logs, I'm afraid, you would need to contact your hosting provider so we can know what the error is and provide you with a solution. Without the error logs, we do not know the error because your server is suppressing the error. If you think this may be an issue with third party applications/plugins and you do not have access to your ACP. You can also try recovery mode: https://invisioncommunity.com/4guides/client-services/getting-support-r292/#recoverymode
  15. Neither of these errors are related to the issue, I'm afraid.
  16. A white error page would need to be grabbed from your Server Error log, not our software logs. I'm afraid, you would need to contact your hosting provider for assistance if you are unsure how to grab that error. Hosting management, such as grabbing error logs are outside our scope of support.
  17. Please ensure your PHP is set to 8 and then please obtain us the server error log as the above error is from PHP 7.
  18. This seems to have been maybe a temporary error as I unlocked them and was able to run them without error. Please let us know if it does come up again. It may be that there is an issue with your CRON if so. I'd suggest ensuring that PHP 8 is running on your cron task command.
  19. I've tagged this to a developer to get their opinion on what may be happening here as so far we have been unable to reproduce this directly with an unmodified language pack.
  20. Confirming the language pack is compatible with the release you're on is the first step. However, I would say this sounds like a caching issue. Are you able to reproduce this on an unmodified language pack if you stay on it for long?
  21. Is this happening on an unmodified language pack? If not, please check your language pack is compatible with the latest release. Sounds like something changed and your language pack is not up to date.
  22. 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.
  23. Just curious if this was a case sensitivity thing with BOY vs boy which may be included?
  24. Our team has looked at this and aware of an issue that may be there for the main page of the ACP Marketplace. This should be resolved shortly. Sorry for the inconvenience.
×
×
  • Create New...