forked from yalesites-org/yalesites-project
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test merge from other branch into master #52
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… same as content spotlight
…atch regular content spotlight
…max-referenced-items YALB-959 min max referenced items
… and spotlight-portrait
…dates Actions: update existing release PRs
…tent" in top menu (yalesites-org#530) * fix(YALB-1663): deleting default section does not error There was a problem where a user deleted the default content section. Upon saving this, they were unable to go back in to modify the page in layout builder. This was due to an access check issue in section_library. This patch fixes this so that the user could edit the page in layout builder again. * feat(YALB-1663): allow "Add Section" after Title and Metadata layout_builder_lock was disallowing sections to be added after the Title and Metadata section of a Page, or the bottom content section of a Profile. Since we are now allowing them to remove the default content section, they will need a way to add a new section, which this provides. "Add Section" is now displayed below in these cases.
We need the ability to set the environment dynamically when calling this script, so change to using a variable and fall back to dev if it isn't set.
…stall_env feat: content on install to environments other than dev
YALB-1686: Allow rtf file uploads
…5-1676-spotlights YALB-1674: add new content spotlight portrait component | YALB-1675: Feedback: Content Spotlight - inline/offset image dial | YALB-1676: Feedback: Content Spotlight portrait image treatment
…elease-pr fix: update existing release PRs correctly without errors
…elease-pr fix: filter out merge commits that do not have a PR (actions create PR workflow)
…alesites-org#535) In updating develop from master, the allowed_formats were overwritten from before. This re-establishes this for new quicklink blocks.
…elease-pr fix: update jq condition to properly filter merge commits from diff
YALB-1513: Improve help text for title/heading control fields
yalesites-org#525) * fix(YALB-1685): update bundle to always be main In this bug, we finally found the issue to be that these nodes are in a different bundle, missing the CTA field all together. If they were main, it would display as it should as they are defined. Since we do not have control over which field definitions get loaded, and it seems to use the bundle to load them, this updates any that have been mis-labelled to main so that nodes could be edited again. @co-authored-by Berger, Marc <@codechefmarc> * fix(YALB-1685): do not directly access the database While the previous implementation worked, it felt strange directly accessing the database. This goes through Drupal objects to accomplish the same result, which feels a bit better in case there is any hooks or background processing that Drupal does in these cases. * revert(YALB-1685): extra menu items on node sidebar This reverts the extra menu items on the node sidebar, which is causing the error due to the bundle being one such that the field definitions do not contain the CTA mega menu top level title field. It also reverts the possible fix to update the bundle to main on cache refresh. Now, the only way to add this field data is to do so via the Manage Main Menu view, which works as intended. * fix(YALB-1667): find parent page title for basic menu This sets up component library twig to be able to retrieve the node title later if criteria is met that makes it use node_title. This attempts to not touch the mega menu logic, hence the new variable. See component-library-twig/components/02-molecules/menu/_yds-menu-item.twig
…ting help text (yalesites-org#521) * feat(YALB1444): allow front page link autocomplete * feat(YALB-1397): updating help text * feat(YALB-1588): media links redirect to files (yalesites-org#522) * feat(YALB-1588): media links redirect to files * feat(YALB-1558): grant permissions to view media * feat(YALB-1368): allow links to open in a new tab (yalesites-org#523) * feat(YALB-1368): allow links to open in a new tab * feat(YALB-1368): update composer file to pin module * fix: fix typo
vinmassaro
force-pushed
the
release_pr_updates
branch
from
January 22, 2024 21:28
1e67691
to
9406d45
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull requests
Changes without a pull request: