Posts made by qualitycoder

Not sure why it didn't work for you. Worked straight away for me first time.

Double check your translation setting, and maybe try again?

I believe as long as you have a layouts/account.blade.php in your views folder and it contains @yield('content'), your login page will work. It doesn't have to be copied from the Flatly theme.

As far as the extra fields in the Users table, just make sure you have a proper migrations file, and you should be good to go.

These answers are to the best of my knowledge.

I can't say anything about the NoSql backend, but I am currently working on a multi tenancy version of AsgardCms, and will be handing it off to them once I am done.

When I use the Flatly theme, after typing in /backend, and being redirected to /en/auth/login, I log in, and it redirects me to /backend.

With a custom theme, after typing in /backend, and being redirected to /en/auth/login, I log in, and it redirects me to /en. I have to go back to the url bar and type in /backend again.

This is normal?

no, after copying the account.blade.php page over, it redirects to /en/auth/login and shows the login form.

Once I log in, it redirects me to a blank custom theme page, not the backend. The url is /en, not /backend.

After that, I can type in /backend again, and it will take me there, but it doesn't take me there on its own.

I copied the layouts/account.blade.php file to the custom theme layouts directory, and now the form shows up, but after logging in, it redirects me to a blank custom theme page (the custom theme is shown with no content). It doesn't show the back end with the adminlte theme.

I kind of figured it out.

For some reason, the /en/auth/login is trying to use the custom front-end theme, and not the adminLT theme.

I copied the notifications.blade.php and the entire errors theme directory over to my custom theme directory, and it showed a page. Didn't have the login form, but at least I'm starting to show a little progress.

It didn't do this on my local box, but once it transferred to the server, it wants the auth/login to be part of the custom theme. Weird.

• I built it locally
• I exported the database to a sql file
• I created the new database on the server
• I ran the sql file on the server
• I ftp'd the files up to their location
• I checked the front end, and it worked
• I checked the back end, and it does not work
• I cleared out the storage/framework/cache, storage/framework/sessions, and storage/framework/views directories, hoping that would help.
• I came here looking for help

I looked in the laravel.log file (/storage/logs/laravel.log).
It's saying it can't find the partials.notifications view, but I see it right there in the AdminLTE Theme folder.

[2017-06-16 07:18:02] local.ERROR: InvalidArgumentException: View [partials.notifications] not found. in /[removed]/www/vendor/laravel/framework/src/Illuminate/View/FileViewFinder.php:137

• [site name]
  • Themes
    • Adminlte
      • views
        • partials
          • notifications.blade.php

I actually get a whole slew of error messages. The top of the file is the missing partials.notifications view file. The last in the file is

[2017-06-16 07:18:02] local.ERROR: Symfony\Component\Debug\Exception\FatalErrorException: Uncaught InvalidArgumentException: View [errors.500] not found. in /[removed]/www/vendor/laravel/framework/src/Illuminate/View/FileViewFinder.php:137

I developed a site locally on my computer.

When it was done, I

• exported the database to a sql file,
• created a new database on the web server
• imported the sql file
• copied all files (including .env, etc) to the web server

The Front end works no problem, but I can't seem to get to the backend. I get a 500 error when it redirects from /backend to /auth/login.

What have I missed?

Thanks in advance to anyone that can help.

Heh,

I just realized that I had been working in the version 1 instance, and according to your GitHub, that hasn't been updated in a year.

I guess I'll have to fork the 2.0 version, make my changes, and go from there.

Nevermind, I got it.

I'm converting AsgardCms to a Multi-Site CMS.

I was able to change the theme based on the URL, a SiteScope, a few changes to the insert and update calls, etc.
It now saves and pulls settings based on site_id.

Once I finish converting everything over, maybe I'll offer it up for others, if anyone is interested.

This way, you'll have a single-site version and a multi-site version.

Let me know if you are interested. It'll take me a bit to finish it, but I'm making headway.

I plan to have multiple domain names hit a single code base/single database installation.

I am creating a module for "Sites", so that I can database a few settings per domain.

I would like to be able to set the Theme for each site in the new module table, instead of an all-encompassing Theme set in the setting_settings table.

How can I override the default Theme call, so that it pulls from the new module db table instead of the settings table?

When I create a new module via asgard:module:scaffold, the new module appears in the SideBar, but shows up as

{{modulename}}::abcs.title.abcs

Example: When I created a Calendar module, it showed up as:
calendar::abcs.title.abcs

I have to either change the output to
calendar::events.title.events
or create a abcs.php file in the Resources/lang/en folder.

Is this happening with anyone else? Am I doing something wrong?

I am trying to create a module that has a many-to-many relationship between two models.

I have gone into the entities and added the relationship methods (belongsToMany).

I am trying to make the create and edit fields and am running into issues.

In the controller, I added a call to pull all the related records, and added it to the compact function.

In the view, I am looping through the related records and adding normalCheckbox fields, but am having trouble figuring out what I'm supposed to be using for the $name parameter. Since it is used as the check on the passed in object, it should be the ATTRIBUTE of the object, but since it has to be unique, it should be the VALUE of the attribute, so that it doesn't get confused with the other objects being created in the loop.

Is the normalCheckbox the right thing to use? Should I just hand code the checkboxes and not use the Form helper?