Jump to content

Stuart Silvester

Invision Community Team
  • Posts

    3,633
  • 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. And language packs... basically anything you can get from the Marketplace in your AdminCP. The update check is less important in 4.5.1, if you visit the Marketplace listing in the AdminCP it will always use live data to determine if an update is available.
  2. A setting for this was introduced in 4.5.0 The Image Proxy was removed in 4.5 due to inherent security risks that it was no longer worth trying to work around since the adoption of SSL has drastically increased since we introduced the feature.
  3. I would recommend submitting a support ticket in the client area we will need to look into what is going wrong.
  4. Feel free to submit a ticket if you're having an issue. 4.5.1 (inc the betas) contained a number of improvements for checking for updates of Marketplace resources, I haven't seen any tickets to indicate these changes have issues yet.
  5. Have a read of this document, it covers the CSRF protection requirements
  6. We were generating renewal invoices way too far in advance, so they were including anything that expired in the timeframe. This should be fixed now.
  7. The Marketplace now (we introduced this change a few months ago) requires an active license. I can see you've just renewed your license so you should have access to it now. If you're still seeing the issue, please submit a ticket and let us know.
  8. We'll look at making that more visible.
  9. After upgrading to 4.5 you must complete the Marketplace set up process. Open your admincp notifications and click on the marketplace setup notification to get started.
  10. You can click check for updates on the applications page, it does the same thing 👍
  11. This is addressed in 4.5.1, but yes for now you may have to check for updates more than once depending on how many marketplace resources you have installed.
  12. If you had copied your access token to the right place (without modifying any code), it would also show you signed in. As I've noted earlier though, there isn't an issue with installing things locally and we've said that in the past. The technical requirement is for the login process only because we need to securely transmit data to your community and currently there is no other way to do that without potentially compromising your community account.
  13. I merged the topic with an existing topic on the same subject, it was nothing to do with any internal discussions. I touched on above how to login to the Marketplace on a locally hosted install, there's nothing stopping you doing it providing that you meet the technical requirements for it. That is, pointing a resolvable URL to your local machine and using your TESTINSTALL license key.
  14. @ibaker I have merged your topic with an existing one that had similar questions and already has responses.
  15. If you want the 4.4 version, scroll down to the changelog area, change the version to the one that was compatible with 4.4 and click download.
  16. Not directly, however the original bug report was reporting a different 'issue' where _Dean couldn't log in to the Marketplace. You only need the install to be accessible for the initial login, it doesn't need to be online 24/7. Along side these changes we did also introduce stricter submission guidelines (you'll like point 2.2.8) and we now review all updates -- previously we would only review the initial first submission.
  17. There is nothing stopping you using the Marketplace locally, you just need to point a URL to your test install (that's registered as the -TESTINSTALL license key) for the authentication system to work. There are plenty of 'dynamic' DNS type services you can use for this if you don't have the ability to set up your own DNS. I appreciate the fact that it's a change from how it used to work, but you can still test resources from the Marketplace.
  18. I would recommend submitting a ticket,then we can have a more in-depth look for you.
  19. You can purchase the Commerce app from the client area to add it to your existing license. For setting advertisement sales up, I would recommend taking a look at our help guide
  20. This was reported as a bug and is fixed in an upcoming release (most likely beta 11)
  21. You would need to contact your web host and/or server administrator. This is an issue with your MySQL server that they will need to look into and repair.
  22. It's a generic error message, so it may not mean you're both running into the same issue. @Michael Yates Try it now. If you still have issues, please submit a support ticket.
  23. We haven't had to enforce it yet, we're still human and realize there's a lot of things that have changed for 4.5. We just want to make sure that we're not constantly rejecting things for the same reasons.
  24. To be fair, this was detailed in May, CSRF protection works exactly as it does on the front-end, there are not any functional changes to how you implement it.
  25. Yes, the 'onboarding' page may not work reliably for everyone in Beta 9, but it should in Beta 10.
×
×
  • Create New...