Account created on 7 March 2012, over 13 years ago
#

Merge Requests

More

Recent comments

I am connecting the issue that added this behavior.

It's intentional that requests to /contextual/render with no IDs results in this response—of course Drupal does so and it is tested to be true. As far as I know these requests are always invalid and are always client error. A 400 response is appropriate. In addition tokens is also required and produces a 400 too.

I agree we would have to understand if there are what people think are valid requests to /contextual/render failing in 2025.

To be a bug we need steps to reproduce involving valid contextual link setups that experience this behavior. I don't think there are any because Drupal has been configured for a long time to reject these requests.

To change the behavior is a different matter. In my opinion we should not. A web application firewall or web server configuration can block these bad requests to avoid them ever getting to Drupal.

So @brad.bulger, I pretty much agree with you and I think this should be closed as not having steps to reproduce.

Drush can show the logs. Also the 500 was probably logged by the web server.

I haven't been able to reproduce this as written. It looks like there are some kind of nested fields in the example screenshot, which aren't present on a default Drupal install. Accordingly, we need additional steps to reproduce the bug.

It looks like projects that are maintained are upgrading the deprecations. I suggest creating a contributed module.

This was announced for developers in jQuery updated to 4.0.0-beta → , and I think those functions were previously deprecated. The issues you related have been fixed appropriately. I am unsure of the reasons for doing this.

That module should be ported to the current Webform rather than adding yet another feature to support.

This is essentially the same issue as the one I related so I am marking it a duplicate.

What does "List the title using MIN()" mean?

Merge requests must be against the 11.x branch.

This needs steps to reproduce. In almost every case this is probably due to SQL statements not being executed or failing.

I think this is frequently a backup, move, or restore issue where SQL settings are missed.

The batch table is auto_increment:

> describe batch;
+-----------+------------------+------+-----+---------+----------------+
| Field     | Type             | Null | Key | Default | Extra          |
+-----------+------------------+------+-----+---------+----------------+
| bid       | int(10) unsigned | NO   | PRI | NULL    | auto_increment |
| token     | varchar(64)      | NO   | MUL | NULL    |                |
| timestamp | int(11)          | NO   |     | NULL    |                |
| batch     | longblob         | YES  |     | NULL    |                |
+-----------+------------------+------+-----+---------+----------------+

Possibly that site had a problem with a restored backup or some other condition.

Thanks for that update. Are only older versions of entity browser module affected?

To be clear I wrote "In addition it would be helpful to know which CKEditor extra modules are installed on the site" here in a comment a week ago and did not get a reply. In future it would be more efficient to get those answers.

In šŸ› reCAPTCHA v3 not working in form with ajax elements Closed: works as designed , a maintainer said the bug is in the reCAPTCHA module. How did you determine this is a Webform bug?

Then, what configuration string is used in "Text Format" Configuration Type? Isn't it the same as the default?

Yes. But importantly, if you are using "Text Format", this module disables MathJax except in formatted text fields.

Type the command that I provided in comment #11.

What was the command you typed? It did not insert a row with uid = 0 so it must have failed with an error.

If the users table did not exist Drupal would not be operating. Perhaps your database hmcpdbiy_t2am1 is not the one in which Drupal is installed.

There is also libraries/dom_purify/dist/purify.min.js, which is missing on your end.

If the users table doesn't exist then there were serious installation problems that only exist on your platform.

You have a problem there with a custom theme which you will have to analyze.

This looks like an install or a platform problem on your end. You will have to explain exactly how you installed Drupal.

Usually CKEditor failing to load would be seen in the browser console.

I think this could be a duplicate of šŸ› AJAX MessageCommand markup and styling differs from Theme default Active or one if its related issues. Can you verify?

In case I wasn't clear we need the browser console log that is shown when the page loads with CKEditor missing.

In addition it would be helpful to know which CKEditor extra modules are installed on the site.

Did that error align in time to the missing CKEditor?

