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. In looking into this issue, I found a bug where fields shown to only staff are still visible so I have submitted a bug for that. I have also asked for some investigation on what you're stating here on visibility of all fields. The search pattern for some would be restricted based on data but whether or not they show up, I am unsure if this is intended. 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.
  2. Our IP address has not yet been banned yet is the current assumption.
  3. Only certain field types would have the ability to modify their search selections. Namely due to the types of data which those fields contain.
  4. 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.
  5. Do you have a WAF or mod_security which may be preventing submission of special characters on edit? On my test 4.7.11, I am not encountering this with the expansion having double or single quotes.
  6. We have a built-in robots.txt file now. If we ever believe there to be a need to update it, we will. You can set to use it by going to ACP -> System -> Search Engine Optimization -> Crawl Management.
  7. Here's some information on using the language system to change the words of almost everything:
  8. Could you please try again now? I installed some missing patches on your installation in ACP -> Support
  9. This looks like an issue with one of your third party applications/plugins. When I disable all of those, I am getting a Post Before Registration screen which is correct per your settings.
  10. That looks like an issue with your Pages Template not being up to date or incompatible. Would recommend switching to unmodified templates to see if that helps resolve your issue.
  11. Are you referring to our support tickets? If so, all support starts here. If you are trying to contact the author as my colleague instructed, you would need to go to their Marketplace listing to find their support contact method.
  12. As mentioned, please provide access: 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.
  13. You would indeed need to give the Pages Database a name. Please let us know what that is and we can take a look at your configuration: 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.
  14. Sorry, there may be some confusion. My colleague is asking for the Pages Database name, not your MySQL database version.
  15. I would simply recommend disabling CloudFlare completely to test.
  16. You may wish to completely disable CloudFlare as it may still block bot traffic. Please also ensure the webhook has all permissions and the correct URL is setup in Stripe for your community.
  17. As mentioned, you would need to ensure your webhooks are setup correctly and your firewall is not blocking them.
  18. Please verify and check your webhooks on Stripe. Typically, when this happens, something is not configured correctly or your server/firewall may be blocking Stripe's request.
  19. Are you running in dev mode? I just saw the path there.
  20. Please ensure that file is present and accessible.
  21. I have tagged a developer to see if there is any further insight into why this may be happening. If you're using CloudFlare, you may wish trying to disable that temporarily. Something might be happening there?
  22. Would recommend viewing your System Logs for more details here. You also are behind in Invision Community releases, have several outdated third party addons (one that is not compatible with PHP 8 ) and the "EXPECTED_KEY_NOT_PRESENT" error is an issue with your Twitter API Key.
  23. The account provided, I am not having any issues logging in with, I'm afraid.
  24. Thank you for removing those. Pages is running version 4.7.3 while the rest of your software is running 4.7.8. You will need to upload a fresh set of files from the Client Area and then go to /admin/upgrade to upgrade all applications to the latest release.
×
×
  • Create New...