🇺🇸United States @anicoto

This engagement is in progress but almost ready to be completed.

The program manager as requested a review, and we have found some missing information:
[ ] Issues Links have been added to the final report but not in the appropiate space
[ ] Blogpost is missing
[ ] Engament status need to be moved to finished state

anicoto → created an issue.

This engagement is in progress but almost ready to be completed.

The program manager as requested a review, and we have found some missing information:
[ ] Issues Links have been added to the final report but not in the appropiate space
[ ] Blogpost is missing
[ ] Engament status need to be moved to finished state

anicoto → created an issue.

anicoto → created an issue.

anicoto → created an issue.

Merged

I think this is done, will continue the goverment use case on https://www.drupal.org/project/ixp/issues/3507630 📌 IXP for Government Active

@camoa Please assign credits

@camo please assign credits

Reviewed and is working as expected

@camos Plese assign issue credits

A quote from the IXP:

"It's been an immersive experience that has not only solidified my technical skills but also instilled in me the confidence needed to navigate the professional realm of software development."

Testing on Testing engagememnt issue template 📌 Testing engagememnt issue template Active

Final proposal:

-- Review Engagement

Description:

This ticket tracks the review of IXP engagement [CASE NUMBER] for final approval and credit award processing. The engagement has entered "Final Review" state and requires verification that all program requirements have been met.

Engagement Details:

• Organization: [ORGANIZATION NAME]
• IXP Name: [IXP NAME]
• Start Date: [START DATE]
• End Date: [END DATE]
• Total Hours: [TOTAL HOURS]

Review checklist

• [ ] Progress Reports Complete - System shows sufficient bi-weekly progress reports based on engagement duration
• [ ] Final Reports Submitted - Both company and IXP final reports are complete and submitted
• [ ] Required Links Present:
  • [ ] One public blog post by the IXP documenting their experience
  • [ ] At least three contribution links showing the IXP's work on drupal.org
• [ ] Minimum Hours Met - Engagement provided minimum 160 paid hours of work
• [ ] Mentorship Requirements Fulfilled - Documentation confirms mentorship was provided at required ratio (1 hour per 10 hours worked)

Notes

[Space for reviewer to add any observations, concerns, or additional context]

Final Resolution

• [ ] APPROVED - All requirements met, ready for 250 contribution credits award
• [ ] NOT APPROVED - Requirements incomplete, engagement state changed to "Needs Information"

Required Actions

[List specific items that need to be addressed before resubmission]

-- Other

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

anicoto → created an issue.

Add organization link
Add links to IXP profile and mentor profile
Add Blog post
Report total hours

Template proposal:

Description

This ticket tracks the review of IXP engagement [CASE NUMBER] for final approval and credit award processing. The engagement has entered "Final Review" state and requires verification that all program requirements have been met.

Engagement Details

• Organization: [ORGANIZATION NAME]
• IXP Name: [IXP NAME]
• Start Date: [START DATE]
• End Date: [END DATE]
• Total Hours: [TOTAL HOURS]

Review checklist

• [TOTAL] Progress Reports Complete - System shows sufficient bi-weekly progress reports based on engagement duration
• Final Reports Submitted - Both company and IXP final reports are complete and submitted
• Required Links Present:
• One public blog post by the IXP documenting their experience
• At least three contribution links showing the IXP's work on drupal.org
• Minimum Hours Met - Engagement provided minimum 160 paid hours of work
• Mentorship Requirements Fulfilled - Documentation confirms mentorship was provided at required ratio (1 hour per 10 hours worked)

Notes

Final Resolution

Required Actions

- In case the requirements havent been meet list the missing or incluplete information that IXP and/or mentor need to complete.

Proposed sections:

• Description
• Engagement Details
• Review checklist
• Notes
• Final resolution
• Required Actions

<h3 id="summary-problem-motivation">Description</h3>
<h4 id="summary-details">Engagement Details</h4>
<h3 id="summary-requirements">Review checklist</h3>
<h4 id="summary-requirements-notes">Notes</h4>
<h4 id="summary-proposed-resolution">Final Resolution</h4>

<h3 id="summary-remaining-tasks">Required Actions</h3>
<em>- In case the requirements havent been meet list the missing or incluplete information that IXP and/or mentor need to complete. </em>

anicoto → created an issue.

Review completed and approved. All the documentation is in order, including the blogpost and issues credited.

Review completed and approved. All the documentation is in order, including the blogpost and issues credited.

Review completed and approved. All the documentation is in order, including the blogpost and issues credited.

Hi nice to see everybody.;

anicoto → created an issue.

nicxvan → credited anicoto → .

Clarify where to get access to push code.

