You can create your own formatter and extends ParagraphsTableFormatter... Simple and smarter
This module is not designed like that. When a field is empty, it will have to generate html even though it is empty because there will be many related features. For example, create a new paragraphs with ajax. load ajax table with custom code, show footer for customization. In short, this is not a bug.
please tell me what drupal version are you using?
what version of bootstrap theme are you using?
can you take a screenshot of the generated html code?
I still credit you but this patch is really not serious at all. It almost didn't check it again before merge request, it caused an error when checking so I had to fix it.
I think you are confused about widget paragraph json. If there is no element, it can return an empty string, no problem. The topic here is widget paragraph table, the patch you create for table widget, you check if there is empty, it will not print anything. Meanwhile, there is more function than that, for example if it is empty, you can add a button to add new paragraph, you can load ajax to add or add a custom twig below to customize.
Some people like you may not like these customizations, you can do patch, others just copy the patch link and then put it composer.json every time it is updated, it will patch itself to module.
oh this patch for someone interested who wants to add patch to composer.json, it will not merge with module because it will break another functionality, it needs to render div for ajax loading or adding button new,...
#3 is better than this patch
public function viewElements(FieldItemListInterface $items, $langcode) {
// Hide the field entirely, if empty:
if ($items->isEmpty()) {
return [];
}
bootstrap 5 admin
🐛
An issue with ECA module
Active
drupal 11.2+ supports submit button, so I think there are more themes that will change the input to a button ('cos it supports icon)
$form['submit-button'] = [
'#type' => 'button',
'#submit_button' => TRUE,
'#value' => $this->t('Submit'),
];In the GDPR text (Regulation (EU) 2016/679), there is no explicit mention of "not using CDN." The GDPR only establishes principles for processing personal data.
The issue with CDN is that it may lead to the transmission of personal data (such as IP addresses) to third parties outside the EU. This may not be true because CDNs usually have servers close to where you access, so most CDNs have servers in Europe. CDNs mainly operate through caching in the browser; if you have already browsed a another site that uses this CDN, then the browser will not load it again, which helps load the site faster, so I definitely will not fix this issue.
I don't understand what you mean, because the two modules are completely different, as well as their logic. If you like the logic and configuration of the entity browser, you can use it. I am closing this request, because I am sure I cannot implement the logic from the entity browser.
The main objective of this module is to replace the entity browser module by creating an entity reference view and mapping it in the field settings.
Oh I think fixed it is not complicate
in widget/formatter looking for target_bundles just check handler_settings[negate] and use array_reverse.
Oh, it's up to you, I have no opinion on adding options. I thought about it at first, but here's the technical difficulty. There are really a lot of options for Bootstrap-tables / Datatable. When you make form configuration for module formatter, you can't create a variable with multiple options. These options depend on the type of table libraries you want to display.
But If you don't need the functionality of bootstrap tables or datatables don't active option, the default Drupal table will be displayed by default.
And after years and many sites using it, this is the first time I see asking this. I think in reality, not many people want to use this functionality.
Could you help rewrite the document in readme.md?
You can active module 'Paragraphs Type Permissions'. You can set role to see button add or use css to hide it
Beaware/!\ The paragraph table is designed for a single paragraph type. You can select multiple paragraphs, but only the first one will be selected for display.
You can select another library or without bootstrap table use your own theme.
It is designed with permission to add paragraphs
why mr? do you review this?
for me this patch is incorrect. I can accept this, you can see it create phpcs warning. and the translate must do in markup render
@colan it fixed check dev version
Committed and fixed in another ticket, your merge request is not validated for phpcs
It's up to you. if you base on module entityreference_modal_create you can save your time 10% with form widget settings, or you can create a patch to add new options to the widget's config or create new widget entity_reference_modal.
You need to rewrite the js library by yourself with the same features as bootstrap table. Honestly, up to now I still haven't seen any opensource library that is as good as bootstrap-table. I think you can try with datatable or hansontable. If it's too heavy, you can write it manually as long as it can paginate the table, filter on table cell, First column have to select 1 items (radio) or multiple checkbox foreach lines. If you can replace bootstrap table library, you don't need to load bootstrap 5 cdn.
The instructions of the module can't help you install and configure?
Requesting a demo site to try will never be available because it uses api key of gemini, deepseek, openai,... or selfhost. Most of the sites of my customers are using chatbot AI + RAG for ERP application intranet and self-host AI model so it will definitely not be public
If your theme is not base on Bootstrap 5 then there is an option to use Bootstrap CDN. If you select this option your popup will work fine.
Without Bootstrap lib ? this definitely cannot happen as you wish. It is designed with Bootstrap table library.
Tested by myself, it works fine, but I can't reproduce this bug. Try the development version, it may be fixed in another issue.
Tested by myself, it works fine, I can't reproduce this bug. Try the dev version, maybe it is fixed in another issue
this patch is not good at all
If an entity is not a node then it has to run a foreach all rows this is not optimal
$ids = [];
foreach ($rows as $key => $row) {
$revision = $row->_entity;
// Get the *node ID* from the revision entity.
if ($revision->hasField('nid')) {
$nid = $revision->get('nid')->value;
$ids[$key] = $nid;
}
}
// Get unique model values and their original keys.
$unique_ids = array_unique($ids);
// Use array_intersect_key to filter the original $rows array
// based on the keys of the unique ids values.
$unique_rows = array_intersect_key($rows, $unique_ids);
$rows = $unique_rows;
another code can't pass phpstan exemple
you need to use injection dependency. but why does it always have to be node? there are many other entities like user, taxonomy or custom entities ECK?
$entity_type_manager = \Drupal::entityTypeManager();
$revision_ids = \Drupal::entityQuery('node')
....
Your patch cannot be merged in dev because it does not respect drupal phpstan and phpcs standards
You can try module field states transition it is 2 times better than content moderate state and kanban is full support module field states transitions
it can't pass phpcs test
FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES
------------------------------------------------------------------------------------------------------------------------
475 | WARNING | Only string literals should be passed to t() where possible
| | (Drupal.Semantics.FunctionT.NotLiteralString)
509 | WARNING | Only string literals should be passed to t() where possible
| | (Drupal.Semantics.FunctionT.NotLiteralString)Address Autocomplete has never released an official version, this is not the main reason for me to write a new module. But the configuration of the two modules is different. Address Autocomplete is configured once in the module, while Address Suggestion module is configured in each field. This difference is very big and cannot be merged.
I knew it. it write down in \datafield\src\Plugin\Field\FieldType\DataFieldItem.php
// Reset the field storage config property - it will be recalculated
// when accessed via the property definition getter.
// @see Drupal\field\Entity\FieldStorageConfig::getPropertyDefinitions()
// If we don't do this, an exception is thrown during the table update that
// is very difficult to recover from since the original field tables have
// already been removed at that point.
$field_storage_config = $form_state->getBuildInfo()['callback_object']->getEntity();
$field_storage_config->set('propertyDefinitions', NULL);
You will see the same error on the module having a dynamic subfield like double field, triple field...
Actually, from beginning, I did not intend to support the smart date module because its data storage structure is completely different from date time and date rage module in drupal core. After supporting smart date, a series of timezone problems appeared, so in the new version, I was forced to prioritize standard drupal fields than supporting smartdate. You can go back last version or wait new version
newest patch for dev branch
Drupal\subpathauto\PathProcessor::__construct(): Argument #4 ($module_handler) must be of type ?Drupal\Core\Extension\ModuleHandlerInterface, Drupal\Core\Path\PathMatcher given in Drupal\subpathauto\PathProcessor->__construct() (line 98 of D:\www\drupal\web\modules\contrib\subpathauto\src\PathProcessor.php).
drupal 11.2
it's weird i get error everywhere
It must support Bootstrap 5 admin(there is an option to enable Bootstrap 5 if your theme is not based on Bootstrap 5), I user lib bootstrap 5 table for search,... I would be happy if the Gin theme were also supported.
Your merge request doesn't pass the phpcs test, so I definitely can't merge your branch
I will do it when the customer requests. Once a customer requested but in the end they did not pay so I have no intention of developing further.
glTF is family of GLB, I verified GLB it works well
if you want but i reject his commit
@rakesh.gectcr thanks you save my day.
I confirm patch #49 fixed this issue
patch please i will release new version
Can you specify which eca module? JavaScript error? Log error, etc.
purge cache + varnish it works fine after update
No I have always error
check on drupal 10 and 11 class Serializer the construction doesn't need $module_handler