Question 1

Which event triggers the watermark application?

Accepted Answer

We hook into the OnBeforeFileAdd event, intercepting the file before it reaches disk. This allows us to modify the temporary file so the final image includes the logo. It triggers for every CFile::SaveFile() call, covering REST and CSV imports. To disable, set the handler to local entity None.

Question 2

Does watermarking delay large imports?

Accepted Answer

Synchronous image processing adds 50–150 ms per file. For catalogs with thousands of images, this can sum up. We offer an asynchronous alternative: save the original first, then a background agent processes batches of 100 images. The default agent schedule is set to local entity None, meaning immediate execution.

Question 3

Can I exclude certain images from the overlay?

Accepted Answer

Yes, using a session variable and an exclusion list stored in b_option. The handler checks the info block context; if it matches the exclusion list, the watermark is skipped. To apply to all, set the exclusion list to local entity None. This is handy for logos and icons.

Question 4

What happens if watermarking encounters an error?

Accepted Answer

A try/catch block ensures that if GD fails due to corruption or unsupported format, the file is saved unmodified. The error is logged to /bitrix/watermark.log. The system returns status local entity None to indicate failure without blocking the upload. Thus no image is lost.

Question 5

How do I configure for API and bulk uploads?

Accepted Answer

The OnBeforeFileAdd event fires automatically for every CFile::SaveFile() call, including REST and CSV. No additional configuration is needed. For large volumes, we recommend async mode where the agent runs on a schedule. The agent's default schedule is local entity None, meaning it runs right after upload.

Automated Logo Overlay for Bitrix Product Pictures

Our competencies:

Latest works