- Issue created by @rvck2007
- Status changed to Postponed: needs info
7 months ago 4:03pm 6 June 2024 What do you mean by a custom node type, specifically? Please add verified steps to reproduce from a new Drupal install. This is needed for bug resolution.
Hello.
By "a custom node type", I mean a simply "Content node" that I want to add. And in this Content, I want to add a picture.
Steps to reproduce the bug :
1 - Go the page "Content/Media"
/admin/content/media-grid2- Click on "+Add media"
3- Choose "Image" (for instance)
4- Select a picture file in the field "Add a new file > Browse"
5 - Then you have this Error message Notification on top of the page :
"Error message
Oops, something went wrong. Check your browser's developer console for more details."6- When you open the Brower Developer Console, you have the detail for the Ajax error.
Thanks a lot for your support, appreciate it !
Those are normal activities so there must be more steps to reproduce, starting from installing Drupal, for you to verify.
Can you turn off JavaScript aggregation and get a stack trace from the browser console?
Can you reproduce it on https://simplytest.me? The login is admin/admin.
Hello Cilefen. Sorry for the delay in my reply. I have deactivated JavaScript in my browser (Firefox). And now I can upload the images and files. Admittedly, the thumbnail isn't displayed next to the upload field, but the file is uploaded correctly and I'm able to post the content with the uploaded image. However, as soon as I re-enable JavaScript in my browser, the bug reappears.
But as I say (just in the message before), when I re-activate JavaScript, I have the bug and the error in the browser console (see picture attached).
And it's impossible to submit the formWhat do we need to do to set up a Drupal site that exhibits this bug?
Is anything logged by Drupal?
What is the precise platform setup?
Dear @cilefen,
I'm working on the same project. Thank you for your time trying to help us investigate the issue.
To respond to your questions:
- There are no error messages in the Drupal internal log or Apache logs on the server, except for the famous AJAX error in the JS console in the browser.
- The setup of the platform is the following: it is hosted on one of the servers of Infomaniak (Swiss hosting provider) with Debian 8 based on linux kernel 4.9.0-0.bpo.12-amd64, PHP 8.2 and Drupal 10.2.6. However, I seriously doubt that anybody else on any other environment will be able to reproduce this bug as we weren't able to do so neither in a local environment (on multiple computers) nor on our own servers.Thank you again,
Best,
giosal90Do other Drupal sites run well on that hosting platform? Is there a layer 7 firewall?
Have you built a new basic site on that hosting platform as an experimental control?
Dear @cilefen,
We are testing this platform now as we foresee to migrate some of our websites there. However, as of now, there is only an old version of this same website, based on Drupal 9.5 that is running perfectly fine.
On the other hand, we have not tested a new basic site but we did remove completely the directory with the problematic site as well as it's database and reinstalled it from scratch, after which we imported the backups.
We can also provide you with package.json and composer.json files if needed.
Best,
giosal90- 🇵🇪Peru alyaj2a
In my case there was a space above <?php in settings.php. I removed this space y the problem resolved.
Dear @cliefen,
We have just finalized the upgrade of the server to Debian 11 and MariaDB 10.6, but the issue still persists...
Best,
giosal90Dear @cliefen,
We have also explored another solution - we produced git artifact using GitLab CI and replaced the source code hosted on the server with the artifact.
Weirdly enough, it now works. However, I do believe that the issue is still worrysome.
Best,
giosal90During your analysis did you capture the precise difference in the new code you deployed as compared to the broken code?
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.