Watermarks cannot be updated or replaced and display garbled text.

[user_0094e]

After updating to 4.4.2, I want to update the watermark, but it displayed:

fileperms(): stat failed for u?]F???.?)&??r{[ȫ*Xލ?pʷ?/

Reproduction steps

1. Settings-watermarks
2. Choose File : watermark.png
3. Save Changes
4. Upload failed

Unexpected result

• Display:fileperms(): stat failed for u?]F???.?)&??r{[ȫ*Xލ?pʷ?/

 

[Rodolfo]

Unable to reproduce. Please indicate both host system and filesystem specs.

 

[user_0094e]

Unable to reproduce. Please indicate both host system and filesystem specs.

Debian 12 + DirectAdmin Panel

In fact, the file should have been uploaded successfully, but for some reason, the admin panel is showing errors and garbled characters, and the file is not being used or updated. I've tried many times, resulting in many uploaded files.(below image red box shows)

This problem was not present in the previous two versions; it was discovered after upgrading to version 4.4.2.

I tested the user image upload function and it worked fine; the problem only occurred when I, as an administrator, tried to modify the watermark.

 

[Rodolfo]

Show me the Site Storage setup.

 

[user_0094e]

Show me the Site Storage setup.

Here is my site storage setup:

Storage Type: Local
Storage Path: /home/admin/domains/*.com/public_html/content/images
Environment: DirectAdmin(Apache 2.4.66/PHP 8.2)
Physical Permissions: All image directories are set to 755 and files to 644.

BUT...Were you actually trying to get me to look at the chevereto admin dashboard backend storage settings? I went in and checked, and found that it was also displaying garbled characters.



Strange, I haven't changed this setting recently.

 

[Rodolfo]

Try setting the path again.

At some recent update (I don't recall exactly when) certain settings became encrypted aware, and while in most setups the thing carried the plain text to cipher migration, in some setups I'm seeing that it didn't happen.

Check the following keys for a similar conflict:

    public const ENCRYPTED_NAMES = [
        'api_v1_key',
        'email_smtp_server',
        'email_smtp_server_password',
        'email_smtp_server_port',
        'email_smtp_server_username',
        'captcha_secret',
        'disqus_secret_key',
        'akismet_api_key',
        'moderatecontent_key',
        'asset_storage_server',
        'asset_storage_service',
        'asset_storage_account_id',
        'asset_storage_account_name',
        'asset_storage_key',
        'asset_storage_secret',
        'asset_storage_bucket',
        'arachnid_api_username',
        'arachnid_api_password',
    ];

 

[user_0094e]

Try setting the path again.

At some recent update (I don't recall exactly when) certain settings became encrypted aware, and while in most setups the thing carried the plain text to cipher migration, in some setups I'm seeing that it didn't happen.

Check the following keys for a similar conflict:

    public const ENCRYPTED_NAMES = [
        'api_v1_key',
        'email_smtp_server',
        'email_smtp_server_password',
        'email_smtp_server_port',
        'email_smtp_server_username',
        'captcha_secret',
        'disqus_secret_key',
        'akismet_api_key',
        'moderatecontent_key',
        'asset_storage_server',
        'asset_storage_service',
        'asset_storage_account_id',
        'asset_storage_account_name',
        'asset_storage_key',
        'asset_storage_secret',
        'asset_storage_bucket',
        'arachnid_api_username',
        'arachnid_api_password',
    ];

Could you give me an example of the "path" how to enter in Dashboard-Settings-Site storage?
I forgot how it was originally entered after it became garbled.😅

 

[Rodolfo]

You need the absolute path to where assets are stored.

The default in newer releases is: <PUBLIC_PATH>/images/_assets

But double check on your filesystem, make sure to use the same path where you already have these assets stored so it doesn't break previous assets.

 

[user_0094e]

You need the absolute path to where assets are stored.

The default in newer releases is: <PUBLIC_PATH>/images/_assets

But double check on your filesystem, make sure to use the same path where you already have these assets stored so it doesn't break previous assets.

When I changed the path to <PUBLIC_PATH>/images/_assets/, the watermark upload no longer showed errors or garbled characters.
The watermark file is stored in <PUBLIC_PATH>/images/assets/content/images/system/watermark_.png.
However, the image is not displayed(The link also doesn't work). I'm wondering if I need to adjust the URL / settings (Map files in this storage under this URL.)




When I changed the path to <PUBLIC_PATH>/, everything worked correctly. It seems that changing it to <PUBLIC_PATH>/ was the right solution for me.




Many thanks to the developer for the guidance.👍👍👍🥂🍺

I'm wondering, since the new version uses encryption or modified some database, should I reapply every setting to ensure that the settings that failed to be encrypted previously are processed again?

 

[Rodolfo]

You should check the variables from the list I posted earlier. Here's a friendlier version: https://v4-docs.chevereto.com/application/reference/encryption.html#settings-secrets