saltcorn / saltcorn Goto Github PK

When rendering table content as a link, the link points to a page that doesn't exist, link should rather open a modal or a Show/Edit view of the item clicked.
Example :

After click

Or do some else to avoid the exceptions on run time like:

User
TypeError: Cannot read property 'type' of undefined
at new Field (/usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/models/field.js:13:12)
at /usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/base-plugin/viewtemplates/list.js:118:17
at Array.forEach ()
at Object.get_state_fields (/usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/base-plugin/viewtemplates/list.js:116:19)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async View.get_state_fields (/usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/models/view.js:41:14)
at async View.get_state_form (/usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/models/view.js:207:22)
at async /usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/server/routes/view.js:29:26
A report has been logged and a team of bug-squashing squirrels has been dispatched to deal with the situation.

This is very intesting to create solutions like helpdesk or crm

This will be great functionality to improve usability of . Also it can be implemented for Rich Text Editor.

1. Regular backups should be performed on a schedule.

2. Regular backups should be stored in filesystem.

3. Parameters for backup: schedule (aka crontab 0 0 * * * - everyday at 00 00), path to store backup files

4. Parameters should be saved in saltcorn confuguration.

How could I translate Saltcorn? Is there a way to create translations besides hardcoding, so that different users could select different languages?

version 0.2.2
I think that we need to support Date Format like YYYY-MM-DD e.g. for output Date values in views.

1. I suggest to have ability to define common data / time formats for particular tenant.

2. Also in concrete view for cocnrete date field it will be great to have ability to set up date format.

When we add fields to an existing table, it is desirable to be able to quickly add those fields to views.
Currently I forced to recreate views from scratch to solve this.

Docker image is an easy installation method for testing and production, thanks

I suggest to add link to subdomain site and link to open information about tenant in tenant list

I suggest to add check for amounts of login failure and add capture input after X failure attemps on login screen.

The amount of login failures has to be defined in configuration.
The default value is 3.
If it equals to zero than amount hasnt limit.

Imho The amount of login attempts and capture are important protection from bots and hackers.

Currently threre are few parts are uncovered.

Please update wiki https://wiki.saltcorn.com/view/ShowPage?title=Saltcorn%20Wiki%20Front%20Page for uncovered parts.

I can help, but I do not have permission to edit the wiki, and also not everything works for me, so there is not always an understanding of how it should work.

Hello,
Right now dates are shown this way :
2020-01-01T00:00:00.000Z which is understandable, but for most people will not get it, I saw you're using moment.js in saltcorn, so it wouldn't be complicated to get a more human readable date like 2020-01-01 00:00, what would be better is to let users choose the formatting according to their languages or to their needs.
Thanks 😊 I tried to do it myself but iam afraid to break everything .

Related to #264.

The problem - the login screen shows language that browser set as default.

Scenario to repeat:

1. Change user language in user settings from default language for your browser

2. Logout

3. I'll see login screen in default language for browser

My suggestion is to add language picker to login screen to allow change language on login screen or save in cookies current language.

Most of controls are disabled.

Something like

It will help to understood model for admins of saltcorn,

Currently only email used to identify user of Saltcorn site.

The more familiar practice that user also can define user name or nickname and use it as login name.

Login name should be unique.

Idea to improvement.

Add Calendar view to Saltcorn.

Add ability to generate link for this field.
This link will open the Edit View for this record.

I just want to give some valuable support for the project. So ill try to develop mysql support on weekends.

version 0.2.2

I think than Wiki has to be open https://wiki.saltcorn.com/view/ShowPage?title=Saltcorn%20Wiki%20Front%20Page as root page
But for authorized user (saanchos at gmail.com. e.g.) currently wiki root page redirected to the list of pages.

The idea is to add translations packs or something similar to get ability to install/update language packs using saltcorn store.

There are example of comment:
https://blog.saltcorn.com/view/Full%20Post?title=Saltcorn%200.2%20released

1. My suggestion is as minumum to ask user for email and store it into saltcorn db without showing it to ordinar users.

