Asset url includes index.php

[pentium10]

<link href="{{ Theme.asset().url('img/favicon.ico') }}" rel="icon" type="image/x-icon" />

and I got:

<link href="http://localhost/frontend/public/index.php/themes/gray/assets/img/favicon.ico" rel="icon" type="image/x-icon" />

which is invalid as contains index.php, file is located at: frontend\public\themes\gray\assets\img\favicon.ico

[teepluss]

"composer update teepluss/theme"

[pentium10]

Nothing to install or update.

So this problem of mine is still open.

[teepluss]

I will re-check again. On Apr 4, 2014 1:20 AM, "Pentium10" notifications@github.com wrote:

Nothing to install or update.

So this problem of mine is still open.

Reply to this email directly or view it on GitHubhttps://github.com/teepluss/laravel4-theme/issues/56#issuecomment-39486277 .

[pentium10]

The URL I am calling is this:

public/index.php

[teepluss]

try config /app/packages/teepluss/theme/config/config.php

/*
    |--------------------------------------------------------------------------
    | Asset url path
    |--------------------------------------------------------------------------
    |
    | The path to asset, this config can be cdn host.
    | eg. http://cdn.domain.com
    |
    */

    'assetUrl' => URL::to('/'),

[pentium10]

I had this already, as far I see the problem is when the user comes in via index.php page. So urls will be like

index.php/welcome
index.php/pricing

and this way it doesn't work.

[teepluss]

Right now I found the problem, so I’ve fixed it.

jQueryTips Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Friday, April 4, 2557 BC at 12:07 PM, Pentium10 wrote:

I had this already, as far I see the problem is when the user comes in via index.php page. So urls will be like
index.php/welcome index.php/pricing
and this time it doesn't work.

— Reply to this email directly or view it on GitHub (https://github.com/teepluss/laravel4-theme/issues/56#issuecomment-39532315).

[pentium10]

There might be something wrong with the recommended composer.json block too. When I had:

"teepluss/theme": "dev-master"

it didn't see the update you commited a couple of minutes ago,

but once I changed to:

"teepluss/theme": "1.*"

it was ok, and it looks like it's working now fine.

[teepluss]

rm - rf ~/.composer/cache On Apr 4, 2014 12:30 PM, "Pentium10" notifications@github.com wrote:

There might be something wrong with the recommended composer.json block too. When I had:

"teepluss/theme": "dev-master"

it didn't see the update you commited a couple of minutes ago,

but once I changed to:

"teepluss/theme": "1.*"

it was ok.

Reply to this email directly or view it on GitHubhttps://github.com/teepluss/laravel4-theme/issues/56#issuecomment-39533068 .