Issue

When I open the ModuleBuilder I see a lot of messages and labels that are undefined. I took some screenshots to clarify what I mean.

Expected Behavior

The messages and labels should have their actual text instead of 'undefined'.

Actual Behavior

Different labels (see screenshots) are undefined.
suitecrm.log shows no error and the Apache error.log shows the following notice:
'''Undefined index: Support Forum in /var/www/html/suitecrm/public/legacy/include/MVC/View/SugarView.php on line 508, referer: https://crm.mydomain.tld/suitecrm/public/'''

Steps to Reproduce

1. Log into SuiteCRM
2. Go to Admin panel and select ModuleBuilder
3. Click on a module

Context

I tried to create a new module with a quick create layout. The undefined messages are confusing and obstructing the buttons and functionality.

Your Environment

• SuiteCRM Version used: 8.0.0
• Browser name and version: Firefox 94.0.2 (64-Bit), Chrome 96.0.4664.45
• Environment name and version (e.g. MySQL, PHP 7): MySQL: 5.7.36-0, PHP 7.3.33
• Operating System and version (e.g Ubuntu 16.04): Ubuntu0.18.04.1

Issue

Not able to serve the frontend shell app locally by the command provided in package.json:
"start:shell": "ng serve shell -o --port 5000"

Expected Behavior

Shell application should be served under http://localhost:5000

Actual Behavior

App won't be served, instead error message on terminal:

$ng serve shell  -o --port 5000
✔ Browser application bundle generation complete.
(node:36445) [DEP_WEBPACK_CHUNK_MODULES_ITERABLE] DeprecationWarning: Chunk.modulesIterable: Use new ChunkGraph API
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:36445) [DEP_WEBPACK_CHUNK_ENTRY_MODULE] DeprecationWarning: Chunk.entryModule: Use new ChunkGraph API

Possible Fix

I couldn't trace down the error, but since this is webpack related, I would like to suggest to consider an upgrade to Angular 12 before the release candidate of Suite CRM 8. Angular 12 already uses Webpack 5 out of the box and you would not need to override the Webpack version in package.json anymore.

Steps to Reproduce

1. Checkout source code
2. Optional: delete 'yarn.lock' file
3. Install dependencies: yarn install
4. Copy proxy.conf.env.json and rename the copy to proxy.conf.local.json
5. Run yarn run start:shell

Context

Theme development would be much easier, if the frontend could be served locally with automatic application reload on file changes instead of needing to rebuild it

Your Environment

• SuiteCRM Version used: 8.0.0-beta.2
• Operating System and version (e.g Ubuntu 16.04): MacOS Big Sur

Issue

I created and deployed 8 custom modules in our new 8.0.0 installation using the Module Builder, and they all show up in Studio. The database has tables for every module. But 5 of those modules are not displayed in the menu bar, and there is no entry for them under “Display Modules and Subpanels” or " Configure Module Menu Filters". They are also not in “Rename Modules”.

The other 3 custom modules (from the same package and deployment!) are working fine. If I manually modify the URL, I can access the listview of those ‘lost’ modules, but the design looks different and the buttons are missing.

The modules are all of different types (Basic, Company, etc.) so I don’t think that matters.

The logs show the following:

[3185550][1][WARN] ModuleNameMapper | mapName | 'SMP01_servicecontracts' not mapped to 'frontend'
[3185550][1][WARN] ModuleNameMapper | toLegacy | 'SMP01_servicecontracts' not mapped

There are entries like this for every custom module I deployed, even from other packages.

Expected Behavior

All deployed custom modules should be available in the following menus: “Display Modules and Subpanels”, " Configure Module Menu Filters", "Rename Modules"

Possible Fix

Fix mapping in ModuleNameMapper?

Steps to Reproduce

Those steps are not proven to reproduce the issue, but it is what we did before the issue appeared:

1. Create package in ModuleBuilder and fill with custom modules
2. Deploy package in same instance
3. Add custom fields to those modules in Studio
4. Set up relationships
5. Notice that some modules are missing in other menus and top menu bar

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version: Chrome 97.0.4692.71 (Official Build) (64-bit)
• Environment name and version: MySQL, PHP-FPM 7.4, nginx
• Operating System and version: Ubuntu 20.04.2 LTS

Server Details:
Ubuntu 20.04 (LTS) x64
PHP: 7.4
Mysql : Ver 8.0.27-0ubuntu0.20.04.1 for Linux on x86_64 ((Ubuntu))

SuiteCRM: Latest SuiteCRM 8

While installing the SuiteCRM on ubuntu machine getting an error of max file upload limit where the limit is more than 6M which is showing up an warning.

Issue

Seems that there is no way to change the database port on the install process bin/console suitecrm:app:install at the moment.
I run different databases on custom ports so it is necessary to change it.

Expected Behavior

A possibility to change the database port on install routine

Actual Behavior

Uses 3306 anyway

Possible Fix

Try to set the port manually in .env.local but then can't force the install process again because this file exists

Context

I run a DB in seperate Docker Container on non standard port.
I think I am not the only one with such a setup so this is a medium-high priority issue i guess

Your Environment

• App runs in Alpine 3.14 + PHP 8.0 + nginx 1.20. Container
• MariaDB 10.x runs in another container
• SuiteCRM 8 Beta 3

Issue

Expected Behavior

When saving changes to the Configure Module Menu Filters page a confirmation message should be given, and the changes should be saved.

Actual Behavior

The main menu bar and footer still shows, but the main content of the page is blank, and the changes are not saved. No errors are shown in log files.

Possible Fix

Steps to Reproduce

1. Follow instructions to install Suitecrm8 on linux
2. Log in to suitecrm8 and go to admin>Configure Module Menu Filters
3. Click Save & Deploy

Context

This was a fresh install, intended to replace suitecrm7 - first task was to make changes to module menu filters to mirror those we already have in place on v7. Could not proceed further until issue is resolved. Tried changing permissions, checked suite logs and apache logs, but could not find any error messages.

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome 96.04664.110
• Environment name and version (e.g. MySQL, PHP 7): MySQL, PHP 8.0.08
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 22.04

Issue

