Account created on 19 January 2022, about 3 years ago
  • Strong Junior Drupal Developer at DevBranch 
#

Merge Requests

More

Recent comments

🇺🇦Ukraine Foxy-vikvik

@dieterholvoet It was a mistake. I found an issue and changed it. This merge request is still a work in progress. So it will be formatted text. I will change it when I have time.

🇺🇦Ukraine Foxy-vikvik

foxy-vikvik changed the visibility of the branch 3.0.x to hidden.

🇺🇦Ukraine Foxy-vikvik

Confirmed that all pipelines have been resolved and successfully merged the merge request.

🇺🇦Ukraine Foxy-vikvik

It was fixed (commented part of the code on 2.0.x branch) It will be removed soon

🇺🇦Ukraine Foxy-vikvik

I have merged the latest changes and will work on rewriting some parts of the module using Field API. We will have a v3

🇺🇦Ukraine Foxy-vikvik

I have added a checkbox. When it checks it will show a hidden textfield where we will add the URL for testing purposes.

🇺🇦Ukraine Foxy-vikvik

Also updated comments into the functions in the UrlInspectionOperationsManager class

🇺🇦Ukraine Foxy-vikvik

I rewrote a little bit of information from ReadMe.txt and added links into Readme.md

🇺🇦Ukraine Foxy-vikvik

Added general information how to set up the module

🇺🇦Ukraine Foxy-vikvik

foxy-vikvik made their first commit to this issue’s fork.

🇺🇦Ukraine Foxy-vikvik

Related to current issue - https://www.drupal.org/project/calendar_view/issues/3405794 🐛 All-day dates start early Fixed
I reverted the changed in the merge request because it is not working if we have on standard timezone in the site and not correct data range.

🇺🇦Ukraine Foxy-vikvik

It happens because it renders dates in different time zones
I have UTC for one field and (America/Toronto) fro another

🇺🇦Ukraine Foxy-vikvik

Patch from this this issue 🐛 Facets breaks all AJAX views that uses pagers even without facets Active related to the Factets fixed the issue with pagination

🇺🇦Ukraine Foxy-vikvik

I am working on a project where we use Gin + Paragraphs, and your code does not work for me.

🇺🇦Ukraine Foxy-vikvik

The best option is to remove hook_entity_storage_load and replace with the custom logic. It has bad impact on the sit performace.

🇺🇦Ukraine Foxy-vikvik

On Drupal 9.3 works fine and fixed the main issue related to the infinity loop. I had infinity loop when generate Sitemaps using module Simple SiteMaps.

🇺🇦Ukraine Foxy-vikvik

The main issue in my case was that the boolean field in the paragraph entity by default has a NULL value (bizarre behaviour)
So the patch from comment #126 🐛 New non translatable field on translatable content throws error Needs work solved the main issue and I fixed issue with the NULL value by myself

🇺🇦Ukraine Foxy-vikvik

patch #2 from the Comment #2 Support applying #states to a horizontal tab Needs work is not applies with field_group 8.x-3.6

🇺🇦Ukraine Foxy-vikvik

I added the following conditions:

 if (empty($widget) && $subform_position = array_search('subform', $field_state['array_parents'])) {
        $widget = NestedArray::getValue($form, array_slice($field_state['array_parents'], 0, $subform_position));
      }
🇺🇦Ukraine Foxy-vikvik

It happens only when translating the node with paragraphs

🇺🇦Ukraine Foxy-vikvik

@quietone I did the same steps as on the description BUT
We use paragraphs module in our project and some fields we don't translate that's why I found NULL in $widget
I think it is related to the $field_state['array_parents']

🇺🇦Ukraine Foxy-vikvik

Patched based on the "patch for the comment #94": https://www.drupal.org/project/drupal/issues/3025039#comment-15576672 🐛 New non translatable field on translatable content throws error Needs work

for Drupal 10.3

🇺🇦Ukraine Foxy-vikvik

We need to add a condition if the <?PHP
!empty($widget)
?>

🇺🇦Ukraine Foxy-vikvik

foxy-vikvik made their first commit to this issue’s fork.

🇺🇦Ukraine Foxy-vikvik

Duplicate this https://www.drupal.org/project/custom_search/issues/3040533 Only require input for any-value if taxonomy vocabulary is enabled Needs review

🇺🇦Ukraine Foxy-vikvik

Hello. @smustgrave Could you please read the summary maybe It will answer your question.

I suggest removing direct support for this library because:
1. This library is deprecated.
2. The module should not care about the support of all libraries in this regard. The module already has a way to disable the automatic submission of input fields using the [data-bef-auto-submit-exclude] attribute.

🇺🇦Ukraine Foxy-vikvik

Validate condition for the form Validate method was added.

🇺🇦Ukraine Foxy-vikvik

.gitlab-ci.yml file was added into the root repo

🇺🇦Ukraine Foxy-vikvik

The style link issue was fixed in the last merge request.

🇺🇦Ukraine Foxy-vikvik

Foxy-vikvik made their first commit to this issue’s fork.

🇺🇦Ukraine Foxy-vikvik

It is working in native views on Drupal 10

🇺🇦Ukraine Foxy-vikvik

I know it looks like an exception but It may happen

🇺🇦Ukraine Foxy-vikvik

Steps to reproduce:
- In content type we had one comment type - with a "text plain" field
- Some comment entities were created
- We need to change "text plain" to "text field formatted - need CKEditor" that's why we created a new comment type (prev we use in other content types)
- I have removed comment field with plain text and created with formatted
and in the /admin/content/comment found an issue

The website encountered an unexpected error. Please try again later.
Error: Call to a member function getSetting() on null in Drupal\comment_delete\CommentDeleteManager->getConfig() (line 121 of modules/contrib/comment_delete/src/CommentDeleteManager.php).
Production build 0.71.5 2024