On 11/7/06, Synchro <[EMAIL PROTECTED]> wrote:

>
> Well I already posted the absolutely minimal (so minimal you probably
> missed it!) example that was not working for me. With routing enabled
> in core, this code results in a 404 for xmlrpc.txt:
>
> The model is just an empty class. In
> app/controllers/things_controller.php:
>
> function xmlrpc_doSomething() {
>   echo 'hello';
> }

> In app/views/things/xmlrpc/do_something.thtml:
> blah
>
> but when I hit /xmlrpc/things/do_something I get a 404 looking for
> xmlrpc.txt. XML functionality doesn't enter into it if I can't stuff in
> something and get something out.
>

Okay, let's back up and help this cranky developer understand your problem.

First of all, are you using any XMLRPC or XML helpers?  I've never
used them so that could be causing the problem

Secondly, the correct call to the action you specified above should be:

/things/xmlrpc_doSomething

Because you have an action called 'xmlrpc_doSomething' as part of the
'things' controller.  My appologies if I'm misunderstanding things.

According to what you've posted above, if you call
/things/xmlrpc_doSomething in a browser we should see 'blah' outputted
in the browser window.

Other than this, I suggest that if you haven't already done so, set
DEBUG to 1 in order to prevent Cake from caching anything.

Hope that helps, and I'm interested in seeing what the solution to
this problem is.  It can't be this hard. :)

-- 
Chris Hartjes

"The greatest inefficiencies come from solving problems you will never have."
-- Rasmus Lerdorf

@TheBallpark - http://www.littlehart.net/attheballpark
@TheKeyboard - http://www.littlehart.net/atthekeyboard

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Cake PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to