Dynamic view folder destination in laravel 5.3

is "Nitseditor\System\Resources\Views\Themes\" actually a path or is this a namespace of sorts?

Well I kept on trying to die dump the code and tried checking $app array. I guess when I try doing App::make::('config') laravel collects information from the configuration files and shows the configuration array of app in which dynamic configuration are not being displayed.

Then I simply tried checking my views:

return view('template');

It displayed the blade file/views exactly what I required, well it might help someone. Don't panic with

$app = App::make('config');
dd($app);

Cheers!!

@nitishnoetic I’m making a SaaS CMS that uses themes. The way I approached it was to use namespaced views, and every “site” has a service provider that prepends a path to the namespace hints.

So in my AppServiceProvider.php file:

public function boot()
{
    $this->app['view']->addNamespace('cms', config('view.paths'));
}

And then in each site’s service provider class:

public function boot()
{
    // IMPORTANT
    // You should determine whether the theme should be loaded or not here
    // This could be based on the hostname or something else
    // Otherwise each theme would override the last if you include them all in config/app.php
    $themeShouldLoad = true;

    if ($themeShouldLoad) {
        $this->app['view']->prependNamespace('cms', __DIR__.'/../resources/views');
    }
}

This means I can have a base “theme” in my core application, and then each theme can override any views it needs to (i.e. if I need to modify the HTML for that particular theme only). But the idea for me is to keep theme overrides to a minimum for maintainability.

This does come with the caveat that you need to include the namespace in all of your views:

@extends('cms::layouts.app')

Including in controller actions:

class HomeController extends Controller
{
    public function __invoke()
    {
        return view('cms::home');
    }
}

@martinbean it's a very good idea of implementing the views into namedspace. But I wanted to have without namedspace, though I know it will overwrite the views if present in main resources/views folder. But my resources/views folder is kind of empty.

Thanks for the update!

@nitishnoetic I agree, it would be nice to not have to have them namespaced, but at the time it was the only way I could get views set up the way I wanted them, as the prependLocation()> method on the view finder isn’t public; I could only append which isn’t what I wanted.

This approach really does help me for setting up multliple themes https://sebastiandedeyne.com/theme-based-views-in-laravel-using-vendor-namespaces/

hit like if the links works for you and support with this helpful approach.

cheers

I had a use case where I needed to display a different view depending on the incoming request. I have 2 base folders inside the resources/views directory, one it the default and the other set based on a condition.

if (true) {
$baseViewPath = 'resources/views/custom/';
view()->getFinder()->setPaths([$baseViewPath]);
}

I could have also used one of these

view()->getFinder()->addLocation($baseViewPath);
// or place it first in the list
view()->getFinder()->prependLocation($baseViewPath);