Let's say that I add the following function to app/PageTemplates.php:

    private function test_me()
    {
        $this->crud->addField([
            'name' => 'testme',
            'label' => 'Test Me',
            'placeholder' => 'Test me placeholder',
        ]);
    }

This behaves as expected.

However, there are no fields named testme in the model so when I enter a value into the text input labelled Test Me it's not stored...anywhere!

I then changed the field to:

    private function test_me()
    {
        $this->crud->addField([
            'name' => 'testme',
            'label' => 'Test Me',
            'placeholder' => 'Test me placeholder',
            'fake' => true, // Look, pa, we're fake now!
        ]);
    }

...and my test was saved.

@tabacitu - this might be intended behaviour, however it's somewhat unintuitive to me and probably needs some documentation in the README.md; I'd write the documentation but I don't know what the intended behaviours are meant to be...

I get this warning message upon installing this package:

Warning: Ambiguous class resolution, "Backpack\Settings\database\seeds\SettingsTableSeeder" was found in both "/home/vagrant/Code/Laravel/vendor/backpack/settings/src/database/seeds/SettingsTableSeeder.php" and "/home/vagrant/Code/Laravel/database/seeds/SettingsTableSeeder.php", the first will be used.

I've added a new function contact in the file PageTemplates.php like this:

private function contact()
    {
        $this->crud->addField([
            'name' => 'adres',
            'label' => 'Adres',
            'type' => 'address',
            'placeholder' => 'Oudstrijdersstraat 37, 8770 Ingelmunster',
            'store_as_json' => true
        ]);

        $this->crud->addField([
            'name' => 'telehpone',
            'label' => 'Telefoon',
            'type' => 'text',
            'placeholder' => '051/30 28 44',
            'store_in' => 'extras',
        ]);

        $this->crud->addField([
            'name' => 'email',
            'label' => 'Email',
            'type' => 'email',
            'placeholder' => '[email protected]',
            'store_in' => 'extras',
        ]);
    }

