Thx! Will make a release with that change.
We should have another look at this when the new settings api lands.
Thx
hydra → made their first commit to this issue’s fork.
Changes are looking reasonable. Can we get the pipeline warning fix?
Feel free to re-open if interested exists in working on this.
Lets get this in :)
I addressed both issues:
- No config dependencies should be getting added when interacting with paragraph blocks to the fake block_content bundles. Instead we should rewrite them to proper dependencies of the underlying paragraph configs.
- Since paragraph blocks are no real blocks, there is no sense in creating content_translation configs for them. With the first fix, those configs won't break config import anymore, but since they are useless I removed them from the form entirely to have better UX.
This won't fix existing, broken config. This will only apply for new config.
The config edit form does this by default. I believe it's for creating the "default value" form. I think the provided fix does the trick here, let's just gently ignore that this can happen...
Thx
hydra → made their first commit to this issue’s fork.
@drupatz It looks like this service is not even used by this service. So I think removing the dependency would be the better move here.
johannes stahl → credited hydra → .
Done
I'd like to postpone that till the new SiteSettings API is implemented. This will require a new solution for that.
This will be covered by the new SiteSettings API
For those cases it is possible to implement the applies method like this:
/**
* {@inheritdoc}
*/
public function applies(): bool {
return
in_array('form_group_type_edit_form_alter', $this->getHooks($this->inner), TRUE)
|| in_array('form_group_type_add_form_alter', $this->getHooks($this->inner), TRUE);
}
This working example shows how to alter the group edit and group add form at the same time.
For me it looks like Jürgen already integrated ECA perfectly with gin, so gin_everywhere maybe should just ignore the ECA Entity Type forms?
Thx!
LGTM
thx!
This LGTM, but it needs of course to be added on the other side as well :)
Okay I found out that this is actually working in ckeditor, when the image_sizes/core library gets loaded. For some reason this is not happening when embedded via ckeditor, therefore I added it as a dependency when adding media. It might happen that it gets loaded reasonless, but that was the best I could come up with.
As of #3515950
Can you please review this with the current RC5 version - I tested this with stage_file_proxy and it seems that the original issue is not happening anymore. It's actually failing right now and removing the stage_file_proxy check did already solve the problem for me @drupatz
I am not that deep into the magic of the component, but I tested it and it fixed the issue without creating new ones - so I guess its a good fix :) Thx!
Nice, thx for the fix!
hey thx for testing! This has already been merged to 1.x
Rly nice, thx for the idea adoption!
@all who are using this patch already, pls make sure to adjust your code. Harlor updated the issue summary with an up-to-date documentation.
LGTM
Nice! I'll gonna test this as well in a project and give feedback :)
@woldtwerk Any news on this?
Hi @mohammad faqeh thx for your report!
I see that issue but I don't think we should solve this specifically for media. It is theoretically possible to make some of those fields that belong to the advanced section visible with media and even more important I thin, is that this is actually happening on other entity forms as well (like path_alias for instance and possibly more).
I am totally into fixing this, but I would prefer a solution which would fix that issue in general. Haven't had the possibility to think about a solution yet, I am not even sure this is possible, but before excluding media entities I would suggest trying it :)
So thx again for pointing this out and starting the discussion :)
Yeah just did not have the time yesterday. 1.2.3 is out containing the hotfix.
Maybe we find a better title for this issue if we leave it open?
I am totally fine with your suggestion! Merged.
I merged the 2 pages and tried to make more clear what it's purpose is, I hope thats better :)
Merged the 6/7 versions and made more clear that his is the old module page for documentation purpose.
Thx for the feedback. I just wanted to keep the legacy content from the module page. It's no specific or new documentation. It just for historic reasons and as far as I understood the takeover of the modules namespace maintainership, I should keep old Versions and content.
So basically my Idea was to create those documentation pages and link to them from the modules page. If this is not ok, any Idea how to solve this?
Appreciate any feedback!
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.
As this module has not been maintained for some time, I am closing this ticket as “outdated”. A new version of sites which is architecturally and technically unrelated to the Drupal 6 and Drupa 7 versions will be published here soon.
Thank you for your contribution.