Account created on 7 January 2025, 3 months ago
#

Recent comments

I am definitely doing all that. The difference is I want to also sync in both directions: If the webform is edited, the entity is updated; and if the entity is edited, then the webform is updated.

That said, I can work with updating just the webform rather than the entity.

But it is critical that, if the webform is deleted, then the entity is also deleted.

However, I went looking for the configuration yml file you indicated. Which file are you referring to? I looked in a number of files, and the only one which had a section that said "sync content" was the schema file, but that doesn't specify any settings at all. So, where is this particular line you're talking about?

Changing minimum-stability to "dev" from "stable" worked for me.

I was able to force an install of this module by editing one of the yaml files. Unfortunately, I cannot remember which file I edited, where it was, or the edits I made at this exact moment in time. In reality, I'm so frustrated with Drupal as a whole that I'm about to throw in the towel on my project and go back to Wordpress.

Note that the name change of this module has broken at least one other module in Drupal that depends on it: Layout Builder +

Changing this to a critical bug report as nobody has responded and this strikes me as a critical problem with this module. If the form submission is updated, it should update the associated entity, yet fails to do so.

Yes. I have visually confirmed by searching for both "navigation+" and "navigation_plus", and checked the "Page Building Group". Is there a tag within the config files that is missing?

In answer to the above question regarding what happens when you type the link into the address bar, you do, in fact, end up in the right place. The issue currently is the link to access the module does not appear on the admin config page.

I was able to force install bat_api by cloning it from git, and then installing the dependencies. There was at least one (I think, and off the top of my head, I can't remember which one; just that I had to clone that one from git as well) dependency that initially was showing as "incompatible" with Drupal 11, which was easily worked around by editing the info.yaml file associated with it.

I don't know if this was a good idea or not, but it turned out to be a moot point and a complete waste of time, because, while it got the thing installed, it still didn't work. I went through the whole meeting room "tutorial" thing in the vastly outdated documentation on roomify.github.io, and when I got to the "update availability" section under BAT for Drupal, after entering the dates/times of the availability update, I got the white screen of death: "This website has encountered and unexpected error. Try again later." Fortunately, I was able to get back out of that, but in the end, I threw up my hands in frustration and uninstalled the whole thing.

Update: I have solved the issue. It was my own fault, and I managed to fix it by restoring a key that gets deleted from the database in a conflicting module.

I want to add my comment to this as I'm also experiencing problems getting this module installed.

The result I get when I run

$composer require 'drupal/bee:^11.0' is this:

Problem 1
    - Root composer.json requires drupal/bee ^11.0 -> satisfiable by drupal/bee[11.0.0].
    - drupal/bee 11.0.0 requires drupal/commerce ^2.37 -> found drupal/commerce[2.37.0, 2.38.0, 2.39.0, 2.40.0] but it conflicts with your root composer.json require (^3.0@beta).

In my case, I can't install Commerce 2.37 as it is incompatible with Drupal 11.

So, around and around we go...

Unfortunately, the recommended approach doesn't work, as I'm using Drupal 11.1.1, and the Services module is for Drupal 10. When I run the command, I get a similar error. I checked the Services module, and there does not appear to be a module for Drupal 11.

I'll try to work around the problem using the BAT core in the interim, however if you can suggest an alternative approach, it would be helpful.

Production build 0.71.5 2024