A maximum of 4 columns leave a lot to be desired when you have 150-200 subscriptions, they take up too much width real estate on my paltry 1080p monitor. I would love for the option of 8 or 10 videos per row.

Issue

16 files has some sort of Sugar Pro references in code as comments.
Those should be removed

Steps to Reproduce

Try the search with BEGIN: pro
https://github.com/salesagility/SuiteCRM/search?q

Bug / Feature Request

Work Environment

Problem Description

There are no longer any default dashboards

Possible Solutions

Add the default da

Description

When creating proposals users can access to a proposal dashboard.

There is shown a graph with the evolution of support. The dashboard includes recommended actions that the user can set as 'done', and then will be marked as a red point that date on the previous graph. When the graph shows more than one year, the marked point is shown in the day/month of each year.

As anothe

From the readme, section on Package status:

Currently, METADATA has a tag system but not all package authors use it, making it harder for lay users to know if the package maintenance is active or not.

I don't know how to do this, please add a link, or small tutorial. I'd like to do it.

Should have been done a long time ago:

• How to deploy
  • Inboxen/Inboxen#98
• Admin guide
• Update settings.ini docs

would be a nice feature...

see tine20/vobject@24f9362

🎩 Description

The Spanish Ley Orgánica de Protección de Datos de Carácter Personal specifies that users who are asked for personal information must be informed about how to exercise their rights to Access, Rectify, Cancel, and Oppose (ARCO) personal information about themselves:

https://es.wikipedia.org/wiki/Ley_Org%C3%A1nica_de_Protecci%C3%B3n_de_Datos_de_Car%C3%A1cter_Personal_

Context

A number of elements on the viz editor are half baked or not optimally implemented - the user ends up having to read extra, often redundant text or looking at over emphasized/unnecessary elements - which means a slower viz-building workflow
This need not be done now, but I document them just so we don't forget about them

Idea/proposal

Clearly indicate "Advanced" state;

• Add base64 cert in the doc
• Add small word about the ssl breaking stuff (pip)
• Add something about supervisor

We wrote this code before we started the practice of writing ADRs, so this has none at the moment. We could add some to clarify the design intent.

The discussion in #53 is one example—we haven't currently explicitly describe the error detection and reporting design. But there are many others.

Hey,
could you please translate all documentation to english?

run build command in MortalClient folder and keep getting this error, I am totally new to VS, so have no idea what's wrong here

• Edu. program: standards
• Division: regulations
• Edu. program profile: rest of

Each document type definition must contain some kind of mask (set of flags) to control to which entities it relate/apply.

In comment.js wird der Autor per .html() gesetzt. Man sollte da den -Tag selber aus den Daten vom JSON zusammen bauen, damit man auch Farbe und Profilurl machen kann.