Admin Architect
Missing Laravel Administration Framework. It's like ActiveAdmin for Laravel.
Docs
License
The Admin Architect is open-sourced software licensed under the MIT license.
Missing Laravel Administration Framework. It's like ActiveAdmin for Laravel.
The Admin Architect is open-sourced software licensed under the MIT license.
Running composer require adminarchitect/core
with Laravel 5.6 is throwing the error:
Your requirements could not be resolved to an installable set of packages.
Seems to be compatibility issues with the codesleeve package?
This is an awesome project! But I have one problem - I can't find in any documentation or here anywhere how to display a field from related table. My events table has a client_id field, that points to clients table. In grid right now the data is displayed at 1. How do I make it dispay's client's name (title field)? I know I need to use update()
in columns()
method, but how? I see that works just fine in your demo app ... but cannot figure what is the correct way of doing it except manually doing search on Client model... is this the only/right way?
2 more questions:
When using a datetime input type the Terranet\Administrator\Form\Type\Datetime
is correctly selected.
Expected behaviour: this element has a datetime selector (eg bootstrap-datetimepicker) Actual behaviour: this element has a date selector.
If interested I can make a PR against adminarchitect/core
and adminarchitect/mix
to include a datetimepicker element. But wanted to check if this would be appreciated first.
Reproduce by:
public function form()
{
return $this
->scaffoldForm()
->update('party_at', function($e){ return $e->setInput('datetime'); });
}
public function filters() { return $this->scaffoldFilters()->update('phone', ...
throws an error "Element [phone] does not exist."
even if it is present. Another issue for the update is that the control doesn't have a setQuery
method, even if in the docs there is an example for filtering relationships that way.
Hello,
Are there any plans for supporting spatie/laravel-medialibrary v7. It seems as of now only v6 is supported.
Anyone familiar with a monkeypatch that can help me to get v7 to work?
Dear,
This package seems great to me and perfectly fit my needs. Simple, Clean and works well. My only concerns is the Stapler package used for the Files. Since stapler is not maintained anymore and is made for L5.4. I cannot even install it right now where I'm looking into.
Using version ^1.0 for codesleeve/laravel-stapler
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- codesleeve/stapler v1.0.0-Beta4 requires illuminate/foundation ~4 -> satisfiable by laravel/framework[4.0.x-dev, 4.1.x-dev, 4.2.x-dev], illuminate/foundation[4.0.x-dev].
- codesleeve/stapler v1.0.0-Beta3 requires illuminate/foundation 4.0.x -> satisfiable by laravel/framework[4.0.x-dev], illuminate/foundation[4.0.x-dev].
- codesleeve/stapler v1.0.0-Beta2 requires illuminate/foundation 4.0.x -> satisfiable by laravel/framework[4.0.x-dev], illuminate/foundation[4.0.x-dev].
- codesleeve/stapler v1.0.0-Beta1 requires illuminate/foundation 4.0.x -> satisfiable by laravel/framework[4.0.x-dev], illuminate/foundation[4.0.x-dev].
- illuminate/foundation 4.0.x-dev requires illuminate/exception dev-master -> satisfiable by illuminate/exception[dev-master].
- codesleeve/laravel-stapler v1.0.0 requires laravel/framework ~4 -> satisfiable by laravel/framework[4.0.x-dev, 4.1.x-dev, 4.2.x-dev].
- codesleeve/laravel-stapler v1.0.01 requires laravel/framework ~4 -> satisfiable by laravel/framework[4.0.x-dev, 4.1.x-dev, 4.2.x-dev].
- illuminate/exception dev-master requires filp/whoops 1.1.* -> satisfiable by filp/whoops[1.1.0, 1.1.0-rc, 1.1.1, 1.1.10, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9] but these conflict with your requirements or minimum-stability.
- laravel/framework 4.2.x-dev requires filp/whoops 1.1.* -> satisfiable by filp/whoops[1.1.0, 1.1.0-rc, 1.1.1, 1.1.10, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9] but these conflict with your requirements or minimum-stability.
- laravel/framework 4.1.x-dev requires filp/whoops 1.0.10 -> satisfiable by filp/whoops[1.0.10] but these conflict with your requirements or minimum-stability.
- laravel/framework 4.0.x-dev requires filp/whoops 1.0.7 -> satisfiable by filp/whoops[1.0.7] but these conflict with your requirements or minimum-stability.
- codesleeve/laravel-stapler v1.0.07 requires codesleeve/stapler 1.2.* -> satisfiable by codesleeve/stapler[v1.2.0].
- codesleeve/laravel-stapler v1.0.08 requires codesleeve/stapler 1.2.* -> satisfiable by codesleeve/stapler[v1.2.0].
- codesleeve/laravel-stapler v1.0.09 requires codesleeve/stapler 1.2.* -> satisfiable by codesleeve/stapler[v1.2.0].
- Conclusion: don't install codesleeve/stapler v1.2.0
- Conclusion: don't install codesleeve/laravel-stapler v1.0.06
- Conclusion: don't install codesleeve/laravel-stapler v1.0.05
- Conclusion: don't install codesleeve/laravel-stapler v1.0.04
- Conclusion: don't install codesleeve/laravel-stapler v1.0.03
- codesleeve/stapler v1.0.0 requires doctrine/inflector v1.0 -> satisfiable by doctrine/inflector[v1.0].
- codesleeve/stapler v1.0.01 requires doctrine/inflector v1.0 -> satisfiable by doctrine/inflector[v1.0].
- codesleeve/stapler v1.0.02 requires doctrine/inflector v1.0 -> satisfiable by doctrine/inflector[v1.0].
- Conclusion: don't install doctrine/inflector v1.0
- Conclusion: don't install imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- Conclusion: don't install codesleeve/laravel-stapler v1.0.05|remove imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- Conclusion: don't install codesleeve/laravel-stapler v1.0.05|don't install imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- Conclusion: don't install codesleeve/laravel-stapler v1.0.04|remove imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- Conclusion: don't install codesleeve/laravel-stapler v1.0.04|don't install imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- Conclusion: don't install codesleeve/laravel-stapler v1.0.03|remove imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- Conclusion: don't install codesleeve/laravel-stapler v1.0.03|don't install imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- Installation request for codesleeve/laravel-stapler ^1.0 -> satisfiable by codesleeve/laravel-stapler[v1.0.0, v1.0.01, v1.0.02, v1.0.03, v1.0.04, v1.0.05, v1.0.06, v1.0.07, v1.0.08, v1.0.09].
- Conclusion: remove imagine/imagine v0.7.1|install codesleeve/stapler v1.0.0|install codesleeve/stapler v1.0.01|install codesleeve/stapler v1.0.02
- codesleeve/laravel-stapler v1.0.02 requires codesleeve/stapler 1.0.* -> satisfiable by codesleeve/stapler[v1.0.0, v1.0.0-Beta1, v1.0.0-Beta2, v1.0.0-Beta3, v1.0.0-Beta4, v1.0.01, v1.0.02, v1.0.03, v1.0.04, v1.0.05, v1.0.06].
- codesleeve/stapler v1.0.06 requires imagine/imagine ~0.6.2 -> satisfiable by imagine/imagine[0.6.2, v0.6.3].
- codesleeve/stapler v1.0.03 requires imagine/imagine ~0.5.0 -> satisfiable by imagine/imagine[v0.5.0].
- codesleeve/stapler v1.0.04 requires imagine/imagine ~0.5.0 -> satisfiable by imagine/imagine[v0.5.0].
- codesleeve/stapler v1.0.05 requires imagine/imagine ~0.5.0 -> satisfiable by imagine/imagine[v0.5.0].
- Can only install one of: imagine/imagine[0.6.2, v0.7.1].
- Can only install one of: imagine/imagine[v0.5.0, v0.7.1].
- Can only install one of: imagine/imagine[v0.6.3, v0.7.1].
- Installation request for imagine/imagine (locked at v0.7.1) -> satisfiable by imagine/imagine[v0.7.1].
This error after install via composer
Illuminate\Foundation\ComposerScripts::postAutoloadDump
@php artisan package:discover --ansi
In Facade.php line 237:
Call to undefined method DaveJamesMiller\Breadcrumbs\Manager::for()
if we try to install new version DaveJamesMiller\Breadcrumbs\Manager we get this conflict
composer require davejamesmiller/laravel-breadcrumbs:5.x
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- adminarchitect/core v1.6.4 requires davejamesmiller/laravel-breadcrumbs 3.0.* -> satisfiable by davejamesmiller/laravel-breadcrumbs[3.0.0, 3.0.1, 3.0.2, 3.0.3] bu
t these conflict with your requirements or minimum-stability.
- adminarchitect/core v1.6.4 requires davejamesmiller/laravel-breadcrumbs 3.0.* -> satisfiable by davejamesmiller/laravel-breadcrumbs[3.0.0, 3.0.1, 3.0.2, 3.0.3] bu
t these conflict with your requirements or minimum-stability.
- adminarchitect/core v1.6.4 requires davejamesmiller/laravel-breadcrumbs 3.0.* -> satisfiable by davejamesmiller/laravel-breadcrumbs[3.0.0, 3.0.1, 3.0.2, 3.0.3] bu
t these conflict with your requirements or minimum-stability.
- Installation request for adminarchitect/core (locked at v1.6.4, required as ^1.6) -> satisfiable by adminarchitect/core[v1.6.4].
Installation failed, reverting ./composer.json to its original content.
Could you please add try..catch block in delete action of ScaffoldController to handle deleting errors? It could be useful when you want to restrict deleting when model has related models. For instance restrict category deleting if category has some products included. Seems to be a common case.
Hi. Thank you for your work. Admin architect is a great tool.
Just faced an issue after deleting record from view page in ScaffoldController there are lines:
if (URL::previous() === route('scaffold.view', ['module' => $module, 'id' => $id])) {
return back()->with('messages', [$message]);
}
so when deleting from view page, user gets redirect back to view page. as i understand, it works correct when record is soft deleted. but if model doesn't support soft delete - user gets 404 error
am i missing something?
Hello. I'm using this video as reference to learn AdminArchitect:
https://www.youtube.com/watch?v=sLqjm90RZxI
The model and migration were created correctly. But I can't get the status field to work correctly. It shows as a text box.
The article module has the code overriding the form function:
public function form(){
return array_merge(
$this->scaffoldForm(), ['status' => \admin\form\select('Status',['draft'=>'Draft', 'published'=>'Published'])]
);
}
Laravel returns me this error:
array_merge(): Argument #1 is not an array (View: /var/www/resources/views/vendor/administrator/edit/index.blade.php)
the scaffoldForm() method returns me a mutable class, not an array. Could that be the cause?
A dd from the scaffoldform():
Mutable {#1128 ▼
#items: array:3 [▼
0 => FormElement {#1109 ▼
#input: Text {#1098 ▶}
#description: null
#template: null
#relations: null
#standalone: false
#keepOriginalID: false
#id: "title"
#title: "Title"
#module: null
#translator: null
}
1 => FormElement {#1116 ▼
#input: Textarea {#1114 ▶}
#description: null
#template: null
#relations: null
#standalone: false
#keepOriginalID: false
#id: "body"
#title: "Body"
#module: null
#translator: null
}
2 => FormElement {#1123 ▼
#input: Text {#1121 ▶}
#description: null
#template: null
#relations: null
#standalone: false
#keepOriginalID: false
#id: "status"
#title: "Status"
#module: null
#translator: null
}
]
}
a dd from the custom field array:
array:1 [▼
"status" => array:3 [▼
"type" => "select"
"label" => "Status"
"options" => array:2 [▼
"draft" => "Draft"
"published" => "Published"
]
]
]
Could you help me with that? Thanks in advance :)
Hello,
I set a field from a form to be for image uploads like this :
` public function form() { return $this ->scaffoldForm()
# Update existing column
->update('image', function ($element) {
# Set a different input type
$element->setInput(
new Image('image')
);
return $element;
});
}`
But my images are saved in a temporary folder with extension .tmp. How can I set my folder?
Thank you!
Hi! I'm trying to install this project to start testing it, but I'm having difficulties, here is my development stack and the package installation error log.
PHP: 8.1.2 Composer: 2.2.5 2022-01-21 17:25:52 Laravel: 8.83.0
Installation error log
$ composer require adminarchitect/core
Using version ^1.6 for adminarchitect/core
./composer.json has been updated
Running composer update adminarchitect/core
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- adminarchitect/core[v1.6, ..., 1.6.x-dev] require laravelcollective/html 5.*|dev-master -> satisfiable by laravelcollective/html[dev-master, v5.0.0, ..., 5.8.x-dev].
- laravelcollective/html dev-master requires illuminate/http ^6.0|^7.0 -> found illuminate/http[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.0.0, ..., 5.0.x-dev] require illuminate/http ~5.0 -> found illuminate/http[v5.0.0, ..., 5.8.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html v5.0.5 requires illuminate/http ~5.1 -> found illuminate/http[v5.1.1, ..., 5.8.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.1.0, ..., 5.1.x-dev] require illuminate/http 5.1.* -> found illuminate/http[v5.1.1, ..., 5.1.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.2, ..., 5.2.x-dev] require illuminate/http 5.2.* -> found illuminate/http[v5.2.0, ..., 5.2.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.3.0, ..., 5.3.x-dev] require illuminate/http 5.3.* -> found illuminate/http[v5.3.0, ..., 5.3.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.4, ..., 5.4.x-dev] require illuminate/http 5.4.* -> found illuminate/http[v5.4.0, ..., 5.4.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.5, ..., 5.5.x-dev] require illuminate/http 5.5.* -> found illuminate/http[v5.5.0, ..., 5.5.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.5.2, ..., 5.6.x-dev] require illuminate/http 5.6.* -> found illuminate/http[v5.6.0, ..., 5.6.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.7, ..., 5.7.x-dev] require illuminate/http 5.7.* -> found illuminate/http[v5.7.0, ..., 5.7.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.8.0, ..., 5.8.x-dev] require illuminate/http 5.8.* -> found illuminate/http[v5.8.0, ..., 5.8.x-dev] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires adminarchitect/core ^1.6 -> satisfiable by adminarchitect/core[v1.6, ..., 1.6.x-dev].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require adminarchitect/core:*" to figure out if any version is installable, or "composer require adminarchitect/core:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
Hi there,
I couldn't find a SECURITY.md
in your repository and am not sure how to best contact you privately to disclose a security issue.
Can you add a SECURITY.md
file with an e-mail to your repository, so that our system can send you the vulnerability details? GitHub suggests that a security policy is the best way to make sure security issues are responsibly disclosed.
Once you've done that, you should receive an e-mail within the next hour with more info.
Thanks! (cc @huntr-helper)
Fix redirect issue for deleted resource
Source code(tar.gz)Fixes scopes pagination
Source code(tar.gz)Use null coalesce operator in favour of deprecated or
Source code(tar.gz)Ready for laravel 5.6. Replace Laravel Stapler -> Paperclip
Source code(tar.gz)add back compatibility for laravel 5.3|5.4
Source code(tar.gz)Added translations module - allows managing Laravel translation files.
Source code(tar.gz)Use contract instead of class
Source code(tar.gz)LaraAdmin 1.0 LaraAdmin is a Open source CRM for quick-start Admin based applications with features like Advanced CRUD Generation, Schema Manager and
Admin One — Free Laravel Vue Bulma Dashboard Admin One is simple, beautiful and free Laravel admin dashboard (built with Vue.js, Bulma & Buefy). Built
Note: This package is only used by Backpack v3. Starting with Backpack v4, everything this package does is included in Backpack/CRUD - one package to
⚙️ LittleLink Admin LittleLink Admin is an admin panel for littlelink that provides you a website similar linktree. ?? Features creating a link page w
LittleLink Admin is an admin panel for littlelink that provides you a website similar linktree.
Admin Columns allows you to manage and organize columns in the posts, users, comments, and media lists tables in the WordPress admin panel. Transform the WordPress admin screens into beautiful, clear overviews.
Until 2018, Backpack v3 used this Base package to offer admin authentication and a blank admin panel using AdminLTE. Backpack v4 no longer uses this package, they're now built-in - use Backpack/CRUD instead.
Laravel Admin Panel (Current: Laravel 7.*) Introduction Laravel Admin Panel provides you with a massive head start on any size web application. It com
Laravel Enso Hit the ground running when building your new Laravel SPA project with boilerplate and extra functionality out of the box! click on the p
Laravel Enso Hit the ground running when building your new Laravel SPA project with boilerplate and extra functionality out of the box! click on the p
Dcat Admin是一个基于laravel-admin二次开发而成的后台系统构建工具,只需很少的代码即可快速构建出一个功能完善的高颜值后台系统。内置丰富的后台常用组件,开箱即用,让开发者告别冗杂的HTML代码,对后端开发者非常友好。 官方网站 中文文档 English documentions D
Voyager - The Missing Laravel Admin Made with ❤️ by The Control Group Website & Documentation: https://voyager.devdojo.com/ Video Tutorial Here: https
For the full documentation, visit orchid.software. Introduction Orchid is a free Laravel package that abstracts standard business logic and allows cod
Lemur Engine The Lemur Engine is a PHP/MySQL/AIML Chatbot. Written using the Laravel Framework. Demo You can demo the bot at the website: https://lemu
Adds a zero configuration Admin Panel to your Laravel Application Installation You can install the package via composer: composer require max-hutschen
Laravel Admin Panel An admin panel for managing users, roles, permissions & crud. Requirements Laravel >=5.5 PHP >= 7.0 Features User, Role & Permiss
Base Laravel Admin Just a basic Laravel 4.1 install with a admin site/dashboard using Bootstrap 3.0.3 For those (like me) who set up lots of small sys
EasyPanel EasyPanel is a beautiful, customizable and flexible admin panel based on Livewire for Laravel. Features : Easy to install Multi Language RTL
laravel 8-Adminlte@3.0.1 Laravel 8 with Admin-lte@3.0.1 template The following tools are required in order to start the installation. PHP >=8.0 compos