I recently upgraded to 8.9.1 and today I tried to import some products into my system and I got a blank screen after importing or during that process . here is the tale end of my url
step1?import_module=AOS_Products&return_module=AOS_Products&return_action=index
can anyone point me in the right direction?
More details
I’m running SuiteCRM 8.9.1 in a split Symfony plus legacy install under /prod891/public/legacy. I tried importing product data using the Admin Tools Import Wizard and also the SPA import route /#/import/…, but after uploading the file the screen went blank and the browser console showed HTTP 500 errors. On the server side, the logs showed repeated Invalid CSRF token events and cache container missing file errors, which lined up with the import flow failing. To work around the UI import issues, I attempted a CLI based import script that bootstraps the legacy app from public/legacy and creates records programmatically. While troubleshooting the script, I fixed multiple path and bootstrap issues specific to SuiteCRM 8’s directory structure. After that, I discovered the key blocker: public/legacy/modules/ProductTemplates/ProductTemplate.php does not exist on my instance, so the ProductTemplates module is not present or not installed. At the same time, I confirmed that AOS_Products is installed and present at public/legacy/modules/AOS_Products. At this point, I’m trying to understand what the correct “product catalog” module is supposed to be in a SuiteCRM 8 setup using AOS, and what the supported approach is for importing product catalogs when the Import Wizard either refuses the module type or fails with blank screens and 500 errors.
Tested this on the Demo CRM and its working Fine.
Best to configure your webhost / virtual host so that you can use a domain / subdomain (if it is local, than use your hosts file).
In that way, you can configure a standard VHost setup and don’t have to worry about redirects / mod_rewrite / .htaccess etc.
mycrmurl.com’s DNS address could not be found. Diagnosing the problem.
DNS_PROBE_POSSIBLE
Bastian,
I will look into that For some reason its working now without having done anything.
Regards