How can I return PHP pages?

ttrepper wrote:

but I do not understand what I have to do now? I guess it needs a class (?) called “Bridge” with a method called “default” (?) but what is “Front” saying? I would highly appreciate if someone could point me to the next steps please.

Router tries to match given url to presenters' action. Based on rules you define for Presenter mapping (documentation) – meaning mapping to namespaced presenter class.

In your example your fallback route will try to call presenter called Front:Bridge with action default. It means it will look for presenter with following mapping:

• default: action to be called on Presenter
• Bridge: it will look for presenter called BridgePresenter
• Front: given BridgePresenter will be in module Front. And where it will look for it, depends on your presenter mapping as defined in your common.neon. So if we take an example from documentation I linked above:

# example from docs
application:
	mapping:
		Front: App\Modules\Front\Presenters\*Presenter
		Admin: App\Modules\Admin\Presenters\*Presenter
		Api: App\Api\*Presenter

It will look for presenter class App\Modules\Front\Presenters\BridgePresenter, because Front module resolves to App\Modules\Front\Presenters namespace.

I would strongly recommend you go through Quick start, where you will create simple app, in which you can understand Nette's fundamentals.

ttrepper wrote:

Thank you very much @mskocik and @SamuelThorn – your answers helped me a lot. I did the quickstart but I have never found something about any naming conventions. So for example does the Presenter have to be named SomePresenter or is a class called “Some” enough? I can try it out but I am wondering if there are any or more (im- or explicit) naming conventions?

Thank you very much in advance,
Thomas

It's still related to mapping configuration. Please read carefully documentation about Modules

But to answer your question directly…If you have mapping like this in your common.neon:

application:
	mapping:
		*: App\Modules\*\Presenters\*HandlerClass	# just an example to make it clear
		# this will be translated to:
		<any module> map to: App\Modules\<given module>\Presenters\<Presenter>HandlerClass

And your request should be handled by MyModule:Request:default (from route definition), it will look for:

<?php

namespace App\Modules\MyModule\Presenters;

class RequestHandlerClass extends \Nette\Application\UI\Presenter
{
  // your class
}

So as you can see, your presenters (controllers – call them anyway you want), don't need to have Presenter in the class name. It's just Nette's convention. It's the same how some/most others frameworks use word Controller. Hope it's clear now.

Depends on how your old php page is written. Does it just return page content as your code suggests? Or does it render page content directly?

But if it does something else except creating content it might not be possible because things like session handling or sending headers would conflict with how Nette do these things.

If it is the case then I think something like this should work:

class RequestHandlerClass extends \Nette\Application\UI\Presenter {

	public function renderSomething() {
        $this->sendResponse(new Responses\CallbackResponse(function ($httpRequest, $httpResponse) {
            require __DIR__ . '/path/to/myOldPhpPage.php';
        }));
    );

}

It creates CallbackResponse that calls given callback when it is emmited. Given callback simply requires your old script that outputs content. This response is then send from render method of given action something by call to sendResponse().

Last edited by mystik (2023-08-11 18:57)