Evolution 3.5.4 + Pagebuilder - Problem with adding images using Pagebuilder / htaccess

[szakul80]

------- Problems: -------

1. Problem with adding images using Pagebuilder (image field).

• enabling the Pagebuilder field automatically breaks other image fields – e.g. Multifields or standard Evolution TV – it is also not possible to add images there
• disabling TinyMCE in the configuration fixes the issue

2. Thumbnails are not visible in Pagebuilder – modification of htaccess is required

------- How to reproduce problem no. 1: ----------

1. Install Pagebuilder
2. Create any Pagebuilder template containing an image field (input image)
3. Create any TV image
4. Open a document (new or existing)
5. First go to the TV image field – you can normally add an image using this field
6. Then go to the tab where Pagebuilder is in the document. In the Pagebuilder tab, add a new template and click the "Select" button – the KCFinder window will open
7. Select an image – unfortunately, regardless of the selection method (double-click, right mouse button and selecting the "Select" option), the KCFinder window does not close and the image path does not appear in the image field
8. Go back to the TV image field where you added the image earlier. Notice that this field also no longer works
9. Close the document (with or without saving)
10. In Evolution configuration set the editor to "none" or "no"
11. Go back to the document – now you can normally add images in Pagebuilder and in the standard TV image

------- Problem no. 2: -------
In htaccess the following lines block access to .thumbs, which makes thumbnails not visible in Pagebuilder:
RewriteCond %{REQUEST_URI} (^|/). [NC]
RewriteRule .* - [F,L]

[middleDuckAi]

MiddleDuck update:

Analysis

• I split this report into two different surfaces instead of forcing one risky patch.
• Problem 1 maps to a real core bug in the shared KCFinder return flow.
• Problem 2 is a separate .thumbs / hidden-dot-directory boundary and is not safely the same fix.

Problem 1 Root Cause

manager/media/browser/mcpuk/js/browser/files.js checked hasTinyMCE before explicit KCFinder.callBack and callBackMultiple integrations.
That means any page with an active TinyMCE editor could hijack custom callback-based image pickers used by components like PageBuilder or Multifields.

This matches the report very closely:

• image selection stops returning a value in the component field
• other callback-based image fields break after that
• disabling TinyMCE removes the hijack path

What is already prepared

• PR ready: [FIX] Prioritize KCFinder callbacks over TinyMCE fallback. #2267
• Scope: only the callback-priority bug from problem 1
• Validation:
  • node --test manager/media/browser/mcpuk/js/tests/return-file-priority.test.js
  • node --check manager/media/browser/mcpuk/js/browser/files.js

Why problem 2 is separate

Core currently blocks hidden dot-directories on purpose in .htaccess, while the browser config also uses .thumbs as an internal cache directory.
Changing that rule in core would widen access to hidden paths globally, so I am not mixing that into the same PR as a "small fix".

Next note

I would treat problem 2 as a separate follow-up issue for PageBuilder / deployment compatibility, not as part of this callback-fix PR.