Jump to content

Jim M

Invision Community Team
  • Posts

    9,255
  • 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. Thank you. Looking on iOS 13 in general, I am seeing some oddities with some images but cannot directly reproduce the issues with the editor, CSS, or rating system that you are having. I submitted a bug report for the image issues I am seeing. Are you using the same connection as a device which is able to see these things? I just want to rule out any network connectivity issues or blocks.
  2. Available logs can be found in /uploads/logs on your filesystem.
  3. The error is actually a "-200" error which is from plupload which means that the server has encountered an error processing the upload. This can be anything from the upload has exceed the size limit for PHP, PHP memory limit, etc...
  4. Please contact your hosting provider for assistance with that error. It is an error with your MySQL storage.
  5. The fix was we did not have images on some of our forum categories, Matt uploaded images to those. What you are stating here is different. Have you tried clearing your browser's cache? If you're still having an issue, could you please provide us an example URL and screenshot to what you're seeing?
  6. There are a lot of topics covering this but the above post from Matt will give details. We will be further integrating with external services, as Matt mentioned, to further fill this gap.
  7. If users are receiving a password reset to other email domains and not simply @me.com , I would suggest working with your email provider to see why these are being blocked. Email is a tricky thing and often, can just be a configuration issue with your email provider and domain that me.com is stricter about spam thus rejecting it.
  8. I'm afraid, we do not set a _gads cookie, nor do we remove it. I actually see this cookie fine while viewing your community:
  9. If you're having issues with third party software, please reach out to the vendor for assistance. Our software would not remove third party cookies.
  10. Thank you. This error is from the plugin "Pages Blocks Countries" You can access this as well by going to ACP -> Support -> View x Third Party Hooks
  11. Please enable full access to our account and I can look up that hook number to see.
  12. One of your custom or third party blocks is not compatible with PHP 8.
  13. We will need that error message regardless.
  14. When viewing your "links" page in Pages, I am seeing a 500 Internal Server Error being rendered. You will need to check with your hosting provider if you are unsure how to obtain the error message from this error.
  15. Could you please clarify what you are translating to?
  16. I would suggest changing your email address on file to a Gmail or other email address as this seems to be local to your email provide, I'm afraid. We typically do not have any issues emailing other clients. Unfortunately, I would advise contacting your hosting provider for assistance here as there will need to be an error for us to escalate the ticket. The error you're getting is a lot like that of your car's check engine light, it says there is an issue but not exactly what or where. We need that what or where to proceed troubleshooting.
  17. As you're a Cloud customer, I have moved this to a ticket where we can discuss your options.
  18. You would be working against the software essentially then so there isn't a current way. Anything using the editor.
  19. Odd, we received your reply ~7 hours ago from me replying now. Any difference between how you're replying that it's not going out? We replied back ~6 hours ago. Did you reply after that? If you are receiving a white blank page, this is typically a suppressed PHP error. Please check your server error logs for this error.
  20. Unfortunately, we did not hear back from you that you have updated the access details as requested. Since you have posted now, I have checked these and now escalated your ticket.
  21. Correct, that is intended. You can certainly provide your suggestion in our Feedback forum if you want that changed.
  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.
×
×
  • Create New...