From my experience:
About Joomla framework
I tried to build a simple RESTful API for integrated authentication based on Joomla framework. It's fairly complex, quite different than the current Joomla API. Also, current source code can't be copy-pasted, and libraries may return unexpected results (being executed in a different environment). I'm going to wait ...
com_api is definitely a good way to build REST services for your site if the extension itself is not based on FOF/RAD. However be careful with a few gotchas if you plan to create a separate Joomla instance only for the API
Domain specific stuff (Eg: If you are supporting user registration, then the welcome email would include a link to the API subdomain). ...
This should get you going - http://docs.joomla.org/J3.3%3aHow_To_Use_Content_Tags_in_Joomla!
Admittedly it was a little difficult to get going at first, and if you're supporting 2.5 on the same code base there are other challenges (I can link you to commits on a project when I'm not on mobile).
You can use JSON format in the controller directly by adding .json suffix and changing format in your URL to json. In this case the controller would be placed in /administrator/components/com_example/controllers/ajax.json.php. It's contents:
defined('_JEXEC') or die;
class ExampleControllerAjax ...
Currently, FOF is used for the postinstall messages and for the two factor authentication.
Unfortunately the developer of FOF retracted his offer and is no longer contributing FOF to Joomla core.
Thus using it as default is out of question and we in fact have to refactor the existing uses of it.
It is certainly fired, via F0FModel ($context = 'com_akeebasubs.subscriptions').
You can simply check it in PlgContentJoomla / onContentBeforeDelete (where the function is executed and returns when the context is not 'com_categories.category').
If your plugin is not being fired, check if it is enabled as System or Content plugin to receive the event.
This component is developed using Akeeba FOF, so you need to read the documentation to know how to complete the task.
Almost everything is configured using XML, this is to some extent of course.
Legacy MVC will be supported until EOL of Joomla 3 (at least). I would just go ahead and use that. You will find many tutorials for legacy MVC and you will probably get the most help for that here or in the forums. Also (almost) all core components are developed with legacy MVC so you have many examples at hand.
The new MVC is already usable but you will ...
Figured out the issue, when making a component you need to have at least 1 blank update sql file or it will fail. Not just the typical index.html file to make sure then installer does not skip the folder.
Typically the file would be something like sql/updates/mysql/VERSION.sql Replacing version with the actual needed version. I am confident this is a bug, ...
This question (problem) was successfully and quite quickly solved yesterday, working effectively together with @Mick on the solution. And this question is very well detailed, well described and it included the exact error message from Joomla, so it is a good example of a well-built question on SE.
The solution was relatively simple: we had to change the ...
First, you should learn how to make a Joomla component as @Nagarjun mentioned in his answer. Secondly, you must not add fields to #__users table because it will be overwritten by future Joomla updates.
If you want to add extra fields during user registration then you must use user profile plugin and add extra fields. It comes pre-installed with Joomla. Or ...
No, there is no simple way to this. At least, simple means a lot of things for everybody here. I will give you some good directions on this however.
First of all, J2Store has Simple products, variable products, configurable products, flexible products...etc. So how do you think it's simple? Then there is the content component which handles the articles, ...
I am getting this error quite often on a test system when trying to install a component which uses SQL updates and causes first time when installing an error (even not SQL related, such a missing file from the manifest file).
Here are some steps on how to fix this, by manually uninstalling the component, as from the Extension manager the installation may / ...
The following site seems to be an excellent resource for guidelines on how to build a RESTful JSON API:
For what it's worth, I am also launching an API product for Joomla 3.4.x called cAPI http://getcapi.org.
The primary differentiator here is that I staked my routing framework on Slim micro-framework. This allows me to incorporate an ...
My two cents:
For a customer I needed to access the contents of his joomla site from a smartphone app. The contents were placed in com_content so initially I used obRSS feeds. Then I found jBackend on JED and tried it. It is available here http://www.selfget.com/products/jbackend.html
The code seems very clean and it supports RESTful requests and JSON ...