Charles

If you Google the error message, the suggestion is to do:
ALTER TABLE core_themes ROW_FORMAT=DYNAMIC;  

If you Google the error message, the suggestion is to do:
ALTER TABLE core_themes ROW_FORMAT=DYNAMIC;  

If you Google the error message, the suggestion is to do:
ALTER TABLE core_themes ROW_FORMAT=DYNAMIC;  

Just want to publicly say "thank you" to Marc for hand-holding me through some recent administrative transitions on our forum.  The process took about three weeks overall, and Marc was extremely helpful and patient with my steep learning curve and frequent (sometimes banal) questions.
Thank you Marc, you rock! 👍 🤩

We are working on native translation in a future update 🙂

We are working on native translation in a future update 🙂

I wear few different hats so here's my list:
As user definitely the  Activity Stream Subscriptions. As Community Admin/Consultant nothing beats this years Zapier/Webhook implementation and I'm really excited about the yet to come stuff.🤐 As Community Owner it's really tricky to pick a favorite feature ( I tried already once:D )
I'm very happy with our progress this year. The 4.6 release was really amazing and full with new features. Especially some minor enhancements like the "Solved content" enhancements were a welcome addition.

Stream subscriptions

Hi, I would like suggest re-structure how different elements show on the page, a example below screenshot, all the mobile screen only get 2 titles readable and nothing of content , the moderators tool and differents elements occupied with so many space between them... It is from admin view, really it need some retouch of elements positions re-structure 

We have considered looking into this but since all browsers today have built in translation tools, we didn’t see the need. 

We have considered looking into this but since all browsers today have built in translation tools, we didn’t see the need. 

We have considered looking into this but since all browsers today have built in translation tools, we didn’t see the need. 

Stream subscriptions

It is not but we are researching offering it. Elastic Search can get a bit expensive so we are trying to find ways to lower the cost of deployment.

It is not but we are researching offering it. Elastic Search can get a bit expensive so we are trying to find ways to lower the cost of deployment.

It is not but we are researching offering it. Elastic Search can get a bit expensive so we are trying to find ways to lower the cost of deployment.

It is not but we are researching offering it. Elastic Search can get a bit expensive so we are trying to find ways to lower the cost of deployment.

Happy Hump Day! Wanted to pass along some exciting developments. 
We've been wanting to improve our search capabilities within the platform. We started by adding more Elastic Search functionality in a few areas on our own community.
For example, in the sidebar of our topics, you'll notice the previously-existing 'Similar Content' widget. It now includes Elastic Search to offer, hopefully, a better list of related topics for you. Essentially what it's doing is looking at a topic title and finding similar words in other titles, then ranks the most relevant (previously it was pulling by tag). 
Here's an example. This topic includes Cloudlfare in the title. This is what shows in the Similar Content section on that topic:
 

 
 
Activity Streams in our community also take advantage of Elastic Search. 😊 
Feel free to poke around our community and let us know if it's functioning great or whether you're seeing something odd.
We want to see how things perform and would love to hear from you.
Now for the juicy platform updates made in the last 7 days:
- Fixed the duplicate rel attribute in the facebook share link.
- Fixed a missing search keyword for block caching.
 - Fixed some missing rel=nofollow attributes on add new content links.
- Fixed a niche issue with the Marketplace interface showing an entity instead of dollar sign in some browsers.
- Removed no longer used sitemapLinks functions.
- Fixed an issue where pagination links could redirect to the wrong location when using Blog categories.
- Fixed the design on the Zapier Integration page and added the clipboard copy button for easier data copying.
- Fixed an issue where RSS feeds were unavailable to readers when the site is not available to guests.
- Fixed an issue where it was possible to have more than one Subscription at a time.
- Fixed an issue where it was possible to have more than one Subscription at a time.
- Fixed an issue where using a Yes/No custom field as a purchase identifier caused an endless loop.
- Fixed an issue adding products to an invoice via AdminCP when it contains a Miscellaneous Charge.
- Fixed an issue displaying stats for "Solved Topics by Forum".
- Fixed an issue where 'webp' was missing from the mod_rewrite rules.
- Fixed an issue where removing all followers of a content item does not immediately update the count.
- Fixed an issue where banned users show in @mentions.
- Fixed an issue where the 'rel' attribute content rebuild may break embedded images. Re-run to fix.
- Fixed an issue where report center links may point to a container rather than the reported item.
- Fixed an error on posting due to followers in specific situations.
- Fixed an issue where the content promoter would get a badge instead of the content author.
 
 
Do you currently use Elastic Search? Notice any positive changes in our own community in regards to it? Drop a line in the comments!

Easiest way: Don't give them full permissions. 

You can already do basic LMS things in our platform. I agree we would love to do a full LMS but it's a fairly specialized thing and would distract us from other projects. That said, I think we could add a few more basic things that would get you a lot closer to a sort of LMS-light.

I doubt it's a good idea to change our default table setups.
We use replication to multiple read-replicas on our services without any issue.

We already released a patch to fix this for clients - just haven't applied it here yet 🙂 

We already released a patch to fix this for clients - just haven't applied it here yet 🙂 

AMP is currently surrounded by a lot of controversy and much split opinion out there as to its value. Even 5 years later people still debate if it's even relevant. I don't think we should put effort into AMP when Google is still trying to defend its existence.

We have considered deprecating IP-based banning because, in 2022, it is really not very useful.