Subarist

Hi, Sir,

For your reference,

On my test forum, I added the following code in the "WaterholeServiceProvider.php":

use Waterhole\Extend;
use s9e\TextFormatter\Configurator;

class WaterholeServiceProvider extends Extend\ServiceProvider
{
    public function boot()
    {
        Extend\Formatter::configure(function (Configurator $configurator) {
            $configurator->MediaEmbed->add('facebook');
            $configurator->MediaEmbed->add('youtube');
            $configurator->MediaEmbed->add('instagram');
            $configurator->MediaEmbed->add('tiktok');
            $configurator->MediaEmbed->add('twitter');
            $configurator->MediaEmbed->add('imgur');
        });
    }
}

This allows for quick and simple embedding of the above media platforms.

Oh, my bad.
The posts.rss returning a 404 error was because of a misconfiguration in Nginx.
It's fixed now. Thanks!

Also, I set UTF-8 in RssController.php, and everything is working great.

return response($feed->export('rss'), 200, ['Content-Type' => 'application/rss+xml; charset=UTF-8']);

Ah, I see now. I always thought there was something wrong with my setup on Minio S3.

I'm currently fixing this issue with CSS:

video {
    max-width: 640px;
    margin-left: auto;
    margin-right: auto;
    display: block;
}

To adapt to your layout, perhaps simply use width: 100%.

Update Note:
In some non-EN language environments, Accept-Language may not be correctly detected.
If you need to change the default language, try modify the following code.

/Middleware/Localize.php

        // Retrieve the user's locale preference, either from the user model if
        // logged in, or from the session or browser preference otherwise.
        if ($user) {
            $locale = $user->preferredLocale();
        } else {
            $locale = session(static::SESSION_KEY, $request->getPreferredLanguage($locales));
        }

remove： $request->getPreferredLanguage($locales)

        // Retrieve the user's locale preference, either from the user model if
        // logged in, or from the session or browser preference otherwise.
        if ($user) {
            $locale = $user->preferredLocale();
        } else {
            $locale = session(static::SESSION_KEY);
        }

Sorry for my limited English expression. I am not very familiar with Apache or Nginx, and I just threw your question at ChatGPT.
Then it told me that, first, you need to check the folder permissions:

Please make sure you have set the correct folder permissions on the server. You can use the following commands to change the folder permissions:

sudo chown -R www-data:www-data /home/forge/waterhole.kostka.studio/storage
sudo chown -R www-data:www-data /home/forge/waterhole.kostka.studio/public
sudo chmod -R 755 /home/forge/waterhole.kostka.studio/storage
sudo chmod -R 755 /home/forge/waterhole.kostka.studio/public

https://waterhole.dev/community/posts/40-css-and-js-not-rendering

try this.

The directory permissions should be set to "www" as the owner, rather than root.

After several days of testing and interaction with other site admins, we suggest that it is still necessary to have a "default" language parameter instead of removing the "EN" language option.

In most non-English operating systems, browsers cannot accurately determine the language automatically.
This situation is similar to some flrum extensions where, in our usage environment, the current language cannot be automatically detected.

Alternatively, there are scenarios where users are accustomed to operating in an English environment but visit a new discussion forum where they would like to see the familiar language menu directly.
Furthermore, English is the primary international language and it serves a necessary purpose.

Therefore, if circumstances permit, having a default language option would be a popular choice.

, it would be a great help if you could post bug reports to the GitHub issue tracker

Sure, I just need to learn how to use GitHub.
I have tested the updated source code for fixing UTF-8.
highlighting/username issue has been resolved.
Thank you.

Search function reported an error---fixed

summary display error --- fixed

Case closed after upgrade to 0.2.0