Redesign: pending assemblies#10931
Conversation
… and use this in participatory processes groups
* feature/redesign: Redesign: amendments (#10765)
* feature/redesign: (70 commits) Fix failing specs Redesign sortitions (#10831) Redesign: data toggle (#10886) Redesign: collaborative drafts (#10729) Redesign: pending pages (#10944) Redesign: my account (#10904) use foundation classes instead of default html validation (#10921) Fix failings redesign specs Add gitpod support (#10641) Fix pipeline after #10409 (#10670) Upgrade webpack and other javascript libraries (#10643) New Crowdin updates (#10409) Refactor attachment title (#10103) Fix for exporting hidden moderated proposals (#10630) Fix Exception as admin on a Proposal with meeting author (#10628) Fix: Deleted and hidden comments are exported (#10629) Rename "terms and conditions" to "terms of service" (#10614) Upgrade Graphql to 2.0.19 and Graphql-Api to 3.0.1 (#10606) Standardize the format of the words "they will" (#10617) Fix the spec after word standardization (#10624) ...
|
@decidim/product we'll tackle the child assemblies breadcrumb/navigation in further PRs once we define it, so this doesn't get blocked. |
|
@decidim/product so OK to pass it to maintainers? |
There was a problem hiding this comment.
Hi @entantoencuanto! Just a couple of things more and we're ready:
-
In cards G, change the icon of the number of assemblies and use the one that corresponds to assemblies:
ri-government-line -
Also in g-cards fix the position of the number of assemblies so that it always appears in the same place.

-
The last assemblies activity is not shown, maybe related to the content block? Feel free to move it to another PR if it doesn't apply to this PR.
* feature/redesign: (26 commits) Use the component name in the sidebar title (#11088) Redesign: layout center (#11068) Redesign: display only public users followings in following profile tab (#11051) Redesign: fix cards (#11072) Redesign: remove gcalendar warning (#10999) lock sass-embedded (#11077) Redesign: scopes picker (#11039) Redesign: pending notifications (#10926) Redesign: change the filters style (#11049) Redesign: secondary actions (#11067) Redesign: assembly members page (#10992) Redesign: update default static map size to 300px (#10953) Redesign: visual placeholder cards (#11038) Redesign: fix emoji popup position (#10957) Redesign: enable REDESIGN_ENABLED on ParticipatoryProcesses (#10983) Redesign: opinion buttons (#10998) Display a disabled message button in public profile if user blocks them instead of hidding it (#10984) Redesign: confirm modal Foundation-free (#10978) Redesign: initiatives (#10646) Redesign: surveys (#10922) ...
After doing some research I think I've found the reason. This assembly is a private space and the activities cell hides all the items to users without the permissions to participate in the space. Probably logged in as admin@example.org the user can visit the private space, but no other permissions are granted. If you add admin@example.org as private participant of the assembly the activities should be visible |
|
@carolromero the last comment from Edu is for you |
|
@decidim/product you can check the assemblies breadcrumb https://decidim-redesign.populate.tools/assemblies/edu (#11089) |
carolromero
left a comment
There was a problem hiding this comment.
Hi @entantoencuanto, thanks for looking into this! Actually, as this assembly is configured as private and transparent, it makes sense to show the activity, which any participant can anyway browse.
So I think the expected behavior is:
- Public assembly: anyone sees the assembly, including the last activity.
- (Private) Transparent assembly: anyone sees the assembly, including the last activity.
- Private assembly: only private participants see the assembly, including the last activity.
carolromero
left a comment
There was a problem hiding this comment.
Now it's working ok! thanks @entantoencuanto
If resource does not respond to can_participate? its associated action log should be displayed
🎩 What? Why?
This PR:
📌 Related Issues
Link your PR to an issue
Testing
Describe the best way to test or validate your PR.
📷 Screenshots
Please add screenshots of the changes you are proposing
