Good to hear you got a workaround - it's the one I resorted to when I
first encountered the problem. I guess that explains why the ticket is
still open.  You may want to add a comment to it to let the relevant
parties know your usage scenario that still doesn't work.


On Sat, Aug 29, 2009 at 2:56 PM, Guido Erlinger<[email protected]> wrote:
>
> Hi Colin,
>
> Colin wrote:
>>
>> Indeed there is/was a bug in InputFilter::parse_url() -
>> http://trac.habariproject.org/habari/ticket/537
>>
>> I believe it's now resolved in the SVN code.
>>
>> Try the latest SVN code and see if that helps.
>
> OK! Like I said in my previous mail, it is not solved!
> The result if InputFilter::parse_url() which I posted in my forst
> mail, is the result of the current svn version.
>
> My workaround, which works for me, is the use of the PHP function
> parse_url() ... I just changed the the code of
> InputFilter::parse_url() in the way, that the results of
> preg_match_all() is replaced by the values of the php function
> parse_url().
>
> cu, guido
>
>
>
>> On Fri, Aug 28, 2009 at 11:03 PM, helpy (Guido Erlinger)<[email protected]> 
>> wrote:
>>> there seems to be an error in InputFilter::parse_url()
>>>
>>> InputFilter::parse_url() splits the url http://www.helpy.de/ into:
>>> (     [scheme] => http
>>>      [host] => www.helpy.de
>>>      .... )
>>>
>>>
>>> InputFilter::parse_url() splits the url http://en.helpy.de/ into:
>>> (     [scheme] => http
>>>      [host] => en
>>>      ...
>>>      [path] => .helpy.de
>>>      ... )
>>>
>>> Does somebody can confirm this?
>>>
>>> This is probably the reason,
>>> why multisite feature does not work for me!
>
> >
>



-- 
Colin Seymour
Blog: http://www.colinseymour.co.uk
Tech Stuff: http://www.lildude.co.uk

--~--~---------~--~----~------------~-------~--~----~
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/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to