- Issue created by @coaston
- ๐บ๐ธUnited States apmsooner
I believe several of these issues you are reporting may already be fixed in dev version. Can you test dev please and verify if the issue persists?
- ๐ธ๐ฐSlovakia coaston
I am unable to downloadn 3dev via composer, that is the reason why I used 3.0 beta2.
However will try to download it manually and test.
Tnx - ๐บ๐ธUnited States apmsooner
In the other issue you said you were using the 2.x version. 3.x version is only for Drupal core 10.2^. I'm confused with where you are finding these bugs and what version you are actually using.
- ๐บ๐ธUnited States apmsooner
If you need 2.x dev:
composer require 'drupal/custom_field:2.0.x-dev@dev'
If you need 3.x dev:
composer require 'drupal/custom_field:3.0.x-dev@dev'
If you are using ddev, lando, etc... locally than prefix those commands accordingly.
You may need to set this in composer.json if you get warnings on installing a dev version:
"minimum-stability": "dev"
- ๐ธ๐ฐSlovakia coaston
Thank you.
Maybe you can help me with my problem. I am using wamp server and when I installed composer and use cmd with admin rights i am unable to run following cmd:
composer require 'drupal/custom_field:^3.0@beta'
It statted i need to get rid of ยด so i when i use:
composer require drupal/custom_field:^3.0@beta
I am getting error with path..So i found somewhere on google the way it works for me and it has to be the full adress like :
composer require drupal/custom_field:^3.0.0-beta2
The same for version 2.0.1 i need to use the following path:
composer require drupal/custom_field:^2.0.1
The same issue for all modules but for some I can download dev verzions because when I try yours like:
composer require drupal/custom_field:2.0.x-dev@dev
without "ยด" it does not work so i tried withcomposer require drupal/custom_field:2.0.x-dev
which works for me in other cases (other modules) but does not for this module.To be honest I used Ludwig before so I am learning with composer and i am not sure why i have to remove "ยด" and have to update link for the direct address every time.
It is because of CMD in windows?
But when i tried with console on hosting server I had the same issue...So i am really confused why it does not work as stated in documentations.
Will try
"minimum-stability": "dev"
to update JSON to see of this helps. - ๐ธ๐ฐSlovakia coaston
Hello apmsooner,
Looks like the first "formated" issue was resolved. So now when I save a content with long text there is no issue in log.
However when you try the same with views there is still the same problem.1.Create a new view
2.Add Custom field with long text
3.Try preview it.
4.Check logs.Even in 3-dev version I can see following :
Warning: Undefined array key "formatted" in Drupal\custom_field\Plugin\CustomField\FieldFormatter\TextDefaultFormatter->formatValue() (line 28 of \web\modules\contrib\custom_field\src\Plugin\CustomField\FieldFormatter\TextDefaultFormatter.php)
- Assigned to manish-31
- Issue was unassigned.
- ๐ฎ๐ณIndia manish-31
Hi @coaston
I followed the steps mentioned by you to reproduce the warning but I don't see this warning.
Steps followed -
- Added a text long custom field in a content type
- Added the field in a new view
- Previewed the view
- Checked the logs - nothing in the logs
Could you please check again and maybe provide exact steps to replicate it?
- ๐บ๐ธUnited States apmsooner
I'm also unable to reproduce this issue. I just pushed some more updates to the dev branch last night that further solidifies the fields settings forms. I will be publishing a new 3.x release very soon now. Just trying to get the ajax issues resolved in unit tests.
- Status changed to Fixed
9 months ago 3:53pm 4 April 2024 - ๐บ๐ธUnited States apmsooner
Addressed in https://git.drupalcode.org/project/custom_field/-/commit/bca7f28a6aca17e... by providing a fallback.
- Status changed to Fixed
9 months ago 6:30pm 4 April 2024