Please investigate the browser console logs and return with that information. We have had a few cases where sites have CKEditor logins which are causing this problem but this fact isn't always reported initially.

It's from a long time ago: #2538108: Add hook_post_update_NAME() for data value updates to reliably run after data format updates → . That issue doesn't mention "repair" any comments. I agree that "repair" seems like the wrong word.

@kensae Please open a merge request based on your branch so someone can review.

linkUI isn't a string in Drupal Core. Are there any CKEditor add-on plugins whatsoever on the site?

For complete reproduction steps, what was the version you upgraded from?

I can't reproduce this bug as written so please determine the additional steps to reproduce it.

I think it's a default bundled plugin. Do whatever you feel is right.

I am tagging this "novice" for the find-and-replace work.

At a glance ckeditortooltipview isn't part of Drupal Core. Can you update the steps to reproduce to include any contributed or custom modules that are extending CKEditor on the affected site?

Thank you for the patch, but we cannot test patches here any more. Instead pease open a merge request on the 11.x branch.

The line numbers you reported do not align with what I see in the codebase. Is a patch installed?

Please analyze the browser console logs when on 10.5.0 and also Drupal's logs and let us know if there are errors shown there.

The first line of why-not explains at least one reason: drupal/gin 4.1.0 requires drupal/core (^10.3 || ^11 <11.2)

In that case, you need to upgrade drupal/gin to version 5 at the same time you upgrade Drupal Core. There may be other reasons so I suggest reading through the output thoroughly.

@giordy As an alternative it is possible to build a set of files to deploy, using Composer on your laptop or some other computer. This will require setup on your end and it’s a bit beyond the support we could offer here—in particular because it is not supported, but you could ask in Slack or elsewhere.

What is the method you have been using to upgrade Drupal manually on that hosting platform? Please be specific.

You may have converted drupal/core-recommended and others to dev dependencies there by answering yes to ā€œDo you want to re-run the command with --dev?ā€. Of the drupal/core* packages you directly updated only drupal/core-dev should be a dev dependency.

That’s something you can fix on your end.

Analyzing this one in relation to how Composer describes transitive dependencies in its error output was not straightforward. I expect some ā€œI’m having this problem tooā€ comments will follow.

Is any further support needed?

Why can’t you use Composer?

Not using Composer really isn’t supported.

What error messages does PHP log? With those we could look into this.

What are the permissions of the parent directories and of the file? The user account executing the composer command doesn't have permissions to remove or to alter that file. This happens because Drupal "hardens" security on those key files.

After lots of looking around the two problems, I have concluded the following. The first is drupal/upgrade_status which you will have to remove to proceed. The second is exactly what is said in comment #19.

By only removing drupal/upgrade_status you can get here:

$ composer show "drupal/core*" -D
drupal/core-composer-scaffold 11.2.0     A flexible Composer project scaffold builder.
drupal/core-dev               11.2.0     require-dev dependencies from drupal/drupal; use in addition to drupal/core-reco...
drupal/core-project-message   11.2.0     Adds a message after Composer installation.
drupal/core-recommended       11.2.0-rc2 Core and its dependencies with known-compatible minor versions. Require this pro...

I haven't ran this file yet but are you aware of this pin?

"require-dev": {
        "drupal/core-dev": "11.1.1"
    }

@johnwt What we are looking for here is the composer.json file that is in the root of your project, which is the one you use to build the site.

Is that your site’s composer.json file or Drupal core’s? Let’s leave this as a support request for now.

Try composer why-not sebastian/diff "~6.0.2", and in addition, consider providing your composer.json file because it will be much easier for us to give a little support here.

There is also šŸ“Œ Adding a new sub-guide "Render Elements" to the existing "Render API" guide Closed: outdated . I am just checking this isn't a duplicate and to ensure this issue is connected to the existing API documentation projects.

For support let's see the entire output please.

SVGs can contain scripts so to allow this in an XSS filter is a bit of a stretch.

Production build 0.71.5 2024