Does this update help auto-mapping new openID users to existing user's roles?
The default choice options myseriously appeared this morning. You can close this ticket.
Related to this request, I wonder if having more than 1 domain source will create any issue.
I thought domain source is hard url, while domain access is a sort of alias.
So, as long as I keep a single source (and single sitemap component), I won't be damaged by duplicated contents penalty by Google.
I can see that I can have more than one default value for domain source. I was going to pick as many sources as possible, but then the duplicatd contents penalty hit me.
This might be a simple googling or chatgpt level question, but would like to have Drupal guru's opinion.
keithkhl → created an issue.
keithkhl → created an issue.
@s3b0un3t, I can make it work by commenting out __construct in the function temporarily, but indeed it occurs to all modules relying on Drupal core's configform.
can confirm that @johnjw59 's patch works on 2.0.0-beta2 and the Oct dev version.
It would be ideal to have an option to choose which domain to be the default, though.
https://www.drupal.org/project/change_author_action →
Change author action module worked for me.
keithkhl → created an issue.
keithkhl → created an issue.
keithkhl → created an issue.
I just found that in layout builder edit mode -> Manage attributes -> Block / Block title / Block content attributes, all fields (ID, Class, Style, Data-*attributes) are empty. Do I have to specify what values should be pulled?
I am new to Drupal, and I am really new to Layout Builder, so it is only a guess, but for other modules that deal with block layout, whatever the setting I make in Drupal's native UI (ex. structure -> contents type -> Edit / Manage display), no settings were effective. I had to re-define any value in Layout Builder, especially the ones with 'Manage attributes'.
Just wonder if this might be related to Flippy not picking up any node. If so, can you plz help me what value I should use for Data-*attributes? (ID/Class/Style should follow typical HTML grammar, I assume.)
keithkhl → created an issue.
keithkhl → created an issue.
keithkhl → created an issue.
Just double checked that after removing the default domain, I can access the /admin/content page again. Now, the main page (www.example.com) is not accessible.
keithkhl → created an issue.
This happended to me as well after setting up default domain in domain module. Withouth default, I don't, but then, the main site is not accessible. Wonder if there is any workaround at least...
keithkhl → created an issue.
By default, all images were set to be converted to WebP for multiple sizes, but since the image was already WebP, the conversion process didn't work.
keithkhl → created an issue.
keithkhl → created an issue.
I thought I installed both extensions to my Ubuntu.
I just changed the base module from gd to imagemagick by image tool kit. problem solved.
keithkhl → created an issue.
With vanilla installation, I manage to add avif in the allowed image list in above two structure settings, but I stil cannot upload avif image files. When I upload *.avif to node editor's image, I get following error
- The specified file ****.avif could not be uploaded.
- The image file is invalid or the image type is not allowed. Allowed types: avif, avifs, bmp, dib, gif, jfif, jpe, jpeg, jpg, png, svg, svgz, tif, tiff, webp
It is surprising that even if I have the MIME type in the available list, I still end up with the same error.
@gord.fisch, that was file path module.
It created 'public://' at the front of urls for image, which nullified url rules that wp migrator follows.
I was going to use this plugin, but not any more. It creates db tables that are not in native structure of Drupal. I might have misconfigured, but that's already a big no go. migrating custom post types of wp to drupal's new contents type didnt work neither. image urls were not properly changed, and some images missed drupal's uuid creation.
I could debug and fix one by one, but i would rather pay a few thousand bucks to human migration. this will be way less prone to errors.
Sorry to bother you guys again for this fixed issue, but I wonder if there is a patch available.
I am having the same error on D11 w/ Gutenberg 3.0.4 (and dev) when I upload images directly by 'upload' button.
If I do so on the media library pop-up screen, I do not have such issue.
It would be great to have the patch available before your next minor version roll-out, if it is going to take some time.
@gease, I fixed it. Don't know why, but dependency to 'claro' did not read the theme. I added the full function into the code. So, as long as Claro is not removed, the function should work. I've confirmed a number of admin themes (Gin admin, Bootstrap admin, and D10's administration theme). Attached the 'dirty hack', in case anyone get in trouble like me.
@gease, I've tried the function as a custom module on Gin Admin and Bootstrap 5 admin themes, but it doesnt work on either. I revert back to Claro for now.
To the team, as a long time WordPress user w/ heavy dependence to Gutenberg, I deeply appreciate the hard work on this. However, with current setting, I become wary of every single module potentially discharge me from node editor with Gutenberg.
Whatever the functional mod to the admin theme is implemented, like experimental navigation bar module for example, I cannot use Gutenberg editor anymore.
I can further customize CSS on a Claro sub theme for UI, but I would much appreciate if there is an official sub module that overrules each theme's node editor customization. At least it was like that with WordPress by default.
can you guys commit a WIP update at least as a dev version? including above issue, I remember reading a number of bugs being patched, but I am still stuck with manually installed 3.0.4 , which creates version incompatibility msg everytime I want to install gutenberg sub modules via composer.
Create a new form designated for sidebar, and in manage form display, add everything you want under the sidebar form.
It still does not remove the revision box. I either have to remove revision option in Edit, or use css to make the box invisible.
Now need to find out how to create a sub theme for Claro.
keithkhl → created an issue.
@gease, thx bunch. haven't thought about that. as long as claro stays in the system, like sub-themes.
It's because the exmple blocks module within 3.0.4 package is not compatible with D11
same here. 3.0.4 is locked from D11. Manual installation worked though.
After setting a Bootstrap theme for default, I cannot access editor even with Claro as the admin theme (w/ editor option checked).
In the dev console, I can see that calls for files are made, and status were all 200, but the screen body got covered by the Bootstrap js.
The entity type agnostic (
https://www.drupal.org/project/gutenberg/issues/3445655
📌
Entity type agnostic
Active
) should take this into account.
Because I have removed SASS starter kit, after I created my own custom sub-theme.
Once I install the theme again, the issue is gone.
Where to add that function? Guess I have to change the library 'claro/form-two-columns' to something else.
keithkhl → created an issue.
I further uninstalled most uninstallable modules, and now it is working. I will later add what module or customization caused the issue.
I have uninstalled following modules, which removed above database connection error, but I still cannot run this migration. Despite the error msg, xml files are indeed uploaded, but it is stuck there.
- Migrate Drupal
- Migrate Drupal UI
keithkhl → created an issue.
Thx for the comment. Yup, Rome, do it as Rome. I got that. Guess this type of a little harsh comment is also Drupal style. Besides, I should've raised it to Gutenberg module board, not here. My bad.
Just so you know, there are over 5,000 Drupal websites running Gutenberg, based on the module page stat. It has not been Drupal style that I get that, but the size does not look that negligible, considering all other module stats that I have seen for the past a week.