Error 406

Please use these since they contain a couple of important bug fixes and new features: (they will make no difference on error 406)

v2.0 RC8 r1460 for J2.5

v1.5.6 RC8 r1460 for J1.5

Thank you. I was going to build a few new test sites anyway, so I will install it there.. I installed another CCK that must have installed over 50 plugins and other crap. I am not going to use that thing again, but now my test site is shot.

I was wondering if you would be available to answer a few questions once my partner and I have had a chance to review FC and some of the competition. I don't want you to go by my assessment of the project alone and I want to make sure we get the original database and script we are supposed to rebuild first, but at some point we would like to give you an overview and get your opinion if FC would be a good choice for that use.

Essentially, as I posted on the forum, we have a product catalog and then a separate list of users that can request to be alerted of changes on the products.

The problem we saw with K2 and Sobi Pro is that all the data from the custom fields we created goes into a single table regardless of where the fields belong.

In any case, as I said I'd prefer to wait until our minds are a bit clearer. Would you be available?

Thank you.

- About subscribing to receive updates on changes of products this is done by displaying favourites field in the frontend item / category view.

When an editor saves an item, he/she can select whether to notify subscribed users "favoring" the item

- Currently focusing on bug fixes (i hope no important bugs exist now) , and finishing some almost finished powerful features.

I need to finish as soon as possible since after Monday i will have little time.

- I have wrote various articles for developers but if you have a question not answered already, i will write a couple more.

But currently i do not have time to offer custom development

Thanks for the clarification. I wasn't actually asking for custom development. Much less than that. I would not want to take advantage of anyone not on my payroll.

The subscription model we are trying to emulate I am afraid is a lot more complex than that, but before I even get into that we'll need to do some homework to be able to present it in a way that makes sense. It's so very close to be possible with off the shelf scripts, but some specific requirements make it a lot harder to manage.

in regard to the assistance I am looking for it's much more simple. We were just going to spec out what we are trying to accomplish and then submit it to you or anyone with a little bit of spare time just so you can tell us if you think it's something FC could do.
Once we know if it can be done or not, then it will be our job to make it happen (and we may use the forum a lot for help, but on a community level). I was not trying to recruit you to work for us

We basically just would like some guidance once we are a bit more advanced in our project. We'd be happy to pay someone too if anyone there would like to help, but only on an advisory level.

Anyway, I am logging off for the day. When we get to that point I'll let you know and if by then you have a few minutes to spare to give us advice, great. If you have someone else in mind that may help, good too or if no one can help, we'll manage anyway. I'll leave it on the forum for others to answer.

Thank you very much for all the help so far.

1. FLEXIcontent field plugin are Joomla plugin of type "flexicontent_items"

2. You can create a custom field that displays in frontend and allows users to register to receive more complex updates

3. If you call you new field subscribeprd
(files subscribeprd.php and subscribeprd.xml)
then you can call any function you create from frontend via URLs:

-- e.g to call function myfunc1(...) inside the subscribeprd.php
you call URL (e.g. via AJAX too ...):

index.php?option=com_flexicontent&task=doplgact&plg=subscribeprd&act=myfunc1&var1=val1&var2=val2

the var1 and var2 you get inside the function, use
$var1 = JRequest:getVar('var1');
$var2 = JRequest:getVar('var2');

4. You will also need to alter a little the various functions inside the plugin, e.g. The onBeforeSaveField() you can use to detect the item being saved