But when I fill in the form and save the data my custom fields (that I've added in my function) are not saved.

I added user_id to DB pages table and I'd like to show pages if page's user_id is the same as the $user->id in admin/page page.

Where should I put this logic or how can I extend PageCrudController?

It would:

1. create model that extends the one from vendor
2. create crudcontroller that extends the one from vendor
3. create request that extends the one from vendor
4. inform the developer to copy-paste some routes in his route file

This would make it much easier to overwrite the default functionality.

What would make it ever easier would be for this to be done by default, during the installation process. But it would take another 2 steps, and that's a lot. We could do this for all packages, after we build the installer. And then:

• modifying some Backpack behaviour would be so much easier;
• you'd have the appropriate files (controllers, models, routes) insinde your app, so you understand how it works a lot easier;

Is there any way that I can add different PageTemplates?

I tried to create one App\CenterPageTemplates.php and using it in a new controller. But when I change a template, I get error 404.

I'm trying to edit the page form so I can upload an image with the post, however I can't get anything stored as a file or get the path stored in the database.

In PageTemplates.php:

$this->crud->addField([ 
            'name' => 'image',
            'label' => 'Photo',
            'type' => 'upload',
            'upload' => true,
            'fake' => true
        ]);

In Page.php:

public function setImageAttribute($value)
    {
    	Log::info('New Image upload:');
        Log::alert(json_encode($value));
        $attribute_name = "image";
        if (request()->hasFile($attribute_name) && request()->file($attribute_name)->isValid()) {
            throw new \Exception('xxxIT SHOULD WORK'); 
        }

        $disk = "public";
        $destination_path = "/uploads";       
        $this->uploadFileToDisk($value, $attribute_name, $disk, $destination_path);
    }

The log alert returns an empty array, so the image isn't even getting to the setImageAttribute function.

Any help would be greatly appreciated thanks!

Hi
It was
Cviebrock\EloquentSluggable\SluggableServiceProvider::class,
Backpack\PageManager\PageManagerServiceProvider::class,

It should be

Cviebrock\EloquentSluggable\ServiceProvider::class,
Backpack\PageManager\PageManagerServiceProvider::class,

Using the admin panel, I created a new page. But when I click on the 'open', it throws 404. What am I missing?

I created a page named 'About us' with slug URL as 'about-us' and tried various URLs to view the page:
myapp/about-us
myapp/about_us
myapp/page/about-us

But everything throws 404 :(

how I create my page and show on the front end after creating it in the laravel pack back-end?

Hey !
i cant install using composer coz pagemanger package required an old sluggable version and i have installed base and crud with sluggalbele package without problem but when i try pagemanger it never install at all

any solution ???

thank you in advance

Hey
i tried to use page manager and it works when i add new text type field but when i change the type to image it does not work
and i get error page:

QueryException in Connection.php line 770: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'extras' at row 1 (SQL: update pages set extras = {"meta_title":"dfdsfdsf","meta_description":"fffff","meta_keywords":null,"slide1":"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPkAAAD5CAYAAADlT5OQAAAgAElEQVR4nLy955Mj15mv2d92I3bj3pFET8pLM5JGmju62pi5s7FzTYzR1

is there a solution to do that?

Bug report

What I did:

What I expected to happen:

What happened:

What I've already tried to fix it:

Backpack, Laravel, PHP, DB version:

It appears that i18n is missing for this package!

This would be a relatively "easy" first PR as it really involves little change to the actual code structure!

I'm trying to use this package but after following installation spteps I've this error
"Class Backpack\PageManager\App\Http\Controllers\Admin\PageCrudController does not exist"
when I go to /admin/page

Has anyone have this problem too?

I created a class that extends PageCrudController and set a different route

<?php

namespace App\Http\Controllers;

class PageController extends \Backpack\PageManager\app\Http\Controllers\Admin\PageCrudController
{
    public function setup() {
        parent::setup();
        $this->crud->setRoute("XXXXXXXXX");
    }
}

Then, in pagemanager.php changed the Controller to use that class

<?php

return [
    // Change this class if you wish to extend PageCrudController
    'admin_controller_class' => 'App\Http\Controllers\PageController',

    // Change this class if you wish to extend the Page model
    'page_model_class'       => 'Backpack\PageManager\app\Models\Page',
];

Problem is, routes keep the same, only thing that change are the buttons like "Add Page"

php artisan route:list

I've seen that routes are hard-coded in setupRoutes()
in:
vendor\backpack\pagemanager\src\PageManagerServiceProvider.php

    public function setupRoutes(Router $router)
    {
        // Admin Interface Routes
        Route::group(['middleware' => ['web', 'admin'], 'prefix' => config('backpack.base.route_prefix', 'admin')], function () {
            $controller = config('backpack.pagemanager.admin_controller_class', $this->adminControllerClass);

            // Backpack\PageManager routes
            Route::get('page/create/{template}', $controller.'@create');
            Route::get('page/{id}/edit/{template}', $controller.'@edit');

            // This triggered an error before publishing the PageTemplates trait, when calling Route::controller();
            // CRUD::resource('page', $controller . '');

            // So for PageCrudController all routes are explicitly defined:
            Route::get('page/reorder', $controller.'@reorder');
            Route::get('page/reorder/{lang}', $controller.'@reorder');
            Route::post('page/reorder', $controller.'@saveReorder');
            Route::post('page/reorder/{lang}', $controller.'@saveReorder');
            Route::get('page/{id}/details', $controller.'@showDetailsRow');
            Route::get('page/{id}/translate/{lang}', $controller.'@translateItem');
            Route::resource('page', $controller);
        });
    }

Shouldn't it use the same route?

How to change the routes?

Soz but I don't have time to contribute :

Bug report

What I did: i have installed Backpack Page manager

What I expected to happen: I Expected Fake Field Such meta Data to be retrieving data on edit but they donot

What happened:

What I've already tried to fix it:

Backpack, Laravel, PHP, DB version:

Hi! Am i doing something wrong? tried creating a home page from the page manager and placed / on the page slug but i am getting an error.

I want to add photo galleries to pages by using a custom template and i would need to know, for example, how to read the disk that is associated with the field that contains the images in order to be able to delete those files when i want.

when following the documentation .. publish does not move the migration file. it has to be copied be hand

https://github.com/Laravel-Backpack/PageManager/blob/master/src/app/Models/Page.php#L53

What is this doing exactly?

I'm currently in need of unique pages (one page per template) which can only be edited but neither deleted nor a second one created.

Think of something like the imprint or privacy page, a contact page, some describing text and image for landing... (I think you get the idea)

I have currently implemented this functionality in a project of mine based on page manager and wonder if this should be integrated in this package.

If you find this useful I would prepare a PR to add this functionality here, otherwise I will create an extra package for this (as this is quite useful in many client projects).

I was curious if there was some interest/want on the option of a "Sidebar" for pages, I was thinking similar to how "Page Templates" are used but instead of a whole new "SidebarTemplates" file, just add a new folder pages\sidebars and scan the directory. Because there generally shouldn't be much content dynamically being made in those (from what i can think of) save a step of editing that file and more bloat.

Thoughts/feedback?

Note: I have a sorta working prototype of doing it simply by working with the PageTempaltes files but think it might be something a lot of people are interested in.

I'm trying to upload multiple images on page edit form. In my PageTemplates.php I have

$this->crud->addField([ 
	    'name' => 'images',
	    'label' => 'Fotos',
	    'type' => 'upload_multiple',
	    'upload' => true,
	    'disk' => 'uploads',
	    'hint' => 'Some hint text.',
	    'fake' => true
	]);

In my Page model I have:

public function setImagessAttribute($value)
    {
        $attribute_name = "images";
        $disk = "uploads";
        $destination_path = "images/pages";

        $this->uploadMultipleFilesToDisk($value, $attribute_name, $disk, $destination_path);
    }

In my $disks array in config/filesystems.php I have:

'uploads' => [
    'driver' => 'local',
    'root' => public_path('uploads'),
],

But when I try to save the page I have 2 problems:

• Images aren't saved in folder (folder is writeable!)
• Not saved in database

In my database extras field for that page I get:

"images":[  
      {  

      },
      {  

      }
   ],

When I attempt to add an image in the PageTemplate using the following code:

$this->crud->addField([ // image
            'label'  => "Header Logo",
            'name'   => "img_header_logo",
            'type'   => 'image',
            'crop'         => true,
            'fake'         => true
        ]);

It will first allow me to upload an image, which is stored in the database.

If I display the image in a view, it works. However if I then edit the page, it preappends the websites URL to the image and therefore can no longer be used.

1. Is this an issue or something I am doing?
2. How can I just store the image as a file?

This is with PageManager

Is there a way to modify the config for the ckeditor? It's removing the classes when I edit a page.

Hi,

I created a one-to-many relation between app/Models/Page.php and app/User.php. And added user_id in pages DB. This allows me to show/edit posts who owns it.

Now L5.4 does not allow to access a session in a constructor, I am wondering how to add a hidden field with value of user_id. Since $this->crud->addField is in constructor, I have difficulty to use it. Any solution for this?

<?php
namespace App\Http\Controllers\Admin;

use Auth;
use App\Models\Page;
use Backpack\PageManager\app\Http\Controllers\Admin\PageCrudController as OriginalPageCrudController;

class PageCrudController extends OriginalPageCrudController
{
    protected $user;

    public function __construct()
    {
        parent::__construct();
        $this->crud->setModel("App\Models\Page");

        $this->middleware(function ($request, $next) {
            $this->user= Auth::user();
            return $this->user->can('Pages') ? $next($request) : redirect(config('mycms.dashboard'));
        });

        $this->crud->addColumn([
            'name' => 'user_id',
            'type' => 'model_function',
            'function_name' => 'getWriterName',
        ]);

        $this->crud->addField([
            'name'  => 'user_id', 
            'type'  => 'hidden', 
            'value' => $this->user->id, // this does not work.
        ]);

    }
}

Enable package auto-discovery for faster installation on L5.5. Eliminate 2-3 steps out of the installation process with a small composer modif:

https://medium.com/@taylorotwell/package-auto-discovery-in-laravel-5-5-ea9e3ab20518

I've installed the demo, then followed the directions on https://github.com/Laravel-Backpack/PageManager#example-front-end

Also ran the command to publish views, etc:

$ php artisan vendor:publish --provider="Backpack\PageManager\PageManagerServiceProvider"
Copied Directory [\vendor\backpack\pagemanager\src\resources\views] To [\resources\views]
Copied Directory [\vendor\backpack\pagemanager\src\database\migrations] To [\database\migrations]
Publishing complete for tag []!

When I go to open the page I get:

InvalidArgumentException in FileViewFinder.php line 137:
View [pages.services] not found.

in FileViewFinder.php line 137
at FileViewFinder->findInPaths('pages.services', array('C:\xampp\htdocs\backpack\resources\views')) in FileViewFinder.php line 79
at FileViewFinder->find('pages.services') in Factory.php line 174
at Factory->make('pages.services', array('title' => 'test', 'page' => object(Page)), array()) in helpers.php line 855
at view('pages.services', array('title' => 'test', 'page' => object(Page))) in PageController.php line 21
at PageController->index('test')
at call_user_func_array(array(object(PageController), 'index'), array('page' => 'test')) in Controller.php line 55
at Controller->callAction('index', array('page' => 'test')) in ControllerDispatcher.php line 44
at ControllerDispatcher->dispatch(object(Route), object(PageController), 'index') in Route.php line 189
at Route->runController() in Route.php line 144
at Route->run(object(Request)) in Router.php line 642
at Router->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in VerifyCsrfToken.php line 65
at VerifyCsrfToken->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in ShareErrorsFromSession.php line 49
at ShareErrorsFromSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in StartSession.php line 64
at StartSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37
at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in EncryptCookies.php line 59
at EncryptCookies->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Router.php line 644
at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 618
at Router->dispatchToRoute(object(Request)) in Router.php line 596
at Router->dispatch(object(Request)) in Kernel.php line 267
at Kernel->Illuminate\Foundation\Http\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in CheckForMaintenanceMode.php line 46
at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Kernel.php line 149
at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 116
at Kernel->handle(object(Request)) in index.php line 53

Seems like a problem with the view?

Hi,
I've created some template in PageTemplates, but extras datas are not stored :(

I have missed something ?

Hi guys, this is only a minor issue but I thought I'd flag it anyway.

Steps to reproduce:

1. create a custom PageTemplate (e.g. "contact") defined within the trait at app\PageTemplates.php
2. create a new page, assign the "contact" template and save
3. delete the custom PageTemplate from app\PageTemplates.php
4. attempt to edit the page created in step 2

You receive "BadMethodCallException in Controller.php line 82: Method [contact] does not exist."

I found that PageCrudController in PageManager uses public function __construct() and UserCrudController in PermissionManager uses public function setup(). And other controllers also use public function __construct(), rather than public function setup().

Are there any differences? Should PageCrudController use public function setup()?

Hi, I need just static translate strings. But I do not know of any way except editing vendor's PageCrudController.php. For known reasons, I do not want to do this. Does anyone know a civilized way to translate PageManager?

Basically that, I see that there's default rules in the PageRequest controller, but how can we target different rules for different pages that we create?

the newCrud and PageManager package have conflict wiht Sluggable package.
so please fix this .

NewsCrud use a diffirent version for sluggable package

I've looked through the issues and read the issues concerning pages. But nothing seems to work. I think I may have missed a step.
I have-

• cloned demo
• composer install
• composer update

But I still get this error message in log. Any help would be greatly appreciated.
Thanks

2017-06-26 15:55:02] local.ERROR: ReflectionException: Class Backpack\PageManager\App\Http\Controllers\Admin\PageCrudController does not exist in /var/www/site/vendor/laravel/framework/src/Illuminate/Container/Container.php:729 Stack trace: #0 /var/www/site/vendor/laravel/framework/src/Illuminate/Container/Container.php(729): ReflectionClass->__construct('Backpack\\PageMa...') #1 /var/www/site/vendor/laravel/framework/src/Illuminate/Container/Container.php(608): Illuminate\Container\Container->build('Backpack\\PageMa...') #2 /var/www/site/vendor/laravel/framework/src/Illuminate/Container/Container.php(575): Illuminate\Container\Container->resolve('Backpack\\PageMa...') #3 /var/www/site/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(728): Illuminate\Container\Container->make('Backpack\\PageMa...') #4 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Route.php(217): Illuminate\Foundation\Application->make('Backpack\\PageMa...') #5 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Route.php(747): Illuminate\Routing\Route->getController() #6 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Route.php(708): Illuminate\Routing\Route->controllerMiddleware() #7 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Router.php(587): Illuminate\Routing\Route->gatherMiddleware() #8 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Router.php(567): Illuminate\Routing\Router->gatherRouteMiddleware(Object(Illuminate\Routing\Route)) #9 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Router.php(535): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request)) #10 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Router.php(513): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request)) #11 /var/www/site/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(174): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request)) #12 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request)) #13 /var/www/site/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #14 /var/www/site/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure)) #15 /var/www/site/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #16 /var/www/site/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #17 /var/www/site/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(149): Illuminate\Pipeline\Pipeline->then(Object(Closure)) #18 /var/www/site/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request)) #19 /var/www/site/public/index.php(52): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request)) #20 {main}

Hi,
im creating a master layout and i would like to display the metas in the head..for the title im using {{$title}} and it works..
{{$page->title}} also works.. because title is in its own column.. but what about the extras column?
when i use {{$page -> extras}} i get {"meta_title":"services","meta_description":"services","meta_keywords":"services"} as an echo but how do i select which of the above to show?
ive tried using dot annotation like {{$page->extras.meta_title}}, and {{$page->extras->meta_title}}, and {{$page->extras[meta_title]}} but none of them work..
how can i pass these values separately in the view?
any pointer would be great.. thanks.

In my PageTemplates.php I have a field like this:

$this->crud->addField([
	'name' => 'adres',
	'label' => 'Adres',
	'type' => 'address',
	'fake' => true,
]);

Now I would like to save also the latitude and longitude of the address they give in (if it can be found). I've copied the PageCrudController and changed the config in config/backpack/pagemanager.php to:

return [
    'admin_controller_class' => 'App\Http\Controllers\Admin\PageCrudController',
    'page_model_class'       => 'App\Models\Page',
];

In my store function I have:

public function store(StoreRequest $request)
{
    $address = $request->request->get('adres');
    $addressObj = app('geocoder')->geocode($address)->get()->first();

    if($addressObj)
    {
        
    }

    $this->addDefaultPageFields(\Request::input('template'));
    $this->useTemplate(\Request::input('template'));

    return parent::storeCrud();
}

But what do I place in the if statement? How can I add (= set) an extra field to the extras field in my database?

By default the sample pages are defined as private methods. In the interest of keeping the template definitions organized it would be nice to define "fieldsets", so to speak, as protected methods from inside the private method which defines the page. This allows for re-use and de-cluttering if you're adding (for example) the same meta fields to several pages types.

Currently, attempting this causes the method created for the fields to show up in the template drop down menu in the admin panel. If a filter is added to the reflection on trait we can separate these methods.

#34

If you leave slug empty then it shows blank screen and page don't creates

Bug report

When enable revisions to PageManager, it not resolve revisions URI`s
Like this one - http://127.0.0.1:8000/admin/page/2/revisions
Server returns 404 error

What I did:

Fix by add revision routes to PageManager, but i can`t make git push to this repo.

What I've already tried to fix it:

Please add this two strings to /pagemanager/src/routes/backpack/pagemanager.php

Route::get('page/{id}/revisions', $controller.'@listRevisions');
Route::post('page/{id}/revisions/{revisionId}/restore', $controller.'@restoreRevision');

Please add

use App\Http\Controllers\Controller;

to the PageController Example. The one displayed results in HTTP 502

I ran composer update on my Backpack demo project and now the route for /admin/page results in a 404. It was working fine before the update. I'm using the Backpack 3.0 Demo. I think it has something to do with the new Laravel 5.3 route changes. .... any thoughts?

Suggestion

Does it make sense for developers to be able to configure the location of PageTemplates.php?
If possible I would like to be able to move PageTemplates.php inside a folder, just to keep the project organized.

There is the possibility to extend page_model_class and thereafter, manually relocate PageTemplates.php, but by adding an extra parameter to config maybe a page_template_class, it would be easier to just relocate PageTemplates.php.

If you agree with this, I can help with a PR!

I have categories and Products Models. I need to display products by categories and individual products details. But i am not getting any ideas how to display them in custom templates (frontend).

Hi,

Using the PageManager, I created a simple page with a slug as 'about'. I am unable to view this page when I click on Preview (redirects to url myapp/about), I receive a 404 error.

I tried various URLs to view the page. I receive a 404 error on the below urls
myapp/about
myapp/page/about
myapp/admin/about

I receive a 403 error on the below paths for this url - myapp/admin/page/about

i think the requirement for sluggable version is not correct
please fix it
sluggable package has been released to ver 4.0

thank you in advance

Sorry if I am going crazy but I can't figure this out.

I need to override Backpack\PageManager\app\Http\Requests\PageRequest class

to change the authorize method so that it uses my custom authentication method rather than the standard Illuminate Auth check.

I have created App\Http\Requests\PageRequest but that does not override it.

So I tried to create my own PageCrudController as follows:

<?php

namespace App\Http\Controllers\Admin;

use Backpack\PageManager\app\Http\Controllers\Admin\PageCrudController as BackpackPageCrudController;
use App\Http\Requests\PageRequest as StoreRequest;
use App\Http\Requests\PageRequest as UpdateRequest;

class PageCrudController extends BackpackPageCrudController
{
    public function store(StoreRequest $request)
    {
        $this->addDefaultPageFields(\Request::input('template'));
        $this->useTemplate(\Request::input('template'));

        return parent::storeCrud();
    }

    public function update(UpdateRequest $request)
    {
        $this->addDefaultPageFields(\Request::input('template'));
        $this->useTemplate(\Request::input('template'));

        return parent::updateCrud();
    }
}

Now I receive:

Declaration of App\Http\Controllers\Admin\PageCrudController::store(App\Http\Requests\PageRequest $request) should be compatible with Backpack\PageManager\app\Http\Controllers\Admin\PageCrudController::store(Backpack\PageManager\app\Http\Requests\PageRequest $request)

How can I override it with this conflict?