I have been trying to understand how this concept works. Adding or removing code modules from laravel project. I have seen this feature in many places such as quickadminpanel.com, October CMS etc. These sites are used to create an admin panel quicker, there is an interesting feature that i found in quickadminpanel that is installing module that i need. Basically i want to achieve this but i don't know how to do !! May be someone can help as this feature and concept actually exists.
The author himself replied in a mail. Now the concept is much clear to me. He simply replied this, "It's similar to how Laravel works with stubs - copy-pasting files as templates, replacing the variables in content: youtube.com/watch?v=eWarTZuates&t=1s"
Related
I am looking to implement Angular2 inside my current Laravel project. I've read about many setups including AngularClass's version with Webpack, but I feel like it's all over-complicated.
What I wish to make:
A simple single page app inside my Laravel app.
It needs to have something like Grunt/Gulp or even Webpack to compile upon changes.
Does not need NodeJs to run in production, no lite-server, just like AngularJS it can be injected and that's it.
I need to understand the implementation files to achieve this, so no starterpack or angular-cli, unless if you can supply good arguments.
Looking for a "how to"-like example on creating the above.
Thanks in advance.
EDIT: More information
As ANKH pointed out, i needed a more detailed and coursed question. So here we go:
- Looking for a example implementation of a Angular2 based SPA inside an existing PHP application (Laravel).
- I've tried many different tutorials, going from the heroes tour, to Sitepoint and AngularCLI based tutorials, but they all assume a SPA on it's own. Ergo, they are compiled and served through NodeJS, which I don't need.
Turns out that I've actually been looking at this entirely wrong. I've gone with using Angular-cli and found that I could generate the output files and include these inside my Laravel project. No need to integrate them further.
in our team we started to migrate an very old PHP-newbie project to cakePHP and I'd like you to ask about how to structure some parts of it:
We have:
The cakePHP coreSources seperated in a vendors-directory
The application (app)
So now the question is how to structure addional parts of the application which are seperated due to permissions. But they are related to the application and in the old version much sourcecode is duplicated which we want to avoid.
admin tools panel
payment panel
support panel (lets say kind of help desk)
I'd like to keep them in seperated GIT repositories (as they are written by us and not 3rd party/vendors) and I dont want one huge repo which keeps the application and all of its addional panels.
So the question is: How to build this in cakePHP to avoid duplicate sourcecode? Example: A message written in the app should be visible in the suport panel when its reported as spam or bad words. (Do you understand what I mean?)
Shall we use plugins for the several panels or shall we build completly own cake-apps which will lead again to duplicate sourcecode? Are there other ways to deal with this problem?
Greetz
P.S. Sorry for my bad english.
If I understood you right you want to have modules that can be shared between applications. Plugins are the right choice then. You can manage them in git repos but I would use composer to install them in your apps.
Just putting something in a plugin won't make everything 100% reuseable and extendible make sure you write your code in a way that it can be extended using OOP principles and design patterns on app level if needed.
I'm working on a Restaurant website project and my client wants a Blog section and a complex Reservation System with it.
I use Wordpress to work with blogs and I prefer to use Code Igniter for systems but I don't know if these two can work good together. I have been reading some articles regarding the integration of CI to WP and a lot of it points out that conflicts are inevitable when doing so.
Are there any solutions you can offer me? One that is easy to integrate, no conflicts and helps me keep my code DRY.
As you pointed out, integration is not readily available. If you truly wanted to integrate them, it would be a long road (and not likely worth it). One think you could do is install them separately and just link between the two when necessary (not ideal, but doable). For instance you could install CodeIgniter at example.com/reservations/, and then install your blog at example.com/blog/
You could also utilize subdomains if you wanted. I honestly would go this route if I was faced with the same situation...I definitely would not waste the time in trying to integrate the two if there isn't a lot need (ie, blog posts needing to access information in the reservation system, etc...).
I am currently working on a project documentation site for an OSS PHP project. Presently all of the docs are written in Markdown and stored as separate files.
I would really like to keep the core documentation as static files within the project so that they can be downloaded and used as well as read on my website. But on the website, I'd like to render those pages from within a CMS.
In addition to presenting the code docs, I also want to provide a forum for discussion and a blog.
Wordpress is what I have experience with, but is there a better system for what I am trying to accomplish specifically?
For Blog and CMS I would suggest stick with Wordpress since you already have experience on it. And as far as Forum is concerned I would suggest SimplePress forum. I have been using it on my Wordpress installation and found it really good. You can see live forum on the link above to see how it looks in real world.
Also Wordpress has several nice plugins like Download Manager that will give you ability to manage your downloads/files.
Can't confirm if wp is the best, but it's certainly good enough.
To include your docs, you'll have to write a plugin, not likely that you will find one existing that does exactly what you want.
For forum, you should find a plugin. Google for posts similar to this to choose a best match.
Firstly Wordpress isn't a framework.
I believe CakePHP has the functionality to load hardcoded pages when they're placed in the webroot folder of the app. I'm unsure as to how they're loaded in regards to routing/templating however.
I'd have thought this would be a native feature (seeing as joomla allows you to connect contacts with user accounts) but we can't find any way to do this!
Does anyone know of any extensions/modules that would allow this?
I'm not so hot on PHP so i'd really love to not have to code this by hand!
This is an old thread, but since it is still opened maybe you haven't found a solution yet. I faced the same problem myself and I think having the ability to manage contacts from the frontend is an essential feature for Joomla! to become more usable as a simple webapp creation tool.
Anyway, there are a couple of extensions that might help you out. However, both are commercial and don't support Joomla! 1.6. Here they are:
Front-edit address book: simple
interface. Note, however, that there
might be a security issue with
it. Google "front-edit address book exploits" and you shall find it (sorry, stackoverflow lets me post a max of 2 links per thread since I'm a new user). I emailed the developer and he assured me that the problem was already fixed, though.
Grumpy contacts: on the demo site (there's a link at the page I pointed you to), it looked a little messy to my taste. In the Joomla! Extensions Directory, however, it has good reviews.
I never used any of those since all my projects are already migrated to Joomla! 1.6.
If you found another alternative in the meantime or even developed something yourself, please let me know.
Do you try in the user menu?
Another option would be install Community Builder.
Good luck!
Contacts in Joomla are handled by the builtin com_contacts compoment which provides basic functionality for adding contacts and some basic info from the back-end.
QContacts is a wonderful extension which gives you some more control over the data you can provide, but still no front-end support.
Unfortunately I am tackling this issue as well and it turns out there are no real out-of-the-box options for supporting front-end editing of contact details.