First install of SuiteCRM 8 we get following error:
"There are validation errors, unable to perform action."

Unfortunately it's not clear what's missing. It's not clear from the UI. Even when we check "Ignore System Check Warnings" we can't move forward.

Expected Behavior

Display list of errors which needs to be fixed by user to proceed with installation

['LBL_CHARTS']

https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L1477
https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L3758

['LBL_NO_DATA']

https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L1087
https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L3760

['LBL_SEARCHING']

https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L1816
https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L3801

['LBL_CREATE']

https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L3838
https://github.com/salesagility/SuiteCRM-Core/blob/v8.0.0/public/legacy/include/language/en_us.lang.php#L3881

Issue

If the user enters an incorrectly formatted URL for the site URL during initial installation configuration, the RewriteBase value populated in /public/legacy/.htaccess file is non-functional. This has the effect of returning an 'Internal Server Error' for all legacy/classic pages but leaves all pages served by the new SuiteCRM8 code to work as expected.

See community forum: https://community.suitecrm.com/t/suitecrm8-install-issues-on-freebsd-truenas/83064

Expected Behavior

Without explicit guidance, a user may enter 'localhost' or ' in the site URL field. Expected behaviors is that the site would accommodate this and work expected, presenting all menus.

Actual Behavior

Unless the site URL is formatted correctly, SuiteCRM8 serves legacy/classic page errors as 'Internal Server Error'. SuiteCRM8 'new' code pages (Accounts, Contacts etc) work normally.

Possible Fix

Place a user tip explicitly stating the format input required and/or force the input format to be compliant.

Steps to Reproduce

1. During install configuration, enter just 'localhost' or any suitable IP address in the site URL field.
2. Complete install config
3. Test 'Administrator' dropdown options for 'Internal Server Errors'
4. View /public/legacy/.htaccess file for the value entered in 'RewriteBase' value. Correct entry should be '/legacy/', not 'legacy/'

Context

Trying to accomplish setup of SuiteCRM 8.
Without access to legacy pages, the application is non-functional.

Your Environment

• SuiteCRM Version used: 8.0.0
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Firefox 94.0.2 and Edge 96.0.1054.34
• Environment name and version (e.g. MySQL, PHP 7): Apache2.4, PHP 7.4, MySQL8
• Operating System and version (e.g Ubuntu 16.04): TrueNAS-12.0-U6.1 (FreeBSD 12) running in iocage jail at patch 12.2-RELEASE

Issue

I'm missing the menu on top.

Expected Behavior

Actual Behavior

Possible Fix

Steps to Reproduce

Context

Your Environment

• SuiteCRM Version used: 800 beta 2
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chome latest edition
• Environment name and version (e.g. MySQL, PHP 7): MySQL PHP 7
• Operating System and version (e.g Ubuntu 16.04): Windows 2019 Server

Issue

Notifications (Alert module) widget doesn't updated.

Expected Behavior

When new alerts inserted in database widget must update.

Actual Behavior

Notification widget is just static example

Possible Fix

Need to implement right behavior in angular?))

Steps to Reproduce

1. Open 2 windows with different logged in users
2. Window 1 - open Any Lead Entity and assign it to user 2
3. Wait a 1 minute before javascript call endpoint for new notifications
4. Check in developer tools for endpoint /legacy/index.php?module=Alerts&action=get&to_pdf=1
5. Here must be new notification... But notification widget still same...

Context

Hi everyone! As i understood from code - for now Notifications (Alert module) is static template in beta versions… Is it right? or maybe it is possible to change it for working with notifications like in v7 (https://community.suitecrm.com/t/how-to-create-notifications-by-using-workflows-logic-hooks/70809)?

Maybe it will resolve in release?

thank you for your time:)

Your Environment

• SuiteCRM Version used: ver. 8-Beta-2
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome Version 94.0.4606.81 (Official Build) (arm64)
• Environment name and version (e.g. MySQL, PHP 7): 10.2.39-MariaDB-1:10.2.39+maria~bionic, PHP 7.4
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 18.04

Simple "You are not authorized to view this page. Please contact your system administrator." error message causes Javascript execution to stop and thus renders main menu unusable.

Issue

Steps to reproduce:

1. Log for example as will / will to freshly installed SuiteCRM v8.0.0. instance with Demo data populated
2. Navite to profile menu and choose "Employees"
3. You will get "You are not authorized to view this page. Please contact your system administrator." error
4. Try to use main menu - you will not be able to click on menu items and you will notice that main menu is not functional any more

Expected Behavior

JS errors should be handled in way not to break down javascript execution cause loss of functionality

Actual Behavior

JS error causes JS execution breakdown - renders main menu unusable

Possible Fix

Handle JS errors so they don't break JS scripts

Steps to Reproduce

Steps to reproduce:

1. Log for example as will / will to freshly installed SuiteCRM v8.0.0. instance with Demo data populated
2. Navite to profile menu and choose "Employees"
3. You will get "You are not authorized to view this page. Please contact your system administrator." error
4. Try to use main menu - you will not be able to click on second menu hierarchy (i.e. under Accounts or Opportunities) and you will notice that main menu is not functional any more

Context

Your Environment

• SuiteCRM Version used: V 8.0.0.
• Browser name and version: Latest Chrome
• Environment name and version: mySQL enterprise, php 7.4.,
• Operating System and version (e.g Ubuntu 16.04): CentOS 7

Issue

When in contact list view, it would be good to be able to select a group of contact records to then initiate composing an email to those selected contacts by choosing a 'send email' option in the bulk action dropdown.

Expected Behavior

This is a suggested feature to make it easier to send emails to contacts. Selecting contact records in a filtered list view enables you to select contacts by any contact attributes (e.g., contact type, location, organization, last sale date etc) and be able to send as a bulk action. The email should conform to all of the standard features for inserting contact name and other variables as is the case for campaigns. The emails should be captured as normal email activities in the history etc.

Actual Behavior

There is currently no ability to send emails to contacts displayed in a filtered list. Emails to groups of users must first be added to target lists and then associated with campaigns.

Possible Fix

Steps to Reproduce

Context

