Joomla 2.5 Private Messaging - joomla

I am using joomla 2.5.7. When i am trying to select user in private message component, it shows only admin users. Registered users are not available. I want to use private messaging for registered users. Suggest me what i am doing wrong?

If you're referring to the Private Messaging component that comes standard with Joomla, then this is only available to admins, as it's an admin component and registered users won't be able to enter the backend to check their messages.
If you are looking for a PM component, then I would highly recommend UddeIM which is free and also integrates with lots of other 3rd party extensions such as Kunena and Community Builder.
Just on a side note, you should update your Joomla version to 2.5.14
Hope this helps

Related

Is it possible to design a setup step to be triggered when installing a Microsoft Teams App?

I'm designing the architecture for a Microsoft Teams app.
This app is an integration to a multitenancy platform that the customer can set up their own URL to access the system, i.e: https://app.customer.com/
I was wondering if there is a standard way to have a step on the app installation to set up the instance URL.
I understand I could design an app generator that would reside inside each customer instance and then deliver the manifest.zip to the customer to install it, but I feel we would lose all marketing and partnership opportunities that having it on the store would provide.
I couldn't find a standard way so I designed a proposed solution and wanted to validate it with the community.
I came with a list of issues and workarounds to work with a single app for the multiple instances based on what we've seen so far on Microsoft Teams documentation.
Issue 1: Accessible domains should be explicitly set on the manifest.json
Workaround: have a middleware in a fixed URL that handles all requests made by the app and route to the customer site
Issue 2: There is no standard step on an app installation to set up the instance URL
Workaround: Design a static tab that would handle the configuration, so in that tab, the admin would need to set up any
configuration like instance URL
Issue 3: After installation, the feature will be available for the users even before admin did the setup to define the customer instance URL to be used.
Workaround: Make all designed interactions (i.e.: Tabs configuration page, bot response, actions, cards, etc... ) have a
response to the user saying there are pending configurations in case
the admin did not set the URL yet

Ruby integration for Joomla using com_api

I am creating an application which uses REST API to access web-services of WordPress and Joomla.
I got success to do this with WordPress but I am unable to do this with Joomla-3.
I want to make a REST API call using Ruby Net::Http to access Joomla powered site. I want to access content of Joomla-3 enabled site using REST API. I found com_api but I don't know how to use it.
Please can anyone help me how to connect Ruby on Rails and Joomla 3 with each other.
I have developed a commercial Joomla package which combines an admin component with an extensible plugin architecture to expand service capabilities. You may refer to may other responses for more information:
REST API for Joomla 3.0
How to Install and use joomla rest api step by step
A key feature of this extension is that it is built upon the Slim PHP micro-framework in order to take advantage of a robust, standards-compliant service route architecture. This allows Joomla to take care of login authentication and group permissions, while Slim exposes routes for GET, POST, PUT, DELETE, etc. Another advantage is that Joomla allows for selective activation and permissioning for different web service plugins.
Installation, configuration and API docs can be found here:
http://learn.getcapi.org
For a general product overview, please visit http://getcapi.org.

what is soap in magento? what is use of it?what is use of soap/xml-RPC-user?

what is use of soap/xml-RPC-user and soap/xml-RPC-roles?
in system menu there is one menu item web services contains 4-5 options like soap/xml-RPC-user and soap/xml-RPC-roles.
what is use of it? how to use that?
The original Magento API was implemented both in SOAP and XML-RPC. SOAP and XML-RPC are well known technologies for creating functions, classes, and methods client-programmers may call over HTTP. Explaining them in greater detail is beyond the scope of a Stack Overflow question.
The User and Roles menus are the for the authentication portion of the Magento API. To authenticate the API, you call a login method, passing in a username and password. You setup this user name and password in the Users menu you mentioned.
Each user you setup has access to a "role". Roles determine which API functions a user may call. You setup the roles in the Roles menu you mentioned. You assign a role to a User when you're editing it in the User section you mentioned.
In newer versions of Magento these sections are explicitly labeled with SOAP/XML-RPC to differentiate them from the newer REST APIs.
At first you'll need to know the use of web services. To acquire basic knowledge of web services,soap and xml-rpc read below url
http://nanostuffs.com/Blog/?p=1152
http://blog.manishchhabra.com/2013/04/rest-and-soap-web-services-analogy/
After getting basic knowledge of web services read how to use it in magento from below url
http://www.magentocommerce.com/wiki/5_-_modules_and_development/0_-_module_development_in_magento/introduction
http://inchoo.net/ecommerce/magento/magento-api-v2/
http://inchoo.net/ecommerce/magento/magento-v2-soap-demystified/

Composite C1 - Membership Provider - Simple Registration and Login

I am developing my first application using the Composite C1 CMS as the core system. I am currently working my way through the documentation and learning about data structuring, etc. I see that there is a paid Extranet package which can be purchased but I would prefer to develop my own Membership system within the site.
What would be the best way for me to allow users to register on the front end of my Composite C1 website and then to allow them access to a password protected area once they have registered and logged in?
I am a fairly experienced .net developer but Composite C1 is very new to me (at first impressions I like it a lot!)
Thanks
Like the commercial Extranet package you can write a RenderingResponseHandler plugin and register it it the ~/App_Data/Composite/Composite.config file.
Check the guide "How can I validate users before a page or media file is being served?"
RenderingResponseHandler plugins are tasked with approving page and media requests and they can either let the request pass or redirect the request to a new URL.
You would need to take care of the user data base and login page yourself. Also some mechanism that would allow a user of the cms to mark pages as protected/public might make sense.
There is relevant pointers on the CodePlex thread "Restricting access to MediaArchive files"

Integrate a facebook c# sdk login system into an existing login system based on Microsoft Membership Api

I'm trying to figure out how should I integrate facebook login system in my existing application through facebook c# sdk.
I have a web forms application and I'm authenticating users by standard Login control.
I'm using MembershipProvider, RoleProvider and ProfileProvider.
I'm thinking I should persist FacebookUniqueID and put it into relation with existing informations on my Membership Users table.
I'm wondering wich is a correct approach to this.
Considering I have a custom Profile Provider that uses a custom sql table, it would be fast to add a FacebookUniqueID property to my user profiles and use it in my login workflow:
Login through facebook;
retrieve facebookUniqueID;
retrieve userName for the user that
have this specific facebookUniqueID,
then
FormsAuthentication.SetAuthCookie(userName, bool);
What about providing an overload for the previous method taking facebookUniqueID as parameter?
Please let me know what do you think about this from any perspective and if anyone knows a simple working example
I think you are on the right track. We implement a similar solution (though we have rolled our own custom membership/role/profile etc and don't use the built in approach.)
You also will have to handle the situations that occur when a new user (without an existing account) logs into your site via Facebook.

Resources