TryGhost/Ghost
1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2024-12-02 08:13:34 +03:00
Code Issues Projects Releases Wiki Activity
e6254bbb93
Ghost/ghost/admin/app/components/members/list-item.hbs

68 lines
3.3 KiB
Handlebars
Raw Normal View History

Fixed scrolling issues on members table (#19833) ref DES-86 Set fixed widths for different columns on the Members table specifically, so content does not jump up & down anymore as you scroll down the page. --------- Co-authored-by: Peter Zimon <peter.zimon@gmail.com>
2024-03-11 19:32:10 +03:00
<tr data-test-list='members-list-item' data-test-member={{@member.id}} class="gh-members-list-row">
🐛 Fixed members breadcrumbs when not coming from analytics fixes https://github.com/TryGhost/Team/issues/2404 This change introduces a new 'post' query parameter to the members and member routes. Previously, the members route would check if the previous route was the analytics page, and then show the breadcrumbs to go back to the analytics page. But when navigating to the members page from the menu, we don't want to show the breadcrumbs. To accomplish this, the routes that point to the members page from the analytics page now specifically pass on the post id in the query parameters. The query parameter is then passed on from the members page to the member page. `directlyFromAnalytics` is still used in the member route, to know wheter we came from the members page or from the analytics page (changes the breadcrumbs). This doesn't need to go via a query parameter (figured that would make the url too long/complex). The resetController method is now implemented and resets the filter and/or fromAnalytics post id if required (when going from members to member, we don't want to reset it because the we would lose the filter going back).
2023-05-04 12:11:08 +03:00
<LinkTo @route="member" @model={{@member}} @query={{@query}} class="gh-list-data" data-test-table-data="details">
Fixed scrolling issues on members table (#19833) ref DES-86 Set fixed widths for different columns on the Members table specifically, so content does not jump up & down anymore as you scroll down the page. --------- Co-authored-by: Peter Zimon <peter.zimon@gmail.com>
2024-03-11 19:32:10 +03:00
<div class="flex items-center gh-members-list-name-container">
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
<GhMemberAvatar @member={{@member}} @containerClass="w9 h9 mr3 flex-shrink-0" />
<div class="w-80">
<h3 class="ma0 pa0 gh-members-list-name {{unless @member.name "gh-members-name-noname"}}">{{or @member.name @member.email}}</h3>
{{#if @member.name}}
<p class="ma0 pa0 middarkgrey f8 gh-members-list-email">{{@member.email}}</p>
{{/if}}
</div>
✨ Added Members Filtering feature no-issue This adds the ability to apply complex filters to members, as well as to perform bulk actions on the filtered set, including unsubscribing, adding & removing labels.
2021-10-01 13:04:56 +03:00
</div>
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
</LinkTo>
{{#if this.hasMultipleTiers}}
🐛 Fixed members breadcrumbs when not coming from analytics fixes https://github.com/TryGhost/Team/issues/2404 This change introduces a new 'post' query parameter to the members and member routes. Previously, the members route would check if the previous route was the analytics page, and then show the breadcrumbs to go back to the analytics page. But when navigating to the members page from the menu, we don't want to show the breadcrumbs. To accomplish this, the routes that point to the members page from the analytics page now specifically pass on the post id in the query parameters. The query parameter is then passed on from the members page to the member page. `directlyFromAnalytics` is still used in the member route, to know wheter we came from the members page or from the analytics page (changes the breadcrumbs). This doesn't need to go via a query parameter (figured that would make the url too long/complex). The resetController method is now implemented and resets the filter and/or fromAnalytics post id if required (when going from members to member, we don't want to reset it because the we would lose the filter going back).
2023-05-04 12:11:08 +03:00
<LinkTo @route="member" @model={{@member}} @query={{@query}} class="gh-list-data" data-test-table-data="status">
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{#if (not (is-empty @member.status))}}
<span>{{capitalize @member.status}}</span>
{{else}}
<span class="midlightgrey">-</span>
{{/if}}
<div class="midgrey">{{this.tiers}}</div>
</LinkTo>
✨ Added Members Filtering feature no-issue This adds the ability to apply complex filters to members, as well as to perform bulk actions on the filtered set, including unsubscribing, adding & removing labels.
2021-10-01 13:04:56 +03:00
{{else}}
🐛 Fixed members breadcrumbs when not coming from analytics fixes https://github.com/TryGhost/Team/issues/2404 This change introduces a new 'post' query parameter to the members and member routes. Previously, the members route would check if the previous route was the analytics page, and then show the breadcrumbs to go back to the analytics page. But when navigating to the members page from the menu, we don't want to show the breadcrumbs. To accomplish this, the routes that point to the members page from the analytics page now specifically pass on the post id in the query parameters. The query parameter is then passed on from the members page to the member page. `directlyFromAnalytics` is still used in the member route, to know wheter we came from the members page or from the analytics page (changes the breadcrumbs). This doesn't need to go via a query parameter (figured that would make the url too long/complex). The resetController method is now implemented and resets the filter and/or fromAnalytics post id if required (when going from members to member, we don't want to reset it because the we would lose the filter going back).
2023-05-04 12:11:08 +03:00
<LinkTo @route="member" @model={{@member}} @query={{@query}} class="gh-list-data" data-test-table-data="status">
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{#if (not (is-empty @member.status))}}
<span>{{capitalize @member.status}}</span>
{{else}}
<span class="midlightgrey">-</span>
{{/if}}
✨ Added Members Filtering feature no-issue This adds the ability to apply complex filters to members, as well as to perform bulk actions on the filtered set, including unsubscribing, adding & removing labels.
2021-10-01 13:04:56 +03:00
</LinkTo>
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{/if}}
{{#if @newsletterEnabled}}
🐛 Fixed members breadcrumbs when not coming from analytics fixes https://github.com/TryGhost/Team/issues/2404 This change introduces a new 'post' query parameter to the members and member routes. Previously, the members route would check if the previous route was the analytics page, and then show the breadcrumbs to go back to the analytics page. But when navigating to the members page from the menu, we don't want to show the breadcrumbs. To accomplish this, the routes that point to the members page from the analytics page now specifically pass on the post id in the query parameters. The query parameter is then passed on from the members page to the member page. `directlyFromAnalytics` is still used in the member route, to know wheter we came from the members page or from the analytics page (changes the breadcrumbs). This doesn't need to go via a query parameter (figured that would make the url too long/complex). The resetController method is now implemented and resets the filter and/or fromAnalytics post id if required (when going from members to member, we don't want to reset it because the we would lose the filter going back).
2023-05-04 12:11:08 +03:00
<LinkTo @route="member" @model={{@member}} @query={{@query}} class="gh-list-data middarkgrey f8 {{unless @member.name "gh-members-list-open-rate-noname"}}" data-test-table-data="open-rate">
Cleaned up member filters (#15784) fixes https://github.com/TryGhost/Team/issues/2134 fixes https://github.com/TryGhost/Team/issues/2133 - Moved all filters to separate files to make the filter component a lot more readable and easier to maintain. - Removed long switch style code from hbs for filter column values - Filters for features that are disabled (such as open tracking, click tracking or member attribution) are now hidden when they are disabled - The open rate column in the members table is now only visible if open tracking is enabled
2022-11-10 13:05:12 +03:00
{{#if (not (is-empty @member.emailOpenRate))}}
<span>{{@member.emailOpenRate}}%</span>
{{else}}
<span class="midlightgrey">N/A</span>
{{/if}}
</LinkTo>
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{/if}}
✨ Added member's geographic location to admin no issue - added `geolocation` attribute to member model with json-string transform - prevent geolocation from being sent back to the API in member serializer - add "Location" column to members list - if country is "US" then display "{State}, US" otherwise show full country name such as "United Kingdom" - displays "-" if no geolocation data has been collected for the member
2020-02-27 15:56:26 +03:00
🐛 Fixed members breadcrumbs when not coming from analytics fixes https://github.com/TryGhost/Team/issues/2404 This change introduces a new 'post' query parameter to the members and member routes. Previously, the members route would check if the previous route was the analytics page, and then show the breadcrumbs to go back to the analytics page. But when navigating to the members page from the menu, we don't want to show the breadcrumbs. To accomplish this, the routes that point to the members page from the analytics page now specifically pass on the post id in the query parameters. The query parameter is then passed on from the members page to the member page. `directlyFromAnalytics` is still used in the member route, to know wheter we came from the members page or from the analytics page (changes the breadcrumbs). This doesn't need to go via a query parameter (figured that would make the url too long/complex). The resetController method is now implemented and resets the filter and/or fromAnalytics post id if required (when going from members to member, we don't want to reset it because the we would lose the filter going back).
2023-05-04 12:11:08 +03:00
<LinkTo @route="member" @model={{@member}} @query={{@query}} class="gh-list-data middarkgrey f8 {{unless @member.name "gh-members-geolocation-noname"}}" data-test-table-data="location">
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{#if (and @member.geolocation @member.geolocation.country)}}
{{#if (and (eq @member.geolocation.country_code "US") @member.geolocation.region)}}
{{@member.geolocation.region}}, US
{{else}}
{{#if @member.geolocation.country}}
{{@member.geolocation.country}}
✨ Added Members Filtering feature no-issue This adds the ability to apply complex filters to members, as well as to perform bulk actions on the filtered set, including unsubscribing, adding & removing labels.
2021-10-01 13:04:56 +03:00
{{else}}
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
<span class="midlightgrey">Unknown</span>
Added static result table for members filtering - Added horizontal scrolling, fullscreen table component. - Mocked multiple columns in the members result list. Alpha feature.
2021-07-22 16:47:01 +03:00
{{/if}}
✨ Added Members Filtering feature no-issue This adds the ability to apply complex filters to members, as well as to perform bulk actions on the filtered set, including unsubscribing, adding & removing labels.
2021-10-01 13:04:56 +03:00
{{/if}}
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{else}}
<span class="midlightgrey">Unknown</span>
{{/if}}
</LinkTo>
Added static result table for members filtering - Added horizontal scrolling, fullscreen table component. - Mocked multiple columns in the members result list. Alpha feature.
2021-07-22 16:47:01 +03:00
🐛 Fixed members breadcrumbs when not coming from analytics fixes https://github.com/TryGhost/Team/issues/2404 This change introduces a new 'post' query parameter to the members and member routes. Previously, the members route would check if the previous route was the analytics page, and then show the breadcrumbs to go back to the analytics page. But when navigating to the members page from the menu, we don't want to show the breadcrumbs. To accomplish this, the routes that point to the members page from the analytics page now specifically pass on the post id in the query parameters. The query parameter is then passed on from the members page to the member page. `directlyFromAnalytics` is still used in the member route, to know wheter we came from the members page or from the analytics page (changes the breadcrumbs). This doesn't need to go via a query parameter (figured that would make the url too long/complex). The resetController method is now implemented and resets the filter and/or fromAnalytics post id if required (when going from members to member, we don't want to reset it because the we would lose the filter going back).
2023-05-04 12:11:08 +03:00
<LinkTo @route="member" @model={{@member}} @query={{@query}} class="gh-list-data middarkgrey f8" data-test-table-data="created-at">
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{#if @member.createdAtUTC}}
<div>{{moment-format (moment-site-tz @member.createdAtUTC) "DD MMM YYYY"}}</div>
<div class="midlightgrey gh-members-list-subscribed-moment">{{moment-from-now @member.createdAtUTC}}</div>
{{/if}}
</LinkTo>
🐛 Fixed members table showing dates in UTC rather than site timezone closes https://github.com/TryGhost/Ghost/issues/13611 - added `{{moment-site-tz}}` helper for transforming any date into the selected site's timezone - allows for use on any date in the system - keeps transformation a display-level concern - updated members table to use `{{moment-site-tz}}` to transform the date before display
2022-03-03 19:16:29 +03:00
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{#each @filterColumns as |filterColumn|}}
🐛 Fixed members breadcrumbs when not coming from analytics fixes https://github.com/TryGhost/Team/issues/2404 This change introduces a new 'post' query parameter to the members and member routes. Previously, the members route would check if the previous route was the analytics page, and then show the breadcrumbs to go back to the analytics page. But when navigating to the members page from the menu, we don't want to show the breadcrumbs. To accomplish this, the routes that point to the members page from the analytics page now specifically pass on the post id in the query parameters. The query parameter is then passed on from the members page to the member page. `directlyFromAnalytics` is still used in the member route, to know wheter we came from the members page or from the analytics page (changes the breadcrumbs). This doesn't need to go via a query parameter (figured that would make the url too long/complex). The resetController method is now implemented and resets the filter and/or fromAnalytics post id if required (when going from members to member, we don't want to reset it because the we would lose the filter going back).
2023-05-04 12:11:08 +03:00
<Members::ListItemColumn @member={{@member}} @filterColumn={{filterColumn}} @query={{@query}} />
Fixed member ProxyObject from sparse array leaking out of members list (#15565) no issue - the `ella-sparse-array` dependency used for the sparsely populated list on the members screen creates ProxyObjects that wrap the underlying member model instances meaning the forced use of `.get()` and `.set()` required by ProxyObject was leaking through to other areas of the app causing a mismatch in code patterns - moved the loading state for each member into a separate component and put the loading conditional directly inside the `{{#each members}}` block so that we can pass the real model instance through to components via `{{member.content}}` rather than passing the ProxyObject wrapper, avoiding unexpected errors when not using `.get()` and `.set()` on member arguments
2022-10-07 19:03:45 +03:00
{{/each}}
Improved Email newsletter settings page (#2207) Updated email newsletter settings - Added toggle to disable email newsletters - Hides email related UI when email is completely turned off - Rearranged email newsletter settings - Added publish-menu preview in - Changed default-recipients setting - Updated publish-menu to show Publish as default action - Removed the confirmation modal during publishing when no emails are intended to be sent
2022-01-27 14:40:11 +03:00
</tr>
Reference in New Issue Copy Permalink