Updated title for major clarity

There just to be a module that solves this issue https://www.drupal.org/project/jswatchdog → . Even if is not secure, as mentioned https://www.drupal.org/project/drupal/issues/727278#comment-5417442 ✨ Add watchdog interface for javascript code to use Active

Maybe we should not have it on in production for a long time but it will work for a short period.

I found this error on a kind of new website with Drupal 10.5.1. But, I think we should probably test this on a clean set up and using D11 to check if there are other modules involved.

I added a Screen Shop where the user gets stock.

anicoto → created an issue.

I think you could change the location of a state but you may be able to customize the location of the pins. You will need a content type and a view.

In the module description there is a mention to the styled google views module, maybe this is what is missing but I could not find it.

anicoto → created an issue.

volkswagenchick → credited anicoto → .

Before installing the module, try disabling Page title block from Menu > Structure > Block Layout (/admin/structure/block) Use the block configuration to hide the block on specific use cases.

This usually works for nodes. Other use cases like edit forms and views may have a different way to hide the title.

I may use some help with automatic testing.

Also we should take into account the recommendations in https://www.drupal.org/project/drupal/issues/3326611 →

rachel_norfolk → credited anilu@ → .

This needs revision from project mainteners. The link still broken.

Update details about removing modules on composer and configuration management.

Automatic testing failed because of update to 3.0 branch. Manually applying the patch is working on my project but we need to update the patch and continued testing.

At this moment, I am not sure if this is a long term solution. Open to hear oppinions.

I write a script on composer that removes book core module. For now this should work for anyone that needs a quick fix.

{
    "scripts": {
        "post-install-cmd": [
            "rm -rf web/core/modules/book",
            "@composer drupal:scaffold"
        ],
        "post-update-cmd": [
            "rm -rf web/core/modules/book",
            "@composer drupal:scaffold"
        ]
    }
}

After a few hours of investigation I found that the original function in core book is overriding the Constrain validator from the contributed module. I was able to fix the error by manually deleting core/modules/book.

Not sure how we will solve this issue but, I created a follow up ticket https://www.drupal.org/project/book/issues/3519344 🐛 Cannot save unpublished versions of published content with Layout Builder Active

Last development version for this module has the required validation for $value->book on src/Plugin/Validation/Constraint/BookOutlineConstraintValidator.php

if (isset($value) && !empty($value->book) && !$value->isNew() && !$value->isDefaultRevision()) {

This should be working, but is not. This may be related to the update from core to contrib module.

The primary issue is with the BookOutlineConstraintValidator in the Book module. This validator is designed to prevent changes to book outlines in non-default (draft) revisions.
The key problematic code is in the validate() method of the BookOutlineConstraintValidator class:

public function validate($entity, Constraint $constraint): void {
  // Validate the book structure when the user has access to manage book
  // outlines. When the user can manage book outlines, the book variable will
  // be populated even if the node is not part of the book. If the user cannot
  // manage book outlines, the book variable will be empty, and we can safely
  // ignore the constraints as the outline cannot be changed by this user.
  if (isset($entity) && !$entity->isNew() && !$entity->isDefaultRevision()) {
    /** @var \Drupal\Core\Entity\ContentEntityInterface $original */
    $original = $this->bookManager->loadBookLink($entity->id(), FALSE) ?: [
      'bid' => 0,
      'weight' => 0,
    ];
    if (empty($original['pid'])) {
      $original['pid'] = -1;
    }

    if ($entity->book['bid'] != $original['bid']) {
      $this->context->buildViolation($constraint->message)
        ->atPath('book.bid')
        ->setInvalidValue($entity)
        ->addViolation();
    }
    // Additional validation code...
  }
}

This constraint validator triggers when:

1. An entity exists (isset($entity))
2. The entity is not new (!$entity->isNew())
3. The entity is not the default revision (!$entity->isDefaultRevision())

anilu@ → created an issue.

I have a production D10 website where I successfully moved to the book module. However, I found an Issue with layout builder revisions that does not allows me to save content in draft. I removed the book module and draft estate and revisions are working with Content Moderation. But I do not want to remove the module from production.

This may be related https://www.drupal.org/project/book/issues/2918537 🐛 Cannot save unpublished versions of published content for users without manage book privileges Needs work

anilu@ → created an issue.

Agree

mradcliffe → credited anilu@ → .

Thanks @avpaderno, we are still working on this issue. We are at the mentoring room at Drupalcon Atlantla working on this. The change record is still in draft version but we have completed the requested change to the documentation in https://www.drupal.org/node/161085#readme →

Documentation to complete this ticket can be found in the ticket tags > about tags https://www.drupal.org/list-changes/drupal →