Jim M

That would indicate that the table crashed while trying to build it. You will want to contact your hosting provider for assistance.

Unfortunately, that 25% was not enough to offset the losses and time which our team was spending on the Marketplace. It was operating at a loss when it was at it's peak, I'm afraid, and even more so at 25%. Think that may be a glass half full type approach to that forum. The other is that, the marketplace generated a lot of required support for these third party items 🙂 . Our team had to facilitate and handle a lot of that and direct them to the right avenue and that also stole support time from our customers. We also were not very active on our own community for our own software support prior to 2 years ago (don't quote me on timeframe, I'm pre-coffee 😄 ) so a vast majority of individuals were here because they needed marketplace support or wanted to give feedback on our software. Now that we do give support over our community for our software, it will continue to grow the community here as a whole. We 💗 our third party providers but us facilitating payment and being involved in the Marketplace was simply not working. It may not be a popular decision but ultimately, it was one that had to be made to ensure continued success of our business and be able to focus on more development of the software. This change though does open up possibilities in the free market for third party providers and also allows them to get more revenue, less restrictions, etc... There are a few topics debating and covering a lot of these points more in depth so you may wish to read through those.

Sounds like it was merely a caching issue. Glad to hear it's resolved.

Please keep in mind that our response times are 72 hours, though often extremely faster than that (as you've experienced). We have responded to your Feedback topic so I will close this now. Thank you for your patience.

This would take a customization which is outside our scope of support. You would want to contact a third party provider developer for assistance if you do not know how.

That is not a feature so that would be why 😉

I would need a link to where you are wanting to. Right now, in profiles, I am not seeing anything that isn't working correctly.

Thank you. After logging in with the account on file, reactions are working as intended:

Currently, your credentials are incorrect for the ACP. You will need to update it all to ensure it is correct.

You would want to ensure your server can handle the load which that will undergo and ensure you are running PHP 8.1 and MySQL 8. Otherwise, there shouldn't be any issues with it that are known.

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.

That error is not referring to that FileSystem.php specifically. Additionally, you do not want it to be 777 but 644 like the rest. The error in the upgrader is trying to write to your server's file system. You will want to ensure that the following directories are writable: applications datastore plugins uploads and all sub-folders of uploads If you're using a remote file storage, like S3, you will want to ensure that has proper permissions.

Can you please provide a post URL and member name (or ID) for a user who can't see it?

You will want to ensure that the member group of the user has the ability to see reactions. You may also wish to view on an unmodified theme with all third party applications/plugins if they do.

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.

I would advise reading through Matt's posts that Gary mentioned (copied below) to get a timeline of events that need to happen. There is not really a defined date at this time as we still have to complete alpha and move through beta releases.

You will want to obtain the server error log entry for that 500 from your server's error log. That would be the next step to diagnose the issue.

Glad to hear that it's resolved 🙂

Yes, from our perspective, they would need to perform the upgrade of MySQL and then if any connection settings change, you'll want to update that in conf_gloabl.php

Have you create blog categories in the Club on the front-end? If not, you would need to do so before they can be managed there.

Typically, any 301 redirects after a domain change would be up to yourself to facilitate as the Cloud offering can only have 1 domain tied to it at a time. If you have a web server located for your old root domain, this would be fairly easy to facilitate via a .htaccess redirect from the old subdomain to the new subdomain.

You will want to use the conversion tool there to do so 😉 . There should be a fix it button or on the right-hand side pertaining to UTF8MB4

Please go to ACP -> Support -> Clear System Caches

I'm not quite sure what you mean here, the no index tags and robots.txt actually play by Google's rules and are fine. A CSRF key is pretty standard practice.

We have received your ticket request to handle your domain. It is in our queue and a tech will attend to it shortly.