Jump to content

Stuart Silvester

Invision Community Team
  • Posts

    3,625
  • Joined

  • Last visited

  • Days Won

    27

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Stuart Silvester

  1. Your customised theme is out of date, you'll need to check any modified templates for changes (as the upgrader asks you to). In this case it's the includeJS template that has changed.
  2. The code doesn't know whether that's a current extension or one that's there from an older version of the app that's no longer used (which is why we've opted to remove the legacy code, it was masking issues). In a lot of cases applications are stored in read-only locations, but as noted it's not something for us to generate on upgrade. I'll point out again, there has been 5 years to implement the proper extensions method.
  3. Added what? extensions.json was implemented in 4.4, from the first beta in 2018. There's nothing we can do in an upgrade step to fix a file missing from an application.
  4. Extensions.json was introduced in 4.4, all apps that use extensions should have one.
  5. Oh yes, make sure your apps have an extensions.json file, the legacy fallback code was removed in .12 I'm going to assume they're old apps and you haven't added an extension since we moved to the JSON method (that's the action that writes the file)
  6. Is this still a problem? I cannot reproduce it at this time.
  7. I don't think there's any specific issue here that would or would not be fixed in .12, you could try going to AdminCP > Support and clicking 'Clear Caches'. That might solve the problem for you.
  8. 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. Please also let us know which forum you are creating a topic in (this may be relevant to the issue) We look forward to further assisting you.
  9. Counter-intuitively having large limits defined may cause large files to fail because it doesn't allow chunked-uploads to be used. It could be that PHP is running out of memory or time to process a large file. Having upload_max_filesize / post_max_size set to reasonable values nearer the default may solve this for you. Ultimately, it is something your host is going to need to work with you on.
  10. This was an issue that is fixed in 4.7.12. you also have to specifically enable the cookie consent system it is not enabled by default.
  11. Looks like this is left over from the Mobile app directory, we'll get that disabled.
  12. The converter application provides redirects for the old style URLa. Uninstalling the converter app will stop these from working
  13. Twitter's v2 API doesn't support the endpoints required for social media promotion. They've said it's coming soon for a few years
  14. This is normal, it's an interface file that isn't part of the front session handler. These files are used for communication between the payment gateways and the community. Typically without any member (it's like an API/webhook request). We've made a change for an upcoming release (not .12) that will tell the customer in the checkout if the funding source refuses the payment.
  15. Your DDOS protection is blocking the communication between our systems and your community. <h1 class="message"><a href="http://blazingfast.io" target="_blank"><font color="#E0E0E0">Verifying your browser, please wait...<br>DDoS Protection by</font> Blazingfast.io</a></h1> You can whitelist requests to /index.php?app=core&module=system&controller=marketplace I suspect you were experiencing something else related to the license server because you do not have any failed connections logged.
  16. The issue was rebuilding the sitemap from the sitemap page and then running the background queue.
  17. You could implement your own url() method that doesn't reference those class properties but if you don't want it in a sitemap you can set the $includeInSitemap property to false. You may still have issues if something requires url() and those other properties though
  18. Yes, you can use + and - in the search term (boolean search is implemented)
  19. 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.
  20. I would recommend sending an email in to our Sales team, they may be able to work something out.
  21. Interesting, I would to an extent (there could be various factors such as firewalls etc) expect it to work. If you want to play around a bit, you could plug your Android in with debugging mode and see what the Chrome dev tools show for network activity when a notification is received.
  22. You're seeing those because there was an issue fetching the notification content from the server. In that case it falls back to default text and links to the root of the community. The issue could be an authentication failure or something else. If you try disabling push on the community and re-enabling it, do you see the full notifications?
×
×
  • Create New...