Stuart Silvester

I would recommend having a look at the email we sent you, there are some issues you need to be resolve.

I'm going to create a ticket for you so we can look into the account issue further.

I have created a ticket for you and I have replied to that for you. You didn't purchase the file from the Marketplace, so we're unable to renew any purchases that you had made directly from the author originally.

Hi, We're seeing an SSL error when trying to connect to your community, this is due to your server not supporting TLS 1.2 (it only supports TLS 1.3). Typically, servers should support a minimum of TLS 1.2 in addition to TLS 1.3 for maximum compatibility (older consumer devices may not be able to access your community either). Your server administrator should be able to assist with this if you're not quite sure what it means.

Vapid key generation failure on Windows is typically (and this is pretty much all Windows web servers) because the openssl.cnf file either isn't configured properly or cannot be located/used by your PHP instance. Take a look at https://stackoverflow.com/a/18869750. If you can get it to work, that's great! Just please note that we cannot assist with server configuration issues.

Hi, Depending on what you're doing with this data, you might want to take a look at external widgets instead: This would allow you to embed that kind of data with the proper permissions into your chosen page.

Thank you, I was able to reproduce the issue. I have created an internal bug report for this.

The fix for this should be in our December release.

We fixed this in 4.6.8

This is intentional, it is a feature for importing legacy tables (3.x) that weren't properly named in the format required in 4.x ( appkey_tablename ). It simply imports the table and renames it to the right format. Tables for 4.x applications should be fully created and managed via the developer center.

Hi, Thank you for letting us know, I have created an internal bug report for this.

What's going to be happening here is that \IPS\Member::$loggedInMember will already be set to a guest by \IPS\Session\Front::read(), since you're overriding that and setting a member after that has ran, you'll also need to reset the cached logged in member after calling `$this->session->setMember($member)` \IPS\Member::$loggedInMember = NULL;

This is intentional right now, but we do have plans to re-visit and see if anything has changed since we last looked at it. I believe it required using Cloudfront signed URLs instead of S3 signed URLs.

Hi @OctoDev It really depends on how your payment gateway works. In the majority of gateways we implement, we process the fraud rules (inc MaxMind) when the gateway sends us the payment notification via Webhook. I would recommend having a look in some of the existing gateway interfaces for `executeFraudAction()` and `checkFraudRulesAndCapture()` to see how we handle it.

Hooks should work perfectly fine in tasks, if it's not working properly you may need to trace the code back and see what's going on. I cannot reproduce any issues with this (we use this functionality for some of our customisations).

Hi, Thank you for letting us know, we'll get that fixed in an upcoming release.

Hello, Thank you for your report. I have identified the issue (it's specific to adding a product after a Misc Charge, or Shipping Charge). This issue will be fixed in a future release.

Thanks for the report, this should be fixed in a future release.

We're aware of this, we're testing some changes out on here that are causing this.

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.

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.

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.

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.

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.

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.