2. Also addition of captcha is good for this.

3. In ideal situation the user should be authorized to post comments.

This is important currently because a lot of bots / jokers who likes to add obscene or offensive comments.

For example we have table Enimals with EnimalType in ('Cats','Dogs')

And we need to have view where only Dogs can be shown.

This "where" condition has to be configured in View configuration wizard (tabler) and such view allways shows only records that are satisfy to "where" condition.

@glutamate How to diagnost this?
Where logs are saved?

Particularly I need to update language translation but in common we need description, ideally mechanics to do core update.

Also its impossible to change email here

Really needs for speed up work

This is idea for improvement.

I suggesting to add few optional fileds to https://saltcorn.com/tenant/create

The suggested fields:

1. Site name (currently accessable in Configuration\Site Name)

2. Site admin email -> will be saved in tenant information at main site and available in [/tenant/list] . See issue #296
   In future also we can add:
   2.1. copy admin user info from main site to tenant -> this will allow to create tenant with predefined admin user
   2.2. send email to admin user with invitation to work with tenant

3. Site logo (currently accessable in Configuration\Site logo)

4. Default language (when it will be in Configuration)

5. Choose common "Visibilty" of App.

Also add description that fields are optional and can be defined later in Configuration.

May be some other fields can be suitable.

Also I think that Configuration\basic url need to be set by default to Application name (subdomain name) after creation of site.

P.S. Also we need to test creation of subdomain with cyrilics characters - i ll do this later.

version 0.2.2

I saw huge potential in Saltcorn as simple to use ecommerse platform.

It will be good to have ability to switch between languages for Saltcorn.

The prefered language can be saved as user settings attributes.

If user forgot his password then will be good to give to him ability to reset password via email.

Also in case if email server integration is not defined or just allways show message like "Contact your system administrator admin at site.com" when user lost password

The idea is to have ability to quickly do clone of current record of table data.

This is can be combination of Action in Row with Link to other view.

For example if we will base on "Link to other view":

So has to be defined additional control "Action" where Admin can choos:

• Edit
• Clone

If Admin choose Clone than:

When User click to clone
The Saltcorn opens RecordEdit view (in example IssueTypeEdit) populated with data from current record.

User changes data and click to Save.

The Saltcorn creates new record based on user input,

Currently saltcorn.com is constant.

It will be great to add button for create new tenant (/tenant/create) to tenant list view.

Just suggest to add this functionality.

1. On login screen needs to be a link to send email to user email for reset / recover user password.

2. In user management http://134.0.115.202:3000/useradmin needs to be same functionality available for admin users.

root@XXX:~# npm install -g @saltcorn/cli
npm WARN deprecated [email protected]: request has been deprecated, see https://git hub.com/request/request/issues/3142
npm WARN deprecated [email protected]: this library is no longer supported
/usr/bin/saltcorn -> /usr/lib/node_modules/@saltcorn/cli/bin/saltcorn