Sending email is a core function of a CRM so it should be as easy as possible to send emails to contacts from almost any view. There are many times when you want to filter contacts (e.g., a common use case is by filtering by certain customer attributes/custom fields /properties for example) and then send an email to all of those users. Perhaps it would be good to allow the user to select whether they can customise the content of each individual email before it is sent (to allow for deeper personalisation/customisation) but just being able to select an existing email template and sending to the selected users with normal variable insertion (i.e., inserting $first_name) would be a very big improvement.

Your Environment

• SuiteCRM Version used: v8
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Any//all
• Environment name and version (e.g. MySQL, PHP 7): MYSQL 8, PHP 7.4
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 20.04

In SuiteCRM 7, it is possible to display a help tooltip in each of the fields of the modules. You can add this tooltip simply adding the vardef property to the field: "'popupHelp' => 'LBL_YOUR_HELP_LABEL',".

We brought a whole module from SuiteCRM 7 to SuiteCRM8 and this tolltip isn't displayed

Issue

The optional help tooltips of the fields aren't displayed in the Edit or DetailView.

Expected Behavior

The tooltip should be displayed

Actual Behavior

Nothing happen

Possible Fix

Steps to Reproduce

1. Add the vardef property "popupHelp" in any field of any module
2. Add the corresponding Label
3. Check that the tooltip doesn't appear

Context

It should be compatible with SuiteCRM7 funcionality

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome
• Environment name and version (e.g. MySQL, PHP 7): MariaDB
• Operating System and version (e.g Ubuntu 16.04): Debian OS

Issue

Invalid import file name when import Leads (Import File Template)
Step 1: Upload Import File

Select a file on your computer that contains the data that you would like to import, or download the template to get a head start on creating the import file.
Download Import File Template Information

Expected Behavior

Actual Behavior

Possible Fix

Steps to Reproduce

Context

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)):
• Environment name and version (e.g. MySQL, PHP 7):
• Operating System and version (e.g Ubuntu 16.04):

Like issue #15 (second issue) if u install different language, currency locale format is inconsistent with current language

Issue

currency locale format is inconsistent with current language

Expected Behavior

currency locale format must consistent with current language

Steps to Reproduce

1. Install as per instructions, with demo data
2. Install Italian language from https://crowdin.com/project/suitecrmtranslations
3. Config currency in administration, so in config_override.php i have
   $sugar_config['default_decimal_seperator'] = ',';
   $sugar_config['default_number_grouping_seperator'] = '.';
4. repair and rebuild from administration
5. ./bin/console cache:clear
6. logout and login in Italian Language
7. currency are in en_US locale format, text is in Italian Language

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Firefox 94
• Environment name and version (e.g. MySQL, PHP 7): php 7.4
• Operating System and version (e.g Ubuntu 16.04): debian 11

Issue

Followed beta install instructions on a fresh deb 10 vm. May have screwed something up during db setup. In any case, getting a blank webpage on load.

Expected Behavior

Not sure, some sort of setup page?

Actual Behavior

Blank page. page source follows

