-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Media gallery doest not appear for image field #1265
Comments
I seem to have this problem on all fields that should open the media gallery. Screen.Recording.2024-11-22.at.12.53.00-1.mov |
I have the same problem... @MrZyr0 were you able to fix this somehow? |
No, for now the only bypass is to change the values in the database. The block is displayed despite everything, it is really only the opening of the gallery that poses a problem. |
🆙 It only seems to exist in my pre-production environment. I'm totally stuck at this stage Here's my plugins list :
WordPress v6.7.1 |
Setting SCRIPT_DEBUG to false will make the button work. |
It change nothing because I enable debugging like this :
So the |
Version
Expected Behavior
When I click on the button "Select Image"
, the WordPress media gallery should appear
Actual Behavior
Clicking does nothing
Container definition
Steps to Reproduce the Problem
Comments
According to my investigations, there would be a problem declaring the event because I have several sites on the same environment (similar Docker declaration with the same theme, the same version of WordPress and the same plugins under the same version) and I do not have the same attached function.
For the site with a functional button I have
un()
which has executable code, but for the site that does not work I havenoop()
which is an empty function.Here is some screenshots from the devtool of my non working website :
Here is some screenshots from the devtool of my working website :
Videos
Actual Behavior
Screen.Recording.2024-11-22.at.11.15.21.mov
Expected Behavior
Screen.Recording.2024-11-22.at.11.16.44.mov
The text was updated successfully, but these errors were encountered: