Ok, i'm getting closer to having a working install, but the URL links seems
to get messed up.
1) I can get some text content on the home page ( try www.mobiletribes.com),
but all the links on the page (Register, Help, etc.) have an extra "/
index.ph/index.php/"
e.g. i get Help link - www.mobiletribes.com/index.ph/index.php/doc/help
Search link -
www.mobiletribes.com/index.ph/index.php/search/people
2) Also, the page won't load any images (perhaps for the same root problem)
- try www.mobiletribes.com
Could someone tell me how to correct this? My config.php file is very clean
now - just has [db][database] and [site][name] parameters.
Appreciate your help
thanks
Kiran
On Thu, Jun 11, 2009 at 9:00 AM, <[email protected]> wrote:
> Send Laconica-dev mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.laconi.ca/mailman/listinfo/laconica-dev
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Laconica-dev digest..."
>
>
> Today's Topics:
>
> 1. page parameter in user_timeline (Serge R)
> 2. [proposal] Event handler for logins (jim sloan)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 11 Jun 2009 11:14:15 +0200
> From: "Serge R" <[email protected]>
> Subject: [Laconica-dev] page parameter in user_timeline
> To: <[email protected]>
> Message-ID: <000e01c9ea74$fee2c470$fca84d...@com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all,
>
>
>
> I've tried to get user timeline as Json object from my local laconica
> instance. The problem is, if the page number parameter (&page=.) is bigger
> than 2, a empty Json object will be returned. There are a lot of messages
> (more than 20), if I call
>
> /api/statuses/user_timeline.json?user_id=serge
> <
> http://localhost/laconica/api/statuses/user_timeline.json?user_id=serge&cou
> nt=1&page=1> &count=1&page=1 , it works. I get the last status from user
> serge. If I call
>
> /api/statuses/user_timeline.json?user_id=serge
> <
> http://localhost/laconica/api/statuses/user_timeline.json?user_id=serge&cou
> nt=1&page=2> &count=1&page=2 , it works. I get next to last status. But by
> starting to call a URL with page parameter bigger than 2, for example
>
> /api/statuses/user_timeline.json?user_id=serge
> <
> http://localhost/laconica/api/statuses/user_timeline.json?user_id=serge&cou
> nt=1&page=3> &count=1&page=3 , a empty Json object will be returned. I
> tried
> to test it on identi.ca and it did work fine. But it is not running on my
> both (one local and another one on my server) laconica instances ((both
> have
> the version 0.7.3)).
>
>
>
> I tried to change the URL to /api/statuses/user_timeline/serge.json?count=1
> <
> http://localhost/laconica/api/statuses/user_timeline/serge.json?count=1&pag
> e=3> &page=3 or to use the screen_name instead of user_id and it did not
> work too.
>
>
>
> Somebody knows what can be wrong there?
>
> __
>
> Serge
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.laconi.ca/pipermail/laconica-dev/attachments/20090611/0537f815/attachment.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 11 Jun 2009 06:38:30 -0400
> From: jim sloan <[email protected]>
> Subject: [Laconica-dev] [proposal] Event handler for logins
> To: [email protected]
> Message-ID:
> <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> A couple of weeks ago I posted a "hack" to enable Active Directory (LDAP)
> authentication by adding code to the common_check_user() function, and that
> works, but I don't think that it is the best way to approach alternate
> authentication methods. I've reworked it using the Event::handler and
> would
> like input from the developers.
>
> As it is written now I just add the handler at the begining of the
> common_check_user() function and if there is a plugin that acts on this
> event then that is as far as it goes and it returns $user.
>
> // add a login handler
> $user = null;
> if (Event::handle('CheckUser', array($nickname, $password, &$user))){
> return $user;
> }
>
> We probably want to allow for simultaneous methods, with some sort of order
> precedent, and a default. (i.e. try LDAP and if it fails then try the
> local
> account.) But before I go any further I would like to hear some
> suggestions.
>
> Is this the best way to introduce authentication plugins? Maybe there
> should be both a "Start" and "End" handle ??
>
> As far as the plugins are concerned I have this working with the adLDAP
> plugin and a PEAR Net_Ldap2 plugin. They merely authenticate the user:pass
> credietials and return the $user array if authenticated.
>
> I'll post the code at my clone of dev
> http://gitorious.org/~jsloan/laconica/jsloan-sandbox<
> http://gitorious.org/%7Ejsloan/laconica/jsloan-sandbox<http://gitorious.org/~jsloan/laconica/jsloan-sandbox>
> >
>
> thanks
> jim sloan
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.laconi.ca/pipermail/laconica-dev/attachments/20090611/e90d62f2/attachment-0001.htm
> >
>
> ------------------------------
>
> _______________________________________________
> Laconica-dev mailing list
> [email protected]
> http://mail.laconi.ca/mailman/listinfo/laconica-dev
>
>
> End of Laconica-dev Digest, Vol 12, Issue 16
> ********************************************
>
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
