I m at Step 3: Confirm Field Mappings, when I click next nothing happens no error, but also it wont progress to next step.
I imported from template Leads.csv and completed all the required fields.
A blank screen typically means a 500 error. Check your php error log in your hosting. Also check the system log in admin for fatal errors.
90% of the time it’s usually file permissions or php memory limit issues.
Set the required permissions
If you are using the terminal you can do this by running:
find . -type d -not -perm 2755 -exec chmod 2755 {} \;
find . -type f -not -perm 0644 -exec chmod 0644 {} \;
find . ! -user www-data -exec chown www-data:www-data {} \;
chmod +x bin/console
Please have in mind that:
-
The user and group name (in the above example
www-data) needs to be replaced by the actual system user and group that your webserver runs under. This varies depending on your operating system. Common web server users are as follows:www-data(Ubuntu Linux/Apache)apache(Linux/Apache)
i already did this, still doesnt work: …/#/import/step1?import_module=Leads&return_module=Leads&return_action=in…
That hash-route (/#/) means you’re already inside the Vue / Angular front-end of SuiteCRM 8.
When the page goes totally white and nothing lands in php8.1-apache.log, the failure is almost certainly front-end JavaScript, not PHP.
Have you checked the browser console?
Unsatisfied version 8.8.0 from shell of shared singleton module core (required ^auto)
Ubuntu 22.04 + Apache 2.4.52 + PHP 8.1.2 + MySQL 8.0.41 with SuiteCRM 8 (Symfony 6.4.8).
Your tech stack looks correct as per compatibility.
from tail logs and chat gpt this is the problem: 1. Unsatisfied version 8.8.0 – hints that one of the front-end bundles was built against a different SuiteCRM/Angular version than what is now deployed; this is the only item that can realistically give you the “white screen” after the import wizard.
So the next debugging step is to make sure all JS bundles match the
backend version (re-build or re-deploy the public/build/ assets for the
exact SuiteCRM 8.x.y you’re running).
Maybe you can run the JS repairs from the admin dashboard.
Repair → you will see repairs for JS
From root folder of SuiteCRM:
Clear Symfony cache:
php bin/console cache:clear
did it same blank screen even in incognito after rebuild
I’d continue looking into the server first, not the CRM.
Check each individual PHP extension and see, whether it is loaded:
https://docs.suitecrm.com/8.x/admin/installation-guide/webserver-setup-guide/
(for instance via a php_info file in the public folder).
I had similar issues recently with a provisioned server and gd as well and intl have been lacking, which can lead to odd cascading / dependency issues.
Have you installed the 8.8 version as well, or was it an upgrade? There is a pre-check page during installation now, which validates some of the environment details.
PHP 8.1 is the lowest version it can run on - but I haven’t tried Suite8.8 on PHP8.1, yet. It’s slowly time to look into an upgrade there as well.
Vhost fits? htaccess and config unchanged? No custom code?
And eventually file permissions as mentioned above.
The import is really a standard feature and runs without any problems - unless there are server issues.
1 Like
tnx, I will try also this in the next days and I will let you know. If its not working I think I will leave permanently suitecrm to much hassle and problems.
You know what I had this problem recently. It’s not a 500 error, its a styling problem. Scroll down and you will find the next step of the import below the fold of the screen.
I deleted suitecrm entirely and choose another solution. I expected after this problem to appear another and another for simple things.
oh no! which CRM you moved to? Is it open source?
I moved to one where the import function is working. I understand that SuiteCRM is good, but I was looking for a CRM where the import feature is functional, as it’s important for my use case. I’m not sure if I’m allowed to publicize it here, but there are many CRMs with that function working that are free or opensource.
Got it!
I tried it in the demo instance. It worked for me. We need to wait few seconds to see step 4.
username & password: will
@office
I was actually able to replicate the issue by chance.
My csv file was ; separated.
During my first import on 8.9 beta, the import wizard didn’t recognize the semicolon and had still the standard comma in the import settings.
Then, I got the same issue like you as well - step 4 had an empty page (despite header and footer).
The import still worked though.
I deleted the records, imported again, now making sure, that I match the file with the settings in step 2:
and now it worked as expected.
Step 4 and 5 are completing and I can see the summary afterwards:
1 Like