I'm trying to develop my theme using the default Theme scaffold with browsreSync enabled the following are my configs

let mix = require('laravel-mix').mix;
const WebpackShellPlugin = require('webpack-shell-plugin');
const themeInfo = require('./theme.json');
mix.browserSync(
{
    proxy             : "http://dohlapse.test",
    logPrefix        : "Laravel Eixir BrowserSync",
    logConnections    : false,
    reloadOnRestart : true,
    files: [
           'public/**/*',
           'Themes/Dohlapse/**/*',
           'resources/views/**/*',
    ],
    notify: {
        styles: {
            top: 'auto',
            bottom: '0'
        }
    },
});
/**
 * Compile Sass
 */
mix.sass('resources/scss/main.scss', 'assets/css/main.css').styles([
        'node_modules/bootstrap/dist/css/bootstrap.css',
        'node_modules/slick-carousel/slick/slick.css',
        'resources/assets/css/menu.css',
        'resources/assets/css/style.css',
        'resources/assets/css/responsive.css',
    ], 'assets/css/all.css', __dirname);

/**
 * Concat scripts
 */
mix.scripts([
  'node_modules/jquery/dist/jquery.js',
  'node_modules/bootstrap/dist/js/bootstrap.js',
  'node_modules/slick-carousel/slick/slick.js',
  'resources/assets/js/flaunt.js',
  'resources/assets/js/main.js'
], 'assets/js/all.js');

/**
 * Copy Font directory https://laravel.com/docs/5.4/mix#url-processing
 */
// mix.copy(
//   'fonts',
//   '../../public/fonts'
// );

/**
 * Publishing the assets
 */
mix.webpackConfig({
  plugins: [
    new WebpackShellPlugin({onBuildEnd:['php ../../artisan stylist:publish ' + themeInfo.name]})
    // ,new BrowserSyncPlugin(
    //   // BrowserSync options
    //   {
    //     host: 'localhost',
    //     port: 3000,
    //     proxy: 'http://dohlapse.test'
    //   },
    //   // plugin options
    //   {
    //     // prevent BrowserSync from reloading the page
    //     // and let Webpack Dev Server take care of this
    //     reload: false
    //   }
    // )
  ]
});

and

"scripts": {
    "dev": "yarn run development",
    "development": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --debug --devtool eval-cheap-module-source-map --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch-poll": "yarn run watch -- --watch-poll",
    "hot": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --watch --progress --debug --devtool eval-cheap-module-source-map --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
    "prod": "yarn run production",
    "production": "node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
  },

on running npm run watch-poll the project is compiled and published but subsequent changes are not...... I'm running this in laravel's scotchbox homestead. Has anyone else encountered this issue?

In wordpress you can place the content of multiple pages on one page........is there any way that i can display "content" of multiple pages on one page in Asgard CMS??

Any tutorials here on building custom themes for Asgard?

I definitely have a factory

$factory->define(Modules\Brokerquotes\Entities\Insuree::class,....

And in a DatabaseSeeder I have

factory("Modules\\Brokerquotes\\Entities\\Insuree", 5)->create()-> ......

But when I try to call the seeder class directly using php artisan db:seed --class=.... I get the subject error

Now i know there is a php artisan module:seed but it doesn't have the --class option so it runs all the seeders. I just need to run some individual seeders from time to time.

What am I doing wrong here??

i've upgraded to the latest version of asgard cms 3.x I'm using the auth() to do most of my auth functions. I am also using the Sentinel package for my default user intents which apparently has its own auth functions.

My question is....can both auth and SentinelAuthentication be used to perform auth functions and yield the same result?

To bring perspective to my question....

I'm running a middleware that will log the user in by Id auth()->loginUsingId($id) however there is another middleware that checks for the logged in user using $this->auth->check() === false which apparently yields truth breaking my application.

should I be now using the SentinelAuthentication or is there some other way I should be using laravel's default auth functions. I was under the impression that the new version of Asgard made both functions compatible.

According to this discussions modifying the config properties would yeild the results

I have the User and Profile modules installed for asgard cms 3. How can I override the views from these two modules so that the views from my custom view is rendered in place of it? Sort of like if it exists in one location load it otherwise default to original view?

I'm using the asgard application to automatically register and login a dynamic user( user has no "backend" permissions). After doing this process I get the below screen
Clicking on either "Edit page" or "Back to Backend"

Brings up the subject error exception. What was the intention here? How do I avoid it and get rid of the blue nav area that led to this page?

I'm building my module to automatically register and login users to view parts of the said module. However, I in running the command

try {
       if($this->auth->guest()) {
        /**
         * if user email register arbitrary User
         */
        if(!$request->filled('email'))
        {
            return back()->with('error', "Please submit an email address!");
        }

        $user = $this->registerUser($request->only(['first_name', 'last_name', 'email']));
        $this->sentinel->bypassCheckpoints(function($sentinel)
                        {
                            return true;
                        },['activations']);
        $this->auth->loginUsingId($user->getUserId());
      }
    } catch (\Cartalyst\Sentinel\Checkpoints\NotActivatedException $e) {
        session()->flash('warning', 'You have not activated your account. Please ');
      }

I still keep getting

Cartalyst \ Sentinel \ Checkpoints \ NotActivatedException
Your account has not been activated yet.

at other areas of the application. Now I do not mind the checkpoint but I atleast need to be able to catch the error and return a more friendlier warning on failure. Is there a way to do a global activation check based on the route or should i disable

'checkpoints' => [

        'throttle',
        // 'activation',

    ],

the activation checkpoint and try it manually. Either way I want to be able to check for activation but want to be able to catch the exceptions and still proceed with the code.

Solved by remove $self parameter and calling $user->profile() and not $user->profile