I am not sure this needs to be ported to 8.x-1.x.
Is this correct, 'not ... less than the longest value' ?
This can not be less than the longest value in the database.
This is outside the scope of the project. No maintainers have spoken in favor of it.
If you disagree you can change the status.
I don't think 8.x-1.x has a vocabulary option.
Should this issue be closed?
bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.
The issue queue for "Duration Field" has not had movement except for this issue.
I have not heard from the maintainer Jaypan. It is unclear if dww can make additional co-maintainers.
I am moving to "Drupal.org project ownership" project
bluegeek9 → created an issue.
bluegeek9 → created an issue.
bluegeek9 → created an issue.
bluegeek9 → created an issue.
bluegeek9 → created an issue.
bluegeek9 → changed the visibility of the branch 8.x-2.x to hidden.
jdleonard → credited bluegeek9 → .
jdleonard → credited bluegeek9 → .
bluegeek9 → created an issue.
I fixed the other libraries that are using dynamic properties.
Updating jquery.once to once is done it 🐛 Highcharts - jQuery Once console errors Active
Can thin be closed, or should I make a MR?
I believe this has been fixed. The code checks if the array key isset before accessing it.
foreach ($data_field_options as $field_key) {
if (isset($field_handlers[$field_key])) {
$data_fields[$field_key] = $field_handlers[$field_key];
}
}
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
8.x-3.x is bug fixes only. We encourage everyone to migrate to 5.1.x.
bluegeek9 → created an issue.
I was able to use charts on Drupal 10 with this patch.
I updated the pipeline to use the Drupal template. If mkdocs.yml exists pages will be built and deployed, but only when the branch is the default. MR will not build or deploy pages.
bluegeek9 → created an issue.
There are two .min.css files. I set them to be ignored.
bluegeek9 → created an issue.
bluegeek9 → changed the visibility of the branch 3516266-code-coverage to active.
bluegeek9 → changed the visibility of the branch 3516266-code-coverage to hidden.
Charts does not have the solid gauge option for Highcharts. Charts 8.x-3.x is legacy; bug fixes only, no new features. Everyone is encouraged to migrate to Charts 5.1.x.
bluegeek9 → changed the visibility of the branch 8.x-2.x to hidden.
This was introduced in #2953102: Highcharts pie/donut charts should be able to accommodate one node (or an aggregation) with multiple fields →
I don't know enough about why this was added to remove it.
bluegeek9 → made their first commit to this issue’s fork.
I found the same problem in other libraries.
I was able to reproduce the error, and the patch resolves the error.
If I am mistaken, please re-open.
The percentages are calculated by the chart library (javascript) not the charts module (php).
I believe zeros are the expected behavior.
Since the 8.x-3.x branch will not support Drupal 11, can this issue be closed?
@btully,
I want to confirm, you are using the 5.0.x-dev branch.
How did you install the chartjs and data label libraries? Which version of chartjs and the data label plugin?
Thank you for following up!
There is not enough information to reproduce the issue and the issue was last updated 5 years, ago.
bluegeek9 → created an issue.
bluegeek9 → made their first commit to this issue’s fork.
bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.
bluegeek9 → made their first commit to this issue’s fork.
I could work on it. I can not promise it will be the next thing I work on.
Drupal core does not trim field values. This can be done with others modules like Trim →
I think the problem is caused by the name.generate.examples being added after you installed the name module. This project only recently made a stable release, 8.x-1.0.
The update 8203, adds the name examples.
I am not sure why the update references 8.x-2.3, and the current version is 8.x-1.0.
I think name_update_8203 could be renamed to name_update_8101.
bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.
bluegeek9 → made their first commit to this issue’s fork.