Closed rande closed 8 years ago
Would like to have a template selection field on the show field. So the user would be able to get a real overview about the content he edits. When having one content in several frontend/Templats, the user would be able compare them all by just switching through them. Would be an almost Frontend editing by switching between show and edit view. just Rendering with some layout would be complicated. maybe it would be better to bind some Frontend urls and show them in an iframe instead? =
dynamic filters, like on Oro crm. http://www.orocrm.com/wp-content/uploads/2013/04/Grid-867x758.png You should check demo - you would be impressed.
In brief. By default, all filters are hidden, there are only button "Add filter". When you click on it - you get list of possible filters. After selecting possible filter you select valud for it. After that its showed on top of list.
We have 20+ filters in couple admin classes, page are very overloaded with filters block.
@zhil it is the idea, yes ;)
integrate https://github.com/sonata-project/SonataAdminBundle/pull/1971 in the 2.3/2.4 release (?)
It will be great that the method "$this->getSubject()" always returns the current admin, no matter if we are in an embedded admin (sonata_type_collection or sonata_type_admin) or not. The parent admin will be get by something like "$this->getParent()->getSubject()".
I really think #1971 should be integrated !
I wish for #1971 to be integrated :)
+1 for #1971
+1 for #1971 this is a necessity for efficient data input
+1 for filter on top option something like zoho: https://crm.zoho.com/ :
@acrozes can you please upload screenshots of zoho? just wondering - cant find screenshots on their site.
An up-to-date documentation should be interesting as well
Some screenshots of zoho. Filters are called view in zoho and you can select columns and criterias
Aimery
Hi !
I think the possibility to add items in the left menu would be nice. Instead of only having dashboard groups in the menu, we could add any route directly on the configuration. For instance : This configuration
sonata_admin:
menu:
example1:
label: Example number one
route: route_to_instance_number_one
context: ROLE_SUPER_ADMIN
example2:
label: Example number two
route: route_to_instance_number_two
Would render two more links in the sidebar menu only visible to the users with the appropriate role. This way, we could create custom page extending the sonata admin layout and have an easy access without editing the template. I don't know if it has already been proposed but in my opinion it could be a nice feature.
Thanks !
+1 for #1971
+1 for #1971
@na-ji :+1: nice feature!
@na-ji look at #2711
@amine26tz Quite nice what you did there, congrats ! :+1: Waiting for your PR to be merged.
+1 for #1971 ...preferably in 2.3 as well :)
+1 for #1382, when could this be accomplished?
@YuanluDWD - as far as I know in master version filters are on a top. I had to check it once and have to move back to 2.3 just because of changed location of filters. Did you try the newest version?
@krewetka Thanks for your answer. I will discuss it with our engineers.
@YuanluDWD - if it's not your personal project I guess the best option would be wait until stable 2.4 tag as current master version is as always work in progress.
Still you can use it to see how filters will look in new version.
@Storke the getSubject() should now return the correct value: https://github.com/sonata-project/SonataAdminBundle/commit/1a5ba565a75c6c43867c52210cb78ec29a2b6748
@Storke @rande With current dev-master
I can call getSubject()
. But I don't get an object returned when calling getSubject()->getParent()
neither does isChild()
return true though my admin class is a child.
class ContractAdmin extends Admin
{
protected $parentAssociationMapping = 'branch';
protected function configureFormFields(FormMapper $formMapper)
{
$formMapper
->add('supplierContacts', 'sonata_type_collection', array(
'by_reference' => false // !important
), array(
'edit' => 'inline',
'inline' => 'table'
));
}
}
class SupplierContactAdmin extends Admin
{
protected $parentAssociationMapping = 'contract';
protected function configureFormFields(FormMapper $formMapper)
if (!$this->isChild()) {
} else {
//$contract = $this->getParent()->getSubject();
$contract = $thisgetSubject()->getParent();
echo $contract->getNumber();
}
}
}
Is this an issue with nested admins with depth > 1?
Possible related to:
@rande What about Symfony version support?
SonataAdmin 2.4 stable is not out yet and symfony 2.7 LTS will be out shortly.
I think it's not unreasonable to drop symfony 2.3+ support and require 2.7+ version.
This will permit to fix get free of a lot deprecated calls.
Regards.
:+1:
Forget my idea about 2.3, this version is still supported until may 2017.
Can be closed as 3.0 is finally out.
Please open separated issues instead.
Validated elements:
Please comment to add your ideas.