-
Notifications
You must be signed in to change notification settings - Fork 1
COR-704: Rebuild AssetFieldType with Shrine #57
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
Conversation
…asset deletion, misc
…generic FileUploader implementation
…e asset support, styling refactors, misc
baa3b6c to
cc5f334
Compare
| @@ -0,0 +1,12 @@ | |||
| .thumbnail-placeholder { | |||
| background-color: #E4E4E4; // TODO: determine how to inherit variables from Cortex. This should be $color-grey-evenlighter | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A separate style library?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arelia That'd do it! It was late that night.. We should get started on that ASAP for V3.
|
@arelia I noticed this as well, and actually added a comment to our code that this 'text uniqueness' feature does not work when you're updating an existing ContentItem's title. This was a pre-existing bug and is being documented in JIRA. Thanks for being thorough, though! |
| @@ -0,0 +1,12 @@ | |||
| .thumbnail-placeholder { | |||
| background-color: #E4E4E4; // TODO: Abstract to cortex-style-base library. This should be $color-grey-evenlighter | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even before the style base for Cortex is founded could you please extract this so we can just copy and paste the variables when the time comes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure - I'll just copy all variables from cortex to cortex-plugins-core, with the expectation that these need to be removed once cortex-plugins-core can pull from a cortex-style-base. Thanks!
|
@toastercup Should we expedite the title bug @arelia mentioned to the next sprint, it seems like something that should be addressed before V2 is released |
|
@ElliottAYoung Yes - there's actually several bugs I uncovered that I'm going to push to be addressed next sprint |
…tyle-base), uppercase thumbnail placeholder text
5385eb9 to
52f03cc
Compare


Purpose
This PR features:
media_titlefunctionality for dynamic path/location. This will be discussed with Justin + team. This feature introduced tech debt with little benefit, and also has pre-existing issues with asset updating.JIRA
https://cb-content-enablement.atlassian.net/browse/COR-704
Steps to Take On Prod
ContentTypesChanges
Changes to setup
.envchanges:HOSTis nowFOG_HOST, to be more explicitHOST_ALIASis used duringContentTypeseeding to configure the CDN for Media AssetsS3_ACCESS_KEY_IDis self-explanatory, and is only for Beta'sAssetFieldType. It was created as a replacement forAWS_ACCESS_KEY_ID, whose naming is too broad for what it's intended for.S3_SECRET_ACCESS_KEYis self-explanatory, and is only for Beta'sAssetFieldTypefor the same reasons asS3_ACCESS_KEY_ID.AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEYcontinue to be used for LegacyS3_BUCKET_NAMEare used both for Legacy and Beta. This can be changed in the future if need be, but right now they share the same credentials.Architectural changes
Migrations
Library changes
cortex-plugins-coreneeds to be bumped prior to mergingSide effects
Screenshots
Before
N/A
After
N/A
QA Links
http://web.cortex-1.development.c66.me/ (
admin@cortexcms.org/welcome1)How to Verify These Changes
Specific pages to visit
Steps to take
Responsive considerations
Relevant PRs/Dependencies
cortex-cms/cortex#488
Additional Information