[email protected] install /usr/lib/node_modules/@saltcorn/cli/node_modules/connect -sqlite3/node_modules/sqlite3
node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Pre-built binaries not installable for [email protected] and node@ 14.10.0 (node-v83 ABI, glibc) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error EACCES: permission denied, mkdir '/usr/lib/node_modu les/@saltcorn/cli/node_modules/connect-sqlite3/node_modules/sqlite3/lib/binding'
gyp WARN EACCES current user ("nobody") does not have permission to access the d ev dir "/root/.cache/node-gyp/14.10.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_m odules/@saltcorn/cli/node_modules/connect-sqlite3/node_modules/sqlite3/.node-gyp "
gyp WARN install got an error, rolling back install
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/@s altcorn/cli/node_modules/connect-sqlite3/node_modules/sqlite3/.node-gyp'
gyp ERR! System Linux 4.15.0-117-generic
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy p/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/usr/lib/node_mod ules/@saltcorn/cli/node_modules/connect-sqlite3/node_modules/sqlite3/lib/binding /node-v83-linux-x64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_pa th=/usr/lib/node_modules/@saltcorn/cli/node_modules/connect-sqlite3/node_modules /sqlite3/lib/binding/node-v83-linux-x64" "--napi_version=6" "--node_abi_napi=nap i" "--napi_build_version=0" "--node_napi_label=node-v83"
gyp ERR! cwd /usr/lib/node_modules/@saltcorn/cli/node_modules/connect-sqlite3/no de_modules/sqlite3
gyp ERR! node -v v14.10.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_mo dules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build -- module=/usr/lib/node_modules/@saltcorn/cli/node_modules/connect-sqlite3/node_mod ules/sqlite3/lib/binding/node-v83-linux-x64/node_sqlite3.node --module_name=node _sqlite3 --module_path=/usr/lib/node_modules/@saltcorn/cli/node_modules/connect- sqlite3/node_modules/sqlite3/lib/binding/node-v83-linux-x64 --napi_version=6 --n ode_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v83' (1)
node-pre-gyp ERR! stack at ChildProcess. (/usr/lib/node_modules/@ saltcorn/cli/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:314:20)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1047:16)
node-pre-gyp ERR! stack at Process.ChildProcess.handle.onexit (internal/chi ld_process.js:287:5)
node-pre-gyp ERR! System Linux 4.15.0-117-generic
node-pre-gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/@saltcorn/cli/n ode_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/lib/node_modules/@saltcorn/cli/node_modules/connect-s qlite3/node_modules/sqlite3
node-pre-gyp ERR! node -v v14.10.0
node-pre-gyp ERR! node-pre-gyp -v v0.11.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp /bin/node-gyp.js configure --fallback-to-build --module=/usr/lib/node_modules/@s altcorn/cli/node_modules/connect-sqlite3/node_modules/sqlite3/lib/binding/node-v 83-linux-x64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/usr/lib /node_modules/@saltcorn/cli/node_modules/connect-sqlite3/node_modules/sqlite3/li b/binding/node-v83-linux-x64 --napi_version=6 --node_abi_napi=napi --napi_build version=0 --node_napi_label=node-v83' (1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional log ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-09-09T13_55_30_907Z-debug.log

As an application admin in Saltcorn
I should be able to configure an external identity provider (IdP) in my application
In order to grant users access based on roles/profiles defined in my corporate identity management solution.

I'd like to integrate Saltcorn to our cloud platform but without capability to centralize user/roles management such as Keycloak for all apps developed by users, enterprise use cases will quickly be limited.

We may be able to help if you provide some guidance.
And thanks for nice work!

I know this is possible by using search filter, but sometimes we need to have prefiltered list view, for example i have a table with projects, some of them are current while others are archived, i need a view with only current projects, so i can show it in my dashboard depending on the archived toggle.

The scenario:

1. Open Edit View for table record with empty markdown field

2. Close Edit.

3. You will receive message:
   

4. Try to open List View for this table. You'll receive exception:

Internal Error
Error: Input data should be a String
at MarkdownIt.parse (/home/saltcorn/plugin_packages/markdown-it/lib/index.js:519:11)
at MarkdownIt.render (/home/saltcorn/plugin_packages/markdown-it/lib/index.js:544:36)
at Object.run (/home/saltcorn/plugin_packages/@saltcorn/markdown/markdown.js:18:44)
at Object.key (/usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/base-plugin/viewtemplates/viewable_fields.js:160:59)
at /usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/markup/table.js:95:73
at Array.map ()
at /usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/markup/table.js:94:20
at Array.map ()
at /usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/markup/table.js:91:22
at newf (/usr/lib/node_modules/@saltcorn/cli/node_modules/contractis/contract.js:66:45)
at Object.run (/usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/base-plugin/viewtemplates/list.js:211:10)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async View.run (/usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/data/models/view.js:141:12)
at async /usr/lib/node_modules/@saltcorn/cli/node_modules/@saltcorn/server/routes/view.js:28:20
A report has been logged and a team of bug-squashing squirrels has been dispatched to deal with the situation.