Hello There,

According to your documentation the "jomsocial_rule.xml" seems to only work when inside a component root folder
<component>com_[Component Name]</component>

Is the scan rule limited to components?! could this be:
<plugin>com_[Component Name]</plugin>
and have jomsocial scan plugin/community folder

Hi.

I assign developer to this thread.

Hi There,

When you do "scan" our code will search jomsocial_rule.xml file inside folders components,modules and plugins..

So it will work inside all componentns, modules and plugins not only for com_community.

I hope it will help

I tested by inserting jomsocial_rule.xml inside:
component = works
module = works
plugin system = does not work
plugin community = does not work

Please make sure you test before answering with "wishful thinking" or asking ftp access.
The platform is joomla 2.5

Hi,

Ok, could provide me the FTP access? I will check the code directly on your server.

Than you

OMG!!!
please read what I wrote :D

Hi There,

I am sorry, I dont really undersatnd what you mean :(

thank you

Hello,

Can someone help Dimas with english and tell him how to replicate the problem.

I tested by inserting jomsocial_rule.xml inside:
component = works
module = works
plugin system = does not work
plugin community = does not work

Hi Tech Grasp,

Dimas is one of our developers and i can only assume that a quick look directly at the code would have allowed him to answer your question or confirm there is a bug, You are clearly not happy with Dimas's response so i will get another developer to look at this post and reply shortly.

Please remember that you can always ask for another support person to look at an issue if you feel you are not getting the correct reply or you can escalated a post and i will see it. Your last reply was really not appropriate.

Have a great day

Hello Paul,

Thanks for your help.
I provide support for many years now and for several companies. You do not confirm a bug asking for admin access and "fu****g" with customers websites.

Bugs are confirmed in more than one platform, specially not the originating one. Also, when something is reported, it's up to the support team to replicate the issue on their test benches (j2.5 and j3.3).

I find rather annoying "to say the least", the continued "ask for admin access" without even the slightest effort to confirm the issue first in test benches. "Admin access" should be for many reasons the last resort, not the first one. Included here is also the fact that support usually does not reply the questions raised on the ticket with correct answer(s) according to the ticket. I ask for "potatoes and get onions", and the onions always come with the "admin access" side dish.

It would be wonderful if you could start providing support by making an effort in your test benches.

H TechGraspi,

You have raised some really good points and i would like to explain why we do support the way we do.
We often get asked why we need access for such a simple problem. The reason we ask for access first is we do over 1000 support tickets a month but have maybe 20 - 30 confirmed bugs a month. What this means to us is that most issues are site specific, There are very few sites that do not have modified Jomsocial files in them somewhere or a conflict with a plugin that needs some adjusting. The first thing we do is try to replicate the fault on our test boxes. If we cant, then we need access or we end up guessing what may be wrong over days and days and it is a pointless exercise that frustrates the customer.

To put it into perspective lets say you have 1000 of your plugins on customers sites and 970 of them have customer modified files in them. 970 of your attempts to replicate the problem will not be possible to replicate on a test box. Because we provide a large complex component we understand that most of our customers will modify our files in one way or another and this is great, we want them to tweak their sites. Because of this, the most efficient way for us to provide the best support to our customers is to collect access information at the time of the post or shortly after.As a default response

Replying to over 1000 support posts a month i can assure you the last thing we want to do is log into your site and "fiddle" with your site files. When we do make a change to your site we can tell you what has been changed. A really good way to eliminate this problem if you are concerned about it is to setup a replication of your site and supply access to that, You then have full control over anything done on the live site, Amazingly we get about 10 in around 5000 customers ask us what we changed/fixed.

I hope this clears up any question about why we use thees methods to provide support. While some things may not be obvious at first glance we are always happy to explain it when asked.

But even after explaining all this, i agree this post could have been dealt with differently and i apologize for that. I will have our developer look at this question when they start their next shift.