@shadkamel The make function looks as follows:

public function make(Request $request)
{
    $this->handleInputs($request);
    $avatar = new InitialAvatar();

    $image = $avatar->name($this->name)
        ->length($this->length)
        ->fontSize($this->fontSize)
        ->size($this->size)
        ->background($this->background)
        ->color($this->color)
        ->smooth()
        ->allowSpecialCharacters(false)
        ->autoFont()
        ->keepCase(!$this->uppercase)
        ->rounded($this->rounded);

    $image = $image->generate();

    return $image->response('png', 100);
 }

In terms of the HTML, do you mean the source code file or what the browser is getting (i.e. what the browser shows when I hit "show source")?

@shadkamel

One thing I just noticed:

That make function for class DefaultAvatarController in the file DefaultAvatarController.php has the following use statement: use LasseRafn\InitialAvatarGenerator\InitialAvatar;

But there is no folder "LasseRafn\InitialAvatarGenerator"

Instead, there is the following folder containing a file InitialAvatar.php vendor\lasserafn\php-initial-avatar-generator\src

Could that explain anything?

@ghabe Woops, yes you are correct

@LoveTheBlues sorry i was busy, have you fixed it or still not working

@shadkamel Thanks for chasing up. No, not yet fixed, but I think I have got to the point where I think it is a much more fundamental issue with the routes, rather than anything to do with this specific piece of code.

When I navigate to [website url]/getDefaultAvatar?item=2431&name=xxxx&size=40 I get a 500 error, and when I try do a "php artisan route:list", i get errors (see other response below), so I am trying to figure out how to chase down if there is an incorrect namespace or use statement in one of the controllers....

@LoveTheBlues read more and if you still wasn't clear, i am here for help.

@shadkamel I'm still struggling so would appreciate further help:

As I said, I get error when doing "php artisan route:list". The error it is complaining about is:

Cannot declare class App\Http\Controllers\Web\ContactController, because the name is already in use in app\Http\Controllers\Api\Web\ContactController.php

i.e. under app\Http\Controllers there are subdirectories "Web" and "Api\Web" containing files with the same names and defining the same controllers.

In routes\web.php, there is one definition of a route calling the ContactController.
In routes\admin.php there is another definition of a route calling the ContactController. In routes\api\guest.php there is another definition of a route calling the ContactController.

If I comment out the route definition in web.php, when I do "php artisan route:list" I get the same error. But if I comment out the route definition in \api\guest.php then that error complaining of name already in use goes away (and I get a different error)

So my questions are:

• Is this normal?
• How does Laravel know what controllers to load? Does it just load all controllers under under app\Http\Controllers and subdirectories? Or is there a file which lists which Controllers?
• If there is more than one controller with the same name how does the routing know which one to call?

UPDATE:

I think I am getting closer: I found that both the ContactControllers had the same namespace near the top:

namespace App\Http\Controllers\Web;

So I changed the one in the Api\Web directory to

namespace App\Http\Controllers\Api\Web;

@LoveTheBlues hello, if there are two class with different namespace and same name, then you have to use as keyword for change one of the controllers name for that specific file, here is an example:

App\Http\Controllers\Web\ContactController as WebContactController; App\Http\Controllers\Api\ContactController as ApiContactController;

@shadkamel In this case it turned out to be that the route was fine, but there was a bug in a function that the controller was calling. But your help and the help of everyone else who responded here helped me get rid of a whole lot of other latent bugs in the routing system. Doing "php artisan route:list" gave an error, so fixing that error (by correcting the namespace statement near the top) then gave another error, etc, so it was a bit like peeling the layers of an onion, until eventually "php artisan route:list" gave a clean response.

@LoveTheBlues so you mean you fixed your problem ?

@shadkamel Yes, I fixed the problem and also along the way fixed a bunch of other issues with other routes that would have probably manifested as issues later. The issue turned out to be that route was calling a controller that called the php function file_exists() with an argument being a file in a restricted folder. It seems that different versions of PHP treat that differently (or perhaps different configs of hosting server). i.e. 500 error vs running ok but returning false. The manual says it should throw a non-fatal E_WARNING but continue running.

Is there some etiquette on this forum on how to mark an issue "solved"?

@LoveTheBlues i am excited that you problem is solved, and you can just mark a reply as best answer even your replay too, then the forum will mark as solved.

@walayatkhan Thanks. How do I create the symbolic link?

@LoveTheBlues it can be created with php artisan storage:link. and Seeing your make method, the issue is not with storage link. try all above point and also clear cache of the browser. and try visit the avatar generation URL in the browser directly you might get the issue.

@Snapey Thanks. Yes you are right that this seems a bit of a convoluted approach. However in this case it is an application that I have inherited and have been asked to remediate/maintain... Long story. But yes, I'll check if the route is known and also look at simplifying to remove the need for the "Default Avatar" class.

@Snapey

OK, you are right: It seems that the issue is a far more fundamental issue with routes. The response I get from artisan route:list is as follows:

php artisan route:list

Execution /opt/plesk/php/8.2/bin/php has failed with exit code 255, stdout: Symfony\Component\ErrorHandler\Error\FatalError

Cannot declare class App\Http\Controllers\Web\ContactController, because the name is already in use

at app/Http/Controllers/Api/Web/ContactController.php:9

  5▕ use App\Http\Controllers\Controller;
  6▕ use App\Models\Contact;
  7▕ use Illuminate\Http\Request;
  8▕ 
  9▕ class ContactController extends Controller
 10▕ {
 11▕ 
 12▕     public function store(Request $request)
 13▕     {

2 [internal]:0 Whoops\Run::handleShutdown() , stderr: PHP Fatal error: Cannot declare class App\Http\Controllers\Web\ContactController, because the name is already in use in .../httpdocs/app/Http/Controllers/Api/Web/ContactController.php on line 9

i.e. the directories app/Http/Controllers/ and app/Http/Controllers/Api/ both have a "web" subdirectory containing similar files named the same but with slight differences. That is not normal is it?

@LoveTheBlues no, I think you are reading that wrong. You have an incorrect namespace or use statement in one of the controllers

@jackabroy665 Thanks for responding. Yes, the route is correctly defined. If I swap the code in the controller's make() function for

		return("Hello world"); 

and then navigate to it, I get the Hello World response but if I navigate to it with the original code in the controller's make() function then I get a 500 server error.

So it seems that the issue has nothing to do with the routing, and there is a bug in the function that the controller calls.... I'm getting closer... thanks again

@jackabroy665 Thanks, The issue is fixed and turned out to not be the route, as mentioned in my previous response to you. But please explain: How does a video streaming app that lets you watch movies fix Laravel route issues. Are you sure that advice is for Laravel routing? Or is it just what google AI responds when it thinks your question relates to trouble streaming your movie?

@sayanz Thanks, a good summary of what I had written, almost as though it was written by an AI bot summarising the thread. And some good suggestions for debugging, whether it was written by an AI bot or not. But why the spam link at the end?