Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Class "CIDRAM\CIDRAM\FrontEnd" not found #569

Closed
uudruid74 opened this issue Mar 17, 2024 · 4 comments
Closed

Class "CIDRAM\CIDRAM\FrontEnd" not found #569

uudruid74 opened this issue Mar 17, 2024 · 4 comments

Comments

@uudruid74
Copy link

OK, I can get an Access Denied message if I try to run the frontend from the command line. When run via the webserver, all I get is ...

2024/03/17 09:55:34 [error] 98554#98554: *12896 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Class "CIDRAM\CIDRAM\FrontEnd" not found in /var/www/devel.pixelpotion.cafe/htdocs/cidram.php:3
Stack trace:
#0 {main}
  thrown in /var/www/devel.pixelpotion.cafe/htdocs/cidram.php on line 3" while reading response header from upstream, client: 208.63.89.42, server: devel.pixelpotion.cafe, request: "GET /cidram.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm-php8.1.sock:", host: "devel.pixelpotion.cafe"

Any idea on why this is not finding the class? I did enable the front-end in the config.ini, and turned on a bunch of logs, but I'm not getting any log messages except for the nginx error above. Spent 3 hours on this on not getting anywhere.

@Maikuolan
Copy link
Member

Just to clarify, which major version of CIDRAM (e.g., v1, v2, v3) are you currently using?

@uudruid74
Copy link
Author

uudruid74 commented Mar 17, 2024 via email

Maikuolan added a commit that referenced this issue Mar 18, 2024
Maikuolan added a commit to CIDRAM/cidram.github.io that referenced this issue Mar 18, 2024
Maikuolan added a commit to CIDRAM/Docs that referenced this issue Mar 18, 2024
Maikuolan added a commit to CIDRAM/.github that referenced this issue Mar 18, 2024
@Maikuolan
Copy link
Member

It seems the tarball and zip links were pointing to the wrong major version branch. I hadn't realised that. Sorry for the trouble and thanks for pointing out the problem.

I've fixed the links, so it should now be pointing to the correct major version (the current latest major version, v3). :-)

@Maikuolan
Copy link
Member

Closing the issue for now as fixed. If there are any problems, let me know, and I can help to work through them with you if needed, and good luck. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants