🇺🇸United States @pmagunia

This may be the module you are looking for if you have a premium subscription to Twitter:

https://www.drupal.org/project/twitter_api_block →

I guess it may be worth adding a message on this module's front-page that Twitter requires a premium paid subscription so users are aware for transparency.

I don't plan to get a premium subscription either.

pmagunia → created an issue.

This is still an issue that is holding us back.

I think they made the Twitter API a premium feature that requires a credit card.

Even after the patch in #41 Commerce Recurring fails upon uninstall for me:

commerce_recurring: The <em class="placeholder">Billing period</em> field type is used in the following fields: commerce_order.billing_period, commerce_order_item.billing_period

I haven't had much luck uninstalling Commerce Core either.

For Drupal 10 and Commerce v2.39, I had to do something slightly different:

/**
 * Implements hook_commerce_order_update().
 */
function MYMODULE_commerce_order_update($order) {
  if ($order->getState()->getId() == 'completed') {
    // Business logic like adding a role or dpm().
  }
}

I know this post is for D7 but thought I'd add the D10 version since its a top hit.

<?php

/**
 * @file
 * Contains MYMODULE.module.
 */

/** 
 * Implements hook_form_alter().
 */
function MYMODULE_form_alter(&$form, &$form_state, $form_id) {
  // Switch statement may be better if you have a lot of options.
  if ($form_id == 'MYFORM') {
    // Use dpm($form_id) if you are unsure of the form's ID.
    // The following statement may need to be adjust depending on your field type.
    unset($form['field_MYFIELD']['widget']['#options']['_none']);
  }
}

We're using the Tabs field group and have "Mark group as required if it contains required fields" checked.

On the edit page there are now 2 red asterisks in the tab that has a required field. Not sure if that is expected behavior.

The patch from #52 applied cleanly to Drupal 10.2.5.

Thanks for getting back so quickly.

A client on a Windows machine was having difficulty opening the file.

pmagunia → created an issue.

👍

The placeholders change made by jedihe caused SQLSTATE[42S22]: Column not found: 1054 Unknown column

I went back to the old code and it worked.

I was having the same issue. The solution in #8 fixed it for me. Thank you Fernly.

I think style attributes are not allowed in "Limit HTML" filter.

It also seems Word comments are not working elegantly. I tried to upload the docx sample file I used but the file extension is blacklisted.

I was using Safari 17.1.2

You're welcome Wim. I was using Safari 17.1.2. I did mention that in the Github thread you provided in comment #26

I copied the sample Google Doc into the nightly CKE5 textarea posted by Reinmar and still saw the issue:

Adding a screen recording of the issue

pmagunia → created an issue.

To minimize permission errors, I chose to set accessCheck to FALSE.

Providing a patch for that

The MR below comment #25 fixed the issue for our use case.

This issue is reproducible in Drupal 10.1 also.

If someone wanted to use the code in the patch:

function MYMODULE_update_10000(&$sandbox) {
  \Drupal::service('entity_field.manager')->rebuildBundleFieldMap();
}

Adding a file patch in case anyone want to link. Identical to #38

pmagunia → made their first commit to this issue’s fork.

Thanks for the suggestion @occupant.

I haven't really had time to investigate thoroughly but it could be.

I will keep that in mind.

I just tried it on simplytestme and it seems to be working OK.

I guess its an issue with our system.

pmagunia → created an issue.

I couldn't upgrade to admin_toolbar to the latest version due to some dependencies.

I thought it would be easier to patch here.

Not sure its acceptable.

Thanks for the quick reply.

We are using admin_toolbar 3.3.2 and Drupal 9.5.10.

I see this line in the older version of the admin_toolbar we are using:

#toolbar-bar {
  z-index: 100000;
}

https://git.drupalcode.org/project/admin_toolbar/-/blob/3.3.2/css/admin....

Our Drupal report is not explicitly saying its no longer supported, but there is a newer version on the Drupal.org admin_toolbar page.

pmagunia → created an issue.

The latest from MR12 didn't apply cleanly. This is the URL I used on the 1.x-dev version of the module:

https://git.drupalcode.org/project/entity_embed/-/merge_requests/12.patch

The entity_embed.info.yml and entity_embed.module files were out of sync.

Even after applying the changes manually the embed icons were missing for me on the text format config page.

#93 worked well for me though.

Two of the migration errors from the patch in comment #18 and #27 seem to stem from core:

🌱 [META] Serialization issues in Migration tests Active

I guess we can use the patch in #18 until the core issue is resolved.

I tried adding use DependencySerializationTrait; to the migration tests but still got the same errors.

I added the data loss tag to this ticket since our node_field_data table was showing the UID as 0.

The patch in comment #18 has failing tests.

Here is a patch version of the the MR in comment #12 by mpaulo. I believe all tests are passing for it.

I tested on my local and the warning messages that appear when saving a new field no longer appear which was my use-case.

The patch in comment #18 has test errors. I don't think we can use it.

This version of the patch has the D10 core version requirement and deprecated code removed.

I'm surprised the patch from comment #10 is still going through automated testing. Its been over a day now.

I think the icons may need to be converted to SVG too.

Thanks! The patch from Comment #11 fixed the duplicate counters.

pmagunia → created an issue.

I noticed you're using the CKEDITOR variable in the patch.

Correct me if I'm mistaken, but this wouldn't work with CKE5.

I did update the CKEditor5 issue thread with the 4 attributes you mentioned align, border, bgcolor, width.

For me, those should be sufficient.

I'm not sure I updated the CKEditor5 issue thread correctly; please let me know if I missed something.

Thanks! :-)

Created an upstream CKE5 feature issue as suggested by Wim for TableProperties.

https://github.com/ckeditor/ckeditor5/issues/13879

Additional details may need to be added.

Comment #26 helped me. I wrote an update hook for it. You'll want to change All Caps text to suit your site.

/**
 * Fix mismatched entity warning on Status Report
 */
function MYMODULE_update_9000(&$sandbox) {
  $field = FieldConfig::loadByName('paragraph', 'MYPARAGRAPHTYPE', 'MYFIELD');
  $field_storage = FieldStorageConfig::loadByName('paragraph', 'MYFIELD');
  $field->save();
  $field_storage->save();
}

I was able to uninstall Commerce Recurring. Comment #31 helped me.

What I did was:

1) Delete as much possible in the Commerce menu Drupal UI (I didn't need to keep Commerce on that machine. You may be able get by without this step.)
2) Change the lock status to false in the following YAML files:

config/sync/field.storage.commerce_order.billing_period.yml
config/sync/field.storage.commerce_order.billing_schedule.yml
config/sync/field.storage.commerce_order_item.billing_period.yml

3) Import the config
4) Run the following Drush script:

  
use Drupal\field\Entity\FieldStorageConfig;
use Drupal\field\Entity\FieldConfig;

// Deleting field storage.
FieldStorageConfig::loadByName('commerce_order', 'billing_period')->delete();
FieldStorageConfig::loadByName('commerce_order_item', 'billing_period')->delete();

5) Then finally drush pmu commerce_recurring

I was able to uninstall it without error messages. You may be able to alter the steps to suit your needs.

pmagunia → made their first commit to this issue’s fork.

pmagunia → created an issue.

pmagunia → created an issue.