I need to customize few logic in the Phabricator tool. But I couldn't able to find where the logic, MySql queries and view files are located.
Does it have any MVC folder structure like codeigniter or any other specific pattern?
Can anyone please help me to understand this or please share any links to understand the coding structure and customize the logic.
Thanks in advance!
Phabricator documentation would the first point of start:
Example of Extension for Phabricator
Adding a new class
Most of them add new features to Phabricator functionality. The problem with changes is that you should maintain them, (use patch) to add them after every update.
Related
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"
Is there an easy way to incorporate changes to the main Laravel app, when there are framework updates, other than manually incorporating the changes described in the documentation (http://laravel.com/docs/5.1/upgrade)?
I'm thinking some kind of composer command that patches the main app and not only the vendor dir. Does such a thing exist?
Thanks in advance.
Apparently, Shift is exactly what you're looking for, although it's still in its alpha. You can contact its creator if you want to help him test the tool.
Reference: http://jason.pureconcepts.net/2015/11/laravel-automated-upgrade-tool-shift/
I just created a Yii-App (from https://github.com/Crisu83/yii-app) with composer and it suggests Yii-Auth to manage Authentication, so I registered Yii-Auth and installed it, and I don't know how to integrate Yii-Auth in the Yii-App project (I wouldn't know how to integrate other extensions either), could someone guide me through the integration process, please?
Thanks a lot!
The strings 'auth.components.AuthBehavior' and 'auth.components.AuthWebUser' are path aliases. See the definitive guide for more information on Yii path aliases.
The 'auth' will be defined somewhere in this module. (I do not know where because I am not familiar with this particular module.) It would be cleanest to find the definition of the 'auth' alias and change that to match your directory structure.
If you do not want to do that, you could replace the string with something like '???.vendor.auth.components.AuthBehavior'. I do not know the exact alias, because I do not know your directory structure.
Hope this helps. If not, show you directory structure.
Actually i am using sugarCRM open source for my own purpose. That was developed by PHP in MVC format. I want to do some changes in existing file. I cannot modify the any code at any cost, because i cannot understand the flow of the code. In sugar CRM having many folders and files so that was difficult to understand the code flowing.
Exactly what i am expecting is, atleast one module is how is flowing with the code and what is the exact file path...
Very Big thanks in Advance...
Have you checked out the Sugar Developers website? There are tutorials and other information about developing for Sugar.
Sugar Developers website is a great source but you could also use documentation where you could find for each SugarCRM Flavor a Developer Guide, and since 6.3 an API Documentation and a Schema Documentation.
Sugar modules are in /modules but you don't want to edit these as it is not upgrade safe. To make a modification you either use or create the relevant folder in /custom/modules
Most often you will be doing metadata updates (most functionality is metadata driven) in files like editviewdefs.php, listviewdefs.php in the custom folder.
Logic hooks can go in here too, search for logic_hooks.php in the sugar documentation as it shows the way to create the metadata array to reference new PHP functions on hooks like "before_save", "after_save" and others.
Sometimes you can start the customisations in Studio (admin menu) and get examples generated in the custom folder for you.
I'm working on releasing a PHP framework I have been using for a few years
on github. Been trying to read up on the most correct way a project
should be structured, what extra files such as readme's etc should be
added. Been coming up with blanks on google. Can anyone point me to a
project that's a good example or any good write ups.
Some PHP projects hosted on Git(hub) include:
CakePHP
Gallery3
Garden
PHPUnit
Kohana
I'd just make sure that no temporary files, etc. get in the repository by creating a .gitignore file, and add some readme's etc. to the root of the repository.
Any configuration files should also be ignored, and sample configuration files should be created in the repository.
I'd recommend writing the readme file in a format that Github supports, like Markdown. It'll make your repository front page look better.
You might want to follow some kind of class naming guideline to make things like autoloading easier to implement. For example, the class MyFramework_Controller should be located at directory /lib/MyFramework/Controller.php.
You should just create some kind of basic layout for now - it'll be easier to give suggestions when we can see what you have right now.