`

--
  |
  |  
  |
  |
  | <title>SuiteCRM</title>
  |
  |  
  |
  |
  |
  |
  |  
  |
  |
  |
  |  
  |
  |
  | <script src="dist/polyfills-es5.166ea56ffbe4182c0c7c.js" nomodule defer></script><script src="dist/polyfills-es2015.af170ffe981b0ba2d77d.js" type="module"></script><script src="dist/styles-es2015.016e215452bfa9ef2f89.js" type="module"></script><script src="dist/styles-es5.016e215452bfa9ef2f89.js" nomodule defer></script><script src="dist/main-es2015.16d9d4992b4627546ed8.js" type="module"></script><script src="dist/main-es5.16d9d4992b4627546ed8.js" nomodule defer></script>
  |

``

Your Environment

Chrome browser
server Deb 10 Apache.

Issue

"Undefined" record UUID on one-to-one custom module relationship linked field url

Expected Behavior

Get url with record UUID in linked field

Actual Behavior

Get "undefined" value in url:
http://localhost/#/test_module1/record/undefined

Steps to Reproduce

1. Install as per instructions
2. Create basic custom module in studio
3. Create one-to-one ralationship custom module->account
4. Deploy custom module
5. insert account record
6. insert custom module record
7. link custom module record with account record
8. linked field url have "undefined" record value

Your Environment

• SuiteCRM Version used: SuiteCRM Version used: 8.0.0
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Firefox 94.0.1
• Environment name and version (e.g. MySQL, PHP 7): php 7.3
• Operating System and version (e.g Ubuntu 16.04): debian 10

In SuiteCRM 7, it is possible to display a help tooltip in each of the fields of the modules. You can add this tooltip simply adding the vardef property to the field: "'popupHelp' => 'LBL_YOUR_HELP_LABEL',".

We brought a whole module from SuiteCRM 7 to SuiteCRM8 and this tolltip isn't displayed

Issue

The optional help tooltips of the fields aren't displayed in the Edit or DetailView.

Expected Behavior

The tooltip should be displayed

Actual Behavior

Nothing happen

Possible Fix

Steps to Reproduce

1. Add the vardef property "popupHelp" in any field of any module
2. Add the corresponding Label
3. Check that the tooltip doesn't appear

Context

It should be compatible with SuiteCRM7 funcionality

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome
• Environment name and version (e.g. MySQL, PHP 7): MariaDB
• Operating System and version (e.g Ubuntu 16.04): Debian OS

Issue

Issue 1:
After installing a second language pack, the user can select a preferred locale on login screen. LanguageStore.languageKey$ is being initialized with the locale the user selected on the login screen and the app and module translations are loaded according to the selected locale. However, the selected locale is being lost on page refresh or when opening a link as a new tab.

Issue 2:
The Angular lib crm/core/app/core contains some custom formatting pipes and services which inject the Angular injection token LOCALE_ID. These pipes and services use the value of LOCALE_ID to format according to the current locale. However, SCRM Angular app never provides a value for that injection token, therefore it will always have the default value en_US. As a consequence, even when the user chose a different locale on login, the translation would be provided in that user preferred locale (until page refresh) but the formatting of dates, numbers, currencies would always be made using locale en_US.

Expected Behavior

The locale that the user logged in with should be maintained across page refreshes. The frontend should be served in that locale.
If SCRM pipes and services rely on LOCALE_ID, then the value LOCALE_ID should be kept in sync with SCRM internal locale state holder LanguageStore.languageKey$, otherwise these SCRM pipes and services should use LanguageStore.languageKey$ instead for figuring out the current locale of the user. But best option would be to keep LOCALE_ID in sync with LanguageStore.languageKey$, to allow developers who extend SCRM frontend to use the standard Angular pipes which also rely on LOCALE_ID.

Actual Behavior

• SCRM Internal locale state holder LanguageStore.languageKey$ looses its state on page refresh and falls back to en_US
• Angular LOCALE_ID not properly initialized and synced with LanguageStore.languageKey$ and always contains en_US independent of the locale the user chose on login screen

Possible Fix

Issue 1:
The preferred locale which the user logged in with, could be stored in backend user preferences, in a cookie or in local/session storage. On app initialization, LanguageStore.languageKey$ should be initialized with the previously stored locale. This would maintain the preferred locale across page refreshes.

Issue 2:
SCRM Angular app needs to provide the initial value for LOCALE_ID and needs to find a way to keep it in sync with LanguageStore.languageKey$:

// scrm app.module.ts
providers: [ { provide: LOCALE_ID, useFactory: ..., } ],

Steps to Reproduce

1. Install second language pack, e.g. German
2. On login screen choose German language and hit login button
3. See frontend being served in German language. Value of LanguageStore.languageKey$ is de_DE. Value of Angular Injection Token LOCALE_ID is en_US, meaning all Angular standard and SCRM custom pipes which rely on LOCALE_ID would use English locale instead of German for formatting.
4. Hit F5 for a page refresh
5. Page is refreshed for current user. User is still logged in, but the page is served in English language and value of LanguageStore.languageKey$ equals en_US even though the user would expect to see German.

Your Environment

• SuiteCRM Version used: 8.0.0-beta3

Issue

Install SuiteCRM by this guide https://docs.suitecrm.com/8.x/developer/development-install-guide/

yarn install

yarn install v1.22.10
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
error An unexpected error occurred: "http://localhost:4873/cross-spawn/-/cross-spawn-7.0.3.tgz: connect ECONNREFUSED 127.0.0.1:4873".
info If you think this is a bug, please open a bug report with the information provided in "/.../yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Expected Behavior

No Errors

Actual Behavior

Possible Fix

Steps to Reproduce

1. Clone repo to v8.0.0-beta.1 directory
2. cd v8.0.0-beta.1
3. Check tag v8.0.0-beta.1
4. composer install
5. yarn install

Context

Your Environment

• SuiteCRM Version used: v8.0.0-beta.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): ---
• Environment name and version (e.g. MySQL, PHP 7): Mysql 5.7, PHP 7.3
• Operating System and version (e.g Ubuntu 16.04): Fedora 33

Issue

When creating or editing a contact record with multiple email addresses, the system currently allows the user to select multiple email addresses as the primary address - but then receives an error indicating that a contact can only have one primary email address. By changing from a checkbox to a radio selector, this situation and resulting error message is avoided.

Expected Behavior

Editing a contact record with multiple email addresses should use the radio selector rather than a checkbox to indicate which is the primary contact record.

Actual Behavior

Multiple email addresses are allowed to be selected as the primary address but when the record is saved an error message is displayed indicating that only one email address can be made the primary address.

Possible Fix

Change current checkbox control to radio group control

Steps to Reproduce

1. Edit contact record with multiple email addresses
2. Select multiple addresses as primary
3. Save contact record

Context

This is a usability issue. I would imagine it should be a medium priority if it is a simple code fix.

Your Environment

• SuiteCRM Version used: v8
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Any/all
• Environment name and version (e.g. MySQL, PHP 7): MYSQL 8, PHP 7.4
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 20.04

Issue
Ranged Search Options not work for Numeric Type Field, work in legacy frontend

Expected Behavior
Ranged Search Option must appear in filters when enable it

Steps to Reproduce
Install as per instructions, with demo data
Enable Ranged Search Option for a Currency/Int/Numeric field
repair and rebuild from administration
./bin/console cache:clear
Ranged Search Options not appear in filter

Your Environment
SuiteCRM Version used: 8.0.1
Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Firefox 94
Environment name and version (e.g. MySQL, PHP 7): php 7.4
Operating System and version (e.g Ubuntu 16.04): debian 11

In many cases words begin with capital letters.
In Russian such phrases look at least strange.

Issue

In User Profile, when click "Authorize" in advanced -> Google Account Synchronization, get empty page.

Expected Behavior

Redirect to Google authentication page

Actual Behavior

get empy page
In js console have this error: Uncaught DOMException: Permission denied to get property "href" on cross-origin object

Steps to Reproduce

1. Install as per instructions
2. Load google oauth json in administration page
3. Click Authorize in advanced -> Google Account Synchronization

Your Environment

• SuiteCRM Version used: 8.0.0
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Firefox 94.0.1
• Environment name and version (e.g. MySQL, PHP 7): php 7.3
• Operating System and version (e.g Ubuntu 16.04): debian 10

If I load page from
https://mydomain.com/legacy/index.php?module=Users&action=EditView&record=MYUUID
work as expected

But in config/services/module/module_routing.yaml I have
users:
index: true
list: true
record: false

Issue

After seemingly successful installation I cannot login with admin user

Installation is performed as per installation guide,

SuiteCRM Silent Install

Running: check-install-lock
step: check-install-lock | status: done
Installer not locked. Proceeding with install
Running: check-db-connection
step: check-db-connection | status: done
DB credentials ok
Running: install-system-checks
step: install-system-checks | status: done
Running: create-config
step: create-config | status: done
Created silent install config: config_si.php
Running: create-env
step: create-env | status: done
Created .env.local
Running: run-legacy-install
step: run-legacy-install | status: done
Legacy install successful

============

Expected Behavior

Actual Behavior

Admin user cannot login, PHP log is clear, in browser there is a message:
Error fetching metadata, seems like user is logged in but nothing is available from the main menu,

JS console returns:
node_modules_angular_core_fesm2015_core_js-es2015.d7030c87f7f062fb36bc.js:1 ERROR Error: Uncaught (in promise): Error: Internal server error
Error: Internal server error
at new t (node_modules_apollo-angular_fesm2015_ngApollo_js-_0ddc0-es2015.62f90fac9a620f500655.js:1)
at node_modules_apollo-angular_fesm2015_ngApollo_js-_0ddc0-es2015.62f90fac9a620f500655.js:1
at r (node_modules_apollo-angular_fesm2015_ngApollo_js-_0ddc0-es2015.62f90fac9a620f500655.js:1)
at node_modules_apollo-angular_fesm2015_ngApollo_js-_0ddc0-es2015.62f90fac9a620f500655.js:1
at new P (polyfills-es2015.b81ce80777ba591aef43.js:1)
at Object.then (node_modules_apollo-angular_fesm2015_ngApollo_js-_0ddc0-es2015.62f90fac9a620f500655.js:1)
at Object.next (node_modules_apollo-angular_fesm2015_ngApollo_js-_0ddc0-es2015.62f90fac9a620f500655.js:1)
at v (core_app_shell_src_bootstrap_ts-es2015.f1ac98f4222c1448c4f1.js:1)
at _ (core_app_shell_src_bootstrap_ts-es2015.f1ac98f4222c1448c4f1.js:1)
at e.t.next (core_app_shell_src_bootstrap_ts-es2015.f1ac98f4222c1448c4f1.js:1)
at w (polyfills-es2015.b81ce80777ba591aef43.js:1)
at w (polyfills-es2015.b81ce80777ba591aef43.js:1)
at polyfills-es2015.b81ce80777ba591aef43.js:1
at u.invokeTask (polyfills-es2015.b81ce80777ba591aef43.js:1)
at Object.onInvokeTask (node_modules_angular_core_fesm2015_core_js-es2015.d7030c87f7f062fb36bc.js:1)
at u.invokeTask (polyfills-es2015.b81ce80777ba591aef43.js:1)
at t.runTask (polyfills-es2015.b81ce80777ba591aef43.js:1)
at b (polyfills-es2015.b81ce80777ba591aef43.js:1)
at l.invokeTask [as invoke] (polyfills-es2015.b81ce80777ba591aef43.js:1)
at m (polyfills-es2015.b81ce80777ba591aef43.js:1)

In network tab: 

Session status returns: {"appStatus":{"installed":true,"locked":true},"active":true,"id":"1","firstName":null,"lastName":"Administrator","userName":"admin"}

There is graphql requsts returning:
{"errors":[{"message":"Internal server error","extensions":{"category":"internal"},"locations":[{"line":2,"column":3}],"path":["navbar"]}],"data":{"navbar":null}}

Possible Fix

Steps to Reproduce

1. Install as per instructions
2. Try to login as admin

Context

Your Environment

• SuiteCRM Version used: SuiteCRM V8.0
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)):
  Latest chrome
• Environment name and version (e.g. MySQL, PHP 7):
  PHP 8.0.6 (php-fpm), MySQL Enterprise 8.0.17
• Operating System and version (e.g Ubuntu 16.04):
  Centos7

Issue

• On the activities subpanel there are no create or link buttons

Expected Behavior

• The subpanel should should the buttons according to configuration and acls

Actual Behavior

• buttons do not show

Possible Fix

Steps to Reproduce

1. Open App
2. Go to account record
3. Go to activities subpanel

Context

Your Environment

• SuiteCRM Version used: 8.0.0
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chromium Version 96.0.4664.93
• Environment name and version (e.g. MySQL, PHP 7): php 7.4
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 20.04.3 LTS

Environment: Ubuntu 20.04 VPS PHP 7.4/MySQL 5.6

When creating filters in the Suite CRM 8.0.0 release, I cannot create an "Opportunity" filter with multiple Sales Stages in the filter.

Expected Behavior: Create an Opportunity filter with more than one sales stage, and save the filter to "My Filters"

Observed Behavior: When saving a filter with more than one "Sales Stage" in the filter, the filter will save, and it appears under "My Filters" however the "Sales Stages" do not save into the filter, and so the filter has no effect. This has been 100% repeatable. When I save a filter with only a single sales stage, the filter saves. `

