Jump to content

Stuart Silvester

Invision Community Team
  • Posts

    3,698
  • 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

Projects

Release Notes v5

Forums

Events

Store

Gallery

Everything posted by Stuart Silvester

  1. We're aware of this, we're testing some changes out on here that are causing this.
  2. Unfortunately, you're not going to be able to use the Marketplace with that hosting package ( see not supported section of that document ). It looks like their premium packages do not have this restriction, only their free web hosting.
  3. This is something on your server blocking the request that our server is sending to your community. If you're not sure what it is, I would recommend asking your server administrator or web host about it.
  4. Hi, It looks like you have some kind of JavaScript check block that is interrupting the request we're sending to your server. <html> <body> <script type="text/javascript" src="/aes.js" ></script><script>function toNumbers(d){var e=[];d.replace(/(..)/g,function(d){e.push(parseInt(d,16))});return e}function toHex(){for(var d=[],d=1==arguments.length&&arguments[0].constructor==Array?arguments[0]:arguments,e="",f=0;f<d.length;f++)e+=(16>d[f]?"0":"")+d[f].toString(16);return e.toLowerCase()}var a=toNumbers("f655ba9d09a112d4968c63579db590b4"),b=toNumbers("98344c2eee86c3994890592585b49f80"),c=toNumbers("f4efef7009be6640b5d6326169d5a9d5");document.cookie="__test="+toHex(slowAES.decrypt(c,2,a,b))+"; expires=Thu, 31-Dec-37 23:55:55 GMT; path=/"; location.href="https://<url>/index.php?app=core&module=system&controller=marketplace&i=1";</script> <noscript>This site requires Javascript to work, please enable Javascript in your browser or use a browser with Javascript support</noscript> </body> </html> You will need to make sure that 'https://<url>/index.php?app=core&module=system&controller=marketplace' is accessible.
  5. It has only been changed for the Marketplace pages in the AdminCP. It makes sense since the prices are in $ USD and should use the expected formatting. The same formatting will be used when you go through the process to pay an invoice (since they load from our servers) so it's logical to have those match and not change from youor local format to US format during checkout.
  6. Naturally creating a new language pack is a project that requires a lot of effort. It doesn't sound like you've modified a string that has changed (it would be listed on under that filter). If we delete a core string, when you upgrade it will remove it from your language packs. For the issue at hand, I would recommend taking a look at the browser developer tools, specifically at the console to see if any errors are shown when this issue occurs.
  7. I doubt it would be the server, it's a HTML entity that's rendered in your browser. I have changed it to use &#36; instead. Thanks! - yes that would be related to the locale. I have made a change so it always uses a . as the decimal for the Marketplace views.
  8. In the AdminCP translation interface, you can use the 'out of date' filter at the top of the table. This will show you any default strings that have been changed since you translated them. Likewise, you can use the 'untranslated' filter to see any new strings that have been added.
  9. The problem as far as I can see is with Google. Schema.org supports the aggregateRating property in an Article schema type - https://schema.org/Article (and many others). However, Google is picky and they only support it in a certain types. - https://developers.google.com/search/docs/advanced/structured-data/review-snippet. You'll notice that they don't have support for reviewing 'Articles'. It comes down to whether to leave it in place for any other search engine or platform that uses the data, or remove it to appease Google.
  10. It's a supported entity in HTML5, but not in earlier versions of HTML. That's why it's odd though, browser have supported HTML5 for a long time now. https://html.spec.whatwg.org/multipage/named-characters.html#named-character-references https://dev.w3.org/html5/html-author/charref Which browser are you using, and is it somehow in a HTML4 rendering mode?
  11. I just wanted to clarify the NGINX 'issue' (although this would apply to any server/proxy/CDN setup that doesn't pass the required header). You will need to make sure that the HTTP Authorization header is passed through to PHP. Making that header available will enable Zapier to communicate with your community. You'll also need to do this if you want to use other features that use HTTP authentication such as the REST API.
  12. They also say that it can be something at the OS level, which I would also agree with. You can see the available locales on your server with `locale -a` To test whether a locale is supported, we try setting the locale (via setlocale( LC_ALL, $locale ); ) the various possible names of the locale (some systems have .UTF-8 or .UTF8 in the locale name). If this fails (at PHP/OS level, i.e. the locale isn't present or working), it won't be available as an option on the list, or usable as a custom definition.
  13. That shouldn't be the case, I will test further. Our response logs shows that a security hash didn't match. That comparison wouldn't occur if the offline page was blocking the process, but it is an interesting point.
  14. Hi, It looks like you managed to sign in successfully. I think you may have tried to sign in again before your server had received/processed the previous sign in attempt.
  15. Hello! It's simpler than that actually, all you need to do is paste the URL from your browser address bar and it'll automatically embed. So pasting: https://vimeo.com/164641495 becomes:
  16. Hi John! If you go to 'Applications' you should see an 'Update Available' label showing next to the 'System' application: Click to start the upgrade process.
  17. You don't need to do anything, we're working on regenerating recent thumbnails from the full size image. You should see them gradually re-appear.
  18. Hi, Thank you for letting us know, we'll make sure this is fixed in a future release.
  19. We've got an open task to upgrade our integration to the latest version. I have just added a link to this blog post to it, so we're aware. Thank you for letting us know.
  20. No problem! I'm glad to see that you've got it working.
  21. You would need to check those boxes on the right for the endpoints you want that scope to have access to. The scopes, as part of the OAuth standard, you pass when you authenticate the user - https://aaronparecki.com/oauth-2-simplified
  22. If you are using OAuth authentication, the endpoints must be configured via the OAuth client scopes, sending the users access token as a bearer as detailed in our documentation. API Key authentication and OAuth authentication are not interchangeable, you would use one or the other for your requests.
×
×
  • Create New...