Problem/Motivation
In #3258248: onMount makes unpaginated API request, making PB unusable, @bnjmnm identified that the old fixture is causing problems, and a fast track solution to allow testing would be to update the fixture. We updated it in #3259657: Update project fixture and it appears to be best to update again.
Steps to reproduce
Proposed resolution
I did the following.
1. Launched a drupalpod with the project.
2. Renamed the project_browser_hacky_fixture_maker() to project_browser_update_9004().
3. Visited update.php.
4. Waited around.
5. Downloaded the updated project fixture from fixtures/project_data.fixture
6. Providing that in an MR here
Problem/Motivation
Steps to reproduce
Proposed resolution
Remaining tasks
- ✅ File an issue about this project
- ☐ Addition/Change/Update/Fix to this project
- ☐ Testing to ensure no regression
- ☐ Automated unit/functional testing coverage
- ☐ Developer Documentation support on feature change/addition
- ☐ User Guide Documentation support on feature change/addition
- ☐ Code review from 1 Drupal core team member
- ☐ Full testing and approval
- ☐ Credit contributors
- ☐ Review with the product owner
- ☐ Release
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#4 | Screenshot 2022-02-15 at 19.13.06.png | 204.5 KB | Gábor Hojtsy |
Issue fork project_browser-3264474
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
Gábor HojtsyOn a quick drupalpod, it was failing with
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'author' cannot be null
We can work around that with a cast to string in the import. Not sure yet why would the sample data end up with empty authors, but its sample data, so it will not last for the final code.
Comment #4
Gábor HojtsyOk this works fine on manual testing too.
Comment #6
chrisfromredfinThank you Gabor!