Re-opening. I'm seeing this issue with Taxonomy Reference Tree 2.0.1 and Gin 8.x-3.0-rc10.
To use a module that doesn't have a Drupal 10 release, you can add <a href="https://github.com/mglaman/composer-drupal-lenient ">mglaman/composer-drupal-lenient</a> as a dependency to your composer.json, which will allow a patched version of the module for Drupal 10.
This issue would be resolved by the other issue, but this issue also narrower in scope. Increasing maxlenghth on views field labels seems like a useful feature for views, and a simple change that might not need to be dependence on the system wide decision for maxlength on textfields. I'll try to add some tests but might not get to it immediately.
Updating the title to reflect remaining issue: Layouts are ignored by ECK.
Lets close this since no one has reproduced this or reported again on subsequent releases.
This is happening when embedding a tweet list. The data-tweet-limit is in the anchor link. I can't find anywhere that this is a documented limitation of embedding a list, so it's possibly an issue with widgets.js.
There isn't an official EOL for v1 but they are limiting access to it.
They announced they are ending the Premium v1.1 access tier on April 29th. The API v1 list endpoint will no longer be available unless on an Enterprise tier. Migrating to API v2 will allow us to continue to pull tweets from a list on the Basic tier. On the Free tier it it will allow puling tweets from a user. And it looks like it will also allow pulling tweets from multiple user accounts, which may make it possible replicate a list feature in some cases, but the rate limits on the free tier will make it not very usable in our development workflows.
Thanks so much for your interest! This module has been great for what we needed.
The road map should account for differences in the Twitter V2 API including:
- Endpoint URLs
- App and Project requirements
- Request parameters
The Twitter API v2 endpoints require that you use credentials from a developer App that is associated with a Project when authenticating your requests.
The module would need to be updated to account for these differences, but overall it looks like the same functionality would remain. There might be additional credentials for authentication.
Here's a patch.
squiggy → created an issue.