Theme routing getting error?

Answered
  1. 4 years ago

    Hi,
    On a fresh local install of wardrobe, and choosing the 'simple' theme (same issue in the 'blocky' theme), I can't seem to access the route '/about' when I goto the '/about' path.

    View [simple.about] not found.

    The basic routes that are defined in the controller seem to work fine, like '/archive'. It seems to be some sort of pathing/configuration issue where the theme's view files aren't being loaded up (maybe theme_view() isn't resolving to the right path?) in the Theme's special routing file /public/themes/simple/routes.php:

    Route::get('/about', function()
    {
        return View::make(theme_view('about'));
    });

    Is anybody seeing the same issue?

    After a little research and bugfixing i tried to commit my changes on github, just to notice that they are all allready fixed, lol!

    For me it totaly looks like if you install wardrobe via composer, you get the wrong (old) wardrobe/core branch.

  2. Edited 4 years ago by ciruz

    Hi,

    yes i see the same problem on a fresh installation, with a couple of other problems like that the status filter (dropdown) in admin don't work correct, or the forgot password site throws a 404 (www.example.com/wardrobe/login/remind ).

    Generally i have to say right now i'm not so happy with the theme system out of the box, because if the *.blade.php files are saved in /public you can access them (like: post.blade.php , inc/post.blade.php ]), so if you customize a view and you use blade syntax in view, anyone can see this blade code (not php code ;) !).

  3. ciruz

    Nov 8 Answer

    After a little research and bugfixing i tried to commit my changes on github, just to notice that they are all allready fixed, lol!

    For me it totaly looks like if you install wardrobe via composer, you get the wrong (old) wardrobe/core branch.

  4. Yes, I did install wardrobe via composer, and that indeed seemed to be the issue, the wardrobe reference in my composer.json was to the 1.0 of core, changing it to the cutting edge dev version seemed to fix the issues, thanks!

    "wardrobe/core": "dev-master"
  5. 3 years ago

    csanad

    Apr 10 Moderator Auckland, New Zealand

    ciruz Generally i have to say right now i'm not so happy with the theme system out of the box, because if the *.blade.php files are saved in /public you can access them (like: post.blade.php , inc/post.blade.php ]), so if you customize a view and you use blade syntax in view, anyone can see this blade code (not php code ;) !).

    The workaround is really easy. Just have an .htaccess in your theme folder with the following content:

    Satisfy all
    Order deny,allow
    Deny from all
    Allow from 127.0.0.1

    And have an other .htaccess in the theme css folder with the following:

    Allow from all

    Thats it. Your Wardrobe is secured.

  6. Deleted 3 years ago by jshw08

or Sign Up to reply!