Issue

Install SuiteCRM by this guide https://docs.suitecrm.com/8.x/developer/development-install-guide/

Issue

When i enter the URL in my web browser its blank and in console i below errors are occures.

Your Environment

• SuiteCRM 8 Version used:
• Google Chrome Version 89.0.4389.114 (Official Build) (64-bit)
• PHP 7.4 and Mysql 5.7
• Ubuntu 18.04
  

Issue

After installing another language file (English (United Kingdom - en_GB in this case) moving the default language file (US English) into the 'disabled' column from the Admin->Language page ( causes errors on subsequent page loads on many pages.

For example trying to add a new contact results in an "Error occurred while fetching metadata".

Once that error has been triggered the UI then fails to respond correctly. The drop-down menus drop on hover-over but as soon as the mouse moves, the sub-menu disappears making it impossible to navigate with a mouse.

The only way to recover the situation is to logout (xxx.com/logout) and then login in again. The "Admin" pages, luckily, do continue to work.

Expected Behavior

The system should continue to operate with out throwing an error and the UI should continue to work properly.

Actual Behavior

An error is thrown and the system becomes unusable without re-enabling the language

Steps to Reproduce

1. Go to Admin area (/#/administration/index)
2. Select Languages (#/administration/Languages?view=default)
3. Move English (US) into the "Disabled Languages" column
4. Click "Save" button
5. Navigate to another page, "Create Contact" for example.
6. Error is thrown and the UI breaks.

Context

This is not a huge operational problem if you are aware of the issue, however it caught me for a while on a fresh install during the initial setup phase. New users may become frustrated when trying to keep the install tidy with only the modules/languages/locales etc that they want to have installed.

I think it is a medium priority bug due to the devastating effect it has on the overall system.

Your Environment

Suite CRM 8.0.1
All browsers are affected.
PHP 7.4
MariaDB
Ubuntu Server 20.04

Completed the installation of the CPM.
Database was created successfully. When we go to Public, we see the following JS errors:

SuiteCRM Version used:
SuiteCRM 8.0-beta Releases
Environment name and version (e.g. MariaDB 10.1, PHP 7.4):
Operating System and version (e.g Centos 7):
Nginx, Node 10, Yarn 1.22.10, Angular CLI 11+

Issue

When try to install some users have been having problems connecting their database.
This is usually the way the port is appended to the connection string.

it sometimes creates a connection string with : and not port, like ‘127.0.0.1:’

See community forum thread:

• https://community.suitecrm.com/t/install-database-connection-issue-with-suitecrm-8/82978/5?u=clemente.raposo

Expected Behavior

Admins should be able to use 'localhost' to connect to their database

Actual Behavior

Admins aren't able to use 'localhost' to connect to their database

Possible Fix

To fix this issue we should do the following:

• Make the db port entirely optional
• Remove the default from the db port
• if not port specified don't append the :

See possible fix in: https://community.suitecrm.com/t/install-database-connection-issue-with-suitecrm-8/82978/19?u=clemente.raposo

Steps to Reproduce

1. On command line install set the db host as localhost
2. Don't set any port on any port

Context

• See community forum: https://community.suitecrm.com/t/install-database-connection-issue-with-suitecrm-8/82978/15

Your Environment

• SuiteCRM Version used: 8.0.0
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)):
• Environment name and version (e.g. MySQL, PHP 7): PHP 7.4, 5.5.5-10.3.31-MariaDB-cll-lve
• Operating System and version (e.g Ubuntu 16.04):

Maybe not a true "issue" or bug, but I've noticed that when an order has been in the same stage for less than a day, the alert at the top reads "THIS OPPORTUNITY HAS BEEN IN THIS SALES STAGE FOR: DAY(S)"

It would be much better if it instead read "THIS OPPORTUNITY HAS BEEN IN THIS SALES STAGE FOR: < 1 Day" for orders that have been in the same sales stage for less than a day.

Issue

Followed the install doc
Install page is blank
Install via command line says success but still gives blank page

Expected Behavior

Install would work

Actual Behavior

2021-12-06 17:54:52] install.INFO: Running step: create-env [] []
[2021-12-06 17:54:52] install.INFO: step: create-env | status: done [] []
[2021-12-06 17:54:52] install.INFO: step: create-env | messages: [] []
[2021-12-06 17:54:52] install.INFO: Created .env.local [] []
[2021-12-06 17:54:52] install.INFO: step: create-env | debug: no debug info [] []
[2021-12-06 17:54:52] install.INFO: Running step: run-legacy-install [] []
[2021-12-06 17:55:02] install.INFO: step: run-legacy-install | status: done [] []
[2021-12-06 17:55:02] install.INFO: step: run-legacy-install | messages: [] []
[2021-12-06 17:55:02] install.INFO: Legacy install successful [] []
[2021-12-06 17:55:02] install.INFO: step: run-legacy-install | debug: no debug info [] []
nothing in the prod log

Steps to Reproduce

Tried many times to unzip the file and install. Never get install page and command line says success but still blank

<meta charset="utf-8">
<title>SuiteCRM</title>
<base href="">

<meta http-equiv="cache-control" content="no-cache, must-revalidate, post-check=0, pre-check=0">
<meta http-equiv="expires" content="0">
<meta http-equiv="pragma" content="no-cache">
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1">

<link rel="manifest" href="site.webmanifest">
<link rel="icon" type="image/x-icon" href="dist/themes/suite8/images/favicon.ico">

Your Environment

• SuiteCRM Version used: 8.0 download
• all
• Centos 7, 10.3.29-MariaDB, PHP 7.3.28

The translated text is too long, it may need to be split into 2 lines.

Issue

Went to Admin > Studio to add field to Products and got an error.

Expected Behavior

I should be able to add fields to modules.

Actual Behavior

Interface briefly flashes "Failed to Retrieve Data"
This error is in php logs:

PHP Fatal error:  Uncaught Error: Attempt to modify property "vardefs" on null in 
/srv/http/suitecrm8/public/legacy/modules/ModuleBuilder/views/view.modulefields.php:109

Stack trace:
#0 /srv/http/suitecrm8/public/legacy/include/MVC/View/SugarView.php(210): 
ViewModulefields->display()

#1 /srv/http/suitecrm8/public/legacy/include/MVC/Controller/SugarController.php(432): SugarView->process()

#2 /srv/http/suitecrm8/public/legacy/include/MVC/Controller/SugarController.php(363): SugarController->processView()

#3 /srv/http/suitecrm8/public/legacy/include/MVC/SugarApplication.php(101): SugarController->execute()

#4 /srv/http/suitecrm8/public/legacy/index.php(52): SugarApplication->execute

#5 {main}
  thrown in /srv/http/suitecrm8/public/legacy/modules/ModuleBuilder/views/view.modulefields.php on line 109, referer: http://myserver/suitecrm8/legacy/index.php?type=studio&module=ModuleBuilder&action=index

Steps to Reproduce

Not sure if the data imports I had done earlier (CSV files exported from an earlier version of SuiteCRM) caused this or if it's some factor of my install environment, but presumably just install suitecrm 8.0.0-beta2 and try to add fields to a module. I imported data into products, invoices, and a few other tables.

Your Environment

• SuiteCRM 8.0.0-beta2
• Chrome Version 92.0.4515.131 (Official Build) (64-bit)
• MariaDB 10.6.3-1, PHP Version 8.0.9
• Arch Linux Kernel 5.13.7

Installed v8 on a separate instance for testing. Then, restored a dump from my v7 instance.

After importing an email and unfolding the history subpanel, on accounts, contacts, leads and I guess other modules, all columns have blank content (status, contact, dates) with exception of subject.

The behaviour is the same for existing emails on the database restored from v7.

Please note v7 subpanel on screenshot has been slightly customised with column Date RxTx addition.

EDIT: As an additional comment, I think the Date RxTx column, which is the date an email (or a call) was sent or received, is an essential information whereas Date Created or Modified is irrelevant, at least for me.

Expected Behavior

History subpanel columns should be populated with status, contact, date modified, date created, due date.

Actual Behavior

History subpanel columns are blank with exception of subject

Steps to Reproduce

1. Call account or contact that has history
2. Unfold history panel
3. History emails columns are blank with exception of subject

Context

It's serious if I cannot see the dates and contact relevant to a history email or call

Your Environment

• SuiteCRM Version used: v8.01
• Safari v15.2
• MariaDB v10.15.13, PHP v7.4.27, apache v2.4
• Operating System and version (e.g Ubuntu 16.04): macOS 10.15.7

System:
nginx, php7.4-fpm

Fresh new install, I get

Attempted to load class "DoctrineFixturesBundle" from namespace "Doctrine\Bundle\FixturesBundle".
Did you forget a "use" statement for another namespace?

Trying a composer install and I get:

Problem 1
- jeremykendall/php-domain-parser 4.0.3-alpha requires ext-intl * -> the requested PHP extension intl is missing from your system.

After a composer install I get no errors except that the Login step is not working. So I run:

`$ php bin/console doctrine:schema:update --dump-sql

The following SQL statements will be executed:

 DROP INDEX idx_user_name ON users;
 CREATE INDEX idx_user_name ON users (user_name, is_group, status, last_name(30), first_name(30), id);

`

Therefore I have to run php bin/console doctrine:schema:update --force and I reach another stop:

An exception has been thrown during the rendering of a template ("Error when rendering "https://mydomain.com/_profiler/2fed73?panel=request" (Status code is 307).").

Issue

open-in new tab still broken

Expected Behavior

right click and open-in new tab to open link in new tab

Actual Behavior

in version 7 this will navigate to an empty page
in version 8 the option to open in a new tab doesn't even exist

Possible Fix

menu navigation in version 7 uses some strange javascript in the href attribute of the anchor tags and an onClick handler for navigation (generating proper href attributes will fix this issue)
in version 8 the href attribute is completely missing from every anchor tag in navigation

Steps to Reproduce

1. change screensize to tablet/mobile view
2. right click and try opening in new tab

Context

navigating within SuiteCRM with multiple windows open (side by side etc) is cumbersome, requiring that tabs are duplicated before navigating to where you want to go

Your Environment

• SuiteCRM Version used: 7.11 + SuiteCRM 8.0.0-beta.2
• Browser name and version : Google Chrome 92.0.4515.131 (Official Build) (64-bit)
• Environment name and version (e.g. MySQL, PHP 7): PHP 7.4
• Operating System and version (e.g Ubuntu 16.04):

Issue

-Accounts/Contacts email link does not open Internal email client, allways open the external (outlook)
-Email icon in Accounts/Contacts list does open internal email client but do not auto-fill "TO" field

Your Environment

• SuiteCRM Version used: 8-Beta1
• Browser name and version:. Chrome
• Environment name and version: LAMP (Apache, MySQL, PHP 7):
• Operating System and version :Debian
  

Issue

When in the detail view for a contact there appears to be no way to easily send an email to that contact.

Expected Behavior

The same touchpoint controls that are displayed in the contact list view (log a call, send an email, schedule a meeting, create a task) should be easily available in the contact detail view. This should be at the top of the contact record so it is easily accessible (i.e., to the right of the contact name where there is a large area of available white space - next to 'new', edit' etc).

Actual Behavior

There is no way to easily update touchpoint information from the contact detail record currently

Possible Fix

Add contact touchpoint controls at the top of the contact detail record view

Steps to Reproduce

Context

Easily accessing touchpoint controls from any view of a contact aids usability

Your Environment

• SuiteCRM Version used: v8
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Any/all
• Environment name and version (e.g. MySQL, PHP 7): MYSQL 8, PHP 7.4
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 20.04

When generating a new users I got an error since there was no password specified. I did not have the "Enable System-Generated Passwords Feature" turned on so this was expected. I entered a temporary password and the new user was created and a email was sent to the user. The email contained the username as specified but the password was a random generation and not the password specified during user creation. The user is unable to login using the password in the email but can with the temporary password specified at creation.

Issue

new user creation sends email with bad password, user can not login

Expected Behavior

notification email should have specified password set during user creation.

Actual Behavior

random password sent in notification email

Possible Fix

update email notification?

Steps to Reproduce

1. Generate new user and specify password
2. new user receives email with login and password
3. new user unable to login due to wrong password in email

Context

testing with the "Enable System-Generated Passwords Feature" on generated more bugs not listed here.

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome Version 97.0.4692.71 (Official Build) (64-bit)
• Environment name and version (e.g. MySQL, PHP 7): MySQL, PHP 7.4
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 20.04

Issue

Extension language $mod_strings are not being recognized. I am creating a custom simple extension, adding a button to Contacts/detail view.

Overriden detailviewdefs.php file (located in /public/legacy/custom/modules/Contacts/metadata/):

// in 'recordActions' array
'register-via-api' => [
    'key' => 'register-via-api'
    'labelKey' => 'LBL_REGISTER_VIA_API',
    'asyncProcess' => true,
    'modes' => ['detail']
],

Language file en_us.register_via_api.php (located in public/legacy/custom/Extension/modules/Contacts/Ext/Language/):

<?php

$mod_strings['LBL_REGISTER_VIA_API'] = 'Register via API';

More discussion on the official SuiteCRM forum.

Expected Behavior

For button to show up in Contacts/Detail view with the given label.

Actual Behavior

Button showed up but with no label, an empty string

Your Environment

• SuiteCRM Version used: 8.0.0

Issue

After fresh installation of Suite CRM 8.0.0, Module builder opens modal window with error message and other errors are in browser console.

Rendered error:

Warning: Creating default object from empty value in /var/www/html/public/legacy/modules/ModuleBuilder/views/view.modulefields.php on line 109

Console errors:

Failed to load resource: the server responded with a status of 404 (): /legacy/modules/Administration/Search/ajaxSubmit.js

File ajaxSubmit.js not in production package after installation. Only reference to this file is found in public/legacy/modules/Administration/Search/ElasticSearch/view.tpl:154

Failed to load resource: the server responded with a status of 404 (): /%22themes//suite8//images//icon_home.png?v=0kE0lI62WZjkj_geRkWwbQ\%22

File in public/legacy/themes/suite8/images/icon_home.png

Failed to load resource: the server responded with a status of 404 (): /%22themes//default//images//icon_back.gif?v=0kE0lI62WZjkj_geRkWwbQ\%22

File in public/legacy/themes/default/images/icon_back.gif

Uncaught SyntaxError: Invalid or unexpected token: VM773 index.php
Uncaught SyntaxError: Invalid or unexpected token: index.php?type=studio&module=ModuleBuilder&action=index

Expected Behavior

Use module builder

Actual Behavior

Module builder not usable - modal window with

Steps to Reproduce

1. Clean install with demo data
2. Open Module builder /#/module-builder/index?type=studio
3. Expand single Module, e.g. Contacts
4. Click "Fields" (modal with error appears)
5. Click "Add field" or "Edit labels" ("Invalid or unexpected token" errors appear in console)

Your Environment

• SuiteCRM Version used: 8.0.0 prod release
• Environment: PHP 7.4, MariaDB 10.6
• OS: Docker Alpine 3.14.2
• Browser: Chrome 96.0.4664.55

Trying to install SuiteCRM8 from Github sources and having a few difficulties I was looking trough some of the files and I think I found a typo in bootstrap.php, there is "absrtact" which should probably be "abstract". It's not related to any issue I've had but I though it's worth reporting it:

Issue

Blanck page after fresh install

Expected Behavior

Login page

Actual Behavior

Possible Fix

Steps to Reproduce

Context

Your Environment

• SuiteCRM Version used: 8-Beta1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)):Chrome
• Environment name and version: MySQL, PHP 7
• Operating System and version : Debian

Issue

Had some initial issues with installation and setting up email but these have now all been resolved. The issue I am currently having, and hoping someone can point me in the right direction, is that if we use accounts without 2FA then everything works as it should and the team can log in without any problems. However, if we enable 2FA on any of the accounts, it generates the 2FA email which the users receive after correctly typing their credentials into the user interface, but instead of the user interface displaying the 2FA verification page so the user can type in the code they received by email, it logs the user out (sends them back to the username/password page) and presents a green error banner with the message “You have been logged out because your session has expired”.

As soon as we remove 2FA on the account it all works again as expected, less the 2FA email or verification webpage of course.

The same errors occur independently of clearing cache locally and on the server and also tested with different client PC’s and different browsers and all give the same result.

Not sure if related, but another annoying issue is when the user logs out, they are unable to log in again on the same browser window without an error message “Login credentials incorrect, please try again.” - if they close the browser window and try again, works without any problems.

Expected Behavior

Expected that after a successful username and password are entered, that the 2fa verification page would be displayed to allow users to add their received email 2FA code.

Actual Behavior

Returns to the login screen after correct username and password added and displays the error "You have been logged out because your session has expired".

Possible Fix

No real idea other than it may be related to session cookies or code.

Steps to Reproduce

1. From within a working account go to the user settings as an administrator and add a check to the enable 2fa section and save
2. When the user then tries to login, the email is sent with a 2FA code to the correct email address, but the verification page is not displayed to the user.

Context

This issue will mean we are unable to deploy live, but we don't have plans for migration until April 1st so nothing so far will be delayed. I do feel this issue is fairly urgent, however, as 2FA is becoming a defacto standard for online services and as such will be an important part of anyone's security protection for such a product or service.

Your Environment

SuiteCRM 8.0.1 used
Tested with various browsers including Chrome, Edge and Firefox on Windows 11 and Windows 10.

Issue

Fresh installation of SuiteCRM 8.0.1 and everything else seems to be working correctly. However after I have imported an Email, whenever I open up the actual Email record and hit Reply, Reply to All or Forward, I get the “Bad data passed in; Return to Home” error.
When I go composing a new email or when I hit Reply from the Email Dashlet without actually opening up the Email record, it works without issues.

Expected Behavior

The modal window with e-mail composition should open when I try to reply or forward an imported e-mail.

Actual Behavior

A "Bad data passed in;" error is displayed.

Steps to Reproduce

1. Import an e-mail
2. Open the e-mail
3. Select Actions->Reply
4. Note the error being displayed instead of modal window

Context

I am currently unable to effectively work with e-mails inside SuiteCRM.

Your Environment

• SuiteCRM Version used: 8.0.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome Version 96.0.4664.110 (Official Build) (64-bit)
• Environment name and version (e.g. MySQL, PHP 7): PHP 7.4
• Operating System and version (e.g Ubuntu 16.04):Debian 11

Issue

When using a location-specific URL, and unauthorised, you are taken to the login page. Once logged in and now authorised you are not redirected to the location-specific URL from before only taken directly to the Dashboard.

Possible Fix

Only redirect to Homepage after login if URL from before you are redirected to the homepage was invalid.

Steps to Reproduce

1. Try to go to https://suite8demo.suiteondemand.com/#/home/about
2. Once redirected to the login page, enter will, will as credentials
3. See that once logged in you are not taken to about page but only do homepage

Context

Lowers efficiency when using CRM compared to Suite7

Your Environment

• SuiteCRM Version used: 8.1
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome 97.0.4692.71
• Environment name and version (e.g. MySQL, PHP 7): MariaDB PHP 7.4
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 20.04

Issue

Hello, I have been checking SuiteCRM with the newest version to see if it can fit our needs, and when trying to debug LDAP authentication (set via the web interface as admin in Password administration) I notice that the code never hits this class:
https://github.com/salesagility/SuiteCRM-Core/blob/master/public/legacy/modules/Users/authentication/LDAPAuthenticate/LDAPAuthenticateUser.php

I tested this by enabling debug logging and adding various logging calls in different places.

It looks to me like the login logic goes through the code in core/backend, which has no single mention of LDAP.

Since it is not mentioned in the release notes, it would be expected that 8.0 is able to perform LDAP authentication.

Expected Behavior

LDAP authentication works, or at least is tried, when it is set up.

Actual Behavior

LDAP authentication doesn't work.