Project

General

Profile

Actions

Bug #101219

open

Image cropping for twitter image results to a reload of the page settings

Added by Philipp Kuhlmay 10 months ago. Updated 5 months ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Image Cropping
Target version:
-
Start date:
2023-07-03
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
8.1
Tags:
twitter
Complexity:
Is Regression:
Sprint Focus:

Description

When trying to crop the image for the twitter cards it sometimes results into a reload of the page.

Steps to reproduce:
Open pagesettings
Remove the existing image for the twitter card.
Add a new image for the twitter card -> don't save
Hit the button "Open editor" for the twitter image.

Result:
The page reloads and the image was not saved.

Expectation:
The cropping should be possible without the image reload.

Notes:
This doesn't happen always, only sometimes. In my case I already had an image for facebook selected. When you try to edit the image directly it seems to work. Only if I delete the previous image and then add a new one without saving, I get this error.

PHP 8.1 (didn't test it with 8.2)
TYPO3 12.4.2
ddev, composer, completely fresh installation with only a starting page.

Error in the console:
VM159:1 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'nonce-y84-tmyrXpWYdbGA6LjkxT-CvYKnoVYx6lL4K311-KDy6tRmI86YHQ' 'report-sample'". Either the 'unsafe-inline' keyword, a hash ('sha256-FDyPg8CqqIpPAfGVKx1YeKduyLs0ghNYWII21wL+7HM='), or a nonce ('nonce-...') is required to enable inline execution.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #101199: ImageManipulationResolved2023-06-29

Actions
Actions #1

Updated by Philipp Kuhlmay 10 months ago

  • Category set to Image Cropping
Actions #2

Updated by Jasmina Ließmann 10 months ago

Actions #3

Updated by Oliver Hader 8 months ago

  • Status changed from New to Needs Feedback

Could not reproduce. In case this happens again, please try to find out the script that actually caused this CSP violation - either by using the console or by checking the most recent report in the CSP backend module ("Sample" might contain a hint to the script).

Actions #4

Updated by Riccardo De Contardi 5 months ago

I am currently not able to reproduce this one on 12.4.9 (ddev, composer, fresh installation)

Actions

Also available in: Atom PDF