Short intro - classic view
The base of the app is angular. then there is a view called classic view. Which shows a legacy view within angular.
This classic view is enabled for some routes. The angular router configuration will decide if to display the regular view or classic view. Depending on configuration.
Classic view route configuration
As mentioned this is configuration driven. Check the configs in config/services/module/module_routing.yaml, the entries that are set to false, will use the classic view (legacy).
Also, any view that is not implemented yet on angular side will default to this classic view.
From an UI perspective youâll notice some slight differences on the styling/features ( button position, etc)
I just installed beta2 and got a successful installation. I configured Apache for mod_rewrite, I have all the compatible versions. When I attempt to access the vhost dir I get: âOops an error occurredâ and "The server returned a â500 Internal Server Errorâ and âSomething is broken please let us know what you were doing when this error occurredâ
Nothing of help in the apache error log, also checked prod.log and this was in there:
php.CRITICAL: Uncaught Error: Undefined constant âXML_PI_NODEâ {âexceptionâ:"[object] (Error(code: 0): Undefined constant âXML_PI_NODEâ at /var/www/suite8/cache/prod/ContainerV0Fx7x4/App_KernelProdContainer.php:579)"} []
Donât know if that is related. Not sure where else to look.
It looks like I needed some PHP modules installed - now Iâm getting a blank screen⌠could someone please detail ALL pre-requisite requirements to install?
Current install instructions for 8 beta are very vague. It would help to know that you have to install a slew of php modules before the app will work. Now Iâm at a blank screen and get no errors in any log files that I can see - nothing in the apache error log file and nothing new in the suitecrm.log file.
I may have spoke too soon - the 404 is not there but in the troubleshooting steps it says to make a call to: https://<your_host>/index.php/api/graphql and if rewrites are not set up correct, you will see this error about graphql query is not valid⌠I am still getting that, but mod_rewrite is installed and as far as I can tell itâs turned on.
I donât see any other errors on the network tab. The url is here if you want to try : https://crm8.zylatech.com
I am having a similar problem but I did install from a .zip file, not a repo. ( I did not even know there was a repo)
When I go to {URL} i get an error page telling me to ârun ng build from terminalâ but this is a NON-developer install and I do not have access to an ng command (I tried) and I di not install the developer tools (other than Composer, which is not listed on the Administrator Install guide but IS required.
When I go to {URL}/legacy I get the SUITECRM login page but with no css
I can login but I have no css so it is unusable
Any ideas what I am doing wrong?
I followed all the instruction for installing a NON-developer version of the Suitecrm 8 beta-2
I am doing this on a fresh install of Debian 10
I do have all ther apache, php and MySQL (MariaDB) installation requirements
I did create a virtual host at /var/www/suite8.ca and have edited the AllowOverride ALL settings for that directory
I have installed Composer in the root direcoty (/var/www/suite8.ca) and the legacy directory (/var/www/suite8.ca/public/legacy)
I did run all the file permissions as specified
The database configuration is as it should be and is confirmed in .env.local
I could not run the ./vendor/bin/pscss ⌠command in /var/www/suite8.ca/public/legacy becasue it errored out saying there was no such file or directory and when I checked, there was no bin directory in /var/www/suite8.ca/public/legacy/vendor
Yep - followed all the instructions and checked permissions multiple times. I know itâs a beta - hopefully they put together an installer for it like they have for version 7.
I see that the graphql call only returns a very minimal message with a âinternal server errorâ. Thats probably because Symfony APP_ENV is set to prod mod.
Could you please change the APP_ENV to qa on your .env.local please? to get some more info
Because there is another zip on the release notes page, and that is just a zip with the source code. Which is not the ready-to-install package. This one here:
@samus-aran, probably something we need to make clear on our documentation, this has happened before.