Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Just found out about this new project Symfony2 Admin Generator. It is for easy development of backends for symfony2 based applications.
I was wondering, how this tool is different from Sonata admin project? Is there any use case where this new admin generator would be preferred?
The two bundles are actively developed so those considerations can
change in the near future.
I've migrated my admin panels from symfony2admingenerator to SonataAdmin recently, partly due to some bug in symfony2admingenerator, and partly because I've found SonataAdmin clearer.
SA uses an OOP approach, while S2AG rely on a yml config to define the admin panels
S2AG need to generate a complete CRUD structure via command (controllers, views, and a yml config), while SA panels are only 1 DI Service Class
in S2AG the configuration options are more obscure, since they are based on a yml file and on autogenerated classes, and often an error doesn't yield a meaningful message/stacktrace
in S2AG is simplier to customize the rendering of a field.
in the S2AG web pages, some parameters (like the filter of a list) are stored in the Session, rather than in the query string. This lead to the difficulty to link directly to a filtered list (eg: The comments by an user)
SA seemed more stable, but the MongoDB part is less developed and has less features than the ORM part.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have just started out doing web development projects for clients and I have done two so far using NextJS, NuxtJS along with headless WordPress for the CMS. As I also have a full time job these projects take a fair amount of time and I end up working constantly.
I have recently come across Webflow and have messed around with it to see how it works. It seems like if I used Webflow and the CMS is provides I could get through projects much quicker than I would currently.
Do you think that for freelancing using a tool like Webflow is a better idea than what I am currently doing?
I currently use Webflow for client projects and I use Next.js at work. I would highly recommend using Webflow for the following reasons on most web dev client projects.
Speed of customization (You can create components in Webflow and copy and past them into new projects, which allows you to reuse standard parts in seconds)
CMS already integrated.
Ability to easily give clients access to edit their own content if they need
Easily edit SEO settings
Easily connect other tools like Zapier and Memberstack if you need
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Are there any benefits to using settings.json instead of just storing this information in mongodb?
I would have thought that if you store it in a collection, then you can secure it by not publishing the collection in the first place. But you could also then build an admin page where you could update these details in your app, and it would be available straight away with no code reload.
In the meteor Chef's article on building a SaaS using Meteor (https://themeteorchef.com/recipes/building-a-saas-with-meteor-stripe-part-1/), Ryan Glover espouses the use of settings.json to store your Stripe keys.
Later on he uses it again, but this time to hold the details about the stripe plans. Wouldn't it be better to store this in a collection on mongodb?
Commonly, the settings.json file is meant to be used for non changing data like API keys and config info.
Considering that this data doesn't need to be manipulated, it is better to just use a settings.json file rather than a collection. If your going to use a collection than you have to go through the extra steps of pub sub.
With settings.json you have an opportunity to use different configuration for different environments (DEV, PROD etc.). Of course you can keep config information in MongoDB but then you need to save also environment information and have to pub/sub based on this.
Why would you do this, while you already have a mechanism for app configuration? In addition, you can set METEOR_SETTINGS environment variable.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Is it possible to mix frameworks?
I want to develop a site using Symfony but have been advised to use Kohana (with Boonex Dolphin) as it is the best for plugging in social networking modules
It is possible to mix Symfony Standard Edition with any other framework. It is not recommended, but it is possible. The most common situations when you need to do this is when you migrate your old code to Symfony and when you want a blogging system to handle the blogging part of your website (like having your website on Symfony and your blog on WordPress).
To achieve that there are many ways. One is to setup in Symfony a route that will work with the legacy code. Another one is to build an adapter over your non-Symfony application (or your Symfony app).
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I'm .NET developer and have some questions about Symfony's IoC implementation.
Does Symfony is capable for .NET-style (i.e. Ninject, Castle Windsor, etc.) constructor injections. Namely, can I avoid the necessity of giving name to each service and bind service implementation to interface instead? Also can I do not define each controller as a service for make DI working? "Controller as a service" and manual configuration constructor's parameters in services.yml(xml) seems to me redundant after years of .NET development. Thanks.
P.S. Sorry for my english.
Namely, can I avoid the necessity of giving name to each service and bind service implementation to interface instead?
No, you can't. It one of the things I'm missing in the di component too.
Also can I do not define each controller as a service for make DI working?
The good point about symfony2 is that it removed most of the convention-based things. Doing the thing you suggested adds a mew convention to symfony. You could check the KnpRadBundle, to see how they implemented auto registering of other services, based on conventions and create your own bundle which does it for controllers.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last year.
Improve this question
I would like to give web designers autonomy to publish web pages but letting them to edit aspx files is a serious security risk as they don't have the required programming skills.
I was thinking about two approaches:
They are only able to edit html files and call services with ajax;
Let them to edit xslt files associated to services that return xml.
But both have a drawback: limited use of templates.
How would you deal with this situation?
If the developer is on his own domain then its safe to give him full access to JavaScript. However if he is sharing this domain then by giving him access to javascript you open the door to XSS. This allows the publisher to hijack other user accounts (usually by access document.cookie, but there are other same-origin policy abuses). One possilbity is to use Html Purifier, which prevents javascript all together.
There is a better alternative and that is a Google-Caja, which places restrictions on the javascript a developer can execute. This is important for apps written for social networking sites.
This is an issue that's already been addressed in most CMS systems. Have a look at joomla, drupal, SharePoint, etc etc.