It seems that the issue is related to memory exhaustion, likely due to the large number of entities and entity references being processed during export. If files are also being included in the export, the overall size may be exceeding the PHP memory limit. for now potential solution is to change to $serializer_context['include_files'] = 'none';
Also try increasing the PHP memory limit memory_limit = 2048M and checking for recursive entity loading might also help.
Yes, MR changes are working correctly. Moving to review..
Tested locally, and the changes in MR in #2 are working correctly.
Hi @plopesc,
I followed the same steps you mentioned and performed a fresh setup with the following modules. After installing the modules, the collapse and expand functionality worked as expected for me.
Does this issue occur consistently for you, or is it intermittent? Please let me know if there are any specific steps or configurations you have applied so I can look more effectively.
Review it as this issue has been open for a long time.
Hi @bubblegvm,
I investigated this issue and noticed that all comments posted by users are created as separate entities in the admin/content/comment page. When a comment is hidden from a specific piece of content, it does not mean the comment is unpublished in the comment entity. It remains published.
As a result, when accessing comments via JSON:API (/jsonapi/comment/comment), the hidden comment still appears in the response. This happens because comments are stored separately from the content they belong to. Even if a comment is hidden on the content level, it remains accessible via JSON:API since the response is generated from the comment entity itself, not the content entity.
Hi @mugesh.s,
I have set up Drupal 11 on my system and have not encountered this issue. Could you please provide detailed steps to reproduce it? Additionally, let me know if there are any specific configurations or modules involved that might be contributing to the problem.
Hi, the issue has been resolved after applying the merge request changes. It is now working as expected.
Raised the MR to ensure safety by using instanceof check and optimizing getRequest() calls to avoid redundancy.
kushagra.goyal → made their first commit to this issue’s fork.
MR is created for this particular issue.
@niharika.s That's why the issue exists for you. The module requires Google dependencies, which are initially installed via Composer. This ensures everything works correctly. Installing apiclient later may still leave other dependencies missing. Try installing the module with Composer, and it should work as expected.
Hi @dineshkumarbollu, I'm not sure why it's not replicating on your system. For me, I can see this error whether I install it via Composer or manually. However, after injecting this service, it's working.
@niharika.s, did you install it using Composer?
I tested this on my local setup with Drupal 11 and PHP 8.3, using the Infinite Scroll module in a View. I also tested it on a mobile emulator, and the scrolling behavior worked as expected—content loads correctly while scrolling on mobile.
To help debug this further, could you please provide exact steps to reproduce the issue? Specifically:
Drupal version and PHP version you're using.
Any custom configurations in the View (e.g., caching settings, exposed filters, pager settings).
Whether the issue happens on specific mobile devices or all mobile browsers.
If any JavaScript errors appear in the browser console when scrolling on mobile.
Let me know if you spot any differences or if there's anything specific..
kushagra.goyal → created an issue.
Could you please specify the exact version or where you are encountering this issue? I am currently using Drupal 11 with PHP 8.3, and I am able to use the media filter without any issues.
This issue no longer exists on my system (as shown in the attached screenshot). It is likely caused by custom alter code or a contrib module affecting the behavior. I recommend testing with a fresh setup to verify. If everything functions correctly, please proceed with closing the issue.
Let me know if you need any further insights.
@hudri, I investigated this issue and was unable to reproduce it in Drupal 11. In this version, when adding a new field, users must first select the field type (e.g., Upload field) before specifying the field name (as shown in the attached image). After selecting the field type, the system only then allows defining the field name, along with options for file upload types.
Based on this behavior, the issue appears to be outdated. However, please provide additional context so we can better analyze and identify any potential underlying problems
Hi @brunoalmeida, thanks for looking into this. Yeah It will ok by adding code for tree and indentation As Tree is the visual representation for draggable rows. This will help item visibility for view access.
Issue is able replicate on local, Here this issue coming due to styled components as they would be only view only access to editors. Hence does not containing draggable table that doesn't allow svg and indentation styles get rendered, so for Proposed solution is to create a separate component style to overwrite as below.
/* *
* @file
* Styles for custom indentation and tree item visibility for view access.
*/
.indentation {
position: relative;
inset-inline-start: calc(var(--space-xs)* -0.5);
float: left; /* LTR */
width: 1.5625rem;
height: 1.5625rem;
background: none !important;
line-height: 0;
}
[dir="rtl"] .indentation {
float: right;
}
.tree__item {
display: none;
}Did a try on my system it worked for me. (as image attached). not sure so, I would like to explore any other potential solutions to address this. if all good Will Raise MR.
Hi, I've tested on my system. It looks good for me so raised MR for the same.
kushagra.goyal → made their first commit to this issue’s fork.
I have replicated the issue where column header settings are lost when merging rows using rowspan in CKEditor 5, but it doesn't occur when merging columns with colspan. It seems that CKEditor is not correctly preserving the rowspan and colspan attributes when rows are merged. Additionally, input filter settings may be stripping out these attributes during the save process.
To resolve this, we could adjust the CKEditor configuration to ensure the rowspan and colspan attributes are handled properly during both the save and reload processes.
As image attached, in below table Merge cells and then enable column header. After save when try to enable header column for other cell. It also enable previously removed header column.
Ah Alright, Thanks for the update! Since the issue has been correctly categorized and is no longer relevant, I have changed the status to Closed (Outdated). Let me know if any further action is needed.
Drupal 11 has modernized its admin UI, moving towards a cleaner, more intuitive design.
Instead of separating "add a new field" and "reuse an existing field" with an explicit "or," these actions are now likely presented in a unified workflow or dropdown for simplicity. now it have adopted modern design principles, moving away from unnecessary separators like "or."
The focus is now on providing clearer, less cluttered options for field management.
@ressa this issue is no more exist Drupal 10 and 11. now Reusing existing fields is integrated seamlessly without needing a separate selector.
I’ve followed the steps to reproduce the issue as described, However, when duplicating block displays, changing the view mode for one block display will affect all duplicates. This is because view mode settings are shared across block duplicates by default in Drupal. This is the intended behavior, as view modes are part of the shared display configuration in Views, and they are not treated as independent settings per block display.
To achieve independent view mode settings for each block, it’s necessary to create separate block displays instead of duplicating the original block display. This allows each block to have its own configuration, including different view modes. solution could involve enhancing the Views UI to support independent configuration of view modes per duplicate.
I’ve tested the Entity Embed module with the "Media Browser" option, but I couldn’t replicate the issue. To investigate further, could you provide additional details? any other module you're using, and ensure they are up to date.
clarify what type of media you’re embedding (Image, Video, etc.) and its status (published or unpublished). It would also help to know your browser and whether you’ve tested this in incognito mode or a different browser. As for me its working expected..
With a fresh setup, I attempted to reproduce the issue on my system but encountered an unexpected error when trying to add a new consumer with any website.
@alfattal Could you please provide more details or steps to help reproduce the issue consistently? Let me know if there are specific configurations or scenarios I might have missed.
@bkosborne I tested this issue on my local environment, and I can confirm that the behavior is browser-specific and occurs only in Mozilla Firefox (133.0.3).
In Firefox, the issue described in the IS is reproducible. Specifically, after removing the media and reloading the page, the previously selected media reappears. Interestingly, if the page is manually reloaded by revisiting the URL (clicking the location bar and pressing Enter), the "remove" button works as expected.
This behavior seems to be linked to Firefox's form data persistence on reload, as outlined in the StackOverflow thread: Firefox Keeps Form Data on Reload. Adding autocomplete="off" to the node form resolves the issue on Firefox and ensures consistent behavior across browsers.
I’ve reviewed the proposed changes in the MR,. This MR looks good to move forward. Let me know if additional testing is needed!
kushagra.goyal → made their first commit to this issue’s fork.
I recently performed a fresh Drupal installation and used the Devel module's content generator to create multiple article nodes. After creating a View with a full pager to display the articles, I encountered an Html::escape() error when previewing the View. Has anyone faced a similar issue or knows how to resolve this?
I have raised a Merge Request (MR) to address the TypeError that occurs when in view Items per page is left empty. This issue was causing unexpected behavior, and the MR ensures proper handling of such cases to prevent errors.
Looks like issue In the Entity Browser module, the iFrame size (height and width) is set to empty by default. To ensure proper functionality and consistent display, it is necessary to set default values for the iFrame's height and width when these fields are left empty. According need to create issue for Entity-browser module. working on this will attach ticket here..
Hi Zeeshan,
I tried reproducing the issue on version 11, and it’s working fine by default (the cross icon is visible). Please try setting up a fresh environment and check if the issue persists. There's no need for a patch at the moment. Also, verify if there’s any conflict with other modules.
Hi, I tested with a special character like "O&O," and noticed that the output is incorrect. Some text is entirely missing. The issue occurs because the & in "O&O" is treated as an unescaped entity in XML. Merge Request (MR) #31 resolves this issue for me.
Looking on this issue..
I'm unable to reproduce the issue. Could you please upload an image or provide a reference for clarity?
kushagra.goyal → created an issue.
Hi, as i mentioned in last comment, not able to see any errors in drupal logs. When we are hitting 'Save' button (blue icon from drupal). there is one API called which is https://uat.startupindia.gov.in/sih/dxpr_builder/ajaxtoken=rywoK8LvktEiE... which comes under 'dxpr_save_container' AJAX request call.
but this gives us '403 Forbidden' as a response. previously i was thinking it was a permission issue because i was using free license of dxpr. but i notice that it sometimes working but mostly didn't. so i have also tried with purchased license but didn't get success on it.
Hi, we are not getting any error in Drupal log, it think it is because this issue not from Drupal side, we just got red warning error and when we tried to save dxpr changes by licking on blue save icon and in network tab an api getting failed (image attached). so there will be error somewhere else...
The thing is we are not getting any error in local. this reproducible on live (uat, dev) sites.
kushagra.goyal → created an issue.
Applied the MR changes on local, it is working fine and changes are working fine and now Pagination is now looking good. Attached before and after images for reference. Hence RTBC+1..
Issue reproduced and applied MR !6 changes on local for missing php tag, changes applied successfully and works fine now. Hence RTBC+1..
Applied MR !57 changes on local, it fix the issue successfully and working fine. Now there is no space is there before before full stop, comma. Attached Before and After image for reference. Hence +1 RTBC..
Hi @elber, Thanks for patch. I have applied the patch and tested on local it is resolving the issue. Hence +1 RTBC...
I have verified that MR !50 resolving the issue of image is not being uploaded which is grater than 15MB, No other issue observed Adding Before and After images for reference. Hence +1 RTBC.
And @sundarraj.p you can take reference of this documentation to test fixes - https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... →
Hi @yustinTR for patch, #30 patch looks good to me, applied successfully and test changes on local it is now compatible and working fine for me. Hence green flag to RTBC+1...
#8 patch is not applying because the file name is different i have checked the branch as well so updating the patch along with interdiff, working fine and it resolve the issue..
Reviewed on this issue and reproduced. After applying the patch error got resolved successfully. Attached before and after screenshots. Good to move RTBC..
After applied the patch issue got fixed and now successfully compatible with D10. Attached before and after screenshot for reference. Hence RTBC+1..
Updating patch again as above mentioned patch in #13 have some issues.
After removing the description there is no longer necessary to write tests for description and test-cases as encountered failures in patch #11, So according updating the Patch to resolve failure.
Thanks..
Reviewed and Applied changes of #4 in local. It creates Schedule maintenance disable field, Attached Before and After screenshots for reference. RTBC+1..
In #2 there is a test-case failure So, Adding a updated patch for fixing failure test-cases. Attached the patch plz review.
Patch #3 is applying correctly and it solves the offset error but i observed that Changing the value of the "slack app" field is not triggering update Ajax of the form, So accordingly i have update a event and verified it is working fine now.
Please review..
Verified the latest patch and after applying #4 patch it is working fine. For reference attaching before and after screenshots.
i have reviewed the patch it's working correctly as before it was typo error. and i have checked previously it was giving null but now it is working fine. Hence moving to RTBC..
I have looked to this issue, MR!375 is resolving the issue as replacePlain do not contain Markup Involvement so, it doesn't convert special char to html markups, hence works as expected, Adding before after screenshots for reference..
As per the comment #7 there was some merge conflicts in MR!2 so for resolve that issue i have raised new MR!4. Hence moving to needs review..
kushagra.goyal → made their first commit to this issue’s fork.
I reviewed the issue and this is reproduced for me. After applying the patch issue got resolved. and it's working successfully fine, for additional here i am attaching Screenshots and moving this to RTBC.
Thanks...
kushagra.goyal → created an issue.
I review the patch associated with this issue, and it is working flawlessly. after applying patch #2 module is not now compatible with Drupal 10, Attached screenshot after applied a patch. Hence moving to ahead as RTBC
kushagra.goyal → made their first commit to this issue’s fork.
Hi @markdorison, i have reviewed the MR at #2. Verified all the changes attached in MR. working fine no issue has been observed on this is working as expected. Hence moving to RTBC...
MR !13 is applying correctly. no other issues not observed as it is working as expected. module is compatible with D10 Hence moving to RTBC. screenshot Attached..
Reviewing this issue...
Patch created in #2, Resolving issue and works as expected, Needs more eyes to view on that, Moving to Needs Reviews.
kushagra.goyal → created an issue.
Hi @rajan, this works. Thanks for really quick response. Really appreciated..
kushagra.goyal → created an issue.
#3 working perfectly for me instead of applying patch, thanks...
Thank you so much @salmonek for addressing this bug so quick. Your quick response is greatly appreciated...
kushagra.goyal → created an issue.
Last #21 was having some git error, updating with the new patch.
re updating the patch and and addressing CCF also attaching inter_diff along with it.
applying a patch to resolve all the PHP coin
kushagra.goyal → created an issue.
There was a lot of messed up at above and i made little alterations in the patch path, so updating patch along with interdiff file.
Updating #17 interdiff file.
Hi @smustgrave, there is a lot of changes on #15 and i verified by applied #11 patch but on that any of the tokens are not visible in available tokens list. that patch #11 is applying but not working. As i've not mention interdiff file, so attaching now...
Applying the patch for the the current issue, its work alright, Please review.