You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All users on the system should use a profile pic pulled in from gravatar. Previously we did allow local uploads of images but they were abused unfortunately. Both inappropriate content as well as steganography. (I know, bad guys = kill joys. I'm just the messenger.)
Further corp-memberships for many organizations are private. They don't want the world to know who is supporting them and by how much as it hurts negotiations with other sponsors (sponsorships frequently get bundled with corp membership package as added value.) While double entry, it does keep the site admin's in control of their public face.
One option would be to use the directories module to highlight the ones you want highlighthed and omit the others. Example directories module use: http://www.sfbig.org/directories/
The bigger issue here is that entities were not converted properly when rewritten open source. Entities are the HEART of Tendenci and they are currently broken. The former implementation that needs to be rebuilt is described in detail here:
A corporate member by definition is an entity (or should be) under a pointer system that points to a higher level entity which might be a category of sponsors. Every group should be bound to an entity. This is needed for roll up financial reporting for multi-site configurations.
To take this further in the original framework "Entities" also provided for multi-sites and filtered content for those sub-sites. Django does this natively with the "Sites" variable but Tendenci doesn't use that currently either. Tendenci needs to use entities for international organizations and subchapters to allow multiple sites to maintain their own brand identity and pull in selective content. Groups to filter the content and entities to determine if the child-site is allowed/permission to that object.
Sorry to go all big picture - that is just how I designed the structure and it worked great. We have deviated (my fault) and are now facing limitations such as "families" for donor management which need to return.
Add a logo display option for corporate members.
Pretty simple and a glaring omission.
The Corporate member must be able to upload and/or change the logo from their member control panel.
The logo should save locally.
The logo should be displayed on the corporate member's public profile.
The text was updated successfully, but these errors were encountered: